Hi all!

I have problems with installation of Intel 536 modem, on Slackware 10.1, kernel version 2.6.11.

Driver that I'm tryin to install is intel-536EP-2.56.76.0


Here's what I get, when I start command make 536 :





bash-3.00# make 536
Module precompile check
Current running kernel is: 2.6.11
/lib/modules... autoconf.h exists
autoconf.h matches running kernel
version.h matches running kernel
uname -r|grep "2.6" && \
cd coredrv && make 536core_26 && \
cp Intel536.ko .. && cd .. && \
strip --strip-debug Intel536.ko && \
exit; \
ls Intel536.ko >/dev/null 2>&1 || uname -r | grep "2.6" && echo "Failed to build driver" && exit; \
if [ ]; then \
cd coredrv; make TARGET=TARGET_SELAH KERNEL_SOURCE_PATH= "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
else \
cd coredrv; make TARGET=TARGET_SELAH KERNEL_INCLUDES=/lib/modules/`uname -r`/build/include \
"PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
fi ; \
cp Intel536.o .. ; \
if [ -a /boot/vmlinuz.version.h ]; then \
cp /boot/vmlinuz.version.h /lib/modules/`uname -r`/build/include/linux/version.h;\
fi
2.6.11
make[1]: Entering directory `/intel/intel-536EP-2.56.76.0/coredrv'
make -C /lib/modules/2.6.11/build SUBDIRS=/intel/intel-536EP-2.56.76.0/coredrv modules
make[2]: Entering directory `/usr/src/linux-2.6.11'
CC [M] /intel/intel-536EP-2.56.76.0/coredrv/coredrv.o
make[2]: Leaving directory `/usr/src/linux-2.6.11'
make[1]: Leaving directory `/intel/intel-536EP-2.56.76.0/coredrv'
2.6.11
Failed to build driver




For me, it looks like version of the driver is not for my version of the Kernel, despite the thing that is driver for 2.6.x kernel versions.


Can somebody help?

I did made some improvement, but still have problems...

In file coredrv/coredrv.c, I have commented three lines (around line 295)

// case PM_SAVE_STATE:
// printk(KERN_WARNING"Saving power state is not implemented\n");
// break;


After that I did manage to compile driver, but can not insmod it. Here's the error:


bash-3.00# insmod Intel536.ko
insmod: error inserting 'Intel536.ko': -1 Invalid module format
bash-3.00# insmod Intel536.ko -f
insmod: error inserting 'Intel536.ko': -1 Invalid module format



Do you have experience with this, please?

Where did you get that driver? Sounds like an old one.. I'd go here:

http://downloadfinder.intel.com/scri...977&page_nbr=2

It's number 15 on the list...

I have a 537ep.. I'll try compiling it if it will help you out. Never bothered to see if it works since I'm on cable..

Nope.

I can compile it, but can not insmod-it (wrong module format).

Can it be that something is wrong in my kernel configuration?

Not sure... Mine compiled and inserted just fine. RoadRunner is too cheap to give you free dialup accounts so I couldn't actually test the modem connection... But by all rights it should work for me... I would still try using a different driver version tho. The latest one compiled for me as well but I couldn't insert it. Spit out some stuff about unresolved symbols and a non-GPL license. I rolled back to a driver that is a couple months older and it worked like a charm. Unless you try various driver versions, you'll never be able to narrow down the problem. That was what I was trying to say I guess... Theres another version besides the one I talked about on the first page of that link. That was 2 pages worth of drivers.

If you did already try a new one and it doesn't work, I would try with a couple different kernel sources. First, I would try with every modem driver you can get your hands on. Then I would try with different kernels. Intel isn't big on keeping up with drivers and it's a miracle they even provide linux drivers. They are just a chipset manufacturer and are under no obligation to even provide software....

Anyway, It worked just fine for me on Slackware 10.1 / Linux-2.4.29. Look at the driver dates of those modem packages... They are nowhere near being close to the latest 2.6.x kernels. That could be your problem. They're just not maintaining their drivers fast enough to keep up with the latest 2.6 kernels.....

And this is precisely why it worked like a charm in your system... The driver API changed in the 2.6 branch of the kernel since version 2.6.10 (work started on this since 2.6.8, though). Intel fully supports 2.4.x kernels, where as 2.6 is not very well supported, especially the new driver API. I'm trying to get running my girlfriend's 537EP modem in FC3 with a 2.6.11 custom built kernel. Oddly enough the driver works just fine with the "boxed" 2.6.9 kernel... And in any case, the latest official Fedora Core 3 kernel is a 2.6.11 based too... In any case, I don't know what has taken Intel so long to migrate their driver over the new API, which (as far as I know) is backwards compatible with the previous one.

echo... echo... echo...

Yes, they don't have any obligation, and we, the community are thankful for that, however they should release their drivers under an Open Source (I'm not saying GPL) license to make things easier (IMO). There is a patch posted in the linmodems.org mailing list (accessible through the archives) that addresses this, I hope Intel will merge this patch into their driver or at least have a better way to solve the problem with 2.6.10+ kernels...

Hi,

does this thread below helps?

http://www.linuxquestions.org/questi...ighlight=536ep

I have just posted there a reference to known patches to the driver
for kernel 2.6.10, there is also one for 2.6.11

Regards

PS: Am a newbee, so take it with a pinch of salt

Hi,

I know nothing about slack
But I have my 536ep to work with 2.6.11-6mdk, see

http://www.linuxquestions.org/questi...17#post1636217

Hope this is relevant to you
Btw i also had this -1 Invalid module format error.
The patch got rid of it.

Please let us know if this works.