Am Mittwoch, 7. Januar 2009 07:26:44 schrieb Alan McKinnon:
e1000e breaks the hardware
e1000 does not break the hardware
Or maybe it's the other way round
Nope. None does. That bug was only present in one or two .27 release
candidates and has been fixed since weeks.
Bye...
Dirk
Neil Bothwick wrote:
On Tue, 6 Jan 2009 15:06:28 +, Peter Humphrey wrote:
I've seen a dev complain that most of the problems he's had to deal
with have been due to oldconfig, so I don't use it at all. I copy
the config in from the previous tree, then I run menuconfig and
search for
On Tue, Jan 06, 2009 at 07:54:30AM +, Neil Bothwick wrote:
That's just FUD.
You should tell it to the documentation team.
--
Nicolas Sebrecht
On Tue, Jan 6, 2009 at 1:44 AM, Nicolas Sebrecht
nicolas.s-...@laposte.net wrote:
On Tue, Jan 06, 2009 at 12:59:13AM -0200, Francisco Ares wrote:
snip
Avoid the HTML format in your mail, please.
Also, learn to quote.
sorry about that
--
Nicolas Sebrecht
Francisco
Dirk Heinrichs wrote:
Am Dienstag, 6. Januar 2009 02:56:28 schrieb Denis:
I have Intel network hardware that
runs on the E1000 driver
Did you try e1000e?
Bye...
Dirk
e1000e had been disabled in 2.6.27 versions, was it put back in by -r7?
Am Dienstag, 6. Januar 2009 11:14:08 schrieb Steven Susbauer:
e1000e had been disabled in 2.6.27 versions, was it put back in by -r7?
Don't know. In vanilla-sources, it has always been there.
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
On 06.01.2009 12:14, Steven Susbauer wrote:
Dirk Heinrichs wrote:
Am Dienstag, 6. Januar 2009 02:56:28 schrieb Denis:
I have Intel network hardware that
runs on the E1000 driver
Did you try e1000e?
Bye...
Dirk
e1000e had been disabled in 2.6.27 versions, was it put back in by -r7?
On Tue, 6 Jan 2009 09:34:31 +0100, Nicolas Sebrecht wrote:
That's just FUD.
You should tell it to the documentation team.
The last time I looked at the docs for this, which was a while ago,
they recommended against using it for major version updates, which makes
perfect sense.
--
Neil
On Tuesday 06 January 2009 11:42:58 Neil Bothwick wrote:
On Tue, 6 Jan 2009 09:34:31 +0100, Nicolas Sebrecht wrote:
That's just FUD.
You should tell it to the documentation team.
The last time I looked at the docs for this, which was a while ago,
they recommended against using it for
On Tue, 6 Jan 2009 12:13:05 +, Peter Humphrey wrote:
I've seen a dev complain that most of the problems he's had to deal
with have been due to oldconfig, so I don't use it at all. I copy the
config in from the previous tree, then I run menuconfig and search for
lines ending in [NEW] or
On Tuesday 06 January 2009 12:45:15 Neil Bothwick wrote:
On Tue, 6 Jan 2009 12:13:05 +, Peter Humphrey wrote:
I've seen a dev complain that most of the problems he's had to deal
with have been due to oldconfig, so I don't use it at all. I copy the
config in from the previous tree, then
On Tue, 6 Jan 2009 15:06:28 +, Peter Humphrey wrote:
I've seen a dev complain that most of the problems he's had to deal
with have been due to oldconfig, so I don't use it at all. I copy
the config in from the previous tree, then I run menuconfig and
search for lines ending in
Neil Bothwick wrote:
On Tue, 6 Jan 2009 15:06:28 +, Peter Humphrey wrote:
I've seen a dev complain that most of the problems he's had to deal
with have been due to oldconfig, so I don't use it at all. I copy
the config in from the previous tree, then I run menuconfig and
search for
I'm doubtful that using oldconfig would make a driver not work because
I have done it this way for a while, going between various 2.6.x
versions, like 2.6.21 to 2.6.24... And there was never an issue.
Maybe the E1000 driver somehow got messed up in this particular
version of the kernel.
Now,
On Tuesday January 6 2009 20:37:31 Denis wrote:
I'm doubtful that using oldconfig would make a driver not work because
Unless the driver (module) changed name ;) (ata-pata/sata anyone?)
Anyway, I've always used oldconfig except when moving from 2.4 to 2.6
Regards,
Norberto
On Wednesday 07 January 2009 00:37:31 Denis wrote:
I'm doubtful that using oldconfig would make a driver not work because
I have done it this way for a while, going between various 2.6.x
versions, like 2.6.21 to 2.6.24... And there was never an issue.
Maybe the E1000 driver somehow got messed
Alan McKinnon wrote:
On Wednesday 07 January 2009 00:37:31 Denis wrote:
I'm doubtful that using oldconfig would make a driver not work because
I have done it this way for a while, going between various 2.6.x
versions, like 2.6.21 to 2.6.24... And there was never an issue.
Maybe the E1000
Hello and Happy New Year!
I was just updating from kernel linux-2.6.24-gentoo-r7 to
linux-2.6.27-gentoo-r7 using the oldconfig method, and I cannot get
the new kernel to load my network. I have Intel network hardware that
runs on the E1000 driver, which I generally compile right into the
kernel
On Mon, Jan 05, 2009 at 08:56:28PM -0500, Denis wrote:
Hello and Happy New Year!
Happy new year to every members here.
I was just updating from kernel linux-2.6.24-gentoo-r7 to
linux-2.6.27-gentoo-r7 using the oldconfig method, and I cannot get
the new kernel to load my network.
The use
On Tue, Jan 6, 2009 at 12:25 AM, Nicolas Sebrecht nicolas.s-...@laposte.net
wrote:
On Mon, Jan 05, 2009 at 08:56:28PM -0500, Denis wrote:
Hello and Happy New Year!
Happy new year to every members here.
I was just updating from kernel linux-2.6.24-gentoo-r7 to
linux-2.6.27-gentoo-r7
On Tue, Jan 06, 2009 at 12:59:13AM -0200, Francisco Ares wrote:
snip
Avoid the HTML format in your mail, please.
Also, learn to quote.
--
Nicolas Sebrecht
Am Dienstag, 6. Januar 2009 02:56:28 schrieb Denis:
I have Intel network hardware that
runs on the E1000 driver
Did you try e1000e?
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
On Tue, 6 Jan 2009 03:25:44 +0100, Nicolas Sebrecht wrote:
The use of 'oldconfig' when upgrading from a previous .z kernel (as in
2.6.z) is a bad idea. There are too much changes between such upgrades.
Please retry a compilation from scratch
That's just FUD. oldconfig is intended to be used
23 matches
Mail list logo
