Subject: port-i386/31298: hangs during boot (no init console output)
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Michael Wardle <michael@endbracket.net>
List: netbsd-bugs
Date: 09/12/2005 00:13:00
>Number: 31298
>Category: port-i386
>Synopsis: hangs during boot (no init console output)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-i386-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Sep 12 00:13:00 +0000 2005
>Originator: Michael Wardle
>Release: NetBSD 2.0.2
>Environment:
System: NetBSD pepper.endbracket.net 2.0.2 NetBSD 2.0.2 (GENERIC) #0: Wed Mar 23 08:53:42 UTC 2005 jmc@faith.netbsd.org:/home/builds/ab/netbsd-2-0-2-RELEASE/i386/200503220140Z-obj/home/builds/ab/netbsd-2-0-2-RELEASE/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
On a fresh install of NetBSD 2.0.2, the kernel messages appear on the
standard console in green, but I see nothing after:
-----
boot device: wd1
root wd1a dumps on wd1b
root file system type: ffs
-----
If I wait a few seconds then press Ctrl-Break, I can see the system
initialization messages and then a login prompt. The system then
works fine.
It seems that the messages generated by init are not printed on the
console.
I have an ASUS nForce 2-based mainboard and an ASUSTek GeForce 2-
based video card. I am unsure whether this video card provides
full VESA video support and do not know what hardware is required
for the standard NetBSD wsconsole. The video card works fine in text
mode and in X, as well as in other operating systems.
I have tried disabling all displays except the console in /etc/ttys
and disabling the wscons entry in /etc/rc, but this makes no
difference. Prior to disabling the displays, I would see kernel
messages about wsdisplay0 adding screens 1 to 4 (I think only after
waiting some time and/or pressing Ctrl-C).
I used to get a couple of extra lines after the root file system
message showing that the system was detecting my HB USB printer on
ulpt0, but the problem persisted after detaching it.
>Fix:
Unknown