MN)" wrote:
>
> > VFS: Mounted root (ext2 filesystem).
> > IN%M.ve.Kzr.&3..boJr; 68k init
> > IN%M.Ent..Jr;.&asc*+b....
> > S
> > .Jr;.6.*j....9:. sysl:#
> > S
> > .Jr;...R4..seK*... i.+"
> >
> > Li......o:.root
> > [rz..ZM[7../rz.ls ..
> > l.Zd.S7..de....2.. e...2.. var....2.. usr....2..
> l.kL.nl.n bi....2.. rz...2.. r....2...
>
> You're using 2.4.0-test2-ac1-rmk2-np3, aren't you? =)
>
> (I thought I was losing it yesterday when both my Assabet and
> Neponset started to do this.)
>
> Back out to -np1; -np3 has some fairly substantial changes in
> the serial character driver which may require some
> sorting.
>
> -jd
I was going to suggest checking inittab on the ramdisk to see what the
gettys are doing. Looks like something is fooling around with the serial
port settings when the tty's are starting up. BTW my -np3 works fine except
for that problem Nico mentioned with keyboard escape sequences and the like
where two characters are sent back to back in quick succession. No trouble
with output, though, and this is at 115200, n, 8, 1. I need to track this
one down as we use serial I/O pretty extensively.
//Jeff
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
