[Bug 408536] New: umtsmon cannot open hs2300 umts modem in HP compaq 8510p
https://bugzilla.novell.com/show_bug.cgi?id=408536 Summary: umtsmon cannot open hs2300 umts modem in HP compaq 8510p Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: zoz@novell.com ReportedBy: bernhard.bender@web.de QAContact: qa@suse.de Found By: --- umtsmon fails to open the USB serial ports associated to the WWAN modem in a HP Compaq 8510p notebook. The modem works fine with the hp WWAN manager in Windows XP. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c1
--- Comment #1 from Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c2
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c3
--- Comment #3 from Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c4
--- Comment #4 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c5
--- Comment #5 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c6
--- Comment #6 from Bernhard Bender
So it would be great, if you could get the ATI from both ports (for me it just works to do "screen /dev/ttyUSB0" as root, then i can type directly to the port).
None of the port /dev/ttyUSB[012] shows any response to AT command using the screen command.
Alternatively, please try both combinations:
- umtsmon -s /dev/ttyUSB0,/dev/ttyUSB2 - umtsmon -s /dev/ttyUSB2,/dev/ttyUSB0
i hope that one of those combinations works.
Both fail the same way as reported in comment #1. Note that umtsmon does not say it cannot get an answer to an AT command. To me it seems the program cannot even send data to the device
Could not write to serial device: Resource temporarily unavailable ##P1 t=477: *** CRITICAL ERROR: Could not write to device (anymore)
I used strace to see what happens. Here is an excerpt:
open("/dev/ttyUSB2", O_RDWR|O_EXCL|O_NOCTTY|O_NONBLOCK) = 9 fstat64(9, {st_mode=S_IFCHR|0660, st_rdev=makedev(188, 2), ...}) = 0 ioctl(9, SNDCTL_TMR_TEMPO or TCGETA, {B9600 -opost isig -icanon -echo ...}) = 0 ioctl(9, SNDCTL_TMR_SOURCE or TCSETA, {B115200 -opost isig -icanon -echo ...}) = 0 select(1, NULL, NULL, NULL, {0, 200000}) = 0 (Timeout) select(10, [9], NULL, NULL, {0, 20000}) = 0 (Timeout) write(9, "\r", 1) = -1 EAGAIN (Resource temporarily unavailable) [...repeats many times...] select(1, NULL, NULL, NULL, {0, 10000}) = 0 (Timeout) close(9) = 0 dup(2) = 9 fcntl64(9, F_GETFL) = 0x2 (flags O_RDWR) fstat64(9, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 2), ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb713c000 _llseek(9, 0, 0xbfffca78, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(9, "Could not write to serial device"..., 67Could not write to serial device: Resource temporarily unavailable ) = 67 close(9) = 0 <<<
So it seems that write()ing to file id 9 (/dev/ttyUSB2) always return EAGAIN... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c7
--- Comment #7 from Bernhard Bender
Just to make sure: please check with lsmod that the "sierra" module is loaded. Unload it (with "rmmod sierra"), clear the dmesg buffer ("dmesg -c"), load the module again ("modprobe sierra"), then post the output of "dmesg". (all commands must be run as root).
sierra module is loaded: # lsmod | grep sierra sierra 30472 3 usbserial 51120 8 sierra usbcore 164812 8 btusb,usbhid,hci_usb,sierra,usbserial,uhci_hcd,ehci_hcd loading module sierra: # modprobe sierra # dmesg drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem sierra 4-1:1.0: Sierra USB modem converter detected usb 4-1: Sierra USB modem converter now attached to ttyUSB0 usb 4-1: Sierra USB modem converter now attached to ttyUSB1 usb 4-1: Sierra USB modem converter now attached to ttyUSB2 usbcore: registered new interface driver sierra drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.2.9c BTW, in WinXP the modem has a total of four serial ports. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c8
--- Comment #8 from Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c9
Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c10
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c11
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c12
--- Comment #12 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c13
Bernhard Bender
What are the two different cards here? Can someone give me a simple 'lsusb' output for both of them?
This is the lsusb -l output for the hs2300 card on my hp 8510p: lsusb -v -s 4:2 Bus 004 Device 002: ID 03f0:1e1d Hewlett-Packard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x03f0 Hewlett-Packard idProduct 0x1e1d bcdDevice 0.02 iManufacturer 1 HP iProduct 2 HP hs2300 HSDPA Broadband Wireless Module iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 7 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 3 Data Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 128 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0000 (Bus Powered) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c14
--- Comment #14 from Bernhard Bender
Bernhard, I managed to package the latest sierra.c driver as a KMP (kernel module package) in the openSUSE build service.
Please go to http://software.opensuse.org/search and search for "sierra" and openSUSE 11.0. You will find download links for the packages. Choose the one matching your kernel (probably the "-default" or the "-pae" i586 version) and install it.
Then run "rmmod sierra", "modprobe sierra" The last line in /var/log/messages should show something like
USB Driver for Sierra Wireless USB modems: v1.2.10b
This worked fine, using the -pae i586 version.
Maybe the new driver works better with your card.
Nope. Still no response using screen on /dev/ttyUSB0 But my system locks up really hard when I try to quit screen. Also locks up hard trying to run umtsmon May be due to different kernel version 2.6.25.11-0.1-pae ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c15
--- Comment #15 from Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c16
--- Comment #16 from Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c17
--- Comment #17 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c18
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c19
--- Comment #19 from Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=408536
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c20
--- Comment #20 from Danny Kukawka
Either way, updating the sierra.c driver is not going to help out here.
The kernel is a "dumb" pass through. Some modems have the ports backwards / different then others, that's not a kernel problem/issue to deal with, it's userspace, unfortunately.
I don't think so. 1) UMTSmon already detect twisted ports, there is no problem. 2) the problem is that the device don't even answer to the AT command (see comment #6) in this case. This don't look like a userspace problem to me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c21
--- Comment #21 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c22
Greg Kroah-Hartman
(In reply to comment #19 from Greg Kroah-Hartman)
Either way, updating the sierra.c driver is not going to help out here.
The kernel is a "dumb" pass through. Some modems have the ports backwards / different then others, that's not a kernel problem/issue to deal with, it's userspace, unfortunately.
I don't think so. 1) UMTSmon already detect twisted ports, there is no problem. 2) the problem is that the device don't even answer to the AT command (see comment #6) in this case. This don't look like a userspace problem to me.
Hm, remember the part about "dumb pass through"? :) The kernel doesn't do anything here, perhaps this is just a device that does not work properly without some "magic" command that we don't know about. The kernel doesn't know anything about AT commands, if the device isn't responding, it's the device's problem. Can someone provide the output of 'lsusb' for the device that does not work properly? I see 2 entries for the device that works, but none for the "broken" device. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c23
Bernhard Bender
Hm, remember the part about "dumb pass through"? :)
The kernel doesn't do anything here, perhaps this is just a device that does not work properly without some "magic" command that we don't know about.
The kernel doesn't know anything about AT commands, if the device isn't responding, it's the device's problem.
Can someone provide the output of 'lsusb' for the device that does not work properly? I see 2 entries for the device that works, but none for the "broken" device.
comment 13 has the lsusb listing for the device that does NOT work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c24
--- Comment #24 from Danny Kukawka
Can someone provide the output of 'lsusb' for the device that does not work properly? I see 2 entries for the device that works, but none for the "broken" device.
Comment #13: lsusb from the not working device Comment #21: lsusb from a working hs2300 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c25
--- Comment #25 from Bernhard Bender
(In reply to comment #22 from Greg Kroah-Hartman)
Can someone provide the output of 'lsusb' for the device that does not work properly? I see 2 entries for the device that works, but none for the "broken" device.
Comment #13: lsusb from the not working device Comment #21: lsusb from a working hs2300
As you can see, these listing do not differ, except for the bus location Also from comments 2 and 3 it seems that there is the same firmware on the devices. Needless to add that the device on my hp 8510p works fine in windoze. Stefan, how to you activate you device? Maybe there is a difference there, when switching between WinXP and Suse 11.0, which I do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c26
--- Comment #26 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
Robert Vojcik
https://bugzilla.novell.com/show_bug.cgi?id=408536
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c27
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c28
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c29
Bernhard Bender
https://bugzilla.novell.com/show_bug.cgi?id=408536
User seife@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c30
--- Comment #30 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=408536
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c31
--- Comment #31 from Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=408536
User bernhard.bender@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408536#c32
--- Comment #32 from Bernhard Bender
@Bernhard: the following link could be interesting for you: http://dkukawka.blogspot.com/2008/08/how-to-activate-your-hp-umts-card.html
Yes indeed, most useful hint. I installed the hp-wmi-kmp-pae module and it works just fine. I noticed this: after loading the module, it said: # grep . /sys/class/rfkill/*/state /sys/class/rfkill/rfkill0/state:1 /sys/class/rfkill/rfkill1/state:1 /sys/class/rfkill/rfkill2/state:1 but the WWAN device was still not responding. so it seems the module does not correctly read the current state of the kill switch on startup. After setting the WWAN killswitch to 0 and back to 1 the device is enabled and umtsmon works properly. I'll try and put this into the system startup... Thank you! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com