edgy AMD64 dhcp busted

PS. I don't actually know what/where is causing the problem; the choice of reporting against dhcp-client is arbitrary. Eth0 is plainly visible using ifconfig - it just can't get an IP address assigned.

And here's an example of DHCP working fine on i386 from the live CD. Both cases are for Edgy.

$ sudo ifup -v eth0
Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:13:d4:b6:73:7f
Sending on LPF/eth0/00:13:d4:b6:73:7f
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 64.142.67.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 64.142.67.1
bound to 64.142.67.205 -- renewal in 10409 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...

$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:D4:B6:73:7F
          inet addr:64.142.67.205 Bcast:64.142.67.255 Mask:255.255.255.0
          inet6 addr: fe80::213:d4ff:feb6:737f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1560 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1259 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1576642 (1.5 MiB) TX bytes:240851 (235.2 KiB)
          Interrupt:169 Base address:0xc000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:200 (200.0 b) TX bytes:200 (200.0 b)

Can you configure the card manually, i. e. does it work at all on your system? If not, this rather looks like a kernel problem.

Can you attach /var/log/kern.log here?

I have long since dumped x86-64 and installed i386 edgy because
of this problem. If you really care, I can run from a live CD and report.
You want me to use edgy? Some feisty beta? Not bother?
No, I can't configure NIC card manually but also wouldn't know where
to start. No kernel module parameters are required as far as I know.

-Jeff

On 2/15/07, Martin Pitt <email address hidden> wrote:
> Can you configure the card manually, i. e. does it work at all on your
> system? If not, this rather looks like a kernel problem.
>
> Can you attach /var/log/kern.log here?
>
> ** Changed in: dhcp3 (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> edgy AMD64 dhcp busted
> https://launchpad.net/bugs/69175
>

Hi Jeff,

Jeff Breidenbach [2007-02-15 9:30 -0000]:
> I have long since dumped x86-64 and installed i386 edgy because
> of this problem. If you really care, I can run from a live CD and report.
> You want me to use edgy? Some feisty beta? Not bother?

The current Feisty daily CD would indeed be nice to test.

Works fine on the current Feisty daily CD. Good. You can close the bug.

-Jeff

On 2/15/07, Martin Pitt <email address hidden> wrote:
> Hi Jeff,
>
> Jeff Breidenbach [2007-02-15 9:30 -0000]:
> > I have long since dumped x86-64 and installed i386 edgy because
> > of this problem. If you really care, I can run from a live CD and report.
> > You want me to use edgy? Some feisty beta? Not bother?
>
> The current Feisty daily CD would indeed be nice to test.
>
> --
> edgy AMD64 dhcp busted
> https://launchpad.net/bugs/69175
>

Thanks a lot for testing!