From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>
Subject: Re: 2.6.18-rc3-mm2: bad e1000 device name
Date: Tue, 08 Aug 2006 08:25:50 -0700 [thread overview]
Message-ID: <44D8ACFE.3060802@goop.org> (raw)
In-Reply-To: <44D8AB08.3000006@linux.intel.com>
Arjan van de Ven wrote:
> Jeremy Fitzhardinge wrote:
>> Andrew Morton wrote:
>>> e1000 seems OK here. Don't know, sorry.
>>>
>>
>> It's happening to all my ethernet-like devices: the Atheros wireless
>> comes up as a mess too. It's different each time, so it looks like
>> random uninitialized crud.
>>
>
> is this the binary atheros driver? then please try without that..
It happens regardless of whether the atheros driver is loaded (or has
ever been loaded). But it also happens to the atheros driver, so it
isn't specific to the e1000.
J
next prev parent reply other threads:[~2006-08-08 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:45 2.6.18-rc3-mm2: bad e1000 device name Jeremy Fitzhardinge
2006-08-08 7:40 ` Andrew Morton
2006-08-08 8:16 ` Jeremy Fitzhardinge
2006-08-08 15:17 ` Arjan van de Ven
2006-08-08 15:25 ` Jeremy Fitzhardinge [this message]
2006-08-08 15:26 ` Arjan van de Ven
2006-08-08 16:17 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D8ACFE.3060802@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).