After booting from CD in VirtualBox 4.1.2 it prints: * Network device eth0 detected, DHCP broadcasting for IP ... but no dhcpcd really started. It appear in install-amd64-minimal-20110915.iso too. Manually network starts without any problems: # ifconfig eth0 up && dhcpcd eth0 -b or via # net-setup eth0 Reproducible: Always Steps to Reproduce: 1. Create LiveCD. 2. Boot from it in VirtualBox. 3. Run ifconfig or ping ya.ru. Actual Results: Only loopback interface provided in ifconfig. Expected Results: Automatically configured eth0 interface.
What network driver? This is likely related to the driver detection / loading than to the network script.
e1000, in compiled into the kernel.
(In reply to comment #2) > e1000, in compiled into the kernel. I'm sorry, I meant what network driver is detected by the install CD on the VirtualBox guest.
(In reply to comment #3) > I'm sorry, I meant what network driver is detected by the install CD on the > VirtualBox guest. In VirtualBox selected adapter: Intel PRO/1000 MT Desktop (82540EM) In guest lspci -k says: 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter Kernel driver in use: e1000 /etc/init.d/autoconfig doesn't show any driver name, only "eth0".
Created attachment 286881 [details, diff] Patch for automatic network start in /etc/init.d/autoconfig Here is my attempt to fix this. May be ugly and misplaced, but works for me :)
Sorry, this is duplicate of old bug, but patch is still not in production :( *** This bug has been marked as a duplicate of bug 198083 ***
