Remove ZTE Modem ZeroCD from unusual_devs.h

[Cleber Santz]

  Like discuted here https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/305968 the ZTE MF 622 Modem and some others 3G Modens have 2 devices using same USB port, in ZTE MF 622 case: ZeroCD (19d2:2000) and Modem (19d2:0001).

  When ZTE Modem is powered on first mount device 19d2:2000 (ZeroCD). When device 19d2:2000 is ejected ZTE Modem switch to device 19d2:0001 (Modem).

  But if ZeroCD are blocked by the Kernel the ZeroCD is never mounted, so ZTE Modem do not switch to device 19d2:0001 (Modem) this cause two problems:

  1) When plug the modem on system already up and running, the ZeroCD are not mounted so you cannot switch to Modem device;

  2) Many BIOS not detect USB devices at BOOT, so when Linux boot ZTE Modem still have device 19d2:2000 active

  The problem one can be solved pluging device before power on the machine, but in the second case the modem cannot be used.

  The better way to solve this is removing ZTE Modem from unusual_devs.h and let user eject the ZeroCD to use the modem, or make a UDEV rule to automatic eject the device when this is mounted.

  Until Ubuntu 8.04 release this work fine.

unusual_devs.h:
++++++++++++++++++++++++++++++++++++++++++++++
/* Reported by Mauro Andreolini <email address hidden>
 * This entry is needed to bypass the ZeroCD mechanism
 * and to properly load as a modem device.
 */
/*UNUSUAL_DEV( 0x19d2, 0x2000, 0x0000, 0x0000,
                "Onda ET502HS",
                "USB MMC Storage",
                US_SC_DEVICE, US_PR_DEVICE, NULL,
                US_FL_IGNORE_DEVICE),
*/
++++++++++++++++++++++++++++++++++++++++++++++

$ lsb_release
Distributor ID: Ubuntu
Release: 9.04
Codename: jaunty

$ uname -a
Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

[Danne MCA (danne-mca)]

This happen with me too. I try compile the kernel, but haven't free disk space to do. Hope a fix in the next kernel, I think this can be easy to do.

[sarcastic (sam-duarte)]

Hello
I have a peculiar situation in my Ubuntu 9.04 with kernel 2.6.29.03 that is already with the code

UNUSUAL_DEV( 0x19d2, 0x2000, 0x0000, 0x0000,
                "Onda ET502HS",
                "USB MMC Storage",
                US_SC_DEVICE, US_PR_DEVICE, NULL,
                US_FL_IGNORE_DEVICE)

 out of the unusual_devs.h

my 10-modem.fdi is like this:

<match <email address hidden>:usb.vendor_id" int="0x19d2">
        <!-- Qualcomm: Telstra/NextG CDMA , ZTE CDMA Tech -->
        <match <email address hidden>:usb.product_id" int_outof="0x0001;0xfffe">
          <match <email address hidden>:usb.interface.number" int="0">
            <append key="modem.command_sets" type="strlist">IS-707-A</append>
          </match>
        </match>
        <!-- ZTE MF626 HSDPA USB dongle -->
        <match <email address hidden>:usb.product_id" int="0x2000">
          <match <email address hidden>:usb.interface.number" int="0">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
        <!-- Onda MSA501HS HSDPA USB dongle -->
        <match <email address hidden>:usb.product_id" int="0x0001">
          <match <email address hidden>:usb.interface.number" int="2">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
        <!-- ZTE MF628 HSDPA USB dongle -->
        <match <email address hidden>:usb.product_id" int="0x0015">
          <match <email address hidden>:usb.interface.number" int="3">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
        <!-- ONDA MF632 HSDPA USB dongle -->
        <match <email address hidden>:usb.product_id" int="0x0002">
          <match <email address hidden>:usb.interface.number" int="2">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
      </match>

lsusb returns "Bus 003 Device 007: ID 19d2:0001 ONDA Communication S.p.A."
but network manager don't detect the modem.

I've tried also with the kernel 2.6.28.11 and 2.6.28.12 but with no changes...

the wired is that i was on the normally surfing on the net with the mf622, i turned off the pc and on the next day when i turn it on again simply NM don't detect the modem... i haven't install any program or made any update. :S

heeeelp meeee
Samuel aka Sarcastic

[Cleber Santz (clebersantz)]

Hello,

   Seens that the code above are removed from unusual_devs.h in Karmic 2.6.30-5-generic

++++++++++++++++++++++++++++++++++++++++++++++
/* Reported by Mauro Andreolini <email address hidden>
 * This entry is needed to bypass the ZeroCD mechanism
 * and to properly load as a modem device.
 */
/*UNUSUAL_DEV( 0x19d2, 0x2000, 0x0000, 0x0000,
                "Onda ET502HS",
                "USB MMC Storage",
                US_SC_DEVICE, US_PR_DEVICE, NULL,
                US_FL_IGNORE_DEVICE),
*/
++++++++++++++++++++++++++++++++++++++++++++++

So for me, ZTE is working fine with Ubuntu 9.10 Alpha 1. But will be helpful create a UDEV rule like attached file to eject the ZeroCD

[Danne MCA (danne-mca)]

I'll install Karmic today in a pc from my work to test. Frist with not udev rule, and after with on in /etc/udev/rules.d/. brb.

[Cleber Santz (clebersantz)]

I having some problems with Karmic, so to test it i have installed the Karmic kernel on Jaunty, install this packages : http://packages.ubuntu.com/karmic/linux-image-2.6.30-5-generic and http://packages.ubuntu.com/karmic/wireless-crda.

Remember !!! Make this at your own risk !!!

[sarcastic (sam-duarte)]

I have found the solution :D
the problem is on the network manager, the version 0.7.1 is only RC and don't detect the device.
Just downgrade to 0.7.0 and use gcom to register your modem in the network
"sudo /usr/bin/gcom -d /dev/ttyUSB2"

if you want to plug the modem with the pc turned on upgrade to kernel 2.6.29 and it works just fine ;)

[Danne MCA (danne-mca)]

OK, I installed the Karmic and did the tests. With a simple instalation, the modem has no detected, even conected in boot or in session. With the udev rule, it are detected in both case =]

I'm thinking about change the Ibex to Karmic already =P

Thanks to all developers and to Cleber to report this.

[Danne MCA (danne-mca)]

... change the Jaunty* ...

[Cleber Santz (clebersantz)]

Danne,

  You can test it in Jaunty with "Mainline" kernel's, go to http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/ and install this files:

   linux-headers-2.6.29-02062903_2.6.29-02062903_all.deb
   linux-headers-2.6.29-02062903-generic_2.6.29-02062903_amd64.deb
   linux-image-2.6.29-02062903-generic_2.6.29-02062903_amd64.deb

  change amd64 for i386 if you still using i386 distro.

Regards,
Cleber Santz.

[Danne MCA (danne-mca)]

Thanks. I do the tests. Install the .debs (i386) and reboot. Choose the new kernel to boot and wait. All ok at here. Plug the modem and wait... Nothing happens, continues 19d2:2000. Use the udev rule and reboot. At boot my cd drive open (O.o). At the session I plug the modem again and wait, ok now, the modem was detected with 19d2:0001. But I can't get connection. Try using other modem (a huawei e226) and it work normal. Try my modem again, and nothing =[.

I remove this kernel and back to my normal Jaunty Kernel.

I will continues using the karmic (with the modem working fine, but with the udev rules making the cd drive open at boot) to test.

Thanks to try help again.

[Cleber Santz (clebersantz)]

Danne,

  Com esses novos Kernels (2.6.29 e superior) o seu modem é montado primeiro
como um CD, você precisa ejeta-lo para poder usar o modem, a regra do UDEV
somente automatiza este trabalho. Se você não quiser usar a regra UDEV você
pode fazer isso manualmente:

execute "dmesg | grep scsi" e procure por ZTE

[ 7.927288] scsi 5:0:0:0: CD-ROM ZTE USB SCSI CD-ROM
2.31 PQ: 0 ANSI: 2
[ 7.948251] sr1: scsi-1 drive
[ 7.949049] sr 5:0:0:0: Attached scsi CD-ROM *sr1*

no meu caso o CD foi montando em *SR1* então após o boot basta executar
"eject /dev/sr1" e você poderá usar o modem normalmente.

Abraços,
Cleber Santz.

2009/5/22 Danne <email address hidden>

> Thanks. I do the tests. Install the .debs (i386) and reboot. Choose the
> new kernel to boot and wait. All ok at here. Plug the modem and wait...
> Nothing happens, continues 19d2:2000. Use the udev rule and reboot. At
> boot my cd drive open (O.o). At the session I plug the modem again and
> wait, ok now, the modem was detected with 19d2:0001. But I can't get
> connection. Try using other modem (a huawei e226) and it work normal.
> Try my modem again, and nothing =[.
>
> I remove this kernel and back to my normal Jaunty Kernel.
>
> I will continues using the karmic (with the modem working fine, but with
> the udev rules making the cd drive open at boot) to test.
>
> Thanks to try help again.
>
> --
> Remove ZTE Modem ZeroCD from unusual_devs.h
> https://bugs.launchpad.net/bugs/373821
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Gustavo Rahal (gustavo-grahal)]

The following has worked for me:

1. install 2.6.30rc6 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc6/ in jaunty
2. reboot, gnome starts up
3. insert ZTE MF636 USB modem
4. wait icon to appear on desktop then "Eject volume"
5. wait around 30s for Network Manager to show device in its devices list
6. Now just create a Mobile connection and connect

[Cleber Santz (clebersantz)]

Yes, with kernel 2.6.30rc6 the modem work's better

[Danne MCA (danne-mca)]

I'll try this kernel in my notebook monday.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi to all above trying hard for this bug.

Custavo can you please determine if at the above "test procedure" I have to install only the:
linux-image-2.6.30-020630rc6-generic_2.6.30-020630rc6_i386.deb
or I need also a Header package? If yes which one?

I have a ZTE MF636 and would like to test it on an EeePC 1000H
(now=Linux pc 2.6.28-12-generic #43-Ubuntu).

For my tests do I have to change/add the 0x0031 productID to /usr/.../10-modem.fdi file?

Please note that it is very helpful to give a specific procedure to test (as above).

Thanks for your time and effort,
George

[Danne MCA (danne-mca)]

I've tested the 2.6.30 RC6 kernel and my modem doesn't work. I'm still in 2.6.28-11, waiting for new RC.

[Gustavo Rahal (gustavo-grahal)]

On Sat, May 23, 2009 at 7:42 PM, GeorgeVita <email address hidden> wrote:

> Hi to all above trying hard for this bug.
>
> Custavo can you please determine if at the above "test procedure" I have to
> install only the:
> linux-image-2.6.30-020630rc6-generic_2.6.30-020630rc6_i386.deb
> or I need also a Header package? If yes which one?
>

only the image, header is not needed (and I have not installed)

>
> I have a ZTE MF636 and would like to test it on an EeePC 1000H
> (now=Linux pc 2.6.28-12-generic #43-Ubuntu).
>
> For my tests do I have to change/add the 0x0031 productID to
> /usr/.../10-modem.fdi file?
>

I did not change anything, just installed the image .deb pkg

> Please note that it is very helpful to give a specific procedure to test
> (as above).
>
> Thanks for your time and effort,
> George
>
> --
> Remove ZTE Modem ZeroCD from unusual_devs.h
> https://bugs.launchpad.net/bugs/373821
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi again,
I tested above in ALL possible parameters and did NOT work.
My EeePC 1000H was a -proposed updated "Linux pc 2.6.28-12-generic #43-Ubuntu" (normal 9.04 and not Netbook remix). Both rc6 and rc7 tested. Possibilities tried: Wireless enabled/disabled, modem attached before or after boot. Every try was a fully shut down, boot again. The modem was removed in every shut down because of power existing to USB port when connected to the power outlet 9USB charge mode). Then reinserted before or after boot.

A typical test cycle was: Boot without modem, wait for the system to stabilise, attach modem, wait to see the ZTEMODEM drive, eject this drive, wait >30 seconds, follow wizard instructions (if started and not stucked), create new connection, click on network icon to find the providers name and connect but: "mobile broadband not managed" or sometimes I saw the provider but before clicking it stucked. Stucked I mean no mouse no kbrd. Holding power button made a power off.

I managed to "dmesg" 2 times before stuck! I will post you a link with the "photos" taken.

I do not know if rc6/7 are facing problems with the EeePC or I have to do a clean 9.04 or 9.10 A1) install and then try the rc6/7 kernel.

A final note is that my Huawei E169 works all times with all kernels (9.04, proposed, rc6, rc7) in the same h/w without any stuck (this note rejects my one above).

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

This image: http://www.acomelectronics.com/GeorgeVita/ZTEMF636_rc7.jpg
shows the last lines of "dmesg" just before the stuck.

[Cleber Santz (clebersantz)]

 George/Danne

   Boot with modem connected and after boot run "dmesg > dmesg.txt" and post dmesg.txt here.

[GeorgeVita (8-launchpad-mhnyma-com)]

EeePC 1000H, 2GB RAM, Wireless and Bluetooth Enabled, no Ethernet connection, all previous Connections Deleted to prevent auto connection via wifi and let the Broadband Wizard begin.
Linux pc 2.6.30-020630rc7-generic #020630rc7
Boot with the ZTE MF636 (original mode 19d2 : 2000) attached
The ZTEMODEM drive found, wait around 30 seconds and dmesg > dmesg_g1.txt (attached)
No stuck at this point.

In another try, after ejecting the ZTEMODEM drive, dmesg shows a loop while creates the ttyUSBx ports, reaching ttyUSB14, 15 ...

[ 317.307900] option 1-3:1.0: GSM modem (1-port) converter detected
[ 317.308173] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB12
[ 323.265365] BUG: unable to handle kernel NULL pointer dereference at 00000029
[ 323.265391] IP: [<c03c4213>] usb_kill_urb+0x13/0xa0
[ 323.265418] *pde = 00000000
[ 323.265430] Oops: 0000 [#10] SMP
[ 323.265443] last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/idProduct
[ 323.265455] Modules linked in: isofs option usbserial usb_storage i915 drm i2c_algo_bit binfmt_misc ppdev bridge stp bnep lp parport joydev snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device iTCO_wdt iTCO_vendor_support snd uvcvideo psmouse soundcore serio_raw videodev v4l1_compat intel_agp pcspkr btusb rt2860sta(C) snd_page_alloc agpgart video output eeepc_laptop atl1e
[ 323.265600]
[ 323.265614] Pid: 4113, comm: nm-modem-probe Tainted: G D C (2.6.30-020630rc7-generic #020630rc7) 1000H
[ 323.265629] EIP: 0060:[<c03c4213>] EFLAGS: 00010202 CPU: 0
[ 323.265642] EIP is at usb_kill_urb+0x13/0xa0
[ 323.265653] EAX: 00000000 EBX: 00000001 ECX: f4d0f900 EDX: f6a5fa00
[ 323.265665] ESI: f4d63300 EDI: f4dcd998 EBP: f4e5be58 ESP: f4e5be3c
[ 323.265676] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 323.265690] Process nm-modem-probe (pid: 4113, ti=f4e5a000 task=f4e02550 task.ti=f4e5a000)
[ 323.265700] Stack:
[ 323.265706] 00000001 c1e0d1c0 00000002 f4e5be58 c050ec64 00000002 f4d63300 f4e5be80
[ 323.265733] f812f93e 00000000 c06eecc0 00000000 f6a5fa00 f4c7b000 f8133000 f6a5fa00
[ 323.265761] f4dcd960 f4e5beb8 f8107e73 ffffffff ffffffff f4c7b000 f4d0f900 f4d0f900
[ 323.265792] Call Trace:
[ 323.265800] [<c050ec64>] ? mutex_lock+0x14/0x40
[ 323.265820] [<f812f93e>] ? option_close+0x5e/0xd0 [option]
[ 323.265849] [<f8107e73>] ? serial_close+0x133/0x180 [usbserial]
[ 323.265879] [<c03396f9>] ? tty_release_dev+0x139/0x480
[ 323.265900] [<c0122498>] ? arch_flush_lazy_mmu_mode+0x8/0x40
[ 323.265919] [<c0127cb2>] ? kunmap_atomic+0x72/0x90
[ 323.265936] [<c01aa809>] ? do_anonymous_page+0x149/0x1a0
[ 323.265957] [<c0339a52>] ? tty_release+0x12/0x20
[ 323.265973] [<c01c85f1>] ? __fput+0xb1/0x1c0
[ 323.265992] [<c01c8719>] ? fput+0x19/0x20
[ 323.266007] [<c01c5137>] ? filp_close+0x47/0x70
[ 323.266024] [<c0512308>] ? do_page_fault+0x188/0x2e0
[ 323.266042] [<c01c64c1>] ? sys_close+0x61/0xb0
[ 323.266059] [<c0102ebc>] ? sysenter_do_call+0x12/0x28
[ 323.266078] Code: 08 85 c0 75 e3 89 f2 b8 78 1f 6e c0 e8 a7 be d8 ff 83 c4 14 5...

[GeorgeVita (8-launchpad-mhnyma-com)]

full file attached, including the looping creation of ttyUSBxx: dmesg_7.txt

[Danne MCA (danne-mca)]

I do more test today, and now get my modem works fine in RC6. At afternoon, will try the RC7.

Maybe I don't do the test yesterday so good. Because I don't make nothing different today, just try again. The modem was detected like a pen drive, and not like a CD. Just eject the drive and wait about 10 seconds to Network Manager find it.

=]

[Cleber Santz (clebersantz)]

George,

   Seems that your problem is in "nm-modem-probe"

      Pid: 3736, comm: nm-modem-probe Tainted: G D C (2.6.30-020630rc7-generic #020630rc7) 1000H

  Please, check your NetworkManager version/configuration and, if you could, try the new kernel with a fresh Jaunty installation. Maybe your distro have incompatible versions of applications.

[Danne MCA (danne-mca)]

I'm using the 2.6.30 RC7 kernel right now. All working fine.

[GeorgeVita (8-launchpad-mhnyma-com)]

Fresh install from "ubuntu-9.04-desktop-i386.iso" (md5sum=ok) resulting to:
Linux pc 2.6.28-11-generic #42-Ubuntu

Then rc7 kernel installed from "linux-image-2.6.30-020630rc7-generic_2.6.30-020630rc7_i386.deb", shut down, boot, uname -a shows:
Linux pc 2.6.30-020630rc7-generic #020630rc7

Shut down, attach MF636, boot, ZTEMODEM drive shown, wait 20-30 seconds more, open terminal, dmesg > dmesg_g11.txt (attached).

Note: I did not update anything after original 9.04 installation. Just run the rc7 .deb file. Would you like to test also after full upgraading the 9.04?
(also Network Manager Applet shows me 0.7.0.100)
Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

I continued with the reject and stucked!

What I did: shut down, attach the MF636, boot, ZTEMODEM drive shown to desktop, wait around 1 minute, eject ZTEMODEM, wait till the wizard started, setup the new Connection, wizard finished, open a terminal window, dmesg > dmesg_g12.txt every 5-6 seconds till the complete freeze of the system. See attached file.

Do I have to update 9.04 and retry?

[GeorgeVita (8-launchpad-mhnyma-com)]

Finally I continued with: complete removal of rc7, full 9.04 update (update manager), shut down, MF636 attached, boot. The ZTEMODEM drive not shown. Within dmesg I found "usb-storage: device ignored". Stated as 19d2 : 2000 at lsusb. A removal/reinsertion gives:

[ 323.366334] usb 1-3: USB disconnect, address 2
[ 665.596104] usb 1-3: new high speed USB device using ehci_hcd and address 5
[ 665.742371] usb 1-3: configuration #1 chosen from 1 choice
[ 665.752174] usb-storage: device ignored
[ 699.568006] usb 1-3: USB disconnect, address 5

And then: rc7 installed, shut down, boot with the modem attached, ZTEMODEM shown, wait some seconds, from terminal: dmesg > dmesg_g31.txt (attached)
Eject, wait, dmesg to the terminal window, "new mobile broadband" window opened below terminal window and some seconds later stucked. At the terminal window you can see the loop again: ttyUSB0,1,2 later 1,2,3 etc. (photo at: www.acomelectronics.com/GeorgeVita/dmesg_g32.jpg

Regards,
George

[Cleber Santz (clebersantz)]

George,

   Install debug symbols and post here the NW backtrace, see https://wiki.ubuntu.com/DebuggingNetworkManager#Debugging%20Crashes.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Cleber,
I firstly "debug" the "debugging instructions" from the wiki!
NO_PUBKEY W: GPG error: http://ddebs.ubuntu.com jaunty
>>> followed instructions from http://ubuntuforums.org/showpost.php?p=7082357&postcount=2
E: Couldn't find package libnm-util0-dbgsym
>>> I used libnm-util1-dbgsym via Synaptic

Then I disabled wireless and bluetooth from BIOS, just to have less problems and minimize log files.

In my 1st try the system frozen before getting the "backtrace"!
A photo taken, www.acomelectronics.com/GeorgeVita/froz_26_1.jpg

In the 2nd try, the wizard started twice, I setup both, 4 (2+2) provider names appeared, I tried to connect with the last one (as ZTE modems have their ttyUSBx x=max useable port), was trying but not connected. No freeze! Got backtrace and syslog.
msgs_and_bt (attached) with ALL messages appeared to the terminal window including back trace (copy/paste).
syslog_g is a copy of /var/log/syslog (attached to next message)

In my 3rd try the debugger found an error, stopped, backtraced, ... frozen before copy!

>>> Can you suggest any "logging to a file" mode for the debugger?

In my next post I will send you some messages shown in the photos!

Regards,
George

At the second capturing the sed

[GeorgeVita (8-launchpad-mhnyma-com)]

"Frozen" photos:
http://www.acomelectronics.com/GeorgeVita/froz_26_1.jpg
http://www.acomelectronics.com/GeorgeVita/froz_26_2.jpg
http://www.acomelectronics.com/GeorgeVita/froz_26_3.jpg
http://www.acomelectronics.com/GeorgeVita/froz_26_4.jpg

syslog_g (attached)

My notes on "Using ZTE MF636 with various UBUNTU versions" at:
http://www.acomelectronics.com/GeorgeVita/ZTEonUBUNTU.html

And and update for the above using an 9.04 standard installation:
1. force it to 19d2:0031 with AT+ZCDRUN=8 (or possibly running usb_modeswitch)
2. EDIT /usr/share/.../10-modem.fdi file to have 0x0031 instead of 0x0015 (for 0x19d2 vendor)
3. reboot with the modem
4. disable wireless (solves other issues)
4. setup twice (that means 4 SAME providers)
5. connect with the last listed provider's name

Please note that I am listing all possible info here to help you solve this incompatibility. Also my netbook is dedicated to tests now! (www.acomelectronics.com/GeorgeVita/a_904_desktop.png)

Regards,
George

[Henrique Barbosa (hmjbarbosa)]

Hello all,

I read this bug report and a thousand of howto's on the net but I still can't get my MF622 working properly.
I'm using Jaunty (fresh install) with Kernel 2.6.28-12-generic on a HP Pavillion dv2137us. Not sure if I should
post this here or in the original bug report http://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/305968

Below I try to describe step by step what I tried so far.

(1) Before doing any changes:

The modem only works if I have it pluged in before booting. Pluging it in after boot makes it permanently
stick as 19d2:2000. usb_modeswitch can't change it. The reason seem to be that the device is ignored
(because of unusual_devs.h) and never get mounted, so that it can't be dismounted and switched to 0x0001.

(2) Modifying 10-modem.fdi (Paulo Neto's posts)

I've tried that but no success so far. I also tried to erase all 0x19d2 entries but the one about product 0x0001.
It also didn't work. By the way, firstly I tried only removing fdi-cache and restarting hal and udev by:

sudo /etc/init.d/hal restart
sudo /etc/init.d/udev restart

and then I tried rebooting... Same result, it doesn't work.

(3) Modifying 20-broken-usb-sticks.fdi (Paulo Neto's posts)

Same here, it doesn't make any difference.

(4) usb_modeswitch + udev rules

Following some howto's on the net, I configured usb_modeswitch and setup a udev rule to switch 0x2000
to 0x0001 and modprobe for usbserial at 0x0001 automatically. That didn't work either. Well, I should expect
that because usb_modeswitch wasn't doing its job on the command line before.

(5) Fixing unusual_devs.h

Tried that but got a compilation error:

ubuntu/qc-usb/quickcam.h:509: error: field ‘vpic’ has incomplete type
ubuntu/qc-usb/quickcam.h:511: error: field ‘vwin’ has incomplete type
ubuntu/qc-usb/qc-driver.c: In function ‘qc_v4l_init’:
ubuntu/qc-usb/qc-driver.c:2285: error: ‘VIDEO_PALETTE_RGB24’ undeclared (first use in this function)
ubuntu/qc-usb/qc-driver.c:2285: error: (Each undeclared identifier is reported only once

Can someone confirm which command should we use to recompile the kernel after removing 0x19d2
from unusual_devs.h? I did:

sudo apt-get install linux-kernel
cd /usr/src
sudo tar -xjf linux-source-2.6.28.tar.bz2
cd linux-source-2.6.28
gksu gedit drivers/usb/storage/unusual_devs.h
sudo make defconfig

By the way, we would have to do it every time we get a kernel update, right?. It would definitelly be better
if the kernel got fixed once and for all.

(6) New network manager.

My NM reports 0.7.0.100, I will try 0.7.1 and report back later today.

(7) New kernel

I'll try 2.6.29 or karmic and report back later today.

Regards,
Henrique

[Henrique Barbosa (hmjbarbosa)]

And attached here is the full kernel compilation error.

[Andy Whitcroft (apw)]

This is not a bug in the linux-meta package, moving to the linux package.

[GeorgeVita (8-launchpad-mhnyma-com)]

Just "keep trying",
approx. same behavior with "Linux pc 2.6.30-020630rc8-generic #020630rc8"
Attached before/after boot= 19d2 : 2000
After Eject of sr0= 19d2 : 0031
Loop creates ttyUSB7, 8 and 9, Network Manager stops running, the system freezes at all, within dmesg found:
option 1-3:1.1 device disconnected
option: option_instat_callback: error -108

All above with 2.6.30-rc8 over jaunty (9.04) full updated on EeePC 1000H single boot from Hard Disk and ZTE MF636 modem.

G

[Leann Ogasawara (leannogasawara)]

Based on the comment, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/373821/comments/3 , from @Cleber Santz, the original bug reporter, I'm marking this bug Fix Released for Karmic. Cleber, feel free to open a bug against udev for the rule you'd like to see included.

For anyone else still experiencing issues, if you could please open a new separate bug report that would be great. It's helpful to the development teams if bug reports target one specific issue against a specific set of hardware. Thanks.

[GeorgeVita (8-launchpad-mhnyma-com)]

Can you please delete also all my posts above as they are below the "fixed & working" 3rd comment.

Regards,
George