Giacomo Catenazzi wrote: > Jim Paris wrote: > > I figured out the problem: the "microcode" module was not loaded. > > (my kernel has CONFIG_MICROCODE=m). After "modprobe microcode" > > and "apt-get -f install", everything was OK. .. > > I would also recommend that you don't unconditionally unload the > > microcode module in /etc/init.d/microcode.ctl. If I, for example, > > included "microcode" in /etc/modules, I wouldn't expect a startup > > script to undo that. .. > Anyway, why do somebody need microcode modules loaded? > I think only microcode.ctl use this module (and in future > udev, but in this case only at module loading).
I ran into it because, while testing, I did: modprobe microctl apt-get remove microcode.ctl # works apt-get install microcode.ctl # works apt-get remove microcode.ctl # works apt-get install microcode.ctl # fails and I was surprised to realize that the "microctl" module had been unloaded and was causing problems again. But I suppose that once the postinst is fixed and doesn't need microctl manually loaded, this won't be a problem for anyone. -jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
