On Mon, Feb 23, 2004 at 10:31:59AM -0600, Mark Gillingham wrote:
>
>
> Why does dmesg report an extra zero in the ttyS* above (i.e., 00 and
> 01)? Is that my problem? Am I anticipating ttyS0 and ttyS1 and getting
> in actuality ttyS00 and ttyS01? If so do I create /dev/ttyS00 and
> /dev/ttyS01
On Sunday, February 22, 2004, at 08:25 AM, Mark Gillingham wrote:
On Saturday, February 21, 2004, at 05:30 PM, Bill Marcum wrote:
The BIOS settings for the serial ports should be clearly labeled.
Maybe your internal ports are disabled; try "dmesg | grep tty"
The result of dmesg | grep tty is:
tt
On Saturday, February 21, 2004, at 05:30 PM, Bill Marcum wrote:
The BIOS settings for the serial ports should be clearly labeled.
Maybe your internal ports are disabled; try "dmesg | grep tty"
The result is the same as the BIOS settings on a similar box:
ttyS00 at 0x03f8 (irq = 4) is a 16550A
tty
On Thu, Feb 19, 2004 at 04:23:35PM -0600, Mark Gillingham wrote:
> When I issue a setserial or statserial command on ttyS0 or ttyS1, both
> internal ports, the commands hang and I just ^C out. The commands on
> ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
> serial ports wh
On Thu, Feb 19, 2004 at 04:23:35PM -0600, Mark Gillingham wrote:
> When I issue a setserial or statserial command on ttyS0 or ttyS1, both
> internal ports, the commands hang and I just ^C out. The commands on
> ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
> serial ports wh
When I issue a setserial or statserial command on ttyS0 or ttyS1, both
internal ports, the commands hang and I just ^C out. The commands on
ttyS2 and ttyS3 behave normally. Since I mostly ignore the internal
serial ports when I installed, I bet I missed something. Something
might be amiss in BI
6 matches
Mail list logo
