new mobo - how 2 detect on boot? Grub loader
 

More madness.

The old mobo (AMD) was over-heating (the fan went bad and runs too slow now).
The only other mobo I have is Intel (P4). The mobo boots well, and the Grub loader menu appears. However when selecting Red Hat 9 (Shrike) the screen blanks and then the PC re-boots.

The HDs are fine. I placed them back into the old server and the system came right up.

I need to know how to get it into full detection mode on boot. I do know the password to get more options on the loader, I just don't know where to go from there.

T.I.A.

While I'm waiting for an answer, I'll be digging through my books and the web. The race is on! <smile>

Kernel compile, possibly
 

Well, this is what I would do if I were in your shoes.

It seems to me that you might have recompiled your kernel for your old AMD motherboard and left out the default settings for your redhat install. Since the kernel is looking for a particular disk controller, it's not seeing the one on your new Intel motherboard.

I'd grab my linux install disk, and do a rescue boot your system.

1) Boot up the disc
2) do a 'root=/dev/<wherever-your-root-directory-is> ro noinitrd' when you get that boot: prompt thing
3) get a root shell in
4) run 'lilo' again, or in your case, reconfigure grub.

If that doesn't work, do the same as above, except recompile your kernel for that particular Intel motherboard.

Oh yes, this procedure works for a Slackware distribution, but I 'm sure if you look through the redhat dox, you'll find how to use/create a rescue disc. HTH

Thank you!

I will try this and get back to you. I did not re-compile that I realize, but then I was massivly new to Linux and probably just didn't recognize it.

I think this is the correct because when I try to boot to DOS from the grub loader it gives me rootnoverify, which, if I understand correctly, means it cannot load the partition.

The only thing that confuses me is how it loads grub. Ah - well. Post problem learning. For now I just need to get it back up.

Thanks again and more later.

OoooKayyyy. Zip and Nada.

I got into the grub command line. Couldn't figure out anything usefull to do there.

Tried editing the grub "bat" file. hd0,0, hd0,1 hd0,2 hd0,3 doesn't work. 0 & 3 are recognized partitions, but they don't seem to contain the kernel file that it is looking for.

Found my Red Hat 9 install cd. Launched rescue and tooled around there. Disks and data are fine and still on hda and hdb in proper order. No luck.

Tried the "upgrade" option from the install cd. That didn't cause a re-detect of hardware like I was hoping. So that didn't work.

Can't find kduzu to run it. Can't run Xconfigurator (whatever that is, I don't really know).

Grrrrrr. Looked into re-compiling kernel. The only book that would mention it is a generic Linux text. I found a red-hat how to, but they just list the programs you need... they don't mention what directories they would be in and whereis can't find them.

Surely there is a simple command to get it to re-detect hardware before the kernel is loaded? Or a utility that does this and then updates the grub file enough to get it to load the kernel?

I'm beging to look at installing a new hard drive and somehow migrating my user database, SAMBA database and SSH info. Although that is very daunting too.

If anyone has run into this, please point me in the right direction. This is very odd to me as I originally remember moving this drive from an Intel platform to the AMD platform w/out all this fuss.

T.I.A.

user database migration
 

Well. I've installed Fedora Core 2 on a new hard disk in the new system. That went wonderfully of course. Now I just need to change the ext2 filesystem to ext3 and figure out how to pull the userdata base over from the old system which is (knock on wood) still running albeit with the temperature alarm sounding.

If anyone has ideas as to how to migrate the user database for Red Hat linux 9 and Samba 2.8x , I'd love to hear from you. Re-setting the passwords for 250+ users is not what I would like to do this week.

T.I.A.