Hullo,
Your modem and problem sound exactly like mine.
I got the very same driver and had make problems BUT ... I can fix them. yay me!
Got modem working ... but had to do a couple of things first.
I did see around stuff on web about ?slmodem? ohhh something else?
Hmm. I can't remember name now.
Or another non intel driver that might work ...
An open source one more generic so would be preferable.
But I saw it after I got the intel one working.
As this one works for me I'm not going to check it out (for now).
The makefile is silly.
If the files do not exist ... the diff result is blank. Yep.
Makefile thinks the diff has matches succesfully and carries on.
diff: /boot/vmlinuz.autoconf.h: No such file or directory
autoconf.h matches running kernel
diff: /boot/vmlinuz.version.h: No such file or directory
version.h matches running kernel
Those files were not there for me either.
To fix this I went looking for them.
locate autoconf.h
locate version.h |grep linux
You will find a good few version.h files but you want the one that applies to your kernel.
e.g. (different machine than at home - redhat 9.1)
your kernel versions will probably be different
/usr/include/linux/autoconf.h
/usr/src/linux-2.4.20-8/include/linux/autoconf.h
/usr/src/linux-2.6.3/include/linux/autoconf.h
/usr/src/linux-2.4.20-8/arch/i386/math-emu/version.h
/usr/src/linux-2.4.20-8/drivers/addon/aep/driver_version.h
/usr/src/linux-2.4.20-8/drivers/addon/cipe/version.h
/usr/src/linux-2.4.20-8/drivers/addon/iscsi/iscsi-version.h
/usr/src/linux-2.4.20-8/drivers/addon/iscsi/version.h
/usr/src/linux-2.4.20-8/drivers/addon/qla2200/qla_version.h
/usr/src/linux-2.4.20-8/drivers/net/sk98lin/h/skversion.h
/usr/src/linux-2.4.20-8/include/linux/version.h
/usr/src/linux-2.4.20-8/include/pcmcia/version.h
/usr/src/linux-2.6.3/include/linux/version.h
which one? The one for your kernel:
maybe /usr/include/linux/autoconf.h (take a look inside) better
maybe to go for one exactly matching kernel
/usr/src/linux-2.4.20-8/include/linux/autoconf.h
/usr/src/linux-2.4.20-8/include/linux/version.h
As root copy them to where makefile wants them:
cp /usr/src/linux-2.4.20-8/include/linux/autoconf.h /boot/vmlinuz.autoconf.h
cp /usr/src/linux-2.4.20-8/include/linux/version.h /boot/vmlinuz.version.h
_now_ try the make again.
and make install.
I had lots of warnings in the make - don't like seeing warnings. They are our
friends BUT they are our friends as developers and we should make sure
to explicitly allow them or remove them. But build was good.
Now the modem was working.
Test using dial up, test using minicom, however you want.
BUT ... next time I restarted the computer the modem service failed to start.
It was not installed as a service on any runlevel.
Or at least ... I saw it but not sure exactly.
Was trying to start before any other service?
Can start the service manually after every restart like this:
/etc/init.d/537_boot start
(as root)
but that would be a pain
So .... need to do more fixing.
As root edit script /etc/init.d/537_boot which was installed as the
service start script for the soft modem.
(NOTE: maybe your installer did work?
check out does modem still work after reboot?
script name could maybe be different)
I changes all calls to lsmod, depmod, rmmod .... to use full
path i.e. /sbin/lsmod /sbin/depmod etc
That's just because I'm fussy.
Add in following lines near top of script:
# chkconfig: 2345
# description: hugely bloated but working intel 537 softmodem driver
# processname: 537_boot
Then install script to start at these runlevels (2,3,4 and 5)
(runlevel 3 would do but ... not worried about others)
as root:
/sbin/chkconfig --add 537_boot
/sbin/chkconfig --list 537_boot
Okay. Hope it works for you.
I'll check back maybe see if it all went horribly wrong :-7
A couple of comments:
Errors in make and service scripts are a little tricky but pretty basic.
Should always put full path in root commands called from service
scripts otherwise scripts fail for non root and sudo users.
e.g. /sbin/lsmod and /sbin/depmod ... instead of just lsmod and depmod ...
The module being loaded into the kernel is ... 6 MEGABYTES!! AIE!
But it seems grand and works beautifully, seems stable.
Now, hmmm, that I've written all this up where could we log bugs/fixes with intel?