On Fri, Jul 16, 1999 at 03:24:56AM -0700, Stephen Monroe wrote:
> To all that were helping me configure my modem and needed more information:
>
> Here is the complete output of "plog" (Fixhate is the computer's name):
>
> Jul 15 01:55:27 fixhate pppd[8750]: Exit.
> Jul 15 01:55:27 fixhate pppd[8753]: pppd 2.3.7 started by root, uid 0
> Jul 15 01:55:27 fixhate pppd[8753]: Device ttyS1 is locked by pid 8388
> Jul 15 01:55:27 fixhate pppd[8753]: Exit. ^^^^^^^^^^^
Ok, at this point it looks like something else is using the the device
ttyS1. What's running on pid 8388? Try "ps aux | grep 8388"
>
> Here is the complete output of "setserial -a /dev/ttyS1":
>
> /dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
> Baud_base: 115200, close_delay: 50, divisor: 0
> closing_wait: 3000, closing_wait2: infinte
> Flags: spd_normal skip_test session_lockout
>
Good.
<Sniped isapnp.conf section>
> I ran "ln -s /dev/ttyS1 /dev/modem" to make a link to my modem. I was told
> to run isapnp /etc/isapnp.conf
> at system startup, but I get the following (when I uncomment the BASE
> 0x02f8):
>
> Board 1 has Identity d7 ff ff ff ff 03 00 73 16: ESS0003 Serial No -1
> [checksum d7]
> Board 2 has Identity 3f 00 00 01 00 19 0c a3 30: LEC0c19 Serial No 256
> [checksum 3f]
> /etc/isapnp.conf:325--Fatal-resource conflict allocating 8 bytes of IO at 2F8
> /etc/isapnp.conf:325--Fatal-Error occurred executing request
> '<IMPLICIT>'-further action aborted
It looks like there is already a device at 2f8. I mentioned in one of these
modem related threads that most computers already have two serial ports
(ttyS0 and ttyS1) built in so internal modems usually have to go on ttyS2 or
ttyS3 (using addresses 3e8 or 2e8). It looks like you just confirmed that
this is the case for you.
>
> When I run isapnp /etc/isapnp.conf with the 0x0100 BASE uncommented I get:
>
> Board 1 has Identity d7 ff ff ff ff 03 00 73 16: ESS0003 Serial No -1
> [checksum d7]
> Board 2 has Identity 3f 00 00 01 00 19 0c a3 30: LEC0c19 Serial No 256
> [checksum 3f]
> LEC0c19/256[0]{LT 56k Modem }: Port 0x100; - - - Enabled OK
>
> Since the modem seems like it will work on Port 0x100, I change the port from
> 0x02f8 to 0x100 using setserial.
0x0100 is a pretty wierd address to use for a serial port. You can
sometimes get away with using unusual addresses but it's asking for trouble
later unless you know what your doing. I highly recomend you use one of the
standard configurations for an internal modem such as:
ttyS2 3e8 irq 4
ttyS3 2e8 irq 3
Once you've set the correct info in isapnp.conf you'll need to make sure
your 0setserial file matches.
>
> Here is the output of 'setserial -a /dev/ttyS1' before I change the base
> address:
>
> /dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
> Baud_base: 115200, close_delay: 50, divisor: 0
> closing_wait: 3000, closing_wait2: infinte
> Flags: spd_normal skip_test session_lockout
>
> Here is the output of 'setserial -a /dev/ttyS1' after I change the base
> address to 0x02f8:
>
> /dev/ttyS1, Line 1, UART: 16550A, Port: 0x0100, IRQ: 3
> Baud_base: 115200, close_delay: 50, divisor: 0
> closing_wait: 3000, closing_wait2: infinte
> Flags: spd_normal skip_test session_lockout
>
> When I initially run "pon" after I boot up I get:
>
> /usr/sbin/pppd: This system lacks kernel support for PPP. This could be
> because the PPP kernel module is not loaded, or because the kernel is not
> configured for PPP. See the README.linux file in the ppp-2.3.7 distribution.
>
> But then I type "modprobe ppp" and when I type "pon" again the above
> information does not appear.
>
> Nevertheless, I suppose it is possible the kernel is not configured for PPP
> since Debian was put on my box at my UA dorms where we have ethernet and that
> is what my friend probably configured it for.
>
Normally kerneld loads modules such as ppp automatically so you "shouldn't"
need to modprobe it but.... After you modprobe ppp do you get an error?
Type "dmesg" and examine the last few messages. After you run pon, try
running "lsmod" to see the list of modules installed.
If you put "ppp" in your /etc/modules file it's get loaded at bootup and
stay loaded but if you can't load it manually then something's wrong.
> Thankyou in advance for any help. Sorry this was so long.
Not too long at all, it's exactly the stuff we need to make this work.
--
Ray
