From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7F690138978 for ; Sun, 10 Feb 2013 19:43:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A2FF621C169; Sun, 10 Feb 2013 19:43:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A41B521C166 for ; Sun, 10 Feb 2013 19:43:26 +0000 (UTC) Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id C86EA33E4F2 for ; Sun, 10 Feb 2013 19:43:25 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id dn14so5541134obc.32 for ; Sun, 10 Feb 2013 11:43:23 -0800 (PST) X-Received: by 10.60.3.103 with SMTP id b7mr8930808oeb.86.1360525403648; Sun, 10 Feb 2013 11:43:23 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.76.90.73 with HTTP; Sun, 10 Feb 2013 11:43:02 -0800 (PST) In-Reply-To: References: <5117560B.3090709@gentoo.org> <20130210174634.77631769@sf> <1360508715.26312.8.camel@belkin4> From: Dirkjan Ochtman Date: Sun, 10 Feb 2013 20:43:02 +0100 Message-ID: Subject: Re: RFC: install linux-firmware with kernel sources (was Re: [gentoo-dev] Lastrite: Firmware cleanup, part #1) To: Gentoo Development Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: a2c98ead-451a-4965-81bf-15753aa9fc2d X-Archives-Hash: c0c1d54eefa8055e164e60adc04f553c On Sun, Feb 10, 2013 at 5:54 PM, Fabio Erculiani wrote: >> +1 from me; I've had a few machines break on kernel upgrades because I >> didn't have the proper firmware installed (I guess older kernel >> sources came with the firmware?). > > This is another problem, namely dependency level problem. > I don't see how having kernel sources ebuilds providing /lib/firmware > would fix any of the listed issues without causing other "side > effects". > For starters, if kernel sources provide /lib/firmware, how do you deal > with file collisions? I'm sorry, I have no clue about any of this; I was just signalling that I've run into problems twice now, where I: - had an old kernel working fine - upgraded it using the usual mechanism - then the network wouldn't come up on rebooting (bnx2 or tg3, not sure) - with an obscure error message that was really quite hard to connect to missing firmware, and - it turned out to work fine after installing linux-firmware. So it would be great to prevent other users from running into these kinds of trouble. Cheers, Dirkjan