Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] New install - no net?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Dr Croubie
Apprentice
Apprentice


Joined: 21 Nov 2006
Posts: 155

PostPosted: Sat Aug 09, 2014 10:39 am    Post subject: [Solved] New install - no net? Reply with quote

Like most things, it's probably an easy thing I've forgotten, but I just can't figure it out.
I had a perfectly working system on a 64GB SSD, until a) I needed more room on a virtualbox, and b) yet another bad nvidia driver update.

So to solve both of them, I thought I'd buy a nice spanking new 128GB SSD, and my first ever Radeon (I've been an nVidia user since my first Riva).
Anyway, they're besides the point. Rather than booting with a livecd etc, I just booted to my old system (which was still working, at least on the command line), and installed on the new SSD.

I followed the handbook pretty much to the letter, except I thought I'd try hardened-sources for the hell of it (and chose a hardened profile).

Copied over most of my old working config files, like make.conf and src/linux/.config, rebuilt the entire system to working, including emerging udev etc, and rebooted to the new system. The only other 'new' thing was that I just didn't want to muck around with framebuffers this time so I disabled that in the kernel, otherwise fairly similar.

But I just got an error on boot 'cannot find net.eth0, kernel module may not be configured' or something like that. After a few hours, I gave up the hardened-sources and went back to gentoo-sources. Built to that, rebooted, and no net.eth0.
Finally, I just copied the old kernel from the working /boot to the new /boot, and booted to that. Still no net.eth0.

So it's not a kernel / module problem, whichever kernel is installed is building the same modules, so it's a software / configuration thing. udev is installed, ln -s net.lo net.eth0, hostname and net and all the rest should be the same.

What am I missing?


Last edited by Dr Croubie on Mon Aug 11, 2014 5:15 am; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Sat Aug 09, 2014 11:40 am    Post subject: Reply with quote

https://forums.gentoo.org/viewtopic-p-7590914.html#7590914
Back to top
View user's profile Send private message
Dr Croubie
Apprentice
Apprentice


Joined: 21 Nov 2006
Posts: 155

PostPosted: Sat Aug 09, 2014 12:47 pm    Post subject: Reply with quote

OK, thanks, but that's really hard to follow.
I'm aware that udev like stuffing things up and renaming things to whatever it feels like, I've met that before on previous occasions when upgrading udev has borked me.

I was kind of hoping with a fresh, clean install, to bypass all of that nonsense and have something working straight up. (although, after 10 years on gentoo I should learn not to get my hopes up on things working, but that's part of the fun I suppose).

So you're saying that I do have the right kernel modules etc loaded (I'd think so, nothing's changed), but net.eth0 isn't called net.eth0 anymore, it's called enbsomething? (Surely at that point in the handbook there might be a hint along the lines of "don't use net.eth0 because it won't be there when you reboot"?)
Or is there any way to install without udev because all it does is make trouble?
Barring that, do I have to figure out what the new name is and update my conf.d/net to the new name? Or where do I rename it back to its rightful net.eth0? Or something else?

FWIW, I'm currently on my old working system. cat /etc/udev/udev.conf gives a file with nothing but comments. ls /etc/udev/rules.d is empty. my /etc/conf.d/net has the usual config_eth0="192etc and routes_eth0="defaultetc, straight from the handbook, I copied that file straight from the old to the new system too.
Back to top
View user's profile Send private message
Dr Croubie
Apprentice
Apprentice


Joined: 21 Nov 2006
Posts: 155

PostPosted: Sat Aug 09, 2014 1:14 pm    Post subject: Reply with quote

ps, when I do ifconfig, I get nothing but net.lo, not a net.enswhatever. As I understand it (which I very well don't), if it were a problem of udev renaming my interfaces, I'd have an interface just called something other than net.eth0, I'd have something else there? Except I don't.
Back to top
View user's profile Send private message
cwr
Veteran
Veteran


Joined: 17 Dec 2005
Posts: 1969

PostPosted: Sat Aug 09, 2014 1:21 pm    Post subject: Reply with quote

Dr Croubie wrote:
ps, when I do ifconfig, I get nothing but net.lo, not a net.enswhatever. As I understand it (which I very well don't), if it were a problem of udev renaming my interfaces, I'd have an interface just called something other than net.eth0, I'd have something else there? Except I don't.


Check with ifconfig -a

Will
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Sat Aug 09, 2014 1:42 pm    Post subject: Reply with quote

Dr Croubie wrote:
(Surely at that point in the handbook there might be a hint along the lines of "don't use net.eth0 because it won't be there when you reboot"?)

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=3#doc_chap1
Quote:
The interface name on your system can be quite different from eth0. Recent installation media might show regular network interfaces names like eno0, ens1 or enp5s0. Just seek the interface in the ifconfig output that has an IP address related to your local network.

In the remainder of this document, we will assume that the interface is called eth0.

:D

I have just point you to ssuominen post because it should answer your problem.
But if you don't wish to have any trouble and keep using eth0 (something i can understand as i myself keep using eth0 too)
Just do ssuominen's point #3 inverse, as his point 3 was to help user getting the stupid enostuff name back.
So a :
3. Verify you are using the net.ifnames=0 kernel commandline
Back to top
View user's profile Send private message
Dr Croubie
Apprentice
Apprentice


Joined: 21 Nov 2006
Posts: 155

PostPosted: Mon Aug 11, 2014 5:11 am    Post subject: Reply with quote

OK, I must have skipped that line in the 'setting up' section, because I was booting to my previously-working system and chrooting from there, the net already worked on that. I didn't see it in the 'second' bit on setting up net again...

Maybe it was because this system had grub2 and I've only ever used grub0 before, but I was trying the net.ifnames=0 and it was doing nothing, so that's why I thought it wasn't a udev thing. I was thinking kernel/drivers but looks like uedv was to blame.
ifconfig -a found it though, and I think it's fitting that my new (un)predictable network name is an anagram of pen15.

I'm still not sure what all the hoopla is about udev renaming things, on my last M2N-SLI motherboard I had eth0 and eth1 running together, and they were always the same (I even marked the adapters with permanent marker), and they only swapped around and became unpredictable after the udev upgrade that was meant to 'fix' and 'prevent' such things.

On my new FXA990 board there's only 1 port though, so I've just let udev do its thing and I've changed my files to point to the new name (of course now I'll just have to check everything else to make sure it doesn't reference eth0 anymore).

Thanks for the help guys.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum