mash, I believe busybox fdisk only uses MB, GB whereas gnu fdisk does use MiB and GiB. In the initrd.gz we only have busbox fdisk available. See screenshot. Ah, I see. Didn't know the output is different. This init works for me too. Either with gyro's or with original lxpup kernel. Yes, the origina...

Give me a few minutes bigpup and I'll upload an initrd.gz I'm using gyro's kernel 5.4.46 and the init I'm going to commit to woof in slacko64-6.9.9.10. My reason is to exclude that it was a scpup issue. Now I'll be using scpup64 when I update the initrd.gz.. is that ok for you? EDIT: I've uploded a...

@gyro

Both init scripts dropped me to the prompt at boot. I think this is the same point as bigpup wrote.

This could be tested by "mash" by booting with his SD card out, then after inserting the SD card, see if "lsmod" shows any of the modules in '/lib/modules/4.4.187/kernel/drivers/mmc/host/' No, it doesn't. I looked into dmesg and run diff on lsmod output before and after insertin...

OK, I think I got it. This post should be prepended by Jean-Luc Picard's facepalm. "The problem" exists only in some circumstances which I describe. I am curious if anyone of you tried to boot from SD card and succeeded because my SD card and/or reader was the case of the problem. So, the ...

@mash @bigpup are either / both of you booting directly from ssd?? I'm booting from USB flash drive. If bigpup's machine will boot with that initrd: https://www.mediafire.com/file/a72erhw7pg1f732/initrd-f53e2b980-20191201.gz/file we can narrow it to two commits from 6th December. Yes, they do not l...

Anyone who wants to check my versions, you can download them here: https://www.mediafire.com/file/a72erhw7pg1f732/initrd-f53e2b980-20191201.gz/file https://www.mediafire.com/file/t04tekv7jh4ih1u/initrd-cb7ac560c-20191206.gz/file Rename it to initrd.gz and place in the frugal install folder. These ar...

mikeslr: thanks for suggestion, I will try that.

And BUILD_FROM_WOOF='HEAD;cb7ac560c;2019-12-06 22:02:47 +1000' initrd is first to fail for me. I got kernel panic.

19.09+7 works. I already have been testing some other builds and have another one working BUILD_FROM_WOOF='HEAD;f53e2b980;2019-12-01 19:44:38 +1000'. It is from 1st December as yours test initrd. I was renaming DISTRO_SPECS as gyro sugest. Simple sed -i 's/19.09/20.01/g' DISTRO_SPECS' in expanded in...

Yes, this is initrd with "the problem". Although initrd from BUILD_FROM_WOOF='testing;7890189c5;2019-12-28 08:51:15 +0100' did not work in my case. I had to go back to ScPup64-19.09+0-uefi-T.iso which is BUILD_FROM_WOOF='testing;12196cacc;2019-09-15 07:49:16 +1000'. Initrd from this ScPup ...

Still the same kernel panic for all mentioned kernels.
Kernel version seems not relevant. (maybe...)

If this might be helpful, I downloaded Slackware live distro https://slackware.nl/slackware-live/ and it boots without problems.

Tried alternative kernels 4.19.13, 5.2.11 and 5.4.6 with no luck. Still the same kernel panic. I attach my PupSysInfo. I tried also to track breaking change. I know that ScPup 19.09 works and 20.01 don't. As I was expected, Slacko64 6.9.9.9 - BUILD_FROM_WOOF='HEAD;12196cacc;2019-09-15 07:49:16 +1000...

Also kernel panic during boot. HP Probook 6475b AMD A10-5750M APU with Radeon(tm) HD Graphics Frugal install and booting from USB sick. I get kernel panic for every ScPup from 20.01+0. Last working is 19.09+0. Also tried building Slacko and BionicPup from latest Woof-CE. They're both failing to boot...

Please add snd_pcsp module to blacklist as a default.
I found it (moderately) annoying to hear loud "beep" while testing puppy on several machines without loading my personal pupsave.

Otherwise that's great distro.