Bug#1016882: Update on the bug reported(reason for regeneration figured out)

[Andreas Beckmann]

On Thu, 11 Aug 2022 00:45:56 +0530 Tanmay Bora 
 wrote:

But now as REMAKE_INITRD is deprecated there should be some other method
for automatically regenerating the initrd after installing
broadcom-sta-dkms package or atleast the Debian wiki should be updated with
the additional note of manually regenerating the initrd after installing
the package.


That sounds like the postinst should call

dpkg-trigger --no-await update-initramfs

or you can simply add debian/broadcom-sta-dkms.triggers with the 
following line:


activate-noawait update-initramfs

to do that without creating a postinst script.
(both solutions untested)


Andreas

Bug#1016882: Update on the bug reported(reason for regeneration figured out)

[Tanmay Bora]

I have figured out why the Initrd image needs to be regenerated(to add the
modprobe blocklist configuration file to the initrd so that the conflicting
modules are not loaded and only then the 'wl' module can be loaded
correctly. In my case the ssb module was loaded when the blocklist config
was not added making the 'wl' module unloadable.).

But now as REMAKE_INITRD is deprecated there should be some other method
for automatically regenerating the initrd after installing
broadcom-sta-dkms package or atleast the Debian wiki should be updated with
the additional note of manually regenerating the initrd after installing
the package.