KnoppMyth version R5A16.

I can't get eth0 to start up on boot.

I have run netcardconfig, select 'no' on the first prompt so I can use static ip addresses, enter in all the info, and exit. (The ip I chose is 192.168.2.103) I then run ifconfig to confirm eth0 is up and is correct with the ip addresses I just entered (there is also an entry showing for lo - the loopback at ip 120.0.0.1). The address of 192.168.2.103 is also what I entered in the mythtv-setup->general section for the frontend and backend addresses.

Everything works - meaning I can ssh in from another machine as well as being able to select Watch TV on the front end.

Then whenever I reboot, the frontend can't connect to the backend server anymore (giving me a message about making sure I have the right ip in the setup.) In the sea of messages that scroll by on startup, I did catch a glimpse of "Failed to bring up eth0".

I run ifconfig to check on eth0, and see that eth0 is not showing anymore, only the loopback entry is there.

I then need to manually bring up eth0 by using the command: "ifup eth0"
Then all networking works again - until the next reboot. Can someone please help?

Here is the content of my ifcfg-eth0 file:

Code:

root@mythtv:~# more /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.2.103
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes

Here is the content of the interfaces file:

Code:

root@mythtv:~# more /etc/network/interfaces
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
# automatically added when upgrading
auto lo
iface lo inet loopback


# I added the auto eth0 line below. It wasn't in the original file.
# But it doesn't seem to make a difference,
# eth0 won't start up automatically either way.
auto eth0

iface eth0 inet static
        address 192.168.2.103
        netmask 255.255.255.0
        network 192.168.2.0
        broadcast 192.168.2.255
        gateway 192.168.2.1

No help here, other than to say that I'm having the same problem. I have to do a "pump" command after bootup. I tried putting into bootmisc.sh, but that's apparently "too early" to help, and I get (another) "network unavailable".

The command to fix is:
pump -i eth0

Then I (re) run my smbmounts and start samba (it fails if I set it to auto run, because the network isn't there...)

I'm on R5A26, using onboard ethernet on MSI K8N NEO4-F (non-platinum) mobo.

Anyone find a solution yet??? I am on R5A26. My onboard NIC died after a power outage... So I put in a new one, and it works only if I run netcardconfig after every reboot.....

Help please....

Come on people, work a little harder on those searches. It seems like I've had to post the same simple answer to 4 different threads in the last couple weeks.

Figure out what kernel module your card needs and make sure that it gets loaded before the ethernet start up is attempted. Using the lsmod command before and after you bring the network up is a good start.

The fundamental problem with search is that everyone thinks and words things differently. Just because we posed the question, doesn't mean we didn't search.

Might have been easier and better for the community had you just posted the answer, rather than criticize, because we asked a question.

Anywone posting the answer would be greatly appresiated.

in /etc/network/interfaces you don't have to use two seperate auto lines for the loopback and eth0

auto lo eth0

in /etc/modules.conf put

alias eth0 <module>

where <module> is the kernel module that your card uses.

if your using dhcp, add eth0 to to auto line like above and put this in interfaces.

iface eth0 inet dhcp

do a "man interfaces" for more information

Demonstratably not true. Just for instance, ever seen a game show called "Family Feud"? The answers to the survey questions show remarkable clustering. This is also the whole principle behind the keyword searching they tried to teach you for using a library card catalog in middle/high school English.

Also, as I've said before, 9 times out of 10 searching for the exact words that people put in the titles of their posts will immediately find a relevant match. In this case a search for "eth0" and "boot" would have found one of the threads I was talking about in the top 5: http://mysettopbox.tv/phpBB2/viewtopic.php?t=8844&highlight=eth0+boot I find this result extremely frustrating, if people can put these words in their titles, why can't they use them successfully in their searches and avoid making yet another FAQ posting?

For those who are having the same problem and want a solution rather than a bunch of flames and archaic tech speak:

at console:

look at the first line it will have the kernel module name followed by the interface name, in my case:

natsemi is what we are looking for..

now

go about to the middle of the file and add natsemi (or whatever yours says) to a line of it's own. In my case I put it just prior to the soundcore entry.
ctl-O to write the file ad ctl-X to exit.

reboot and see if that helps.

See tjc, was that so hard????

????
Here's what I get:


Do I put "forcedeth" into the modules file?

I'm in the boat where: "at bootup, it says 'network unavailabl', but later if I issue a pump, it'll work"

looks like your module should be: nvnet
http://forums.debian.net/viewtopic.php? ... 21d02c985a

when you do a "lsmod" after the ehternet card is up, do you see the nvnet module?

scanman717, "archaic tech speak" ? Were not talking about gardening. The terminology is basic and directly related to the subject.

Hmmm... Nope.

But I do see this:


I can try that one, but it'll have to wait until tomorrow. Housewives is on in 14 min, and I'd take -WAF points if I messed that up.

I'll look for the forcedeth before/after my "fix" script, to see if that's the net result of my "pump" command that I perform manually after it boots.

BTW, it's the onboard lan on a "near-dragon" MSI K8N Neo4-F (non-Platinum).

figued you had already tried that.. yes add an it your modules.conf.
ie..

alias eth0 forcedeth