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



this didnt go to list (by accident i guess ... CCing again).

On Sun, Nov 16, 2008 at 07:24:37PM +0100, Knud Müller wrote:
> On Sat, Nov 15, 2008 at 2:26 PM, Alexander Sack <asac ubuntu com> wrote:
> > On Fri, Nov 14, 2008 at 05:15:09PM -0500, Dan Williams wrote:
> >> On Fri, 2008-11-14 at 22:40 +0100, Knud Müller wrote:
> >> > Hi,
> >> >
> >> > My Vodafone Card creates when plugged into my notebok 3
> >> > devices /dev/ttyUSB0,1 and 2. Network Manager recognises
> >> > it correctly and opens a wizzard to create a connection.
> >> > NM uses when connecting afterwards /dev/ttyUSB0 (I found out by accident
> >> > as it is mentioned in the tooltip / is there any log). NM fails
> >> > silently, there is simply no connection, but no error message too. This
> >> > devicedoesnt work with gnome-ppp too, so I assume its the wrong Port.
> >> > When using /dev/ttyUSB2 with gnome-ppp I can establish a 3G connection.
> >> > As I was unable to find any setting to tell NM to use ttyUSB2 instead -
> >> > what can I do about it?
> >>
> >> Which port is actually the control port is determined (at the moment) by
> >> HAL .fdi files, typically in:
> >>
> >> /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi
> >>
> >> The full 'lshal' output would be needed to determine how to update
> >> 10-modem.fdi correctly.
> >
> > If you are using ubuntu, please file a bug against hal-info package in
> > launchpad with the fixed modem.fdi information.
> >
> >  - Alexander
> >
> >
> Alexander: Yes, it is Ubuntu 8.10 - I think your request is directed to Dan?

No, I ment you ;): If you find out what is wrong file a bug against
hal-info package in launchpad so we can take care that your device is
fixed everywhere.






> 
> Dan: I fiddled a little with the fdi file. Ive found the dtd on my
> filesystem and it gave me some idea of whats going on if a device is
> added.
> lshal prints something like '7011' for my modem. The fdi file has an
> 'Option' entry where 0x7011 occurs.
> 
>       <!-- Option -->
>       <match key="@info.parent:usb.vendor_id" int="0x0af0">
>         <!-- Colt,Ricola,Ricola Light,Ricola Quad,Ricola Quad
> Light,Ricola Ndis,Ricola Ndis Light;Ricola Ndis Quad,Ricola Ndis Quad
> Light,
>              Cobra,Cobra Bus,Viper,Viper Bus,Gt Max Ready,Gt Max,Fuji
> Modem Light,Fuji Modem Gt,Fuji Modem Ex,Fuji Network Light,Fuji
> Network Gt,
>              Fuji Network Ex,Koi Modem,Koi Network,Scorpion
> Modem,Scorpion Network,Etna Modem,Etna Network,Etna Modem Lite;Etna
> Modem Gt,
>              Etna Modem Ex,Etna Network Lite,Etna Network Gt,Etna
> Network Ex,Etna Koi Modem,Etna Koi Network -->
>         <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">
>           <match key="@info.parent: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>
>       </match>
> 
> But as far as I understood it only adds the modem command set. The
> interface Number is already set, as this entry matches on it. But
> where is the interface number set? How can I start hal in debugging
> and force it to write some more log? The 'latest HAL specification'
> gave me no hint at all...
> 
> 
> I just got some more Idea: lsusb shows "Bus 007 Device 003: ID 0af0:7011 Option"
> But theres nowhere the device name ttyUSB0 or 2 or whatever - where is that set?
> 
> Knud
> 
> Knud
> 

 - Alexander



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