login
Search
Hi. I've recently got the 2.6.2 stable build compiled rather successfully, except for the ethernet support.
I've got a RTL8139 compatable card in a pci slot.
I've enabled all there is to enable for ethernet support under the networking section(imho), left out all unnecessary ones like FDDI or token ring etc. I've enabled almost all options with PCI as well.
My previous stock kernel 2.4.2-08 from a redhat 9 install had it working perfectly. but no modules were loaded; they seem to be built in.
any ideas? i can modprobe 8139too.ko but eth0 refuses to get an ip (as it would haf in my old kernel) when i do an ifup. i've tried compiling it into the kernel as well but no luck.
thanks.
~lummyk
RTL 8139
I am also having this problem with my 8139 based card. Ethernet card worked fine under kernel 2.4.22, but it wont under 2.6.2. dmesg|grep eth shows that it did find the card, however, ifconfig doesn't show eth0 at all. I have the 8139 support built right into my kernel, along with PCI support (its a PCI card, a Dlink actually). I have heard of at least one person who upgraded to a 2.6 kernel with a 8139 based card without any problems. Any help would be appreciated.
RTL 8139
My 8139 based D-Link card works great under kernel 2.6.0.
After you modprobe 8139too (if necessary) and then run ifup, do you see any error messages in the system log file? What happens when you run ifup anyway, do you get an error message from that? What if you run dhclient instead of ifup? After you modprobe 8139too, do you see the eth0 interface in the output of ifconfig?
RTL 8139
I have a DLink 8139 running just fine under 2.6.2.
Do you have any of the 8139too options enabled in
you kernel ? Such as PIO, rev K, older-8129/8130,
or RX-reset options enabled ? If you do not have an
older card you likely do not need the last three. I have
PIO = 'N'. Postup your dmesg|grep eth for info.
--
Those who can do, those who can't sue.
bits of my dmesg, .config and dhclient output.
i tried as cyclone suggested, to turn off all the options under the 8139 driver. it worked worse for me. now, ifconfig doesn't show me eth0. perhaps i have an older card. anyway, here's the latest fm my dmesg, .config n dhclient.
dmesg | grep eth
divert: not allocating divert_blk for non-ethernet device lo
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0xe08d7c00, 00:e8:4c:78:21:8f, IRQ 11
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
divert: freeing divert_blk for eth0
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0xe08d7c00, 00:e8:4c:78:21:8f, IRQ 11
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
dhclient output
Internet Software Consortium DHCP Client V3.0pl1
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/eth0/00:e8:4c:78:21:8f
Sending on LPF/eth0/00:e8:4c:78:21:8f
Listening on LPF/lo/
Sending on LPF/lo/
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 4
8139 portion of .config
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
RTL 8139
When I first upgraded (I've got an RTL8139) I found that eth0 wouldn't start.
I discovered that this was because my dhcp client daemon wouldn't start. This turned out to be because I had not enabled the af_packet module when I build the kernel. I guess that dhcpcd sends out raw ethernet packets as part of the dhcp protocol and so needed the packet socket module.
So make sure you've enabled:
Device Drivers ---> Networking Support ---> Networking Options ---> Packet Socket
create the file /etc/sysconf
create the file
/etc/sysconfig/network-scripts/ifcfg-eth0
With something like the following contents
DEVICE=eth0
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
since mine's a pci slot i rea
since mine's a pci slot i reasoned it might be irq conflicts. i disabled that and it works fine now. thanx all.
~lummyk
I had the same problem, reaso
I had the same problem, reason for googling and finding your thread. As nothing of the hints worked, I finally found out that no dhclient was running. That was all!
I can't seem to get my dhcp c
I can't seem to get my dhcp client running.
I have this problem with 8139too with both 2.6.0 and
2.6.2. I'm using Debian.
Here's something interesting and maybe a clue, but I don't
know what to do with this info. The very first time I booted
into 2.6.0 no network drivers were loaded. I had to manually
modprobe 8139too. And then my network connection worked.
Then I had to shut off my pc for the weekend and when I booted
up into 2.6.0 it automatically loaded my 8139too driver and
I couldn't get an IP address using dhcp.
when I built the kernel I just used the default kernel settings
as supplied by Debian. My workstation is in sync with Debian
Testing.
I sure wish I could get this working. In the meantime I have
Mandrake Cooker 10.0 beta 2 running on ancient hardware with
2.6.2
model name : Pentium II (Deschutes)
stepping : 2
cpu MHz : 400.984
Intel Corp. 82557/8/9 [Ethernet Pro 100]
and dhcp works fine over here.
But I want my Debian workstation to be running 2.6 too!
dhclient
neither can I ...
it says unknown kernel version... lame dhcp :>
any fixes?
dhclient
on my box... on line 22 of /sbin/dhclient i added a 6 after the 5 where it had 2.[12345] and it worked fine....
thanks
that rig-job for the dhclient worked for me too... went looking for a new version to dhclient after noticing static addressing worked fine but I wanted dhcp preferably... stumbled on that, worked fine..
Thanks, too
It worked for me as well using Kernel 2.6.7. I added 6 and 7 this time obviously. Thanks a lot!
I have solved the 8139t00 pro
I have solved the 8139t00 problem with RTL8139 with kernel 2.6.11:
Put in the 8139too module option parameters:
Media = 0x230
(bits 4+9=force full duplex; bit 5 = 100Mbps)
full_duplex = blank
multicast_filter_limit = blank
debug = blank
I am using Mandrake linux 10.2, limited edition 2005, AMD 64. I set the parameters in Mandrake control centre >> hardware >> configure module.
Hope this helps.
David