ScPup & ScPup64 - Slackware Current based Woof-CE pups

[bigpup]

Hi bigpup,

Compiled a driver in scpup64 kernel 5.4.6 from sources at https://github.com/mid-kid/r8822be

I stuck it here http://ibm-pc.org/puppy/scpup64/k5.4.6/ ... r8822be.ko
It needs firmware rtl8822befw.bin

No idea if it will work as I don't have a device with that chipset.

Thanks for compiling the driver!!
I just have not tried using it, yet

[gyro]

Do you know what kernel config is needed?

While the kernel panic issue does not seem to be an "mmc module issue", there is an "mmc module issue" in that "01micko" had to resort to using the 'initrdmdules' utility and the 'initrdmdules' patch to the 'init' script to do his tests.

A place to start with the "mmc module issue" would be to recompile the kernel with a modified 'DOTconfig':
The basic idea is; In the section headed "# MMC/SD/SDIO Host Controller Drivers", replace every "=m" with "=y".

Although this could be slightly modified based on BK's 'DOTconfig-5.4.12'.

BK's 'DOTconfig-5.4.12' leaves the following as modules:

Code: Select all

CONFIG_MMC_REALTEK_PCI=m
CONFIG_MMC_REALTEK_USB=m

At least 1 of these represents a moudle already mentioned in this forum topic, so I suggest changing these to "=y".

BK's 'DOTconfig-5.4.12' also leaves the following unset:

Code: Select all

# CONFIG_MMC_RICOH_MMC is not set
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_ALCOR is not set
# CONFIG_MMC_SPI is not set

So probably these could be left unset.

gyro

[gyro]

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.

Obviously the drivers for your emmc haredware are builtin to the default kernel, others are not so fortunate.

I have attached a test 'init' script that contains the line:

Code: Select all

#  /sbin/resize_part $FS

so it will never try to do the actual partition resize.
The idea is to identify if the issue is related to the code in the actual 'init' script or the code in '/sbin/resize_part'.
Could you please, replace the 'init' script in the release 'initrd.gz' with this test 'init' script, and reboot using this "patched" 'initrd.gz'.

gyro

[gyro]

I've attached another test 'init' script.

This one uses a different method of parsing the output from "fdisk -l".

gyro

[peebee]

A place to start with the "mmc module issue" would be to recompile the kernel with a modified 'DOTconfig':

64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic. ... 96#1060596

[bigpup]

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.

Obviously the drivers for your emmc haredware are builtin to the default kernel, others are not so fortunate.

I have attached a test 'init' script that contains the line:

Code: Select all

#  /sbin/resize_part $FS

so it will never try to do the actual partition resize.
The idea is to identify if the issue is related to the code in the actual 'init' script or the code in '/sbin/resize_part'.
Could you please, replace the 'init' script in the release 'initrd.gz' with this test 'init' script, and reboot using this "patched" 'initrd.gz'.

gyro

Did not boot.
Only got to point of loading the kernel and stopped,

No kernel panic, but stopped with only something looking like the process stopped.

[bigpup]

I've attached another test 'init' script.

This one uses a different method of parsing the output from "fdisk -l".

gyro

No boot.
Stopped at loading kernel.
No kernel panic, but stopped with only something looking like the process stopped.

[gyro]

@bigpup,
Thanks for testing.
Unfortunately the result is a little confusing. I had expected that either of those 'init' scripts would have either worked, or produced the kernel panic.

gyro

[gyro]

64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic. ... 96#1060596

I've had a look at this kernel package, while it should solve the "mmc module issue" for my Lenovo, I don't think it will do the same for "01micko"s test machine, I think it might also need:

Code: Select all

CONFIG_MISC_RTSX_PCI=y
CONFIG_MMC_REALTEK_PCI=y

I intend to actually try this new kernel on my Lenovo, as soon as I can.

Later edit: Your kernel 5.7.2 worked fine on my Lenovo, both the internal mmc device (mmcblk1) and the mmc sdcard (mmcblk2) were seen by the 'init' script wihout any kernel modules being involved.

gyro

[gyro]

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.

Does it work both, when you specify that a partition needs resizing, and when you don't?

gyro

[mash]

@gyro

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

[bigpup]

@gyro

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

The same for me.
I was not sure that was actually a prompt it stopped at.
So, I just said stopped.

[01micko]

@bigpup and @mash.. just before the prompt doesn't it say "To save debug info to a partition, type 'debugsave'" '

Do it and post the results (just zip up the resulting directory on your drive)

DISCLAIMER: probably doesn't support nvme type drives

[01micko]

@gyro, I didn't test with the presize param set, I would expect to get the kernel panic. I'll attach the init I used and @mash and @bigpup can test it too, without changing boot options.

A thought did occur to me. If the mmc/sd/whatever drive is formatted gpt then fdisk will fail, probably critically.

[gyro]

A thought did occur to me. If the mmc/sd/whatever drive is formatted gpt then fdisk will fail, probably critically.

Hmmm...it could be that the code in 'init' is working too well, after your commit.
Maybe folk who have a problem, also have an "mmcblk0" that can be seen by the 'init' script.

At least you have your own test bed, unfortunately my Lenovo, won't even recognise the micro SD card as a boot device, even though I can successfully boot from it when it is inserted in a usb stick adapter and plug it in as a usb stick.

gyro

[gyro]

64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic. ... 96#1060596

I just compiled kernel 5.4.46 in ScPup64 with DOTconfig changes.
After the compile, I noticed that the produced DOTconfig contained an additional configuration set,

Code: Select all

CONFIG_MISC_RTSX=y

I have attached 'DOTconfig-5.4.46-120620'.
I've also attached 'mmc.diff' which shows the changes that I now consider to be those required for mmc support, well at least a starting point that is better than our current kernel configs.
Using these changes, the resultant kernel should support "01micko"s Realtek mmc card reader, without any need to use 'initrdmodules',
as should my new 64-bit kernel 5.4.46.

gyro

[gyro]

I've uploaded 'huge-5.4.46-gyro-64.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup64.

This kernel package does not contain any firmware, it requires the presence of an fdrv...sfs.

gryo

[gyro]

I've uploaded 'huge-4.14.184-gyro-pae.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup.

This kernel package does not contain any firmware, it requires the presence of an fdrv...sfs.

This kernel provides much improved mmc support, the equivalent of 'huge-5.4.46-gyro-64.tar.bz2'.

Note that the kernel config variables required for Realtek support are slightly different between kernel v4 and kernel v5.

gyro

[bigpup]

@bigpup and @mash.. just before the prompt doesn't it say "To save debug info to a partition, type 'debugsave'" '

Do it and post the results (just zip up the resulting directory on your drive)

DISCLAIMER: probably doesn't support nvme type drives

Using the initrd.gz that only boots to a prompt.
I see this:
Loading vmlinuz
Loading initrd.gz
stops at a prompt

Type debugsave
Get a bunch of errors about stuff not being found.
Ends with no partitions found.
So, I cannot provide debugsave info.

I tried this with the original initrd.gz that is in ScPup64 20.01.
This boots to point of kernel loading, but stops with bunch of error messages and kernel panic.
No prompt provided.
So, cannot provide debugsave.

Bionicpup64 8.0 boots OK.

ScPup64 20.01 using the the initrd.gz from ScPup64 19.09+0-uefi-T.iso boots OK.

The boot loader, is the UEFI boot loader, installed by Frugalpup Installer.
Secure boot is enabled in the UEFI bios.

This is the drive I am using.

[01micko]

@bigpup if you plug in a usb stick you might be able to save the debug logs on that.

Also try @gyro's kernel and init script. (edit.. gyro's init wont work.. see below for explanation)

Your drive is indicated as gpt via that screen shot which explains the kernel panic as fdisk will error because it only supports mbr so init stops and boot can't go on which confirms my initial hunch.

The problem I now face is that I either have to do an early init check on the partition type or find a utility other than fdisk to check the partition sizes in the init function check_resize_part().