eth0: Not installed

Same for me.
2.2.3 ok
tb 2.6 and elastix 1.0 same problem.

and the eth0 is not down (ping, etc ...) ok!
only this information : eth0 not installed .

And on the first screen info server.
Asterisk not installed
mysql not installed....

On freepbx all is ok!

Why this diffrent information?????

If the modules aren't installed no amount of rebooting is going to help.

At some point I'll try to sit down and write a how-to, but by the nature of the subject it requires actual thinking on the part of the reader, and those are the most difficult to write.

What usually needs to happen in these cases:

1) google the hell out of your network device to see if there's a linux driver out there somewhere.

2) if you find one, follow the instructions that come with it.

In a bit more detail, you can do:

lspci -v

to see if you can find some more information about your device. Just because it says "ACME Network Card" on the box doesn't mean that the chip on the card (which is the important part) is an "ACME" chip. Using lspci might give you the chip name.

Either way, you're going to have to google variations of "ACME network card linux driver" or "chipname linux driver source" and similar. You'll find a lot of useless garbage, and you'll find a lot of people in forums asking the exact same question as you. Sometimes, however, you'll find a link to driver source code.

What I usually do once I find a driver is throw another network card in the box that I know works, and get it set up for Internet access.

Then I install development tools: yum install kernel-devel gcc c++

Once I've got the dev tools, I download the drivers I found:

wget http://host.of.drivers/path/to/drivers.tar.gz

Once I get them I untar and uncompress them:

tar zxvf drivers.tar.gz

then start exploring the directory tree it created. Look for README files, or INSTALL files, or a doc directory or something that might have more information.

Regardless, it's usually a simple matter of going into the source directory and doing "make install" and then "depmod -a" and then modprobing the driver that was just built: "modprobe acme". NOTE THAT THE DRIVER WILL PROBABLY NOT ACTUALLY BE CALLED ACME (I guarantee that someone will email me and say "I have a hessen-feffer 5000, but I can't find the acme driver you're talking about.") However, if there are instructions, follow them.

The important conceptual information you should take from this is that:

If the kernel you're using does not have a driver for your hardware, you're going to have to find, build, install and configure a module for your hardware.

To build the driver, you're most likely going to need, at a minimum, the kernel headers (contained in the kernel-devel rpm,) a compiler (gcc,) and the source code for your device.

Just an upfront warning: many, many times you will have a device in your hand that uses a supported chip. However, the driver for that chip does not recognize the PCI ID for that device (this is usually because the card is a minor revision of another supported card, or it's a new brand or something like that.) If you know how, you can edit the source code for the driver in question and add support for that PCI ID, but that's way, WAY outside the scope of this forum post.

It appears I've misread the problem.

You guys are saying the NIC works, but "it" says eth0: not installed?

Can you be a bit more descriptive when defining what "it" is? Are you talking about the motd when you log in as root?

I'll keep my lame humor to a minimum since you're using google to translate.

Try using system-config-network instead of netconfig to make your changes.

I don't know if it will do any good, but it's worth a shot.

That motd (which stands for "message of the day") is generated by a script. It is purely informational. I suspect that, for some reason, the network isn't up when that script runs.

Try running:

/usr/local/sbin/motd.sh

and then just log out and log back in. It should show the IP. Then reboot and see if the problem comes back. It's probably not an issue, it's just that the script that generates that information runs before your network device is ready.

I hope that helps.

Ok, for some reason the $IPADDR variable isn't getting set.

Run the following commands:

ifconfig eth0

ifconfig eth0|gawk '/inet addr/{print $2}'|gawk -F: '{print $2}'

And post the output.

Interesting mine says addr!

Scott

His also says "Masque" so I'm assuming this is an artifact of i18n.

Just change the script to use "adr" instead of "addr" and it will work. Keep in mind that it is cosmetic and doesn't serve a real purpose.