> 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,
-- Fabrice Gautier <gautier@email.enst.fr>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/