....
>After I figured out that I have a winmodem, I went ahead and bought a REAL
>modem (USR 5610). Today, I tried to configure it under Linux (RedHat 6.0).
This is good. I use a 3CP5610 also.
....
>Medium devsel. IRQ 9.
>I/O at 0x1040 [0x1041]
>
>2- I typed the following as suggested:
>setserial /dev/ttys1 irq 9 port 0x1040 ^fourport ^auto_irq skip_test
>autoconfig spd_vhi
No, don't use /dev/ttys1 or /dev/ttyS1, because it will likely confuse
itself with your already configured motherboard COM2. I've never set it up
your way, but I'd imagine that this is the bulk of your problem. You want
to use a COM port that's not being used already, perhaps /dev/ttyS2 or
/dev/ttyS3. My setserial command is:
/bin/setserial /dev/ttyS2 uart 16550A port 0xb800 irq 9
and it works very well. Using your /proc/pci information my setserial
command for you would be:
/bin/setserial /dev/ttyS2 uart 16550A port 0x1040 irq 9
This setserial command is the first non-hash line in my
/etc/rc.d/rc.sysinit file. I have it there so that anything needing the
modem in /etc/inittab will have access to it (which get's run before
/etc/rc.d/rc.local, there's bound to be a "better" place, though).
>3- I got the following error:
>/dev/ttys1: Input/Output error
This is the first indication that your setserial options were wrong.
>4- I also link /dev/modem and /dev/ttys1
link /dev/modem to /dev/ttyS2 or whatever you choose to use, but not
/dev/ttyS1
>5- to see the current settings, I typed the following:
>setserial /dev/modem
>
>and got this:
>/dev/modem, UART:unknown, Port:0x02f8, IRQ:3
This is the second indication that your setserial options were wrong; it is
still referring to something that is on 02F8 (COM2) IRQ3 - which is where
your motherboard COM port is, most likely.
>Obviously, minicom did not communicate with the modem as well.
>FYI, under windows the modem is on COM2 (initially it was COM5, I changed
>it to COM2) and IRQ 9.
....
You really shouldn't refer to Windows settings for linux configurations.
Sometimes you'll get it lucky, but you're asking trouble this way. Just
because Windows drivers will utilize this at COM2 doesn't mean that linux
will.
So, you could continue with your setserial command and disable the your
motherboard's COM port(s), or you could just change the /dev/ttyS1 to
/dev/ttyS2 (note also that I think that the capitalization there is
significant).
Lee Howard
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
