[opensuse] Cellular Modem (GOBI) w/openSUSE 12.2
I have a laptop with a Gobi 2000 wireless modem. The qcserial module is automatically loaded at boot but the device appears to be inoperative [no response to commands via minicom and /dev/ttyUSB0]. I'm told this device was working with a previous install, but it isn't working now [it was reinstalled]. Thoughts / suggestions? Bus 001 Device 004: ID 03f0:241d Hewlett-Packard Gobi 2000 Wireless Modem (QDL mode) - qcserial 12868 1 usb_wwan 20410 1 qcserial usbserial 47315 4 qcserial,usb_wwan - [ 15.345361] EDAC MC: Ver: 2.1.0 [ 15.346360] usbcore: registered new interface driver qcserial [ 15.346411] USB Serial support registered for Qualcomm USB modem [ 15.346446] qcserial 1-5:1.1: Qualcomm USB modem converter detected [ 15.346580] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2012-11-23 at 14:54 -0500, Adam Tauno Williams wrote:
I have a laptop with a Gobi 2000 wireless modem. The qcserial module is automatically loaded at boot but the device appears to be inoperative [no response to commands via minicom and /dev/ttyUSB0]. I'm told this device was working with a previous install, but it isn't working now [it was reinstalled]. Thoughts / suggestions?
Baffling. If I hook-up the SSD that was previously in this device and examine the log files I see - Sep 27 18:32:14 linux kernel: [ 3.303648] usbcore: registered new interface driver qcserial Sep 27 18:32:14 linux kernel: [ 3.303672] USB Serial support registered for Qualcomm USB modem Sep 27 18:32:14 linux kernel: [ 3.305245] qcserial 1-5:1.1: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.305360] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 Sep 27 18:32:14 linux kernel: [ 3.307537] qcserial 1-5:1.2: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.307810] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB1 Sep 27 18:32:14 linux kernel: [ 3.309392] qcserial 1-5:1.3: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.309549] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB2 But it doesn't seem to have any GOBI stuff or special firmware installed; but the device looks like it was operational. And I see mentions of - Sep 27 14:41:55 linux ifdown[5093]: wwan0 name: HP un2420 Mobile Broadband Module - which is a device I don't see at all following the reinstall.
Bus 001 Device 004: ID 03f0:241d Hewlett-Packard Gobi 2000 Wireless Modem (QDL mode) - qcserial 12868 1 usb_wwan 20410 1 qcserial usbserial 47315 4 qcserial,usb_wwan - [ 15.345361] EDAC MC: Ver: 2.1.0 [ 15.346360] usbcore: registered new interface driver qcserial [ 15.346411] USB Serial support registered for Qualcomm USB modem [ 15.346446] qcserial 1-5:1.1: Qualcomm USB modem converter detected [ 15.346580] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Freitag, 23. November 2012, 14:54:30 schrieb Adam Tauno Williams:
I have a laptop with a Gobi 2000 wireless modem. The qcserial module is automatically loaded at boot but the device appears to be inoperative [no response to commands via minicom and /dev/ttyUSB0].
http://www.thinkwiki.org/wiki/Installing_OpenSUSE_12.2_on_a_ThinkPad_T410s Replace 12.2 by the oS version you use (goes back to 11.4). While your USB ids do not match, you should get the point: You need the gobi_loader package and the appropriate firmware copied to /lib/firmware/gobi/. Please see http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000 for details.
[...] Bus 001 Device 004: ID 03f0:241d Hewlett-Packard Gobi 2000 Wireless Modem (QDL mode)
The USB id indicates that there was no firmware loaded.
[...]
In your other mail you said that if you install the old SSD and, thus, the old OS, it will work. Which OS is the old OS? Linux? Windows? BTW, pleas note that the firmware survives a simple (warm) reboot. Thus, it sometimes looks like it works but a previous start of Windows loaded the firmware and not your current Linux. However, when installing the old SSD, you surely did a cold boot. Gruß Jan -- Everyone hates me because I'm paranoid. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2012-11-24 at 12:50 +0100, Jan Ritzerfeld wrote:
I have a laptop with a Gobi 2000 wireless modem. The qcserial module is automatically loaded at boot but the device appears to be inoperative [no response to commands via minicom and /dev/ttyUSB0]. http://www.thinkwiki.org/wiki/Installing_OpenSUSE_12.2_on_a_ThinkPad_T410s Replace 12.2 by the oS version you use (goes back to 11.4). While your USB ids do not match, you should get the point: You need the gobi_loader package and the appropriate firmware copied to /lib/firmware/gobi/. Please see http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000 for details. [...] Bus 001 Device 004: ID 03f0:241d Hewlett-Packard Gobi 2000 Wireless Modem (QDL mode) The USB id indicates that there was no firmware loaded. [...] In your other mail you said that if you install the old SSD and, thus, the
Am Freitag, 23. November 2012, 14:54:30 schrieb Adam Tauno Williams: old OS, it will work. Which OS is the old OS? Linux? Windows?
The SSD is an openSUSE 12.2 x86_64 installation. I mounted it on another workstation an I can't find any trace of gobi_loader of firmware on that drive. But it does initialize the device to three USB tty ports (I see that in the recorded /var/log/messages from that drive).
BTW, pleas note that the firmware survives a simple (warm) reboot. Thus, it sometimes looks like it works but a previous start of Windows loaded the firmware and not your current Linux. However, when installing the old SSD, you surely did a cold boot.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 24. November 2012, 08:58:42 schrieb Adam Tauno Williams:
On Sat, 2012-11-24 at 12:50 +0100, Jan Ritzerfeld wrote: [...]
In your other mail you said that if you install the old SSD and, thus, the old OS, it will work. Which OS is the old OS? Linux? Windows?
The SSD is an openSUSE 12.2 x86_64 installation. I mounted it on another workstation an I can't find any trace of gobi_loader of firmware on that drive. But it does initialize the device to three USB tty ports (I see that in the recorded /var/log/messages from that drive).
There must be the firmware and the gobi_loader. Where did you search? E.g. as root: find / -iname "*.mbn" and find / -iname "*gobi*" Gruß Jan -- Everything is worth what it's purchaser will pay for it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2012-11-24 at 17:42 +0100, Jan Ritzerfeld wrote:
Am Samstag, 24. November 2012, 08:58:42 schrieb Adam Tauno Williams:
On Sat, 2012-11-24 at 12:50 +0100, Jan Ritzerfeld wrote: [...]
In your other mail you said that if you install the old SSD and, thus, the old OS, it will work. Which OS is the old OS? Linux? Windows? The SSD is an openSUSE 12.2 x86_64 installation. I mounted it on another workstation an I can't find any trace of gobi_loader of firmware on that drive. But it does initialize the device to three USB tty ports (I see that in the recorded /var/log/messages from that drive). There must be the firmware and the gobi_loader.
I thought so to, but I can't find any evidence of it. BUT it is a x86_32 installation, rather than an x86_64. When I talked to the previous user he said that when he had it installed as x86_64 it did not work - but when he reinstalled as an x86_32 it worked right away.
Where did you search? E.g. as root: find / -iname "*.mbn" and find / -iname "*gobi*"
[Mounted the root volume of the old SSD on a workstation's /mnt] cebolla:/mnt # find . -name *.mbn cebolla:/mnt # find . -name *gobi* ./usr/lib64/ModemManager/libmm-plugin-gobi.so cebolla:/mnt # chroot /mnt cebolla:/> rpm -qf ./usr/lib64/ModemManager/libmm-plugin-gobi.so ModemManager-0.5.2.0-2.4.1.x86_64 ./usr/lib64/ModemManager/libmm-plugin-gobi.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xe5e753d39eef70f71f698aeb3d602b13926f6fe2, stripped Odd, that looks like a 64 bit package. But the user said it was 32 bit. In var/log/messages Sep 27 18:32:14 linux kernel: [ 3.303648] usbcore: registered new interface driver qcserial Sep 27 18:32:14 linux kernel: [ 3.303672] USB Serial support registered for Qualcomm USB modem Sep 27 18:32:14 linux kernel: [ 3.305245] qcserial 1-5:1.1: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.305360] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 Sep 27 18:32:14 linux kernel: [ 3.307537] qcserial 1-5:1.2: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.307810] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB1 Sep 27 18:32:14 linux kernel: [ 3.309392] qcserial 1-5:1.3: Qualcomm USB modem converter detected Sep 27 18:32:14 linux kernel: [ 3.309549] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2012-11-26 at 13:31 -0500, Adam Tauno Williams wrote:
On Sat, 2012-11-24 at 17:42 +0100, Jan Ritzerfeld wrote:
Am Samstag, 24. November 2012, 08:58:42 schrieb Adam Tauno Williams:
On Sat, 2012-11-24 at 12:50 +0100, Jan Ritzerfeld wrote: [...]
In your other mail you said that if you install the old SSD and, thus, the old OS, it will work. Which OS is the old OS? Linux? Windows? The SSD is an openSUSE 12.2 x86_64 installation. I mounted it on another workstation an I can't find any trace of gobi_loader of firmware on that drive. But it does initialize the device to three USB tty ports (I see that in the recorded /var/log/messages from that drive). There must be the firmware and the gobi_loader. I thought so to, but I can't find any evidence of it. BUT it is a x86_32 installation, rather than an x86_64. When I talked to the previous user he said that when he had it installed as x86_64 it did not work - but when he reinstalled as an x86_32 it worked right away.
Of course, re-installed as 32-bit and that did *not* fix it; didn't really expect it to. Clearly something magickal happened before. Now trying to dig the firmware files out of the Windows setup package... I found the .mbn files, and their checksums match those provided @ <http://opensuseadventures.blogspot.com/2011/11/gobi-loader-and-mobile-broadband.html> $ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ... pc02813:/lib/firmware/gobi # ls -l total 9672 -rw-r--r-- 1 root root 6733876 Nov 29 10:39 amss.mbn -rw-r--r-- 1 root root 3141676 Nov 29 10:39 apps.mbn -rw-r--r-- 1 root root 17260 Nov 29 10:39 UQCN.mbn Rebooted. Still no joy. Nov 29 10:56:17 pc02813 dbus-daemon[634]: modem-manager[678]: <info> (ttyUSB0) closing serial port... Nov 29 10:56:17 pc02813 modem-manager[678]: <info> (ttyUSB0) closing serial port... Nov 29 10:56:17 pc02813 modem-manager[678]: <info> (ttyUSB0) serial port closed Nov 29 10:56:17 pc02813 dbus-daemon[634]: modem-manager[678]: <info> (ttyUSB0) serial port closed Nov 29 10:56:23 pc02813 udevd[388]: timeout: killing 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] Nov 29 10:56:23 pc02813 udevd[388]: 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] terminated by signal 9 (Killed) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 11:10 -0500, Adam Tauno Williams wrote:
On Sat, 2012-11-24 at 17:42 +0100, Jan Ritzerfeld wrote:
Am Samstag, 24. November 2012, 08:58:42 schrieb Adam Tauno Williams:
On Sat, 2012-11-24 at 12:50 +0100, Jan Ritzerfeld wrote: [...]
In your other mail you said that if you install the old SSD and, thus, the old OS, it will work. Which OS is the old OS? Linux? Windows? The SSD is an openSUSE 12.2 x86_64 installation. I mounted it on another workstation an I can't find any trace of gobi_loader of firmware on that drive. But it does initialize the device to three USB tty ports (I see that in the recorded /var/log/messages from that drive). There must be the firmware and the gobi_loader. I thought so to, but I can't find any evidence of it. BUT it is a x86_32 installation, rather than an x86_64. When I talked to the previous user he said that when he had it installed as x86_64 it did not work - but when he reinstalled as an x86_32 it worked right away. I found the .mbn files, and their checksums match those provided @ <http://opensuseadventures.blogspot.com/2011/11/gobi-loader-and-mobile-broadband.html> $ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ...
On Mon, 2012-11-26 at 13:31 -0500, Adam Tauno Williams wrote: pc02813:/lib/firmware/gobi # ls -l total 9672 -rw-r--r-- 1 root root 6733876 Nov 29 10:39 amss.mbn -rw-r--r-- 1 root root 3141676 Nov 29 10:39 apps.mbn -rw-r--r-- 1 root root 17260 Nov 29 10:39 UQCN.mbn Rebooted. Still no joy. Nov 29 10:56:17 pc02813 dbus-daemon[634]: modem-manager[678]: <info> (ttyUSB0) closing serial port... Nov 29 10:56:17 pc02813 modem-manager[678]: <info> (ttyUSB0) closing serial port... Nov 29 10:56:17 pc02813 modem-manager[678]: <info> (ttyUSB0) serial port closed Nov 29 10:56:17 pc02813 dbus-daemon[634]: modem-manager[678]: <info> (ttyUSB0) serial port closed Nov 29 10:56:23 pc02813 udevd[388]: timeout: killing 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] Nov 29 10:56:23 pc02813 udevd[388]: 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] terminated by signal 9 (Killed)
Running the gobi_loader manually [as root] just seems to hang.. $ /lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi Stracing that it looks like the ttyUSB device is unresponsive to the write operation: open("/dev/ttyUSB0", O_RDWR) = 3 chdir("/lib/firmware/gobi") = 0 open("amss.mbn", O_RDONLY) = 4 fstat64(4, {st_mode=S_IFREG|0644, st_size=6733876, ...}) = 0 ioctl(3, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0 ioctl(3, SNDCTL_TMR_START or SNDRV_TIMER_IOCTL_TREAD or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0 write(3, "~", 1) = 1 write(3, "\1QCOM high speed protocol hst\0\0\0"..., 38) = 38 write(3, "~", 1) = 1 write(3, "~", 1) = 1 write(3, "%\5,\300f\0\1\0\0\0\4\0\0xS", 15 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 29. November 2012, 11:10:33 schrieb Adam Tauno Williams:
[...] Of course, re-installed as 32-bit and that did *not* fix it; didn't really expect it to. Clearly something magickal happened before. [...]
Been there...
$ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ...
BTW: Do you have an CDMA2000 or EV-DO provider? E.g., in the US? If not, and you have a UMTS provider, please try the generic firmware files that are located in the directories "6" and "UMTS".
[...] Nov 29 10:56:23 pc02813 udevd[388]: timeout: killing 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] Nov 29 10:56:23 pc02813 udevd[388]: 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] terminated by signal 9 (Killed)
Well, while this is not ok, at least you see that the gobi_loader udev rules match your WWAN modem and it finds your firmware. And that is good news! Maybe the NetworkManager/ModemManager plugins are trying to access the modem while gobi_loader tries to upload the firmware? Could you try stopping them first: # systemctl stop NetworkManager.service Gruß Jan -- There are two reasons for doing things, a very good reason and the real reason. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 19:30 +0100, Jan Ritzerfeld wrote:
Am Donnerstag, 29. November 2012, 11:10:33 schrieb Adam Tauno Williams:
[...] Of course, re-installed as 32-bit and that did *not* fix it; didn't really expect it to. Clearly something magickal happened before. [...] Been there... $ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ... BTW: Do you have an CDMA2000 or EV-DO provider?
Hmmm, not sure. Verizon, USA.
E.g., in the US? If not, and you have a UMTS provider, please try the generic firmware files that are located in the directories "6" and "UMTS".
Will do.
[...] Nov 29 10:56:23 pc02813 udevd[388]: timeout: killing 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] Nov 29 10:56:23 pc02813 udevd[388]: 'gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi' [523] terminated by signal 9 (Killed) Well, while this is not ok, at least you see that the gobi_loader udev rules match your WWAN modem and it finds your firmware. And that is good news!
Yep, pc02813:/etc/udev/rules.d # grep 241d 60-gobi.rules ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="241d", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
Maybe the NetworkManager/ModemManager plugins are trying to access the modem while gobi_loader tries to upload the firmware? Could you try stopping them first: # systemctl stop NetworkManager.service
Ok, I'll try that. I find mention on Ubuntu forums about blacklisting the device from ModemManager; not sure if that is equivalent to openSUSE. Does gobi_loader typically log anything to the system log? How do I know if it even tried to load the firmware? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 13:39 -0500, Adam Tauno Williams wrote:
On Thu, 2012-11-29 at 19:30 +0100, Jan Ritzerfeld wrote:
Am Donnerstag, 29. November 2012, 11:10:33 schrieb Adam Tauno Williams:
[...] Of course, re-installed as 32-bit and that did *not* fix it; didn't really expect it to. Clearly something magickal happened before. [...] Been there... $ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ... BTW: Do you have an CDMA2000 or EV-DO provider? Hmmm, not sure. Verizon, USA. E.g., in the US? If not, and you have a UMTS provider, please try the generic firmware files that are located in the directories "6" and "UMTS". Will do.
SHAZAM!!!! NetworkManager now has a broadband option. /lib/firmware/gobi # ls -l total 14236 -rw-r--r-- 1 root root 11333684 Nov 29 13:40 amss.mbn -rw-r--r-- 1 root root 3223596 Nov 29 13:40 apps.mbn -rw-r--r-- 1 root root 10748 Nov 29 13:40 UQCN.mbn pc02813:/lib/firmware/gobi # md5sum * 80fcfbb41a7d4331d4b7145972f5f3c4 amss.mbn 00cbd411048cdadc3e4caf0d89d14fca apps.mbn bdf27325ebb63251c1310cd3a8f7bab6 UQCN.mbn kernel: usb 1-5: New USB device found, idVendor=03f0, idProduct=251d kernel: usb 1-5: New USB device strings: Mfr=3, Product=2, SerialNumber=0 kernel: usb 1-5: Product: HP un2420 Mobile Broadband Module kernel: usb 1-5: Manufacturer: Qualcomm Incorporated kernel: qcserial 1-5:1.1: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 kernel: qcserial 1-5:1.2: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB1 kernel: qcserial 1-5:1.3: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB2 <me-does-a-little-dance/> NetworkManager-0.9.4.0-5.13.1.i586 ModemManager-0.5.2.0-2.4.1.i586 3.4.11-2.16-desktop #1 SMP PREEMPT i686 ***BUT*** I now cannot connect to the wireless network. The only "plan name" described in the configuration dialog is "4G LTE..." and this is a 3G card. It doesn't connect. :( On the next issue.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 14:00 -0500, Adam Tauno Williams wrote:
On Thu, 2012-11-29 at 13:39 -0500, Adam Tauno Williams wrote:
On Thu, 2012-11-29 at 19:30 +0100, Jan Ritzerfeld wrote:
Am Donnerstag, 29. November 2012, 11:10:33 schrieb Adam Tauno Williams:
[...] Of course, re-installed as 32-bit and that did *not* fix it; didn't really expect it to. Clearly something magickal happened before. [...] Been there... $ find . -name *.mbn ... e4d8d4dbd0a10d17f01f7f3bbd2ea734 ./1/UQCN.mbn 06f76ed398458dad7b91c2d99a85a0a7 ./1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./1/apps.mbn ... BTW: Do you have an CDMA2000 or EV-DO provider? Hmmm, not sure. Verizon, USA. E.g., in the US? If not, and you have a UMTS provider, please try the generic firmware files that are located in the directories "6" and "UMTS". Will do.
SHAZAM!!!! NetworkManager now has a broadband option.
/lib/firmware/gobi # ls -l total 14236 -rw-r--r-- 1 root root 11333684 Nov 29 13:40 amss.mbn -rw-r--r-- 1 root root 3223596 Nov 29 13:40 apps.mbn -rw-r--r-- 1 root root 10748 Nov 29 13:40 UQCN.mbn pc02813:/lib/firmware/gobi # md5sum * 80fcfbb41a7d4331d4b7145972f5f3c4 amss.mbn 00cbd411048cdadc3e4caf0d89d14fca apps.mbn bdf27325ebb63251c1310cd3a8f7bab6 UQCN.mbn
kernel: usb 1-5: New USB device found, idVendor=03f0, idProduct=251d kernel: usb 1-5: New USB device strings: Mfr=3, Product=2, SerialNumber=0 kernel: usb 1-5: Product: HP un2420 Mobile Broadband Module kernel: usb 1-5: Manufacturer: Qualcomm Incorporated kernel: qcserial 1-5:1.1: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 kernel: qcserial 1-5:1.2: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB1 kernel: qcserial 1-5:1.3: Qualcomm USB modem converter detected kernel: usb 1-5: Qualcomm USB modem converter now attached to ttyUSB2
<me-does-a-little-dance/>
NetworkManager-0.9.4.0-5.13.1.i586 ModemManager-0.5.2.0-2.4.1.i586 3.4.11-2.16-desktop #1 SMP PREEMPT i686
***BUT*** I now cannot connect to the wireless network. The only "plan name" described in the configuration dialog is "4G LTE..." and this is a 3G card. It doesn't connect. :( On the next issue....
A cold start got the device up and running with the Verizon /1 firmware. But NetworkManager only wants to create a "4G LTE Contract", or a custom contract. Neither connect. In the past I believe I have used just a dial string of #777 and an APN name of "vzwinternet", but it isn't working. I have one connection on number "*99#" which is what it wants by default. Also have a profile #777. Both have an APN of "vzwinternet" and a Type of "any". I can only edit this using the old nm-connection-editor as Network Settings has the Option button from "Mobile broadband" grayed out. But NetworkManager does see the "Qualcomm HP un2420 Mobile Broadband" device. -- Adam Tauno Williams GPG D95ED383 openSUSE, a LINUX desktop for humans who need to get work done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 16:32 -0500, Adam Tauno Williams wrote:
NetworkManager-0.9.4.0-5.13.1.i586 ModemManager-0.5.2.0-2.4.1.i586 3.4.11-2.16-desktop #1 SMP PREEMPT i686 ***BUT*** I now cannot connect to the wireless network. The only "plan name" described in the configuration dialog is "4G LTE..." and this is a 3G card. It doesn't connect. :( On the next issue.... A cold start got the device up and running with the Verizon /1 firmware. But NetworkManager only wants to create a "4G LTE Contract", or a custom contract. Neither connect. In the past I believe I have used just a dial string of #777 and an APN name of "vzwinternet", but it isn't working. I have one connection on number "*99#" which is what it wants by default. Also have a profile #777. Both have an APN of "vzwinternet" and a Type of "any". I can only edit this using the old nm-connection-editor as Network Settings has the Option button from "Mobile broadband" grayed out. But NetworkManager does see the "Qualcomm HP un2420 Mobile Broadband" device.
Hmmm. Captured a modem-manager log file. That doesn't look healthy. Log @ <http://wmmi.net/documents/20a565b3da424b8db8c8436a90c104bf.mmlog.txt> -- Adam Tauno Williams GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-11-29 at 16:56 -0500, Adam Tauno Williams wrote:
On Thu, 2012-11-29 at 16:32 -0500, Adam Tauno Williams wrote:
NetworkManager-0.9.4.0-5.13.1.i586 ModemManager-0.5.2.0-2.4.1.i586 3.4.11-2.16-desktop #1 SMP PREEMPT i686 ***BUT*** I now cannot connect to the wireless network. The only "plan name" described in the configuration dialog is "4G LTE..." and this is a 3G card. It doesn't connect. :( On the next issue.... A cold start got the device up and running with the Verizon /1 firmware. But NetworkManager only wants to create a "4G LTE Contract", or a custom contract. Neither connect. In the past I believe I have used just a dial string of #777 and an APN name of "vzwinternet", but it isn't working. I have one connection on number "*99#" which is what it wants by default. Also have a profile #777. Both have an APN of "vzwinternet" and a Type of "any". I can only edit this using the old nm-connection-editor as Network Settings has the Option button from "Mobile broadband" grayed out. But NetworkManager does see the "Qualcomm HP un2420 Mobile Broadband" device. Hmmm. Captured a modem-manager log file. That doesn't look healthy. Log @ <http://wmmi.net/documents/20a565b3da424b8db8c8436a90c104bf.mmlog.txt>
Sadly the only firmware combinations I can seem to get to work only talk about a "4G LTE Connection", which [of course] doesn't work. It does seem that the device retains its firmware unless *POWER IS LOST* - as in disconnect the power cord AND the battery. So that might explain why it worked before. It must have still had the firmware from the initial Windows installation; and we've now no way of identifying which/what firmware that was. The HP Qualcomm driver package doesn't seem to contain a UQCN.mbn file - only lots of amss.mbn & apps.mbn files. So I was stuck with the Lenovo firmware images, the incomplete HP firmware images, or a mix-n-match of both. I have to give up at this point. Anyone interested in the gory details can also see the thread over on the NetworkManager list @ <https://mail.gnome.org/archives/networkmanager-list/2012-November/msg00204.html> -- Adam Tauno Williams GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Freitag, 30. November 2012, 10:45:13 schrieb Adam Tauno Williams:
[...] It does seem that the device retains its firmware unless *POWER IS LOST* - as in disconnect the power cord AND the battery.
Interesting!
So that might explain why it worked before. It must have still had the firmware from the initial Windows installation; and we've now no way of identifying which/what firmware that was.
Too bad. However, as I wrote in the thinkwiki article, I used a VirtualBox Windows 7 installation with USB enabled to fully install the WWAN driver there. Maybe you could then identify the correct firmware.
I have to give up at this point. [...]
Sorry for that. What do you think about filing a bug report? Gruß Jan -- Give your child mental blocks for Christmas. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Adam Tauno Williams -
Jan Ritzerfeld