Re: NM and my Vodafone PCMCIA-card doesnt work, NM uses /dev/ttyUSB0 instead of /dev/ttyUSB2



On Mon, Nov 17, 2008 at 9:13 AM, Tambet Ingo <tambet gmail com> wrote:
> On Sat, Nov 15, 2008 at 3:26 PM, Alexander Sack <asac ubuntu com> wrote:
>> If you are using ubuntu, please file a bug against hal-info package in
>> launchpad with the fixed modem.fdi information.
>
> I'm not using ubuntu, but I've seen the same issue reported elsewhere.
> Does the attached patch fix the issue for you? (Uncompress it to
> /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi and restart
> the computer).
>
> Tambet
>

Hi Ingo,

yesssss! This one works. I made a diff

32c32
<         <!-- Colt,Ricola,Ricola Light,Ricola Quad,Ricola Quad
Light,Ricola Ndis,Ricola Ndis Light, Ricola Ndis Quad,Ricola Ndis Quad
Light,
---
>         <!-- Colt,Ricola,Ricola Light,Ricola Quad,Ricola Quad
Light,Ricola Ndis,Ricola Ndis Light;Ricola Ndis Quad,Ricola Ndis Quad
Light,
34c34
<            Fuji Network Ex,Koi Modem,Koi Network,Scorpion Modem,Scorpion
Network,Etna Modem,Etna Network,Etna Modem Lite, Etna Modem Gt,
---
>            Fuji Network Ex,Koi Modem,Koi Network,Scorpion Modem,Scorpion
Network,Etna Modem,Etna Network,Etna Modem Lite;Etna Modem Gt,
36c36
<         <match key="@info.parent:usb.product_id"
int_outof="0x5000;0x6000;0x6100;0x6200;0x6300;0x6050;0x6150;0x6250;0x6350;0x6500;0x6501;0x6600;0x6601;0x6701;0x6711;0x6721;0x6741;0x6761;0x6731;0x6751;0x6771;0x6800;0x6811;0x6901;0x6911;0x7001;0x7021;0x7041;0x7061;0x7031;0x7051;0x7071;0x7100;0x7111">
---
>         <match key="@info.parent:usb.product_id"
int_outof="0x5000;0x6000;0x6100;0x6200;0x6300;0x6050;0x6150;0x6250;0x6350;0x6500;0x6501;0x6600;0x6601;0x6701;0x6711;0x6721;0x6741;0x6761;0x6731;0x6751;0x6771;0x6800;0x6811;0x6901;0x6911;0x7001;0x7011;0x7021;0x7041;0x7061;0x7031;0x7051;0x7071;0x7100;0x7111">
42,49d41
<
<         <match key="@info.parent:usb.product_id" int_outof="0x7011">
<           <match key="@info.parent: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>
<
184c176
<         <!-- PC5740, PC5750, UM150 EVDO rev A card -->
---
>         <!-- PC5740;PC5750;UM150 EVDO rev A card -->
227c219
<              5720 Mobile Broadband CDMA/EVDO Mini-Card == Novatel
Expedite E725 CDMA/EV-DO,
---
>              2x 5720 Mobile Broadband CDMA/EVDO Mini-Card == Novatel
Expedite E725 CDMA/EV-DO,
229c221
<         <match key="@info.parent:usb.product_id"
int_outof="0x8114;0x8117;0x8128;0x8129;0x8133">
---
>         <match key="@info.parent:usb.product_id"
int_outof="0x8114;0x8117;0x8128;0x8129;0x8133;0x8134">
354,355c346,347
<         <!-- 6300/3109c/6120
Classic/E71/E70/N95-3/E90/N70/E61/N95-2/N96/N82 -->
<         <match key="@info.parent:usb.product_id"
int_outof="0x4f9;0x64;0x2f;0xab;0x418;0x4f0;0x4ce;0x43a;0x44d;0x070;0x3a;0x72">
---
>         <!-- 6300/3109c/6120
Classic/E71/E70/N95-3/E90/N70/E61/E51/N92/N95-2/N96 -->
>         <match key="@info.parent:usb.product_id"
int_outof="0x4f9;0x64;0x2f;0xab;0x418;0x4f0;0x4ce;0x43a;0x44d;0x42;0x72;0x70;0x3a">
369c361
<         <match key="@info.parent:usb.product_id" int="0x6000">
---
>         <match key="@info.parent:usb.product_id" int_outof="0x6000">


and it simply matches port 2 and port 2 gets the protocol attribute?

So my interpretion is that it goes through that cascade for every port.
The data port gets the modem protocol information and that is the
trigger to use this port by the network-manager?

Alexander: where can I post this bug and will they cross check, as other
modems occur as well in this passage, that the other products that work
differently are not affected by this patch? (I will stress this anyway)?

Knud


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]