Help needed installing driver

[Sean_Foster]

My problem lies in the fact that when I try to connect, I get to the "Initializing Modem . . ." stage and it gets stuck there.

I'm not sure if it has anything to do with the problem, but the only way I can start KPPP is as SU from a console.

Any suggestions would be greatly appreciated.

Sean Foster

As I encounter different problems, I update the "Subject". Please scroll down 8 posts to see the post most relevant to the current subject.

[ericrun]

It sounds like you need your user account to be added to the dip group, which can be done in Kuser. I think you have to log out and back in after you do this.

[Sean_Foster]

Okay, I added my user to the dip group and this solved the problem of having to start KPPP from the console, but it still hangs at "Initializing Modem . . .".

You were correct about having to log out and then back in again.

Thanks for the help so far. Please keep it coming!

[ericrun]

I get a similar problem with KPPP. I've been using wvdial with no difficulty.

[ericrun]

Oh, I've only gotten wvdial to run from the command line, so I have to run a terminal, type in wvdial, and it will connect, then I leave the terminal open, and later when I want to disconnect, I have to type Control-C with the terminal as the active window to get it to disconnect.

If someone has any idea on why neither of us can get kppp to work, feel free to contribute.

[Sean_Foster]

New info:

I've tried many different ports and adjusted my pre- and post-init delays but nothing. Also, I get nothing back when I query my modem. Is KPPP not seeing my modem? If not, what can I do to correct this? My modem is a Creative Blaster V.92 PCI (not sure of the chipset).

[ericrun]

Since it is a PCI modem, run lspci -vv (that will list your PCI devices in very verbose mode). When you search for the device in the list, it should be listed either by name, or as an unknown communication device. If you have Windows, the Input/Output address and IRQ should match what you have listed in the Windows Hardware Manager.

If you run dmesg, you will get another list of hardware on the machine. Look line by line through the list, and look for your hardware address. You will hopefully find it with the device number you need listed somewhere in the next few lines (it will look like ttySx where x will be some number between 0 and 20, mine is ttyS14)

It looks like you have a winmodem, which means you'll probably have to download a driver (or buy a hardware modem that supports linux). You should start at http://www.linmodems.org/ where they link to software that will help you find the chipset, and they have instructions on how to track down your driver based on the chipset. Post the chipset that you get from that program, and we'll see if we can walk you through the rest.

[Sean_Foster]

My modem is on ttyS15. To configure the connection, I followed these steps:

Run KPPP
Click on "configure . . ."
Select the "Modems" tab
Click "Edit . . ."
Select the "Device" tab

The problem is that the only devices listed under "Modem Device" are:

/dev/ttyS0
/dev/ttyS1
/dev/ttyS2
/dev/ttyS3
/dev/ttyS4

[Sean_Foster]

Okay, I went to http://www.linmodems.org and found a wealth of info. I'm using a PCTel HSP56 MicroModem and I followed some links to instructions for this modem (http://www.peacefulaction.org/sayami...OWNLOADDRIVERS). The problem now is that it uses the pct688t chipset and the instructions only list the following:

pct789
cm8738
i8xx
via686a

Do I take a chance and try the pct789?

[ericrun]

To get ttyS15 run:

cd /dev
./MAKEDEV ttyS15

Then run:
ln -s ttyS15 modem (KPPP didn't have ttyS15, but it can use /dev/modem)

Then you have /dev/modem linked to ttyS15.

Unfortunately, I followed the http://pctelcompdb.sourceforge.net/search.php link from the peacefulaction website, and it allows you to search for the chipset, and when I searched for pct688t, it returned three records, and the relevant one appears to be

226 PCtel inc I56PSP-F40 pct688t Not Working

and has a link to http://pctelcompdb.sourceforge.net/v....php?id_no=226 which doesn't add much useful. You can try the pctel driver at http://linmodems.technion.ac.il/pctel-linux/ but I suspect it won't work. If that's the case, you're probably going to need to buy a modem.

I'd recommend something from Froogle, checking that it is a PCI (There are several ISA modems on this list), 56K and the page says that it comes with Linux drivers (or if you get something like my US Robotics 5610B, the linux kernel already has the driver):
http://froogle.google.com/froogle?nu...Search+Froogle

In the past, it was common to recommend external SERIAL modems, they all used to "just work", you just need to know which port to connect to. Today, you have to becareful, because some external modems (and most usb modems) are not Linux compatible.