dsleaf67
Member
I have a airlink nano wifi that works fine in old kernel but not in the new kernel. using superzaxxon 1.5b4. Not sure if this is known or tried by anyone else. Will post dmesg later if needed.
Yup, several people have reported that (myself included)--no word from the devs yet on what they think might be causing it.In Beta 4 I'm getting occasional lockups of the whole OS when activating WIFI.
Yeah do 'lsmod' on the old kernel, dmesg on both new and old and post the output somewhere.I have a airlink nano wifi that works fine in old kernel but not in the new kernel. using superzaxxon 1.5b4. Not sure if this is known or tried by anyone else. Will post dmesg later if needed.
Never managed to reproduce it, and nobody described how to reproduce it reliably.Yup, several people have reported that (myself included)--no word from the devs yet on what they think might be causing it.In Beta 4 I'm getting occasional lockups of the whole OS when activating WIFI.
Done. Just added /lib/boot/ in front of uImage in autoboot.txt and now the new kernel boot. Great, thanks.The new kernel is in /lib/boot/ you should point (auto)boot.txt to it. Latest SD installer is supposed to use later kernel now, but I haven't verified that.
on the SD in /boot correct? Because obviously the uimage on the root of the SD card (fat partition is the 3.2 kernel).
[EDIT] I was wrong, there is no /boot on the SD card ext partition. So where do I look for the 2.6 kernel?
77:~$ sudo find / -iname mcs*
/lib/modules/3.2.16-00257-g22711aa/kernel/drivers/net/usb/mcs7830.ko
/lib/modules/2.6.27.57-omap1/kernel/drivers/net/usb/mcs7830.ko
/usr/share/vim/vim72/compiler/mcs.vim
find: ftsfind.c:477: consider_visiting: Assertion `ent->fts_info ==
11 || state.type != 0' failed.
Aborted
That's usually the first thing that's suggested.Check you routers men!
Ouch, those are terribleAnyone else getting similar, worse, or better averages?
That's usually the first thing that's suggested.Check you routers men!
Have you tried eliminating other Wifi sources? I'm wondering there could be interference from other sources.
Have you tried disabling power saving features? In a terminal type "sudo iwconfig wlan0 power off".yeah there's a real possibility. I assume the Pandora's wifi is real low? I will try chaging the channels again too. But TKIP was the real blocker up to now!
Have you tried disabling power saving features? In a terminal type "sudo iwconfig wlan0 power off".yeah there's a real possibility. I assume the Pandora's wifi is real low? I will try chaging the channels again too. But TKIP was the real blocker up to now!