Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: ed sharpe archivist for on July 15, 2001, 11:07:40 AM
-
Hi using us robotics isa card.. it trys to connect as i hear it click but does not dial. Yea though! this is the last thing to solve, I have everything else going on the lan!
thanks ed sharpe archivist for smecc
-
problem fixed.
We now have our server under test!
ed
-
Just a quick reminder for anyone else reading this (and having hopes raised!) that he is using an ISA card!!! Their PCI cards really DO NOT work under Linux in spite of discussions on 'Linmodems', etc. I have really tried hard to persuade an otherwise perfectly sound and latest model card to function ... with absolutely no joy! Red Hat even have (unofficially?) an .rpm script that seems to sort everything - not! So don't waste your time.
Surprisingly hard to find internal cards that DO work here in the UK - I have been using an old Pace ISA card with good results to date but need Class 2 fax for Fax2Send and have just tracked down a hopeful looking card from Scan in Bolton which they actually advertise as Linux compatible! Will report back when I receive and install it
-
yes it was a isa card! it is working now though!
this brings up an interesting point though, there must be pci cards that are not win modems also??
many of the new machines out there do not even have an isa slot.
another option would be an externail modem too.
ed sharpe
-
What did you do to get it working? I, like you, have only the modem left to get working before everything will be functional. I have a USR ISA modem set to COM4 and IRQ 5. I tried testing the internet connection from the console and from a network attached PC, but no go.
Cheers,
BB
-
I set mine up on com 3 with the irq that is norrmal for that port.
I tend to like to use com 3 as in the past eons I remembered having conficts in some manner when I would set modems for com 4
this may have been a comidy of errors for me though, as I have reason to belive the modem was working the whole time, however the line I was plugging in was from a phone with 2 phone lines, one of which I had disconnected eyars ago... the tip and rig that the usr was looking for may have been the dead pair! of course I can still use the phone as I just selected the other line.... there is also one number that is quite busy at my isp and once the line was changed that may have contributed to the problems!
it turns out I may have not really had a modem problem after all!
funny though before I arrived at this I tried all kinds of old 2400 baud modems, and externial hayes 1200 baud modem etc etc I had a mountain of these things retrived from my junk pile in the garage.... of course NONE of them seemed to be good! they probaby all are good but was as I mentioned abaove jsut the problem of the phone line wire pairs and then a overly busy number.
ed ( with lotsa egg on my face!)
-
Good technique for all modem problems is to use the 'minicom' program to get quick feedback - lets you see if the modem is responding to commands. I seem to remember that if you get no response you have set the wrong port and if you get a slow response you have the wrong irq (it may not be that simple however!). Basically just change these parameters at will with the 'setserial' command and then make sure you have altered the serial port that minicom is sending to accordingly.
Do search the internet for an rpm script published (unofficially?) by USR - I can't remember where I found it but it looked like it would do all the setting up automatically .... for an ISA card! Trouble is I was using a PCI one!! Further reminder - don't waste time trying to get PCI USR internal modems to work under Linux - they just don't, although I like them a lot for Windoze systems.
Incidentally Maplin here in the UK stock Actiontec PCI internal modems which seem the best Linux bet (class 2 fax, etc).