Re: [OT] usbnet problem on pc side

Oliver Kurth wrote:
>

> When you plug the ipaq into the cradle, do yiu see _any_ message in the
> kernel logs of your desktop (dmesg, or cat /proc/kmsg)? Even if usb is
> not running on the ipaq, you should see someting like "device not
> accepting new address". If you do not see anything, it's probably
> someting with the cable.

yes. *a lifesign* :

Sep 5 18:08:43 kleineronkel kernel: usb.c: registered new driver
usbnet
Sep 5 18:08:54 kleineronkel kernel: hub.c: USB new device connect
on bus1/2, assigned device number 50
Sep 5 18:08:54 kleineronkel kernel: usb-uhci.c: interrupt, status
3, frame# 580
Sep 5 18:08:54 kleineronkel kernel: usb.c: USB device not accepting
new address=50 (error=-110)
Sep 5 18:08:54 kleineronkel kernel: hub.c: USB new device connect
on bus1/2, assigned device number 51
Sep 5 18:08:54 kleineronkel kernel: usb-uhci.c: interrupt, status
3, frame# 830
Sep 5 18:08:54 kleineronkel kernel: usb.c: USB device not accepting
new address=51 (error=-110)>

so it
s not the hardware. <sigh>
but neither lspci nor ifconfig -a show any traces of an ipaq :(

now what does the usb.c error mean ?
do i need to force a certain address for the ipaq ?
but usb addresses *have* to be dynamic, don't they ?

anyway, i see a bit of light now. will dig deeper into usb.
which is quite a task given the state of documentation :)

(NOI. as we said on LinuxTag when people complained about the lack
of ALSA Documentation: WTFM.)

regards,

jörn

> Greetings,
> Oliver
> --
> oliver.kurth_at_innominate.com
> software engineer innominate AG
>
> tel: +49.30.308806-0 fax: -77 www.innominate.com

-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/