Comment 2 for bug 123145

The first issue should be corrected in Debian 1.17-2: I do better error checking and I handle better debconf

The cause: the device was not found (no module loaded?) so postinst calls MAKEDEV, and MAKEDEV prints an error. debconf doesn't like console output (in particolar when debconf helper script are called in the wrong place (to late)).

Anyway Debian 1.17-2 is correct.

The second report is not an issue ;-):

The first part: If you run it manually, you should have also kernel/hardware support. The init.d script load the module, but I think it is not task of the program to load module (see devfsd vs. udev discussions). But then it would be an other question: should udev load the module (hardware found) at boot timet?. Maybe I will add some more info on man page.

The second part: it is correct. the microcode kernel driver have two loading methods: the "old" method with special device /dev/cpu/microcode and a loader "microcode.ctl";and a new method, using firmware kernel infrastructure (which print the warning). Unfortunately the second method is still in development. I think Intel will release it this summer. Anyway, maybe firmware_helper should be improved, because it should be a warning and not an error, and the "driver '(unknown)" is not correct ;-)