Hi Fabrizio, Upgrading to kernel 3.2.0 indeed solved the problem. I hadn't before simply because a dist-upgrade didn't include a new kernel.
It might still be a good idea to warn users before overwriting older firmware files, because fixing the situation might be difficult without wireless connectivity. I would suggest implementing a preinst script that emits a non-zero exit code to prevent installation, based on a debconf question in the config script (see http://www.fifi.org/doc/debconf-doc/tutorial.html#AEN113). Ideally, the are-you-sure question would be skipped if the system is already running a kernel >= 3.2 at installation time. What do you think? Cheers, Joris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
