You are not logged in.
Pages: 1
Hello all.
I have an HP Photosmart C4280 All-in-One, and here's my problem. When I first boot into Arch and turn on the printer, it works fine. However, after the printer is turned off and, later, back on, it no longer works. Therefore, I have to print things when I first turn on the computer or print and then restart, which prints the documents immediately after startup. Here is the appropriate section of /var/log/messages.log after turning on the printer (for a second time after startup; as I said, it mounts and works fine the first time):
Apr 28 11:46:11 arch usb 4-2: new high speed USB device using ehci_hcd and address 7
Apr 28 11:46:11 arch usb 4-2: configuration #1 chosen from 1 choice
Apr 28 11:46:11 arch usblp0: USB Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5C11
Apr 28 11:46:11 arch logger: cannot find module usb:v03F0p5C11d0100dc00dsc00dp00icFFiscCCip00
Apr 28 11:46:11 arch scsi6 : SCSI emulation for USB Mass Storage devices
Apr 28 11:46:11 arch logger: cannot find module usb:v03F0p5C11d0100dc00dsc00dp00icFFiscFFipFF
Apr 28 11:46:16 arch scsi 6:0:0:0: Direct-Access HP Photosmart C4280 1.00 PQ: 0 ANSI: 5
Apr 28 11:46:16 arch sd 6:0:0:0: [sdc] Attached SCSI removable disk
Apr 28 11:46:16 arch sd 6:0:0:0: Attached scsi generic sg4 type 0
Any ideas on what is going wrong and/or how to fix it?
Last edited by nabl (2008-04-29 20:00:09)
Offline
what about creating an udev entry which loads your printer module (I dunno, usblp maybe?) and then unloads it at printer poweroff?
Try the following.
Powerup your pc, and print something.
Poweroff your MFC and rmmod usblp (as uncle sam )
Powerup your MFC and try to print again.
If it works, read about creating udev rules. I know how to create some of them, but I'm not a master, so I recommend you to google a little bit until you get proper information (or try man udev )
See ya.
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
Before getting too deep in udev intricacies, I would suggest you try fixing the known problem in the klibc-udev package, which affects device recognition. You can do that by running this (as root):
sed -i -r 's|echo *-e.*/proc/sys/kernel/hotplug|echo "" > /proc/sys/kernel/hotplug|' /lib/initcpio/udev/start_udev
and then rebuilding your initramfs:
mkinitcpio -p kernel26
and then rebooting.
larch: http://larch.berlios.de
Offline
I had exactly the same problem and your solution just works fine for me. Thanks
Last edited by jeanuel (2008-04-29 15:19:56)
Offline
Before getting too deep in udev intricacies, I would suggest you try fixing the known problem in the klibc-udev package, which affects device recognition. You can do that by running this (as root):
sed -i -r 's|echo *-e.*/proc/sys/kernel/hotplug|echo "" > /proc/sys/kernel/hotplug|' /lib/initcpio/udev/start_udev
and then rebuilding your initramfs:
mkinitcpio -p kernel26
and then rebooting.
Thanks a million! That worked perfectly!
Offline
I was having an issue with a Canon a610 and this partially solved the problem. I can download pictures via digiKam, but still can't access the files via Konqueror like I used to.
Thanks!
Offline
Is this klibc-udev thing still an issue (and a fix)? My canon camera stopped working (AGAIN), I've fixed it 3 or 4 times already, and now none of the old fixes are working. just wondering if it's still necessary to run this fix for klibc-udev before i go through the whole thing only to find out it's been fixed and it's some other problem.
this udev thing with the camera breaking every other month is really getting old. :roll:
Offline
There is a fix/work-around in the latest initscripts (/etc/rc.sysinit), so although klibc-udev still has the bug (I think), it doesn't do any harm.
larch: http://larch.berlios.de
Offline
This fix did not work for me... When I typed as root:
sed -i -r 's|echo *-e.*/proc/sys/kernel/hotplug|echo "" > /proc/sys/kernel/hotplug|' /lib/initcpio/udev/start_udev
I received the following error:
sed: can't read /lib/initcpio/udev/start_udev: No such file or directory
I then entered:
mkinitcpio -p kernel26
And then rebooted... I still have the errors "could not lock device" and "device in use" errors though...
Offline
Okay, I found a way to get around this... If you plug in your camera and it is auto detected/mounted you must then unmount (umount) the device. After that, you can open F-Spot or gThumb and import without any errors. I really hope they fix this issue soon because it's annoying and definitely isn't a confidence builder...
Offline
Pages: 1