LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   Haldaemon causing problems with my Huawei E220 USB HSDPA modem. (https://www.linuxquestions.org/questions/linux-general-1/haldaemon-causing-problems-with-my-huawei-e220-usb-hsdpa-modem-609949/)

redarrow 12-30-2007 07:57 AM

Haldaemon causing problems with my Huawei E220 USB HSDPA modem.
 
I have a Huawei E220 USB 3G/HSDPA modem..

It always worked relatively hassle free..

But recently when I updated from Fedora Core 7 to Fedora Core 8 a new problem was introduced:


If "haldaemon" is running when I plug it in then it will not initialize properly and I get loads of errors like this:
Code:

Dec 22 16:06:52 localhost kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Dec 22 16:06:52 localhost kernel: scsi 7:0:0:0: CD-ROM            HUAWEI  Mass Storage    2.31 PQ: 0 ANSI: 2
Dec 22 16:06:52 localhost kernel: sr2: scsi-1 drive
Dec 22 16:06:52 localhost kernel: sr 7:0:0:0: Attached scsi generic sg3 type 5
Dec 22 16:08:01 localhost kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Dec 22 16:08:16 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:08:31 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:08:31 localhost kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Dec 22 16:08:47 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:09:02 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:09:02 localhost kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Dec 22 16:09:12 localhost kernel: usb 3-2: device not accepting address 3, error -110
Dec 22 16:09:13 localhost kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Dec 22 16:09:23 localhost kernel: usb 3-2: device not accepting address 3, error -110
Dec 22 16:09:23 localhost kernel: sr 7:0:0:0: scsi: Device offlined - not ready after error recovery
Dec 22 16:09:23 localhost kernel: sr 7:0:0:0: rejecting I/O to offline device
Dec 22 16:09:23 localhost kernel: usb 3-2: USB disconnect, address 3
Dec 22 16:09:23 localhost kernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Dec 22 16:09:23 localhost kernel: option 3-2:1.0: device disconnected
Dec 22 16:09:23 localhost kernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Dec 22 16:09:23 localhost kernel: option 3-2:1.1: device disconnected
Dec 22 16:09:23 localhost kernel: scsi 7:0:0:0: rejecting I/O to dead device
Dec 22 16:09:23 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 4
Dec 22 16:09:38 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:09:53 localhost kernel: usb 3-2: device descriptor read/64, error -110
Dec 22 16:09:54 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 5
Dec 22 16:10:09 localhost kernel: usb 3-2: device descriptor read/64, error -110

If I stop haldaemon ("/etc/init.d/haldaemon stop") and only then plug it in, then it initializes correctly and I can successfully connect:
Code:

Dec 30 10:24:06 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2
Dec 30 10:24:06 localhost kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 30 10:24:06 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Dec 30 10:24:06 localhost kernel: usb 3-2: USB disconnect, address 2
Dec 30 10:24:07 localhost kernel: usbcore: registered new interface driver usbserial
Dec 30 10:24:07 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Dec 30 10:24:07 localhost kernel: usbcore: registered new interface driver usbserial_generic
Dec 30 10:24:07 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Dec 30 10:24:07 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
Dec 30 10:24:07 localhost kernel: usbcore: registered new interface driver option
Dec 30 10:24:07 localhost kernel: drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
Dec 30 10:24:07 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 3
Dec 30 10:24:07 localhost kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 30 10:24:07 localhost kernel: usb-storage: probe of 3-2:1.0 failed with error -5
Dec 30 10:24:07 localhost kernel: option 3-2:1.0: GSM modem (1-port) converter detected
Dec 30 10:24:07 localhost kernel: usb 3-2: GSM modem (1-port) converter now attached to ttyUSB0
Dec 30 10:24:07 localhost kernel: usb-storage: probe of 3-2:1.1 failed with error -5
Dec 30 10:24:07 localhost kernel: option 3-2:1.1: GSM modem (1-port) converter detected
Dec 30 10:24:07 localhost kernel: usb 3-2: GSM modem (1-port) converter now attached to ttyUSB1
Dec 30 10:24:07 localhost kernel: scsi5 : SCSI emulation for USB Mass Storage devices
Dec 30 10:24:12 localhost kernel: scsi 5:0:0:0: CD-ROM            HUAWEI  Mass Storage    2.31 PQ: 0 ANSI: 2
Dec 30 10:24:12 localhost kernel: sr2: scsi-1 drive
Dec 30 10:24:12 localhost kernel: sr 5:0:0:0: Attached scsi generic sg3 type 5
Dec 30 10:24:13 localhost kernel: PPP generic driver version 2.4.2
Dec 30 10:24:13 localhost pppd[2629]: pppd 2.4.4 started by root, uid 0
Dec 30 10:24:13 localhost pppd[2629]: Using interface ppp0
Dec 30 10:24:13 localhost pppd[2629]: Connect: ppp0 <--> /dev/ttyUSB0
Dec 30 10:24:13 localhost pppd[2629]: CHAP authentication succeeded
Dec 30 10:24:13 localhost pppd[2629]: CHAP authentication succeeded
Dec 30 10:24:13 localhost kernel: PPP Deflate Compression module registered
Dec 30 10:24:17 localhost pppd[2629]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 30 10:24:17 localhost pppd[2629]: local  IP address 172.28.10.175
Dec 30 10:24:17 localhost pppd[2629]: remote IP address 10.64.64.64

Anyone have any ideas whats going on?
I don't know if this is a kernel issue a haldaemon issue or perhaps a Fedora Core specific issue?

At the very least, is it possible to somehow specify that haldaemon should completely ignore this device when it's plugged in?

Leaving haldaemon permanently disabled does not seem like the correct solution..

(Kernel version is: 2.6.23.1)

Thanks.

Person_1873 01-05-2008 04:51 AM

well maybe you should just initiate hald again once you've connected, or better yet, write a shell app that you run when you want to plug it in which disables hald just long enough to connect then re-engages it, without hald, your applications will essentially start fighting eachother for resources

redarrow 01-05-2008 06:03 AM

Quote:

Originally Posted by Person_1873 (Post 3012128)
well maybe you should just initiate hald again once you've connected, or better yet, write a shell app that you run when you want to plug it in which disables hald just long enough to connect then re-engages it, without hald, your applications will essentially start fighting eachother for resources

Thanks for answering!

Unfortunately that doesn't work.. if I restart haldaemon after I've connected, it just "de-initialises" the modem and produces the same errors.. :(
It also makes no difference whether the modem was connected to the net or not - if it is connected to the net when I restart haldaemon, then the connection just dies.. :(

Person_1873 01-06-2008 08:45 AM

maybe if you install the old HALd from F7?

by the way, fedora have now dropped the "core" from their distrobution name, since F7, it went from FC6 to F7


All times are GMT -5. The time now is 04:15 PM.