@s_raiguiel: What's the status of this problem with Ubuntu 12.04?
Unchanged?
** Summary changed:
- Possible issue with 64-bit 10.10 network drivers
+ NM often fails to configure wired interface -- Intel 82566DC e1000e
--
You received this bug notification because you are a member of Ubuntu
Bugs
Ok, on the off-chance that somebody, somewhere might actually be reading
these entries and following the thread, let me say that re-compiling and
installing the latest e1000e NIC driver from Intel fixes the problem
with kernel 2.6.35.23 just as it did with 2.6.35.22.
--
Possible issue with 64-bit
Regression! With the latest kernel update, 2.6.35.23, the network
doesn't connect at all. I had to boot 2.6.35.22 to even get online to
send this message. I suppose it's possible that by manually installing
the updated Intel driver with 2.6.35.22, I broke the update chain. I'll
try re-installing In
This will be my last comment on this thread, because the new Intel
driver has essentially solved the problem. At most, there's now a
failure-to-connect only 1 out of 4 or 5 boots, which is good enough for
me. Seems to me that it would behove the Ubuntu developers at this point
to either take anothe
I just downloaded and installed the latest e1000e NIC driver from Intel.
This seems to help though it's still not perfect. Whereas it was taking
up to half a dozen reboots before I could finally get a connection, of
the last three reboots, two have resulted in a network connection.
--
Possible is
The issue is still with us following full install! I went ahead and
installed Maverick onto the hard drive. Sometimes it gets an IP number
and connects, sometimes not, and there doesn't seem to be any particular
thing that I can do during bootup to insure that it does or doesn't
connect. Attached i
Whoops! Suddenly, the wired network seems to be connecting, though
nothing, as nearly as I can tell, has changed. Earlier, I had tried to
connect several times from the live CD, then I put system onto a USB
stick, so I could boot from that, again confirmed that the network still
remained disconnect
Yes, sorry the info was so sketchy. I didn't mention that the NIC in
question was an Intel 82566DC, which might have been pertinent, and it
certainly didn't occur to me that I could save the output of apport to a
file. I've attached the saved apport output here.
** Attachment added: "apport output
I'm sorry but there is just not enough information to properly triage
this bug -- without knowing exactly which drivers these are, there is
little that can be done.
In order to help us deal with this issue, could you try the live CD
again and use the 'apport-cli linux --save /tmp/drivers.apport' c
