Re: SUSE 10.1 Printer problem
- From: Lee Ayrton <layrton@xxxxxxxxx>
- Date: Mon, 26 Feb 2007 17:41:23 -0500
On Sun, 25 Feb 2007, Darrell Stec wrote:
Lee Ayrton perhaps from layrton@xxxxxxxxx wrote:
[snip]Store-bought packaged SUSE v10.1
Compaq Professional Workstation AP550, SCSI HD, external SCSI Zip100
drive, internal FDD.
Loaded SUSE as a new dual-boot install on a machine that was successfully running RH Workstation (Once I remembered that you have to use DOS FDISK before mucking with partitions in Linux...). I've done a
In the many Suse installations I have done (OK, not quite as many as
some of our resident geniuses like Houghi have done), I found using
Fdisk and Partition Magic really mucked things up. This is especially
true if one used a product like Disk Manager to initially set up the
drive. Suse is very clever at setting up the proper partitions all by
itself. You can accept the default values it gives or change some
values. In older version I recommended setting up a separate /home
directory. I believe that since 10.1 Suse does that automatically.
For whatever stupid whim I'd had a few years ago, the dual-boot DOS/RH system ended up with a 1MB DOS primary partition and a 100MB DOS Extended partion, plus whatever awful partition hash I made of the RH install.
After a few false starts with the SUSE install I ended up backing all of my DOS stuff off onto floppies, booting from a DOS floppy, and using FDISK to delete all of the existing partition information. Then I created and a single 100MB DOS (MS-DOS v6.22, no Windows), made that the Primary and left the rest of the disk uncommitted. Rebooting in SUSE install, SUSE then gracefully took over the rest of the disk and I happily accepted the offered defaults, including a 9.6GB /home partition. Unlike the discarded RH system, SUSE can see into the DOS partition, but I haven't played any further with _that_.
[snip other error messages]Problem 1:
SUSE correctly senses local printer, a HP LaserJet 6L on parallel port 0. I am unable to print to it. As Root from YaST2 I attempt to print test pages that always result in an error message window:
Unable to print test page.
Output from lpr:
lpr: error - unable to print file:
Did you set up a password for the Print Manager yet? I've had to do
this before I could print on my printer. It never asks for it in usage
but I am pretty sure it must be done initially at first.
No, I didn't know to try that. As root I tried
lppasswd -a root
and gave it a password, without any change in printer-as-doorstop status. Partial success was then had by stumbling onto the CUPS management utility at http://localhost631 Under "manage printers" I reset the local parallel printer "reject jobs" status and successfully printed the test page.
However, the network printer stll won't print, status is given as: (Cut-n-pasted):
Printer State: idle, accepting jobs.
"Network host '192.168.0.4' is busy; will retry in 30 seconds..."
Device URI: http://192.168.0.4:631/
Going to that address with Firefox allows me access to the miniprint server there, and allows me to print its on-board test page, but I can't the CUPS test page.
Changing from URI to http changes the messages, (I also changed the driver to HP LJ-III), but still no joy on printing the test page (Cut-n-paste):
Description: ActionLaser-1500 as HP LJ-III
Printer State: processing, accepting jobs.
"Connected to 192.168.0.4..."
Device URI: http://192.168.0.4:80/
Is this a network configuration problem on this machine? It did work under HR, the only change has been the OS on this box.
SUSE sees the floppy drive and provides me with a handy desktop icon,
refuses to easily mount it. Attempts to mount the drive as root from
the desktop result in an error message window:
[show more details]
Method "Mount" with signature "ssas" on interface
"org.freedesktop.Hal.Device.Volume" doesn't exist.
I am able to mount to device successfully as root from a terminal
window, but that's clunky.
My floppies, CD, DVD and USB flash drives all mount automatically with
Suse 10.0. I don't even have an icon with this version. Did you make
the icon or did Suse place it on your desktop at installation?
SUSE placed the icons on the desktop as part of the install.
SUSE senses the external SCSI Zip 100 drive and provide me wit ha
handy desktop icon for it, but will not mount it from the desktop. The
error messsage window:
Could not create dbus message
[show more details]
I was able to successfully mount it from a terminal window as root and
moved the files I needed off, but /that/ is part of Problem 4. When I
attempted to unmount it from the desktop the system complainted that
it couldn't figure out where the device was mounted.
[SNIP Hint on how to cut-n-paste from fstab to PINE -- thanks!]
/dev/sda6 / reiserfs acl,user_xattr 1 1
/dev/sda7 /home reiserfs acl,user_xattr 1 2
/dev/sda1 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/sda5 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/sdb4 /media/zip auto noauto,user 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
The entry /dev/sdb4 _looks_ OK to my novice eyes -- the Zip drive is an external SCSI device and has always ID itself as 4. I just checked the back of the drive and the ID switch is set to "5" (options are 5 or 6), I assume that drive numbers are zero-based. Termination is ON, and it's the only external device. But it won't behave from the desktop.
Suggestions? Any other places to look?
[snip advice on changing file permissions Thanks again!]
"We began to realize, as we plowed on with the destruction of New Jersey,
that the extent of our American lunatic fringe had been underestimated."
Orson Wells on the reaction to the _War Of The Worlds_ broadcast.
- Prev by Date: Dell to sell full line of consumer Linux computers
- Next by Date: Re: Dell to sell full line of consumer Linux computers
- Previous by thread: Re: SUSE 10.1 Printer problem
- Next by thread: xine and yuotube