This messy page is for myself incase I need to reinstall everything again 🙂
HP Download page
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c0173883 Get the Gobi2000 firmware drivers from here
WWAN
Current qcserial and gobi_loader doesn’t work for Gobi2000 devices. Some of the QDL handshakes have changed. I’ve updated the code and it works…upload it later…
http://www.codon.org.uk/~mjg59/gobi_loader/
Add to qserial.c and rebuild kernel module
{USB_DEVICE(0x03f0, 0x241d)}, /* HP un2420 Gobi QDL Device */
{USB_DEVICE(0x03f0, 0x251d)}, /* HP un2420 Gobi Modem Device */
Add to /etc/udev/rules.d/60-gobi.rules
ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="241d", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"Keyboard Shortcuts
Menu->System->Preferences->Keyboard Shortcuts->Desktop->Launch Calculator->Disable (Backspace)
Sound
Add to /etc/modprobe.d/alsa-base.conf
options snd-hda-intel model=hp-dv5 enable_msi=1HACK TEMP AREA
Maintenance Videos from HP
Thank you so much for the correct audio sound configuration! 🙂
Uploaded the changed code anywhere?
I’m dualbooting with Windows 7 and can only see one device id for the Gobi ( 03f0:231d ). Any ideas on how to get Gobi to play nice with dualboot?
Seems I now, after modprobe hp-wmi also see it as 03f0:241d.
Still, even with gobi_loader, no luck.
What would it take to bribe you to write a step by step? You seem to be the only
Already added IDs to gcserial.c, make, make install, for gobi_loader make and make install as well, updated /etc/udev/rules.d/60-gobi.rules to have03f0:241d in it.
/lib/udev/gobi_loader /dev/ttyUSB0 /lib/firmware/gobi takes a while and does not complain, yet nothing works with network manager (does not even show tho mobile connection option) and even wvdial cannot see the modem.
oops: you seem to be the only person with actually the same laptop as I have, who has reported getting gobi working on the device.
Will post will post 😉 Was just lacking motivation and wanted to rewrite gobi_loader such that its more of a readable code than the ‘magic’ it is now 🙂
E-mailed you the current source I have that works.
For test purposes you could skip qcserial and modifying your udev.
sudo modprobe usbserial vendor=0x03f0 product=0x241d./gobi2kloader /dev/ttyUSB0 /lib/firmware/gobi/
Wait a bit…check with lsusb…then…
sudo modprobe usbserial vendor=0x03f0 product=0x251dMight need to restart modem-manager (just kill it)
Gobi_loader 0.3 will just hang by the way…
Oh just realised where you’re from…:) Huomenta!
Will gladly take some KarlFazer Nordic Gourmet Lingonberry Milk Parfait hehe
Oh, seems I also need a UQCN.mbn file in addition to the other two files… I wonder how to find the right one.
In your Windows 7 Install, in your Qualcomm driver directory (find it?) there should be a log file called QDLService2kHP.txt
In it you should find….
12/11/2009 06:42:25.592 [00460] QDL sending image file: C:\Program Files\Qualcomm\Images\HP\UMTS\AMSS.mbn
12/11/2009 06:42:26.472 [00460] Sending image file: C:\Program Files\Qualcomm\Images\HP\UMTS\Apps.mbn
12/11/2009 06:42:26.792 [00460] Sending image file: C:\Program Files\Qualcomm\Images\HP\0\UQCN.mbn
Or something similar, copy those 3 referenced files to /lib/firmware/gobi.
Hope that helps 🙂 (Quick reply?)
Nice pice of Hardware with nice performance and features.
But the only disadvantage is the single slot for RAM. A upgrade to 4gigs is very expensive.
I also have problems with audio and the gobi module.
I have solved the audio problem with the following entry in the alsa-base.conf file:
options snd-hda-intel model=hp-m4 enable_msi=1
I have tried allready other settings, but when sound was working the mic won’t and vice versa.
The gobi problem i haven’t solved yet. I have tried gobi_loader and the qcserial mod but i haven’t got a ttyUSB device.
Then i have read the post from “http://www.spinics.net/lists/linux-usb/msg25137.html” and was happy that this is no major problem.
What do you have changed to get this gobi-device working?
Hi Tom,
I’ve Emailed Lynoure the instructions and she has it working (kind of apparently) now. Give me a couple of days to leave Las Vegas and I’ll post up everything in a how-to 🙂
Check back in a couple of days!
Hi,
Thanks a lot for the tips. Do you have Ethernet working? I’ve installed 9.10, and default sky2 driver does not seem to work at all 🙁
Hi,
The sky2 driver is broken in karmic. But when you enable the “karmic-proposed” software-sources you get the newest already working sky2 driver.
Why do you say its broken?
[ 1.853102] sky2 driver version 1.23
[ 1.869059] sky2 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.869113] sky2 0000:03:00.0: setting latency timer to 64
[ 1.869206] sky2 0000:03:00.0: Yukon-2 Extreme chip revision 2
[ 1.869939] sky2 0000:03:00.0: irq 28 for MSI/MSI-X
[ 1.870998] sky2 eth0: addr 00:26:22:ab:ff:a5
[ 4.161445] sky2 eth3: enabling interface
Seems to be working for me… and I’ve used wired Ethernet…
I think the problem is only with the 64bit version.
Its Bug Nr.:407824 on Launchpad.net.
The solution is to add “pci=use_crs” to the kernel load command.
It seems to be a Problem on 64bit.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/407824
Hi,
I’m in the same predicament, I seem to have the newer style Gobi card which isn’t quite working with the process you’ve put together; will check back in a few days.
Thanks again, much appreciated.
Andrew
UK
🙂 Sorry for the delay… it is holidays and I’ll be flying back to Sydney soon… might post up the ‘hacky’ files in the interim…
Edit : Uploaded the modified qcserial.c and a gobi2kloader.c
Wordpress wouldn’t let me upload the udev rules file for some reason… probably won’t let me do the Makefile either… This is only for people who can’t wait anyway…
Thanks for the update, I’ve got a plug in dongle which I’m using for the time being, just would be nice to go dongle free.
I greatly appreciate your work with the code. I’m having problems with gobi2kloader after upgrading to kernel 2.6.32. You can operate the gobi2kloader with kernel 2.6.32?
I’m on 2.6.31 and have not tried with 2.6.32. Have you tried the code posted in http://www.madox.net/blog/2010/01/06/hp5310m-un2420-wireless-gobi2000-module-in-ubuntu/ , it isn’t quite so hacktastic 🙂
Hi,
I tried this code.
The code works perfectly for the kernel 2.6.31 but when I boot with the 2.6.32, gobi2kloader not work.
The code hangs after the first file is loaded. QDL protocol server response received (-1).
I suspect the problem is the usbcore.
Anyone experiencing freezes after unplugging the power cable? This happens for me both on karmic and lucid beta.
Strangely enough when I boot on battery then this is not reproduceable after you plug in and out the cable.
I get it from unplugging the network cable I think. Plus the wired network doesn’t seem to work unless it was plugged in during reboot.
Might be the power cable since I would tend to unplug both at the same time…Nope… Just tested 🙂
I think I just found the solution. Disabling powersave mode for LAN in bios seems to fix my issue. And ethernet driver seems to be loaded now all the times regardless of the presence of eth cable on boot.
Ooo thanks for that. Going to give it a try on next boot.
So far so good on my machine, after disabling power save on the LAN port I get consistent eth3 😉
thank you! you made my day, dude!
Hi,
Is anyone experiencing sporadic system pauses or freezes under Ubuntu? I have a situation where sporadically the system freezes, the keyboard will not respond and the active window greys out while this is going on the hard drive light is maxed out. The system usually recovers in about 5-10 seconds.
Also how are people finding general performance. I am finding program load times to be extremely slow on Karmic i.e. 15 seconds + for firefox.
I’d be interested to hear what others are experiencing.
Thanks,
James
On my HP mini 5102 the appropriate device seems to be 03f0:231d which i could not find in the customized qcserial.c
Bus 001 Device 003: ID 04f2:b159 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:231d Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
What I did was adding the device id to qcserial.c – after installing it I got a /dev/ttyUSB0
When I try to upload the firmware by gobiloader, it just shows:
QDL protocol server request sent
01 51 43 4f 4d 20 68 69 67 68 20 73 70 65 65 64
20 70 72 6f 74 6f 63 6f 6c 20 68 73 74 00 00 00
00 04 04 30 03 0b
…and stops. What can I try to do now?
Hmm…. after downloading I managed to run gobi_loader (sucessfully?).
dmesg outputs:
[ 19.889363] USB Serial support registered for Qualcomm USB modem
[ 19.906361] qcserial 2-2:1.2: Qualcomm USB modem converter detected
[ 19.906618] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
BUT… it does not show up in network-manager. What am I doing the wrong way?
Hm… back to start.
03f0:231d is the bluetooth device…
Under WIndows, device manager shows the Gobi WWAN/GPS device (after having it enabled manually in “HP Connection Manager”). Its address is 03f0:251d.
The problem is, lsusb under Ubuntu Karmic (9.10) does not even list a device with address 03f0:251d. What can I do now?
Please help!
Is there anybody who can help me to figure out why ‘lsusb’ is not showing an appropriate device?
I am just getting these:
Bus 001 Device 003: ID 04f2:b159 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:231d Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Hi Ronzo,
You should get a 03f0:241d with an uninitialized gobi, and 03f0:251d only after you load the firmware.
@madox: Thx for your answer. I do NOT see a device with ID 03f0:241d and I really do not have a clue why…
Under Windows 7, device manager lists the Gobi Device (251d) only when I “turn it on” with the HP Connection Mgr. Software… I guess that this is what has to be done as well under Linux. But how? Loading the hp-wmi kernel module did not help.
Do you have any ideas?
(I am using Ubuntu 10.04 with kernel 2.5.32)
I am running kernel 2.6.32-21, not 2.5.*…
Hi,
The Pb is the Kernel, in 2.6.32 or 2.6.33 the Gobi is not in lsusb … in 2.6.31 : it’s ok 🙂
But now the NetworkManager don’t connect to my provider … i don’ know why …
I had to add this 3 lines in /etc/modprobe.d/alsa.conf (Getoo user here) on my 5310m
options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1
adding only `options snd-hda-intel enable_msi=1` didn’t help 🙂
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
I forgot to say thanks to the autor of this fix here:
http://ubuntuforums.org/showthread.php?p=9481650#post9481650
Hi! I got th problem with gobi_loader 0.7 and kernel 2.6.35.22 on ubuntu 10.10. qcserial adds gobi to ttyUSB0 but when i run gobi loader no output i just hangs…Help….PLease…
Hi,
I’m not the maintainer of the gobi_loader, that’ll be Michael. I know there are some conditions where it will hang if the device is not ready for the firmware load. Have you tried with my [albeit a bit old] code?
I have the same problem as bobic257. gobi_loader just hangs. kernel 2.6.35-23 on ubuntu 10.10. i can activate the modem in windows and then reboot into ubuntu and then use it fine, but after suspend/resume or power cycling, the modem is again deactivated and i can’t get linux to activate it.
I tried gobi2kloader.c posted on this page, but it too hangs after “Starting Gobi2kLoader”.
What should I try next? I’m pretty sure I have the right firmware files, but could having the wrong ones possibly cause this behavior? If not, then what could?
THANKS
this appears to be my issue: “Kernel 2.6.35-17 breaks gobi_loader”
https://bugs.launchpad.net/ubuntu/+source/gobi-loader/+bug/621743