Date: Sun, 08 Feb 2004 15:53:50 -0500 From: Jeff Gardner <freebsd@newgalaxy.net> To: Alex Teslik <alex@acatysmoof.com> Cc: list-freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: struggling with hylafax installation Message-ID: <4026A1DE.8060308@newgalaxy.net> In-Reply-To: <20040208073327.M69654@acatysmoof.com> References: <20040208045053.M14436@acatysmoof.com> <4025D085.4000306@newgalaxy.net> <20040208073327.M69654@acatysmoof.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Teslik wrote: > ---------- Original Message ----------- > From: Jeff Gardner <freebsd@newgalaxy.net> > To: Alex Teslik <alex@acatysmoof.com> > Cc: list-freebsd-questions <freebsd-questions@freebsd.org> > Sent: Sun, 08 Feb 2004 01:00:37 -0500 > Subject: Re: struggling with hylafax installation > > >>Alex Teslik wrote: >> >>>Oy, the second post to questions in the same day :( >>> >>>So, I bought new modem and got it "working", but only kind of - the modem is >>>not echoing commands back to the 'cu' or 'ppp' terminals. It is a USRobotics >>>5610B 56K Pro Modem. It is not winmodem and the system put it on sio2. >> >>Is this an internal or external modem? > > > Internal > > dmesg | grep 'sio[0-9]': > sio0: configured irq 2 not in bitmap of probed irqs 0x20 > sio0: <3COM PCI FaxModem> port 0xe000-0xe007 irq 2 at device 10.0 on pci0 > sio0: moving to sio2 > sio2: type 16550A > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > > > > >>>I made all the devices in /dev eventhough they already existed. >>> >>>I added a direct line to the modem in /etc/remote like: >>>cuaa2:dv=/dev/cuaa2:br#57600:pa=none >>> >>>I can connect to the modem like: >>>cu -l /dev/cuaa2 >>>or >>>tip cuaa2 >>>or >>>ppp (then 'term') >>> >>>I can type commands and see them. I type ATDT1234567 and the modem picks up >>>and dials. So I know it hears and understands me. But it never echoes back >>>result information. I never see an "OK" or anything from the modem in the >>>terminal. >> >>So you get nothing when you type 'AT' followed by enter with nothing else? > > > > Correct. > > > >>>The problem is that HylaFAX relies on these echo results to control its >>>communication with the modem. It is looking for those "OK"s. Does anyone have >>>any ideas on how to get the "OK"s working? I have gone through all of the AT >>>commands USR documents and I can't get anything. Is this a problem with 'cu' >>>or 'ppp' or 'tip'? The results are obviously going somewhere, but I don't know >>>where. >> >>And this makes me ask my first question. Is this internal or external? >> >> >>>The AT command set for this modem is documented (USR issues the same document >>>for all their modems - this is an online version from another model instead of >>>a PDF version that is posted with my specific model, but they are the > > same) here: > >>>http://www.usr.com/support/839/83909-ug/six.html >>> >>>This should turn on all echos (but does not): >>>ATQ0 E1 F0 >> >>These should at least get the result codes you need. Maybe try an at&f1 >>which is Load Factory 1, HW FC and see if that gets the OK working. The >>only thing I could do to mine to turn of the OK is Q1. > > > > Nothing with at&f1 or any of the factory settings. Do you have this modem? Are > you willing to share the steps you took to get it working properly? > > uname -a: > FreeBSD xxx.xxx.xxx 4.8-RELEASE FreeBSD 4.8-RELEASE #6: Sat Feb 7 16:57:02 > PST 2004 alex@xxx.xxx.xxx:/usr/obj/usr/src/sys/DUALP3-4_8_0-RELEASE i386 > > Thanks, > Alex > I have: sio0: configured irq 17 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <3COM PCI FaxModem> port 0xb400-0xb407 irq 17 at device 2.0 on pci2 sio0: moving to sio4 sio4: type 16550A running: FreeBSD genesis.at.home 5.2-CURRENT FreeBSD 5.2-CURRENT #15: Wed Feb 4 23:09:22 EST 2004 root@genesis.at.home:/usr/obj/usr/src/sys/CUSTOM i386 All I did is plug mine into a PCI slot and used the cu command you mentioned above and it simply worked. Before that I used it with ppp for dialup before I got my ISDN line. Maybe your modem is bad? Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4026A1DE.8060308>