Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. If you are unable to change the version, please add a comment here and someone will do it for you. So, I have a solution, but it doesn’t solve the problem regarding the NIC itself Attempts to force gigibit via ethtool were unsuccessful. On Fri, at
|Date Added:||16 October 2004|
|File Size:||19.36 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version.
Thanks, Timo – 0d: Approximately 30 thirty days from now Fedora will stop maintaining and issuing updates for Fedora I’m amused about PeeCee hardware sorry, only half of a pun intended Intel does not plan to resolve this erratum in the Gigabit Ethernet Controller.
The process we are following is described here: Login [x] Tehernet in using an account from: I know, even CPUs may have hundreds of errata, but shipping and selling crappy NIC chipsets is something that collides with my universe. Note You need to log ehternet before you can comment on or make changes to this bug.
Aug 20, at 3: Intel MM using ee will not connect at gigabit speed. Timo Schoeler Doesn’t work either. Has anybody an idea what goes wrong here?
Boot to Fedora 3. Description Brianna Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. Fedora 13 is no longer maintained, which means that it will not gigbit any further security or bug fix updates.
eth0 — router-kasarna
Timo Schoeler I tried with Intel’s most recent driver, it shows the same behaviour: Although we aim to fix as many bugs as possible during every release’s lifetime, sometimes those efforts are overtaken by events. Timo Schoeler Interestingly, I somewhere got the same PDF from the intel site that required a password — and didn’t investigate further on your link. One of them has a workaround available for its brokenness. Comment 3 Bug Zapper JohnS I read that also.
Downloads for Intel® E Gigabit Ethernet Controller
corpotation Since you can’t set the mtu you may benefit from setting the tcp values in sysctl. Actually, both of them are broken.
The chipset you’ve got has a bug, and jumbo frame support is disabled as a result. Now, out of curiosity, I did Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. It is Fedora’s policy to close all bug reports from releases that are no longer maintained.
If you would still ethrrnet to see this bug fixed and are able to reproduce it against a later version of Fedora please change the ‘version’ of this bug to the applicable version. Browse Requests Reports Product Dashboard. If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the ‘version’ to a later Fedora version prior to Fedora 13’s end of life.