Modem won't connect
Thanks for your help with my gaphics problem, now maybe you can help me with my modem one! :D
I have a PCI modem called the Intel 536EP DataFax Modem. As far as I know, this is not a "WinModem". It is an actual hardware card which I installed myself. The trouble is, when I try to connect, everything goes fine until I get to a step that says, "Waiting for carrier" in the log. It waits for a while, then prints, "NO CARRIER" and hangs up, then it starts over again. I don't get it, I've gone over it again and again and all the settings are right for dialup (password, username, number...) What's wrong? |
Modem Problem
hello
well ur problem is simple "NO CARRIER" mean that the modem is not getting line check ur connection or cable again regards |
Well I can't imagaine why it can't find the line when Windows uses the same one without any trouble.
|
Problem Solved now
Ok well u said that your not having any problem with the line coz u have already used the same line with the windows....ok it shows that you have not yed configured your modem properly
|
Okay what should I do? What exactly is wrong?
|
I have the same modem chipset (intel 536ep is the chipset used under many mfrs names of internal pci modems) Actually I have two different PCI modems using that chipset. In 10 distros I have had NO luck getting it to work (on some I can connect, and even maintain the connection, but any attempt to input like in a form box, locks the system). I have several sets of drivers for linux from the two mfrs, and looking recently it seems they have withdrawn the linux ones. I would upload to my webspace if you like to try them. Good Luck. Although officially a newbie, I have been at the linux for awhile and had no joy with this winmodem (and yes, one mfr claimed it to be a hardware modem-maybe it is possible for the chipset to go either way, that I don't know enough about that). I have two external modems, an oldie and new one and no problems. Unless you are really strapped for cash, it isn't worth the aggravation of trying to get one to work, IMHO
|
There's a great little used computer store near where I live. I'll just go get a new (old) modem for Linux! Thanks a lot. Can you tell me any specific models I should NOT get?
|
I have an intel model 537-ep
it is in fact a winmodem but, intel makes drivers for it for a direct link to the uncompiled drivers: go here http://downloadfinder.intel.com/scri...7&DwnldID=6497 for a link to ALL the drivers (uncompiled/binaries) go here: http://downloadfinder.intel.com/scri...*&submit=Go%21 <EDIT> btw: I got my Intel 537ep drivers to work fine! The 536 should be no different, just make sure you have the kernel source installed, it's very easy to compile them. |
Scuzz, would be great if I could get either one of these winmodems going for a spare box or two. Thanks much for the links! The modems are just sitting gathering dust while I have two boxes that I would like to put some lightweight 2.4 kernel distros on. Will let you know what happens. I don't know why encore and the other mfr pulled the linux drivers for this chipset. At least they were nowhere to be found a few months ago on their sites. I tried what I had on knoppix and compiling failed. On kanotix modem couldn't be initialized. And on Lindows of all things it was recognized, even connected but locked the system. I believe I also had go's on Morphix and gnoppix, debian-based all and maybe that's what is making it so much harder.
Plant, I still think you can't go wrong with a nice external (I believe serial interface is preferred for linux over usb) and I at least had no trouble with either of mine. One ancient Practical Peripherals and a new Actiontec. My 2.6 kernel knoppix has no trouble either. Just make sure it has its own controller, I seem to remember USB ones that didn't so I guess that made them external winmodems of a sort. |
Well, thanks for showing me this, now I hate to say it, but I'm not entirely sure how to do this...
1. The readme says I need: Quote:
2. Quote:
Hmmm... maybe this isn't so hard, actually. I'm just not sure. :newbie: |
Plant, first off if you are using running suse 9.0, seems you would want the download from this link http://downloadfinder.intel.com/scri...7&DwnldID=6508
from the readme: 6 steps to install 1. login as ROOT 2. extract the archive into a directory with "tar -zxvf <archivename>.tgz" 3. cd into the directory it created. 4. Type: make clean 5. Type: make 536 6. Type: make install Step #2 creates a folder that is likely to be called intel536-4.68-s90-up if you use the suse download linked above. "cd" is the command to change to that directory (folder) you just created, for instance: cd /home/whatevertheusername/whereuextracted/intel536-4.68-s90-up |
and in answer to your question #1, kernel source headers for what you are running is essential when you compile things like this.
If you have a need to get online before you are comfortable getting into these areas, again I would recommend to get an external modem to get you connected with the least fuss. OTOH, this is a great way to learn and get your hands dirty so to speak - you will just need to do a bit more reading up on some of these basics. |
I'm trying to compile these drivers but the shell keeps saying "make: command not found." I tryed the ./configure command, but it said "./configure: no such file" What's wrong?
|
make: command not found
install your distro's development tools (g++,gcc,gdb,etc) |
Since you are using SuSE, there is another way: Just type
Code:
Attention: You have to set it up first, though. I use for my modem three initialization strings called in kppp Init1, Init2 Init3: Code:
|
All times are GMT -5. The time now is 09:52 AM. |