On Tue, May 05, 2009 at 11:46:14AM +0100, lux-integ wrote: > Greetings, > > My LFS setup is with Linux (AMD64 64bit-only) > kernel2.6.27.7, CUPS-1.3.9 and KDE4.2.1. I have KDE working. I have > and epson stylus DX6000 (USB) printer/scanner attached. The CUPS daemon > is running, for example http://localhost:631 responds. However on > launching kdeprint, nothing happens. > > I compiled the kernel with USB printer support. However the device is > seen as a 'scssi-emulated' usb-storage device. Is there a hal setup for > usb-printer that overcomes this? > Yeah, recent kernels report strangely for usb printers. This is what I get from 2.6.28.10.
May 5 13:37:37 ac30 kernel: usb 1-1: new high speed USB device using ehci_hcd and address 2 May 5 13:37:37 ac30 kernel: usb 1-1: configuration #1 chosen from 1 choice May 5 13:37:37 ac30 kernel: Initializing USB Mass Storage driver... May 5 13:37:37 ac30 kernel: scsi4 : SCSI emulation for USB Mass Storage devices May 5 13:37:37 ac30 kernel: usbcore: registered new interface driver usb-storage May 5 13:37:37 ac30 kernel: USB Mass Storage support registered. May 5 13:37:37 ac30 kernel: usb-storage: device found at 2 May 5 13:37:37 ac30 kernel: usb-storage: waiting for device to settle before scanning May 5 13:37:37 ac30 kernel: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x04B8 pid 0x082C May 5 13:37:37 ac30 kernel: usbcore: registered new interface driver usblp May 5 13:37:42 ac30 kernel: scsi 4:0:0:0: Direct-Access EPSON Stylus Storage 1.00 PQ: 0 ANSI: 2 May 5 13:37:42 ac30 kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk May 5 13:37:42 ac30 kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0 May 5 13:37:42 ac30 kernel: usb-storage: device scan complete Dunno when it decided to mention usb-storage, but it seems to work (I don't print from kde). This is with the host controllers built in and the usb printer and usb storage as modules. Perhaps this system has always reported like that because they are both modules (i.e. all usb modules get loaded because _something_ showed up on the usb bus). For clfs, I've always had to add things to the minimalist rules in that book. In this case, a rule for the printer: BUS=="usb", KERNEL=="lp[0-9]*", NAME="usb/%k", GROUP="lp" With recent versions of udev that might no longer be necessary. In cups, I always make sure the printer is set as the default - a few things print to the default printer, and (if started from an xterm) can fail noisily if there is no default. If you can start the application you use from konsole, you might get more diagnostic information. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
