Muppy 008.4c (final release)

[zgp152]

Updated network wizard to newest version without a hitch and my wireless is working perfectly.
...

This positive message tells that the driver can be installed to Muppy. Nice.

Could you pls report further for instance to wireless thread http://www.murga-linux.com/puppy/viewtopic.php?t=31522 what was your interface driver and whether you used encryption, WEP or WPA, and did the wizard store and recall your profile, with encryption key, MAC address etc.
Rgds
zgp152

[otropogo]

Have just quick erased a CDRW with TkDVD, then burned the Fat Free 2.16 ISO with Pburn. The burn seems to have completed properly, but I got no verification option.

The disk was automatically ejected, and I reinserted it to look at the files.

Then, when I tried to eject it,
MUT showed the device as unmounted (yet I could view the contents), but failed to respond to clicking the "eject" button

the desktop device icon gave the following response

Eject '/mnt/dvd'
umount: cannot umount /dev/dvd: Invalid argument
eject: unmount of `/dev/dvd' failed
eject failed

Done
There was one error.

and the "eject" button on the popup when closing the device, also failed to work.

It was only after I clicked on the "unmount" button in the close device popup, that the disk finally ejected.

I then tried to run the LiveCD on another machine, but Wakepup couldn't find it, although several other Puppy LiveCDs have booted fine on this machine a dozen times in the last 24 hours.

I came back to the PC with Muppy and reinserted the CD to have another look at it. On my first look, I'd just glanced at the file icons, and hadn't actually looked at the properties of the Puppy 2.16 Fat Free files.

Now, when I re-inserted this same CDR, things get even weirder:

1. The MUT window was still open from my previous activity, and when the disk was inserted, the only option it showd for the burner was "close", but clicking on it did nothing.

2. I couldn't shut down MUT using the "X" tab

3.when I tried to mount the CDRW by clicking on the burner desktop icon, the popup reads:

Mounting /mnt/dvd

and hangs

4. now the MUT window has gone completely blank -

5. I tried closing it from the taskbar, but this only closed the device icon popup. The taskbar shows no tab for MUT

6. I then minimized the MUT window, and it was reduced to an icon on the taskbar

7. when I restore it, it's still blanked out, an still can't be closed


8. I then tried reopening MUT from its desktop icon, and it showed the green popup for a second, then shut down.

NB: just now, some ten minutes or more after I clicked on its icon, MUT finally opened a second instance it showed it's normal window for a second, then closed, leaving a tab on the taskbar and the blank MUT window on the desktop.

The taskbar tab only offers to close MUT, not to kill it. And the close tab doesn't work. So MUT remains disabled.

9. I restarted X, with the CDRW still in the burner, and the blank MUT window and its taskbar icon were gone.

10. tried reopening MUT, and the green opening popup flashed, but no window opened.

I tried mounting the CDRW with the DVD icon, but it hung the same as before.

11. I tried "eject" and that failed too

12. I pushed the drive's eject button and that worked, then MUT immediately opened four windows, and the CDRW appared in ROX (but still showed as "unmounted" in MUT)

13. I closed the ROX window, and chose the "unmount" button

14. I then clicked on "mount" in MUT, and MUT finally showed the contents of the CDRW

15. I then tried to umount the CDRW in MUT, and first the MUT window went blank again, and immediately afterward, X closed, losing everything I'd been entering here.

16. I did get a chance to look at the properties of the Puppy files on the CDRW, and couldn't find any obvious problems in terms of byte counts.

17. Have now established that there IS something wrong with the FF 216 ISO burned by Pburn 2.0.3:

When I tried to boot it on my main desktop, I got the following error message:

Loading Initrd.gz isolinux disk error 01, AX=4200, drive 82
boot failed

I also established the the initial test machine can load Puppy from multisession written LiveCDs.

So my guess is that MUT's malfunction is definitely related to the files on the CDRW.

18. have no accessed the same CDRW unchanged with both Pmount and the burner icon, and both ways it mounted properly. There was no problem in unmounting it. Nothing hung, and nothing refused to close. So whatever the problem is with the way the disk was burned by Pburn 2.0.3, Pmount seems to be immune to it.

19. Finally, I tried opening the CDRW with MuppyQuickmountCD under Puppy 4.0, and had no problem there either...

I saved the Pburn burn log, but it turns out to be empty! Happily, I copied and pasted the text from the burn window, as with the erase window in TkDVD:

TkDVD CDRW quick erase

cdrecord blank=fast dev=/dev/dvd

cdrecord: Warning: Running on Linux-2.6.21.7
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '/dev/dvd'
devname: '/dev/dvd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Cdrecord-ProDVD-Clone 2.01.01a23 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling
Using libscg version 'schily-0.9'.
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-4081B'
Revision : 'A100'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Starting to write CD/DVD at speed 10 in real BLANK mode for single session.
Last chance to quit, starting real write in 9 seconds. 8 seconds. 7 seconds. 6 seconds. 5 seconds. 4 seconds. 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts.
Writing finished

Pburn ms ISO burn

cdrecord: Warning: Running on Linux-2.6.21.7
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATAPI:/dev/hdc'
devname: 'ATAPI:/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: dev=ATA: is preferred over dev=ATAPI:.
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
SCSI buffer size: 64512
Track 01: data 55 MB
Total size: 63 MB (06:16.28) = 28221 sectors
Lout start: 63 MB (06:18/21) = 28221 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 3
Reference speed: 6
Disk Is not unrestricted
Disk Is erasable
Disk sub type: High speed Rewritable (CAV) media (1)
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359848 (79:59/73)
1T speed low: 4 1T speed high: 10
2T speed low: 4 2T speed high: 0 (reserved val 6)
power mult factor: 1 5
recommended erase/write power: 5
A1 values: 24 1A D8
A2 values: 26 B2 4A
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.

Capacity Blklen/Sparesz. Type
0 2048 No Media Present or Unknown Capacity
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 331627
Starting to write CD/DVD at speed 10 in real TAO mode for multi session.
Last chance to quit, starting real write in 9 seconds. 8 seconds. 7 seconds. 6 seconds. 5 seconds. 4 seconds. 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Performing OPC...
Starting new track at sector: 0

Track 01: 0 of 55 MB written.
Track 01: 1 of 55 MB written (fifo 100%) [buf 100%] 0.7x.
....
Track 01: 55 of 55 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: Total bytes read/written: 57792512/57792512 (28219 sectors).
Writing time: 49.548s
Average write speed 7.6x.
Min drive buffer fill was 98%
Fixating...
Fixating time: 35.861s
cdrecord: fifo had 911 puts and 911 gets.
cdrecord: fifo was 0 times empty and 833 times full, min fill was 90%.

I suggest Muppy users upgrade to Pburn 2.0.9, where CDRW support has improved significantly, at least for DATA writing (I haven't tried to burn an ISO with it yet - maybe I"ll do that next...)

[MU]

otropogo

thanks for the suggestion.
Pburn is one of the programs with highest "update priority".
So 0084D will contain the newesst version.

general
Recently, I try to build a new version using the retro kernel from Puppy 409. 409 contains more wifi drivers.

I was able to build a Mini with all drivers included using a new vmlinuz, initrd.gz and some patches.
I later must try, to create a new zdrv_084.sfs from this version.

But before I do that, I will try to get Kernel 2.6.25.16 also to work.

This also will include the new network wizard.
Unfortunately, that one is a fork of the old wizard, that does not contain my localization patches.
So the localization must be added again

It will take some days to get all this working.

Mark

[otropogo]

otropogo

thanks for the suggestion.


Mark

You're welcome.

BTW I was editing my post one more time while you posted this comment. Suggest you review it again, particularly points #17 to 19

PS. Have now fast blanked (don't use complete blank until Zigbert has fixed it) the same CDRW with Pburn 2.0.9 and then reburned the Fat Free 2.16 Dillo ISO with Pburn 2.0.9.

I didn't notice anything different during the burn. IIRC, it actually ran faster than the defective burn of 2.0.3. But this one boots up fine. In fact I'm typing this post edit in Dillo using FF 2.16 (the post window is VERY small, and quotes and underlines, etc. don't work.)

Here's the log of the successful burn with Pburn 2.0.9 under Puppy 4.0:


###################################################
COMMAND:
###################################################

wodim -multi -tao -v dev=ATAPI:/dev/hdc driveropts=burnfree "/mnt/hda3/AllPups/fatFree301_216/fat-free-2.16-dillo.iso"

###################################################
OUTPUT:
###################################################
scsidev: 'ATAPI:/dev/hdc'
devname: 'ATAPI:/dev/hdc'
scsibus: -2 target: -2 lun: -2
WARNING: the ATAPI: method is considered deprecated on modern kernels!
Mapping device specification to ATA: method now.
To force the old ATAPI: method, replace ATAPI: with OLDATAPI:
Linux sg driver version: 3.5.27
Wodim version: 1.1.6
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 3 = CD-ROM XA mode 2
Driveropts: 'burnfree'
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-4081B'
Revision : 'A100'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x000A (CD-RW)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x001A (DVD+RW)
Profile: 0x001B (DVD+R)
Profile: 0x0010 (DVD-ROM)
Profile: 0x0009 (CD-R)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1204224 = 1176 KB
Drive DMA Speed: 11027 kB/s 62x CD 7x DVD
FIFO size : 4194304 = 4096 KB
Speed set to 1764 KB/s
Track 01: data 55 MB
Total size: 63 MB (06:16.28) = 28221 sectors
Lout start: 63 MB (06:18/21) = 28221 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 3
Reference speed: 6
Is not unrestricted
Is erasable
Disk sub type: High speed Rewritable (CAV) media (1)
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359848 (79:59/73)
1T speed low: 4 1T speed high: 10
2T speed low: 4 2T speed high: 0 (reserved val 6)
power mult factor: 1 5
recommended erase/write power: 5
A1 values: 24 1A D8
A2 values: 26 B2 4A
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 331627
Starting to write CD/DVD at speed 10.0 in real TAO mode for multi session.
Last chance to quit, starting real write in 4 seconds. 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0

Track 01: 0 of 55 MB written.
Track 01: 1 of 55 MB written (fifo 100%) [buf 100%] 0.8x.
...
Track 01: 55 of 55 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: Total bytes read/written: 57792512/57792512 (28219 sectors).
Writing time: 49.153s
Average write speed 7.7x.
Min drive buffer fill was 99%
Fixating...
Fixating time: 36.752s
wodim: fifo had 911 puts and 911 gets.
wodim: fifo was 0 times empty and 834 times full, min fill was 92%.

[MU]

otropogo

thanks for reporting your success!

-------------------
general

I also made progress, see the attached screenshot

Now I must find out, why no network modules are loaded, and why german umlaute are not visible at startup.

Mark

[MU]

I made a EXPERIMENTAL version of Muppy-Mini.
It seems to work on my system, but I made no intensive tests yet.
My ethernet card and soundcard are detected automatically, what is a good sign

It uses the new Kernel 2.6.25.16 from Puppy 4.1 rc (409).

Pburn was upgraded to 2.0.9, and the networkwizard replaced with the english only version from Dougal, network-wizard-oct-1st.

Note:
if you use addons_084.sfs with it, and the CF-Wizard runs, do NOT choose the propriatary Graficsdrivers from ATI or NVidia.
There are no matching Kernelmodules available yet for them.

Download:
ftp://ks301128.kimsufi.com/Muppy0084/0084-experiments/


The current version is "c3", that fixes issues with "c2".

EN = english
DE = german

The german version cannot display the characters äöüß at startup; if anyone knows a solution for that, please let me know.

I cannot guarantee, that everything works as in Puppy 4.1, as for Muppy, I created a new zmsy_084.sfs.
Puppy 4.1 no longer uses such an additional kernel file, but I want to keep it, to reduce memory usage.
But we now must test together, if that works reliable, too.

Mark

[Dpup]

Mark,

Installed Muppy Mini 008.4c (final release) USB boot on several laptops and desktops for tests, updated Network Wizard to Sep 25th that you posted. All work fine with my WPA2 TKIP wireless router, auto reconnects on boot from USB flash drive. Approx 30 seconds total from power on to wireless connected. The new release Network Wizard is much faster and enabled the auto wireless reconnect on boot.

Also tested 4.1rc which I understand has the same Sep 25th Network Wizard. It also works fine on the same computers.

Then I downloaded your experimental Muppy Mini... cannot detect any wireless... so I reinstalled the Network Wizard update of Sep 25th (which should already have been there), but still no networks detected. Am using ZyXEL and Airlink USB wireless that work well with Puppy 4.00, 4.1rc and a number of variants.

Any suggestions? I understand that this is all very early experimental and maybe too early.

Thanks,

Dpup

[MU]

Dpup,

please try two different things.

1.) click on the zmsy_084.sfs from the CD, to mount it.
then copy the folder:
/mnt/+mnt+home+muppy0084k2626+zmsy_084.sfs/lib/firmware
to:
/lib/

Reboot to check, if it works now.

2.) if 1.) has no success, do it again, but now copy everything in:
/mnt/+mnt+home+muppy0084k2626+zmsy_084.sfs/
to:
/

You can choose yes or no to overwrite existing files, that makes no difference.
+home+ can be also something like +sdb+.


Reboot again to check, if this works.

Depending on the result, I had to apply changes to how zmsy_084.sfs is used, or stop using it.

Mark

[Eyes-Only]

Salut Mon Cher Frere Mark!

Just wanted to post in quickly that I downloaded your Mini-Sys Mini over the weekend along with the addons.sfs file and have been really enjoying it with the Openbox/LXpanel desktop for now in a frugal install. You've REALLY done your homework on this one Mark!

Really seems great to be using a Linux system where I didn't need to do hardly ANY configurations whatsoever because 99% of the software I use is already there and ready to go. As if you've read my mind on what I needed and assembled it together!

On another note Mark: I'll try to answer your email soon. Sorry for taking so long. I'll explain why in the reply.

Best of success to you mon frere!

mfg/Amicalement,

jimmi
"L'Peau-Rouge"

[MU]

BUGFIX
I added a Servicepack to the new EXPERIMENTAL Mini "c2".
It might fix the network issues.
There was a wrong (old) /etc/networkmodules.
The modules have different names with the new Kernel.
I also applied a small fix, so that Opera should use Flash if you run the Mini without addons.

Download:
same folder as the Isos.

I also uploaded updated Isos "c3" !


Eyes-Only
many thanks for your encouragement
And as I stated before, no need to hurry

Mark

[Dpup]

MU

Tried the two patches and the service pack, in all cases the wireless device is detected, but reports no networks found.

Also notice an unusually long delay "loading kernels"

Dpup

[MU]

ok, then I must go and buy a new wlan-usb-stick tomorrow, it seems I lost mine. I was sent a wireless router I can use then.
Without a stick, I cannot check that no network was found, I only can check that modules are loaded

Thanks for testing it so far!

Mark

[Jim1911]

Mark,

Thank you for updating muppy to run on 4.1. I downloaded the c2 version and had the same problems with network detection on my Dell 8250 as noted above. I used a frugal installation and renamed my existing save files and muppy dir so that they would not be detected.

Then I downloaded the c3 version and had problems with it initially detecting network, sound card, and printer. Then I discovered that for some reason it needed a save file before they could be detected. After a reboot, I lost the network again and couldn't restore it.

I suspected some interference with existing files so I did another frugal install on a separate partition and was able to get a network connection after creating a save file. Running in it's own partition, so far it's running fine. I've loaded addons, kde, and gnome sfs files and have noted no problems other than those already noted with the regular muppy.

This is being sent from the new installation.

I believe that you have a winner with this one.

Jim

[MU]

Jim1911
great, thanks for your info!
Maybe an old zmsy_084.sfs was found by Puppy in another folder, with the old kernelmodules.
So installing to an own partition solved it, as Puppy searched there, first.
I just wonder, why a savefile is required, so that network works.
I'll buy the new wireless stick today, to check that.

Mark

[Jim1911]

Mark,

I've tried several times with c3 to set up a network prior to generating a save file with a frugal install on a dedicated partition with no success. I haven't noticed anything unusual on bootup. Possibly, it is picking up an older file from another partition. However, it seems to be stable and run fine after a save file is generated.

Pmount is the only application that I've discovered so far that doesn't work. Msg "You have unplugged these drives while they are still mounted: ...." Then Pmount must be closed. Muppy quickmount works fine.

Let me know if there is anything specific you want checked.

Jim

[MU]

Jim,
thanks for the offer, but I fear, I now must continue on my own.
I will try to explain the problem.

I bought two different wlan sticks today, so I can test it myself this weekend.
This will be a bit difficult to do via forum, as I must look directly at the logfiles to get an idea, what is wrong.

/tmp/ contains several, also /var/log/.
I expect to find a hint in them.

I solved the last bug, by running net-setup.sh from a consolewindow. I tried to load the "rt73" module for tests, as I have some experience with that one.
It told me, that "rt73" could not be found.
First I thought, there was an issue with the scripts /sbin/modprobe or /sbin/zdrvfind. They are different from Puppy 4.
I added some code to show me the content of variables, but found nothing that helped me. Then I examined /lib/modules/modules.dep.2.6.25.16, and found only "rt73usb", not "rt73".
So it was clear, that the modulenames changed with this the new kernel.
I finally "just" had to find, where those are used, what finally led me to /etc/networkmodules, that had to be updated.

The current issue hopefully will generate an error-message somewhere, that will give me an idea, where I have to search more detailed.
At moment I have no idea at all, so I depend on such messages, to be able to find out more.

--------------
thanks for the pmount info.
I think I must replace it with the one from Puppy 4.1, Barry has added several modifications for the new kernel.

Mark

[recycler]

Really enjoying Muppy and have been busy trying it on various machines. We have noticed a problem here that sometimes a window opens and the top of the window is hidden underneath the bar which has the 'start' button on. This is using the DVD version with the 'standard' window manager. Mostly it happens in Opera. Sometimes holding down the 'alt' key and moving the window works. Then you can see the X in the top right corner to close the window. Sometimes it happens right at the start upon first booting up. Then clicking on 'setup' and rerunning the xorgwizard to restart X is the only way I've found to get out of it. Chess works but after a minute or so CPU usage goes up to 100% and stays there. Small things. Those I show Muppy to like the contemporary look of it. I've been emailing screenshots to friends and family I love it so. Never done that with any program before Also like the 'preferred applications' option in the DVD version which allows me to easily choose my web browser and email program. Oh, one last thing. Had a problem which has only occured on two Dell Dimension desktops (Pentium4) where I install Muppy (DVD version) create a save file at shutdown and reboot but the save file is not found. First machine I gave up. The second machine I tried saving the save file a second time when the first one was not found after several reboots. This second save file was saved into the puppy084 folder rather than onto the home partition...and this one was found. Usually Muppy has been finding the save file on the second reboot. I use the first reboot to manually move it into the puppy084 folder. Something I found useful on Puppy 4 series is the option to change the foler where the save file goes. Helpful when putting several frugal installs into one partition.
Leon

[tlchost]

I made a EXPERIMENTAL version of Muppy-Mini.
It seems to work on my system, but I made no intensive tests yet.

One thing I noticed is that Wine in this version does not operate as it does in previous versions.

I can no longer simply click on the icon of a windows application and have it run. It would be nice to have it work as it did before, thus allowing the use of windows programs that do not require registry entries.

If you want to experiment, you can use http://portableapps.com/apps/utilities/keepass_portable.

Thom

[zgp152]

I wish to have Muppy distro on DVD but the save file and a minimum of other files on HD.

The next is otherwise good, but if DVD station is closed, Muppy starts always. I would like to keep the station closed. Muppy should appear in the menu and be launched from there. Puppy 4.0 is fully HD installed.

C:/Muppy currently contains save file, vmlinuz and initrd.gz. Windows is XP SP3.

######################################################
# GvR Sept 30th 2004
color black/cyan yellow/cyan
timeout=5
default=0

title Puppy Linux 4.00
rootnoverify (hd0,0)
kernel /puppy400/vmlinuz PMEDIA=idehd psubdir=puppy400
initrd /puppy400/initrd.gz
boot

title Muppy 008
rootnoverify (hd0,0)
kernel /Muppy/vmlinuz
initrd /Muppy/initrd.gz
boot

title Default Boot on HD 0
rootnoverify (hd0,0)
chainloader +1
boot
######################################################

How to finalize the menu.lst and the files on HD without putting 2 Gig on HD?

Rgds, Timo

[MU]

Jim1911

I bought 2 USB wlan sticks:
1.) AVM Fritz wlan USB stick
http://www.murga-linux.com/puppy/viewto ... 001#237001

2.) Linksys Compact Wireless G WUSB54GSC

For 1.) I had to compile modules on my own, see the link.

For 2.) It is not supported by Muppy original Kernel. Ndiswrapper is told to work, but I did not try that.
I tested it in Muppy0084c3-k2.6.25.16.
I have it installed frugal.
Ran it without savefile.
The stick was plugged in.
All modules were loaded correctly.
I ran the network-wizard, scanned the network, it found my "muppy" ESSID (the wireless router).
I clicked on "use this profile", then on "auto-dhcp".
Voila, I'm online.

----------
So why does it not work for you without savefile?
- I must test, to run from CD. Maybe zmsy_084.sfs is not found then?
I'll do it tomorrow, too tired now.

- you could do this:
run without savefile.
Type in a consolewindow:

Code: Select all

lsmod >/root/test.txt
gzip /root/test.txt
dmesg  >/root/test2.txt
gzip /root/test2.txt

Then please attach here the files /root/test.txt.gz and /root/test2.txt.gz.

Then boot with your working system (with savefile).
Do the same procedure again, please.

Maybe I find a hint, if I compare your files.

Thanks very much for testing so carefully

Mark