[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.WNT.2.00.0903161143180.5116@jbrandeb-desk1.amr.corp.intel.com>
Date: Mon, 16 Mar 2009 11:47:22 -0700 (Pacific Daylight Time)
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: Ben Greear <greearb@...delatech.com>
cc: NetDev <netdev@...r.kernel.org>, dwmw2@...radead.org,
jesse.brandeburg@...el.com, e1000-devel@...ts.sourceforge.net
Subject: Re: e100 firmware in 2.6.29-rc7?
On Fri, 13 Mar 2009, Ben Greear wrote:
> I have selected build-firmware-into-kernel
> but it seems e100 is still unhappy in 2.6.29-rc7.
>
> e100 0000:02:01.0: firmware: requesting e100/d102e_ucode.bin
> e100: eth4: e100_request_firmware: Failed to load firmware "e100/d102e_ucode.bin": -2
can you post anything extra about your config? arch? full dmesg? full
.config?
There have been several other reports of this but setting
CONFIG_FIRMWARE_IN_KERNEL=y seems to fix them in general.
also please post lspci -vvv -s 2:1.0, after failing to load. I'm curious
if the device might be in D3 still.
you can likely just get working by commenting out the firmware load for
e100. It may or may not re-enable a hardware bug depending upon the
hardware you have.
Jesse
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists