I use inner modem to connect to the net. In NT4 before,it shows--AOpen FM56-PM 56k Speakerphone PCI Modem(COM3). Now I use win2k Adv Srv and RedHat 7.2 dual boot only. Win2k can use the same inner modem to surf the internet. It shows--HCF 56K PCI Modem(COM3). How can I config this modem on RH7.2? Will it conflict the setting of the modem in another OS(win2k's) on the same disk? I once read a book of Peter Norton,saying that maybe some versions of linux do not support inner modem. Does RH7.2 have some new features to support mine? Any ideas about the config procedure? Williams
Frank Carver
Sheriff
Joined: Jan 07, 1999
Posts: 6913
posted
0
The main issue with modems and Linux is whether the modem is a "real" modem or a "Winmodem". A "real" modem is the same as an external modem, just mounted on a card inside the PC. It has enough procesing power on board to handle all the messaging, and process "Hayes AT" commands sent from the computer. A "Winmodem" is a much simpler device, and relies on the Windows operating system to handle the "Hayes AT" commands from Windows applications. In general, Linux works fine with "real" modems, but finds "Winmodems" hard to handle, although there are attempts at Winmodem support available if you look around the net. The best thing to do when trying to configure hardware under Linux is to chech out the appropriate HOWTO document. In this case something like the "modem HOWTO" at: http://www.linuxdoc.org/HOWTO/Modem-HOWTO.html . I hope this helps.
Then where to check my this PCI modem whether is supported by RedHat7.2? I search the net but hard to find one. My modem is not a winmodem,right? Williams
When I check the AOpen site,it seems not support linux,but when I issue lspci -v in RH7.2,showing me--...Communication controller:CONEXANT unknown device 1036...IRQ 9...I/O port 9400[size=8].... It seems linux do find the AOpen 56k v.90 PCI PM.Any idea? Williams
Finding something and being able to use it are two different things. The BIOS/OS can "find" a device because it adheres to plug-and-play specs, and it can show its name because that's retrieved by plang-and-play from ROM on the device, but that doesn't mean it can connect a driver to it. Attempts are being made to support "Winmodems" - you can find info at http://www.linmodems.org . However, I recommend that you try and get a "real" modem. Not only is support much better, but there are reports that WinModems steal processing power from your CPU to run the modem.
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
williams Green
Greenhorn
Joined: Feb 05, 2002
Posts: 5
posted
0
Suppose it is a "real" modem,then what I need to do is just issue(* are data from lspci -v): setserial /dev/ttys* irq* port* autoconfig right? and then issue:minicom I'd use command line to config modem,anyone familiar with the next steps? I use dual boot win2ksrv/rh7.2,the setting in linux will not conflict with that of in win2k,right? But how about if I save setserial cmd in rc.local,conflict or not? Williams
Frank Carver
Sheriff
Joined: Jan 07, 1999
Posts: 6913
posted
0
I don't think setting the serial parameters in rc.local would interfer with operation of the modem under Windows :- all you are doing is telling Linux how to talk to the modem, not modifying the actual modem settings :- that's done during BIOS boot. To test if you have a usable modem, and have configured Linux to talk to it correctly; after you start minicom just type AT and the modem should reply OK If this works, you are good to go, and most Linux software should be able to access the modem correctly.
Guy Allard
Ranch Hand
Joined: Nov 24, 2000
Posts: 776
posted
0
At present, Linux support of Winmodems is in a rapid state of flux. Anything you try might (or might not) work. Frank's suggestion about minicom is very good. Luck, Guy
0
