** Changed in: dhcp3 (Ubuntu)
Status: Confirmed => Fix Released
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This was no longer an issue when I upgraded to Edgy, and also works in
Feisty.
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this same problem: I must usually do a manual "sudo dhclient" to
get an IP address after boot, on Ubuntu Dapper, though it seems to be
intermittent. This is annoying because I have to attach a monitor and
keyboard to my server to do this.
Bug #34505 seems similar.
Bug #19740 (rejected) also
Confirmed on my new install of dapper fo an ASUS M2NPV-VM mainboard.
After boot, the ethernet port doesn't work. I noticed this on my
initial install, then dropped in an old 3com card which works fine. Now
I should have two ethernet ports but *three* are reported! The built-in
port (using forced
Sorry peeps, false alarm. For the first 3 or 4 reboots after changing
kernel dhcp worked ok, tried again last night and it failed again. Must
just have been a coincidence.
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I've always run the k7 kernel so I don't know if that'll help you, but
good luck anyway.
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just installed the linux-k7 kernel package last night and the problem
seemed to go away, I'll do some more testing and confirm shortly.
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I can confirm this defect.
I have a
:00:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev
01)
:00:09.0 0200: 14e4:4401 (rev 01)
Subsystem: ASUSTeK Computer Inc. A7V8X motherboard
Subsystem: 1043:80a8
I am not sure if it is the problem of dhclient3 because sometimes a
I'm fairly sure it's DHCP as I can also do a 'dhclient eth0' to get it
to work.
--
Ethernet interface not working after reboot
https://launchpad.net/bugs/42608
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Setting a static IP address (IP=computer's assigned IP address, and
Gateway=Router's IP address) in Network Settings fixes it for me, but
DHCP should work. Perhaps it is an issue with DHCP, as somebody
mentions that above too?
--
Ethernet interface not working after reboot
https://launchpad.net/
My motherboard is an Asus A8N-VM CSM, NVIDIA nForce 430 chipset.
Symptoms are very similar but show randomly. First live CD boot went
well. Once installed, I get random behaviour (sometimes works, sometimes
doesn't). My network fails both at startup and after some time of using
Firefox to surf the
11 matches
Mail list logo
