Chuck Short, as you no longer have the hardware this report is being closed.
For all others, if you are having a problem in Ubuntu, please file a new report
by executing the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux
Thanks!
** Tags added: needs-upstream-te
I've just upgraded to Natty. The bug is still there. Here is output from
gmesg:
$ dmesg | grep e1000e
[2.171983] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2
[2.171986] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[2.172022] e1000e :00:19.0: PCI INT A -> GSI 20 (leve
I installed the last kernel for Lucid (Linux 2.6.35-28-generic
#50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64). The bug is still
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
So where is this newly opened bug? I am also suffering from this issue
and would help to fix it. My laptop is a Dell Latitude E6510, currently
running Ubuntu 10.04 64 bit version. Unfortunately there is no progress
in the kernel bugtracker for this issue
(https://bugzilla.kernel.org/show_bug.cgi?id
@Jim,
First, you should open a new bug. That way we'll be able to track your
specific issue and get information about your specific setup.
Brad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
T
Brad, I am running Maverick, but I realized it's not the same bug. I
get an IP address, but my problem is that the connection keeps
disappearing at random but frequent intervals. I would be willing to
test a new kernel. Can I just add an appropriate apt-source to install
an alpha kernel with syn
Jim,
Which series are you running? Maverick or Lucid? Are you willing to try
test kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt work on 2.6.35.
--
I am suffering from this bug as well. It should be marked as important
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt work on 2.6.35.
--
ubuntu-bugs mailin
Marking this incomplete until someone steps up to testing.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSI
I dont have the hardware anymore so Im not able to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt work on 2.6.35.
--
ubuntu-bugs mailing list
ubuntu-b
After reviewing the code for the current Lucid and Maverick kernels,
this looks like it should still be an issue for both. Anyone want to
step up to being a tester for patched kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Does this issue still exist? I'm reading back and comment #3 indicates a
patch in 2.6.36 that should be in Natty. Can someone test a fix for
Lucid? Maverick? Natty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Tags added: maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt work on 2.6.35.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
It still exists for me too. Upgrading to 11.04 alpha fixed it (and made
life more exiting).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt work on 2.6.35.
--
Agree; if nics weren't 5 bucks a piece I'd have moved away from Ubuntu
thanks to this bug and the fact it's still open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000
It's a joke that this bug still hasn't been fixed. The cause is known.
Just revert it and push a new update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619841
Title:
[REGRESSION] e1000e doesnt wo
I experienced this bug as well and reported it about the same time (see
#616984, now marked duplicate). I tried Natty Alpha 1 with a 2.6.37
kernel and my network works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Tags removed: needs-kernel-logs
** Tags added: regression-release
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Sorry no, looks like I spoke too soon, it did not help, I must have
missed something.
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I have managed to extract Fedora 14's patch for e1000e kernel module and
apply it on my system and so far so good, it seems to work ok.
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs,
I have tested using linux-image-2.6.36-020636-generic and can confirm that the
network cards works, reverting back to 2.6.35 and the network may work for one
reboot but not a cold boot (as the registers have been set by the 2.6.36 kernel)
This could be used as a work around however I have another
Affects my box as well, Intel DG965OT mainboard.
Between about 20 reboot cycles (warm and cold), I managed to get a connection
exactly once. I played with network settings, fixed IP addresses, but wasn't
able to get the nic to transfer any data at all.
Had to revert to Karmic because this is my
Hi,
I have a box that is affected by this problem, is there anyway I can
help (testing/provide support info)?
R
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Changed to confirmed now that the new information needed is attached.
Also, the lastest kernel was tested by Albert Bicchi, as requested.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You
Thanks Fabian, Here's the output of apport-cli -f -p linux --save
bug.apport
** Attachment added: "apport-cli -f -p linux --save bug.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/619841/+attachment/1729538/+files/bug.apport
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https:/
Hi mon,
I have now fixed the documentation here:
https://help.ubuntu.com/community/ReportingBugs#Filing%20bugs%20when%20off-line
I tested the instructions there and they should let you submit an
offline report.
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
mon, there's a way to collect apport information on that system, then
take it to an online system and submit it.
Let me try it first and I'll come back here, it seems the current
documentation regarding this is lacking.
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bug
Also, I tried to launch:
apport-collect -p linux 619841
when the bug happened, but since the computer has no network the command
failed. Are we supposed to run that command when the issue is NOT
happening?
thanks,
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619
This problem still ocurrs on 2.6.35-23-generic (x86_64).
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Just a comment: this problem very rarely if using kernel from
ppa:tuxonice/ppa (linux-image-generic-tuxonice).
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This problem occurred for me in ubuntu-10.10-rc-desktop-amd64.iso but is
no longer a problem in ubuntu-10.10-desktop-amd64.iso
I hope that means it was actually fixed, rather than randomly
disappearing.
--
[REGRESSION] e1000e doesnt work on 2.6.35.
https://bugs.launchpad.net/bugs/619841
You rece
Hi,
I still have this problem with todays updates.
Non-working ethernet after an upgrade, is that not a showstopper?
Shouldn't there at least be a warning in the release notes??
https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview
Best
Anders
--
[REGRESSION] e1000e doesnt work on 2.6.35
I have compiled and installed 2.6.36-rc6 which contains the fix i
mentioned above.
I confirm that this commit fixes the problem for me:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5f3eed6fe0e36e4b56c8dd9160241a868ee0de2a
By the way, these might be duplicates of th
I am also getting hit by this bug after upgrading to Maverick's RC:
lspci:
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)
Currently DHCP fails to get an IP and this NIC worked under lucid. I
have a feeling this is a show stopper as this NIC/modu
Hi Chuck,
Please be sure to confirm this issue exists with the latest development release
of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run
the following command from a Terminal (Applications->Accessories->Terminal).
It w
35 matches
Mail list logo
