Is it easier to just do a different modem than it is to instal linmodem drivers?

[Ranger_Ski]

This sure is hard. Just when I get one thing right, I get another problem. First RH9 didnt recognize my PCtel Micromodem, then I found a driver for it and attempted to install it only I didnt have a header right so I recompiled my kernal. After symlinking my linux 2.4.20-8 to a linux directory it installed. When I went to insmod pctel and insmod ptserial I came up with unresolved symbols error messages. Does anyone know if it is easier to install say a us robitcs modem on a PC card slot in lieu of using the on board micromodem? I am getting so frustrated that it is getting hard to type straight. As of now I am going to recomplie my kernal again after make clean and see if I can redo this whole thing. Any help would be GREATLY appreciated.

[Stween]

Originally posted by Ranger_Ski
When I went to insmod pctel and insmod ptserial I came up with unresolved symbols error messages.

An unresolved symbol message generally means that you're running a different kernel version to the one that you've tried compiling your modem drivers to, which would be the version of the source that /usr/linux points to.

Take us through what you've tried. Did you compile the kernel, add it to your boot manager (lilo or grub), and reboot *into the new kernel version* before trying to compile your modem drivers?

[Ranger_Ski]

Yes I compied my kernal. But I dont really know what compiling does except make a symlink from /usr/src/linux-2.4.20-8 to /usr/src/linux. I didnt change anything with xconfig, partly because I didnt want to take any chances on messing up. After the xconfig I typed Make dep and make clean followed by make bzImage. Everything was fine so I typed make modules. Next I typed mv /lib/modules/2.4.20-8 /lib/modules/2.4.20-8.old.

I typed moduels_install and everything was good to go. I didn't move it to the boot successfully and have had to reinstall linux a few times (due to my lack of knowledge and stupidity) The problem I get when I go to install the new compiled kernal into the boot all stems from this command line

mv bzImage vmlinuz-2.4.20-8

I get unable to stat bzImage.
(this is supposed to move the old kernal so I dont overwrite it at least that is what it says on the compilation page here in justlinux) so I skipped it. I figure what the hell do I need the old kernal for anyways.

I followed the rest of the way through and I ran into the System.map. After 30 mins and a reinstall I figured out that CAPS DO MATTER as in my System.map file the S is capitalized. So I moved it and and copied that bzImage and the System.map and all was well. I restarted, went to the zip drive where I have the PCTel drivers on it, and I went through that whole process.

I installed it to both /root/ and /usr/src/linux/ just to make sure it was in both places.

I typed that tar -zxvf pctel-0.9.6.tar.gz line to unpack the driver.

Then I cd to the pctel-0.9.6 directory
I type ./configure-with-hal=sis (seeing how I everything else is sis on the board and 0.9.6 is the only driver for micromodems)

The machine does its thing and I go through the whole process. When I do the insmod part I have to use insmod -f so because I have gcc 3 running and gcc is the compiler for the driver.

After I do that it takes and all is good or so I think that is when I get "known not to work.... taint kernal.... "and other things I was like $hit! what have I done. So I type minicom just to see if the drivers work. It ends up just hanging there I cannot enter ATX or ATI3. So right now I have reinstalled linux for time number 4 and I am awaiting someone that might have knowledge or see what I am doing wrong and tell me how to fix it. I have read and printed out so many how tos on this subject that I dont think I care bare to look at too many more. I hate the fact that I cannot even see what linux looks like on the net and the fact that I have no knowledge in the unix based operating systems.

[Ranger_Ski]

oh another thing 2.4.20-8 is the latest kernal right? I mean I do have the brand spanking new kernal so what am I specifically compliing?

[JohnT]

Originally posted by Ranger_Ski
This sure is hard. Just when I get one thing right, I get another problem. First RH9 didnt recognize my PCtel Micromodem, then I found a driver for it and attempted to install it only I didnt have a header right so I recompiled my kernal. After symlinking my linux 2.4.20-8 to a linux directory it installed. When I went to insmod pctel and insmod ptserial I came up with unresolved symbols error messages. Does anyone know if it is easier to install say a us robitcs modem on a PC card slot in lieu of using the on board micromodem? I am getting so frustrated that it is getting hard to type straight. As of now I am going to recomplie my kernal again after make clean and see if I can redo this whole thing. Any help would be GREATLY appreciated.

An "external" modem is the all-around best way to go with linux. The only configuring...... is your dial-up. A ZOOM modem is the best and not any more expensive to comparable 3COM, but with lightening protection through the phone line. Can't find one......let me know.

[barneyt]

Agree with John T.

Use an external serial modem for Linux (Mdk 9.1) and my internal PCI modem for XP. Both wok fine and do the trick!

Barney

[Ranger_Ski]

OK thanks you guys. ONe question the external modem that you descrbe is it USB or parallel? I am guessing a good USB2.0 would be the best route.

[drummerboy195]

ok, first things first, the kernel wouldnt boot cause you didnt put it into the boot folder. you need to "cp ./arch/i386/boot/bzImage /boot/mykernel" this copies the kernel image to the boot folder, and then you need to use whatever boot config utility red hat comes with to add it to the bootloader. you could do it manually, but its prbly easier for you to do it graphically.

second, the whole point of recompiling is to make changes to it, using xconfig or menuconfig, so that it runs better/faster/smarter. if you dont make any changes, then the new kernel is exactly the same as the old one.

third, no usb modems. everything ive heard has said they are worse than winmodems. serial is the only "real" modem connection.

[Ranger_Ski]

OK I will give that a whirl. I can only try right? I figure it this way. I am learning hands on. In your thread you refer to as "/boot/mykernel" is that what I should name it? or should I search for a kernal file in the /boot/

[Stween]

Originally posted by Ranger_Ski
OK I will give that a whirl. I can only try right? I figure it this way. I am learning hands on. In your thread you refer to as "/boot/mykernel" is that what I should name it? or should I search for a kernal file in the /boot/

You could quite happily call it 'mykernel' if you wanted, the only requirement is that your bootloader (probably lilo) knows what it's called and where it is. :)

Personally, I label mine by kernel version, so looking at /boot just now I see l2418 and l2534.

[JohnT]

Go serial, rather than USB. It's just one more thing to comfigure if you go USB. Serial is Plug n Go.

[barneyt]

The modem that I got was an external serial modem from ComputerGeeks. It was billed as Linux compliant... it was.

Barney

[irlandes]

Linux is about choice, the reason many if not most of us use linux. So, I sure don't complain if someone wishes to buy an external modem, rather than learn how to use winmodems with correct drivers.

However, it really does twist my crank when someone, anyone, spreads misinformation about the need for external modems in linux. This is pure nonsense when used in a general sense, which it usually is.

There clearly are some really odd modems which have no drivers available at this time. If you have one of them, yeah, you gotta' get another winmodem or an external modem.

However, many winmodems do have drivers available, and you are doing no one any favor if you state might as well give up and buy an external, don't even try, it's too hard, sigh -- just because YOU had problems with it.

I travel a lot. Am I gonna' buy an external modem bigger and heavier than my laptop and drag it all over the U.S. and Mexico when I can set up the internal winmodem in a few minutes? In a rat's butt!

My old laptop had a lucent modem. The state of the art now has what I call automatic rpm's for Redhat and Mandrake for lucent modems. Click on the file icon wherever you put it, and in a few seconds, you have a live, working modem ready to go. That is the experience most lucent owners have with Drake and RH.

An old desktop was just as easy.

My latest laptop, a Dell, has a Conexant hsf modem. it took a bit longer because I was led to believe it was a hcf modem, so I wasted some time. I am at this moment connected with that Conexant hsf modem with linux Drake 9.1.

You can find a lot on google; type in modem type, and linux, etc. Or, by memory, I think the source of info is www.linmodems.org

ltmodem.heby.de/ is a source for really good lucent drivers.

[robk40]

external serial modem is the way to go. I use it for both linux and the other os. and i'm sure not bored.

[Ranger_Ski]

iralandes, I did not mean to offend you. But as you might guess with my post I am new to linux. I have red all of the readme, FAQ, How-tos, and any other advice that anyone has given me, but I have had no success with my new modem. I simply asked what many NEWBIE Linux users ask "if it was easier to get a modem or to use my 'linmodem'". I am sorry if this invades your process of choice or if you think that I am suggesting in giving up. As I am an ARMY RANGER I dont give up too often, but when I am faced with a task of seemingly impossible ends I have to ask what the logical path of decision is. Since you have been all over the world (as have I) perhaps you could tell me what I was doing wrong and a means to correct it instead of merely stating your accomplishments and opions. I am great at windows, an expert at shooting things and people, good at programming, and LOUSY at linux although I am getting better. Perhaps next time you could better instruct me or give you opinion on what I was doing wrong instead of critesizing my question. I am happy that your modem works but perhaps you could read my other threads and help me to figure out what is wrong with mine. Remember as I applied to this forum it is technical support not technical "boasting and critisizing". I am here to learn and to be taught so why dont you teach instead of talk?

[JohnT]

Originally posted by Ranger_Ski
iralandes, I did not mean to offend you. But as you might guess with my post I am new to linux. I have red all of the readme, FAQ, How-tos, and any other advice that anyone has given me, but I have had no success with my new modem. I simply asked what many NEWBIE Linux users ask "if it was easier to get a modem or to use my 'linmodem'". I am sorry if this invades your process of choice or if you think that I am suggesting in giving up. As I am an ARMY RANGER I dont give up too often, but when I am faced with a task of seemingly impossible ends I have to ask what the logical path of decision is. Since you have been all over the world (as have I) perhaps you could tell me what I was doing wrong and a means to correct it instead of merely stating your accomplishments and opions. I am great at windows, an expert at shooting things and people, good at programming, and LOUSY at linux although I am getting better. Perhaps next time you could better instruct me or give you opinion on what I was doing wrong instead of critesizing my question. I am happy that your modem works but perhaps you could read my other threads and help me to figure out what is wrong with mine. Remember as I applied to this forum it is technical support not technical "boasting and critisizing". I am here to learn and to be taught so why dont you teach instead of talk?

He,he:p There are quite a few considerations to weigh and not all based on technical accomplishments. I personally prefer external modems, in this case Zoom, because of reliability and functionality...plus they have a great warranty. On the other hand winmodems are very inexpensive, somewhat reliable and they take up a pc slot. I too have traveled the world, but one thing I failed at is conducting a modem survey wherever I went. I hope I can make up for those short-comings here.

[barneyt]

Hi Irlandes,

When I first got started with Linux, I initially used RH 9.0 and had the same identical problem as many here.... with these Winmodems and Linux not being able to recognize them. After days of configuration changes and looking into the drivers at linmodem, I wrote both RH technical support and posted on other forums.

Basically, tech support said that Linux didn't support Winmodems and the sites for both RH and Mandrake did the same. They did, however, say that laptop modems were supported. At the linmodem website, I downloaded and installed the correct driver for my PCI modem, but after another day of fooling with it, and more forum postings, I still couldn't get it to work.

So, while I completely understand your aggravation with this post, I for one, like to hear a wide variety of experiences so that I choices and know that there are other alternatives. While my experiences with Linux is probably much less than yours, I found many ways to make things work. Serial modems was one way that I reduced my frustration level.

Barney

[irlandes]

Perhaps you need to cool down and read my posting again I did clearly state there are modems which cannot at this time be set up in linux. And, for all I know you may have one of them.

My statements were, I think, clearly addressed not so much to you as to those who responded with the comment too common on this URL that everyone should just get an external modem. they are doing a major dis-service to the linux newbies, many of whom will in time be able to use the winmodems already present in their machines. Detractors of linux often point -- incorrectly -- to the need to buy another modem as a reason not to use linux.

there is no better way to demonstrate a point about anything except to point out one has personally done what they say cannot be done. You take that as boasting. That is your problem, in my opinion.

When I was in the Army in the 60's, I served at times as squad leader. We had a function called "demonstrator". When I was assigned to train others on something, he was the one who did things as I described them, and at times, I was demonstrator for others. I have no other demonstrator; when I am talking about something I did, I must use my own experience.

Your heated response tends to show you as an impatient, hotheaded person, WHICH DOES NOT MEAN YOUR MODEM HAS AN AVAILABLE DRIVER. Linux takes patience. Your heat and quickness to act without thinking is a great survival tool in the Army Rangers. it is counter-productive for linux.

I will bookmark this thread, and come back when I get time later tonight, and see what I can find for you -- though I did point out the places to go for information. In linux, it is better to learn as much as possible. and, I did give you the places to go, which in linux is usually the best response for any problem.

If you choose to install another internal modem -- another valid choice -- be sure to get one with a lucent or aegere (sp?) chip,a s they are the easiest to set up.

Note also that these postings are commonly read by other newbies, even months later, and so part of posting here is to provide information for those who may come next month or next year, using the search function within the URL. I have posted a large number of responses, and frankly write with future users in mind. This was a perfect topic for others, and the reason I stated it as I did is to try to encourage those who might be mislef by statements by others that one should use external modems;

I thank you in these troubled times when so many are frightened for your service to your nation and to our mutual security. My generation, my buddies in the Army of the 60's, were not treated as well as yours, and I am glad things are better now and that we had no serious losses in iraq as my generation experienced when I was in.

[irlandes]

I just typed in:
"pctel micromodem"

into a google window, and got 1,310 hits, including HOW-TOs. I usually recommend newbies first hit google for most efficient usage of time and resources.

In many cases, problems will have to do with kernel versions v. version used in creatind drivers.

Correction: that should have been:

"pctel micromodem" linux

which gives 989 hits, many of which should help you.

Note to Army Ranger:

In these forums, often responses below your original posting will be in response to someone else's response, not to yours. Sometimes even on subjects unrelated to the original posting. And, sometimes others will get in a cat fight, or flame-war about something.

[bones996]

I was just looking at the zoom website & was wondering if the external USB modem was linux compatible. I saw that it supports windows but said nothing about linux & I don't have a serial port so I thought this might be my best bet. Also I have an internal conexant modem & since I installed it from the source binary from linuxant.com I haven't had any problems with it, unlike when I installed from the generic binaries - my system would freeze up about once a day:mad:

[slapNUT]

Your first mistake was recompiling the new kernel. All you needed to do was to install the kernel sources then build the driver for the current kernel.

I would recommend a little more effort into the winmodem driver before you go and buy a serial.

Ancient Hawaiians say, "You'll get much more satisfaction knowing you solved a problem than knowing you successfully avoided a problem."

[Ranger_Ski]

Thank you all for your posts. It just so happens that I have a lucent modem. After a few days of roofing I think that tonite is the night to get this thing going. I will keep this thread posted as I continue this operation. After I do that I will "attempt" to build the modem driver.

Oh irlandes no hard feelings. I too was a squad leader and we practice the "demonstrator post!" techniques still today.

[slapNUT]

It just so happens that I have a lucent modem. You are in luck then. The driver for the Lucent chip is probably the best supported WinModem chip around. I have been using a Lucent Technologies WinModem for years.

So not only is the chip supported but many Linux users are using it so they can help you install the drivers. Actually it practically installs itself.

[CrashTestDummy9]

Originally posted by JohnT
An "external" modem is the all-around best way to go with linux. The only configuring...... is your dial-up. A ZOOM modem is the best and not any more expensive to comparable 3COM, but with lightening protection through the phone line. Can't find one......let me know. Only thing I disagree with is the dialup suggestion...Get a DSL external modem and quit fooling with dialup.:D

[RWiggum]

<soapbox>A great suggestion to the few folks who actually have it available to them. I'd readily pay $50 a month for broadband. Unfortunately, I can't even get cable TV on my street, much less DSL or cable internet. Dialup will just have to suffice for most of us for quite some time to come. Most broadband providers have halted expansion of the service because they don't want to spend the capital on infrastructure with the economy in a slump.</soapbox>

Back to the topic at hand:
I've got a Linux driver for the Lucent Winmodem in my laptop, and I also bought an external USR Courier V.everything Corporate - the Cadillac of modems. They retail for about $200, but I yanked one off of eBay for $40. I don't think the seller knew what he had. I only purchased the external after my internal hardware modem died. It's difficult to ascertain a Winmodem's chipset (and therefore, Linux compatibility) before purchase, and true internal hardware modems are becoming hard to find. If you have to buy a new one anyway, an external is a good choice. If you already have a Winmodem - or your laptop has one entombed in it - it's worth attempting to get it running with a Linmodem driver. I agree with irlandes, don't just immediately write off your Winmodem and try to fix the problem with money.

[slapNUT]

<soapbox>A great suggestion to the few folks who actually have it available to them. I'd readily pay $50 a month for broadband. Unfortunately, I can't even get cable TV on my street, much less DSL or cable internet. Dialup will just have to suffice for most of us for quite some time to come. Most broadband providers have halted expansion of the service because they don't want to spend the capital on infrastructure with the economy in a slump.</soapbox> Ahhh sooo. You live in Hootersville too. I was going to comment about that "Just get a DSL modem post" but I bit my tongue. I may bite the bullet one of these days and go satellite, cause I fear DSL may never make it to this neck of the woods.

[Ranger_Ski]

Yeah I hear you both. Why is it that us country bumpkins all have high speed comps great OS and no access to the fast stuff without the satellite plunge.

[bs_texas]

Originally posted by CrashTestDummy9
Only thing I disagree with is the dialup suggestion...Get a DSL external modem and quit fooling with dialup.:D

Broadband snob!! :p

Man, I wish I had broadband out where I live.

Oh, and I had modem problems with a PCI US Robotics modem last year, so I took JohnT's advice and bought a Zoom external serial modem. Works like a champ. Never falters. Best 56K performance I've ever had.

regards...

woo hoo - it's still there:
http://www.justlinux.com/forum/showthread.php?threadid=81739

[JohnT]

Originally posted by bs_2003
Broadband snob!! :p

Man, I wish I had broadband out where I live.

Oh, and I had modem problems with a PCI US Robotics modem last year, so I took JohnT's advice and bought a Zoom external serial modem. Works like a champ. Never falters. Best 56K performance I've ever had.

regards...

woo hoo - it's still there:
http://www.justlinux.com/forum/showthread.php?threadid=81739


Glad to hear it. Can't stress enough the dependability of ZOOM. The "only" modem with lightning protection (over the phone line).

[dlausevic]

The modem I bought <specifically so I could throw windows out the window> is an internal PCI controller based modem that I bought for around $30 at Fry's. I read the hardware requirements and it listed Linux. So, I took it home, installed it, installed linux. It saw and configured my modem during the install. I didn't have to play with any settings whatsoever. Once I setup my connection for KPPP, I haven't looked back. That $30 purchase was a great investment.

[JohnT]

Originally posted by dlausevic
The modem I bought <specifically so I could throw windows out the window> is an internal PCI controller based modem that I bought for around $30 at Fry's. I read the hardware requirements and it listed Linux. So, I took it home, installed it, installed linux. It saw and configured my modem during the install. I didn't have to play with any settings whatsoever. Once I setup my connection for KPPP, I haven't looked back. That $30 purchase was a great investment.

You should list the make and model number, so that others can benifit from your experience.

[Ranger_Ski]

The model number is ATS 127A and it is made by Atech

[Ranger_Ski]

Well new modem same issue. When I installed the new modem linux recognized it as a Lucent winmodem (which it is) and it configured it, but when I went to run the internet configuration utility it says no modem found. If it saw it to configure it should it not be there or must I start the hunt for a lucent modem driver.

[dlausevic]

Originally posted by JohnT
You should list the make and model number, so that others can benifit from your experience.

You're right, stupid moi. When I go home tonight, I will post my modem stats. And as a matter of fact, when I went to get the modem, there were 4-5 other controller based modems to choose from. I simply picked the cheapest one in the lot. So, if anyone has a Fry's nearby, they should be able to find a selection for controller based modems. My winmodem is now wedged under the door in my school's computer lab to keep the door open (a neat little doorstop don't you think).

[slapNUT]

When I installed the new modem linux recognized it as a Lucent winmodem (which it is) and it configured it, but when I went to run the internet configuration utility it says no modem found. Well Linux can recognise winmodems but I don't know of any distros that actually have the driver for a Lucent Winmodem. The driver has "non GPL" code in it and will taint the kernel, no big deal, but you need to download the driver or look for a driver made for your distro's kernel.

[Ranger_Ski]

And so it begins again. Different modem same problem. I will try to find the driver for this one, but I am about to waste the 30 bucks on a new modem supported for linux

[dlausevic]

Originally posted by JohnT
You should list the make and model number, so that others can benifit from your experience.

My modem is:

Actiontec 56K Internal v.90/92 PCI Call Waiting Modem

Running off the Lucent modem chip sets.

The side of the box lists linux among the requirements. And I'm typing this message using a computer running online with the modem. The init string for KPPP is:

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0^M

[Ranger_Ski]

Thanks for the input Daniel. Did you have to make the modem drivers for that particular modem, or is it a harware modem?

[dlausevic]

Originally posted by Ranger_Ski
Thanks for the input Daniel. Did you have to make the modem drivers for that particular modem, or is it a harware modem?

No sweat. It is a controller based card <or hardware based>. That's what the lucent chipset is all about. It runs about $30 at Fry's. Maybe $40.

[dlausevic]

Oh, and it comes in a purple and black box.

There is a gold oval with the words, "Controller-based Improves Performance on Older PCs See back for more details" inscribed.

[cs25x]

I had a bit of trouble with a conexant thingo,
yep, it is hsf but detected as hcf. Common
problem.
It works very well, in fact it is consistantly
better under linux than under windozze.
But you need something above a 500Mhz
box to make it run.
There are some things you have to be
careful of. First, is the symlink from
/dev/modem to your /dev/softmodem.
Is it there?
Second since you are actually adding a
device, you might have to reboot to
get the thing going.
When you build it, you need your linux
headers, at least, but that is indicated
when you build the modem.

[Ranger_Ski]

Thanks I will check it out. The Atech modem that I have has lucent chips but doesnt have a linux driver. I am just so tired of pi$$ing with this thing.

[Ranger_Ski]

I am not sure but I can check. Where did you learn to build software modems? Is there a better tutorial to better inform me as to what is what and what each step means. I have read the HowTos on the PCtel modem (I counted at least 4 versions with varying degrees of technicality.) I basically follow each step. The chief problem I had was that the software driver that I use to install is written to write into the /usr/src/linux directory. My Distro does not have a /usr/src/linux/directory mine has a /usr/src/linux-2.4.20-8 directory. So I compiled my kernel in order to get the linux directory. However after playing around I found the I can just create a linux folder and copy the contents of the linux-2.4.20-8 folder to it (a lousy hack but effective in continuing with the driver install) After I do that, I do this:

type uname -r to make sure that I am in 2.4x kernel for the pctel-0.9.6 driver.

type tar -zxvf pctel-0.9.6.tar.gz to open the tarball and create the pctel-0.9.6 directory, I do this all as root and from the /root/ directory.

type cd pctel-0.9.6 to get to the pctel-0.9.6 directory

type ./configure --with-hal=sis because I have a sis chipset ***Question could I also type pctel1789 because that is the model of my MicroModem (on a highrise)***

After typing the ./configure line everything goes smoothly **Note if you do not create the linux directory either by compiling the kernel or the way I mentioned you will get an error modversions.h is missing is the error. I am open to anyone's ideas on another way to eliminate that error**

type make and everything goes again. This is where I start to get errors. I think 2 times out of the 10 or so that I have tried I have not gotten errors

type make install and everything goes again

type insmod pctel followed by insmod ptserial each of these tells me that the drivers do not exist in the mod folder**Anyone have a clue as to what I am doing wrong here?** I also note that if I use the insmod -f pctel and insmod -f ptserial instead of insmod pctel and insmod ptserial it does go through

And this is where I am. That is what I did step for step and the source of documentation that I was using was found here (http://www.peacefulaction.org/sayamindu/pctel.html)

I apologize is I sound like an idiot to most of you experienced users and please by all means guide me if I am astray. I rather learn from your mistakes then to repeatedly learn from my own.

[dlausevic]

Hey, email me at moi@e-dan.net. I will work with you to get your modem going.

[Ranger_Ski]

OK will do. just let me know if you need the driver file or anything like that.

[JohnT]

The chief problem I had was that the software driver that I use to install is written to write into the /usr/src/linux directory. My Distro does not have a /usr/src/linux/directory mine has a /usr/src/linux-2.4.20-8 directory. So I compiled my kernel in order to get the linux directory.

CD into the directory /usr/src and make a "symlink" to linux-2.4.20-8 , this is where your linux directory comes from. The command "ln -s linux-2.4.20-8 linux" will get you there.

[Ranger_Ski]

JohnT I already did it but I still had to compile the kernal again. The final thing I need to do is to find the pctel.o and ptserial.o files. I am thinking that the make install and make didn't put them where it should. When I scroll up to the part that flies by I see some things that indicate that those two files should be loctated in /root/pctel-0.9.6/usr/ptserial or another location such as /lib/modules/2.4.20-8/misc/ I can find the ptserial.o in the pctel directory (that was originally created when I decompressed the tarball) but I am clueless as to where the pctel.o is?

Another question I found a way to configure the kernel with grub in justlinx should I do that and then try to build the driver?

[MarcD]

I have tried to set up winmodems in the past, but I have not been successful, so I do not use them, even when I set up MS Windows systems. I currently use the US Robotics Performance Pro internal modem in 2 different Linux systems, successfully, no software problems at all. Check the package to make sure that Linux compatability is guaranteed. (This hardware was somewhat expensive, but the price has recently gone down at Walmart.)

The winmodems will always be inferior to controller-based modems, because the winmodems do not have a standard interface to the main system; each modem is different. The issue of standard interfaces is the key to the problem.

Whether you choose internal or external is a trade-off depending on what you want. The internal saves space and cabling; the external has the advantage that you can power-cycle it if it gets hung up.

In general I believe that getting better hardware is the correct choice in the long run, rather than wasting weeks of effort trying to fix up problems in software. (I recently went through a similiar experience with an old graphics card. It looked like there was a software problem, but a new graphics card fixed all the problems.)

[slapNUT]

I am not sure but I can check. Where did you learn to build software modems? Is there a better tutorial to better inform me as to what is what and what each step means. I have read the HowTos on the PCtel modem (I counted at least 4 versions with varying degrees of technicality.) I basically follow each step. The chief problem I had was that the software driver that I use to install is written to write into the /usr/src/linux directory. My Distro does not have a /usr/src/linux/directory mine has a /usr/src/linux-2.4.20-8 directory. So I compiled my kernel in order to get the linux directory. However after playing around I found the I can just create a linux folder and copy the contents of the linux-2.4.20-8 folder to it (a lousy hack but effective in continuing with the driver install) After I do that, I do this:
The proper way is to make a symlink like JohnT said. If it didn't work then you didn't have the symlink set up correctly. This is pretty much standard practice and is in the kernel README.

type uname -r to make sure that I am in 2.4x kernel for the pctel-0.9.6 driver.

type tar -zxvf pctel-0.9.6.tar.gz to open the tarball and create the pctel-0.9.6 directory, I do this all as root and from the /root/ directory.

type cd pctel-0.9.6 to get to the pctel-0.9.6 directory

type ./configure --with-hal=sis because I have a sis chipset ***Question could I also type pctel1789 because that is the model of my MicroModem (on a highrise)***
I would try ./configure --help and see what it says. There is also probably an INSTALL and README file with the driver which might tell you what to do.

After typing the ./configure line everything goes smoothly **Note if you do not create the linux directory either by compiling the kernel or the way I mentioned you will get an error modversions.h is missing is the error. I am open to anyone's ideas on another way to eliminate that error**
Once again the standard practice is to create a symlink /usr/src/linux -> /usr/src/linux-<version>

type make and everything goes again. This is where I start to get errors. I think 2 times out of the 10 or so that I have tried I have not gotten errors
If you get errors then make install will not work. The best thing to do is start over with make clean. If that doesn't help then remove the directory and start with untarring the source tarbal.

type make install and everything goes again
Once again make install will not work if all the preceeding steps did not work

type insmod pctel followed by insmod ptserial each of these tells me that the drivers do not exist in the mod folder**Anyone have a clue as to what I am doing wrong here?** I also note that if I use the insmod -f pctel and insmod -f ptserial instead of insmod pctel and insmod ptserial it does go through
Did you do depmod -a first?
Try again from the start and before doing insmod do a depmod -a

And this is where I am. That is what I did step for step and the source of documentation that I was using was found here

I apologize is I sound like an idiot to most of you experienced users and please by all means guide me if I am astray. I rather learn from your mistakes then to repeatedly learn from my own.


MarcD
The winmodems will always be inferior to controller-based modems, because the winmodems do not have a standard interface to the main system; each modem is different. The issue of standard interfaces is the key to the problem.To answer that rediculous reply I'll borrow a quote from www.linmodems.org

Id Software's John Carmack has posited that a linmodem may be able to have lower latency than a controller-ful modem. This is an issue of great importance to real-time gamers, as the slightest decrease in latency translates into a higher score.

Russ Nelson writes: A lot of people claim that a Winmodem has no place in a Linux box. I disagree. There are many applications for a Winmodem if you stop thinking of it as a modem, and start thinking of it as a telephone interface:

Think telephone emulation (put the audio card into full duplex, and talk to the linmodem with it).
Think telephone with a backspace key (use the linmodem to dial for you).
Think smart telephone: "That line is busy. Do you want me to retry in five minutes?"
Think "voice dialling".
Think "soft pbx". Equip enough machines in an office for all the outside lines. Then do IP telephone inter-office, and go to a linmodem when you need an outside line.
Think answering machine.
Think pager interface. Your answering machine takes the call, phones your pager company and pages you).
Think "contact database with integral dialler, and answering machine recognition".
Think "call recording with no off-hook click".
Think message detail recorder (basically a record of all time spent on the phone. Great for billing.
None of these require more CPU than a 386.


Notice the last statement about the 386 CPU!

[CrashTestDummy9]

just an idea...Sams club has a generic Lucent Winmodem for about 15 bucks...it say on the box its "Linux Compatible".

Hardware DSP too.Try it and see...in WinXP it installs on first boot.Kinda nice since ive had as many problems with modems in Windows(9x-XP) as I could ever have in Linux.

Plug and play my a$$.

[JohnT]

Think telephone emulation (put the audio card into full duplex, and talk to the linmodem with it).


At this stage of configuration even a whisper to the monitor is not unusual.:p

[JohnT]

Think telephone emulation (put the audio card into full duplex, and talk to the linmodem with it).


At this stage of configuration even a whisper to the monitor is not unusual.:p

[RBUL]

God bless you for tryin...with all the modem driver gobledygook....you have more patience than me...I have always used an US Robotics 56K external modem....no problems whatsoever works better in Linux than Windows in fact...with everyone going to the fat pipe broadband there are plenty of used units out there floating around attics and garages...I bought a second unit at a yard sale for three bucks(brandy new at any comp store $99.00).......think of it as a recycling project.........leave all your troubles behind and save your patience for configuring your Xserver(this will truly scramble your brain)....ain't it fun?.......

[RBUL]

God bless you for tryin...with all the modem driver gobledygook....you have more patience than me...I have always used an US Robotics 56K external modem....no problems whatsoever works better in Linux than Windows in fact...with everyone going to the fat pipe broadband there are plenty of used units out there floating around attics and garages...I bought a second unit at a yard sale for three bucks(brandy new at any comp store $99.00).......think of it as a recycling project.........leave all your troubles behind and save your patience for configuring your Xserver(this will truly scramble your brain)....ain't it fun?.......

[RBUL]

God bless you for tryin...with all the modem driver gobledygook....you have more patience than me...I have always used an US Robotics 56K external modem....no problems whatsoever works better in Linux than Windows in fact...with everyone going to the fat pipe broadband there are plenty of used units out there floating around attics and garages...I bought a second unit at a yard sale for three bucks(brandy new at any comp store $99.00).......think of it as a recycling project.........leave all your troubles behind and save your patience for configuring your Xserver(this will truly scramble your brain)....ain't it fun?.......

[JohnT]

Consider....... triplicate post . Although a great deal on a modem, I'm afraid you were to late to avoid it. (eg:brain scramble):p

[GavinX]

I am using a fairly old US Robotics 56K internal modem on Drake 9.1. Used it on Hat 8 and 7.3. Never gave me any trouble, it was recognized immediately by all three OSes. As a matter of fact that is what I'm using at this moment.

What I realize is that modems with chipsets that were developed before 98 or 99 will generally work well under Linux without any need to tweak anything. If I were you, I would try hunting down one. Best of all, it may cost less than 15 bucks!

[louis_b]

I recently bought a Compaq Presario 1500 with a PCI modem (Conexant HSFi V92 Mini PCI) The notebook was running XP, so I was able to get all the relevant details concerning the modem. Without going into all of the details of the installation, I resized the Windows partition down to 10 gigs and installed Mandrake 9.0 in the remaining 25 gigs. Everything went quite well and in a short time I was on the Lan, installed a wireless keyboard and mouse, etc., etc. Finally, it was time to install an external modem since everyting I've read indicates that it can be a nightmare to get a winmodem to work. As I was going to plug in the modem to the serial port, I noticed that there was no serial port. Not having purchased the port replicator, I tried using a USB to serial port adaptor but that requires a driver (I had a driver for Windows only). Therefore, whether I wanted to or not, I had to get the winmodem to work.

Thanks to the link provided by irlandes, (www.linmodems.org) I navigated to www.linuxant.com and downloaded an rpm for Mandrake 9.0. After installation of the rpm, the modem was recognized in kppp and I was able to connect to my isp.

BTW, installing Mandrake 9.0 was the easiest distro I have installed so far.

[Ranger_Ski]

Well all, I tried and did manage to get the winmodem to do its thing. That lasted for a short time as I was tired of being DC every 5 mins. I went to Staples spent about $80 and bought a 56k performance pro modem. I have had no problems with it using windows or linux, and I am happy to say that I use linux more and more than I use windows. The one thing that I have not been able to solve but I am sure I will soon is the annoying like "how long you have been on timer" I mean for real why would I want to know that and why is it not an easy click to get rid of problem?

[carrja99]

Sadly, I am now in the same boat as the people who whine about not getting thier modems working with linux. Having moved off campus, I have to use dialup until I get DSL at the end of August, and I sadly discovered that I have a PCTEL modem. :(

I dunno if I want to go through the pain of getting it to work, or just wait till I get DSL and use the computers in the Lab and at work in the mean time.

Oh, and I must love the usual answer from most Linux gurus. For some odd reason, they assume all of us linux users can just go out and snatch up a spankin new modem or any other piece of hardware at the drop of a hat! :mad:

[mdwatts]

Originally posted by carrja99

Oh, and I must love the usual answer from most Linux gurus. For some odd reason, they assume all of us linux users can just go out and snatch up a spankin new modem or any other piece of hardware at the drop of a hat! :mad:

Why specifically Linux gurus?

Wouldn't you (or anyone else) just need the ca$h?

[Ranger_Ski]

I dunno bro. I had one hell of a time trying to compile it. I had it almost working then other things kick in. I just went and bought a modem. It was fast easy and painless. IN fact that is what I am using to post this. Good luck if you try to build the driver.

[CrashTestDummy9]

Originally posted by carrja99


Oh, and I must love the usual answer from most Linux gurus. For some odd reason, they assume all of us linux users can just go out and snatch up a spankin new modem or any other piece of hardware at the drop of a hat! :mad: And I love how most ppl with computers will spend 30-60 bucks a month on Coca Cola or Pepsi but they cant swing a 20-50 dollar modem...Do you ever change the oil in your car?New spark plugs?How about those 4 dollar air fresheners to cover the pot smell?

[mrgoodbytes]

I am running a Lucent Winmodem with Mandrake 9.0 and figuring out the installation was, how does one say this in international fashion, "le hairball". I would have to suggest not doing it if you don't have clear documentation on how to do it.

I could see using an external if that's a viable option for you.

[JohnT]

U-m-m-m...It seems the used computer store still has external modems for $5.00........OUTRAGEOUS!!!:p