From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Qstl8-0005Wl-Ua for garchives@archives.gentoo.org; Mon, 15 Aug 2011 09:47:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9223F21C130; Mon, 15 Aug 2011 09:46:53 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id E384221C0E6 for ; Mon, 15 Aug 2011 09:45:53 +0000 (UTC) Received: by vws13 with SMTP id 13so4744348vws.40 for ; Mon, 15 Aug 2011 02:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gzpZPSulCAHapsP3j48Z0DTOtDWBqmJtEqaCmFndy5Q=; b=HTBw7FeZjqNKHA/wI14kJmpAYH87tLsyiSEOh62xoPqXUIx7+Vx5x2iCUSBQ7kgFwM Vwg9U3+t8FAQFoVSp/pM8wcidR5/bHBRM0gHoRQwq1ERRUOO9oyl+uv4DwXCq3LEJsxz P8Csyhy5ehxmY8fWPHWo8K3a+KfN8Uv/DyxUY= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.220.24.11 with SMTP id t11mr915929vcb.224.1313401553325; Mon, 15 Aug 2011 02:45:53 -0700 (PDT) Received: by 10.220.179.2 with HTTP; Mon, 15 Aug 2011 02:45:53 -0700 (PDT) In-Reply-To: <09f426b281f06826f8603d8086e279c1.squirrel@www.antarean.org> References: <09f426b281f06826f8603d8086e279c1.squirrel@www.antarean.org> Date: Mon, 15 Aug 2011 19:45:53 +1000 Message-ID: Subject: Re: [gentoo-user] Firmware exists but fails to load From: Adam Carter To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: X-Archives-Hash: a52b86188ce00fe5dc4bba6b46749130 > Is the filesystem mounted when it tries to find the firmware? I thought it was, but having another look at dmesg, it looks like that's not the case. proxy linux # dmesg | grep eth0 [ 0.897559] r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xffffc90000360000, 1c:6f:65:20:3f:c6, XID 083000c0 IRQ 41 [ 70.453673] r8169 0000:02:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168d-2.fw (-2) [ 70.461027] r8169 0000:02:00.0: eth0: link down [ 70.461050] r8169 0000:02:00.0: eth0: link down [ 70.461444] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 72.851287] r8169 0000:02:00.0: eth0: link up [ 72.851846] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready proxy linux # dmesg | grep btrfs [ 1.647953] btrfs: use lzo compression [ 2.129807] VFS: Mounted root (btrfs filesystem) on device 0:13. > In other words, are you perhaps using a ramdisk? > > If you have this drives as a module, can you try removing it (rmmod > and then reloading it (modprobe )? > > If it isn't a module, can you rebuild your kernel to have the relevant > driver as a module? Its not a module - i'll make it one and see how that goes.