User talk:Dinghy

Hi Dinghy,

Thanks for the edit. :)

In this case it was needed, otherwise I would get the error message: 'IP: No interfaces found' I don't know why, tried all sort of device names (e.g. eth0, eth1, udev-name, etc.), but it would simple not activate the interface. After adding the module (in this case r8168), it could perfectly setup the interface on eth0.

If needed, I'll contact the dev, otherwise the note should be fine. ;) Francoism (talk) 22:02, 18 January 2016 (UTC)

Hi. Thanks for commenting on this.

Actually, r8168 or r8169 are kernel modules for Realtek devices. In your case this worked, since you obviously have this kind of device in your machine. Therefore, adding precisely this would not help other users with other devices.

This is why I edited it to redirect users to the appropriate page (Networking#Device Driver) where they can find out which modules they need for their machine.

About eth0 etc.: this would never have worked, as is the "pointer" to the first ethernet card in your machine, not a driver saying how to use this card.

You might want to look into udev and its issues, since the module for your card should have been loaded automatically (except of course if your Realtek card's PCI ID as seen in lspci is garbled -- therefore my question in the edit summary).

Hope this helps! — Dinghy (Talk) 22:15, 18 January 2016 (UTC)

I agree, just give the r8169 as an example, but your edit is 100x times better. :)

The udev device name cannot be used when using the ip kernel parameter. To check if I was correct, I've tried using enp3s0 as the device-name, but that didn't work.

I'm still searching for the reason why I do need to load the module, but it may be better to open an issue instead.

It may be something stupid, like a configuration error, but so far I've followed everything as describe on the Wiki and forums. In case I was wrong, I'll remove the note. :)

Francoism (talk) 22:26, 18 January 2016 (UTC)