RE: Modem replies to commands mostly not seen.
I have a USR sportster 14.4 external serial modem which works fine under FBSD 4.8. Dip switches 3-7-8 are set to 'on' which is down, all others are set to off which is up. 3 = display result codes 7 = load factory defaults 8 = smart mode Modem has to be powered on before you boot FBSD box modem is cabled to. Modem is found and listed in /var/run/dmesg.boot file. During PC post process a summary PC hardware config screen shows the irq's assigned to hardware. Check this summary screen to verify the irq assigned to modem is not shared with other hardware. If it is, go into pc bios to change, be sure bios plug-n-play option is disabled, and serial ports are enabled. I use TIP command to issue Hayes AT commands. If you get an OK response to AT command, then you are talking to modem just fine and it's working. If you still have problems, post dmesg.boot file and use the script command to log your TIP command test output to a file and post that also. Most PC's have 2 serial ports, try cabling modem to different port and test again. Can you run mswindows on the pc to verify serial port and modem work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gary W. Swearingen Sent: Monday, July 14, 2003 2:27 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Modem replies to commands mostly not seen. fbsd_user [EMAIL PROTECTED] writes: Sounds like you have echo turned off in the modems internal prom setting. Use Hayes AT command to turn on echo function of modem hardware. Did these modems you tested work ok in FBSD 4.8? I tried the external Sportster under 4.8 but after it wouldn't work, I upgraded to 5.1 to lower the chances of having to go through this again when I did switch. I have modem manuals and played with dip switches and lots of AT commands including ATE1 (keyboard commmands), ATF0 (I think that's only for data that the modem sends out the phone line), ATX4 (result codes), re-init commands ATZ, ATZ1-ATZ5, ATF1, and many others. I've been through this several times before (on Linux) and think I know what I'm doing (except I've never understood the interactions of stty and serial-port-using programs like terminal emulators. It's strange that ATI gives it's results if I press keys, but AT or $ don't. I've found a place to do my FAXing, so the pressure's off on getting this fixed. BTW, my other question was about the dmesg files, but I should have thought of the HISTORY_SIZE thing for at least the console. (/var/run/dmesg.boot has 943 lines of nothing I care about.) Someone suggested kern.consmsgbuf_size=16384. Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Modem replies to commands mostly not seen.
fbsd_user [EMAIL PROTECTED] writes: I have a USR sportster 14.4 external serial modem which works fine under FBSD 4.8. Dip switches 3-7-8 are set to 'on' which is down, all others are set to off which is up. 3 = display result codes 7 = load factory defaults 8 = smart mode Which my 14.4 internal's manual recommends for software flow control (which is recommended only if the cable doesn't support hardware handshaking which almost all cables do support). Except it recommends switch 5 be on/down too. It doesn't bother to describe the switches, but my other manual says it's for auto answer so it's position shouldn't matter for this problem. Of course, my internal modem has no switches at all, so it can't help with the internal modem problem. FreeBSD surely should support hardware flow control (it's in stty), but I guess I can try an XON/XOFF configuration; I don't have a distinct memory of trying that on the external modem. Modem has to be powered on before you boot FBSD box modem is cabled to. Now, THAT could be my problem in the case of the external modem. I thought the drivers were smarter than that; rebooting is nasty, when serial lines are hot-pluggable. I'll try the external modem again. again. Can you run mswindows on the pc to verify serial port and modem work. I've no mswindows to run, but I've tried three different serial ports on the motherboard and ISA card. I've probably tried the other things you suggested; I hoped there would be some hints about software configuration that I had missed. But I can do more experiments with other modems and other computers and Linux to determine whether the problem is in the hardware or software. Thanks for the hints. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Modem replies to commands mostly not seen.
Sounds like you have echo turned off in the modems internal prom setting. Use Hayes AT command to turn on echo function of modem hardware. Did these modems you tested work ok in FBSD 4.8? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gary W. Swearingen Sent: Monday, July 14, 2003 12:26 AM To: [EMAIL PROTECTED] Subject: Modem replies to commands mostly not seen. I hooked up an external 28.8 modem after continuity-cheking the cable but the lights didn't seem right, as I remember them. (I've not use my modem for several years.) Modem doesn't respond to terminal emulator commands and seems broken, so I throw in an internal (non-winmodem) Sportster (that I've just seen working OK under Linux). Boot message looks OK as it flashes by; it identifies the proper UART, IRQs, etc, (but not an ID string from the modem -- I don't know if that's expected or not). I hand-set the COM # and IRQ and made things match in /boot/device.hints. And it sort of works. I'm using /dev/cuaa3. When I run a terminal emulator (tip, seyon, and minicom, so far), I get the same behavior: 1) Each character typed isn't seen until I type the next character. 2) Giving it the AT command (or most others), it never says OK, but a few info commands, like ATI6 will slowly spit out their reply (even ending with OK) if I bang away on the keys, one or two characters per key. Looks like some kind of flow-control problem, but I've tried lots of fixes (using the terminal emulator's config controls) and always get the same behavior. I've even messed with some of the stty stuff, though I think that should be overruled by the terminal emulators (except maybe tip, which I barely know). Any hints? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Modem replies to commands mostly not seen.
fbsd_user [EMAIL PROTECTED] writes: Sounds like you have echo turned off in the modems internal prom setting. Use Hayes AT command to turn on echo function of modem hardware. Did these modems you tested work ok in FBSD 4.8? I tried the external Sportster under 4.8 but after it wouldn't work, I upgraded to 5.1 to lower the chances of having to go through this again when I did switch. I have modem manuals and played with dip switches and lots of AT commands including ATE1 (keyboard commmands), ATF0 (I think that's only for data that the modem sends out the phone line), ATX4 (result codes), re-init commands ATZ, ATZ1-ATZ5, ATF1, and many others. I've been through this several times before (on Linux) and think I know what I'm doing (except I've never understood the interactions of stty and serial-port-using programs like terminal emulators. It's strange that ATI gives it's results if I press keys, but AT or $ don't. I've found a place to do my FAXing, so the pressure's off on getting this fixed. BTW, my other question was about the dmesg files, but I should have thought of the HISTORY_SIZE thing for at least the console. (/var/run/dmesg.boot has 943 lines of nothing I care about.) Someone suggested kern.consmsgbuf_size=16384. Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
