Skip to contentSkip to conversation

Serial Ports

DISCUSSION Stephen Torri 3 participants 3 messages Sep 7, 2001 – Sep 22, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 10 lines · D. Stimits

Make sure your bios is set to "not plug-n-play aware". I have a Supermicro Dual P3 board that works fine (actually, 2) with serial mice. In the case of the modem serial port, I have to use setserial to get the characteristics I want, plus the setserial options seem to require speed_normal and skip_test to work correctly. Incidentally, if your board is based on the i840 chipset, you'll have to run noapic or it will die under some circumstances, such as heavy disk load, or rapid mount/umount of any filesystem (even a cdrom).

D. Stimits, [email protected]

I have noticed that serial ports change IRQ to either 3 or 4. There is no reason for this behavior. I have created a perl script to create a log containing the irqs assigned and their ioports. Is there anything else I could log that might unmask the problem?

So far if the serials are assigned to IRQ 4 then the sync with the palm pilot doesn't work (/dev/pilot = /dev/ttyS0). If its IRQ 3 then it does.

Stephen

#2 lore raw

From: "Stephen Torri" <[email protected]>

Quoted 4 lines

I have noticed that serial ports change IRQ to either 3 or 4. There is no reason for this behavior. I have created a perl script to create a log containing the irqs assigned and their ioports. Is there anything else I could log that might unmask the problem?

Try posting the contents of /proc/irqs and /proc/ioports, perhaps someone here will see something you don't.

..Stu

#3 lore raw
In reply to a message not in the archive
Quoted 8 lines · On 2001.09.06 16:27:06 -0400 Stephen Torri wrote:

I have noticed that serial ports change IRQ to either 3 or 4. There is no reason for this behavior. I have created a perl script to create a log containing the irqs assigned and their ioports. Is there anything else I could log that might unmask the problem?

So far if the serials are assigned to IRQ 4 then the sync with the palm pilot doesn't work (/dev/pilot = /dev/ttyS0). If its IRQ 3 then it does.

As I understand it, /dev/ttyS0-3 are set to industry standard values on startup (they are not probed). The values can be changed using the command-line utility setserial. You can specify non-standard values in an rc.serial conf file which will be read on startup.

The setserial manpage covers this is some detail.

HTH,
Ian

Signature · 2 lines
"God may have mercy.  We will not."
--Senator John S. McCain (R-AZ)