serial console and kernel 2.4
I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18). This box has no display and use the serial console. Since the upgrade I can see the boot output on the remote console but I can't use the keyboard. Each time I press a key, an interrupt is seen by the no-display machine but no char appears in the console.
Today I've upgraded an another box to 2.4.7 with a similar setup and I've the same problem.
Is there something that I'm missing ? (something new with the kernel 2.4 that is required for a serial console that was not required with the 2.2 ?)
Is sombody else experienciong the same problem ?
Christophe
Signature · 6 lines
Christophe Barbé Software Engineer - [email protected] Lineo France - Lineo High Availability Group 42-46, rue Médéric - 92110 Clichy - France phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01 http://www.lineo.com
Hi!
I had the same problem and I attached you a patch how I'm working around this problem.
Reto
char/serial.c Thu May 3 09:29:34 2001 renamed from char/serial.c.orig Thu May 3 09:29:00 2001 +2 -2
@@ -1764,8 +1764,8 @@ /* * !!! ignore all characters if CREAD is not set */ - if ((cflag & CREAD) == 0) - info->ignore_status_mask |= UART_LSR_DR; +// if ((cflag & CREAD) == 0) +// info->ignore_status_mask |= UART_LSR_DR; save_flags(flags); cli(); if (uart_config[info->state->type].flags & UART_STARTECH) { serial_outp(info, UART_LCR, 0xBF);
Quoted 30 lines
I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18). This box has no display and use the serial console. Since the upgrade I can see the boot output on the remote console but I can't use the keyboard. Each time I press a key, an interrupt is seen by the no-display machine but no char appears in the console.
Today I've upgraded an another box to 2.4.7 with a similar setup and I've the same problem.Is there something that I'm missing ? (something new with the kernel 2.4 that is required for a serial console that was not required with the 2.2 ?)
Is sombody else experienciong the same problem ?
Christophe
Signature · 11 lines
Christophe Barbé Software Engineer - [email protected] Lineo France - Lineo High Availability Group 42-46, rue Médéric - 92110 Clichy - France phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01 http://www.lineo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines · christophe barbé
Is there something that I'm missing ? (something new with the kernel 2.4 that is required for a serial console that was not required with the 2.2 ?)
I've just started using 2.4.6 on both a Cobalt Qube 3 and Raq 4R (which use serial consoles), and they seem to be fine... although if the console isn't plugged in then it causes all sorts of problems so I've hacked around the kernel to allow the console to point at null...
I'm just about to upgrade to 2.4.8-pre2 if it all works...
Signature · 5 lines
- Steve Hill System Administrator Email: [email protected] Navaho Technologies Ltd. Tel: +44-870-7034015 ... Alcohol and calculus don't mix - Don't drink and derive! ...
Thank you very much.
It solves my problem.
I'm going to look in it to understand what is CREAD. certainly a patch need to be proposed here.
Christophe
Quoted 66 lines · Le lun, 30 jui 2001 17:18:12, [email protected] a écrit :
Hi!
I had the same problem and I attached you a patch how I'm working around this problem.
Reto
char/serial.c Thu May 3 09:29:34 2001 renamed from char/serial.c.orig Thu May 3 09:29:00 2001 +2
-2@@ -1764,8 +1764,8 @@ /* * !!! ignore all characters if CREAD is not set */ - if ((cflag & CREAD) == 0) - info->ignore_status_mask |= UART_LSR_DR; +// if ((cflag & CREAD) == 0) +// info->ignore_status_mask |= UART_LSR_DR; save_flags(flags); cli(); if (uart_config[info->state->type].flags & UART_STARTECH) { serial_outp(info, UART_LCR, 0xBF);Quoted 3 lines
I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18). This
box
Quoted 1 line
has no display and use the serial console. Since the upgrade I can see
the
Quoted 1 line
boot output on the remote console but I can't use the keyboard. Each
time I
Quoted 3 lines
press a key, an interrupt is seen by the no-display machine but no char appears in the console.
Today I've upgraded an another box to 2.4.7 with a similar setup andI've
Quoted 3 lines
the same problem.
Is there something that I'm missing ? (something new with the kernel
2.4
Quoted 1 line
that is required for a serial console that was not required with the
2.2 ?)
Quoted 15 lines
Is sombody else experienciong the same problem ?
Christophe
Signature · 8 lines
Christophe Barbé Software Engineer - [email protected] Lineo France - Lineo High Availability Group 42-46, rue Médéric - 92110 Clichy - France phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01 http://www.lineo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel"in
Quoted 4 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 6 lines
Christophe Barbé Software Engineer - [email protected] Lineo France - Lineo High Availability Group 42-46, rue Médéric - 92110 Clichy - France phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01 http://www.lineo.com
Quoted 10 lines · On Mon, 30 Jul 2001 16:54:53 +0200 christophe barbé…
I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18). This box has no display and use the serial console. Since the upgrade I can see the boot output on the remote console but I can't use the keyboard. Each time I press a key, an interrupt is seen by the no-display machine but no char appears in the console.
Today I've upgraded an another box to 2.4.7 with a similar setup and I've the same problem.Is there something that I'm missing ? (something new with the kernel 2.4 that is required for a serial console that was not required with the 2.2 ?)
It's probably a bug in your init.
I had the same, my init is busybox init, but maybe the sysv init has/had the same problem.
Init have to set (or unset i don't remenber exactly) the CREAD flag when opening the console in order to receive the input. Before 2.42 (or is it 2.4.3 ?) it seems that the kernel was not taking this flag into account for anything.
The proposed fix for the kernel is a workaround.
The bug has been fixed in busybox (around v0.50 or v0.51). (The guy working on busybox for lineo should be able to tell you. )
regards,
Signature · 1 line
Fabrice Gautier <[email protected]>
In article <[email protected]>,
Quoted 6 lines · Fabrice Gautier
Quoted 2 lines
Is there something that I'm missing ? (something new with the kernel 2.4 that is required for a serial console that was not required with the 2.2 ?)
It's probably a bug in your init.
I had the same, my init is busybox init, but maybe the sysv init has/had the same problem.
It has, was fixed in 2.80 which I put on ftp.cistron.nl/pub/people/miquels/software/ a few days ago.
It's probably wise to wait for your vendor to ship a new sysvinit package, or for all I know some vendors might have patched 2.78 already.
Mike.
Signature · 2 lines
"dselect has a user interface which scares small children" -- Theodore Tso, on debian-devel