To: Graham, David
Subject: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and
ICH9 gigE chipsets at risk
Burned the iso, followed your instructions, but:
eth0 EEprom len 4096
checksum ed0e wrong should be 830e
So I can't send you my ethtool.dmp
My
] 2.6.27 e1000e driver places Intel ICH8
and ICH9 gigE chipsets at risk
lspci -tv:
+-19.0 Intel Corporation 82566DC Gigabit Network Connection
lspci -xxx:
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 03)
00: 86 80 4b 10 03 01 10 00 03 00 00 02 00 00
I have downloaded LiveCD for AMD 64 and for x86 64 yesterday and when
I tried AMD 64 version as a LiveSession I was not able to use network
on a computer that I use now to write this message :)) (now I an
writing in Hardy) so it is not yet released AFAIAC.
On 10/17/08, Chris Jones [EMAIL
I am very sorry that I have missused this place. I hope that You will
be able to forgive and forget. I am just an old guy ... ;)
I will wait for official release.
Thank You very much.
Once again sorry for the noise.
On 10/17/08, hefeweiz3n [EMAIL PROTECTED] wrote:
For your Information:
For those who got this working on the 2.6.27-5.4 kernel. Does the newer
2.6.27-5.5 kernel that is in the repositories now also work for you?
On Mon, Oct 6, 2008 at 7:10 AM, mrbean71 [EMAIL PROTECTED] wrote:
I don't know if open a new bug. I think e1000e have some problem here
result of furter
Hi,
I confirm that it works for me. I just update the kernel to 2.6.27-5. In a
first moment it seemed to do nothing, but I just did:
sudo ifconfig eth0 down
sudo ifconfig eth0 up
And that was all, my network started to be ok.
Bye,
Juan David Cuevas Guarnizo
Investigador - Grupo GASURE
Tel:
The fix was not in 20081004 but it should be in 20081005 and is
definitely in 20081006. Therefore any of the ISO would have the correct
kernel.
No, 20081007 will be the first daily image that includes this module
again.
--
Steve Langasek Give me a lever long enough and a
2.6.27-5 fixed my problems, just to confirm that this works for some
people.
On Sun, Oct 5, 2008 at 4:09 PM, mrbean71 [EMAIL PROTECTED] wrote:
Hi all, my NIC won't work with any 2.6.27 kernel, now i'm writing from:
Linux marcoPC 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686
once you have the kernel running do modprobe e1000e
On Saturday 04 October 2008 4:07:43 pm Simon Sigre wrote:
Since the Kernel upgrade i still appear to be having some troubles with
the network card; im using an X200 laptop that ships with a 82566DC-2
network card;
[EMAIL PROTECTED]:~$
Please ask in the forum not here
On Fri, Oct 3, 2008 at 9:29 AM, Daniel Kutik [EMAIL PROTECTED] wrote:
How could I install this fix manually (not over the internet).
At the time I've got no other connection as a wired. Is there a possibility
to update the system via usb stick?
--
Will You update/rebuild beta cd/dvd images once fix is released?
No. The fix will be included in the subsequent daily images, in the release
candidate image, and in the final release.
It should be at least mentioned as warning in release anouncement.
It was.
--
[intrepid] 2.6.27 e1000e
You could also probably just put the kernel packages on a flash drive, and
install them manually.
On Fri, Oct 3, 2008 at 2:32 PM, Steve Langasek [EMAIL PROTECTED]
wrote:
Will You update/rebuild beta cd/dvd images once fix is released?
No. The fix will be included in the subsequent daily
On Wed, Oct 1, 2008 at 7:46 PM, vjohn [EMAIL PROTECTED] wrote:
So, the Intel haven't opened the code of your hardware? So, how it's
happen?
It's happen because it isn't a stable kernel release, and because linux is
developed by humans, and they might make mistakes. And I think the linux
And because, after they learned about the problem, they failed to
communicate effectively and never removed the cd-image.
This has never happened before, and obviously there was no policy for this
situation. Which automatically means that some developpers turn into 'its
your fault'-mode and be
Hi,
Quoting vjohn [EMAIL PROTECTED]:
Hi people, sorry by angry message, but I'm realy needing my onboard
network working in gnu/linux... Yesterday I have installed m$
windows in my machine to test the onboard network card (for
something it's work! hehe)
You definatly should *NOT*
What make's an alpha or beta tester's hardware less valuable than the
hardware the final release is installed on? In many cases it is the same
hardware.
While I agree many install alpha or beta releases when they shouldn't, a
large number of people are actually working to do testing, and their
So can we expect an Ubuntu Alpha 7 with this Intel provide eeprom
protection patch and the removal of the e1000 blacklisting? This will
allow me to continue testing Intrepid on a machine with e1000 (and it
needs at least Alpha 6 anyway because it has GMA 45000 graphics). Or
is the hope that beta
On Thu, Oct 02, 2008 at 10:53:21AM -, Vincenzo Ciancia wrote:
Indeed the alpha release should have been replaced in a hurry by a new
release with the module blacklisted. What I see from outside is that
the burocratic need to release images only at established dates is
preventing a well
@JavaJake
What more can they do?
Well, they could:
a) Pull the images immediately, instead of entering a discussion just
how import the hardware of those who volunteer to test really is.
b) Put the warning on planet-ubuntu, instead of entering a discussion
just how import the hardware of those
Hew McLachlan wrote:
Ravindran, it looks like you are affected. Here's a list of affected
devices taken from
http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/302000834931?r=202000364931#202000364931
That looks kinda like it's just a list of PCI IDs claimed by the driver.
AFAIK
On Wed, Sep 24, 2008 at 11:18 AM, Pelládi Gábor
[EMAIL PROTECTED]wrote:
Can this bug destroy hardware even if Intrepid alpha 6 is run as a guest
on a stable Hardy? That is, does a virtual machine protect my hardware
from this bug?
No, it cannot. It may or may not be capable of damaging the
On Wed, 24 Sep 2008, Leonardo Silva Amaral wrote:
Ive created a VERY stupid script to find if the system have a NIC
vulnerable to the faillure (Used the list from
http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/302000834931?r=202000364931#202000364931)
Here is:
Em Wednesday 24 September 2008 13:18:53 Jesse Brandeburg escreveu:
On Wed, 24 Sep 2008, Leonardo Silva Amaral wrote:
Ive created a VERY stupid script to find if the system have a NIC
vulnerable to the faillure (Used the list from
I'm sorry to say that but I think this will be the last time I'll run
Ubuntu Alpha on my machine. I'm willing to help, but I have to be 100%
sure that Ubuntu developers have very CLEAR policy on what will be
pushed in the repositories for testing.
Such a policy can do nothing to address bugs
Em Wednesday 24 September 2008 14:27:31 Peter Frühberger escreveu:
Please fix your script, you are printing awk $1, this is not what you
want to compare, use $3. Please do not post scripts, which the user
thinks he is secure.
I am affected - and your script said not.
Peter
PS: I wrote
Em Wednesday 24 September 2008 20:36:41 Brian Murray escreveu:
** Attachment removed: DETECT_INTEL_E1000E_BUGGY.sh
http://launchpadlibrarian.net/17925250/DETECT_INTEL_E1000E_BUGGY.sh
Thanks
--
Leonardo Amaral - Administrador de Sistemas Linux
Tel: 31 8432-5025 / 31 4062-7411
Cerificado
For those that might be interested in testing the Alpha, but has an at risk
machine, is there an accepted workaround that removes the e1000e driver
without jeopardizing the hardware?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The only place where I can find official download links to the
BitTorrent is at http://cdimage.ubuntu.com/releases/intrepid/alpha-6/,
where the warning exists.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received
28 matches
Mail list logo
