I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.18.el5) root (hd0,0) kernel /vmlinuz-2.6.18-92.1.18.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-92.1.18.el5.img title CentOS (2.6.18-53.el5) root (hd0,0) kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-53.el5.img ~ ~ "grub.conf" 21L, 725C
Mark Snyder JMK Computerized TDIS 703 S Glover Ave. Urbana, IL 61802 (217)384-8891
On Wed, 2008-12-03 at 15:44 -0600, Mark Snyder wrote:
I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz
Your conf looks like mine, mostly, except for the "splashimage=(hd0,0)/grub/splash.xpm.gz". I did a quick "info grub" and paged through (_very_ quickly - you might want to double check) and there was no entry for splashimage that I spotted. Maybe that's an old parameter? Or?? Maybe someone more knowledgeable will know. Try removing that and see if it makes a difference.
hiddenmenu title CentOS (2.6.18-92.1.18.el5) root (hd0,0) kernel /vmlinuz-2.6.18-92.1.18.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-92.1.18.el5.img title CentOS (2.6.18-53.el5) root (hd0,0) kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-53.el5.img ~ ~ "grub.conf" 21L, 725C
Another possibility is a bug, I guess. Try upgrading to 5.2 (yum update after ensuring your repos are good).
Mark Snyder
<snip sig stuff>
HTH
Mark Snyder wrote:
I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.18.el5) root (hd0,0) kernel /vmlinuz-2.6.18-92.1.18.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-92.1.18.el5.img title CentOS (2.6.18-53.el5) root (hd0,0) kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-53.el5.img ~ ~ "grub.conf" 21L, 725C
The NOTICE generated by anaconda indicates a separate /boot partition. Be sure that you are editing the grub/grub.conf file that is in your boot partition (hda1) and not a similar, but superfluous, file that you find under /boot in your root filesystem when your /boot partition is not mounted.
Robert Nichols wrote:
Mark Snyder wrote:
I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.18.el5) root (hd0,0) kernel /vmlinuz-2.6.18-92.1.18.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-92.1.18.el5.img title CentOS (2.6.18-53.el5) root (hd0,0) kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.18-53.el5.img ~ ~ "grub.conf" 21L, 725C
The NOTICE generated by anaconda indicates a separate /boot partition. Be sure that you are editing the grub/grub.conf file that is in your boot partition (hda1) and not a similar, but superfluous, file that you find under /boot in your root filesystem when your /boot partition is not mounted.
I did a find for grub.conf and there are two copies of this file on the system, one in /etc and one in /boot/grub however the file in /etc is just a link back to /boot/grub/grub.conf
To check that this is the file being used I commented out the second title which then did not appear on the grub screen so I am sure that I am editing the correct file.
On Wed, Dec 3, 2008 at 4:44 PM, Mark Snyder mark@jmktdis.com wrote:
I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
<snip>
Have you tried to reinstall GRUB? If you do, possibly the problem will go away. http://wiki.centos.org/TipsAndTricks/ReinstallGRUB
Lanny Marcus wrote:
On Wed, Dec 3, 2008 at 4:44 PM, Mark Snyder mark@jmktdis.com wrote:
I recently installed CentOS 5.1 on a DL71 ASI notebook.
After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot.
Any help or suggestions to fix this would be much appreciated
<snip>
Have you tried to reinstall GRUB? If you do, possibly the problem will go away. http://wiki.centos.org/TipsAndTricks/ReinstallGRUB _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I did the grub reinstall, it did not change anything but thanks for the suggestion and link.
I do not know, but I suspect that the problem has something to do with the fact that /boot is type ext2 while the rest of the file system is type ext3. I must have done this accidentally installing the system. It would take up to much of my time to reinstall the whole system again on the laptop, setup repositories, install wine, install wireless, install gstm and configure etc etc.
[root@dhcppc3 ~]# mount -l /dev/hda3 on / type ext3 (rw) [/] proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hda1 on /boot type ext2 (rw) [/boot] tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
I also tried umount on /boot and checked to try and find another grub.conf file. After the umount command the /boot mount point was empty so I do not think this is a problem
Thanks for the suggestions so far, but so far nothing has helped.
Mark
On Fri, 2008-12-05 at 11:02 -0600, Mark Snyder wrote:
<snip>
Thanks for the suggestions so far, but so far nothing has helped.
Did you ever try the removal of the splashimage thingy I noticed? I had quickly perused "info grub" and could not find that documented therein.
Mark
<snip>
William L. Maltby wrote:
On Fri, 2008-12-05 at 11:02 -0600, Mark Snyder wrote:
<snip>
Thanks for the suggestions so far, but so far nothing has helped.
Did you ever try the removal of the splashimage thingy I noticed? I had quickly perused "info grub" and could not find that documented therein.
Mark
<snip>
I have several other systems that I can check against, which all have the "splashimage thingy" and work as expected. I did verify that splashimage is referencing the file correctly i.e. (hd0,0) is /boot and I can open splash.xpm.gz in gimp and it looks like what is displayed when the system boots.
Mark Snyder wrote:
I do not know, but I suspect that the problem has something to do with the fact that /boot is type ext2 while the rest of the file system is type ext3. I must have done this accidentally installing the system. It would take up to much of my time to reinstall the whole system again on the laptop, setup repositories, install wine, install wireless, install gstm and configure etc etc.
I doubt this is the source of your problem, but google can tell you how to convert an ext2 fs to ext3 (tune2fs). Very easy, nothing to reinstall.
On Fri, Dec 5, 2008 at 10:44 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
Mark Snyder wrote:
I do not know, but I suspect that the problem has something to do with the fact that /boot is type ext2 while the rest of the file system is type ext3. I must have done this accidentally installing the system. It would take up to much of my time to reinstall the whole system again on the laptop, setup repositories, install wine, install wireless, install gstm and configure etc etc.
I doubt this is the source of your problem, but google can tell you how to convert an ext2 fs to ext3 (tune2fs). Very easy, nothing to reinstall.
I agree.
Are you sure that the hardware is supported on CentOS? I don't recognize the specific model you mentioned, so I don't know what CPU, motherboard, memory, etc. you have.
Have you tried timeout=0?
Have you checked all the PROM settings?
I'm just fishing here 'cuz nothing so far rings a bell....
HTH
mhr
MHR wrote:
On Fri, Dec 5, 2008 at 10:44 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
Mark Snyder wrote:
I do not know, but I suspect that the problem has something to do with the fact that /boot is type ext2 while the rest of the file system is type ext3. I must have done this accidentally installing the system. It would take up to much of my time to reinstall the whole system again on the laptop, setup repositories, install wine, install wireless, install gstm and configure etc etc.
I doubt this is the source of your problem, but google can tell you how to convert an ext2 fs to ext3 (tune2fs). Very easy, nothing to reinstall.
I agree.
Are you sure that the hardware is supported on CentOS? I don't recognize the specific model you mentioned, so I don't know what CPU, motherboard, memory, etc. you have.
Have you tried timeout=0?
Have you checked all the PROM settings?
I'm just fishing here 'cuz nothing so far rings a bell....
HTH
mhr _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You are both absolutely correct, changing from ext2 to ext3 did nothing to fix this. Not sure about the MB manufactured but it is a Pentium M 1.60GHz stepping 08 CPU with an Intel 915G chipset and a WD600UE ATA HDD
About the only options in the BIOS are the Date and Time and the Boot sequence.
I had actually tried to load Ubuntu first as I had herd (pun intended) "good things" about it. Was not at all happy with that distro and moved back to CentOS ASAP.
Setting timeout=0 does allow it to boot without having to press the enter key. The splash screen just flashes then the boot starts. Not really a solution but a workaround. I can live with it this way but still curious as to what is going on.
-
Lanny Marcus -
Mark Snyder -
MHR -
Nicolas Thierry-Mieg -
Robert Nichols -
William L. Maltby