Hello.
On 06/10/05 02:24, Svein Seldal wrote:
> Hi.
>
> I'm running getty. Still, if I remove the getty on ttyS0, the result
> remains the same. The lockup occurs somewhere after init has started (as
> previously) and remains until init 2 is run (when the syslogd/klogd
> kicks in).
>
> I am wil
Hi.
I'm running getty. Still, if I remove the getty on ttyS0, the result
remains the same. The lockup occurs somewhere after init has started (as
previously) and remains until init 2 is run (when the syslogd/klogd
kicks in).
I am willing to bet on interrupt problems. As it seems, 16 bytes is
Hello.
Two ideas.
1. What program is bound to ttyS0 in inittab? *getty? Nothing? What if
to change this (something to nothing or vice versa)?
2. Damned IBM PC interrupts? It may be deja vue, but it seems me that I
had same effect in Novell server 10 years ago; the reason was incorrect
combinat
Hi.
I have some strange problems during boot of my system:
I'm running stable (Sarge) with kernel-image-2.6.7-2-686 plus ditto-smp.
I have a Intel machine with a Intel P4 (family 15, model 4) @3GHz. I
have 1G of memory. My SATA HDD's are running software RAID-1 with LVM
(but that's probably i
4 matches
Mail list logo