You are not logged in.
.. Very disappointed that this major issue made it into core..
You are not alone
This seems to be a frequent and very annoying occurrence in Arch. I assume it has something to do with the huge number of different hardware combinations that are out there ... but I too find it troubling (and bordering on irresponsible) that the powers in charge permit such things to enter into core.
Is it really that necessary to rush "cutting edge" packages into core? IMHO it would be much more responsible and helpful for the public image of Arch to keep these things out of core until they are really "ripe." Those folks wanting the "latest and greatest" still have access to it (though not from core), while those "just" interested in using a really fast, trim and generally super OS -- which, of course, Arch is -- will not have to feel like laboratory test animals
Just my 2 Eurocents worth
Best regards to all Arch-Lovers and I wish everyone a successful and healthy 2010,
-- Dr.U
Offline
A number of Ralink cards are now pretty messed up with this kernel. Disabling power saving helps with some issues. Try this is root and see if the script stabilizes:
iwconfig <your_wireless_interface> power off
Thanks for the tip, skottish!! This works for my MSI notebook with a RaLink RT2561/RT61 rev B 802.11g network controller.
But I still stand by my comments in my previous post. Good luck, everyone else.
Regards,
-- Dr.U
Offline
You all use x86_64 archlinux?
No, I'm on x86.
Last edited by dfelicia (2010-01-02 14:39:56)
Offline
I'm using x86_64 archlinux, but mrutter said that the problem is present in 32 bits arch too, at least that's what i understood.
I'm glad it isn't only me. I just (after this problem came up on my 32bit install) did a clean install to move to the 64bit version (what the hell) and with the dhcpcd version and kernel (2.6.30) that was came with the core ISO everything works fine. But after the systems upgrade I got the same behaviour. Unfortunately I didn't think to try to isolate the problem by upgrading dhcpcd first.
.....
Offline
I'm using x86_64 archlinux, but mrutter said that the problem is present in 32 bits arch too, at least that's what i understood.
mrutter wrote:I'm glad it isn't only me. I just (after this problem came up on my 32bit install) did a clean install to move to the 64bit version (what the hell) and with the dhcpcd version and kernel (2.6.30) that was came with the core ISO everything works fine. But after the systems upgrade I got the same behaviour. Unfortunately I didn't think to try to isolate the problem by upgrading dhcpcd first.
.....
You understood correctly.
Offline
Although some say that this applies to Intel cards as well (4965AG, specifically), I suffer no such problem. The following is on a ThinkPad T61p, Arch x86, fully updated (partial output):
$ pacman -Qs kernel
local/kernel-headers 2.6.32-1 (base)
Kernel headers sanitized for use in userspace
local/kernel26 2.6.32.2-2 (base)
The Linux Kernel and modules
local/kernel26-firmware 2.6.32.2-2 (base)
The included firmware files of the Linux Kernel
$ pacman -Qs intel
local/iwlwifi-4965-ucode 228.61.2.24-2
Intel wireless firmware for IPW4965 (iwlwifi driver)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Yeah, from what i heard, all the IBM laptops haven't been affected with that problem.
All the other have.
Offline
So, it is not an issue specific to any wireless hardware. It breaks something else, which in turn breaks wireless.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
I've got also some issues with my wireless connection with the upgrade of kernel to 2.6.32
I'm using x86_64 archlinux and my wireless card is a Ralink (rt61pi driver). I use WPA for my wireless network, but I've tested it with no security and the issues are the same.
To be more precise, I can connect to my network, but Internet connections are really slow (about 1 mn to load Google homepage). I've also got a Debian distribution (but on another computer) with kernel 2.6.32 and it works fine (even if it's a little bit slow).
Offline
Any idea when an update will get pushed to fix this?
Offline
@shenga: From what I've observed, this is also system-dependent. IBM/Lenovo laptops are not effected by any of these regressions, for example.
@jugs: There are already patches for some of these issues (search the forums & google), but I'd stick with 2.6.31 if that works for you.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Has anyone tried to obtain a local ip while having kernel 2.6.32 ?
Offline
@shenga: From what I've observed, this is also system-dependent. IBM/Lenovo laptops are not effected by any of these regressions, for example.
That may come from the wireless card also. My laptop one is a Intel 4965. (same as dcc24 I think)
I've made some more tests : ping works fine (about 45-60 ms from Google and some other websites), but pacman is really slow.
About browsers, I noticed a thing : I use a Netvibes page as homepage and Firefox wasn't able to load it. I tried it with Chromium and it worked (quite slowly, but it worked), and after that, it worked also in Firefox. I was thinking the problem could come from DNS resolution and some cache makes Firefox get it well after Chromium did ?
Offline
Hey guys!!! good news!!! I just updated the kernel to 2.6.32.3-1 and the issue seems to have been eliminated, i tried 4 times to use my wifi script and then reboot, and within all of them the conection was succesfully stablished. Now I can enjoy the led of my wireless card changing from blue to ambar very fast (not always, depends on the traffic, i guess) when the card is working. No problems with the download speed or the pign time. I have arch64, atheros ar5001.
... Well, now the problem is other, this kernel makes my Splashy theme to dissapear after udev event... but that is for another thread I guess
Thanks for the comments!!!
Offline
Hey guys!!! good news!!! I just updated the kernel to 2.6.32.3-1 and the issue seems to have been eliminated, i tried 4 times to use my wifi script and then reboot, and within all of them the conection was succesfully stablished. Now I can enjoy the led of my wireless card changing from blue to ambar very fast (not always, depends on the traffic, i guess) when the card is working. No problems with the download speed or the pign time. I have arch64, atheros ar5001.
... Well, now the problem is other, this kernel makes my Splashy theme to dissapear after udev event... but that is for another thread I guess
Thanks for the comments!!!
As OP I cannot confirm that this is the case. I upgraded to 2.6.32.3-1 and encountered the same problem, and a revert back to the newest 2.6.31 package resolved the problem.
Last edited by mrutter (2010-01-10 15:31:58)
Offline