Not so sure of that, Ben:
> Bullshit, sir.  The kernel defaults to the commonly used values at boot, and
> setserial is used to configure them as needed within the system boot scripts
Yes, I did the latter, added the pertinent "setserial" line into one of
the "init" scripts (and this did not help, I still needed Kppp to have
the modem go.)

But: When I re-installed the system (i.e., the distro), there _was_ a
section (in Mandrake 8.2) on network configuration where, for a dial-up
connection, I could type in both the "device" (/dev/ttyS3) _and_ the
IRQ.  And that solved it for good.

> All setserial is is a wrapper around the serial device
> configuration ioctl function, which'll return an error if some other driver
> has claimed the specified IRQ.  You should see this shown as "File or device
> busy" or somesuch, I believe.
Hmm. What I got on the former non-working arrangement (and what I still
get on this other, not yet re-done install) is an "error 35". I could
not find anything relevant which _would_ give an error number "35" -
the list in "setserial" stops with number 19.

Next time I'll be at that other machine I'll check that IRQ-list in
"/proc" again; but I remember it gave me "3" for that ttyS3 (the 2f8
port) and nothing which used IRQ 7; so the IRQ 3 setting did survive
the running of "setserial ... irq 7".
(If I'm not mistaken, one gets any IRQ indication in that list only if
it is/wa actually in use. And I looked for that lst after various
trials with the start-up script for pppd.)

I don't really believe in a conflict on IRQ 7, for the rest; when ths
system is booted up, the comm- and par-ports are "polled" but not
tested on their hardware (jumpered) IRQ settings. If the second
par-port (which would get a default IRQ of 7 _if_ used) then is never
activated, there wouldn't be an entry in the /proc's IRQ-list either.
So that IRQ 7 is let alone anc coul be safely used with another,
serial port. (And in fact there _is_ no problem with using Kppp.)

// Heimo Claasen // <hammer at revobild dot net> // Brussels 2003-01-20
The WebPlace of ReRead - and much to read  ==>  http://www.revobild.net

To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with 
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html

Reply via email to