RIGHT! All this works for Red Hat 9 running the 2.4.22 kernel
Installing the driver - the readme instructions only work if your system looks like they expect.
You must have:
/lib/modules/'uname -r'/build/include/linux/
- with files "version.h" and "autoconf.h" in it.
You will also need the
/lib/modules/'uname -r'/drivers/char (or whatever your char module directory is)
--- without the first one you get an error on make 536ep to the effect that the directory/file dosn't exist, and without the second you get an error on make install to the effect that 536ep.o and 536epcore.o cannot be installed.
If you don't have the first one - (i.e. you are using the "Publishers' Edition) - then you need to recompile your kenel from a source distribution - just get the latest kernel from
www.kernel.org or whatever it is. The fileroller seems to have trouble with very large tarballs so use the command line to unpack it (as root) into /root ... it helps to do the entire install (yes the 536ep drivers too) as root.
If you don't have the second one, well you should have enabled char devices when you installed the kernel but I found that just creating the directory allowed the drivers to install. (modprobe couldn't find them though - dunno why not yet or even if it's a problem, perhaps the 536ep-boot script will fix it when I reboot???)
having installed successfully - lsmod should show 536ep and 536epcore loaded.
the /dev directory should have 536ep driver installed and the modules will be in the char module directory.
minicom can be configured to use the 536ep modem by calling
#minicom -s
the device is to be set to "/dev/536ep" though probably "/dev/modem" will work. (/dev/modem is a symbolic link to /dev/536ep with rwx file permissions for all users so anyone can use it.)
With this config - minicom goes fine.
Now for the Internet configuration Wizard... first you have to go launch the network management and "configure". This can be done from command line but is easier via GUI.
main>system tools>network device control
configure>hardware>new>modem
select the new modem and put /dev/modem or /dev/536ep for device, hardware for control and switch the modem speaker off - it is very loud! (It is no good trying to configure it for /dev/ttySx since it is a PCI device not RS232.)
OK and file>save
There will now be a hardware option called modem1 (if you already have another modem configured)... good.
NOW you can enter the internet configuration wizard. It will still assume you are using modem0 (if you had one) otherwise is will probably not detect 536ep. Not to worry, configure it the same. When you've finished with the wizard, you'll have to edit the new device you've just created. Network Device Control>Configure as before, select the new modem from the device tab and edit.
General > get a new nickname for it like "i536ep-HaM" so you can easily see what it is.
Provider > check the provider settings are OK
Advanced > under modem make sure the correct hardware (wot you just created) is selected... in my system this was modem1 (sinec the HaM modem is the second installed).
OK and save and exit. You should be able to use the HaM modem to connect to your ISP.
-----------------------------yay!
I'm not out of the woods yet!
As of the date of posting this, I can connect to my ISP - collect the pop summary - but I cannot send or receive mail or anything else. I suspect a configuration problem. As far as I can tell all the right modules are there...
Simon
