View previous topic :: View next topic |
Author |
Message |
jedikalex Tux's lil' helper

Joined: 23 May 2004 Posts: 99
|
Posted: Tue Jun 01, 2004 2:12 am Post subject: Net.eth0 failed to start |
|
|
Ok. I have a SOYO KT400 Ultra Black. AMD 2100+
I am using a nic that used tulip.. on start up i have it set to autoload the tulip module for my card and it does with no complaints. but then when It gets to Bringing eth0 up it fails to do it and says
"failed to bring eth0 up
Error: Problem starting needed services.
'netmount' was not started"
i have done dhcpcd eth0 and it doesnt do **** but take up time. ifconfig does not list eth0 or anything but lo after or before a dhcp eth0 or eth1.
For somereason all the kernels seem to hate me. I have had this probelm with the vanilla sources the gentoo sources and i cant even get the gaming sources to compile so idk what to do. Its times like this when Windows can be better. |
|
Back to top |
|
 |
po0f Apprentice


Joined: 08 Apr 2004 Posts: 162
|
Posted: Tue Jun 01, 2004 2:21 am Post subject: |
|
|
Did you set up /etc/conf.d/net correctly?
Then:
Code: | rc-update add net.eth0 default |
to have it start on boot up. |
|
Back to top |
|
 |
jedikalex Tux's lil' helper

Joined: 23 May 2004 Posts: 99
|
Posted: Tue Jun 01, 2004 2:33 am Post subject: |
|
|
yes its set up like that and yes it is in the start up |
|
Back to top |
|
 |
po0f Apprentice


Joined: 08 Apr 2004 Posts: 162
|
Posted: Tue Jun 01, 2004 2:50 am Post subject: |
|
|
I've always found it easier to include support for the network card in the kernel (not as a module).
Are you positive it's a tulip card? |
|
Back to top |
|
 |
jedikalex Tux's lil' helper

Joined: 23 May 2004 Posts: 99
|
Posted: Tue Jun 01, 2004 4:15 am Post subject: |
|
|
i have done it both ways for the kernel. I am positive because both the 20040.0 livecd and knoppix have it running with tulip |
|
Back to top |
|
 |
jedikalex Tux's lil' helper

Joined: 23 May 2004 Posts: 99
|
Posted: Tue Jun 01, 2004 4:17 am Post subject: |
|
|
i have done it both ways for the kernel. I am positive because both the 20040.0 livecd and knoppix have it running with tulip |
|
Back to top |
|
 |
ianskate n00b

Joined: 01 Jun 2004 Posts: 10
|
Posted: Tue Jun 01, 2004 5:07 am Post subject: |
|
|
Sadly, I've had this problem too.
I tried both .0, and .1, liveCD's. Neither one would get the card running. Once I got everything compiled, I tried getting tulip configured both as a module, and in the kernel, on two seperate occasions. It worked neither way. (Compiled or directly from the CD)
To ensure that the card was working, I tried it in my windows machine, and I even tested it with Fedora Core, and it did work. I really don't get it, but if there's a working solution to get tulip to work on "tulip supported" cards, I'd be grateful. (Maybe liveCD .2 will be a blessing in disguise... I'm not up to trying to experimental one though )
This must be a bug, although sometimes I wonder about how I got everything configured. I know it is mentioned on bugzilla, but it only seemed to apply to 2004.1, not 2004.0, which gave me the same results.
Oh well. I guess I'll just wait, and hope. |
|
Back to top |
|
 |
thechris Veteran

Joined: 12 Oct 2003 Posts: 1203
|
Posted: Tue Jun 01, 2004 6:32 am Post subject: |
|
|
this is perhaps the 6th post about "netmount failed to start" that i've seen. serach for some of the others in the installing gentoo forum and see if they can help you. from my understanding, most were solved by messing with modules.
i've had this problem in the past and asked this same question and also gotten no definitive answer. i later fixed the problem by re-installing gentoo. |
|
Back to top |
|
 |
ianskate n00b

Joined: 01 Jun 2004 Posts: 10
|
Posted: Tue Jun 01, 2004 4:34 pm Post subject: |
|
|
thechris wrote: | this is perhaps the 6th post about "netmount failed to start" that i've seen. serach for some of the others in the installing gentoo forum and see if they can help you. from my understanding, most were solved by messing with modules.
i've had this problem in the past and asked this same question and also gotten no definitive answer. i later fixed the problem by re-installing gentoo. |
I don't know, I added every single network driver, and it still didn't support my card, even though it was considered a tulip card.
I've tried compiling them all into the kernel, and added a number of them as modules to autoload.d and it still had no effect. As I mentioned, nothing worked from the LiveCD either. This could just be lack of driver support, or something goofy... |
|
Back to top |
|
 |
thechris Veteran

Joined: 12 Oct 2003 Posts: 1203
|
Posted: Sat Jun 12, 2004 8:42 pm Post subject: |
|
|
ok, now i get the problem agian. for a while i just did rc-update delete net.eth0 so i wouldn't waste startup time. then i can do as root:
Code: | modprboe tulip
dhcpcd
dhcpcd
|
where i usually need both passes of dhcpcd to get an IP.
but then i rc-update add net.eth0
and get the netmount error again. now i don't have to modprobe tulip though!
from advice in other threads:
Code: | bash-2.05b$ grep TULIP /usr/src/linux/.config
CONFIG_NET_TULIP=y
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
CONFIG_PCMCIA_XIRTULIP=m
bash-2.05b$ lsmod | grep tulip
tulip 42016 0
bash-2.05b$ lspci
bash: lspci: command not found
|
and my modules.autoload.d/kernel2.6 has nvidia and tulip listed in it.
also rc.conf has been modified as suggested in other threads, using the dhcp line instead of the static IP address line. i recently tried passign the & argument to dhcp in hopes it would boot faster due to it not waiting for netmount to fail.
at one time this worked for me, not sure what happened. i think it worked when i was using the 2.6.5 speedy sources with reiser4 ironically enough. with 2.6.5 love or gentoo it seems not to work! |
|
Back to top |
|
 |
cyrillic Watchman


Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Sat Jun 12, 2004 9:50 pm Post subject: |
|
|
Some NIC drivers are sensitive to IRQ routing problems (tulip is one of them), and this can make the NIC not work even though the hardware is fine.
Try this, and look to see if eth0 is getting an IRQ assigned to it.
Code: | # modprobe tulip
# dmesg
# ifconfig eth0 up
# cat /proc/interrupts
# ifconfig -a |
If you are having problems with this, you may need to pass "acpi=off" to the kernel at boot time. Or you may need to recompile the kernel with different settings for ACPI, APIC, IO-APIC to get IRQ routing working properly. |
|
Back to top |
|
 |
thechris Veteran

Joined: 12 Oct 2003 Posts: 1203
|
Posted: Tue Jun 15, 2004 11:32 pm Post subject: |
|
|
the soundcard and network card are shareing an IRQ. |
|
Back to top |
|
 |
cyrillic Watchman


Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Wed Jun 16, 2004 12:56 am Post subject: |
|
|
It is normally OK for PCI devices to share IRQs, but if you move the soundcard or the NIC to a different PCI slot, the IRQs should get reassigned so they are not shared.
As long as eth0 shows up in /proc/interrupts , then you should be able to get it working (i.e. with dhcpcd or a static address).
If the NIC is losing the connection or its IRQ, then you should see some errors in dmesg related to tulip or eth0. |
|
Back to top |
|
 |
|