It seems this is a problem with other laptops as well as mine as others have posted to this bug tracker with similar problems (which I hadn't seen before I posted). But I shall post the workaround here so if others search for it it may help.
I hadn't realised that there is more information than the normal "dmesg" within "syslog" (something to remember). For the record pressing "e" on the installer boot option that you want to run and then inserting "modprobe.blacklist=mt7921e" (without quotes) on the line before the ---- allows the installer to work beyond the point of the error message (as far as the scanning disks which found the nvme and the partitions on it successfully; I didn't go any further as I don't want to reinstall again). The issue seems to be that the driver isn't loaded, and then is being removed which is causing the crash dump. At this point this is way beyond my abilities... but as the workaround fixes the issue (however [in]correctly) I'm happy. I vaguely remember that when I was running Bullseye for a short time it didn't have a driver for the wireless/Bluetooth and required me to download a driver from another site and DKMS it so I'm guessing that is why the install works on Bullseye (it doesn't even bother to try and load it as its much newer than that kernel?) and not Bookworm. Although it seems bad that failing to remove a module that is not loaded causes the whole thing to fall down in a big messy heap. At least now I know about the bug tracker and how to actually search it (the layout really isn't for the uninitiated!) and that it exists (does google even index the tracker?) the next time I have an issue this will be the first port of call. Jon
