Puppy Linux Discussion Forum

These guides might be helpful to some users:

A hack to run Optimus with nvidia-xrun on Void based systems:
https://ubh.sh/posts/optimus-void/

Bumblebee method:
https://github.com/Bumblebee-Project/Bumblebee/wiki/

Ironhide method (Ubuntu only branch from original creator of Bumblebee):
https ...

@AlexOceanic glad to see you have gotten your PC to allow the behavior you are seeing. I apologize to you ofr NOT going forward with my commitment BECAUSE I was suspecting hardware issues over the software steps and was trying to play with UEFI settings on my old PCs to arrive at what you were ...

Hi All

Can anyone see any obvious blunders in the below attempt to install my Nvidia 540M driver in KLV RC12 please?

Happy to post this in Void or Arch forums if more appropriate :thumbup2:

These are the steps I've taken so far just in case anyone has any initial thoughts or could point me to ...

Well I'm glad I was sitting down just then because KLV just booted properly and save persistence is confirmed!!! :thumbup:

All I did was:

- Enabled then disabled UEFI boot (gave a "not secure boot" error on booting)
- Disabled then re-enabled Legacy Boot Support (just skipped USB and went to the ...

Have you checked the klv iso is on usb stick in BOOTISOS? And correct size. Can you write files ok to that sdb1 usb stick partition? I'm wondering if the usb stick is faulty and maybe read only?
Yes the KLV ISO is in the BOOTISOS directory
Size of original and copied file match at 811,718,656 ...

I will do the whole thing from scratch using latest Ventoy which is version 1.0.88. Please don't use old versions of Ventoy - who knows what bugs are in these...

Steps:

1. Making a bootable Ventoy usb stick.

Per: https://www.ventoy.net/en/doc_start.html

For Linux - CLI mode
Download the ...

hi
I have been standing back pondering what is happening by observing these recent comments.

This is my Ventoy disk list on ! of 3 pages of ISO files in the BOOTISOS folder. I will give more detail as I am finding some different behavior in booting my Ventoy USB via QEMU without a Persistence ...

... BOOTISOSis empty (1 item, 0 bytes) ??? I have NO files that has 0 content. My Ventoy partition looks like this. And as you can see why my earlier picture of a screen from my Ventoy boot show some of this content.Ventoy-KLV test in QEMU(3).jpg


The BOOTISOS directory previously had 0 bytes ...

Look in BOOTISOS usb directory. Is KLV iso in there? What size is it? If necessary do:

md5sum KLV-airedale-rcX.iso and compare with what it's md5sum is supposed to be in case your copy corrupted it.


OK so I put the KLV ISO inside the BOOTISOS directory (apologies - can't believe that rooky ...

Look in BOOTISOS usb directory. Is KLV iso in there? What size is it? If necessary do:

md5sum KLV-airedale-rcX.iso and compare with what it's md5sum is supposed to be in case your copy corrupted it.


BOOTISOSis empty (1 item, 0 bytes)

I ran the md5sum from terminal but not sure what to compare ...

Actually, QEMU isn't alone in using that menu.lst.

You would also get that menu your test shows if booting KLV after writing it's hybrid iso image to a usb stick with dd or similar image writing utility. But then you are not booting via special Ventoy image. My request and help was for Ventoy ...

Actually, QEMU isn't alone in using that menu.lst.

You would also get that menu your test shows if booting KLV after writing it's hybrid iso image to a usb stick with dd or similar image writing utility.


Could you expand on what you mean by that please?

I'm simply using the default Kali file ...

I don't know what is going on on your system..
The menu your attached images are showing is not the menu Ventoy shows for me.
Rather, what your system is finding and displaying is the menu KLV presents for QEMU, which h is not going to work for Ventoy booting...
Clarity should be able to confirm ...

[bYour only job is to:[/b]
1. Make sure to use LABEL "Ventoy" on that partition.
2. Make a directory called "BOOTISOS" on that same ext4 formatted partition.
3. Put your KLV-Airedale iso into that BOOTISOS directory.
4. Boot the resulting Ventoy usb stick and choose menu option 3 or 4 from KLV ...

Error messages displayed for items 10 and 11:

Your only job is to:
1. Make sure to use LABEL "Ventoy" on that partition.
2. Make a directory called "BOOTISOS" on that same ext4 formatted partition.
3. Put your KLV-Airedale iso into that BOOTISOS directory.
4. Boot the resulting Ventoy usb stick and choose menu option:

menuentry "KLV ...

Your only job is to:
1. Make sure to use LABEL "Ventoy" on that partition.
2. Make a directory called "BOOTISOS" on that same ext4 formatted partition.
3. Put your KLV-Airedale iso into that BOOTISOS directory.
4. Boot the resulting Ventoy usb stick and choose menu option:

a. menuentry "KLV ...

Hello @AlexOceanic

I read over your work and see multiple attempts with varied configurations of your PC. Check your PM, soon, as I am going to give you access to an image file that I know boots F96 AND KLV.
Reason: Want to see if we can narrow down your efforts determining if the problem is ...

Check this KL-related information revarding its use with Ventoy. Done this way, no user work is required to get w_changes=RAM2 save on demand mode working. It just does. If it doesnt that would be a different kind of problem such as failing hardware or missing firmware:

https://forum.puppylinux ...

There is no Kennel Linux installer programs fully formed and coded yet. Lots of room for development on this front.


Ah ok - I guess KLV and the kennel distro's are too different from Puppy to use an easily amended version of Puppy's installer perhaps?

It seems AntiX is able to install itself ...

1st paragraph
I assume you placed those ISO files in the BOOTISOS folder you created on Ventoy USB partition #1... Correct ???
If by "BOOTISO folder" you mean the sdb1 exfat Ventoy partition with "boot" flag (as opposed to the sdb2 fat16 VTOYEFI partition with "esp" flag) then yes - I copy ...

Check this KL-related information revarding its use with Ventoy. Done this way, no user work is required to get w_changes=RAM2 save on demand mode working. It just does. If it doesnt that would be a different kind of problem such as failing hardware or missing firmware:

https://forum.puppylinux ...

OK, I see that yu are using Ventoy's utility v63. That's OK, for forum distros, but, for Fedora, I wonder if you should UPDATE your utility to the latest Ventoy...now at v88.

If so and you run the latest Ventoy, it will offer the same Install or UPDATE option. UPDATE will retain all the prior ...

rockedge

Just to say, after I'm up and running on KLV, I'm happy to update the name of this thread to something more appropriate like "Diagnosing intermittent usb boot/nic issues - it was nearby magnets!!!" as not sure this will be useful to anyone with questions about using KLV although there's ...

Please see responses in line/bold below:


Something interesting is going on with your hardware....maybe.

Reason: I see a GParted which seems that the creation process or some action (hardware/software) erased the partition #1 of that USB, 'sdb'. Is the GParted you are using old, maybe?
I am ...

... I thought I could simply delete the Fed partitions on the HDD and then install a new OS with GRUB in its place that would auto detect Win7 and create boot entries on its menu for Win7 and the new OS ... GRUB2, from my experiences does this automatically.

I you want to spare yourself some ...

... I thought I could simply delete the Fed partitions on the HDD and then install a new OS with GRUB in its place that would auto detect Win7 and create boot entries on its menu for Win7 and the new OS ... GRUB2, from my experiences does this automatically.

I you want to spare yourself some ...

I've nothing myself really to add to my previous comments Alex. You just need to keep trying and hope someone sees something they can help with if you run into problems. There are so many ways to do thing.

I suppose one comment is that KLV w_changes=RAM2 mode is likely not working because you are ...

I think the main point is that dual boot with Windows isn't a straight forward undertaking.

Also it is difficult for you to get across exactly how your system is organized and where are what any existing grub2 components remain.

Best to read the related threads I gave and try whatever best suits ...

I think the main point is that dual boot with Windows isn't a straight forward undertaking.

Agreed - I thought I could simply delete the Fed partitions on the HDD and then install a new OS with GRUB in its place that would auto detect Win7 and create boot entries on its menu for Win7 and the new ...