Update from 2.6.25.4-30 to 2.6.25.6-55.fc9.x86_64 causes kernel panic on x61
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Update from 2.6.25.4-30 to 2.6.25.6-55.fc9.x86_64 causes kernel panic on x61
Hi,
I've used the automatic update to migrate from a Fedora 9 kernel 2.6.25.4-30 to 2.6.25.6-55.fc9.x86_64.
My machine, a Lenovo X61 which worked OK with the old kernel, now boots fine, but after the first few seconds of running Gnome as a user the machine has a kernel panic (frozen, Caps lock blinking).
The problem is entirely reproducible, but I was not able to find any relevant log messages in /var/log/messages. Where else to look?
As far as I can tell there's no previous post on the subject matter. Any help would be appreciated.
I have similar problem with 2.6.25.6-55.fc9.x86_64 kernel after upgrading from 2.6.25.4-30.fc9.x86_64. It is booting normally, but after login (in graphical mode) when wireless card try to connect (managed by Network Manager) to network everything is frozen and Caps Lock start blinking.
My wireless card is Intel Corporation PRO/Wireless 4965 AG.
with 2.6.25.4-30.fc9.x86_64 kernel everything works fine.
I have similar problem with 2.6.25.6-55.fc9.x86_64 kernel after upgrading from 2.6.25.4-30.fc9.x86_64. It is booting normally, but after login (in graphical mode) when wireless card try to connect (managed by Network Manager) to network everything is frozen and Caps Lock start blinking.
My wireless card is Intel Corporation PRO/Wireless 4965 AG.
with 2.6.25.4-30.fc9.x86_64 kernel everything works fine.
Thank you for any help and suggestion.
Armen
I have the exact same card with the exact same problem.
I have the same problem on my ASUS a6km laptop with fedora 9. The older kernel 4-30 works fine (including the wireless), while the newer 6-55 immediately freezes into a kernel panic
However, I have a different wireless card, to quote my lscpi entry:
Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
I am using NetworkManager and used fw-cutter (as opposed to ndiswrapper) to get the card working.
Just thought I'd mention this -the problem is apparently not limited to intel wireless cards. And to emphasize this is not an isolated issue, but something more users are experiencing.
This problem has been reported by many users. Indeed, it seems to be related to the wireless card drivers. This thread on the Fedora forum suggests to install a patched kernel built from one of the official Fedora packagers. Anyway, I'd suggest to stick with the old kernel until a further new version is released.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.