HI !
> > Moreover try to give the -noinput option to all fbdev targets but one.
> Please don't. It's not necessary, and will most likely prevent
> finding the real bug.
Oh - I thought I remembered you suggesting this to someone else a while ago, so
I just repeated it. Maybe you fixed it in the meantime.
O.K. - the guy sent me an strace log and the interesting thing was, that it
really did set RAW mode twice, but it also did set back to ascii mode (once)
at the end. Unless the kernel has some kind of "counting" behaviour (which
would be silly IMHO) on that, I don't get how the console could stay screwed.
I have asked him back, if that was with noinput enabled or something.
A few wild guesses at what might cause it (you know the console code better
than me, so I think you'll find it more quickly than me digging through it):
What do you do with the old state of the terminal ? Do you save and restore
it ? In that case, it might be caused by overlapping opening/closing of the
subvisuals (i.e. open 1 sees xlate, sets raw, open 2 sees raw, sets raw,
close 1 sets xlate, close 2 sets raw ...).
We should check that behaviour anyway ... wait ... ooops - yes.
At least multi doesn't do a "bracketized" close ... tile not as well ...
I'll fix that tonight unless you have objections ...
CU, ANdy
--
Andreas Beck | Email : <[EMAIL PROTECTED]>
