Using iwl3945 instead of ipw3945 in gutsy?
Christopher James Halse Rogers
chalserogers at gmail.com
Tue Aug 28 00:14:57 UTC 2007
On Mon, 2007-08-27 at 19:30 +0300, Marius Gedminas wrote:
> On Mon, Aug 27, 2007 at 05:25:05PM +0200, Reinhard Tartler wrote:
> > Hi fellow gutsy users,
> > I noticed that gutsy ships the ipw3945 driver in
> > /lib/modules/2.6.22-10-generic/ubuntu/wireless/iwlwifi/iwl3945.ko in
> > addition to the ipw3945:
> > /lib/modules/2.6.22-10-generic/ubuntu/wireless/ipw3945/ipw3945.ko
> Cool, I'll have to try it.
> > On boot, ipw3945 is loaded. Is there some easy way to switch from
> > ipw3945 to iwl3945? I mean, I can of course `modprobe -r $driver &&
> > modprobe $other_driver`, but is there some way to make this more
> > permanent?
> You could add ipw3945 to /etc/modprobe.d/blacklist, but I don't know if
> that will get you iwl3945 loaded automatically. Probably not: I do not
> see the pci alias lines in modinfo iwl3945 that I see in modingo ipw3945.
You can add iwl3945 to /etc/modules, and it'll get loaded on startup.
If I remember the changelog correctly, the PCI aliases are deliberately
patched out to ensure iwl isn't accidentally loaded. Experiences with
this driver vary - for some people it apparently works better than ipw,
for me it stops working after 15-60 minutes and leaks references
preventing the module being unloaded and a clean shutdown.
> > Moreover, a manual module load didn't make network manager detect my
> > wifi hardware with iwl. Does this work for other people?
I find that restarting network manager works
- /etc/dbus/event.d/25NetworkManager & 26... can be restarted like init
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part
More information about the Ubuntu-devel-discuss