Date: Wed, 5 Jan 2005 10:25:33 -0500 From: Timothy Luoma <lists@tntluoma.com> To: "Donald J. O'Neill" <donaldj1066@fastmail.fm> Cc: freebsd-questions@freebsd.org Subject: Re: modem not responding to mgetty Message-ID: <0AAB74E3-5F2E-11D9-BE17-000D93AD26C8@tntluoma.com> In-Reply-To: <200501050841.03874.donaldj1066@fastmail.fm> References: <1E7FDB38-5E7A-11D9-AD10-000D93AD26C8@tntluoma.com> <200501050841.03874.donaldj1066@fastmail.fm>
next in thread | previous in thread | raw e-mail | index | archive | help
> Do you have a serial port on your computer? There's a 9 pin connector (nothing attached) that I'm not sure what it's for, a printer port, and mouse and keyboard connectors, otherwise they are all USB ports. (Hardware is NOT my specialty. This is a new Dell Dimension 3000, if that helps any.) > If you do, somewhere in dmesg it should be telling you that your modem > was moved to a different port. Below is the out put from my computer: > > donaldj ==> dmesg |grep "^sio" > sio0: <3COM PCI FaxModem> port 0x1490-0x1497 irq 3 at device 10.0 on > pci0 > sio0: moving to sio4 > sio4: type 16550A > sio0: <Standard PC COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled This remains all that dmesg shows: # dmesg |grep "^sio" sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled I'm starting to think that my modem (US Robotics that I salvaged from an old HP I had) isn't detected by FreeBSD on boot. If so, would I be better off getting a new modem that might be recognized? It's a 56k fax modem, IIRC what WinXP was telling me. (I tried to save $20 by not buying a modem installed by Dell, and I knew I was going to regret it...) > Also, look at /dev for more than cuaa0 > > donaldj ==> ll /dev | grep cua > crw-rw---- 1 uucp dialer 240, 128 Jan 1 09:55 cuaa0 > crw-rw---- 1 uucp dialer 240, 132 Jan 1 09:55 cuaa4 > crw-rw---- 1 uucp dialer 239, 160 Jan 1 09:55 cuaia0 > crw-rw---- 1 uucp dialer 239, 164 Jan 1 09:55 cuaia4 > crw-rw---- 1 uucp dialer 239, 192 Jan 1 09:55 cuala0 > crw-rw---- 1 uucp dialer 239, 196 Jan 1 09:55 cuala4 # ls -l /dev/ | fgrep cua crw-rw---- 1 uucp uucp 237, 128 Jan 5 10:04 cuaa0 crw-rw---- 1 uucp dialer 236, 160 Jan 5 09:42 cuaia0 crw-rw---- 1 uucp dialer 236, 192 Jan 5 09:42 cuala0 I'm not sure what that tells me. Should I be telling mgetty to use cuaia0 or cuala0? (Is there a good way to test a new /etc/ttys and mgetty config w/o doing a full reboot?) TjL
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0AAB74E3-5F2E-11D9-BE17-000D93AD26C8>