@J Boyan:
Please try a cold boot, then enter
lsusb | grep 05c6:9204
Getting a result means that your modem is still uninitialized, as you
know by now... Then do a
lsmod | grep qcserial
The number in the third column *should* be 0, but it's probably 1, which
means that some process opened /dev/ttyUSB0.
In case that the number is 0, running
sudo /lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi
should work. If it doesn't, please check the /lib/firmware/gobi
directory: Are the firmware files still the same as they were when you
copied them over? Still the same name (case is important!)? Any strange
permissions on the files or on the directory path to these files?
Perhaps you should check them with md5sum and compare with the firmware
files on the windows side?
On the other hand, if the module usage (number in the third column of
lsmod output) is not zero, we'll need to find the offending processes.
Enter
sudo fuser /dev/ttyUSB0
to get a list of process IDs that opened /dev/ttyUSB0.
ps -fp <PID>
will identify the processes. If it's only gobi_loader, kill it
pkill gobi_loader
and try the "sudo fuser" command again. I'd be willing to bet that
modem-manager will make its appearance... Please post your results here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/621743
Title:
Kernel 2.6.35-17 breaks gobi_loader
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
