LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 11-28-2007, 03:08 PM   #1
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Rep: Reputation: 22
ASUS Rhinefet net driver


I have a ASUS A8V-XE motherboard with built in 100 MHz network interface. I am running Slackware 11.0, kernel 2.4.33.3. I have a driver on the mfgr CD, called rhinefet.o but I cannot figure out how to make it work.

I installed the kernel source and ran "make config" and "make dep" in order to satisfy the rhinefet makefile, and I was able to compile the driver and get the rhinefet.o file as the instructions described and I copied it to the /lib/modules/... directory. But when I attempt to use it, when I run a "insmod rhinefet" I get > 50 unresolved reference error messages. Can anyone tell me what I'm missing?
 
Old 12-15-2007, 05:18 PM   #2
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
ASUS no help w/ Linux

I contacted ASUS regarding the 100MHz on-board NIC problem and got a detailed explanation of use under Windoz; they completely ignored the part about the fact of Linux. They seem to have no support for Linux at all. Granted, the mobo was cheap, so I should not expect much and that's what I got.
 
Old 12-16-2007, 06:04 PM   #3
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Try modprobe rhinefet. As well you can run strace insmod full_path_to_rhinefet_module or strace modprobe rhinefet to check what is causing those missing references.

Last edited by Alien_Hominid; 12-16-2007 at 06:54 PM.
 
Old 12-17-2007, 05:49 PM   #4
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by Alien_Hominid View Post
Try modprobe rhinefet. As well you can run strace insmod full_path_to_rhinefet_module or strace modprobe rhinefet to check what is causing those missing references.
I am not familiar with these routines. Modprobe returns "Can't locate module rhinefet" although it is in the /lib/modules/.../net/ dir.
Strace insmod ... gives me a gob of info, I cannot interpret. What am I looking for? Or, is there a step I've missed in installation so modprobe needs something? And thanks for the help.
 
Old 12-18-2007, 01:35 AM   #5
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 287Reputation: 287Reputation: 287
Perhaps you could try using slackware 12? The newer 2.6 kernel might have an updated driver that works.
 
Old 12-18-2007, 02:30 AM   #6
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by tommcd View Post
Perhaps you could try using slackware 12? The newer 2.6 kernel might have an updated driver that works.
I do not find this kind of advice helpful. The fact that it "might" have another driver means you have no idea and are simply talking for the sensation of it. You are sending me on a "wild goose hunt." I would prefer if you only gave advice to me when you are sure of something. Don't take this the wrong way, I promise I will not give you advice unless I know the topic well.
 
Old 12-20-2007, 08:11 AM   #7
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
I've thought about it and maybe you need to rename your .o file into .ko (kernel object). Maybe that's why modprobe can't find it.
 
Old 12-23-2007, 01:31 AM   #8
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by Alien_Hominid View Post
I've thought about it and maybe you need to rename your .o file into .ko (kernel object). Maybe that's why modprobe can't find it.
It's worth a try. The instructions say that is necessary for 2.6, whereas I am running 2.4 but it is easy to try and harmless if wrong. I've been going through the driver code looking for the unresolved refs and they seem to be external, in the kernal I suppose. I'll look in the kernel nm list next.
 
Old 12-23-2007, 04:47 AM   #9
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Quote:
Originally Posted by rdx View Post
It's worth a try. The instructions say that is necessary for 2.6, whereas I am running 2.4 but it is easy to try and harmless if wrong. I've been going through the driver code looking for the unresolved refs and they seem to be external, in the kernal I suppose. I'll look in the kernel nm list next.
That's why I mentioned strace.
 
Old 12-23-2007, 02:31 PM   #10
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by Alien_Hominid View Post
That's why I mentioned strace.
Okay, I am finding the refs in System.map-ide-2.4.33.3.

The way they are listed has a suffix, e.g. proc_net_Rsmp_8ce6be10 whereas the namelist entry is:
c03a0888 B proc_list

but the refs are in the kernel. So, whatever I am doing wrong is in the linking to the lib thingy, whatever that is. I am not clear on how these dynamic libs work so I don't know where the prob is but that seems to be the vacinity.
 
Old 12-26-2007, 01:22 PM   #11
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
A few drivers will need System.map to resolve symbols (since they're linked against the kernel headers instead of, say, glibc). They will not work correctly without the System.map created for the particular kernel you're currently running. This is NOT the same thing as a module not loading because of a kernel version mismatch. That has to do with the kernel version, not the kernel symbol table which changes between kernels of the same version!

From: http://linuxmafia.com/faq/Kernel/systemmap.html
 
Old 12-27-2007, 01:49 AM   #12
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 123

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by Alien_Hominid View Post
A few drivers will need System.map to resolve symbols (since they're linked against the kernel headers instead of, say, glibc). They will not work correctly without the System.map created for the particular kernel you're currently running. This is NOT the same thing as a module not loading because of a kernel version mismatch. That has to do with the kernel version, not the kernel symbol table which changes between kernels of the same version!

From: http://linuxmafia.com/faq/Kernel/systemmap.html
How is the System.map used? Is it read during make of the driver or is it used when you try to insmod? I see what you mean, the linkages move around depending on the particular make but I'm going to have to find the System.map for the bare.i kernel the I am running.
 
Old 12-27-2007, 07:55 AM   #13
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
The system map for the default Slackware kernel is placed in /boot, but new one is created each time you compile a kernel. I think it is left in /usr/src/linux if you don't do make install (not recommended). I think it's used at both times, but I'm not 100% sure.
 
  


Reply

Tags
asus, driver, net


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
ASUS wl-160g driver dolphs Linux - Wireless Networking 0 12-03-2005 09:28 PM
Asus P5GDC-V lan driver takatam Linux - Hardware 0 10-27-2004 06:22 AM
Audio driver for ASUS board and HP 1150 Laser PRinter Driver ccatindia Linux - Hardware 1 05-11-2004 04:20 AM
ASUS A7VX8 audio driver dzel Mandriva 2 02-25-2004 08:23 PM
driver for asus motherboard vher Linux - Hardware 12 07-02-2003 02:31 AM


All times are GMT -5. The time now is 10:20 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration