Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
BAD EIP Value on Shutdown - happened after NorthEast Blackout.
- I have Redhat 9 installed and running just fine. My PC performed an unusual shutdown during the Blackout, i was unable to shutdown correctly.
- Now, the system boots fine. However when I ask it to shut down, I get the following Code: Bad EIP Value. This massage appears after it kills several procceses, after unmounting file system, after Halting System. THe systme hangs and I just shut it down or reboot.
I checked the log files for Boot and everything logs as successful
Under system log I get these unusual logs:
Aug 16 15:02:35 localhost gconfd (root-3809): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Aug 16 15:07:31 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:07:31 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 16 15:13:16 localhost kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 15:13:16 localhost kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb is my slave drive on the first ide channel...this is where I have my linux partitions.
I am unsure how to use badblocks but I did try fsck. I ran it in single user mode, unmounted hdb and then I did fsck /dev/hdb and it told me that the superblock did not recognize a valid ext2 partition or drive.
I also tried setting my bios to pio instead of dma.
I also tried switching cables and nothing has worked.
hopefully I can figure out how to use the badblocks command.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.