| 2008-12-07 13:39:31 |
Mike |
bug |
|
|
added bug |
| 2008-12-17 15:47:37 |
Cleber Santz |
bug |
|
|
added attachment '10-modem.fdi' (10-modem.fdi) |
| 2008-12-17 15:47:55 |
Cleber Santz |
bug |
|
|
added attachment 'lsusb.log' (lsusb.log) |
| 2009-02-12 20:17:37 |
Martin Pitt |
hal-info: status |
New |
Incomplete |
|
| 2009-02-12 20:17:37 |
Martin Pitt |
hal-info: assignee |
|
pitti |
|
| 2009-02-12 20:17:37 |
Martin Pitt |
hal-info: statusexplanation |
|
Mike, Cleber, can you please try Paulo's suggestion? Run this in a terminal:
gksu gedit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi
do the change as proposed
sudo rm /var/cache/hald/fdi-cache
reboot
|
|
| 2009-02-16 00:15:11 |
Paulo Neto |
hal-info: status |
Incomplete |
In Progress |
|
| 2009-02-16 00:15:11 |
Paulo Neto |
hal-info: statusexplanation |
Mike, Cleber, can you please try Paulo's suggestion? Run this in a terminal:
gksu gedit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi
do the change as proposed
sudo rm /var/cache/hald/fdi-cache
reboot
|
|
|
| 2009-02-16 10:47:39 |
Martin Pitt |
hal-info: status |
In Progress |
Incomplete |
|
| 2009-02-16 10:47:39 |
Martin Pitt |
hal-info: statusexplanation |
|
OK, I researched the history of this a bit. It seems that this chip is used in two different devices, but with the same product ID, and speak two different protocols:
<!-- Qualcomm: Telstra/NextG CDMA , ZTE CDMA Tech -->
<match key="@info.parent:usb.product_id" int_outof="0x0001;0xfffe">
<match key="@info.parent:usb.interface.number" int="0">
<append key="modem.command_sets" type="strlist">IS-707-A</append>
</match>
</match>
The 1 here was assumedly correct when this got committed first. But it is not called "ONDA" here. So perhaps we need a more fine-grained differentiation based on product names. Can anyone who is affected by this please do
lshal > /tmp/hal.txt
and attach /tmp/hal.txt here? |
|
| 2009-02-16 16:29:45 |
jsenlai |
bug |
|
|
added attachment 'hal.txt' (result of lshal) |
| 2009-02-17 01:54:02 |
Paulo Neto |
bug |
|
|
added attachment 'lshal.txt' (lshal.txt) |
| 2009-02-18 10:57:58 |
Martin Pitt |
bug |
|
|
assigned to linux (Ubuntu) |
| 2009-02-19 13:41:04 |
Danne MCA |
bug |
|
|
added attachment '20-broken-usb-sticks.fdi' (20-broken-usb-sticks.fdi) |
| 2009-03-04 14:58:33 |
Martin Pitt |
hal-info: status |
Incomplete |
Won't Fix |
|
| 2009-03-04 14:58:33 |
Martin Pitt |
hal-info: assignee |
pitti |
|
|
| 2009-03-04 14:58:33 |
Martin Pitt |
hal-info: statusexplanation |
OK, I researched the history of this a bit. It seems that this chip is used in two different devices, but with the same product ID, and speak two different protocols:
<!-- Qualcomm: Telstra/NextG CDMA , ZTE CDMA Tech -->
<match key="@info.parent:usb.product_id" int_outof="0x0001;0xfffe">
<match key="@info.parent:usb.interface.number" int="0">
<append key="modem.command_sets" type="strlist">IS-707-A</append>
</match>
</match>
The 1 here was assumedly correct when this got committed first. But it is not called "ONDA" here. So perhaps we need a more fine-grained differentiation based on product names. Can anyone who is affected by this please do
lshal > /tmp/hal.txt
and attach /tmp/hal.txt here? |
We will not do anything about this in jaunty. Jaunty's network-manager will use the udev modem prober from tomorrow on, which will dynamically detect this, without the 10-modem.fdi maintenance nightmare.
Please see http://lists.freedesktop.org/archives/hal/2009-February/013004.html for details.
It would be great if people here could test Jaunty Alpha 6 next Thursday (booting the live system from CD should work, no install required) and see if things work. |
|
| 2009-03-04 14:58:54 |
Martin Pitt |
hal-info: status |
Incomplete |
Won't Fix |
|
| 2009-03-04 14:58:54 |
Martin Pitt |
hal-info: assignee |
pitti |
|
|
| 2009-03-04 14:59:30 |
Martin Pitt |
linux: status |
New |
Invalid |
|
| 2009-03-04 14:59:30 |
Martin Pitt |
linux: statusexplanation |
|
|
|
| 2009-03-04 15:01:12 |
Martin Pitt |
title |
3G ZTE MF622 modem not working after bugfix #291333 |
3G ZTE MF622 modem does not work with static hal FDIs |
|
| 2009-03-04 15:01:38 |
Martin Pitt |
linux: status |
New |
Won't Fix |
|
| 2009-03-04 15:01:38 |
Martin Pitt |
linux: statusexplanation |
|
We won't change the kernel in stable releases for this. |
|
| 2009-03-04 15:05:31 |
Martin Pitt |
hal-info: status |
New |
Incomplete |
|
| 2009-03-04 15:05:31 |
Martin Pitt |
hal-info: statusexplanation |
|
I'm not sure what to do with hal-info in intrepid (Ubuntu 8.10). I could revert the newly added modem in #291333, but since that has a different product ID (0002 instead of 0001 which is the problem here) it feels that this is just a red herring.
If anyone knows how to set up hal FDIs in a way that makes the 19d2:0001 with GSM-07.07 work without breaking the same device with the IS-707-A protocol, please speak up. So far the workarounds proposed here just make one or the other work, which is fine for local modifications, but we can't use that as a general solution. Or am I missing something?
Thank you! |
|
| 2009-04-01 18:43:53 |
Danne MCA |
bug |
|
|
added attachment 'hal.txt' (hal.txt) |
| 2009-12-18 11:51:16 |
berg |
linux (Ubuntu Jaunty): status |
Invalid |
Confirmed |
|
| 2010-05-13 00:27:49 |
Alex Valavanis |
hal-info (Ubuntu Intrepid): status |
Incomplete |
Invalid |
|
| 2011-07-18 18:12:17 |
Leann Ogasawara |
linux (Ubuntu Jaunty): status |
Confirmed |
Won't Fix |
|
