> In article <Pine.LNX.3.91.950928215423.443A-100000@ts.pcnet.ro> you write:
> >The problem is this:
> >We have a lab full of old dumb VT52s distributed on a FourPort, but they
> ...
> >what they send to the kernel is useless - it's strange, random chars.
>
> Ech, are you stuck in some sort of Linux-kernel time warp, or do you _really_
> mean that not only do 1.1.x kernels not work, but 1.2.x and 1.3.x also fail?
Yes, not only 1.1.x, but also 1.2.x and 1.3.x(tested with:1.1.54, 1.1.59,
1.2.3, 1.2.6, 1.2.8, 1.3.3, 1.3.25).
>
> In any case, we also use an AST FourPort under Linux, and it has always
> worked happily; no kernel modifications have been needed for a very long
> time.
>
> Get a recent kernel (1.2.10 or something), build it and boot it. Get the
> 'setserial' package. Use it to enable the 'fourport' option on the serial
> ports, and (if necessary) set the IRQ, port address, etc..
yeah, i know what to do, but the problem is like this:
when i boot into linux-1.0, they are *perfectly* working..
but when i boot into 1.2.3 or something(having done *no* modifications)
they fail to work correctly.
>
> From what it sounds like, you may have the port address correct, but not the
> IRQ, and you may not have the fourport option set.
I do have the IRQ *and* the port address set correctly, and i have
compiled kernels with fourport support.
Also, when the system boots, the kernel detects correctly the fourport card.
>
> Dan
Anyway, can you send me to <top@lbi.sfos.ro> the configurations on your
machine? Just in case it's a typo or something..
Tudor