FedoraThis forum is for the discussion of the Fedora Project.
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.
Same thing just happened to me when updating FC1 to FC2 using yum. The kernel is 2.6.10-1.8_FC2. The board is a MSI-6565 (Intel E7205) with a DupliDisk1 for hardware RAID1.
I managed to boot into the new kernel by tweaking the grub kernel boot parameters at the grub boot screen to add "ide=nodma" (no quotes) to the linux line and making sure that /etc/sysconfig/harddisks had USE_DMA=0.
Can you let me know what hardware you are using? I think my issue is a conflict between the board and the DD1.
I have not been able to boot with the new kernel's that are being distributed with Fedora Core 3. FC3 works just fine with 2.6.9-681 inclusive but fails with the following message for all subsequent kernel's.
Kernel panic - not syncing: drivers/ide/pci/piix.c:232: spin_lock(drivers/ideide.c:c036e408) already locked by drivers/ide/ide-iops.c/1222
The above fix seems to work. My question is what changed and why is it important? My drives are new enough, both Western Digital Caviar's (160GB and 200GB) so they should be supported. Why would this break between kernel releases?
Originally posted by JordanH Has anyone else reported this yet?
I haven't bugzilla'd it yet, but there may already be some related ones there. The system I run it on is at a different location, and a production machine so I can't easily test new ideas or provide the type of info a bugzilla would require. Someone should make sure it's known in the normal channels.