serial port mystery

Bill McCormick wpmccormick at sbcglobal.net
Mon Apr 4 03:13:21 UTC 2005


Bill McCormick said the following on 4/3/2005 6:00 PM:

> Sometime ago I upgraded to FC3 from RedHat 9 to, among other reasons,
> get my VScom PCI 2 port serial card working.
>
> (RedHat 9 required a kernel re-compile)
>
> Anyway FC3 made it work. The two ports have been working for sometime on
> /dev/ttyS4 & 5. Now, inexplicably (after a reboot test) the 2 ports
> insist on using /dev/ttyS14 & 15.
>
> I removed my rc.serial ...
>
> <reference>
> [root at billinux ~]# cat /tmp/rc.serial
> setserial /dev/ttyS4 port 0xeca8 autoconfig
> setserial /dev/ttyS5 port 0xec98 autoconfig
> </reference>
>
> ... and still they come up as ttyS14 & 15.
>
> Somehow, the kernel must be doing this. But how? ACPI?  Where is the
> config?
> How might this have changed? yum?
> Can I still use a rc.serial?
> How can I get the ports permissions set to 666?
>
> <reference from: dmesg>
> ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 25 (level, low) -> IRQ 177
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS14 at I/O 0xeca8 (irq = 177) is a 16550A
> ttyS15 at I/O 0xec98 (irq = 177) is a 16550A
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> </reference>

I checked /etc/sysconfig/hwconf and found:

class: MODEM
bus: PCI
detached: 0
device: ttyS4
driver: unknown
desc: "Titan Electronics Inc VScom 200L 1 port serial adaptor"
vendorId: 14d2
deviceId: 8020
subVendorId: 14d2
subDeviceId: 8020
pciType: 1
pcidom:    0
pcibus:  0
pcidev:  4
pcifn:  0

I then ran $/usr/sbin/kudzu -p and it said:

class: MODEM
bus: PCI
detached: 0
device: ttyS14
driver: unknown
desc: "Titan Electronics Inc VScom 200L 1 port serial adaptor"
vendorId: 14d2
deviceId: 8020
subVendorId: 14d2
subDeviceId: 8020
pciType: 1
pcidom:    0
pcibus:  0
pcidev:  4
pcifn:  0

again, this device is a 2 port serial card. So now I'll reboot and see 
what port it gets assigned ...




More information about the fedora-list mailing list