Re: unable to connect to ttyS1
On Thu, 1 Oct 1998 [EMAIL PROTECTED] wrote: > Perhaps your modem is a PLUG and PLAY modem or a winmodem of some thought ? > > > Hi. I'm currently running a Debian 1.3 system, and I'm working on putting > > together a Hamm system to replace it. I'm trying to get a ppp connection > > running on an external modem plugged into COM2 of the Hamm system and I'm > > having no luck. > > > > First, I defined the connection and then 'pon' to start the connection. > > No dice. /var/log/ppp.log contained the following lines: > > > > pppd 2.3.5 started by root, uid 0 > > tcgetattr: input/output error (5) > > Exit. > > > > Ok, I went back a few steps. I pulled down the PPP-HowTo and slog > > through the advice it has (which isn't 100% the same as the default Hamm > > setup). I discovered that using Minicom, I didn't get any response to AT > > commands sent to /dev/ttyS1. > > > > I rebooted the system and use Lilo to boot MS-Dog. Kermit saw a modem on > > COM2 and I was even able to use it to dial my ISP and transfer some more > > stuff to my new system. So the modem/serial port/phone line *do* work. > > > > Back to Linux (stopping by the BIOS setup on the way to note COM2's I/O > > address and IRQ: 2f8, IRQ 3). I did a 'setserial /dev/ttyS1': > > > > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3 > > > > I searched the mailing lists, and everybody else who was having similar > > problems was using Plug-n-Pray internal modems. No responses seemed to > > apply to a built-in serial port. > > > > So I'm stumped. I'm guessing it's a conflict of some kind, but it's a > > little too subtle for my experience level. > > > > Any help would be greatly appreciated. > > What speed is your modem? Perhaps the port is talking faster than modem can listen if it's a slow modem? Kent
Re: unable to connect to ttyS1
[EMAIL PROTECTED] writes: > Perhaps your modem is a PLUG and PLAY modem or a winmodem of some thought ? Sigh. What's frustrating is this isn't the first person to ask this question. As I said in my post: > > I'm trying to get a ppp connection running on an external modem > > plugged into COM2 of the Hamm system and I'm having no luck. In case it was missed in the opening paragraph, I mentioned it again: > > I searched the mailing lists, and everybody else who was having similar > > problems was using Plug-n-Pray internal modems. No responses seemed to > > apply to a built-in serial port. Fortunately, I finally found the problem. My WD8003EB Ethernet Adapter (not a PnP device) was conflicting on IRQ3. Unplug the adapter, serial port works fine. Now I just have to find the docs for the adapter so I can shove that off onto another IRQ... Thanks to everyone who actually READ my post and sent me _constructive_ suggestions. -packy Packy AndersonDardan Web Assoc. 518/266-1226 CEO/Webmaster PO Box 94 www.dardan.com [EMAIL PROTECTED] Troy, NY 12181-0094 O- Localized advertising solutions for a World-Wide Web.
Re: unable to connect to ttyS1
Perhaps your modem is a PLUG and PLAY modem or a winmodem of some thought ? > Hi. I'm currently running a Debian 1.3 system, and I'm working on putting > together a Hamm system to replace it. I'm trying to get a ppp connection > running on an external modem plugged into COM2 of the Hamm system and I'm > having no luck. > > First, I defined the connection and then 'pon' to start the connection. > No dice. /var/log/ppp.log contained the following lines: > > pppd 2.3.5 started by root, uid 0 > tcgetattr: input/output error (5) > Exit. > > Ok, I went back a few steps. I pulled down the PPP-HowTo and slog > through the advice it has (which isn't 100% the same as the default Hamm > setup). I discovered that using Minicom, I didn't get any response to AT > commands sent to /dev/ttyS1. > > I rebooted the system and use Lilo to boot MS-Dog. Kermit saw a modem on > COM2 and I was even able to use it to dial my ISP and transfer some more > stuff to my new system. So the modem/serial port/phone line *do* work. > > Back to Linux (stopping by the BIOS setup on the way to note COM2's I/O > address and IRQ: 2f8, IRQ 3). I did a 'setserial /dev/ttyS1': > > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3 > > I searched the mailing lists, and everybody else who was having similar > problems was using Plug-n-Pray internal modems. No responses seemed to > apply to a built-in serial port. > > So I'm stumped. I'm guessing it's a conflict of some kind, but it's a > little too subtle for my experience level. > > Any help would be greatly appreciated. >
