> What is the output of "ls -l /dev/ttyS*", "ls -l /dev/cua*" ?
> Is the serial port in-use when you try to configure it
> (uugetty or gpm running) ?
> Are your serial ports enabled in BIOS ? Is there IRQ or I/O
> conflicts (cat /proc/ioports) ?
> What is the result of "strace setserial <your parameter>" ?
> Are the failing ports software PNP modem ?
> Is serial compiled as module (".config" serial related lines) ?
> What is your hardware (Intel UP/SMP) ?
Etienne,
Here's a followup to what is going on with setserial. I restarted without
running isapnp, and loaded the modified serial driver (with the printk()'s
I added), ran isapnp, then tried running setserial to setup its port.
Here's what I got out of it:
Jun 10 09:06:17 medusa kernel: set_serial_info() failed, parameter info:
Jun 10 09:06:17 medusa kernel: new_serial.port = 2f8
Jun 10 09:06:17 medusa kernel: new_serial.irq = 3
Jun 10 09:06:17 medusa kernel: new_serial.type = 4
Jun 10 09:06:17 medusa kernel: new_serial.xmit_fifo_size = 0
This was with the command line
setserial /dev/ttyS1 port 0x2f8 auto_irq uart 16550A
If I tried to let it autocoonfigure the UART type, new_serial.type ended
up being 0. If the serial driver itself is determining the UART type, then
I guess that's okay, right? All I know for sure is the xmit_fifo_size
value is what's blocking the setting of the serial port parameters. If
anyone else has any other ideas, please let me know. FYI, I'm running
setserial v2.10.
Derrik Pates
dpates@kalifornia.com
dpates@acm.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu