Re: dmesg default color
Hello, I'd like to add a (somewhat) related question to that. Working with an IMPI card in a server, the BIOS has an option where you can keep redirecting keyboard/screen output in 3 options: - Only BIOS / BOOTLOADER / Always The first 2 OPTIONS work and I prefer the Until BOOTLOADER, so if a Software RAID fails, I can make it boot from the second disk (which has a different ccd config in the /etc folder). But the option always doesn't work. It looks like the blue colored screen sends out all kinds of ASCII color codes or something. I get all kinds of messed up data on the terminal (IPMItool or the software which comes with the motherboard). I've read up on this and found out I need to tell OpenBSD to redirect the console (in a boot.conf file for example), this works great. But is there a way to completely disable the ASCII output, since then I could just set the BIOS option to Always, because the current solution still has 1 problem. I need to have the IPMITool or software from the motherbord activated, so OpenBSD keeps on booting. (or rename the file to boot.conf.bak and for the time don't have console redirection, which is what I've currently done). So to shorten my question: Can you disable the color code stuff during boot time. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roman Strogin Sent: zaterdag 15 maart 2008 6:37 To: misc@openbsd.org Subject: dmesg default color Hello, while booting dmesg is in white on blue by default. How can it be changed? Thanks.
Re: dmesg default color
* Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 10:22]: I'd like to add a (somewhat) related question to that. Working with an IMPI card in a server, the BIOS has an option where you can keep redirecting keyboard/screen output in 3 options: - Only BIOS / BOOTLOADER / Always But the option always doesn't work. always never works :) It looks like the blue colored screen sends out all kinds of ASCII color codes or something. I get all kinds of messed up data on the terminal i highly doubt that is related in any way. the bios level serial redirections are all shitty crap. some are at least somewhat useable. most fuck up your terminal. so, what happens: the bios just has hooks in the i/o routines to do serial. any half modern OS does not use the bios once booted, but probes hardware itself and talks to it directly. so that always option is pretty useless (unless you want to waste electricity on running DOS). (IPMItool or the software which comes with the motherboard). I've read up on this and found out I need to tell OpenBSD to redirect the console (in a boot.conf file for example), this works great. yes. that is the way to go. bios redirection until bootloader, then boot.conf. usually works. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: dmesg default color
On Sat, Mar 15, 2008 at 08:36:51AM +0300, Roman Strogin wrote: Hello, while booting dmesg is in white on blue by default. How can it be changed? You may redefine WS_KERNEL_FG (foreground) and WS_KERNEL_BG (background) in your kernel configuration file: option WS_KERNEL_FG=WSCOL_WHITE option WS_KERNEL_BG=WSCOL_BLUE Please see sys/dev/wscons/wsdisplayvar.h for colours' definitions. Thanks. -- C programmers never die. They're just cast into void. () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Re: dmesg default color
Alright, I'll just change the bootorder in the BIOS if something goes horribly wrong. Except I was really hoping to use the IMPI card to monitor the blue output of OpenBSD too for when doing kernel updates and rebooting if something goes wrong. And if I understand you correctly, that data will probably never be sent over IPMI since that is when BSD probes the hardware... Guess I'll have to save up for a KVM :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henning Brauer Sent: zaterdag 15 maart 2008 12:25 To: misc@openbsd.org Subject: Re: dmesg default color * Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 10:22]: I'd like to add a (somewhat) related question to that. Working with an IMPI card in a server, the BIOS has an option where you can keep redirecting keyboard/screen output in 3 options: - Only BIOS / BOOTLOADER / Always But the option always doesn't work. always never works :) It looks like the blue colored screen sends out all kinds of ASCII color codes or something. I get all kinds of messed up data on the terminal i highly doubt that is related in any way. the bios level serial redirections are all shitty crap. some are at least somewhat useable. most fuck up your terminal. so, what happens: the bios just has hooks in the i/o routines to do serial. any half modern OS does not use the bios once booted, but probes hardware itself and talks to it directly. so that always option is pretty useless (unless you want to waste electricity on running DOS). (IPMItool or the software which comes with the motherboard). I've read up on this and found out I need to tell OpenBSD to redirect the console (in a boot.conf file for example), this works great. yes. that is the way to go. bios redirection until bootloader, then boot.conf. usually works. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: dmesg default color
* Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 12:44]: Alright, I'll just change the bootorder in the BIOS if something goes horribly wrong. Except I was really hoping to use the IMPI card to monitor the blue output of OpenBSD too for when doing kernel updates and rebooting if something goes wrong. And if I understand you correctly, that data will probably never be sent over IPMI since that is when BSD probes the hardware... that IPMI card should just see the serial port output, no matter wether serial level redirection, bootloader set tty, or getty. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: dmesg default color
You are correct I assume, but I wasn't talking about tty's or bootloader, I was talking about the kernel output. Which is after the bootloader, but before tty's are initialized, which is what I wanted to see remotely... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henning Brauer Sent: zaterdag 15 maart 2008 13:51 To: misc@openbsd.org Subject: Re: dmesg default color * Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 12:44]: Alright, I'll just change the bootorder in the BIOS if something goes horribly wrong. Except I was really hoping to use the IMPI card to monitor the blue output of OpenBSD too for when doing kernel updates and rebooting if something goes wrong. And if I understand you correctly, that data will probably never be sent over IPMI since that is when BSD probes the hardware... that IPMI card should just see the serial port output, no matter wether serial level redirection, bootloader set tty, or getty. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: dmesg default color
On Sat, Mar 15, 2008 at 02:02:21PM +0100, Erwin van Maanen wrote: You are correct I assume, but I wasn't talking about tty's or bootloader, I was talking about the kernel output. Which is after the bootloader, but before tty's are initialized, which is what I wanted to see remotely... You haven't tried using set tty in boot.conf, have you? There is nothing you can see on a VGA console that you can't see with one set in boot.conf, except the pretty colors. -- Jussi Peltola
FW: dmesg default color
I have done so yes, but in my previous e-mail I stated the problem this results in: I have to always have the ipmitool enable when the server is rebooted, or the system doesn't want to boot up. Sorry, let me explain it better: - If I set the bios to always, this results in weird data on the terminal. - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: : I don't see the kernel output (or is this a ascii related output problem) : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. I tried to get my explanation in small steps, so I don't make a mail with 3 problems I can't fix :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jussi Peltola Sent: zaterdag 15 maart 2008 14:42 To: misc@openbsd.org Subject: Re: dmesg default color On Sat, Mar 15, 2008 at 02:02:21PM +0100, Erwin van Maanen wrote: You are correct I assume, but I wasn't talking about tty's or bootloader, I was talking about the kernel output. Which is after the bootloader, but before tty's are initialized, which is what I wanted to see remotely... You haven't tried using set tty in boot.conf, have you? There is nothing you can see on a VGA console that you can't see with one set in boot.conf, except the pretty colors. -- Jussi Peltola
Re: FW: dmesg default color
* Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 15:30]: - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: : I don't see the kernel output what a surprise. you want com0. (or is this a ascii related output problem) forget about that finally : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. that is totally weird. sounds like daramatically fucked hardware/bios. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: FW: dmesg default color
On Sat, Mar 15, 2008 at 03:41:28PM +0100, Henning Brauer wrote: : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. that is totally weird. sounds like daramatically fucked hardware/bios. Couldn't it be the classical problem of something inputting crap at the prompt making it, of course, not boot? -- Jussi Peltola
Re: FW: dmesg default color
Okay, let me try to be even clearer :) - If I set the bios to always, this results in weird data on the terminal. (hence my first question: can I use always in the bios for impi output, which apperently I can't) - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: (com0 is the normal com port in this specific type of mobo it seems) : I don't see the kernel output but DO get a login prompt after the system is booted (so my question here is: could this be an ascii related output/translation problem) : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. (my last question: can this be normal?) My boot.conf.bak looks like: stty com1 19200 set tty com1 And this works fine, but only while listening on the impi interface while booting and it doesn't display the kernel output: - is this because of ascii translation troubles in the ipmi protocol implementation? - or can't the kernel console redirect to the com port while initializing hardware (and is the what bsd is doing while outputting the blue text)? My 2 solutions I've come up with are, but that's where I'm stuck. - Switch in and out the boot.conf whenever I need it and am sure I can use the impitool to listen when the system reboots. - Buy a KVM. Sorry, it's actually quite a few questions packed together, hence I can't figure it out... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henning Brauer Sent: zaterdag 15 maart 2008 15:41 To: misc@openbsd.org Subject: Re: FW: dmesg default color * Erwin van Maanen [EMAIL PROTECTED] [2008-03-15 15:30]: - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: : I don't see the kernel output what a surprise. you want com0. (or is this a ascii related output problem) forget about that finally : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. that is totally weird. sounds like daramatically fucked hardware/bios. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: FW: dmesg default color
On Sat, Mar 15, 2008 at 04:10:58PM +0100, Erwin van Maanen wrote: Okay, let me try to be even clearer :) - If I set the bios to always, this results in weird data on the terminal. (hence my first question: can I use always in the bios for impi output, which apperently I can't) - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: (com0 is the normal com port in this specific type of mobo it seems) : I don't see the kernel output but DO get a login prompt after the system is booted (so my question here is: could this be an ascii related output/translation problem) boot.conf has nothing to do with that, it's /etc/ttys. Are you sure 19200 is the correct speed, and did you try without 'stty' at all?
Re: FW: dmesg default color
* Jussi Peltola [EMAIL PROTECTED] [2008-03-15 15:59]: On Sat, Mar 15, 2008 at 03:41:28PM +0100, Henning Brauer wrote: : The system won't boot beyond the bootloader if I don't have the ipmitool enabled and listening during boottime. that is totally weird. sounds like daramatically fucked hardware/bios. Couldn't it be the classical problem of something inputting crap at the prompt making it, of course, not boot? yup. except that i have never actually seen that, yet not so classical from my pov :) -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
FW: FW: dmesg default color
Ah okay, forgot about that yeah... I've set /etc/ttys as well: tty01 /usr/libexec/getty std.19200 vt220on insecure That's why I get the prompt, skipped that step sorry... It's been a while back since I configured it and doing this from memory... But still if I use the boot.conf, it doesn't display the blue stuff, but does show the rest after (network settings, diskchecks etc). And the system also doesn't boot if I have the boot.conf in place, but don't listen with the ipmitool. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jussi Peltola Sent: zaterdag 15 maart 2008 16:19 To: misc@openbsd.org Subject: Re: FW: dmesg default color On Sat, Mar 15, 2008 at 04:10:58PM +0100, Erwin van Maanen wrote: Okay, let me try to be even clearer :) - If I set the bios to always, this results in weird data on the terminal. (hence my first question: can I use always in the bios for impi output, which apperently I can't) - If I set the bios to boatloader only and openbsd in boot.conf tty to com1: (com0 is the normal com port in this specific type of mobo it seems) : I don't see the kernel output but DO get a login prompt after the system is booted (so my question here is: could this be an ascii related output/translation problem) boot.conf has nothing to do with that, it's /etc/ttys. Are you sure 19200 is the correct speed, and did you try without 'stty' at all?
dmesg default color
Hello, while booting dmesg is in white on blue by default. How can it be changed? Thanks.
