home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!mcsun!Germany.EU.net!rz.uni-hildesheim.de!agsc!veeble.han.sub.org!gkminix!gero
- From: gero@gkminix.han.de (Gero Kuhlmann)
- Subject: Re: Serial communications problems
- References: <723765164snx@hamster.com>
- Organization: gkminix, Hannover, Germany
- Date: Thu, 10 Dec 92 03:41:08 GMT
- Message-ID: <1992Dec10.034108.280@gkminix.han.de>
- Lines: 27
-
- hwm@hamster.com ("Hartmut W. Malzahn") writes:
- > Hi again! I've got another problem with my Linux setup (SLS 0.98.5). I have
- > the second serial port (COM2 or /dev/ttys1) connected to my modem and the
- > third (COM3 or /dev/ttys2) to another PC via a null modem cable. I have
- > neither been able to connect to the modem into Linux nor does the null modem
- > give me any access.
-
- Are you using COM1? If yes, then COM1 and COM3 probably use the same IRQ. That`s
- not working on a standard PC platform. You have to patch the kernel source AND
- make different modifications to your hardware (adding a few diodes and
- resistors). Or you have to setup your serial cards to use different interrupts.
- Nevertheless you have to patch the kernel anyway.
-
- > I am using Qmodem under DOS on the other PC (386/40), and if I set the baud
- > rate to, say, 9600, and run "getty 9600 /dev/ttys2 &", for example, I get the
- > login message on the other PC just fine, but that's it then. No reaction
- > whatsoever to any characters I send to Linux from the other machine.
-
- Or is it just that you forgot to attach the DCD pin? The serial driver may
- get a false signal on that pin and send a SIGHUP to getty, which then aborts.
-
- Hope this helps. gero.
-
- --
- Gero Kuhlmann Zerberus: G.KUHLMANN@A-LINK-H.ZER
- Donarweg 4 SubNet: gero@gkminix.sub.org
- D-3000 Hannover 51 IN: gero@gkminix.han.de
-