ok, found it. On the sixth I did #make menuconfig && make modules_install and rebooted without any problem, everything worked as before. But I neglected to copy over the new kernel. All the fresh modules seeemed to get along fine with the stale kernel for an entire week so it never occured to me there was a problem till I tried to go mobile and the wifi module gagged. I wonder why that one was singled out.
So, crisis passed. Well, until I go mobile again and try to connect. Thanks for your interest mw On 10/13/09, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Tue, Oct 13, 2009 at 4:13 PM, Maxim Wexler <maxim.wex...@gmail.com> > wrote: >> Hi group, >> >> Emergency here. After my eee pc boots I log in and enter '#ifconfig >> wlan0 up' as usual to take advantage of the free wifi at the coffee >> shop. Then, just before I enter the next command, the kernel panics >> and the console freezes. The top line of hexidecimal barf reads: >> >> ath5k_tasklet_rx40x1fd/0539[ath5k] >> >> and ends with: >> >> Kernel panic -- not syncing: fatal exception in interrupt >> >> I'm wracking my brains trying to figure out what I did or neglected to >> do prior to this but am drawing a blank. >> >> Running 2.6.29-r5. Never had this problem before. '$cat >> /proc/acpi/net/wireless' indicates that wlan0 is configured. >> >> Anybody have any ideas? >> >> Maxim > > Maybe you can try to use newer drivers; if you don't want to update > the entire kernel you can build just the latest wireless drivers from: > http://linuxwireless.org/en/users/Download/stable/ > >
