[Solved] eth0 does not exist

[KLIM8D]

Hello,

I've just finished the install of gentoo, but after reboot my network device cannot be found.

I configured and compiled the kernel from hardened-sources. When it was done compilling this messages appeared:
"Found 8 modules mismatch(es)"
Is this bad, and could this be the reason it can't find my network device?

I'm installing on a Intel Desktop Board D425KT (Intel Atom), which have this network controller:
Realtek RTL8105E

In the kernel menuconfig, I enabled all Realtek and Intel under "Ethernet device support".
How ever when I run "make menuconfig" from the same .config file, only Intel (82586/82593/82596) devices are enabled and the list way shorter than before - containing no realtek.

lspci -k from livecd:

[olek]

Sounds to me, as you are working with other kernel sources as you did when you configured it. Do you remember the version?

What do

[KLIM8D]

[oquol]

[KLIM8D]

[oquol]

[NeddySeagoon]

KLIM8D,

It only matters a little if you use <M> or <*>.

<M> means make a loadable module, so the code can be removed from the kernel. Loadable modules are stored in /lib/modules/`uname -r`/
Most modules are auto loaded but udev or the kernel but not normally network modules, so if you use <M> you may need to name the module in /etc/conf.d/modules so its loaded at boot.
You can load it manually too.

If you use <*> the selected code is built into the kernel binary. Its loaded with the rest of the kernel and cannot be removed from memory.

There are several advantages to <M>. You can compile and load a module into the running kernel, no reboot required.
Many modules take module parameters at load time. Sometimes the correct module parameter needs to be determined by trial and error.
Loadable/unloadable modules mean you can try a parameter, if its not right, unload the module and try another one.
With <*> (built in) code a reboot is required.

Many USB Wifi devices and a few sound cards are like this.

What does

[KLIM8D]

I seems like it didn't boot with the right kernel, it used the one from the install media.

How ever, new problem. I'm not able to boot - my system now gets kernel panic at boot.
Here's some pictures of the screen:
http://imageshack.us/g/443/img20120921012642.jpg/

[supperskidvn]

The drivers for your Network card are either:

- Not installed
- Failed at start up
- Not configured correctly.

If you include the Make/Model/version of your network card we can start helping from there.

In linux device names are assigned to hardware devices. Skyhome In this case: eth0 corresponds to an ethernet card.

In a terminal (console) type the following and paste the result along with your card information:
Code:

[wcg]

Note: booting what you suspect is the wrong kernel would be a
"/boot/grub/grub.conf" problem. (That is where you list kernels
to be displayed as boot options in the grub boot menu.)

grub.conf syntax and logic is a whole subject of its own.

If the Gentoo manual is not enough:
http://www.troubleshooters.com/linux/grub/index.htm

There is a sea change in progress from grub-1.x to grub-2.x
in the upstream grub project. Grub-1.x, also known as "grub-static"
in Gentoo Portage, is still the stable grub bootloader in Gentoo,
but many systems are now using grub-2.x for a variety of reasons.
There are differences in syntax, etc.

(Some of the reasons for moving to grub-2.x are GPT, a new partition
table format that can accomodate large disks and has other
advantages over DOS MBR format, and EFI system
initialization:
http://rodsbooks.com/gdisk/booting.html
http://www.rodsbooks.com/efi-bootloaders/index.html
http://rodsbooks.com/gdisk/bios.html
)

You probably do not need to make this change from grub-1.x to
grub-2.x simply to boot kernels in your new Gentoo system, but if
the online grub documentation seems to be talking about two
different programs at times, this may be why. You need to know
whether it is grub-1.x or grub-2.x that a page is referring to.
_________________
TIA

[KLIM8D]

[KLIM8D]

Great, it's solved now. I found this post: http://askubuntu.com/questions/71332/kernel-panics-with-cannot-open-root-device-error-where-do-i-append-the-root

Where the guy had the same error messages as I did. Followed some of the suggestions and compiled my kernel with all ext3 + ext4 options and nvidia-sat, and some more. Finally I can get started setting up my system

[wcg]

So, grub issues are not relevant to this system, and you probably know
lilo's config file from use with another Linux distribution. Your error log
shows that the kernel is possibly not finding the root partition. In grub.conf,
it is specified as "root=/dev/[partition on a device]" as part of the
"kernel" command.

Perhaps you need lilo to pass the same information to the kernel,
with an "append=" within the "image=" sections for the different kernels.

[KLIM8D]