Joe Morris (NTM) wrote:
This all looks correct. So, it is not your menu.lst, and if it tries to boot, it is not grub. Your kernel images look fine in boot. That comes down to a possibility the kernel module tree is messed up, if I still remember the problem correctly. Try rpm -V kernel-default, and/or ls -R /lib/modules/2.6.16.21-0.21-default/ which will be long, to long to transcribe to a different computer. If the first comes back clean, transcribe that one, if the second is short, then that one. If the first comes back clean, your kernel (according to rpm) is OK. If the second is long, it confirms what rpm is saying. If your kernel tree looks good, your machine should be working. BTW, how are you booting to get this info from your system? I am still confused by the uname -r output compared to ls /lib/modules.
I will try all the above. I am not re-booting. As stated in my 1st mailing "Finally got the system running by going into install and then backing out to "boot from hard drive." " I got lucky, and I left the machine running so I could supply all the files I knew I was going to be asked for. Thanks again for helping, --ED--