I need some serious help with this one. I downloaded the Mandrake 10.0 distribution and have it on dual boot with Windows 98. Installed the kernel source (the correct one as far as I can tell - however I am a novice) and tried to install the drivers for the modem step by step per the instructions that came with it. The modem is a TRENDnet TFM-PCIV92I using the Intel 537EP chipset. Here is what I get:

typed: make clean
response: cd coredrv; make clean
make[1]: Entering directory '/modem/intel-537EP-2.60.80.0-mdk10-smp/coredrv'
rm -f .ko *.o *~ core
make[1]: Leaving directory {same as above}
rm -f *.o *.ko

typed: make 537
response: Module precompile check
Current running kernel is 2.6.3-7mdk
/lib/modules... autoconf.h does not exist
please install kernel source
make: ***[check] Error 1

as I stated before, I installed the kernel source. Did I install the wrong one? Please help. I want to make the switch to Mandrake permanent, but can't if the modem does not work. Thanks for your help.

Jeff

First set up your urpmi sources.

Then RE-install the kernel source.

DO NOT "make clean" or anything like this when you are instructed to do so.

This cleans out the Mandrake customizations and configuration changes which you WANT!!!

Instead follow the proceedure which comes after, dealing with the actual compilation of the new kernel module provided for the modem... not the recompilation of the kernel or it's modules, which is unneccesary.

So I checked out the urpmi sources website you suggested... typed in the info, and it generated lines to addresses on the web.... I can not currently access the web with my linux dist. That's what I'm trying to get a handle on. Is there any other way?

Jeff

Find the kernel-source rpm on the CD or DVD you have.

There will be serveral.

Type

uname -a

to see which kernel is currently installed.

Find the corresponding kernel-source rpm and re-install it with

rpm -Uvh --force kernel-source-xx-xx-xx.rpm

Adjusting for the actual name.

Now DO NOT run make clean, or make config....

At worst type in

make bzImage modules

And go out for the evening... (depending upon the speed of your system...)

Note the "make bzImage modules" step may not be required at all.

Now follow the directiosn for build the module from the point AFTER the instruction tells you to

make dep or make clean, etc.

If it still fails let us know what the steps indicate and where it failed.

I'm going to just download CD3 and install the kernel from there... might as well. I'll let you know what happens. Thanks for all your help so far!!

Jeff

We're close... I finished downloading CD3, installed the kernel source as you said, then SKIPPED make clean and did make 537... got an error. But when I then did, on a whim, 'make install', it seemed to install correctly! Now I just have to enter my internet connection and see if it will dial in to the network. Hopefully the next time I send a message, it will be off Mandrake, not Windows.

Jeff

Okay, so when I run 'make install', here is the response with the 'up' (not 'smp') version of the driver:

rm -f /etc/hamregistry.bin
bash 537_inst
running kernel 2.6.3-7mdk
installing hamregistry, used for persistant storage
installing usrsound, a soft buzzer
installing 537 module
mandrake 537_boot script
starting module and utilities
done

Now, in the readme.txt file, it says it's supposed to create a /dev/modem directory for applications to look to when using the modem... no such directory was created, and so I am as yet not able to use my modem.... now what??

Thanks again for all your help!
Jeff

You may have to alias the module to the device in /etc/modules.conf if it Mandrake doesn't automatically create the entry for you upon reboot.

However note that usually you must MANUALLY create the /dev/modem entry, to point to the actual device name for the hardware.

If for instance your modem appeares as /dev/ttySL0 (as does my softmodem) you have to simlink an entry for it...

e.g.

ln -s /dev/ttySL0 /dev/modem

This creates the /dev/modem entry...

However exactly WHAT you specify depends upon what the driver shows up as.

Usually after the driver is modprobed (either at startup or when you do this manually) the actual device name will be reported by the kernel both to the logs and in the dmesg output.

Thus look at the output of dmesg to see what your actual "device name" shows up as.

Okay, the latest:

Ran dmesg and looked for a listing regarding my modem... here is what I found -

Intel537: no version for "struct.module" found: kernel tainted
INtel537: no version magic, tainting kernel
Intel537: module license 'Proprietary' taints kernel
sound disabled
Intel 537EP card found


Also, I DID find the /dev/modem file... I thought it was a folder. Oops. So there is a /dev/modem file and a /dev/537 file that I found. Where do I go from here?

Jeff

You need to determine what the device driver mounts the modem as under /dev

It sounds like you have it successfully loading which is most of the work.

post the output of

ls -l /dev/537

and

ls -l /dev/modem

You will also need to alias the driver in modules.conf/modprobe.conf if it hasn't already been done by the installation script.

Usually the install readmes include directions on what needs to be done.

ls -l /dev/537 results in:
crw-rw-r-- 1 root root 240, 1 Mar 5 /dev/537
ls -l /dev/modem results in:
lr-xr-xr-x 1 root root 8 Mar 5 /dev/modem -> /dev/537

Also, there is no modprobe.conf that I can find. In the file /etc/modules.conf, the only listings are:

probeall usb-interface .....
above snd-intel8x0 .....
alias sound-slot-0 .....

What next?

Jeff

New to Linux. Just got on line with Amigo AMI-IA56 internal PCI dialup modem with Intel 536ep chipset. Maybe this will help.
1. Your ISP must play nice w/Linux...mine didn't (AOL) , had to change ISP.
2. I guess you know that DSL thru LAN (NIC) connection is easiest. No drivers. Took about 4 minutes.
3. Next easiest is dialup with external serial (NOT USB) modem. Google for Best DATA or US Robotics. No drivers. Takes about 10-15 min. to configure in Kppp. I bought one for the kid's PC at thrift store. ($4). Everyone's getting rid of older 56k ser. modems. (they work with linux and are faster than some int. PCI modems)
4. Of course I chose the most difficult install. This was my tutorial to myself after successful install.
I cannot guarantee any success with your setup:
Mandrake 10.0 download.
KDE3.2
Konqueror
2.6.3-7 kernel
Amigo AMI-IA56 internal hdwr PCI modem w/Intel 536ep chipset

Intel 536ep modem install

Install modem in PC
make sure kernel source is installed by the following:
(you must have your install cd's ready)
open a terminal>logon as root(su)>enter password>then type:
# urpmi kernel-source


Must use EXACT drivers for EXACT modem for EXACT kernel version.
Use the intel 536ep 4.69-mdk10-up.tgz file from Intel site. Drivers on modem disk are outdated (they are for kernel 2.4.x)
Use GUI to create empty folder in /home/user/ ....named Intel
copy .tgz file to folder using GUI
unzip the file by one of the following methods:
In terminal:
# tar -zxvf <filename>.tgz
the file will be unzipped into a new folder in the Intel folder

OR

In the GUI (Konqueror) right click the .tgz file>choose actions>choose extract here. Again, new folder will be created in Intel folder.
Use whichever method DOES NOT impose locked permissions on the unzipped files.
Follow instructions in the readme created in the unzipped folder.
Go back to terminal:
move into the directory created by the unzip action by:
# cd <filename directory>
# make clean
# make 536
#make install
reboot PC
this will create a /dev/modem/ link. Use this setting in the Kppp dialer

I am still experimenting with modem commands...... but slower connect speeds (28800 - 45000) actually give the best combination of speed AND stability.
Good luck

Thanks for the tips, however, I'm using 537EP, not 536EP... different driver, and I did get the driver off the Intel website... that is what we are trying to get working right now. The /dev/modem link has already been made, but for some reason it won't dial out at all, so the ISP is not the problem, yet. But I appreciate your input.

Jeff

It looks like /dev/modem is being properly symlinked to /dev/537.

You need to test it. Run minicom in a console as root and configure it to utilize /dev/modem.

Exit out and go back in. If you see modem commands appear on the screen you may be done.

As far as modprobe.conf you'll need to make the appropriate changes to it. As I mentioned this should be included in the documentation for the driver.

Test to see if the kernel module is working by running minicom as I mentioned.

Also look to see if the driver is installed by running "lsmod".

Finally you MUST make the changes to /etc/modules.conf /etc/mod* as indicated by the driver docs.