Puppy Linux Discussion Forum

So, 10.0.43 boots OK from usb,,, refind, 1 iso per partition (efi)
But when installed on scsi drive, loads kernel and initrd OK (limine loader)
but can't find any sfs a few seconds later, so drops to recovery shell
blkid does not list scsi drive
pmedia=scsihd makes no difference
all of the 9.2 series on that drive give no problem,
somehow the kernel finds and loads mptsas module (shows in dmesg)
but not in 10.0.43
suggestions?
and so far, my bluetooth mouse is still not found, but doesn't lock bluetooth,
so at least that is better

Please attach the output of these commands on 9.2.x:

dmesg
lspci
cat /proc/cpuinfo
fdisk -l

Well, are you sure that you want so much? dmesg is 1635 lines
I don't want to pollute the forum
Maybe something like,,, dmesg |grep mpt and dmesg | grep scsi ??
and dmesg |grep blue

@wdt write the output to a file then make it a tarball or put a fake .gz extenstion on the file name and attach that file to a post.

OK, gz appended,, 13.gz

03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

Did this controller ever work with any Puppy version other than Vanilla Dpup 9.2.x? CONFIG_SCSI_MPT3SAS=m rather than CONFIG_SCSI_MPT3SAS=y in every "official" Puppy kernel I've looked at.

Yes, I see that in 9.2.x mptsas is builtin, so now it all makes perfect sense

Is this controller common in desktop computers? I don't know. I can change to CONFIG_SCSI_MPT3SAS=y, but this makes me wonder what other SCSI drivers need to become =y.

LSI is fairly common, my guess is LSI, adaptec, others (dell/hp/buslogic) in that order
LSI costs less than adaptec, the others often come as part of a server package(rather than add-in cards)
Curious, why is MPT3SAS=y in 9.2.x (rather than =m)?

wdt wrote: Sun Oct 16, 2022 3:19 pm

Curious, why is MPT3SAS=y in 9.2.x (rather than =m)?

It was a mistake