Phil_54 wrote: Tue Jan 10, 2023 12:10 pm
Neither booted, but hung after initrd line. Initially I did not copy the grub_config.txt file as I thought it irrelevant, but because it is in the stanza it gave an error about missing file. No error thrown up after putting grub_config.txt in.
I don´t have another sdcard to try pristine.
Ventoy and Ventoy/SG2D fails to boot rc 6.1 and beta25. (SG2D doesn´t list them anywhere I could see). My ventoy/SG2D works very well on standard distro iso's.
It also fails on a debiandog iso that I have.
Thanks for trying Phil. The grub_config.txt file, by the way, is simply used as a 'marker' file in that boot stanza; isn't actually used in the boot itself (it is just a txt file for humans to read). By marker file, I just mean a way to tell grub4dos it is at the relevant folder (I noticed the need for that when reading grub4dos config file needs when using LABEL method - prior to discovering that I didn't even know grub4dos could handle that case).
Pity I don't have a machine like yours to test, but I agree from your tests with your opinion that something about the kernel (or more likely the modules from that kernel used inside the intird.gz) isn't satisfactory for your machine. You haven't wasted any of my time; rather you led me to notice that modules for sdcard booting were missing. Prior to the fix I then made, rc6.1 would not have been able to boot on my old HP 2560p laptop either, but it can now.
In summary, no waste of time involved at all, and maybe still just a module short of working on your machine, or maybe just not suitable for your computer afterall. The fact it works (Ventoy and all) with many other distros suggests to me it could be made to work with Void kernel too. If you don't mind, there is one more test we could do, which is to use a much bigger initrd.gz that includes all the modules that Void Linux provides by default. That is not hard for me to build so I'll do so anyway since can always later be tried on anyone's computer that is having similar difficulties. Worth a try I'd say and more so since if it works then it becomes easier to track down what the difference is. Of course, it could be a firmware issue, which would be the last thing I'd try (Void Linux official firmware is pretty huge). Actually, I doubt it is firmware, per se, since the beta25 release came with same firmware as 6.1 as far as I recall.
I was hoping to re-download the linux kernel 6.1 from Void along with its modules, but unfortunately I note that 3 hours ago Void Linux upgraded it to a slightly later version so the modules for that newer release won't do for KLV rc6.1 release. But I'm hoping (and think it is likely) that 00modules.sfs contains all the modules that were available for KLV rc6.1 and I'll simply shove a copy of all of them into the initrd.gz. If that doesn't work on your machine, I guess we have to give up on this release! 
Actually, it is clear from your previous tests you know what you are doing so, though I will build a copy, I'll tell you the steps how to do it here:
1. In the directory where you have a frugal install of latest KLV rc6.1, open a terminal (for these instructions I refer to this as 'terminal 1') and fetch a copy of the shell script modify_initrd_gz.sh into your KLV rc6.1 frugal install directory, which can be done by using command:
Code: Select all
wget -c https://owncloud.rockedge.org/index.php/s/HRZhsnouSm3Gpf3/download -O modify_initrd_gz.sh && chmod +x modify_initrd_gz.sh
2. Now run that script using command:
To produce a decompressed version of initrd.gz in its own folder named "initrd_decompressed". The procedure does not delete the original initrd.gz.
Do not close that terminal (terminal 1) or type any new commands into it thereafter till we have modifed the contents of the that initrd_decompressed directory that has been automatically been created in your frugal install directory.
3. What we are going to do now is simply go into that initrd_decompressed directory, using your filemanager to location initrd_decompressed/usr/lib/modules and delete the contents of that modules directory (6_0_12_1 or whatever version it is) because we are going to replace it with a full set of same kernel version modules prior to trying a reboot with some hope of success(?).
4. Hopefully (and I think) the full set of kernel modules are in 00modulesXXX.sfs, so assuming you are on a different KLV host or a Puppy system or a DebianDog when doing this modification/development work, just clicking in your filemanager on 00modulesXXX.sfs should open it up in a separate filemanager window; in that opened up result you go to usr/lib/modules and there you should see the 6.0_12_1 (or whatever version it is for current supplied kernel) subdirectory.. Continuing to use your file manager to do this, simply copy that 6.0_12_1 subdirectory (or whatever version number it has) into your initrd_decompressed/usr/lib/modules directory.
5. Finally, in the first terminal (the one we called terminal 1), simply enter the word: exit
and wait for a bit whilst the initrd_decompressed directory gets automatically compressed for you again.
6. Actually, there is one last simple step prior to trying to boot the system. The newly made full-module-set initrd.gz has been created with a datestamp in its name. You need to disable (meaning rename) the original initrd.gz and then rename the new datestamp version simply initrd.gz so that grub will find it. Now reboot, and good luck...
I would really like to get this one to work if possible, since same full module set initrd.gz might well then work for others, such as Clarity after which we may well be able to track down which extra modules made the difference.
Not wanting to be too optimistic, above might well not work... but worth a try maybe...
