Date: Sat, 15 Jan 2000 03:04:07 +0100 (CET) From: Juergen Lock <nox@jelal.kn-bremen.de> To: msmith@FreeBSD.ORG Cc: Mike Bristow <mike@urgle.com>, Mike Smith <msmith@FreeBSD.ORG>, R Joseph Wright <rjoseph@nwlink.com>, freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels Message-ID: <200001150204.DAA28337@saturn.kn-bremen.de> In-Reply-To: <200001121739.JAA02551@mass.cdrom.com> References: <20000112170704.A5073@lindt.urgle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200001121739.JAA02551@mass.cdrom.com> you write: >> I still maintain that the /right/ solution is for the BIOS to have >> a ``while booting shovel data out COM1 and accept data from COM1 as if >> it were my keyboard'' option. >> >> I've seen them on (I think) NCR boxes. > >Intel do this on their server boxes, to the extent that if you have a >colour ANSI terminal you can run fullscreen expansion BIOS tools like eg. >Adaptec's. I'm reasonably sure that it's just an extra-price option from >the major BIOS vendors. Compaq has something like this too, only better. i recently configured a Proliant 1600 server box that has a `integraded remote console' that could even drive a modem (unless its a `win'modem, obviously) and have it accept calls to `log in' to the console. it lets you construct any key combination thru special character sequences, force a reset remotely, capture NT's blue screen of death, etc. probably _very_ useful for the poor guys trying to depend on `server OS'es less stable than unix... :) (unfortunately i didn't get around actually playing with it, and when i just wanted to configure it to use a serial console the `usual' way i had to use -h in boot.config because -P didn't work as it believed it always had a keyboard.) And in case anyone else comes around such a machine... you have to run the setup CD that comes with it first, otherwise the BIOS doesn't even know how much RAM it has, and the SCSI controller(s) apparently don't get properly initialized causing the BOOTMFS kernel to panic. (i may even still have the actual place where in the ncr driver it died in case that interests anyone...) The setup CD installs a DOS partition that can be used to do configurations later (apparently it doesn't have any configuration screens in the BIOS itself?), and after that the BIOS still didn't seem to report the amount of RAM properly, the kernel still only saw 16MB until i added VM86. Oh and the on-board `tl'-type NIC caused a panic once, so we installed an fxp. (i got the crashdump and mailed wpaul a backtrace but ne needed me to do more tests which i didn't find the time for, sorry. I only managed to update it to the latest -stable before it got installed in order to get the sym driver...) Regards, -- Juergen Lock <nox.foo@jelal.kn-bremen.de> (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001150204.DAA28337>