Where is my network !?

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

Hi world !

So I just finished my second gentoo and both times I got the same problem : I don't have access to internet.

I can't ping ==> connect: Network is unreachable.

So here is my ifconfig : ifconfig

My /etc/conf.d/net : net

The /etc/hosts file : hosts

I'm new to this so hope it's not something stupid to have troubles with ^^

Thanks for your help !

B.T.W. I'm on VMware and my "network adapter" is on Bridged (but it doesn't work on NAT either).

tryn · Posted: Mon May 11, 2015 8:47 pm Post subject:

TitiTwister

One thing that might help is this.

NeddySeagoon · Posted: Mon May 11, 2015 8:52 pm Post subject:

TitiTwister,

What does

krinn · Watchman Joined: 02 May 2003 Posts: 7470

Networking for dummies

1/ find your card

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

krinn · Watchman Joined: 02 May 2003 Posts: 7470

No, i won't tell you.

But you need to add that option to your kernel, and (i'm sure you won't like that), you have two choices (well, three in fact):
a) build the driver buildin the kernel -> need recompile, and install it -> make && make install
b) build the driver as module -> need to recompile modules and install them (make modules && make modules_install)
c) If your kernel was so badly built that you lack some symbols and the modules compilation fail, it is well, really just because you did an ugly kernel for networking

In this case, you're doom, making it as module or build in, you will have to recompile the kernel AND the modules so they get the new symbols too.
But even you miss to add your network card driver, could we assume you weren't crazy enough to not miss all networking options?

In case you are doom to c) or scared by a) or b) just use c) It is nothing more than just checking the network driver for your card that will force you to check other needed options to enable it, and the "OMG it was so hard to configure" is just limit to typing: make && make modules modules_install && make install

Just to be sure: you know your driver name to use right? I mean, not everyone use r8169, that's the one for my card in my example, and if you don't have that kind of card... Because also i'm unsure if a card under vmware need some vmware driver or just its native one.

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

Jaglover · Posted: Mon May 11, 2015 11:38 pm Post subject:

Actually, if you enable it as a module you need to do make modules and make modules_install, this will enable your NIC, no reboot needed.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

krinn · Watchman Joined: 02 May 2003 Posts: 7470

TitiTwister: you seems a bit lost with "driver" and "module".
That's the same. Say i need the r8169 for my card. I'm going to my kernel source and look where is the r8169 driver.
If i check <*> or <M>, i will have the driver, it's just the handling that will change, but the driver will be there.

<*> the driver is build inside your kernel, it mean everytime your kernel boot, the driver is load (even you don't have the card, it is just load). So if you build it like that, it mean you need to reboot.
<M> the driver is load when you ask it to load, for most people, they will still not need to ask it loaded, as dev manager (eudev, udev...) will load it for you when it see you have a device that need it (but when the device is discovered, and except if the device is hotplug, it is then when booting).
So if you build it as module, you install it, and as your card is not hotplug, you need to ask it loaded: modprobe r8169 (or lazzy ones can just reboot, and it will be discovery at booting by dev manager that will use his little fingers and type <modprobe r8169> for you).

As you fail to see, your pic showing your lspci -k output, still didn't gave you the driver name to use. That's because your kernel doesn't have the driver at all. To get it, you can google that, or wait some users giving you the answer, or browse the kernel and search what driver match it, or redo the <lspci -k> but with a kernel that handle many drivers (including the one you need). That's the kind of kernel you have in installationcd that of course have as many as possible.

But it is more for kernel for dummies than network for dummies

If you need more about kernel, read the linux sea (excellent) from sven http://swift.siphos.be/linux_sea/
Or you can check kernel entry in the gentoo wiki (that sure sucks) http://wiki.gentoo.org

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

Ok I'm getting close I think ^^

So now I know I need this driver now : AMD PCNet32 PCI support.
Which is now built in my kernel. But still no changes ( it's this one I had before rebooting for the first time ).
The lspci run still show no driver in use.

So now I saw this while rebooting : reboot error

Maybe it's something I don't know.

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

Are you sure you need or want netmount? Otherwise, remove it.

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

Ok ok ok

So I managed to make this driver appear on my lspci run.

But when I do a ifconfig -a still no eth0.

And when I do :

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

You should find out what the names of your network interfaces are. That's the reason why netifrc is not recommended.
Try

TitiTwister · n00b Joined: 08 May 2015 Posts: 18

NeddySeagoon · Posted: Tue May 12, 2015 7:10 pm Post subject:

TitiTwister,

Thats safe. If you want your eth0 back, add