um...disregard that last comment...took me about all the time since the last post to figure this out:

Anyway, I'm up to set 4.10 in the linmodem mini-howto:...
the error message I get is:

[root@linux misc]# insmod pctel country_sel=1
Using /lib/modules/2.2.15-4mdk/misc/pctel.o
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrOpen
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrClose
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrWrite

someone in #linuxhelp suggested recompiling the source, but I've done that at least 20 times already....

bjc, how did you get past your problem?

Maybe you have the wrong module? There are other PCtel modules on the homepage you directed me to. Just a thought.

Have you tried to force it? (i.e: insmod -f .....)
It works for me that way, otherwise I get a different compile error.

Apart from that I dont know about the errors themselves.

yes, there's two you're supposed to insmod...from the lin modem mini-howto. I first insmod ptmodule.o (in /src/module), then insmod pctel.o. insmod -f will not work because the errors come up; it's the module itself not any hardware or anything with linux.

No way!, I have not insmod that ptmodule.o file at all! Maybe that will work. I will try it. Have you tried to insmod pctel WITHOUT the country bit on the end. I read that it is not totally necessary. There are some extra files to read on the Wallace and Grommit page about the PCtel module. They are on the bit where it goes

PCTel [1] [2]

They may be of use to you, but they were not relevant to me.

Keep going.

well...still stuck here...........ahem, admins?

Believe it or not, but I have crashed kppp! I know what your thinking, so what? Well, every other time I went to Query Modem, I got the sorry....modem is busy.

This time, when I insmod ptmodule,then run kppp, I managed to crash it. I am thinking that the module IS working, just not able to find the modem.

I will try to use setserial to configure the modem from the configuration in windows, and hopefully get the modem recognised. Also I used YAST2 to find the modem and believe it or not, it too crashed (i.e wouldn't respond). I am going to double check ervy process then post what happens.

bjc, have you just tried to just enter:
insmod -f pctel

I know that you don't need those country arguements, or they don't often work. Also check you have inisitialised the module dispite the error using: lsmod

Another question: what distro are you running?

To anyone, does anyone know what the other files are for that you download with the modules? especially those in the /lib file.

YES, I HAVE TRIED insmod -f pctel

The error message, yet AGAIN, is:

[root@guesswaineedhelphere lib]# insmod -f pctel
Using /lib/modules/2.2.15-4mdk/misc/pctel.o
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrOpen
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrClose
/lib/modules/2.2.15-4mdk/misc/pctel.o: unresolved symbol IntrWrite

I've tried this on Debian 2.2, TurboLinux 4 Workstation/6 Server Lite, Mandrake 7.1 (7.2 does not install and configure correctly), StormLinux 2000 [Hail], Corel Linux Second Edition, Slackware 7.1, RedHat 6.2 (7.0 has problems like Mandrake 7.2), and all have had this problem.

I would try it on a Lucent modem, but I can't find the drivers for it.

Currently running Mandrake 7.1

You can get hold of a Lucent driver from http://www.linmodems.org
There is also plenty of info there.

I still am unable to get somewhere apart from crashing kppp.

Will keep trying though.

I have finally got kppp to recognise my modem, and can get to the point where it says Dialling 0808 545345. Then nothing. I have seen the terminal window and it appears the modem is talknig to the program because of the OK signals it recieves. I went to query modem but nothing came up from the AT boxes. Does any one know what is wrong. After finally getting the modem recognised I am not stopping now. bjc, I will post later of how I finally got the modem recognised.

Okay here is what I did in a terminal window:

#:rm /dev/ttyS15
#:mknod /dev/ttyS15 c 62 79
#:chmod 666 /dev/ttyS15
#:insmod -f pctel
#:insmod ptmodule
#:setserial /dev/ttyS15 port 0xd000 irq 10 skip_test

I then ran kppp and it found modem, but it could not get a dial tone. Does anyone know why? Also, when I went to Query Modem nothing came up next to the AT boxes. Does this mean it is still not recognised? Is it something to do with no uart specified?

I get "Sorry, the modem is busy"...as always...

That error message usually means one of a few things,

1) Wrong driver.
2) Incorrect setup of modem (wrong com port, wrong irq, etc.)
3) Some other software is already accessing the modem.

Wierd...the first time I tried what you posted, CragStar, nothing was unusual (in error messages AND results). Now I do it again, using a different driver (or, at least, file), and I get "iPC-TEL drive (88) found : irq = 10, base = 0xff00" when I "insmod -f pctel"..

Then, obviously, I changed the setserial command to:
"setserial /dev/ttyS15 port 0xff00 irq 10" (I don't like the skip_test idea).

Yet, even that, I STILL get Modem is busy...

...never mind, I can dial out with minicom now...

I still have a few problems:

(1) How do you write a script that will run the "setserial" command, AND automatically dial out and then log on?...

(2) Which proxy, squid/ipchains, will run the script when needed?

(3) HOW do you set the proxy to use that connect? because, as of now, I can't even surf locally on that computer using netscape (lynx seems to be configured to my existing proxy)

Yes, I know this is no longer on the subject, but...

oh, CragStar, this is the 6th time I followed YOUR directions and did it...only this time I did this from a windows machine telnetting in...(same driver, still)