| View previous topic :: View next topic |
| Author |
Message |
tristure
Apprentice
Joined: 30 Oct 2003
Posts: 270
Location: France
|
 Posted: Sat Jun 19, 2004 12:06 pm Post subject: network down after etc-update |
 |
|
Hi, I ran etc-update and accepted the update for /etc/init.d/net.eth0.
Now my network won't start.
When I boot (or try to restart /etc/init.d/net.eth0) I just get "Bringing eth0 up via dhcp" (with the previous version I just got "Bringing eth0 up")
then I get [!!] error and nothing...
My /etc/hosts is the same as before, /etc/conf.d/net seems okay too, I got the line
iface_eth0="dhcp" in it (well, same as before...)
Does anybody have ideas on how I could get my network back, or post the listing of an "old" net.eth0 script??
Thanks a lot! |
|
| Back to top |
|
 |
tristure
Apprentice
Joined: 30 Oct 2003
Posts: 270
Location: France
|
| Posted: Sat Jun 19, 2004 12:30 pm Post subject: |
|
|
A few additional info :
rc-update doesn't help (net.eth0 is already in default runlevel)
/sbin/ifconfig show lo only
dhcpcd eth0 doesn't do anything.
The live CD still works. I get network with it.
Thanks for your help; I'm bumped here! |
|
| Back to top |
|
|
Lajasha
Veteran
Joined: 17 Mar 2004
Posts: 1040
Location: Vibe Central
|
| Posted: Sat Jun 19, 2004 4:40 pm Post subject: |
|
|
post up your /etc/conf.d/net file maybe you are skipping something in there...
Also was your network card compiled into the kernal or a module.. I ask this cause it might have updated the /etc/modules.autoload.d/kernel-2.X file and if it was a module that you autoloaded there then it prolly isn't being loaded any more.
_________________
Come and play in my land |
|
| Back to top |
|
|
tristure
Apprentice
Joined: 30 Oct 2003
Posts: 270
Location: France
|
| Posted: Sun Jun 20, 2004 7:54 pm Post subject: |
|
|
Here's some additional info :
| Quote: | # /etc/conf.d/net:
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/conf.d/net,v 1.7 2002/11/18 19:39:22 azarah Exp $
# Global config file for net.* rc-scripts
# This is basically the ifconfig argument without the ifconfig $iface
#
#iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
#iface_eth1="207.170.82.202 broadcast 207.0.255.255 netmask 255.255.0.0"
# For DHCP set iface_eth? to "dhcp"
# For passing options to dhcpcd use dhcpcd_eth?
#
iface_eth0="dhcp"
#dhcpcd_eth0="..."
# For adding aliases to a interface
#
#alias_eth0="192.168.0.3 192.168.0.4"
# NB: The next is only used for aliases.
#
# To add a custom netmask/broadcast address to created aliases,
# uncomment and change accordingly. Leave commented to assign
# defaults for that interface.
#
#broadcast_eth0="192.168.0.255 192.168.0.255"
#netmask_eth0="255.255.255.0 255.255.255.0"
# For setting the default gateway
#
#gateway="eth0/192.168.0.1"
|
My etc/modules.autoload.d/kernel-2.6 looks like this :
| Quote: |
# /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.6,v 1.1 2003/07/16 18:13:45 azarah Exp $
#
# Note that this file is for 2.6 kernels.
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line. Comments begin with # and
# are ignored. Read man modules.autoload for additional details.
# For example:
# 3c59x
usbserial
nvidia
supermount
|
It's really the same as it was before.
Here's the output of lsmod and lspci : I think the network card drivers are loaded OK , as they were before.
bash-2.05b$ lsmod
Module Size Used by
ehci_hcd 24324 0
8139cp 16384 0
mii 4224 1 8139cp
via_agp 6016 1
agpgart 28328 2 via_agp
supermount 35988 3
nls_iso8859_15 4480 4
nls_cp437 5632 3
nvidia 1700908 10
sg 29984 0
sr_mod 13988 0
scsi_mod 67264 2 sg,sr_mod
bash-2.05b# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:08.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0a.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3)
I tried and emerge system, emerge baselayout, tried some different versions of the net.eth0 think, and still nothing works. It's really driving me nuts.
Thanks for your help!! |
|
| Back to top |
|
|
Lajasha
Veteran
Joined: 17 Mar 2004
Posts: 1040
Location: Vibe Central
|
| Posted: Sun Jun 20, 2004 8:06 pm Post subject: |
|
|
Try checking out /var/log/messages to see if it is logging more info about the problem there.
_________________
Come and play in my land |
|
| Back to top |
|
|
tristure
Apprentice
Joined: 30 Oct 2003
Posts: 270
Location: France
|
| Posted: Sun Jun 20, 2004 8:40 pm Post subject: |
|
|
Ah, here's some significant progress!
I checked dmesg and saw :
| Quote: | 8139cp: 10/100 PCI Ethernet driver v1.1 (Aug 30, 2003)
8139cp: pci dev 0000:00:09.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
|
So I modprobed 8139too, and restarted net.eth0 : miracle, it worked!!!
Conclusion : I was wrong : there seems to be a driver problem. Now my problem is :"How come this hardware was suddenly associated to a different driver than it was before?"
And how can I make 8139too to be loaded instead of 8139cp? I assume I could add 8139too in my modules.autoload.d/kernel-2.6 file, but by doing this I would still have the 8139cp loaded, which I don't really want. How can I make the correct hardware / driver association???
Thanks a lot for your help, I'm getting closer to the end of this! |
|
| Back to top |
|
|
Lajasha
Veteran
Joined: 17 Mar 2004
Posts: 1040
Location: Vibe Central
|
| Posted: Mon Jun 21, 2004 2:39 am Post subject: |
|
|
did you build the 8139cp into the kernel? If so then you will need to reconfigure it and while your in there might as well put the new one in.
_________________
Come and play in my land |
|
| Back to top |
|
|
meowsqueak
Veteran
Joined: 26 Aug 2003
Posts: 1549
Location: New Zealand
|
| Posted: Thu Jul 08, 2004 3:38 am Post subject: |
|
|
I too have this problem - my NIC needs 8139too but it's detecting and loading 8139cp instead. dmesg has this:
| Code: | 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp: pci dev 0000:01:05.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
|
If I modprobe 8139too after boot, I can start net.eth0. Putting 8139too into /etc/modules.autoload.d/kernel-2.6 resolves this, but it still loads 8139cp as
tristure mentioned.
EDIT: I put 'alias eth0 8139too' in /etc/modules.d/aliases and that seems to have fixed it. |
|
| Back to top |
|
|
|
Networking & Security
