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