On Tue, 2009-03-10 at 19:54 -0700, Josefa Molina wrote:
>
> Hi,
>
> I am having this problem and would like to know what exact text change
> is needed so that I can add it to the file. Also, I've seen this fix
> list the location of the file in "etc/hal/fdi/information/modems.fdi"
> vs "/usr/share/hal/fdi/information/10freedesktop/". Which is correct?
Only /usr/share/hal/fdi/information/10freedesktop is the "official"
location provided by the upstream hal-info project. Not sure what is
creating the other location.
In the file you'll see a section for Sierra devices. Look for the
section starting with "<!-- Sierra Wireless -->". In that section,
you'll see one block for GSM devices, and one block for CDMA devices.
Add your modem's "product ID" to the end of the list in the right
section for your modem. The "product ID" can be found as the
hexadecimal number after the colon in the output of 'lsusb' for your
modem:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
^^^^ product ID
Dan
> Thanks.
> ____________________________________
> Message: 4
> Date: Tue, 10 Mar 2009 10:08:11 -0700
> From: Chetan Karia <[email protected]>
> Subject: Supporting new Sierra CDMA modems.
> To: [email protected]
> Message-ID:
> <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I am an employee of Sierra wireless USA. I was testing network manager
> on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with
> network manager except our two new products which were not detected by
> Network Manager. On investigating further I discovered its just matter
> of adding the Vendor ID and Product ID of our new devices to the file
> "10-modem.fdi" under the directory
> "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file
> and add the VID/PID's the Network Manager detects the devices and
> connects to CDMA network. I wanted to know the procedure to officially
> add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I
> do not have to edit it manually.
>
> Your help will be much appreciated.
>
> Thanks,
> Chetan
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 10 Mar 2009 18:12:38 +0100
> From: Rapha?l Jacquot <[email protected]>
> Subject: Re: Supporting new Sierra CDMA modems.
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote:
> > Hi,
> >
> > I am an employee of Sierra wireless USA. I was testing network
> manager
> > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well
> with
> > network manager except our two new products which were not detected
> by
> > Network Manager. On investigating further I discovered its just
> matter
> > of adding the Vendor ID and Product ID of our new devices to the
> file
> > "10-modem.fdi" under the directory
> > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this
> file
> > and add the VID/PID's the Network Manager detects the devices and
> > connects to CDMA network. I wanted to know the procedure to
> officially
> > add the VID/PID's of new Sierra device to 10-modem..fdi file, so
> that I
> > do not have to edit it manually.
> >
> > Your help will be much appreciated.
>
> you should contact the Udev people
>
> [email protected]
>
> > Thanks,
> > Chetan
> > _______________________________________________
> > NetworkManager-list mailing list
> > [email protected]
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 10 Mar 2009 18:50:37 +0100
> From: Alexander Sack <[email protected]>
> Subject: Re: Supporting new Sierra CDMA modems.
> To: Chetan Karia <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> Hi,
>
> On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote:
> > Hi,
> >
> > I am an employee of Sierra wireless USA. I was testing network
> manager
> > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well
> with
> > network manager except our two new products which were not detected
> by
> > Network Manager. On investigating further I discovered its just
> matter
> > of adding the Vendor ID and Product ID of our new devices to the
> file
> > "10-modem.fdi" under the directory
> > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this
> file
> > and add the VID/PID's the Network Manager detects the devices and
> > connects to CDMA network. I wanted to know the procedure to
> officially
> > add the VID/PID's of new Sierra device to 10-modem.fdi file, so that
> I
> > do not have to edit it manually.
>
> Please provide info on the exact pieces required.
>
> One way to move foward would be to file a bug with that info against
> hal-info [1] package in launchpad. We (ubuntu) takes care that info
> submitted there regularly gets committed upstream.
>
> [1] - https://bugs.launchpad.net/ubuntu/+source/hal-info/+filebug
>
> - Alexander
>
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 10 Mar 2009 14:58:51 -0400
> From: Chuck Anderson <[email protected]>
> Subject: Forcing a BSSID, unchecking "Connect automatically" doesn't
> work
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> I'm trying to force a specific BSSID (testing 802.11n in fact) but
> NetworkManager keeps trying to associate to the other BSSID's (APs)
> on
> the same ESSID. In fact, it popped up with a dialog to set up the
> encryption settings, etc. (WPA TLS) because it couldn't use the
> connection profile that I forced the BSSID on. So I let it create
> another Auto profile, set up the encryption, and then unchecked the
> "Connect automatically"...but guess what? It still connects
> automatically.
>
> How do I force NetworkManager to ignore all BSSID's for a specific
> ESSID, except for the one I want?
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 10 Mar 2009 12:20:44 -0700
> From: Drew Moseley <[email protected]>
> Subject: Shutting down specific device
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Is there a bit of scripting magic where I can force a specific
> network device to shut down?
>
> We have a device that when it is powered down via external switch,
> Network Manager handles it but sees a state change to FAILED so it
> is marked as invalid. I'd like to be able to tell Network Manager
> that it should be disconnected so it is handled more gracefully.
>
> I've started playing with dbus-send but so far can only manage to
> use the sleep and wake commands successfully.
>
> Drew
>
>
> ------------------------------
>
> _______________________________________________
> NetworkManager-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
> End of NetworkManager-list Digest, Vol 54, Issue 22
> ***************************************************
>
> _______________________________________________
> NetworkManager-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list
