Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 536290 - Network not working after chrooting from install-x86-minimal into stage3
Summary: Network not working after chrooting from install-x86-minimal into stage3
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Stages (show other bugs)
Hardware: x86 Linux
: Normal blocker (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-11 08:54 UTC by fachat
Modified: 2015-01-11 10:28 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fachat 2015-01-11 08:54:54 UTC
I am trying to install gentoo on a small VIA EPIA-M Mini-ITX board. Because of the processor architecture I can't use i586 or later, but have to use x86.

I installed "install-x86-minimal-20141209.iso" onto an USB stick, booted from there, and downloaded "stage3-i486-20140415.tar.bz2". Note that the network was working perfectly there, with dhcp, default routes, dns etc, even IPv6 (address).

I unpacked the stage3 tree into another mounted drive, then did all the rbind mounts (/sys, /dev, /proc, even /etc/resolve.conf), made them rslave mounts as well. 

When I then chroot into the new environment, networking suddenly ceased to work there. It works fine outside the chroot, but not within.

With "not working" I mean: even a "ping -v -I 192.168.0.130 192.168.0.1" gives a "Destination host unreachable" - where 192.168.0.1 even is the default route!

It should not be DNS-related (and thus not resolve-related, as /etc/resolve.conf was copied over, even within the chroot, ifconfig and route show a perfectly well configured network. It ... just doesn't work.

Unfortunately I only find pages on the web where someone forgot to copy resolve.conf, but that is NOT the case here.
Comment 1 fachat 2015-01-11 08:57:56 UTC
Additional note: the VIA EPIA-M board I'm trying to install it on has two network interfaces on the board, named enp0s15 and enp0s18. I down'd the one I did not need, but did not help either.

I also deleted the IPv6 addresses, but it did not help either.
Comment 2 fachat 2015-01-11 10:28:26 UTC
Ok, time for a brown paper bag. Looks like I copied it over as "resolve.conf" instead of "resolv.con". 
At least re-doing the whole installation with the 20140415 build it gets over this point now.