Date: Wed, 11 May 2005 08:32:53 -0400 (EDT) From: Peter Larkowski <peter@larkowski.net> To: "Gallagher, James" <james.gallagher@misys.com> Cc: freebsd-sparc64@freebsd.org Subject: RE: serial console on ultra axe Message-ID: <Pine.NEB.4.62.0505110830270.18293@pm6500.larkowski.net> In-Reply-To: <A99171D862A6D511A8F700B0D0D1307F02ED35A2@singex2.misys.com> References: <A99171D862A6D511A8F700B0D0D1307F02ED35A2@singex2.misys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I upgraded from 5.3 to 5.4 (stable cvsup) yesterday. I built >> a GENERIC >> kernel with the audiocs driver added. I read UPDATING and >> took note of >> the change to uart, updating /etc/ttys accordingly. >> Unfortunately I get >> nothing on the serial console after: >> >> Hit [Enter] to boot immediately, or any other key for command >> prompt. Booting [/boot/kernel/kernel]... nothing to autoload >> yet. jumping to kernel entry at 0xc0048000. >> >> It should be noted that I've never been able to use the >> default /etc/ttys. >> I've always had to start a getty on /dev/console, which doesn't work >> anymore either. In any case I'm not even getting kernel >> messages. Any >> ideas? The machine boots normally. as soon as the disk stops >> thrashing, I can ssh right in. > > Probably related to this issue here > http://lists.freebsd.org/pipermail/freebsd-stable/2005-May/014509.html ? It > was reported while I was in the middle of a cvsup (on x86) over the weekend. > I got away fine, didn't seem to have any noticeable problems (apart from an > annoying BIOS default I'd never noticed before). > Well, it looks like that was related to keyboard input, and this is console messages and everything. Plus that seems to have been resolved by Sunday, and I cvsuped yesterday morning (2005-05-10 ~08:00 EDT). Thanks for the heads up though. -p
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.4.62.0505110830270.18293>