Re: [hylafax-users] Modem wedged. A hardware problem? (fixed email)

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Aidan Van Dyk wrote:

> No,ttyS14 is *quite* normal in modern linux w/ modern modems.

Here's some dmesg output from a Fedora Core 2 (Linux kernel 2.6.10) 
system with a RockForce QUATRO+ ...

Serial: 8250/16550 driver $Revision: 1.90 $ 76 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
PCI: Found IRQ 12 for device 0000:00:0b.0
ttyS14 at I/O 0xe400 (irq = 12) is a 16550A
ttyS15 at I/O 0xe408 (irq = 12) is a 16550A
ttyS44 at I/O 0xe410 (irq = 12) is a 16550A
ttyS45 at I/O 0xe418 (irq = 12) is a 16550A
ttyS57 at I/O 0xe478 (irq = 12) is a 16450

Now maybe I'm doing something wrong, but those don't work... ttyS14, 
ttyS15, ttyS44, ttyS45, and ttyS57 do not work.  I do this:

setserial /dev/ttyS4 port 0xE400 irq 12 uart 16550A autoconfig ^fourport
setserial /dev/ttyS5 port 0xE408 irq 12 uart 16550A autoconfig ^fourport
setserial /dev/ttyS6 port 0xE410 irq 12 uart 16550A autoconfig ^fourport
setserial /dev/ttyS7 port 0xE418 irq 12 uart 16550A autoconfig ^fourport

and then ttyS4, ttyS5, ttyS6, and ttyS7 all work... and I suppose that I 
could have used ttyS14, ttyS15, ttyS44, and ttyS45 as the device names, 
but, I prefer to not.

So like I said, either Linux kernel 2.6.10 is not modern enough, or I'm 
doing something wrong.

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*