linux-kernel - Warning: unable to open an initial console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <31532395.1254330324879.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net>
Date:	Wed, 30 Sep 2009 13:05:24 -0400 (EDT)
From:	"Steven A. DuChene" <linux-clusters@...dspring.com>
To:	linux-kernel@...r.kernel.org
Subject: Warning: unable to open an initial console

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-----
>From: "Steven A. DuChene" <linux-clusters@...dspring.com>
>Sent: Sep 30, 2009 11:55 AM
>To: Arjan van de Ven <arjan@...radead.org>, linux-kernel@...r.kernel.org
>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-----
>>From: Arjan van de Ven <arjan@...radead.org>
>>Sent: Sep 30, 2009 11:47 AM
>>To: "Steven A. DuChene" <linux-clusters@...dspring.com>
>>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.
>>
>>
>>-- 
>>Arjan van de Ven 	Intel Open Source Technology Centre
>>For development, discussion and tips for power savings, 
>>visit http://www.lesswatts.org
>
>



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/