On Fri, 28 Jul 2006, Alejandro Riveira Fernández wrote:

> > > Hi,
> > > 
> > > I'm having problems with usb and lastest 2.6.18-rc kernels. lsusb does
> > > not give any output although the usb harware seems to work properly. The
> > > usb mouse and speedtouch modem do work but cups does not recognize my hp
> > > printer.
> > 
> > What does /proc/bus/usb/devices show?  Note that you may need to mount 
> > /proc/bus/usb before you can see anything:
> > 
> >     mount -t usbfs usbfs /proc/bus/usb
> 
> Yes, I did have to mount it manually... extrange becouse it did get
> mounted automatically in prior kernels (2.6.17.2).
> for the record i'm using ubuntu dapper. the output of the following
> command is with an 2.6.18-rc2 kernel (debug_usb is not set)
> 
> $ cat /proc/bus/usb/devices

> T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=03f0 ProdID=1904 Rev= 1.00
> S:  Manufacturer=Hewlett-Packard
> S:  Product=DeskJet 3820
> S:  SerialNumber=CN32J1C20K18
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  2mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

> Nothing shows up when I turn on the printer only when i turn it off:
> 
> Jul 28 02:38:07 localhost kernel: usb 2-1: USB disconnect, address 3
> Jul 28 02:38:07 localhost kernel: drivers/usb/class/usblp.c: usblp0: removed
> Jul 28 02:38:08 localhost kernel: ohci_hcd 0000:00:0a.1: wakeup
> Jul 28 02:38:08 localhost kernel: usb 2-1: new full speed USB device using 
> ohci_hcd and address 4
> Jul 28 02:38:09 localhost kernel: usb 2-1: Product: DeskJet 3820
> Jul 28 02:38:09 localhost kernel: usb 2-1: Manufacturer: Hewlett-Packard
> Jul 28 02:38:09 localhost kernel: usb 2-1: SerialNumber: CN32J1C20K18
> Jul 28 02:38:09 localhost kernel: usb 2-1: configuration #1 chosen from 1 
> choice
> Jul 28 02:38:09 localhost kernel: drivers/usb/class/usblp.c: usblp0: USB 
> Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x1904

This is what show up when you turn the printer on.  It looks like 
everything is working normally.

> I have used git bisect to pin down the bad commit. Both problems: lsusb
> not showing anything due to usbfs not getting mounted automatically and
> the printer not working[1] appear with the following commit:
> 
> c182274ffe1277f4e7c564719a696a37cacf74ea is first bad commit
> commit c182274ffe1277f4e7c564719a696a37cacf74ea
> Author: Greg Kroah-Hartman <[EMAIL PROTECTED]>
> Date:   Mon Jun 19 23:59:31 2006 -0700
> 
>     [PATCH] USB: move usb_device_class class devices to be real devices
>     
>     This moves the usb class devices that control the usbfs nodes to show up
>     in the proper place in the larger device tree.
>     
>     No userspace changes is needed, this is compatible due to the symlinks
>     generated by the driver core.
>     
>     Cc: Kay Sievers <[EMAIL PROTECTED]>
>     Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
> 
> :040000 040000 879a23a817afb7237bb79a24d2b80ebf66ec52cd 
> a9f43bad474a0d1877db24a11282427e863a2718 M    drivers
> :040000 040000 167350de305feb4e79d2656f00b28475461405ce 
> e2957848b084cce6cbab275d636ee8685ddbd789 M    include

Are you certain this patch is responsible?  That is, if you remove the 
patch does everything then work correctly?

This really appears to be a problem with ubuntu, not with the kernel.  
Have you tried asking on an ubuntu mailing list?

Alan Stern


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to