| View previous topic :: View next topic |
| Author |
Message |
TequilaTR
n00b
Joined: 01 Feb 2005
Posts: 68
|
 Posted: Wed Feb 13, 2008 7:55 am Post subject: Re: iwl4965agn |
 |
|
| pzasso wrote: |
10:00.0 Network controller: Intel Corporation Unknown device 4229 (rev 61)
|
I think it won't help with you real problem, but did you try using "update-pciids"? |
|
| Back to top |
|
 |
cipherus
Apprentice
Joined: 07 May 2004
Posts: 174
|
| Posted: Wed Feb 13, 2008 9:55 am Post subject: |
|
|
| Lawless wrote: |
Well, I went back to ipw3945 for the time being. Had to patch it to get it compiled with 2.4.24 but it's working for now until I have the time to look deeper into that problem... |
Patched drivers! Thanks for the idea, works great for me too now  |
|
| Back to top |
|
|
swimmer
Veteran
Joined: 15 Jul 2002
Posts: 1330
Location: Netherlands
|
| Posted: Wed Feb 13, 2008 12:25 pm Post subject: Re: iwl4965agn |
|
|
| pzasso wrote: | Has anybody had success at any level with getting the 4965agn adapter to connect at N speeds? I have had success with it connecting at G speeds and it is pretty reliable both with simple encryption at home and complex encryption at work. I went to a buddies house and tried to connect to his Netgear WNR834M wireless router, and although I connected for a moment, it ended up bringing his router to its knees, and the local lan was hosed as well. As soon as I shut down my NIC on my laptop, everything recovered on his network. I am not sure exactly what happened, but I did make it as far as to get a DHCP address from the wireless router before it died.
I am using an HP/Compaq 8710w Mobile workstation with the following device as shown by lspci. My understanding is that this is a wireless nic that can do N speeds.
10:00.0 Network controller: Intel Corporation Unknown device 4229 (rev 61)
Thanks
--Paul |
@Paul, I got it working with everything branch of the wireless-2.6.git sources from John Linville (http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=tree;h=everything;hb=everything) ... note that I did not reach 300Mb but at least 160Mb with a D-Link Dir-655 router.
HTH
swimmer |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Sun Feb 17, 2008 8:16 pm Post subject: |
|
|
anyone getting this with the recent version of iwlwifi?
| Code: |
wlan0: CTS protection disabled (BSSID=00:14:6c:ae:c5:38)
wlan0: CTS protection enabled (BSSID=00:14:6c:ae:c5:38)
|
|
|
| Back to top |
|
|
micro_mx
n00b
Joined: 11 Nov 2004
Posts: 29
|
| Posted: Wed Mar 19, 2008 5:12 am Post subject: |
|
|
wlan0: CTS protection disabled (BSSID=00:14:6c:ae:c5:3
wlan0: CTS protection enabled (BSSID=00:14:6c:ae:c5:38
Yes, im getting those messages xD
im using linux-2.6.24-gentoo-r3 (gentoo-sources) but wifi seems to work fine, including the led |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
| Posted: Thu Mar 20, 2008 9:21 pm Post subject: |
|
|
Hello,
I would like to upgrade my kernel up to the latest stable release, that is 2.6.24-r3 at the moment, but I also want to continue using the iwlwifi drivers included in portage. What should I do in order to be able to install them?
I have these problems (obviously), doing module-rebuild:
| Code: | * iwlwifi is included in 2.6.24, this ebuild is not guaranteed to
* build against the newer kernel. |
I guess I should remove the iwlwifi drivers included into the kernel, but I don't know how.
Thanks
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Sat Mar 22, 2008 4:52 pm Post subject: |
|
|
fbcyborg,
Install and compile your latest 2.6.24 kernel first. Then symlink /usr/src/linux to a kernel branch that didn't include iwlwifi and boot into that kernel. Then and only then emerge iwlwifi. Note you'll have to manually emerge packages listed by module-rebuild, except iwlwifi, when you boot with 2.6.24.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Sat Mar 22, 2008 5:53 pm Post subject: |
|
|
| Why using the iwlwifi package instead of the one inside the kernel ? |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Sun Mar 23, 2008 1:38 pm Post subject: |
|
|
Yeah, since I have upgraded to the kernel 2.6.24-Gentoo-r3, my wireless connection hang or even disconnect from time to time.
I never had this kind of problem with the old ipw3945 or even the iwlwifi. |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
|
| Back to top |
|
|
nyk
Guru
Joined: 28 Aug 2004
Posts: 527
Location: Bern (Switzerland)
|
| Posted: Tue Mar 25, 2008 9:34 am Post subject: |
|
|
| I can tell you that it's really worth to use IWL3945 instead of IPW3945, the wlan quality has drastically improved on my X60. With the old driver, I could not use the wlan where I work, now it works perfectly (70%)! |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
| Posted: Tue Mar 25, 2008 9:49 am Post subject: |
|
|
| nyk wrote: | | I can tell you that it's really worth to use IWL3945 instead of IPW3945, the wlan quality has drastically improved on my X60. With the old driver, I could not use the wlan where I work, now it works perfectly (70%)! |
Excuse me but, I didn't understand exactly what you mean. Anyway, ipw3945 it's not suggested anymore. iwlwifi driver is better even though it is not yet fully optimized. There's some bug they have to correct and other little things (e.g. the led). So, what do you prefer?
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered |
|
| Back to top |
|
|
nyk
Guru
Joined: 28 Aug 2004
Posts: 527
Location: Bern (Switzerland)
|
| Posted: Tue Mar 25, 2008 3:11 pm Post subject: |
|
|
I meant that I also think that the IWL is better!
But now I found out it really has some bugs. For example you can't turn it back on if you turn it off or if it looses the connection! |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
|
| Back to top |
|
|
mikedilger
n00b
Joined: 21 Nov 2004
Posts: 2
|
| Posted: Mon Mar 31, 2008 10:25 pm Post subject: Re: iwlwifi in 2.6.24 |
|
|
| chris.c.hogan wrote: |
I was excited to see the driver make it into 2.6.24. So I tried it out tonight. However, I'm not having any luck with it. It still fails while loading the default runlevel. However, it also fails after login with an error I've never seen before:
| Code: | /etc/init.d/net.wlan0 start
* Starting wlan0
* Wireless radio has been killed for interface wlan0 [ !! ]
|
Dmesg shows:
| Quote: |
[ 127.849731] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 128.401880] iwl3945: Error sending REPLY_RXON: time out after 500ms.
[ 128.401889] iwl3945: Error setting new configuration (-110).
[ 128.901096] iwl3945: Error sending REPLY_RXON: time out after 500ms.
[ 128.901105] iwl3945: Error setting new configuration (-110).
[ 129.400325] iwl3945: Error sending REPLY_RXON: time out after 500ms.
[ 129.400331] iwl3945: Error setting new configuration (-110).
[ 129.400336] wlan0: Initial auth_alg=0
[ 129.400342] wlan0: authenticate with AP 00:0d:3a:2a:7a:f3
|
As I said, works alright under 2.6.22, doesn't under 2.6.24. Any ideas? |
I get this same issue, except with iwl4965. Works for me on 2.6.23, but not 2.6.24. I gave up on this back in January. Now I'm trying again more earnestly (4 hours so far) with 2.6.24-r5. Still no luck. As soon as I run /etc/init.d/net.wlan0, the rf_kill gets set on, and the driver fails to work:
| Code: |
# /etc/init.d/wlan0 start
* Starting wlan0
* Wireless radio has been killed for interface wlan0
|
I can manually reset rf_kill software kill to 0, but it doesn't help anything:
| Code: |
# cat /sys/bus/pci/drivers/iwl4965/0000\:03\:00.0/rf_kill
1
# echo 0 > /sys/bus/pci/drivers/iwl4965/0000\:03\:00.0/rf_kill
# cat /sys/bus/pci/drivers/iwl4965/0000\:03\:00.0/rf_kill
0
# /etc/init.d/wlan0 start
* Starting wlan0
* Wireless radio has been killed for interface wlan0
# cat /sys/bus/pci/drivers/iwl4965/0000\:03\:00.0/rf_kill
1
|
I have also rmmod, then modprobe again, without any change to its behavior.
| Code: |
iwl4965: Error sending REPLY_RXON: time out after 500ms.
iwl4965: Error setting new configuration (-110).
iwl4965: Error sending REPLY_ADD_STA: time out after 500ms.
iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: time out after 500ms.
iwl4965: Error sending REPLY_RXON: time out after 500ms.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:1b:**:**:**:**:** [EDITED]
iwl4965: Error sending REPLY_RXON: time out after 500ms.
iwl4965: Error setting new configuration (-110).
iwl4965: Error sending REPLY_RXON: time out after 500ms.
iwl4965: Error setting new configuration (-110).
iwl4965: Error sending REPLY_STATISTICS_CMD: time out after 500ms.
|
The hardware switch is ON and works fine if I reboot into 2.6.23 without touching it.
I'm trying this with gentoo-sources-2.6.24-r5 and /lib/firmware/iwlwifi-4965-1.ucode (iwl4965-ucode-4.44.1.20) |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
| Posted: Tue Apr 01, 2008 9:31 pm Post subject: |
|
|
| VinzC wrote: | fbcyborg,
Install and compile your latest 2.6.24 kernel first. Then symlink /usr/src/linux to a kernel branch that didn't include iwlwifi and boot into that kernel. Then and only then emerge iwlwifi. Note you'll have to manually emerge packages listed by module-rebuild, except iwlwifi, when you boot with 2.6.24. |
Hello again, and Thank you for your suggestion.
I have a question: you said Then symlink /usr/src/linux to a kernel branch that didn't include iwlwifi and boot into that kernel.Then and only then emerge iwlwifi. Ok but if I do in that way, drivers will be installed in the other kernel module directory. Isn't it?
Shall I manually copy the drivers in the 2.6.24 kernel module directory?
Is there a simple and fast way to do that?
It's very annoying I can't emerge iwlwifi drivers as well as I can do for audio or video drivers. The iwlwifi driver in the kernel are not good for me. The card often disconnects from the AP.
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered |
|
| Back to top |
|
|
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Wed Apr 02, 2008 8:37 am Post subject: |
|
|
| fbcyborg wrote: | | I have a question: you said Then symlink /usr/src/linux to a kernel branch that didn't include iwlwifi and boot into that kernel.Then and only then emerge iwlwifi. Ok but if I do in that way, drivers will be installed in the other kernel module directory. Isn't it? |
Sure. Since 2.6.24 now includes iwlwifi there's no more reasons to install them from portage with that kernel level. If you emerge iwlwifi while running 2.6.24 and above you'll probably (for I never did that) get a warning or error message.
Anyways, the driver from portage and the one that's included in the 2.6.24 tree is exactly the same. I see no obvious reason for preferring using portage's to the kernel's built-in.
As per my own experience with ipwXXXX packages, I prefer using wireless drivers from the kernel tree. The only module that I use as an exception is KVM.
You might try disabling the iwlwifi modules in your kernel configuration and try emerging the drivers from portage.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
| Posted: Wed Apr 02, 2008 10:41 am Post subject: |
|
|
| VinzC wrote: |
Sure. Since 2.6.24 now includes iwlwifi there's no more reasons to install them from portage with that kernel level. If you emerge iwlwifi while running 2.6.24 and above you'll probably (for I never did that) get a warning or error message.
Anyways, the driver from portage and the one that's included in the 2.6.24 tree is exactly the same. I see no obvious reason for preferring using portage's to the kernel's built-in. |
Ah! Ok, I tought they were two different versions. I tought the recent one was in portage. Anyway, I'll use the drivers into the kernel tree. | VinzC wrote: |
As per my own experience with ipwXXXX packages, I prefer using wireless drivers from the kernel tree. |
Me too actually. But, sometime the driver fails and (as I told before) the card disassociates from the Access Point. | VinzC wrote: | The only module that I use as an exception is KVM.
You might try disabling the iwlwifi modules in your kernel configuration and try emerging the drivers from portage. |
Thank you.
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed Apr 02, 2008 11:45 am Post subject: |
|
|
| fbcyborg wrote: | The iwlwifi drivers, whose are included into the kernel, are very bad. My card often disassociate from the AP, making me mad!!!
I NEED to use the iwlwifi drivers, included in portage, how to do that? |
My problem seems to be gone away with the kernel 2.6.24-Gentoo-r4... |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
|
| Back to top |
|
|
padan
n00b
Joined: 21 Feb 2004
Posts: 34
|
| Posted: Thu Apr 03, 2008 1:41 pm Post subject: |
|
|
Maybe I have gone crazy...
I just did a reinstall on my laptop and after reading that we are supposed to use built-in support for the 3945 card I searched around in my kernel source for the two main things to enable:
networking -> wireless -> mac80211
device drivers -> network device support -> wireless lan -> intel wifi drivers
and they are not present in either the gentoo sources (2.6.24-r4) or the vanilla sources. They do not appear in a freshly generated .config file either. What is going on here?
EDIT: I had missed enabled incomplete drivers in the general setup...
_________________
-- padan
"But you know what users are like - couldn't find the space bar if their stomach didn't roll into it." - BOFH 1998 |
|
| Back to top |
|
|
fbcyborg
Advocate
Joined: 16 Oct 2005
Posts: 3056
Location: ROMA
|
| Posted: Thu Apr 03, 2008 1:51 pm Post subject: |
|
|
| padan wrote: | Maybe I have gone crazy...
I just did a reinstall on my laptop and after reading that we are supposed to use built-in support for the 3945 card I searched around in my kernel source for the two main things to enable:
networking -> wireless -> mac80211
device drivers -> network device support -> wireless lan -> intel wifi drivers
and they are not present in either the gentoo sources (2.6.24-r4) or the vanilla sources. They do not appear in a freshly generated .config file either. What is going on here?
EDIT: I had missed enabled incomplete drivers in the general setup... |
Just a simple question: have you already read this? Maybe there's some dependency required to be selected.
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered |
|
| Back to top |
|
|
cyberdaniel
n00b
Joined: 09 Apr 2008
Posts: 1
|
| Posted: Wed Apr 09, 2008 11:42 pm Post subject: Re: iwlwifi in 2.6.24 |
|
|
| mikedilger wrote: |
I get this same issue, except with iwl4965. Works for me on 2.6.23, but not 2.6.24. I gave up on this back in January. Now I'm trying again more earnestly (4 hours so far) with 2.6.24-r5. Still no luck. As soon as I run /etc/init.d/net.wlan0, the rf_kill gets set on, and the driver fails to work:
| Code: |
# /etc/init.d/wlan0 start
* Starting wlan0
* Wireless radio has been killed for interface wlan0
|
I can manually reset rf_kill software kill to 0, but it doesn't help anything:
|
I get that as well, the message can be a bit confusing. To get it working again do:
| Code: |
ifconfig wlan0 up
iwconfig wlan0 txpower on
/etc/init.d/net.wlan0 start
|
Make sure you have them in that order. Also make sure you use /etc/init.d/net.wlan0 start and not restart since restart will turn off your wireless first.
In case the interface is up but not associated run /etc/init.d/net.wlan0 stop first then the above steps.
Alternatively, to automate, add the following code to /etc/conf.d/net and you can simply start/restart your interface normally without any additional steps.
| Code: |
preup() {
if [ ${IFACE} == "wlan0" ]; then
ifconfig wlan0 up
iwconfig wlan0 txpower on
fi
}
|
|
|
| Back to top |
|
|
|
Kernel & Hardware
