[arch-general] Dropping ipw3945 from core
After I discovered that my problems with the new Intel driver where related to dhclient and fixed the bug, I am now successfully using iwl3945 on my machine. It seems to be working perfectly, so I am considering dropping ipw3945 from core/support with the 2.6.25 release (so there will be no new package versions after ipw3945-1.2.2-8). This is intended as a warning, but also as a question: Is there anyone who cannot use iwl3945 instead of ipw3945?
On Mon, 31 Mar 2008 13:18:27 +0200 Thomas Bächler <thomas@archlinux.org> wrote:
After I discovered that my problems with the new Intel driver where related to dhclient and fixed the bug, I am now successfully using iwl3945 on my machine.
It seems to be working perfectly, so I am considering dropping ipw3945 from core/support with the 2.6.25 release (so there will be no new package versions after ipw3945-1.2.2-8). This is intended as a warning, but also as a question: Is there anyone who cannot use iwl3945 instead of ipw3945?
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945. Cheers, Sergey
Sergey Manucharian wrote:
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945.
Exactly the same here. kr Michael
Michael Schaefer schrieb:
Sergey Manucharian wrote:
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945.
Exactly the same here.
kr Michael
The module is installed by default with (arch-)kernel 2.6.24 and newer. Did you guys install the firmware?
On Mon, 31 Mar 2008 14:17:45 +0200 Thomas Bächler <thomas@archlinux.org> wrote:
Michael Schaefer schrieb:
Sergey Manucharian wrote:
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945.
Exactly the same here.
kr Michael
The module is installed by default with (arch-)kernel 2.6.24 and newer. Did you guys install the firmware?
Most probably that was the problem, I cannot check it right now. But the think that the installer put "iwl3945" into MODULES line of rc.conf is disappointing people - they think that everything is already done... Anyway, thanks for the hint! Cheers, Sergey
2008/3/31, Sergey Manucharian <sergey.manucharian@rmico.com>:
On Mon, 31 Mar 2008 14:17:45 +0200
Thomas Bächler <thomas@archlinux.org> wrote:
Michael Schaefer schrieb:
Sergey Manucharian wrote:
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945.
Exactly the same here.
kr Michael
The module is installed by default with (arch-)kernel 2.6.24 and newer. Did you guys install the firmware?
Most probably that was the problem, I cannot check it right now. But the think that the installer put "iwl3945" into MODULES line of rc.conf is disappointing people - they think that everything is already done... Anyway, thanks for the hint!
Didn't installer show messages abut firmware/licenses/etc. during boot? This had to bring users' attention. -- Roman Kyrylych (Роман Кирилич)
On Mon, Mar 31, 2008 at 7:05 PM, Michael Schaefer <archlinux.org@micele.de> wrote:
Sergey Manucharian wrote:
Recently I was installing Archlinux on a notebook and the network was working fine with iwl3945 during the installation, but after reboot it couldn't find the module. Since I had no time to investigate this I've just switched to ipw3945.
Exactly the same here.
While the module is included in the kernel, you still have to install the firmware. http://archlinux.org/packages/search/?q=iwlwifi
Thomas Bächler wrote:
After I discovered that my problems with the new Intel driver where related to dhclient and fixed the bug, I am now successfully using iwl3945 on my machine.
It seems to be working perfectly, so I am considering dropping ipw3945 from core/support with the 2.6.25 release (so there will be no new package versions after ipw3945-1.2.2-8). This is intended as a warning, but also as a question: Is there anyone who cannot use iwl3945 instead of ipw3945?
I can use iwl3945 but the radio led on my acer laptop doesn't work with it, where it does with ipw3945. Not a big issue but it's nice to see if wireless is up at a glance. Hans.
Hans Janssen wrote:
I can use iwl3945 but the radio led on my acer laptop doesn't work with it, where it does with ipw3945. Not a big issue but it's nice to see if wireless is up at a glance.
Gave it a second try and works fine for me now. But i have the same issue with the non working wireless led. any solution for this? would be nice to see if wireless is up or not... btw: did anyone bring kismet up and running with iwl? with ipw it wasn't a problem. with iwl kismet crys for "unknown source iwl3945" while starting and craches... kr Michael
Michael Schaefer wrote:
Gave it a second try and works fine for me now. But i have the same issue with the non working wireless led. any solution for this? would be nice to see if wireless is up or not...
Hey, we know the wireless led doesn't work, it has always been said so! There is no need to repeat 10 times. And I personally couldn't even notice it, I don't see what's so critical about it. You find out whether the net is working or not the second you try to access something. And when it doesn't work and you have doubts, a simple iwconfig usually helps. Anyway, the support will be added, just be patient. http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1209#c59 PS: this mail isn't aimed at you in particular, I just wanted the "led doesn't work" messages to stop :)
On Mon, Mar 31, 2008 at 07:12:40PM +0200, Xavier wrote:
Michael Schaefer wrote:
Gave it a second try and works fine for me now. But i have the same issue with the non working wireless led. any solution for this? would be nice to see if wireless is up or not...
Hey, we know the wireless led doesn't work, it has always been said so! There is no need to repeat 10 times. And I personally couldn't even notice it, I don't see what's so critical about it. You find out whether the net is working or not the second you try to access something. And when it doesn't work and you have doubts, a simple iwconfig usually helps.
Anyway, the support will be added, just be patient. http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1209#c59
PS: this mail isn't aimed at you in particular, I just wanted the "led doesn't work" messages to stop :)
Coincidentially, my LED doesn't work either. But the patch was added to the git tree three days ago: http://git.kernel.org/?p=linux/kernel/git/rchatre/iwlwifi-2.6.git;a=commit;h... So I'm cool with killing ipw, no more userspace daemon, yay! -S
Xavier wrote:
Hey, we know the wireless led doesn't work, it has always been said so! There is no need to repeat 10 times. And I personally couldn't even notice it, I don't see what's so critical about it. You find out whether the net is working or not the second you try to access something. And when it doesn't work and you have doubts, a simple iwconfig usually helps.
well, this was the second 'led doesn't work'-post in this thread. don't see the issue. furthermore i tried iwl first time today - sorry for not searching the hole net if someone else mentioned the non working led before ;) please don't take it personal, that i would like to have my hardware working the way it's supposed to..didn't know i have explain myself cause i would like to have a working led insetad of using iwconfig or whatever. there is always a workaround..
PS: this mail isn't aimed at you in particular, I just wanted the "led doesn't work" messages to stop :)
well.. ok. but i think there is nothing bad in just telling about the differences when changing from ipw to iwl. this was the initial intention of this thread i guess. anyhow there was a second question (about kismet), maybe this gives my post a right to exist? kr Michael
Hans Janssen wrote:
I can use iwl3945 but the radio led on my acer laptop doesn't work with it, where it does with ipw3945. Not a big issue but it's nice to see if wireless is up at a glance.
Sane think here on my Thinkpad. Wireless works good but without the led.
Hans Janssen schrieb:
I can use iwl3945 but the radio led on my acer laptop doesn't work with it, where it does with ipw3945. Not a big issue but it's nice to see if wireless is up at a glance.
Hans.
As I already said on the BBS, the LED is not implemented yet. IIRC, it will be in the upcoming 2.6.25.
Thomas Bächler wrote:
Is there anyone who cannot use iwl3945 instead of ipw3945?
I was having various problems with getting iwl3945 to work. Most of the times I wasn't able to associate to any network before I run 'iwlist scan' manually. Also, when I finally connected, I got disconnected every couple of minutes. Activity LED is missing as well.
Thomas, On Mar 31 13:18, Thomas Bächler wrote:
It seems to be working perfectly, so I am considering dropping ipw3945 from core/support with the 2.6.25 release (so there will be no new package versions after ipw3945-1.2.2-8). This is intended as a warning, but also as a question: Is there anyone who cannot use iwl3945 instead of ipw3945?
Instead of removing ipw3945 entirely, could you place the last version (1.2.2-8) in extra or community? Also, once you do (re)move the package will you add a replaces=('ipw3945') to the iwlwifi PKGBUILD? Sincerely, -- Antony Jepson / <antonyat@gmail.com> / GPG Key: 0xFA10ED80
participants (11)
-
Antony Jepson
-
Emmanuel Benisty
-
Hans Janssen
-
Jakub Schmidtke
-
lists＠roothausen.de
-
Michael Schaefer
-
Roman Kyrylych
-
Sergey Manucharian
-
Simo Leone
-
Thomas Bächler
-
Xavier