similar to: kickstart and grub parameters

This is irritating: I've got a server I just upgraded 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

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

I have a grub.conf (below) 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

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

Hi. I just noticed I had a CentOS 5.3 system that I updated to CentOS 5.5 a few days ago, and I just ran "yum -y update" again to get the latest kernel, and I just noticed it still has the old 2.6.18-128 kernel instead of the new 2.6.18-194.17. What gives? /etc/grub.conf points at 2.6.18-194.17, but when I reboot, 2.6.18-128 comes up. Any suggestions? Thanks, -at myserver# yum -y

Many times when i boot my Xen machine i get a message saying something like "The greeter application has failed many times, using alternative greeter." From there on I can do everything OK as far as i can see. Sometimes when i boot the machine, it just randomly restarts halfway through the boot process. It has also been crashing alot lately when i try to run it 24/7. Any ideas? here

# grub.conf generated by anaconda I recently tried installing xen on another machine and I''m getting the "CPU0 is toast rebooting in 5 seconds" message. Reading through past postings, I was hopeful setting the dom0_mem=128M would solve the problem. Unfortunately, it didn''t make a difference. I haven''t fooled with anything on this system -- just a fresh FC4

There was a discussion here several days ago that was precipitated by my decision to manually install the new kernel before YUMming the upgrade to CentOS 4.2. The upgrade went south but I recovered by doing a fresh install and a bunch of copying from backups. All's well EXCEPT that I'm back in the same "box", thanks to anaconda. I set out to upgrade kernels this morning:

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

Hi, One of my servers in a IDC in another country mysteriously went down this morning, and when I contacted the IDC, I was told that XEN doesn'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

Hi all, I have an odd problem, for which I couldn't find any suggestions on google. A CentOS 5.7x64 gives me a blank screen on bootup, both to the 17" LCD monitor connected to the VGA port, and to the KVMOVIP device built-into the server, I can see the GRUB boot loader, and everything booting up, upto the point where it says "Waiting for driver initialization.", then it goes

Hi all, Recently 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

Hey, I built a 2.6.18.8-xen kernel and created the initial ram disk by following the instructions in README file in Xen source package. Then I put a entry for new kernel in /boot/grub/menu.lst (I am using CentOS 5). Here is the menu.lst: ########################################## default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-8.el5) root

I installed the xen 2.6 binary tarball on my Linux 2.6 Fedora Core x86 system and added the entry to the grub.con file. I am still not able to get it up and working. It keeps restarting itself during the boot process. I''ve managed to capture the contents of the boot at the end before it restarts: error opening /dev/console error dup2''ing fd of 0 to 0 error

I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # 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 #

Hi my friends, I am running into a problem with my NIC. [root@xxxx ~]# ifup eth0 Error for wireless request "Set Encode" (8B2A) : SET failed on device eth0 ; No such device. SIOCGIFFLAGS: No such device Failed to bring up eth0. eth0 is not a wireless device. Below are some information about my host: [root@xxxx ~]# lspci |grep -i ether 00:04.0 Ethernet controller: Intel Corporation

Hi, all: I'm using centos 6.2-x86_64, the built-in kernel version is 2.6.32-220.el6.x86_64. Now I compiled kernel of version of linux-2.6.32-220.23.1.el6.x86_64, which get from kernel-2.6.32-220.23.1.el6.src.rpm. I have put vmlinuz and initramfs into /boot directory, as follow: [kdev at panda boot]$ ll /boot/vmlinuz-2.6.32-* ./initramfs-2.6.32-* -rwxr-xr-x. 1 root

I've been going along not noticing things happening right under my nose. so imagine my surprise when I discovered last night that my Centos 5 box has installed multiple new kernels over the last few months, as updates come out, and IT IS NOT BOOTING THE NEWST ONE. grub.conf says to boot kernel 0, and 0 is the newest one. but the one it actually boots is 6 or 8 down the list (clearly I've

I've also had a few Xen systems grub entry issues. I'm not yet sure what triggers the events, but I do think there *may* be a correlation to the "/boot" part. I've found the Xen servers that have "/boot" before any of the the lines like "/boot/xen.gz" ended up missing complete grub entries. Not sure it's 100% true. Anyone else comment? Thanks PJ On

Hi, I installed Fedora 10 as domU on CentOS 5.3. I need new 2.6.25.14 kernel under domU (in order to patch it for MPLS protocol). I followed advice on http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen, and compiled kernel with XEN options enabled under domU. I got all relevant packages in /boot and /lib/modules, but when I try to boot virtual machine I got this error: Error starting