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 > 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? > 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. > 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. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
