Launchpad has imported 129 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=425480.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Launchpad has imported 37 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=459202.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
this bug is not a catchall for all e1000e issues, the original issue
this bug was filed against is fixed and will be highly unlikely to
reoccur. If you're having e1000e issues please file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have ThinkPad X60 with 82573L, and after upgrading to 11.04 beta with latest
kernel it stop working almost at all.
Tested e1000e 1.2.20-k2 (in stock kernel) and 1.3.10a driver with no luck,
booting with option pcie_aspm=force doesn't help, I've tried
e1000e_recover.iso but it does not boot on
** Changed in: linux (Mandriva)
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263555
Title:
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263555
Title:
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE
chipsets at risk
** Changed in: linux (Gentoo Linux)
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263555
Title:
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE
** Changed in: linux (Ubuntu)
Status: Fix Released = 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
Please don't change bug statuses without explanation
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
[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
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 notebook is a Fujitsu Siemens Lifebook E8410
Thank you Dave!!!
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9
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
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 00 00
10: 00 00 40 fe 00 40 42 fe 21 18 00 00 00 00 00 00
20: 00 00 00 00
] 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 am still contacted about once per month for instructions on how to
recover ethernet functionality on systems that have had their 1Gb flash
content corrupted, possibly by this defect.
If you believe that you are affected by this isssue, you can safely
perform steps 1 through 5 from the bullet
Prior to upgrading to kernel 2.6.27-9 No kernel panics were experienced.
However kernel panics seem random they seem to occur during high network
activity when using the Ethernet device (Intel Corporation 82573L Gigabit
Ethernet Controller) which uses the e1000e driver. No reports of hardware
Is there a link as to how to recover ?
--
[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
While we should expect no further reports of flash corruptions due to
this bug, I would like to know of any systems which did fall foul of the
bug, and have not yet had their flash restored. Pleae let me know if you
have system that had proper (e1000e) LAN functionality proor to
installing a
** Changed in: linux (Ubuntu)
Assignee: Tim Gardner (timg-tpi) = (unassigned)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Basilisk (bluebal-1)
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You
** Changed in: linux (Ubuntu)
Assignee: Basilisk (bluebal-1) = Tim Gardner (timg-tpi)
--
[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
** Also affects: linux-lpia (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lpia (Ubuntu Intrepid)
Importance: Undecided = Critical
Assignee: (unassigned) = Amit Kucheria (amitk)
Status: New = Fix Committed
Target: None = ubuntu-8.10
--
[intrepid]
This bug was fixed in the package linux-lpia - 2.6.27-4.9
---
linux-lpia (2.6.27-4.9) intrepid; urgency=low
[ Amit Kucheria ]
* SAUCE: Start new release Ignore: yes
* SAUCE: Add LPIA keyword in front of all our tags
* SAUCE: Disable DYANMIC_FTRACE
- LP: #263555
*
** Changed in: linux (Gentoo Linux)
Status: Confirmed = Fix Released
--
[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
So in the interests of adding some closure to this bug. The issue turns out to
have never been the e1000e driver's fault.
Just to clarify. there were two bugs here. Yes the ftrace code should
have been more careful in using cmpxchg, and tried harder to not write
into code that might have
** Changed in: linux (Gentoo Linux)
Status: Fix Released = 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
Is this Problem resolved now? I think I read somewhere that there
already is a patch that you guys from Ubuntu just need to integrate. Is
that true? If yes why is it taking so long? (no offense, just curious)
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
jagdfalke: Please see the top of the page, it's marked as Fix Released
--
[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
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
For your Information: Launchpad is NOT a support forum, in future
situations please refer to the forums. As for your Problem: The driver
is fixed in the current kernel-release, but as the live-cd still ships
with the old kernel, networking is of course disabled with this card. I
recommend waiting
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:
So in the interests of adding some closure to this bug. The issue turns out to
have never been the e1000e driver's fault. The fault lies with the
CONFIG_DYNAMIC_FTRACE option. So specifically when the FTRACE code was
enabled, it was doing a locked cmpxchg instruction on memory that had been
Try to get a Vista DVD from somebody. You can actually boot them in a
sort of Live System, perhaps you can install the drivers in it (the
installation does not need a restart).
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
hello,
a week ago I have upgraded my Hardy to Intrepid beta on 3 machines. the
oldest one is still with Intrepid but two new had to be downgraded to
Hardy since network did not work.
is it safe now to upgrade them to Intrepid beta or should I wait for
official release?
--
[intrepid] 2.6.27
Michael as im having the same issue; i might try and do the same. Quite
disappointing that we have to rely on Windows to bail us out. Ive even
tried compiling the Intel drivers under Linux with the same error.
Perhaps a live Windows Distro like Barts PE? I dont want to have to put
the V1sta disks
** Changed in: linux (Suse)
Status: In Progress = Fix Released
--
[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
This is the patch which has passed Intel's testing and with this patch that
issue can't be reproduced again now. It looks to be a work-around and with the
.28 a fix for the root cause of the problem.
Date: Wed, 15 Oct 2008 18:21:44 -0400 (EDT)
From: Steven Rostedt [EMAIL PROTECTED]
To:
I fixed my network card in my x61t with the Vista drivers from intel.com
(
http://downloadcenter.intel.com/Filter_Results.aspx?strOSs=AllstrTypes=AllProductID=2775lang=engOSFullName=All%20Operating%20Systems
). Yust installed them and played with their diagnostic tools in the
driver.
Both PXE and
** Changed in: linux (Gentoo Linux)
Status: Confirmed = Fix Released
--
[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
If it helps i am also having this problem aswell; i have included output of
lshw aswell
//
Linux penfold 2.6.27-6-generic #1 SMP Tue Oct 7 04:15:04 UTC 2008 i686 GNU/Linux
[2.319073] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
[2.319076] e1000e: Copyright (c) 1999-2008 Intel
** Changed in: linux (Fedora)
Status: In Progress = Fix Released
--
[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
** Changed in: linux (Fedora)
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
same for me:
under Linux, the e1000e driver refuses to load:
388.961230] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
[ 388.961249] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 388.961346] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20
[ 388.961374] e1000e
sorry .. i miss to read previous comment, i done it manually now i get
from dmesg
[ 25.596061] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
[ 25.596065] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 25.596142] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20
[
I don't know if open a new bug. I think e1000e have some problem here result of
furter investigation.
Same behaviour from 27.3 and 27.5 (in the last driver is not blacklisted).
Sometime network work out of the box, sometime network work out of the box
sometimes I need to:
sudo modprobe -r
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
I confirm that the new binaries are working for me.
uname -r
2.6.27-5-generic
Thanks a lot for the great job!
--
[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
The fix will be included in the subsequent daily images
Is the fix avalible now in the daily builds?:
http://cdimage.ubuntu.com/daily-live/current/
if not when will it be? Or is there another link?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Driver seems to be ok, eth0 come up automagically.
Now I think there are problems with knetwork manager: i wrote manually
resolv.conf and i have to restar network from a shell to make dns work.
But probably this is another story.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9
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.
--
[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
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
the updated kernel is in the 20081006 manifest:
linux-generic 2.6.27.5.5
linux-headers-2.6.27-5 2.6.27-5.8
linux-headers-2.6.27-5-generic 2.6.27-5.8
linux-headers-generic 2.6.27.5.5
linux-image-2.6.27-5-generic 2.6.27-5.8
linux-image-generic 2.6.27.5.5
linux-libc-dev 2.6.27-5.8
any ways to fix/patches/ways for eeprom/NVM problem? after upgrade to
2.6.27-5.8, the Ethernet still wont work ?
$ dmesg | grep e1000e
[5.604448] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
[5.604456] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[5.604557] e1000e
** Changed in: linux
Status: In Progress = Fix Released
--
[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.
--
@Anil: While that re-enables the driver for the session, it's not the
permanent solution.
I just upgraded from 2.6.27.4 to 2.6.27.5, but /etc/modprobe.d
/blacklist-e1000e still remains on disk, and you'd need to either
comment out the line blacklisting the driver, or move/delete the file to
get
i've finally received the -5 drivers and i still don't have an internet
connection available to me. the only kernel im having any luck with is
-3.
--
[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
Hi all, mi 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
GNU/Linux
This is lspci result:
00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)
It seems card is
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
GNU/Linux
This is lspci result:
00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)
It seems card is
Arve's fix was good, I have blacklisted the driver e1000e as the
workaround and never removed the blacklist. With the removed from
/etc/modprobe.d/blacklist it works fine
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
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
Just confirming that it works fine with my T61p 6457-7WU.
$ uname -r
2.6.27-5-generic
$ lsmod | grep 100
e1000e128040 0
lshw also shows the device properly setup, and no longer unclaimed.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Mine was T61 6464 - AP3
If upgrading the 2.6.27-5 this morning
[EMAIL PROTECTED]:~$ uname -r
2.6.27-5-generic
[EMAIL PROTECTED]:~$ lsmod | grep 1000
it doesnt give me any result, should i remove the blacklist manually or
it will be done automatically after upgrading it ?
--
[intrepid]
i've tried manually remove the blacklist-e1000e but it doesnt work for
me at all .. any suggestion what should i do next ?
--
[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
No package here, when it will arrive? It's really amazing when you have
no network ...
--
[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
If you have no network whatsoever, you'll need to grab the package using
another machine or OS, use a daily build CD image, or downgrade to a
version where the driver was not disabled and then upgrade to the
current one.
http://packages.ubuntu.com/intrepid/linux-image-2.6.27-5-generic
Kernel Bugzilla #11382 is already fixed
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4a7703582836f55a1cbad0e2c1c6ebbee3f9b3a7
Best regards,
Renato S. Yamane
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
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]:~$ uname -a
Linux penfold 2.6.27-5-generic #1 SMP Fri Oct 3 00:38:23 UTC 2008 i686 GNU/Linux
[EMAIL PROTECTED]:~$ sudo
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]:~$
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?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
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?
--
This is very creepy that Linux can permanently damage hardware!
How can this be? Why?
How can it be prevented?
Does it really need to do these risky operations?
Similar things must never happen in the future! Completely unacceptable!
If Linux permanently damages peoples hardware, then nobody will
Fred, please comment only if you can provide relevant informations about
this bug, and use forums if you just want to complain.
--
[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
The bug is not fixed yet except to disable the driver.
I just upgraded from 8.04 to 8.10 beta using update
manager and the the card on a HP dc7800 was
disabled.
One problem with this is that once upgraded, you
have no connection to the internet to get fixes.
Had to do a fresh reinstall 8.04. I
** Changed in: linux (Mandriva)
Status: Confirmed = Fix Released
--
[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
Michael,
I don't believe the new package has been made available to download in
repositories yet, (i just checked). Once the new package is there, I would
test the upgrade again, for now you can use an older kernel and it should work.
I am not going to change back to Fix Released in case i am
Is there a way for me to unblacklist this until the update? The card
worked fine until I updated to the kernel with the blacklist. - Or is
this really a danger even if it works?
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Everyone here needs one answer. If we run 'apt' when are we going to get
the '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
https://launchpad.net/ubuntu/+source/linux/2.6.27-4.7/+build/728333
Status: Failed to upload
(...)
2008-10-03 02:46:59 INFORejection during accept. Aborting partial accept.
2008-10-03 02:46:59 WARNING Upload was rejected:
2008-10-03 02:46:59 WARNING Unable to find source package
2.6.27-4.7 was rejected because 2.6.27-5.8 had already been uploaded. I
just accepted the binaries for 2.6.27-5.8 into the archive, and they
should be available within the hour; it will take a little bit longer
for the 'linux' etc. metapackages to catch up with this.
** Changed in: linux (Ubuntu
Thanks Colin.
2.6.27-5-8 works for me:
00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit
Network Connection [8086:10f5] (rev 03)
--
[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
Will You update/rebuild beta cd/dvd images once fix is released?
Sorry for negative opinion but it's ridiculous that many people who have such
ethernet cards can't use this beta because of not functional network card and
even can't get fixed packages by update without other Internet connection.
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
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
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
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 known practice - release a fixed iso in a hurry - to
happen.
--
http://ubuntuforums.org/showthread.php?p=5889487#post5889487
--
[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.
--
Some people might have been around long enough to remember the Xorg
breaking dapper update in 2006. There are quite a few similarities in
what happened and peoples responses.
After the incident there was a report, and changes were made to make
sure it did not happen again [0,1]. Once this has
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) and it work fine
in windows... only in linux box have the The NVM Checksum Is
** 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
This bug is in an alpha release which is using a release candidate
version of the kernel so I think your comments are too tough. Why don't
you use hardy as suggested in many places in Ubuntu documentation?
My only concern about the present bug is that it discourages testers of
alpha software who
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
Hey guys,
Let's use this bug tracker to get the problem fixed. Can we please keep
the discussion of whether or not to pull the CD image to the forums or
mailing lists? This is a place to talk about the bug *itself* and how to
get the bug *itself* fixed, not to discuss the implications of this
A small Button with the phrase Don't Panic on it ...
http://lkml.org/lkml/2008/10/1/368
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4a7703582836f55a1cbad0e2c1c6ebbee3f9b3a7
This patch is meant to prevent all future corruptions of the
e1000e NVM (non volatile
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
I'm using intel based HP dc5800 Desktop with Ethernet card that is using the
bad drivers. I've migrated to Intrepid after alpha 2 was released and unti the
e1000e driver was blacklisted (i've noticed no eth0 :) ) I had no problems. Now
I'm using external LAN and my dualboot Vista is working
Well, those patches were released in the last two or three days --
basically, we have to wait for upstream kernel devs who are
capable/willing to reproduce the issue to test the patches, and then
consider how to get that code into the Ubuntu kernel. (Directly applying
patches? Go through Debian
The patch is already committed to ubuntu git branch of the kernel. All
ubuntu packages have been frozen for a few days for the beta release. I
dont think there is any chance of putting a new kernel in the beta at
this stage. After the beta is out there will most likely be a kernel
update with the
So will the nic drivers be blacklisted in the beta? And hopefully
updated later with a patch?
--
[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,
1 - 100 of 204 matches
Mail list logo
