(OLD) (ARCHIVED) Puppy Linux Discussion Forum

bigpup · Joined: 11 Oct 2009 Posts: 13981 Location: S.C. USA

On my HP Stream 14
Having a SD card plugged in or not has no affect.
But, I do need the different initrd.gz to get it to boot.

ScPup64 20.01 is frugal install on internal emmc drive.

01micko · Joined: 11 Oct 2008 Posts: 8787 Location: qld

gyro · Posted: Tue 09 Jun 2020, 04:09 Post subject:

peebee · Posted: Tue 09 Jun 2020, 04:28 Post subject:

bigpup · Joined: 11 Oct 2009 Posts: 13981 Location: S.C. USA

01micko · Joined: 11 Oct 2008 Posts: 8787 Location: qld

gyro · Posted: Tue 09 Jun 2020, 06:45 Post subject:

gyro · Posted: Tue 09 Jun 2020, 06:56 Post subject:

mash · Joined: 18 Dec 2017 Posts: 14

perdido · Posted: Tue 09 Jun 2020, 20:39 Post subject:

gyro · Posted: Wed 10 Jun 2020, 01:02 Post subject:

Sorry folks.

It looks like my "unavailable mmc kernel module" theory is wrong.

"mash" has reported that inserting an SD card after booting, does not cause the loading of a module.

And I have done some testing on my Lenovo IdeaPad 100S:

I know that it has an "unavailable mmc kernel module" issue.
So I if my theory were correct, I would expect the Lenovo to exhibit the issue, and kernel panic.
But it did not, it boots scpup32 out of the box, fine, i.e. with the "offending" code in the 'init' script.

Without the needed mmc kernel module, the 'init' script is completely unaware of any mmc devices, as seen in '/initrd/tmp/probepart.log'

So, I have nothng.

gyro

01micko · Joined: 11 Oct 2008 Posts: 8787 Location: qld

I have a Dell Latitude E7270 laptop with builtin card reader. The reader is not available for booting unless I use gyro's initrdmodules tool.

The computer boots fine from a usb stick with the sdcard plugged in, but nothing can be found on it until zdrv is loaded of course.

For the record, I'm running slacko64-6.9.9.10 fresh out of woof-ce.installed to a usb stick with gyro's other utility f2stickpup, part of frugal pup. Secure boot is enabled on this machine.

On my sdcard I installed the same OS as on my stick. On the stick I ran the initrd modules facility which installed the rtsx_pci and rtsx_pci_sdmmc modules to the initrd.gz. Unfortunately, the init script didn't get updated so I manually patched it with the diff in gyro's first post of the related initrdmodules topic.Once I got this sorted I proceeded to boot the card. I was able to reproduce the kernel panic. Completely different OS and kernel. Again for the record, the kernel is freshly compiled 4.19.125.

I also booted the stick with the patched initrd and the sdcard plugged in but no kernel panic. I only got the panic when booting off the sdcard.

Frankly, I don't understand it. There seem to be no syntax errors in the init code and it is a simple operation to grep the probedisk log and decide which way to proceed.It does seem though that the script decides that we should check if the card needs resizing so the error possibly comes from /sbin/resize_part, but that looks ok to me too. Works just fine on raspberry pi boards.

The only thing I can think of is to set a boot parameter to specify if a partition needs resizing. It does work, am booting from the sdcard right now.

Further thoughts appreciated.

gyro · Posted: Wed 10 Jun 2020, 12:24 Post subject:

gyro · Posted: Wed 10 Jun 2020, 13:19 Post subject:

Is it my late, late, late night stupidity, or is there a problem with '/sbin/resize_part' trying to actually resize the same partition that it's booting from.

gyro

bigpup · Joined: 11 Oct 2009 Posts: 13981 Location: S.C. USA

On my Hp Stream 14

I am booting from an emmc drive.
It is the internal drive for this computer.

I am using the 5.4.6 kernel that comes in ScPup64 20.01

Have to use a different older initrd.gz to get it to boot.

The initrd.gz in ScPup64 20.01 causes kernel panic.

This is the initrd.gz that is working OK.