-   Linux - Newbie (
-   -   Switching from onboard video to PCI in BIOS causing Debian to give boot problems (

Gigue 03-27-2011 08:06 PM

Switching from onboard video to PCI in BIOS causing Debian to give boot problems
Hello all, this is my first post ever, I usually try my hardest to research the problem and always find a solution, but in this case I'm stumped. Essentially, I have an older Compaq that I am setting up to act as a low grade "practice" web server. I have a video card I wish to install just to have a better quality picture on my largish display.
The video card is a Radeon 9200. When it sits in the computer and I'm running normally with the onboard, its recognized and everything about it seems fine. Then when I switch over to PCI in the bios and fire it up, I get the boot menu, then it starts to load and hangs with various results different times. The first few times, it would hang after a series of lines that said something to the effect of "... [SDA1] deleted INODE at xxxxxxxxxxxx" and above that "no INITTAB found". I read a suggestion somewhere to add "blacklist agpgart" and "blacklist intel_agp" to blacklist.conf. I did so, and upon reboot I know longer got a bunch of boot text culminating in the aforementioned "deleted inodes" jazz, but instead a simple prompt:

INIT: Entering run level 2

Debian GNU/Linux 6.0 (None) tty1

(none) login: root

xx.xxxxxxxxxx EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced xxxxxxxxxxxxxxxxxxxx

Debian GNU/Linux 6.0 (None) tty1

(none) login:

... What this could have to do with switching from onboard to PCI I have no idea (which is why I'm here :) )

Upon removing the blacklist additions and rebooting, I did not end up with my original boot output that I first described as one might expect, but still back at the one just described. Yet another reboot yielded a different variation:

loading, please wait...
INIT: version 2.88 booting
xxxxxxxxx Ext3-fs error (device sda1): ext3_lookup: deleted INODE referenced xxxxxxxxxxxxxxxx

xxxxxxxxx Ext3-fs error (device sda1): ext3_lookup: deleted INODE referenced xxxxxxxxxxxxxxxx

INIT: no inittab file found

Enter runlevel: 3
INIT: entering runlevel: 3
INIT: no more processes left in this runlevel
_ (<--- unresponsive blinking cursor)

... Like I said, different restarts yield different results. But if I switch over back to onboard everything disappears and its smooth sailing. It might be of interest that when I initially installed Debian, the installer constantly denied me at the CD-ROM detecting and mounting stage. It would say either that my CD did not contain a valid release file, and upon a CD rom diagnostic it basically said it couldn't use my drive. I spent hours and hours, burning new disks, using different installs (net based, DVD, CD), checking MD5, and swapping out different drives. No matter what, it would tell me my CD didnt have a valid release file. This whole time, my monitor was plugged into my PCI video card, where it had been left when I switched the computer over from windows. For whatever reason I switched the monitor over to onboard and was shocked to find that the next time it booted, the installer did its autorun and sailed right on through to the rest of the install. Everything was fine after that.
What is going on? Why did having my monitor plugged into the PCI slot make the installer say my release file wasnt valid. Why is it making me hang on boot with these seemingly unrelated messages. Needless to say I'm a little intrigued, I'd be very interested to hear any ideas. Thanks for your time reading this long post, but I thought I'd be thorough in explanation.

JZL240I-U 03-28-2011 06:26 AM

Never heard anything like this. Now for my story: When I update the kernel GRUB swaps sda <-> sdb. Does it every time. Never found out why. I just correct the hd0 <-> hd1 stanzas in menu.lst and that's it. Might it be the same effect in your system?

Did you take a live CD and run "fsck" on all your partitions yet?

All times are GMT -5. The time now is 09:00 AM.