This bug is still on Oneiric. I have used
http://archive.ubuntu.com/ubuntu/dists/oneiric/main/installer-i386/current/images/netboot/ubuntu-installer/i386/
linux kernel and initrd for instalation on IBM/Lenovo T60 (Type 2007-FSG),
uname -a: Linux (none) 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Triaged = Won't Fix
--
e1000 EEPROM Checksum
** Changed in: linux (Ubuntu)
Importance: High = Undecided
Assignee: Tim Gardner (timg-tpi) = (unassigned)
Status: Fix Committed = Invalid
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because
linux 2.6.24-21 copied to hardy-updates.
** Changed in: linux (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs,
I have experienced the same problem with ubuntu 8.04.1 (Hardy ) and
linux kernel 2.6.24.19 generic. In the dmesg I get the message bad
checksum. I have worked around it using the module parameter to allow
the bad checksum.
--
e1000 EEPROM Checksum validity check should be disabled
I have this problem with both 2.6.26-5 and with Alpha 5 Ubuntu 8.10
(2.5.27-3). Solving it with a work around at the moment on 2.6.26 by
using the terminal command ... sudo ifconfig eth0 hw ether
00:1c:25:1e:0f:e6 or by putting the command in the rc.local file.
I have not tried a work-around for
** Tags added: hw-specific
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
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.ubuntu.com
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
e1000 EEPROM Checksum validity check should be disabled
** Tags removed: verification-done
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
pushing the milestone back to 8.04.2 for the second part of this
reopened bug.
** Changed in: linux (Ubuntu Hardy)
Target: ubuntu-8.04.1 = ubuntu-8.04.2
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification
SRU Justification:
Impact: e1000 checksum test sometimes fails causing loss of network
connectivity
Patch Description: Check checksum validity before HW reset, reset and
try again on checksum failure.
Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
The thinkwiki link in comment 8 has a section which suggests that checking the
checksum a second time causes it to validate. Would this patch be acceptable to
us? Checking a broken checksum a second time doesn't immediately sound
insane/dangerous, but making a commonly used chipset work in more
I can confirm this fix. With 2.6.24-16-generic, the e1000 driver was
not working for me, and the eeprom_bad_csum_allow option was not
recognized. With 2.6.24-17-generic, the e1000 driver appears to work
better generally, and the eeprom_bad_csum_allow is also recognized.
** Tags added:
Accepted into hardy-proposed.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
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.ubuntu.com
** Tags added: verification-needed
** Changed in: linux (Ubuntu)
Assignee: Ben Collins (ben-collins) = Tim Gardner (timg-tpi)
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of
SRU Justification:
Impact: Users of the e1000 driver cannot override default behavior of a
bad eeprom checksum, e.g., the driver exits.
Fix Description: Implement a module parameter that allows the driver to
proceed with initialization when eeprom checksum fails. The user can
then set the MAC
** Changed in: linux (Ubuntu)
Target: ubuntu-8.04 = ubuntu-8.04.1
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ben, this bug is marked as 'fix committed' since April 10, but (using
the ethernet on my T60 for the first time in months) I'm still seeing
the same old checksum error and the eeprom_bad_csum_allow parameter
isn't recognized. Was this committed somewhere other than to the
'linux' package?
--
oh, that was a dumb comment, wasn't it, there have obviously been no
kernel uploads since April 10. :)
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I see this on Hardy every time I boot my computer. For me it is clearly not
connected to any suspend/resume issues.
I removed the check from the source and compiled it which works fine for me.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Re-added the eeprom_bad_csum_allow module parameter.
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Ben Collins
(ben-collins)
Status: New = Fix Committed
Target: None = ubuntu-8.04
--
e1000 EEPROM Checksum validity check should be disabled
I'm seeing this on Hardy, every now and then. I think it has something
to do with suspend and resume but haven't narrowed it down at all.
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.24
I am also seeing this on Hardy occasionally.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Are you also using suspend-and-resume?
** Attachment added: signature.asc
http://launchpadlibrarian.net/13178186/signature.asc
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of
Sorry. Yes, it does seem to be happening after a suspend and resume.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I am experiencing this on my Thinkpad X60s with Gutsy. I did not
experience this bug on Feisty or earlier releases.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which
The ibm script worked on this T60p on gutsy.
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I had the same problem, for just about any Ubuntu version I tried
(dapper, edgy, feisty) and a range of kernels (generic and custom). Also
I used to have the same problem in Gentoo aswell.
The ibm-script I'm referring to can be found at the above link or, more
exactly, here:
This bug also affects 2.6.22-8-generic on a Thinkpad T60.(8744-5bu)
It would be nice if this bug could be fixed in the kernel or detected and
resolved upon installation.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
e1000 EEPROM Checksum
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team
Status: New = Triaged
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Fix Committed = Fix Released
--
e1000 EEPROM Checksum validity check should be disabled
https://bugs.launchpad.net/bugs/60388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Is this command line parameter still in the code (i.e. = 2.6.20-12)?
I always get:
Unknown boot option `e1000.eeprom_bad_csum_allow=1': ignoring
e1000: :02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of :02:00.0 failed with error -5
Unfortunately, I can't test it
Are you using ubuntu? I had the issue with ubuntu but not with RHEL.
Debo
On 4/17/07, Johannes Schmidt [EMAIL PROTECTED]
wrote:
Is this command line parameter still in the code (i.e. = 2.6.20-12)?
I always get:
Unknown boot option `e1000.eeprom_bad_csum_allow=1': ignoring
e1000:
In 2.6.20-10, on the kernel command line:
e1000.eeprom_bad_csum_allow=1
should allow your card to work, can you please test it. Thanks!
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: In Progress = Fix Released
--
e1000 EEPROM Checksum validity check should be disabled
First off, sorry for not responding sooner.
I am currently using 2.6.20-9 and the e1000 driver works without the
commandline argument.
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Moving milestone forward
** Changed in: linux-source-2.6.20 (Ubuntu)
Target: herd-5 = beta
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Kyle McMartin
Status: Unconfirmed = In Progress
Target: None = herd-5
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
Sebastian, there have been no changes to the e1000 driver between -2 and
-5... Are you sure it worked? Were you just upgrading along the way? It
sounds like your EEPROM checksum was somehow corrupted.
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
2.6.20-9-generic still has this problem (Thinkpad X60s)
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
ubuntu-bugs mailing list
Kernel 2.6.20-2-generic works fine with e1000 on my ThinkPad X60s,
Kernel 2.6.20-5-generic does not.
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It seems that this patch has been applied to the 2.6.17 kernel of edgy,
but 2.6.19 and 2.6.20 (feisty) again refuse to work with the e1000
driver.
It works flawlessly when applying the patch to 2.6.19/20, i.e.
uncommenting the checksum check and recompiling the driver (as done with
the machine I
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) = Ben Collins
Status: Unconfirmed = Fix Committed
--
e1000 EEPROM Checksum validity check should be disabled
https://launchpad.net/bugs/60388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
43 matches
Mail list logo
