OK, I see. This has been quite educational for me, so thank you for your reply.
I think I'll submit a wishlist "bug" to the debian-installer so that the user is notified during installation whether installing the CPU microcode package is recommended or not. If data loss may occur without having the updated microcode installed, I think it may be worth having the installer telling you. 2013/6/22 Ben Hutchings <b...@decadent.org.uk> > Control: tag -1 wontfix > > On Sat, 2013-06-22 at 01:13 +0200, Eugenio M. Vigo wrote: > > Hi, > > I want to get rid of the warning, mainly because I don't know whether > > it is of importance or not. My concern is that this didn't happen with > > the 3.2 kernel, so maybe there is a way to avoid installing that > > non-free package. > > Yes, there is a way to avoid installing that non-free package: do > nothing. > > The kernel didn't previously actively try to load updated CPU microcode, > and now it does. I think this warning is correct behaviour: CPU bugs > can cause data loss, and Debian promises not to hide problems. And your > CPU already runs non-free microcode, so installing the updated microcode > package doesn't become any more dependent on it. As always, you have > the choice whether or not to install non-free software. If you want a > kernel that takes that choice away, there is always linux-libre. > > Ben. > > -- > Ben Hutchings > Klipstein's 4th Law of Prototyping and Production: > A fail-safe circuit will destroy > others. >
