SCIENTIFIC-LINUX-USERS Archives

October 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Fri, 6 Oct 2006 08:03:11 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Francois Colonna wrote:
> Hello
> 
> 
> with  kernel  42.0.2.ELsmp
> it is impossible for me to make the network card (Realtek) be recognized
> 
> dmesg | grep eth0
> 
> gives an empty answer
> 
> while with the 2.6.9-34.0.2.ELsmp kernel it gave :
> 
> eth0: Identified chip type is 'RTL8168B/8111B'.
> eth0: r10001.0, the Linux device driver for Realtek Ethernet Controllers 
> at 0xc800, 00:17:31:25:6b:37, IRQ 169
> eth0: Auto-negotiation Enabled.
> eth0: 100Mbps Full-duplex operation.
> eth0: no IPv6 routers present
> 
> How to make things work ?
> 
> 
> Thanks
> François Colonna

Hello,
I'm sorry, I kept meaning to reply to your e-mail but kept getting 
sidetracked.

When you are booted up into that kernel, you need to do a

/sbin/depmod -a

That will get that kernel module loaded in so the kernel recognizes it 
and loads it at bootup.
As I look at the postinall scripts for my kernel module's, I'm seeing 
that they aren't all consistant.  They are supposed to do this for you, 
but it looks like for the r1000 it only does it if you are running the 
kernel that the module was made for ... which isn't going to be the case 
if you are doing an upgrade.
I'll work on fixing that.
Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________

ATOM RSS1 RSS2