search for: splashimag

...king 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...

...inux system on which to verify the bug. It seems to be only intermittently reproducible on CentOS and appears to be specific to the hardware and/or the details of grub.conf. The conditions under which I have seen it involved machines that had both CD/DVD and CD-RW/DVD-RW drives as well as using a splashimage from the hard disk [i.e. splashimage=(hd2,0)/grub/splash.xpm.gz as opposed to splashimage=(cd)/boot/grub/splash.xpm.gz]. Would be interested to hear if anyone else has seen this problem and can document the conditions to reproduce it. Phil ******************************************************...

Hello, Ive tried to find any hard information on how to install, and boot, opensolaris from a USB stick. Ive seen a few people written a few sucessfull stories about this, but I cant seem to get it to work. The procedure: Boot from LiveCD, insert USB drive, find it using `format'', start installer. The USB stick it not found (just stands on "Finding disks"). Remove USB stick,

...aking 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=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.12-1.1447_FC4xen0) root (hd0,0) kernel /xen.gz dom0_mem=128M module /vmlinuz-2.6.12-1.1447_FC4xen0 ro root=LABEL=/ module /initrd-2.6.12-1.1447_FC4xen0.img title Fedora Core (2.6.12-1.1447_FC4) roo...

...s to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/sda1 # initrd /boot/initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.17-1.2187_FC5xen0) root (hd0,0) kernel /boot/xen.gz-2.6.17-1.2187_FC5 module /boot/vmlinuz-2.6.17-1.2187_FC5xen0 ro root=LABEL=/ quiet module /boot/initrd-2.6.17-1.2187_FC5xen0.img title Fedora Core (...

...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/cciss/c0d0p6 # initrd /initrd-version.img #boot=/dev/cciss/c0d0 default=1 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title CentOS (2.4.21-27.0.2.EL) root (hd0,0) kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/ initrd /initrd-2.4.21-27.0.2.EL.img title CentOS (2.4.21-27.0.2.ELsmp) root (hd0,0) kernel /vmlinuz-2.4.21-27.0.2.ELsmp ro root=LABEL=/...

...ed to 5.4, then rebooted, only to discover that it just *sits* there at the grub boot menu. I looked at grub.conf, and uncommented hiddenmenu (which should have been done long ago). It *still* sits there when I reboot. Any clues, folks? mark grub.conf: #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-164.2.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-164.2.1.el5 ro root=LABEL=/ rhgb initrd /initrd-2.6.18-164.2.1.el5.img title CentOS (2.6.18-164.el5) root (hd0,0) kernel /vmlinuz-2.6.18-164.el5 ro ro...

...s. I might try with real hardware, but I thought that VMWare had full support for Solaris / PXE booting. Currently I'm loading the pxegrub via pxelinux and this is my menu.lst file for pxegrub. # #pragma ident "@(#)install_menu 1.1 05/04/15 SMI" # default=0 timeout=30 splashimage=/boot/grub/splash.xpm.gz foreground=ffffff background=444444 title OpenSolaris 2008.05 kernel$ /boot/grub/unix -B install_media=192.168.20.57:/srv/pxeboot/opensolaris module /boot/grub/x86.microroot title OpenSolaris 2008.05 text console kernel$ /platform/i86pc/kernel/$IS...

...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/dom0/root # initrd /initrd-version.img #boot=/dev/md0 default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-128.1.10.el5xen) root (hd0,0) kernel /xen.gz-3.2 #kernel /xen.gz-3.2 dom0_mem=256M module /vmlinuz-2.6.18-128.1.10.el5xen ro root=/dev/dom0/root module /initrd-2.6.18-128.1.10.el5xen.img I google this problem for a whole day. Someone says...

...cently I build XEN 4.1 (from the xen.org) on centIOS 5.5 (kernel 2.6.38.4). After changing the grub file and rebooting the machine, I am continuously getting out of memory error. The content of my grub file: default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=10 console serial splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.38.4) root (hd0,0) kernel /vmlinuz-2.6.38.4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.38.4.img title CentOS (2.6.38-xen0) root (hd0,0) kernel /xen-4.1.0.gz loglvl=all dom0_mem=512m...

..., you can use it as >your base of one of the following links[1-4], should be sufficient to >get you started. >[0] https://github.com/EarlRamirez/snipeit_iso In above github project, in https://github.com/EarlRamirez/snipeit_iso/blob/master/isolinux/grub.conf file, there is ?@? symbol for splashimage, and for kernel, @KERNELPATH@, @ROOT@, etc. Will those be replaced by actual values? Where do actual values come from? How does actual values substitute those variables? Thanks again, - Xinhuan

...o remove all the GUI components of the boot. But when I try this from a kickstart-installed box, either from a %post section or manually, I still get (mostly) the GUI boot process. Here's my relevant menu.lst exerpts: first, the one working the way I like: #boot=/dev/hda default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title CentOS (2.6.18-194.11.4.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.11.4.el5 ro root=LABEL=/ initrd /initrd-2.6.18-194.11.4.el5.img Then, the one not behaving the way I expect: #boot=/dev/sda default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.x...

Hey, I ran a yum update and it installed a new kernel. ?? ... ?? Installed: ??? kernel.x86_64 0:2.6.32-71.29.1.el6? kernel-devel.x86_64 0:2.6.32-71.29.1.el6 but it did not modify the grub.conf file. ? #boot=/dev/sda ? default=0 ? timeout=5 ? splashimage=(hd0,0)/grub/splash.xpm.gz ? hiddenmenu ? title CentOS (2.6.32-71.el6.x86_64) ?? ?????? root (hd0,0) ?? ?????? kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=... ?? ?????? initrd /initramfs-2.6.32-71.el6.x86_64.img Is this the new behavior or...? Thx, JD

Hi, After reading the tutorial at http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 I have the following question: What should I put instead of splashimage=(hd0,0)/grub/splash.xpm.gz and root (hd0,0) on /etc/grub.conf? Should I leave those lines untouched? If so, how would grub know where to boot from if /dev/sda fails? Or I would need to swap the drives in order to boot properly and then put a new one as /dev/sdb and then add it to the a...

...unable to find the root volume, the kernel panics and reboots immediately so I can''t capture or write down anything and I can''t seem to find a log anywhere in /var/log that would capture the failed boot sequence. I have a SATA drive. My grub.conf file is: default=0 timeout=5 splashimage=(hd0,2)/boot/grub/splash.xpm.gz hiddenmenu title Xen 3.1 / XenLinux 2.6 kernel /boot/xen-3.1.gz console=vga module /boot/vmlinuz-2.6-xen root=LABEL=/1 ro console=tty0 # have also tried root=/dev/sda3, no luck. title Fedora (2.6.23.9-85.fc8) root (hd0,2) kernel /...

...o 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/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title CentOS-4 i386-up (2.6.9-22.EL) root (hd0,0) kernel /vmlinuz-2.6.9-22.EL ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.9-22.EL.img You have new mail in /var/spool/mail/root Then, I proceeded with the kernel upgrade and chec...

...le # 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/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title Red Hat Enterprise Linux Server (2.6.18-8.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-8.el5 module /vmlinuz-2.6.18-8.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet module /initrd-2.6.18-8.el5xen.img title Red Hat Enterprise Linux Server...

...ow) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi. How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi. What can I do to get this parameter in my kernel boot line. Jerry ----------------- default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-164.11.1.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/ rhgb quiet pci=nomsi initrd /boot/initrd-2.6.18-164.11.1.el5.img cat /proc/cmdline ro root=LABEL=/ rhgb quiet dmesg | more...

...if I remove sda, the machine doesn't boot and grub complains. The question I have is how does one reinstall the boot sector at this point? I'm a little confused as far as to what device to install it on and what to specify as the root. This is grub.conf if it helps: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz title CentOS (2.6.18-194.e15) root (hd0,0) kernel /vmlinuz-2.6.18-194.e15 ro root=/dev/VolGroup00/LogVol01 initrd /initrd-2.6.18-194.e15.img Grub has always been a little confusing for me, so I guess I don't understand. What do the two root entries specify? And...

...esn't boot up, as follows: [QUOTE] This is error message on the screen " Error 19: Linux Kernel must be loaded before initrd" Server is currently up with 2nd kernel. Please check the grub.conf. [/QUOTE] Looking at grub.conf, I see the following: #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-128.1.10.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol01 ide0=noprobe ide1=noprobe initrd /initrd-2.6.18-128.1.10.el5.img title CentOS (2.6.18-128.1.10.el5) root (hd0...