similar to: 6308072 need to update boot image with one supplied by brand artist

I'm having some difficulties pxe booting Solaris. So far I have tried the mboot.c32, and the pxegrub shipped with Solaris. At first I had some problems with blksize, but this disapeared when I changed from atftpd to tftpd-hpa. The point at which I'm stuck now is, the kernel and x86.microroot/x86.miniroot is loaded but then VMWare crashes. I might try with real hardware, but I thought

Author: setje Repository: /hg/zfs-crypto/gate Revision: bb9f8eccd7d8aef91c3bf4f6b393f812a8d0ce16 Log message: 6362643 GRUB graphics still not in line with unified "coolstart" branding 6363028 progress indicator needs to move and turn green to accommodate "coolstart" branding 6363031 boot progress graphics need to be updated with unified "coolstart" branding 6372042

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

Background: I am in the habit of making bootable GRUB CDs with menus and copies of working kernels and initrds, particularly for multiple-boot testing machines with multiple distros and/or the Redmond OS. This has helped pull my fat out of the fire more than once when a system was rendered unbootable by hardware changes, or when Bill Gates decided the MBR should be taken over. This generally

Hey list, I recently started working with kickstart. It is awesome! I really had no idea how easy it would be to use. I do have one strange issue, that's really not that important, but that I'd like to figure out. I like to watch all the kernel boot messages go by in text mode by default, and when I've set up a box in the past, I've modified grub's menu.lst file to remove

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

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

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

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:

# 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

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'm playing with software RAID and LVM in some virtual machines and I've run into an issue that I can't find a good answer to in the docs. I have the following RAID setup: md0: sda1 and sdb1, RAID 1. This is /boot md1: sda2 and sdb2, RAID 1. This is a PV for LVM. VolGroup00, this is the volume group and md1 is the only PV in it. LogVol00 is swap LogVol01 is / LogVol02 is /home

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

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

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 have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when I did the kernel update) and have modified grub.conf to use the single CPU kernel: # 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. #

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

Hi: Any hints/pointers welcome. I am very new to Xen, I have a AMD "AMD Athlon(tm) 64 X2 Dual Core Processor 4000+" based system on which I am running X86_64 Fedora Core 8. I have installed Xen-3.1 on it, but I can''t get Xen to boot. It seems unable to find the root volume, the kernel panics and reboots immediately so I can''t capture or write down anything and I

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

Hello all, I am sort of new to XEN and I have a dedicated server that is hosted for me. This server is an intel single quad 4 with 4 gig of ram. The OS is Centos 5 completely updated. I have installed XEN from the add and remove applet within Centos. Here is my grub.conf: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.10.el5PAE)