-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Replying to myself for the archives:
Marian Hettwer wrote: > > The Dell only knows 3 Parameters for console redirection to serial port: > > enabled / disabled (is set do "on" obviously) > Remote Terminal Type: ANSI or VT100 (is set to VT100) > Redirection After Boot > > When I set the last paramter to disabled, I don't even see the pxeboot > (pxe bootloader) of OpenBSD. Logically, I can't type in "set tty com0". > > If I set this parameter to enabled, I can see the OpenBSD pxeboot and > can type in stuff like "set tty com0". > But as mentioned earlier, the command is returned with "com0 console not > present". > Damn... > > set tty com0 --> "switching console to com0, com0 console not present" > > Any more ideas? Yeah, I have more ideas to my own question... I disabled the "Redirection After Boot" again and created a etc/boot.conf in my tfptroot, consisting of the following lines set tty com0 set image bsd.rd boot bsd.rd files in my tftproot are now looking like that bsd.rd etc/boot.conf openbsd-pxe (aka pxeboot) bootet the Dell via pxe and see... - - no serial output while PXE asked for a DHCP server - - serial output seen as soon as bsd.rd bootet thus I'd say, the set tty com0 was successfull and before the BIOS was "blocking" the serial port. Linux can cope with this situation and OpenBSD can't. That's not particulary beautiful, as I am now missing the PXE output (which has some information available), but at least I can pxeboot the Dell and install OpenBSD via network. All in All, I'd say: Was easy with Linux, was a bit harder with OpenBSD, and as I'm now reading the FreeBSD docs on PXE... ugh! wtf and omfg. Why making easy things hard?? ./Marian iD8DBQFE9Zv/gAq87Uq5FMsRAkFfAKDf2NDYJMFtEeRjCmlIHCXwartDFgCeKBOk vF1/Nvxytf5d+3vUSfiMhBM= =LeND -----END PGP SIGNATURE-----
