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
This seems to give some hope, even on de-bricking hardware...
http://lkml.org/lkml/2008/10/1/368
Is it?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubunt
The current "fix" is to disable the driver to prevent damage to your
hardware.
Various developers are still working on finding the actual cause of the
problem, please be patient. You are recommended to use the latest stable
LTS (8.04) for anything mission-critical.
--
[intrepid] 2.6.27 e1000e dr
when will we get a kernel with this fix ?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I do a bios update from Intel, but can't activate the ethernet yet.
On load module (e1000e), show this message: "The NVM Checksum Is Not Valid"
Any help?
Thanks
Vinicius
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You
I have a desktop too, MBoard Intel DP35DP with:
00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network
Connection (rev 02)
After installing Intrepid 8.10, the version without the blacklisted drivers, I
saw no network. The device was unlisted.
On the same machine I have Ubuntu
Hi! I have a DESKTOP with motherboard Intel DG965WH with a onboard
ethernet card 82566DC: 00:19.0 Ethernet controller: Intel Corporation
82566DC Gigabit Network Connection (rev 02)
I have installed, unfortunately, the ubuntu kernel 2.6.27-3-generic in
my Debian Etch and the onboard network stop wo
FWIW, I apologise to all and retract my inane statement earlier in the thread
at:
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/11
I'll plead a very bad month.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad
@Rich:
No, it wasn't disabled the 17th (afaik). It was disabled in 2.6.27-4.6 which
was published 2008-09-24:
https://launchpad.net/ubuntu/intrepid/+source/linux/2.6.27-4.6
True, it's not a very consistent problem. My guess is that some BIOS routine in
some(!) ThinkPads (and maybe others) is auto
Same thing happened to me on an Intel D975XBX with a Gigabyte Ethernet.
Fortunately just disabled it. I'll wait untill December. See what
happens. In the meantime I have Sabayon there.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/b
@gertvdijk: I'm curious to see what works out in terms of what's going
on, but from what I've read, it looks like A) it's not a consistent
problem with easy reproducibility, and B) isn't Sept 17th after the
blacklist of the affected driver went in?
In any event, I'm glad there's a story for resolv
** Changed in: linux (Ubuntu Intrepid)
Target: None => ubuntu-8.10
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
ThyMythos: I don't think that post proves "it is definitely a X server
problem" - it's a strong suspicion among the people investigating this,
but as yet there is no solid evidence of what is causing it and allowing
it to happen.
Removing the e1000e module will mean that the EEPROM is not mapped i
For more information also have a look at:
http://article.gmane.org/gmane.linux.kernel/738578
According to http://article.gmane.org/gmane.linux.kernel/738618 it is definitly
a X server problem.
Are we really sure, deactivating the e1000e removes the problem?
--
[intrepid] 2.6.27 e1000e driver pl
Removing beta milestone since the workaround is sufficient for beta
** Changed in: linux (Ubuntu Intrepid)
Target: ubuntu-8.10-beta => None
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug noti
An update on the current status of this bug:
This issue has never affected a released version of Ubuntu, only an
alpha milestone of Ubuntu 8.10 (Intrepid).
The problem was worked around in kernel version 2.6.27-4.6 in Intrepid
by temporarily disabling the e1000e driver (the e1000 driver is still
UBUNTU: SAUCE: e1000e: Map NV RAM dynamically only when needed.
I'm going to go with this until upstream converges on a solution that
I'm happy with. One point of contention with upstream is that Ubuntu is
using the e1000e driver from Intel's SourceForge project, when we ought
to be using the in-k
T61 users saw "Starting up..." message shown for long time (just after pressing
enter at grub menu) ?
May be thats when EEPROM was getting into RESET state ?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received th
@Rich: I have the same laptop, with the same card and I've run the
september 17th daily build of the Intrepid live CD at the time (not
knowing this bug was present), but my ethernet card is still working. I
see more reports (see related bug trackers on top of page) of T61p users
which are not affec
** Changed in: linux (Fedora)
Status: Fix Committed => Confirmed
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hey world,
Are we still having trouble finding a machine to reproduce this bug on? I have
a T61p with an 82566MM (8086:1049 (rev 03)) that I'd be willing to volunteer
for testing purposes, if someone wants it. :)
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at ris
If your card cannot be detected as of 2.6.27-4.6, please stop commenting
as it is creating unnecessary bug mail. Since the e1000e was at risk of
being damaged, it has been intentionally disabled to prevent hardware
damage while a fix is developed. Please comment only if you have new
information to
I have a Acer AM5620-E1204A (Quad core desktop) which got the Intel
e1000e card (Intel Corportation 82566DC-2 Gigabit Network Connection
(rev 02))
I had no problem running the supported kernels 2.6.27-2 or 2.6.27-3 but
today I upgraded to the latest 2.6.27-4, and with this version my
network canno
** Description changed:
In some circumstances it appears possible for the 2.6.27-rc kernels to
corrupt the NVRAM used by some Intel network parts to store data such as MAC
addresses.
This is limited to the new e1000e driver, and reports have only appeared from
users of "82566 and 82567 base
I also have a thinkpad T61p which it hit by the same bug, but booting
other operating systems (and older linux kernels) makes the wired
ethernet work just fine. So it doesn't seem permanently corrupted like
many bugreports suggests.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gi
In case this helps: I've been using Intrepid for about a month now and
my wired NIC is fine; I tested it by booting into Windows. It only
stopped working this week when I got the module blacklist. The machine
is a Thinkpad T61p with NVidia graphics. Before the blacklisting I used
the wired netwo
For those who are stuck with a box without eth0 the rt kernel appears to
be a good temporary work around.
~$ dpkg -l | grep 2.6.26
ii linux-headers-2.6.26-1-rt 2.6.26-1.15
Linux kernel headers for version 2.6.26 on Ingo Molnar'
ii linux-headers-rt
I used alpha 6 with this Kernel (64bit version) on a ThinkPad R61. I installed
Ubuntu intrepid on its release date and used it until today. In that period of
time I used the (wired) ethernet device two times (checking mails and surfing
-> not much traffic). When I read this bugreport I immediate
Shwan, Good idea. However, I cannot find 2.6.26-5 on archive.ubuntu.com.
Does anyone have a link to the source, image, headers, restricted
modules for this kernel?
(Hardy's 2.6.24 kernel works somewhat but is not an ideal temporary
solution.)
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8
For you who have not functioning network card now, try start with
another kernel (older) min works booting by older one ( I have a lenovo
X61 tablet, and for you, who have a wiped eeprom , I guess it is
possible to get a EEPROM-dump from another computer with same lan card
and edit its MAC adress a
Are there any CD images which have the black listing in place? It can
take a few days before a kernel propagates to the cd
the latest daily live seems to be 20080923. i guess this is still
venerable.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs
> Would it make sense to write some
> random junk in the EEPROM to see if the issue appears again? I don't
> need a network adapter at the moment.
Bad idea. Don't try this. Now my ethernet controller isn't even listed
in lspci anymore and the driver won't see it. Damn!
--
[intrepid] 2.6.27 e1
Anil, the "fix" Fedora released was nothing more than disabling the
e1000e driver.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I have an 82566DC-2 and I had no idea why eth0 disappeared until I found this
bug report.
Please include some sort of warning if this does not get fixed soon.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received t
what else is more important than fixing some bug like this ?
Fedora seems to have already done it.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs,
Craig: most of us never use windows but have been constrained to pay for
it, so if it's able to restore a dead hardware device, at least I paid
for something! :) It's better than never use the ethernet card anymore
isn't it? It is better to know in this page that the hardware damage is
reversible,
I just checked my syslog and interestingly, the first time I got the
"e1000e: probe of :00:19.0 failed with error -5" error was during
wake-up from standby. The syslog doesn't indicate an X server crash (or
restart) between booting the computer and suspending it. I'm not sure
how useful this
@Craig
Sorry, if you think this...
I just wanna say that your network card is not permanently inoperable.
however, there is no need to be rude.
thanks
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bu
@NekoNemo
Thank you very much for the utterly nonproductive, and frankly insulting to the
people who actually work on and care about Ubuntu/Linux, comment you supplied.
Congratulations on using an *alpha* copy of Ubuntu, having a problem, then
switching to Windows. Once again, congratulations on
"Due to an unresolved bug in the Linux kernel included in Alpha 6, it
should not be used on Intel ethernet hardware handled by the e1000e
driver (Intel GigE). Doing so may render your network hardware
permanently inoperable."
yeah, but i have resolved on my hp 8510w with an old image of windows,
a
** Changed in: linux (Suse)
Status: In Progress => Incomplete
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@Jesse - Regardless of the reasons unrelated crashes are presumed to be
corrupting flash, why not modify the driver so that NV RAM is only
mapped while ethtool is actually using the interface? Even if the root
cause is found this time, it seems like something that could happen
again.
--
[intrepid
** Changed in: linux (Gentoo Linux)
Status: Unknown => Confirmed
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Bug watch added: Gentoo Bugzilla #238489
http://bugs.gentoo.org/show_bug.cgi?id=238489
** Also affects: linux (Gentoo Linux) via
http://bugs.gentoo.org/show_bug.cgi?id=238489
Importance: Unknown
Status: Unknown
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE
I am using a 2.6.26 kernel in hardy which loads the e1000e module on a
Thinkpad X300. I have not seen any problems but as a precaution have
blacklisted the module by hand by adding the line
blacklist e1000e
to the end of the file
/etc/modprobe.d/blacklist
This prevents the module loading when
This might be a red herring, however over at
http://lkml.org/lkml/2008/9/24/133 is a report of the same symptoms on a
RealTek ethernet system.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notificat
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
Cerificad
** Attachment removed: "DETECT_INTEL_E1000E_BUGGY.sh"
http://launchpadlibrarian.net/17925250/DETECT_INTEL_E1000E_BUGGY.sh
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you a
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 wro
Remo, this bug is about the e1000e driver, which is a Gigabit ethernet
driver. Any issues you're seeing with your wireless are unrelated to
this bug.
What reason do you have to believe your wireless has been broken, as
opposed to simply being unsupported by Intrepid?
--
[intrepid] 2.6.27 e1000e
HELP!! Intrepid Ibex broke the wireless of my brand new Latitude e6500..
(Wireless NIC is a Intel Wifi 5100)
Someone here has an idea on how to fix it??
Ubuntu disappointed a big big Ubuntu fan with this!!
I mean.. We are talking about breaking HW not partitions or SW..
If someone can help me in
** Changed in: linux (Fedora)
Status: Confirmed => Fix Committed
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
> 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 bu
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 myself a script in perl, i will NOT post this. Please Ubuntu
Developers post
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
> > http://episteme.arstechnica.com/eve/forums/a/tpc/f/9650
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: http://paste
I suggest to change the topic, provided Hew McLachlan's list is
reasonable. Since those chips are also on add-on and riser cards, also
systems with non-ICH8/9 chipsets are possibly affected. My suggestion:
2.6.27 e1000e driver places Intel gigE network chips (affected: ICH8 /
ICH9 chipsets and pos
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
Pelládi: Afaik a "full" virtual machine protects you from this bug,
since it only emulates a network card and does not grant direct access
to the hardware. I've seen that VirtualBox can emulate a e1000 gigabit
adapter, maybe you can try to currupt your virtual NVRAM if you want to.
Something else
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: http://pastebin.com/f6e9042ad
--
[intrepid] 2.6.27 e1000e driver place
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?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received th
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
.
8086:1049 82566MM Gigabit Network Connection (Centrino Pro notebooks made since
2007)
8086:104a 82566DM
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
Hi,
I understand Intel Gigabit controller are affected. But which ones
exactly? Wht PCI IDs and model?
Currently I have:
00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network
Connection (rev 02)
Subsystem: Intel Corporation Unknown device 0001
Control: I/O+ Me
Someone try this patchs from Jeff Kirsher (Intel)?
http://lkml.org/lkml/2008/9/23/427
http://lkml.org/lkml/2008/9/23/431
http://lkml.org/lkml/2008/9/23/432
Best regards,
Renato
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263
As previously mentioned:
Discussion, flames, complaints,anything not immediately useful to
getting the bug fixed etc goes here:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Anything else that *is relevant* to getting the bug fixed goes here.
--
[intrepid] 2.6.27 e1000e drive
@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
Daniel, to be honest, no one can really protect anyone of bugs until
they know about the bugs to protect people against. This is the first
time in a long time (perhaps ever) that this sort of report has been
confirmed.
They've done the best they can to protect people by educating everyone
on the m
All this is just crazy!
I'm testing Intrepid since Alpha 3, I have done testing on all Ubuntu
releases at very early stage (Alpha 2) starting from 6.10. I'm not
developer myself and the only way I can help improve Ubuntu is to test
and submit bugs. I assume that I can loose some data and on regul
Not fixed - LP closed the bug due to the reference in the changelog.
** Changed in: linux (Ubuntu Intrepid)
Status: Fix Released => In Progress
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug
Fahim: the driver has been disabled until a proper fix emerges. This does mean
that anyone using e1000e with Intrepid is unable to do so at the moment, but
this is felt to be a better workaround than continuing to place unknown numbers
of machines at risk of permanently losing their ethernet chi
Came in to work this morning and updated my intrepid system, noticed a
new kernel and had to update. When the system came back up, eth0
disappeared. Now I have no network connection at all. :( Did an lspci,
and I have an Intel 82566DM-2 Gigabit Network Connection (rev 02)
I'm guessing (and I'll ad
my t61p has
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
Connection (rev 03)
I work on
2.6.27-4-generic i686
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification b
I own an X61s, with an Intel Graphics Card and the following Network device.
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
Connection (rev 03)
I used the e1000e module sind alpha5 and with all new kernels till
yesterday. I did not get in any problem with this driver - lu
Jojo: Your T61p is ICH8 based, right? Is the following ethernet card
built into all ICH8-based machines? (just run lspci):
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
Connection (rev 03)
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at ris
I'm using X4500 Intel graphics, too.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Nothing happend to me either. Probably it depends on the system bios /
firmware. My Vaio Z does not have an ordinary BIOS, but a new (U)EFI
firmware with bios emulation. Probably the emulation denies access (to
some parts) of the NVRAM!? Just to make sure, blacklisted and removed
e1000e.
Please no
I was using 2.6.27-rc era e1000e on a Dell desktop machine and my
ThinkPad X300 for a few weeks, and they operated fine.
Both machines have the Intel 965 video chipset.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You
according to
http://groups.google.com/group/linux.kernel/browse_thread/thread/a5ef7deff8551186/d05c233ecb430178
this bug might be related to xorg and Intel graphics.
I used e1000e for 5 days with lot of traffic on eth0 and nothing
happened (luck?) but I have T61p wit NV Quadro
--
[intrepid] 2.6
This bug was fixed in the package linux - 2.6.27-4.6
---
linux (2.6.27-4.6) intrepid; urgency=low
[ Tim Gardner ]
* Disable e1000e until the NVRAM corruption problem is found.
- LP: #263555
[ Upstream Kernel Changes ]
* Revert "[Bluetooth] Eliminate checks for impossibl
** Changed in: linux (Mandriva)
Status: Unknown => Confirmed
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Mandriva Linux #44147
http://qa.mandriva.com/show_bug.cgi?id=44147
** Also affects: linux (Mandriva) via
http://qa.mandriva.com/show_bug.cgi?id=44147
Importance: Unknown
Status: Unknown
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipset
If we don't pull the images (we should, but I won't comment since it's
already being discussed), it might be a good idea to at least make the
words "permanently inoperable" on the Alpha 6 testing page in big, bold
letters so users have less of a chance to skim over that part.
Think about it: How m
Please listen to what Jesse said in comment #24. This is a bug report,
not a discussion forum.
Calls for ISOs to be pulled, legal claims, accusations and use of
capslock should be on the ubuntu-devel or ubuntu-devel-discuss mailing
list. For one thing, by posting to those lists your opinion will b
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 t
I was really shocked to see that it took more than one day between the
Issue becoming apparent and the warning being placed on the website.
This is a very serious issue and can cause severe damage on really
expensive hardware (i.e. most recent Lenovo Thinkpads like the X200,
X301, T400, T500 and so
Not to mention the thousands of people who downloaded these images
before the warning was posted.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs,
I think a warning (with Jesse Brandeburg's advice) should go to *every* tester
who is running such a system.
I just read about it on a computer news site and I wish I got this news form
canonical (maybe via update manager)
Ing0R
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gig
Why do i not feel the warnings are enough?
for one, because users who download VIA bittorrent will never see those
warnings, and like somebody above noted, not all testers know for
certain the hardware they are running. Simply saying "if your computer
breaks, tough luck, we warned you" will not ga
Thomas, why do you feel that the present warnings are not enough? I for
one feel that they are certainly sufficient warning to people running
those chipsets to not download them. Also, this isn't a democracy; we
don't vote on whether to pull images or not. That's up to the core
developers/Canoni
I for one second the motion to remove the alpha images until they have
been prepared so that there is no risk of hardware damage. I would be
seriously concerned about the negative effects of ignoring this issue.
There is a liability on Canonical for the distribution of software which
causes perman
One alpha tester has already been lost, at least partially. When the
problem occurred I sucked it up and said to myself, you know, it is
alpha. Things like this shouldn't happen, but they do from time to
time. Now that I see the indifference of Ubuntu devs to people losing
their hardware, and ev
** Changed in: linux
Status: Confirmed => In Progress
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Changed in: linux (Suse)
Status: Incomplete => In Progress
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
>The process is working as far as I can see, we have a set of users that
is reporting the problem, which will help keep the kernels with the
issue from being promoted to full production status.
I'm sorry .. will you buy these a new laptop? Ifso, then the proccess is
working.
Try advertising: ther
I had the duplicate bug 272630 and consider myself lucky. I had the
Intel NIC but had used Alpha 5. I only had the dmesg error and not the
hardware eeprom failure. I had Alpha 6 ready to test until I found this
bug thread. For folks like me, it will be a good decision to blacklist
e1000e pendin
Even if it means making myself look like an idiot: May I also suggest
publishing (maybe along with the warnings) hints about how to find out
whether your hardware is / will be / might be affected. And when does
that eeprom writing actually happen - at boot time, when using the lan
interface, or els
Uploaded module-init-tools_3.3-pre11-4ubuntu10 to temporarily blacklist
e1000e.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
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
https://bugs.launchpad.net/bug
Intel has ~80% CPU market share and >=70% of the chipset market for
their own CPU.
So at least 56% of machines sold are Intel CPUs with Intel chipsets that
are susceptible to this bug.
1 in 2 of Ubuntu testers could be vulnerable to this.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and
101 - 200 of 204 matches
Mail list logo
