rtl8139 not showing in ifconfig

C-Sniper · 07-18-2007, 04:04 PM

Hi all,
I have a Hp zv6000 laptop and im tryin to get my RTL8139 ethernet card to work. i have enabled all the marks in the Kernel for the card but it still will not show up. i recompiled and used

Code:

modprobe 8139too 
modprobe 8139cp

well anyway i recieved this message

Code:

FATAL: Error inserting 8139too (lib/modules/2.6.21.5-smp/kernel/drivers/net/8139too.ko): Unknown symbol in module or unknown parameter (see dmesg)
FATAL: Error inserting 8139too (lib/modules/2.6.21.5-smp/kernel/drivers/net/8139cp.ko): Unknown symbol in module or unknown parameter (see dmesg)

ok well heres the dmesg

Code:

8139too: Unknown symbol mii_ethtool_sset
8139too: Unknown symbol mii_check_media
8139too: Unknown symbol mii_nway_restart
8139too: Unknown symbol generic_mii_ioctl
8139too: Unknown symbol mii_ethtool_gset
8139cp: Unknown symbol mii_ethtool_sset
8139cp: Unknown symbol mii_check_media
8139cp: Unknown symbol mii_nway_restart
8139cp: Unknown symbol generic_mii_ioctl
8139cp: Unknown symbol mii_ethtool_gset

any suggestions?
Thanks for your time.

-edit-
this card worked with the 6.20.3 kernel so if anyone knows what changed in the way of the Ethernet networking support i would be grateful

Mark Havel · 07-18-2007, 04:20 PM

This is a strange one, usually this kind of chip works pretty well if not directly out of the box (at least, mine did). If you compiled your kernel yourself, did you activate all the networking stack and the related options?

C-Sniper · 07-18-2007, 04:56 PM

well the reason i went in to check this out was because it wasn't working with the "huge" kernel. so its the standard slk 12 kernel. also i found the mii module and tried to disable it but it wouldn't let me it was either yes or module.

C-Sniper · 07-19-2007, 03:31 AM

hmmm... now when ever i try 'ifconfig' i get a whole bunch of output in the form of a Kwrite window. 'KWrited - Listening on Device /dev/pts/0' im guessing this is debug info but i dont have any debug things checked in the kernel. this looks like its going to be a long uphill battle.

--edit--
and from the look of things i just messed up my ipv6 as it is causing a kernel panic on shutdown.