On Sun, Feb 10, 2013 at 5:54 PM, Fabio Erculiani <[email protected]> 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
