| View previous topic :: View next topic |
| Author |
Message |
crazyzed
Apprentice
Joined: 26 Mar 2004
Posts: 154
|
 Posted: Tue May 01, 2007 6:36 pm Post subject: no eth0 when ifconfig |
 |
|
My internal NIC seams to be dead so I'm trying to get an old 10/100 PCI card running but I guess I'm doing something wrong. The card is an AcerLAN ALN-325 and I have built a whole lot of drivers into kernel to be sure to have compability. When I reboot into the new kernel I get during startup
| Quote: | Starting eth0
Bringing up eth0
dhcp
network interface eth0 does not exist
Please verify hardware or kernel module (driver)
ERROR: cannot start netmount as net.eth0 could not start |
And when I run dmesg I get this
| Quote: | e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp 0000:00:06.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:00:06.0: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.27
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 17 (level, low) -> IRQ 16
eth0: RealTek RTL8139 at 0xdc00, 00:60:67:73:2c:42, IRQ 16
eth0: Identified 8139 chip type 'RTL-8139B' |
which looks good to me?? But ifconfig does only show me the loopback device. eth0 is configured to use dhcp and it's my old configuration that worked with my internal device. So why is eth0 not created, what have I missed to do? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Tue May 01, 2007 6:50 pm Post subject: |
|
|
crazyzed,
Please post your lspci output.
Your post shows a RealTek 8139 chipset being located and its driver loading (8139too)
As you say, that looks good.
Your post also shows e100, which is for an Intel chipset, forecdeth, which supports nVidia and 8139cp which is for a different Realtek card.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
mudrii
l33t
Joined: 26 Jun 2003
Posts: 789
Location: Singapore
|
| Posted: Wed May 02, 2007 7:22 am Post subject: |
|
|
check if module startead with lsmod
and ifconfig -a will show you all network interfaces active and inactive in your system
_________________
www.gentoo.ro |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Wed May 02, 2007 7:47 am Post subject: |
|
|
/etc/udev/rules.d/70-persistent-net.rules could be setting your new NIC to eth1 as it has a persistent rule setting your old NIC to eth0.
You can check by looking at this file. If it is setting the new NIC to eth1, you can edit /etc/udev/rules.d/70-persistent-net.rules to swap them over and reboot (some people say running udevstart is enough).
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
crazyzed
Apprentice
Joined: 26 Mar 2004
Posts: 154
|
| Posted: Wed May 02, 2007 12:53 pm Post subject: |
|
|
ok, I will try those things when I get home from work.
I have done some changes to kernel, I removed all nic-drivers except the 8139too (built into kernel, no module). Now dmes looks like this
| Quote: | 8139too Fast Ethernet driver 0.9.27
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 17 (level, low) -> IRQ 16
eth0: RealTek RTL8139 at 0xdc00, 00:60:67:73:2c:42, IRQ 16
eth0: Identified 8139 chip type 'RTL-8139B' |
ifconfig is the same though (will try ifconfig -a when I get home)
| Quote: | lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b) |
and lspci gives me
| Quote: | 00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:08.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
00:08.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
00:08.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
00:0d.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7800 GS] (rev a2) |
|
|
| Back to top |
|
|
crazyzed
Apprentice
Joined: 26 Mar 2004
Posts: 154
|
| Posted: Wed May 02, 2007 9:16 pm Post subject: |
|
|
ifconfig -a showed me that it was configured as eth2 and editing the /etc/udev/rules.d/70-persistent-net.rules solved my problems  thanx guys! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
