Intel WiFi 5300, kernel : kernel 2.6.32-rc7(any) wpa_supplicant-0.6.9 with networkmanager-0.7.1-r6, or any other ebuild in the portage, pinging google.com after a while gives me an error: ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available However, if I do this: stop NetworkManager, ifconfig wlan0 down ifconfig wlan0 up iwconfig wlan0 AP XX:XX:XX:XX:XX:XX dhclient wlan0 and leave pinging in terminal, the error never happens. I modified wpa_supplicants (scan_helpers.c) wpa_scan_result_compar function to favour 5GHz APs by inserting following code. I believe there is nothing bad in this code, favouring 5GHz N networks over 2.4GHz N networks. if(wa->level && wb->level && wa->freq && wb->freq && abs(wb->freq - wa->freq) > 2000 ) { return (wb->freq-wa->freq); } Reproducible: Always Steps to Reproduce: 1.connect to wifi network 2.start pingig 3.error hapens
I've heard that this problem might by caused by faulty hardware or that resetting the BIOS helps. Does this problem also occur with older Kernels? You're using an RC-Kernel which we don't support.
(In reply to comment #1) > I've heard that this problem might by caused by faulty hardware or that > resetting the BIOS helps. > > Does this problem also occur with older Kernels? You're using an RC-Kernel > which we don't support. > I used some stable kernels (gentoo-sources) in portage - the same thing. What can I do about bios and my hardware - nothing. But I really doubt that it is the HW or BIOS as the same machine can ping anytime in Windows. I reported upstream here > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2129 those shitheads are useless :) I mean there are bunch of people struggling just like me, and they think it is with specific AP type...what a load of shitheads @ intel....
(In reply to comment #2) > I reported upstream here > > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2129 > > those shitheads are useless :) I mean there are bunch of people struggling just > like me, and they think it is with specific AP type...what a load of shitheads > @ intel.... Honestly, how is that kind of language going to help?
Indeed, it won't help them at all. In fact nothing is going to help them. I have to say this, reported at the bug report also, I had to disable CONFIG_IPV6 in the kernel for the bug to go. Interesting, right ? it never happened on the wired interface, however on wifi with iwlfifi you never get a solid network. However if I set it on again guess what happens ? Nothing changed - same bug. Anyway, I am not able to test those settings any more, so I say it is up to "UPSTREAM", hence the new status. thanks, Aidar
Just for someones information, I'm getting the same error on a wired network second NIC. Both NIC's are on-board. When I stop and start the first NIC, the second NIC starts working again.
