On Sat, Jun 28, 2025 at 10:52:26AM +0200, Roland Sommer wrote: > Hello Uwe, > > > That is surprising. I would have expected that the only effect of that > > blacklist entry is that the module is not loaded. I don't understand > > how that entry makes a difference if it doesn't prevent the module > > being loaded. > > > > You can try > > > > update-initramfs -u -k all > > > > maybe then the module isn't loaded any more on the next boot. > > I'm sorry, it is. > > > The sr module might be enough to handle a DVD-RAM. > > Ok, then lets try it the hard way: rename > /usr/lib/modules/6.1.0-37-amd64/kernel/drivers/block/pktcdvd.ko and > reboot. > > -> dmesg reports > > Jun 28 10:38:06 nb06 (udev-worker)[2081]: sr0: Process '/usr/sbin/pktsetup -i 11:0' failed with exit code 1. Ahh, now that makes sense. pktsetup calls `/sbin/modprobe pktcdvd` explicitly, the blacklist entry doesn't help for that. Without the kernel module renamed, does the 2nd DVD-RAM result in the blocking behaviour? > -> lsmod reports pktcdvd not loaded > > -> And most important: DVD-RAM fully operational > > > Puzzled! > > And now? ;-) It's a tad better now :-) Given the lack of upstream response, the driver being orphaned, a working setup even without the module I think we'll go with disabling that module. Thanks for your report and helpful testing, Uwe
Attachment:
signature.asc
Description: PGP signature
