[Bug 46822] Network interface ureliable in Dapper release-candidate
Christian Convey
christian.convey at gmail.com
Fri May 26 20:22:31 UTC 2006
Public bug reported:
I'm using the Dapper release-candidate that was announced 26 May 2006.
Here's the history...
I use DHCP normally. According to lspci I have a "Davicom
Semiconductor, 21x4x DEC-Tuplic compatible 10/100 Ethernet (rev 31)"
It's in a Penium IV box.
For many months I ran Breezy with no network problem at all. I
installed the Dapper release-candidate, and the update went smoothly.
However, starting with my first reboot into Dapper, the network
interface didn't work. When I try to bring it up, it eventually times
out trying to get a DHCP lease. Sometimes the DHCP process gets far
enough to give me an IP#, but even in those cases I don't seem to have
routes to any hosts that I've tried pinging - not even our DNS servers.
I tried a static (that is, non-DHCP) configuration, and it didn't help.
In order to fix the problem, I decided to reinstall Breezy from scratch,
and then right away upgrade from that clean Breezy install to the Dapper
release-candidate. I followed this plan. Networking worked just fine
in Breeezy, but once I was in Dapper I had these same problems all over
again.
** Affects: linux-source-2.6.15 (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
--
Network interface ureliable in Dapper release-candidate
https://launchpad.net/bugs/46822
More information about the kernel-bugs
mailing list