Recent Slackware-current kernel panics during install
by gordydawg from LinuxQuestions.org on (#6QVN5)
As of 9/18/2024 with the recent -current changes to one generic kernel, I tried a usb stick install on two Asus AMD motherboards (ryzen 5 3600 and 7600 cpu's) with BIOS set to CSM compatibility. Supporting both legacy and uefi booting.
Picking uefi, the install boots up normally.
When choosing to boot mbr, the install indicates loading of /kernels/generic.s/bzImage
and /isolinux/initrd.img
The Boot process runs through to the point where it goes through all of the available file systems, then kernel panics with the message: Not syncing, unable to mount root fs on unknown block (2.0)
I checked my usb stick against the Current file tree: isolinux, System.map.gz, bzImage and config all show the newest file updates.
I was wondering if a pointer or link name used in mbr booting was dropped when the 'one generic kernel to rule them all' was adopted.
Picking uefi, the install boots up normally.
When choosing to boot mbr, the install indicates loading of /kernels/generic.s/bzImage
and /isolinux/initrd.img
The Boot process runs through to the point where it goes through all of the available file systems, then kernel panics with the message: Not syncing, unable to mount root fs on unknown block (2.0)
I checked my usb stick against the Current file tree: isolinux, System.map.gz, bzImage and config all show the newest file updates.
I was wondering if a pointer or link name used in mbr booting was dropped when the 'one generic kernel to rule them all' was adopted.