ipw3945 wireless driver

raymano · 2007-07-26 22:19:49

Do the iwlwifi and iwlwifi-...-ucode packages, which are now available in the current repos, make the ipw3945 and ipw3945-ucode packages obsolete?

Thanks,
Raymano

peart · 2007-07-27 01:30:01

They are supposed to replace ipw3945 one day, when they reach maturity. I tried the iwl driver for a few days last week, and I suggest sticking with ipw for now. The new driver is still very "beta."

My 0.02.

peart · 2007-07-27 01:34:09

PS: iwl also adds support for a newer wireless device, which ipw3945 does not handle. That might explain why they are both in the repos right now.

raymano · 2007-07-27 03:43:43

Thanks. I guess I'll wait for a while before switching over.

quetzyg · 2007-07-27 12:40:27

peart wrote:

They are supposed to replace ipw3945 one day, when they reach maturity. I tried the iwl driver for a few days last week, and I suggest sticking with ipw for now. The new driver is still very "beta."
My 0.02.

The latest version (1.0.0) works like a charm for me. It can connect to protected (WPA2/TKIP) and unprotected networks, and the recovery from a suspend to ram is just awesome.

Btw, I'm running Linux 2.6.22.1.

brain0 · 2007-07-27 16:12:14

The latest version (1.0.0) works like a charm for me. It can connect to protected (WPA2/TKIP) and unprotected networks, and the recovery from a suspend to ram is just awesome.
Btw, I'm running Linux 2.6.22.1.

Have you ever tried switching from an encrypted AP to an unencrypted one and back? If you do that several times, the driver becomes unusable and you have to reload it (and sometimes not even that helps). I confirmed that with 0.0.42, but 1.0.0 has no changes to the actual code.

quetzyg · 2007-07-27 16:24:50

brain0 wrote:

The latest version (1.0.0) works like a charm for me. It can connect to protected (WPA2/TKIP) and unprotected networks, and the recovery from a suspend to ram is just awesome.
Btw, I'm running Linux 2.6.22.1.
Have you ever tried switching from an encrypted AP to an unencrypted one and back? If you do that several times, the driver becomes unusable and you have to reload it (and sometimes not even that helps). I confirmed that with 0.0.42, but 1.0.0 has no changes to the actual code.

I have no idea.

raymano · 2007-07-27 16:39:10

It also seems to have problems when connecting to a wireless router which does not broadcast its SSID.

Last edited by raymano (2007-07-27 16:39:26)

cpu · 2007-07-27 22:51:54

With ipw3945 I have random disconnects all the time, with iwlwifi no so far...

lloeki · 2007-07-27 22:59:37

stumbling upn this thread, I decided to finally really give iwlwifi a go (last time I tested it I was still under gentoo ). so far it works just totally fine no matter what I throw at it (WPA-PSK:TKIP+AES via wpa_sup, intense up/downloads, suspend), just like ipw3945 does (same perfs, although it seems to assoc+negociete wpa in no time, where ipw3945 it was taking ~1s).

now I will see how it holds in the long run.

Last edited by lloeki (2007-07-27 23:00:52)

quetzyg · 2007-07-27 23:09:17

And best of all, it doesn't need a regulatory daemon!

lloeki · 2007-07-27 23:24:49

to be 100% clear: it has a regulatory system, but not in daemon anymore, now it's in ucode.

btw, funny implementation they did, with two net ifaces:

wlan0     Link encap:Ethernet  HWaddr 00:18:*********
          inet addr:192.168.1.39  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:204646 errors:0 dropped:0 overruns:0 frame:0
          TX packets:142425 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:278436356 (265.5 Mb)  TX bytes:20338835 (19.3 Mb)

wmaster0  Link encap:UNSPEC  HWaddr 00-18-*********-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Last edited by lloeki (2007-07-27 23:25:04)

cpu · 2007-07-28 11:49:45

Transfered 6 GB data over samba and NO disconnect with iwlwifi !! It was impossible with ipw3945 ! I'm extremely happy !

lloeki · 2007-07-30 07:12:33

so far, with iwlwifi (compared to ipw3945):
- wifi led does not work
- performance a bit reduced (770kB/s -> 580kB/s)
- had two disconnects in two days. in dmesg:

iwl3945: Grabbing access while already held at line 873.

requires a rmmod && modprobe + ifplugd+wpa restart

nice progress compared to the first versions, which would panic the kernel , but I'm back to ipw3945 (because of last point)

Last edited by lloeki (2007-07-30 07:12:57)

daeltar · 2007-10-22 20:01:02

In my case it seems that iwl3945 solves most of the issues and no problems over. Like it much

Damnshock · 2007-10-22 20:57:38

I can't get iwl3945 to work with web wireless configs . I'll have to wait a bit more...

Arch Linux

#1 2007-07-26 22:19:49

ipw3945 wireless driver

#2 2007-07-27 01:30:01

Re: ipw3945 wireless driver

#3 2007-07-27 01:34:09

Re: ipw3945 wireless driver

#4 2007-07-27 03:43:43

Re: ipw3945 wireless driver

#5 2007-07-27 12:40:27

Re: ipw3945 wireless driver

#6 2007-07-27 16:12:14

Re: ipw3945 wireless driver

#7 2007-07-27 16:24:50

Re: ipw3945 wireless driver

#8 2007-07-27 16:39:10

Re: ipw3945 wireless driver

#9 2007-07-27 22:51:54

Re: ipw3945 wireless driver

#10 2007-07-27 22:59:37

Re: ipw3945 wireless driver

#11 2007-07-27 23:09:17

Re: ipw3945 wireless driver

#12 2007-07-27 23:24:49

Re: ipw3945 wireless driver

#13 2007-07-28 11:49:45

Re: ipw3945 wireless driver

#14 2007-07-30 07:12:33

Re: ipw3945 wireless driver

#15 2007-10-22 20:01:02

Re: ipw3945 wireless driver

#16 2007-10-22 20:57:38

Re: ipw3945 wireless driver

Board footer