View previous topic :: View next topic |
Author |
Message |
slashlinux n00b
Joined: 26 Nov 2011 Posts: 62 Location: dan
|
Posted: Tue Apr 02, 2013 7:03 pm Post subject: problem with iface eth0 down |
|
|
Hello people.
I have one problem with installing gentoo on vmware player or vmware workstation 9.0.
I just finish to install my gentoo server, my kernel gentoo is compiled with genkernel wich is included and installed all modules on kernel...but my eth0 interface is not showing up..i have only this :
lo iface...etc etc etc..
What can i do, i put you a print screen from my lspci command..
Controller ethernet on vmware "Ethernet controller : Advanced Micro Devices [AMD] 79c970 [PCnet32 Lance] (rev 10)"
[IMG]http://imageshack.us/a/img689/6771/vmnet.png[/IMG] |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Apr 02, 2013 7:46 pm Post subject: |
|
|
If genkernel did not include pcnet32: Code: | genkernel --menuconfig all | edit menuconfig toinclude Quote: | Device Drivers --->
[*] Network device support --->
[*] Ethernet driver support --->
[*] AMD devices
< > AMD 8111 (new PCI LANCE) support
<M> AMD PCnet32 PCI support |
_________________ Defund the FCC. |
|
Back to top |
|
|
slashlinux n00b
Joined: 26 Nov 2011 Posts: 62 Location: dan
|
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Apr 02, 2013 11:27 pm Post subject: |
|
|
does eth0 appear?
does eth0 appear?
Code: | ls -l /etc/init.d/net* | does /etc/init.d/net.eth0 -> net.lo appear? does /etc/init.d/net.lo appear?
Code: | rc-update show | grep -i net | do net.lo | boot and net.eth0 | default appear?
Code: | /etc/init.d/net.eth0 restart | any action?
Code: | lsmod | grep-i pcnet32 | what appears?
in vmware with cd booted what does lspci -k report for module and driver in use for the nic? _________________ Defund the FCC. |
|
Back to top |
|
|
slashlinux n00b
Joined: 26 Nov 2011 Posts: 62 Location: dan
|
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Wed Apr 03, 2013 9:20 pm Post subject: |
|
|
don't fix it
just use it
Code: | cd /etc/init.d
rm net.eth0
ln -s net.lo net.enp2s1
rc-update del net.eth0
rc-update add net.enp2s1 |
edit /etc/conf.d/net to replace eth0 with enp2s1 anywhere it might appear.
when portage tells you there are news items you should read them.
Code: | eselect news read all | to catch up _________________ Defund the FCC. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21595
|
Posted: Wed Apr 03, 2013 10:30 pm Post subject: |
|
|
As described in the news, you can fix this and use the traditional naming by creating an empty /etc/udev/rules.d/80-net-name-slot.rules. |
|
Back to top |
|
|
SamuliSuominen Retired Dev
Joined: 30 Sep 2005 Posts: 2133 Location: Finland
|
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 698 Location: San Diego, CA
|
Posted: Thu Apr 04, 2013 12:12 am Post subject: |
|
|
"eth0" is the name I've been using for as long as I can remember. I'm sure the new scheme was added for very valid reasons and I usually prefer new things (Python 3.x instead of Python 2.x, for example), but I think it might take a while for me to adapt to the new way of naming network interfaces. I believe Gentoo Handbook (http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=8) still uses "eth0".
Of course, I don't have to use the new names if I don't want to. I'm torn in-between.
__
sol |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21595
|
Posted: Thu Apr 04, 2013 1:11 am Post subject: |
|
|
ssuominen: it was my understanding that we would be reintroducing the randomly assigned kernel names that people have always had.
OP: If you do not have at least two cards which register under the same namespace prefix (eth, wlan, etc.), then the traditional non-predictable names are fine. Predictable names only help you if you have multiple cards which all register with the same prefix, in which case some kernel drivers may, under some circumstances, not number them the same on every startup. I have yet to figure out why the feature defaults to enabled when most users lack the hardware complexity to benefit from it. |
|
Back to top |
|
|
EvadingGrid n00b
Joined: 04 Apr 2013 Posts: 13
|
Posted: Sun Apr 07, 2013 10:55 am Post subject: |
|
|
This really is a problem with the upstream
The consequences are horrendous.
For example, if a newbie follows the Gentoo Handbook the result will be a computer with NO Internet
They are not going to be able to Google the answer, because they have NO Internet
Now I know some people will be aware of the changes to udev, and will know to do a quick
ifconfig -a
Its just not fair to expect newbies to be psychic. |
|
Back to top |
|
|
Killerchronic Tux's lil' helper
Joined: 24 Apr 2007 Posts: 91 Location: UK
|
Posted: Sun May 05, 2013 6:29 pm Post subject: |
|
|
Just spent well over an hour sorting this, not sure yet when it came in but this caused numerous problems on a vmware install i had started some weeks back and never finished. Because i had no net i was not trying to emerge anything and wasn't seeing anything in regards to news, this also hasn't become an issue on my server or laptop and i do often go through a month or 2 without reading the news of updates unless something breaks. Last part is my own fault in a way but rather large change considering i can imagine most don't have more than 1 nic and never experience the issue or eth0 moving to eth1 on reboot. Infact even on a system where i have 2 nic's its never happened.
Least the fix was simple enough:
Code: | You disable the assignment of fixed names, so that the unpredictable kernel names are used again. For this, simply mask udev's rule file for the default policy: ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules |
Must remember to do this on my headless server before it next reboots.
Regarding the ifconfig -a part, i've never used that switch before either, i will check if an interface is there with ifconfig, if not i start looking for module issues etc. |
|
Back to top |
|
|
|