Re: udev doesn't recognize my gsm dongle

[Dan Williams <dcbw redhat com>]

On Tue, 2010-02-09 at 11:46 +0100, Maxime Boure wrote:
> 
> 
> On Tue, Feb 9, 2010 at 11:29 AM, Maxime Boure <mboure ubiquiet com>
> wrote:
>         
>         
>         On Mon, Feb 8, 2010 at 11:27 PM, Dan Williams
>         <dcbw redhat com> wrote:
>                 On Mon, 2010-02-08 at 17:07 +0100, Maxime Boure wrote:
>                 > Thank for this answer !
>                 >
>                 > It is really helpful. I tried the lshal at boot and
>                 no device is
>                 > seen ... I assume that is the problem !
>                 
>                 
>                 Yeah, likely.  HAL requires that the device (a) have a
>                 driver, and (b)
>                 have the right sysfs links set up before it shows up
>                 in HAL.  This
>                 particular Huawei device is driven by the 'option'
>                 driver, so can you
>                 
>                 
>         Hmm yes I can ;) but what could I do ? :)
>         
>         
>          
>                 > But now I don't know what to do to get hal to
>                 recognize the dongle at
>                 > boot. I don't get any print from udev at boot it
>                 must be a redirection
>                 > to /dev/null/ but nm-modem-probe is for sure called
>                 with good
>                 > informations I managed to display them.
>                 >
>                 > Concerning prints at boot I got that :
>                 >
>                 > [   20.445983] usb 1-1: new high speed USB device
>                 using ehci-omap and
>                 > address 3
>                 > [   20.624420] usb 1-1: configuration #1 chosen from
>                 1 choice
>                 > [   20.651214] usb-storage: probe of 1-1:1.0 failed
>                 with error -5
>                 > [   20.702789] usb-storage: probe of 1-1:1.1 failed
>                 with error -5
>                 > [   20.766571]
>                 > [   20.766571] usb_stor_huawei_e220_init
>                 > [   20.772644] usb-storage: probe of 1-1:1.2 failed
>                 with error -1
>                 > [   20.804779]
>                 > [   20.804779] usb_stor_huawei_e220_init
>                 > [   20.810913] usb-storage: probe of 1-1:1.3 failed
>                 with error -1
>                 > [   20.817810] usb 1-1: New USB device found,
>                 idVendor=12d1,
>                 > idProduct=1003
>                 > [   20.824676] usb 1-1: New USB device strings:
>                 Mfr=2, Product=1,
>                 > SerialNumber=0
>                 > [   20.831909] usb 1-1: Product: HUAWEI Mobile
>                 > [   20.836120] usb 1-1: Manufacturer: HUAWEI
>                 Technology
>                 
>                 
>                 When this error occurs, do you have any /dev/ttyUSB*
>                 nodes?
>          
>         This error occurs at boot and indeed I don't have any ttyUSB 
>         
> I was on a strange state on my board it seems ... the option driver is
> called and the ttyUSB0 and 1 are created but I still have the same
> errors (but it is related to storage do we really care here ?):
> 
> [   20.438293] usb 1-1: new high speed USB device using ehci-omap and
> address 3
> [   20.616241] usb 1-1: configuration #1 chosen from 1 choice
> [   20.624725] usb-storage: probe of 1-1:1.0 failed with error -5
> [   20.633544] usb-storage: probe of 1-1:1.1 failed with error -5
> [   20.641113] 
> [   20.641113] usb_stor_huawei_e220_init
> [   20.648498] usb-storage: probe of 1-1:1.2 failed with error -1
> [   20.656677] 
> [   20.656707] usb_stor_huawei_e220_init
> [   20.663513] usb-storage: probe of 1-1:1.3 failed with error -1
> [   20.670410] usb 1-1: New USB device found, idVendor=12d1,
> idProduct=1003
> [   20.677154] usb 1-1: New USB device strings: Mfr=2, Product=1,
> SerialNumber=0
> [   20.684387] usb 1-1: Product: HUAWEI Mobile
> [   20.688629] usb 1-1: Manufacturer: HUAWEI Technology
> [   21.827423] usbcore: registered new interface driver usbserial
> [   21.833374] USB Serial support registered for generic
> [   21.838867] usbcore: registered new interface driver
> usbserial_generic
> [   21.845489] usbserial: USB Serial Driver core
> [   22.216644] USB Serial support registered for GSM modem (1-port)
> [   22.222961] option 1-1:1.0: GSM modem (1-port) converter detected
> [   22.229675] usb 1-1: GSM modem (1-port) converter now attached to
> ttyUSB0
> [   22.236785] option 1-1:1.1: GSM modem (1-port) converter detected
> [   22.243347] usb 1-1: GSM modem (1-port) converter now attached to
> ttyUSB1
> [   22.250305] usbcore: registered new interface driver option
> [   22.255950] option: v0.7.2:USB Driver for GSM modems

Ok, this seems to point to issues binding drivers to devices at boot
time, but not after boot.  That's either udev or the kernel misbehaving,
not sure which.

Dan

> 
>         
>                 
>                 > Do you think that nm-modem-probe doesn't recognize
>                 the device I tried
>                 > the command from the udev rule after booting with
>                 the dongle plugged
>                 > before boot :
>                 > /lib/udev# nm-modem-probe --vid  0x12d1 --pid
>                  0x1003 --usb-interface
>                 > 00 01 --driver  option --delay 1000 --timeout 5000
>                 --export --verbose
>                 > --log /tmp/probe.log
>                 > L: (946685003.877166) main(): (01): usb-vid 0x12d1
>                  usb-pid 0x1003
>                 > usb-intf 0  driver 'option'
>                 > L: (946685003.877380) main(): waiting 1000 ms before
>                 probing
>                 > L: (946685004.877807) main(): probing 01
>                 > E: (946685009.983703) open(01) failed: 2
>                 
>                 
>                 This is probably related to the issue above with the
>                 kernel USB
>                 messages.  Basically, if you never see /dev/ttyUSB*
>                 then we either have
>                 driver problems of kernel USB stack issues.
>          
>         I don't think the problem is that deep it works when I plug it
>         after boot.
>          
>                 
>                 > Does that speak to you ? the error at opening means
>                 it doesn't see it
>                 > either ?
>                 > The more I try to understand things the more I get
>                 lost TT
>                 
>                 
>                 NM 0.8 works better here because it uses only udev for
>                 device detection,
>                 which means one fewer layer that can go wrong.
>         Ok ! Seems nice I'm going to try that but I hope it
>         dependences doesn't change to much from th 7.2
>          
>         
>                 
>                 Dan
>                 
>                 
>         Many thanks 
>         
>         
>