Hi, I have a very weird modem problem. I am building a PC for a friend who is stuck on dial up. Well anyway unfortunately I chose a Intel Corporation 536EP Data Fax Modem, because on the box it said it was a hardware modem. (this turned out to be a lie - it was still a winmodem).

In any case I found a driver for it avaiable from the intel site. The driver compiles fine, without any difficulties at all, but for some reason the install script borks. This means i am left sitting with a driver which I cannot properly install.

I can load it as a module if I navagate to the directory where the driver is located and enter a terminal and type:

Or in other words, I can load the module providing I am sitting right on top of it. The question is though, if the install script for it is borked, can I just move it somewhere so that it will be in a location that the kernel will be able to find it so that I can have it automatically loaded at boot time?

I am running Debian Sid/Kanotix so really all I should have to do and want to do is add it to my /etc/modules so that it will be found and loaded during boot up. Is there a way to do this - or more specifically - is there a way to do this manually?

Other than that when the driver is loaded the modem does appear to function normally.

Any help would be appreciated.

GJ

Hey I finally got my modem to work! I installed a modem driver for the Intel Corporation 536EP Data Fax Modem that I got directly from Intel.

But the big problem now is in order to use it, I need to create a link from it (it is called 536ep0 in /dev) to /dev/modem. I need to do this specifically so that KPPP can see it.

The only thing is that everything in /dev/ gets deleted and rebuilt each time I reboot.

I have been led to believe (rightly or wrongly) that it is udev that is responsible for this. (And I do in fact have udev installed). So the question is how can I make a symlink from /dev/536ep0 to /dev/modem that will remain in place and will persist even after a reboot?

GJ

"for some reason the install script borks."

What error messages do you get when the install script fails?

"if the install script for it is borked, can I just move it somewhere so that it will be in a location that the kernel will be able to find it so that I can have it automatically loaded at boot time?"

Take a look at the install script and figure out when the install script was trying to place the driver.


------------------------------
Steve Stites

Well that's not the problem any more I just moved it to ~/drivers/net and it works. The real problem I'm having is in my second post. How do I create a persistant symlink in /dev?

GJ

"But the big problem now is in order to use it, I need to create a link from it (it is called 536ep0 in /dev) to /dev/modem. I need to do this specifically so that KPPP can see it."

It is the other way around. You need a link from /dev/modem to /dev/536ep0. The way to do that is:
rm /dev/modem
ln -s /dev/536ep0 /dev/modem

See:
man ln

--------------------
Steve Stites

Yes your right I just got it the wrong way round. The point is my symlink called /dev/modem that points to my real modem keeps getting deleted after each reboot.

I tried pointing KPPP at my real modem theough kppp.conf but that made no difference. The only way it does work is if it is a symlink.

GJ

NM I just wrote a small bash script and and added it to my start up scripts and had it create the /dev/modem symlink. It works a treat!

I wish i'd thought of that originally. Much simpler.


GJ