Sponsored Content
Operating Systems Linux Ubuntu nothing happens when booting kernel Post 302263425 by osulinux on Monday 1st of December 2008 03:16:33 PM
Old 12-01-2008
nothing happens when booting kernel

I have a Fedora 9 installation. The initial kernel worked fine. Then I did a yum update and one of the new updates was a new kernel, but when I tried to reboot with that kernel it won't do anything. The same exact thing happens with the latest kernel in yum.

If I take the vga= line out of my grub command I can get the following:
Code:
Decompressing Linux... Parsing ELF...Done
Booting Kernel ....

Aperture beyond 4GB Ignoring

Kernel Alive

That's it, nothing else. No HD activity, nothing. If I leave the vga= line in there then after grub I just get a blank screen.

Here's my grub.conf..
Code:
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27.5-41.fc9.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.27.5-41.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vga=0x31A selinux=0
	initrd /initrd-2.6.27.5-41.fc9.x86_64.img
title Fedora (2.6.26.6-79.fc9.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.26.6-79.fc9.x86_64 ro root=UUID=3c047f95-6124-4d87-85cd-8ffdb34f4f44 rhgb quiet vga=0x31A selinux=0	
	initrd /initrd-2.6.26.6-79.fc9.x86_64.img
title Fedora (2.6.25-14.fc9.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=3c047f95-6124-4d87-85cd-8ffdb34f4f44 rhgb quiet vga=0x31A selinux=0
	initrd /initrd-2.6.25-14.fc9.x86_64.img
[root@spiderpig ~]#

I've tried with both the UUID= gunk and the /dev/whatever stuff as well. Both do the same exact thing.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Booting

Hi all, I've managed to get Mandrake 9 installed by disconnecting my 2 windows' drives. When I reconnect them Mandrake wants to take over. I figure it's time for the BootManager, or should I use a Linux specific one like Lilo? Or have I already stuffed up by not running Lilo at time of... (2 Replies)
Discussion started by: onestepto
2 Replies

2. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

3. Programming

kernel-kernel call communication

hi all! i have developed a mechanism in system.c to count how many times each kernel call is called. The results are held in an array in system.c . What i want to do is to create a new kernel call which will print this array. I need help in passing the array from system.c to the new kernel call. ... (5 Replies)
Discussion started by: aureliano
5 Replies

4. SuSE

max number of slabs per kernel module (kernel 2.6.17, suse)

Hi All, Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff. Cheers, Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies

5. AIX

How to convert a partition usin 64 bits kernel to 32 bits kernel?

Hello there: I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel? Please help me. Regards. (2 Replies)
Discussion started by: GEIER
2 Replies

6. UNIX Desktop Questions & Answers

kernel panic-not syncing:fatal exception while booting

Hi ALL, I am getting error.. kernal panic-not syncing:fatal exception while booting. Please help me.. Thanks Jack (7 Replies)
Discussion started by: jack00423
7 Replies

7. Linux

Supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" me

supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes. I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason? It has... (1 Reply)
Discussion started by: pankajd
1 Replies

8. Solaris

Which file is read by kernel to set its default system kernel parameters values?

Hi gurus Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies

9. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
PCINITRD(8)						      System Manager's Manual						       PCINITRD(8)

NAME
pcinitrd - create a PCMCIA initrd ram disk image SYNOPSIS
pcinitrd [-v] [-a] [--all] [-d alternate-root] [--dir=alternate-root] [-r kernel-release] [--release=kernel-release] [-s image-size] [--size=image-size] [-u] [--update] initrd-image [modules ...] DESCRIPTION
The pcinitrd script creates an initrd ram disk image for booting with the root filesystem on a PCMCIA device. If the target is a block special device (i.e., /dev/fd0), then the initrd image is created on that device. If the target does not already exist or if it is an ordinary file, then pcinitrd will create the image file using the ``loopback'' device. Modules are specified with paths relative to /lib/modules/[kernel-release]. The core PCMCIA modules (pcmcia/pcmcia_core and pcmcia/ds) will automatically be installed in the target image. All other device-specific modules need to be listed on the command line, along with the appropriate socket driver (pcmcia/i82365.o or pcmcia/tcic.o). Alternatively, if -a is specified, then all available PCMCIA socket drivers and block device drivers will be included in the image. Additional files to be copied to the initrd image may also be listed on the command line. Executable programs will be installed in /bin, shared libraries will be installed in /lib, device files will be installed in /dev, and any other files will be placed in /etc. The startup script in the resulting image, linuxrc, may need to be customized for a particular system. It contains the same variable defi- nitions as the normal PCMCIA startup scripts (i.e., PCIC=, PCIC_OPTS=, and CORE_OPTS= variables). The /etc/config.opts file may also need to be edited. Any changes to linuxrc or config.opts will be preserved if pcinitrd is executed in ``update'' mode. Another feature of the generated linuxrc is that if the DEBUG variable is set to a non-blank string at the boot prompt, then cardmgr will echo all its status messages to the console, and after linuxrc executes, it will fire up a shell on the console. This can be helpful for debugging initrd problems. However, few commands are available in the normal initrd environment. OPTIONS
-v Verbose mode. Identify files as they are copied. -a, --all Install all socket drivers and block-style PCMCIA device drivers, including memory card, SCSI card, and fixed-disk drivers. This is mainly intended for use by package maintainers. -d alternate-root, --dir=alternate-root Specifies an alternate directory tree to search for all the files used to put together the initrd image. This may be helpful for running pcinitrd after booting from an installation or rescue diskette. -r kernel-release, --release=kernel-release Specifies the kernel release number (i.e., 2.0.28) to use when looking for modules in /lib/modules. The default is the release of the running kernel. -s image-size, --size=image-size Specifies the filesystem size to create on the target file or device, in 1k blocks. The default is 2400. -u, --update Update mode: updates cardmgr and all the kernel modules in an existing initrd image, but does not modify other files. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
pcmcia(5), cardmgr(8), lilo(8). pcmcia-cs $Date PCINITRD(8)
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy