(old)Puppy Linux Discussion Forum

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

CONFIG_MISC_RTSX=y

01micko wrote:@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

bigpup wrote:OK.

But Booting Bionicpup64 8.0
I see information about e2fsck doing a check and giving the results of that check.
e2fsck 1.44.1 (24-Mar-2018)
The boot process continues as a normal boot to working desktop.

Same e2fsck checking drive information, with results.
Booting ScPup64 20.01, using the the initrd.gz from ScPup64 19.09+0-uefi-T.iso.
e2fsck 1.45.6 (20-Mar-2020)
It also boots OK.

--- init	2020-05-31 11:46:29.210999690 +1000
+++ /root/spot/init	2020-06-13 07:22:03.702212647 +1000
@@ -667,6 +667,7 @@ umount_unneeded() {
 
 check_resize_part() { #must be fast, no partitions can be mounted, can't work out pupmode at this stage
  DEVICE=/dev/mmcblk0 # sd card only for now
+ fdisk -l $DEVICE | grep -qm1 "using GPT" && return
  grep "$DEVICE" /tmp/probedisk.log | grep -q 'card' || return
  FS=`grep "$DEVICE" /tmp/probepart.log | tail -n1 | cut -f 2 -d '|'`
  case $FS in

fdisk supports GPT since util-linux 2.23

01micko wrote:I have an init script for you to try.

For the record it is a simple check with fdisk (which won't error, just skip the offending code) to see if we have a GPT partition.

It works before any of the probedisk log checks.

I'll attached the file as a tar. Untar and insert it into your initrd-expanded overwriting the init script and repack the initrd.gz

01micko wrote: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 an initrd.gz for scpup64

http://01micko.com/packages/initrd.gz

Code: Select all

# md5sum initrd.gz 
c68615601ab676ade73a3c0eab774cba  initrd.gz

Make sure to change kernels to gyros, however you may need a wireless driver compiled, but it is needed for a thorough test.

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 an initrd.gz for scpup64

http://01micko.com/packages/initrd.gz

Code:
# md5sum initrd.gz
c68615601ab676ade73a3c0eab774cba initrd.gz


Make sure to change kernels to gyros, however you may need a wireless driver compiled, but it is needed for a thorough test.

In the meantime, I found the source of @mash 's bug!

A stupid assumption grepping for GB! Embarassed I've put in code for KB|MB|GB and that will fix it. I tested on a 8GB card which in fdisk shows up at ~8000MB. I tested with KB too because (and I don't know, but it doesn't hurt to add) smaller cards do have the possibility I guess as showing up in KB.

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

mash wrote:This init works for me too. Either with gyro's or with original lxpup kernel.

Network controller
• Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter
• VendorID=10ec DeviceID=b822
Realtek RTLB872 Cartier 2x2 ac / BT4.2 M.2
• Kernel Driver=r8822be
• Kernel Module=rtwpci, r8822be