Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 141306 - RTx86: Livecd says that DHCP is broadcasting for IP but does not do so
Summary: RTx86: Livecd says that DHCP is broadcasting for IP but does not do so
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: LiveCD/DVD/USB (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-21 09:52 UTC by Andrey Falko
Modified: 2006-08-23 09:41 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 Andrey Falko 2006-07-21 09:52:20 UTC
Using livecd: 
91a1b475d4c0d4e843990509c629c43d  install-x86-minimal-2006.1.iso

Modules load properly, ifconfig shows eth0 (this is the nvidia gigabit controller used with the reversed engineered driver) to be there, but without an IP. Ping sites also does not work.
Running /etc/init.d/net.eth0 start (or restart sometimes) gets networking running.

Here is the tail end of dmesg: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.54.
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:0a.0 to 64
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0
eth0: no link during initialization.
eth0: link up.
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
fbsplash: console 0 using theme 'livecd-2006.0'
fbsplash: switched splash state to 'on' on console 0

But here is the intersting stuff. The tail end of /var/log/messages (this is before I manually restart the devices:

Jul 21 12:36:45 livecd forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.54.
Jul 21 12:36:45 livecd ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
Jul 21 12:36:45 livecd ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 16
Jul 21 12:36:45 livecd PCI: Setting latency timer of device 0000:00:0a.0 to 64
Jul 21 12:36:45 livecd forcedeth: using HIGHDMA
Jul 21 12:36:45 livecd eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0
Jul 21 12:36:46 livecd eth0: no link during initialization.
Jul 21 12:36:46 livecd rc-scripts: Configuration not set for eth0 - assuming DHCP
Jul 21 12:36:46 livecd dhcpcd[10798]: MAC address = 00:11:d8:4a:05:f3
Jul 21 12:36:47 livecd eth0: link up.
Jul 21 12:36:49 livecd Floppy drive(s): fd0 is 1.44M
Jul 21 12:36:49 livecd FDC 0 is a post-1991 82077
Jul 21 12:36:50 livecd dhcpcd[11599]: MAC address = 00:11:d8:4a:05:f3
Jul 21 12:36:51 livecd fbsplash: console 0 using theme 'livecd-2006.0'
Jul 21 12:36:51 livecd fbsplash: switched splash state to 'on' on console 0
Jul 21 12:36:53 livecd dhcpcd[10798]: verified 192.168.1.105 address is not in use
Jul 21 12:36:53 livecd dhcpcd[10798]: your IP address = 192.168.1.105
Jul 21 12:36:53 livecd dhcpcd[11599]: terminating on signal 1
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2006-07-21 09:56:23 UTC
What version of dhcpcd is on this CD?

dhcpcd --version

Thanks...
Comment 2 Andrey Falko 2006-07-21 10:27:33 UTC
The version is v.2.0.8
Comment 3 Andrew Gaffney (RETIRED) gentoo-dev 2006-07-22 18:36:07 UTC
This works fine for me and another person, although we're not using forcedeth. However, my main workstation uses forcedeth and dhcpcd works fine with it.
Comment 4 Andrey Falko 2006-07-23 18:02:49 UTC
Hmmm...It appears just that machine...my laptop works just fine.
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2006-08-23 09:41:55 UTC
It is possible that the particular device isn't sending a proper netplug event to the kernel to let it know that it has link state.  The current CD wont' run DHCP on any interface that it doesn't think is "up" when booting.

Please REOPEN this (without the RTx86... :P) after 2006.1 is released if this is still a problem.  We've made a few minor updates here and there along the way that could resolve this for you.