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?
Thanks.
____________________________________
Message: 4
Date: Tue, 10 Mar 2009 10:08:11 -0700
From: Chetan Karia <
chetankaria gmail com>
Subject: Supporting new Sierra CDMA modems.
To:
networkmanager-list gnome orgMessage-ID:
<
521673c40903101008y3634b54cjcbfb73cb470822d3 mail gmail com>
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 <
sxpert sxpert org>
Subject: Re: Supporting new Sierra CDMA modems.
To:
networkmanager-list gnome orgMessage-ID: <
20090310171238 GF11537 sxpert org>
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
linux-hotplug vger kernel org> Thanks,
> Chetan
> _______________________________________________
> NetworkManager-list mailing list
>
NetworkManager-list gnome org>
http://mail.gnome.org/mailman/listinfo/networkmanager-list------------------------------
Message: 6
Date: Tue, 10 Mar 2009 18:50:37
+0100
From: Alexander Sack <
asac ubuntu com>
Subject: Re: Supporting new Sierra CDMA modems.
To: Chetan Karia <
chetankaria gmail com>
Cc:
networkmanager-list gnome orgMessage-ID: <
20090310175037 GH29428 jwsdot com>
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 <
cra WPI EDU>
Subject: Forcing a BSSID, unchecking "Connect automatically" doesn't
work
To:
networkmanager-list gnome orgMessage-ID: <
20090310185851 GO10097 angus ind WPI EDU>
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 <
dmoseley mvista com>
Subject: Shutting down specific device
To:
networkmanager-list gnome orgMessage-ID: <
49B6BD8C 7090000 mvista com>
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
NetworkManager-list gnome orghttp://mail.gnome.org/mailman/listinfo/networkmanager-listEnd of NetworkManager-list Digest, Vol 54, Issue 22
***************************************************
