@Alex: I'm also running Lucid and Gobi works fine here (at least most
of the time but that might be related to my ThinkPad W510). I didn't
install any backports packages, though, but patched the kernel by hand
as described in one of messages at the very beginning of this bug
discussion. (Also 2.6.35-020635rc4-generic is my kernel version in
case you need it but any newer version should do, too.)

On Wed, Mar 2, 2011 at 17:32, Alex Denvir <email address hidden> wrote:
> Done some testing with both lucid and maverick on a Dell Latitude E5410
> here -
>
> With maverick, installing gobi-loader, dropping the firmware into
> /lig/firmware/gobi and rebooting works first time, nice and easy.
>
> With lucid, I had absolutely no success at all. Installed gobi-loader,
> backports etc. and network-manager would never show any options under
> mobile broadband.
>
> Ideally I'd like to get this working on lucid as I have about 4 of these
> laptops in the company, and would preferably like to stick to the LTS,
> but I guess I can cope with shifting to maverick for this.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/554099
>
> Title:
>  Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken
>
> Status in The Linux Kernel:
>  Fix Released
> Status in “gobi-loader” package in Ubuntu:
>  Fix Released
> Status in “linux” package in Ubuntu:
>  Fix Released
> Status in “linux-backports-modules-2.6.32” package in Ubuntu:
>  Invalid
> Status in “gobi-loader” source package in Lucid:
>  Invalid
> Status in “linux” source package in Lucid:
>  Won't Fix
> Status in “linux-backports-modules-2.6.32” source package in Lucid:
>  Fix Released
> Status in “gobi-loader” source package in Maverick:
>  Fix Released
> Status in “linux” source package in Maverick:
>  Fix Released
> Status in “linux-backports-modules-2.6.32” source package in Maverick:
>  Invalid
>
> Bug description:
>  SRU justification (for LBM in Lucid):
>
>  Impact: Certain models of 3G hardware (Gobi) which apparently are quite
>  common, require several changes to work. First, the kernel module needs
>  to be updated, which requires larger modifications. Second, a new firm-
>  ware loader is required together with a matching udev rule.
>
>  Fix: In order to prevent regressions, the driver backport was done in
>  LBM and also adds a new binary subpackage (lbm-wwan). This package also
>  contains the loader and the udev rule.
>  NOTE! The drivers also requires firmware files which need to be manually
>  gathered as they are not redistributable.
>
>  Testcase: Without this backport no 3G connections are possible. Sevral
>  users in the bug report had successfully used the driver from the test
>  package after collecting the required firmware files.
>
>  ---
>
>  Binary package hint: linux-image-generic
>
>  $ uname -a
>  Linux phoenix 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux
>
>  $ cat /proc/version_signature
>  Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
>
>  $ lsusb
>  03f0:201d Hewlett-Packard <-- HP un2400 Mobile Broadband Module (QDL interface)
>
>  HP un2400 mobile broadband modem stopped working after i upgraded to lucid.
>  I can not load firmware anymore to my modem's Qualcomm Gobi USB chip using gobi_loader.
>  http://www.codon.org.uk/~mjg59/gobi_loader/
>
>  There was no problems on previous Ubuntu version (Karmic, kernel
>  2.6.31*). As i understand all devices based on this chip will not work
>  on lucid, if this will not be fixed.
>
>  HP un2400 is recognized by kernel's qcserial module. qcserial.c was not changed from 2.6.31 to 2.6.32.
>  After searching internet i found that this is related to changes in the kernel's usbserial module:
>  "The qcserial driver is currently broken in 2.6.32 and later. It's due to the switch to using kfifo for usb serial, but we haven't been able to work out the actual cause. I'm looking at alternative approaches."
>  Source: http://mjg59.livejournal.com/120577.html
>
>  Contact me if You need additional information.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/linux/+bug/554099/+subscribe
>