Skip to contentSkip to conversation

Warning: unable to open an initial console

DISCUSSION Steven A. DuChene 2 participants 2 messages Sep 30, 2009

lore
Share & tools
lore
#0 lore raw

Hmm, I tried various combonations of turning off the framebuffer support all together and then turning it back on with various drivers (nvidia or vesa vga) but still I get the same message about "Warning: unable to open an initial console."

Anything else I should be looking at besides the graphics support part of the drivers section of the kernel config?

Again this is a fairly standard PCChips A13G motherboard with NVidia chipset and AMD Athlon 3600+ CPU that works fine with the regular distro supplied FC9 kernel (2.6.25-14.fc9.x86_64) and I have the x86_64 version of FC9 installed.

-----Original Message-----

Quoted 39 lines

From: "Steven A. DuChene" <[email protected]>
Sent: Sep 30, 2009 11:55 AM
To: Arjan van de Ven <[email protected]>, [email protected]
Subject: Re: newer non-distro kernels don't boot / unpack?

OK, so after removing rhgb and quiet from the menu.lst for this kernel the last few messages it prints are:

sdb:
sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
XFS mounting filesystem sda3
VFS: Mounted root (xfs filesystem) readonly on device 8:3. Freeing unused kernel memory: 416k freed
Warning: unable to open an initial console.

Since it does not seem to be reaching the init stage but does seem to be finding the disks and mounting the filesystems it is getting much further along than I thought. I guess I have a problem with the console/terminal parts of the kernel compile/configuration.

-----Original Message-----

Quoted 13 lines

From: Arjan van de Ven <[email protected]>
Sent: Sep 30, 2009 11:47 AM
To: "Steven A. DuChene" <[email protected]>
Subject: Re: newer non-distro kernels don't boot / unpack?

first remove rhgb and quiet.. that way you get at least the kernel log on the screen... to see where you get stuck.

Signature · 3 lines
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
#1 lore raw
Quoted 5 lines · On Wed, 30 Sep 2009 13:05:24 -0400 (EDT) "Steven A. DuChene"…

Hmm, I tried various combonations of turning off the framebuffer support all together and then turning it back on with various drivers (nvidia or vesa vga) but still I get the same message about "Warning: unable to open an initial console."

Quoted 7 lines

Anything else I should be looking at besides the graphics support part of the drivers section of the kernel config?

Again this is a fairly standard PCChips A13G motherboard with NVidia chipset and AMD Athlon 3600+ CPU that works fine with the regular distro supplied FC9 kernel (2.6.25-14.fc9.x86_64) and I have the x86_64 version of FC9 installed.

on FC9 ....
here's what to do on a successful boot

mkdir /tmp/mnt2
mount /dev/sdaX /tmp/mnt
(where the X is your root device, if you use lvm, mount the lvm thing there)
cp -a /dev/console /tmp/mnt/dev/console
umount /tmp/mnt2