LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-06-2005, 01:35 PM   #1
proNick
Member
 
Registered: Apr 2005
Posts: 104

Rep: Reputation: 15
Intel536ep problems on kernel 2.6.11


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?
 
Old 04-06-2005, 05:56 PM   #2
proNick
Member
 
Registered: Apr 2005
Posts: 104

Original Poster
Rep: Reputation: 15
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?
 
Old 04-06-2005, 07:09 PM   #3
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
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..
 
Old 04-07-2005, 03:15 AM   #4
proNick
Member
 
Registered: Apr 2005
Posts: 104

Original Poster
Rep: Reputation: 15
Nope.

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

Can it be that something is wrong in my kernel configuration?
 
Old 04-07-2005, 03:09 PM   #5
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
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.....


Last edited by jong357; 04-07-2005 at 03:16 PM.
 
Old 04-18-2005, 03:19 PM   #6
Thetargos
Senior Member
 
Registered: Mar 2003
Location: Mexico City
Distribution: Fedora, Ubuntu & Mint
Posts: 1,679

Rep: Reputation: 45
Quote:
Originally posted by jong357

Anyway, It worked just fine for me on Slackware 10.1 / Linux-2.4.29.
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.
 
Old 04-18-2005, 03:42 PM   #7
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Quote:
Originally posted by jong357
They're just not maintaining their drivers fast enough to keep up with the latest 2.6 kernels.....
echo... echo... echo...
 
Old 04-18-2005, 03:44 PM   #8
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Quote:
Originally posted by jong357
They are just a chipset manufacturer and are under no obligation to even provide software....
 
Old 04-19-2005, 02:21 AM   #9
Thetargos
Senior Member
 
Registered: Mar 2003
Location: Mexico City
Distribution: Fedora, Ubuntu & Mint
Posts: 1,679

Rep: Reputation: 45
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...
 
Old 05-06-2005, 08:30 AM   #10
Emmanuel_uk
Senior Member
 
Registered: Nov 2004
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606

Rep: Reputation: 53
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
 
Old 05-11-2005, 02:19 AM   #11
Emmanuel_uk
Senior Member
 
Registered: Nov 2004
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606

Rep: Reputation: 53
536ep works with kernel 2.6.11-6mdk

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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
What is confusing my Intel536ep? bobzilla Debian 1 11-24-2005 08:34 PM
Intel536ep modem anjum Ubuntu 3 08-11-2005 03:14 AM
Intel536ep modem: i am just about there anjum Linux - Software 1 08-01-2005 07:58 AM
Intel536EP Modem matarodi Linux - Hardware 0 07-21-2005 06:44 AM
intel536ep modem in mandrake 10.0 rsuave Linux - Newbie 1 11-10-2004 02:05 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:32 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration