Puppy Linux Discussion Forum

VM tests, thus far: ISO file boots to desktop while USB booting does not.
Easy to replicate: Here's the VM stanza.

qemu-system-x86_64 -name "QP64 vRC8 ISO from USB" -enable-kvm -vga cirrus -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime /dev/sdc

You are using a video card of the '90s. Have you already tried with another video driver? I mainly use virtio on my VMs.

-vga [std|cirrus|vmware|qxl|xenfb|tcx|cg3|virtio|none]

VGA and other display devices in qemu

Whoa! This QP64 vRC8 just booted via SG2D not touching anything at QP's boot menu (allowed it to default on its own).

I am at desktop with this QEMU stanza (Notice the video difference):

qemu-system-x86_64 -name "QP64 vRC8 ISO from Ventoy" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime /dev/sdc

QuickPup64 24.01 RC9 released

Changes:
* Linux kernel 6.9.5
* Fix VPN connections
* Easyeffects replaced pulseaudio-equalizer

Download: https://1drv.ms/u/s!As14nV96TZw0ggMuW_o ... i?e=24bIVE
MD5 Checksum: 092743891dd7f4806cf3c3b671abbdb8

Hi @one

one wrote: ↑Tue Dec 05, 2023 10:55 am

Hi @Clarity ... Attached savespec, where 'Ventoy' is the label of the first partition (ext3). ...

In review of this post from you, I should have offered this.

There is nothing wrong with what you have, BUT, for me, as you may have notice in some/many of my past posting, I suggest to never place any forum's persistence on a USB. Too many issues to cover in a post, here and I do not want to derail the good work @mistfire offers us.

Just a note (in my case). Create a partition on a system drive if space is available and keep ALL of your forum's persistence for all the distros you boot in that system drive partition. To me, our sessions is the MOST important file-folder outside of the ISO files. And we benefit from the integrity and consistency of your system drive.

Just a note.

Booting Results Testings

Bare Metal (Using a Lenovo Mini M90n:)

• Ventoy without boot parms additions - boots to desktop. As expected for current WoofCE PUPs, does not use the SAVESPEC file for directing persistence at shutdown..

• Ventoy with PSAVE parm - boots to desktop. UNexpected does not use the PSAVE info for directing persistence at shutdown.

• SG2D - booting errors out and drops to GRUB prompt no matter which menu stanza selected. The 'debug' file is attached, below.

Booting Results Testings

QEMU VMs

• ISO file - boots to desktop. All expected behavior works including providing persistence at shutdown as prescribed in SAVESPEC file.

• Ventoy USB launch of ISO file - does not get to desktop. Stops at QP64's console. "xorgwizard" is no help to get to the desktop. Multiple vga parms were tested.

  

  No desktop via Ventoy USB in a VM

  Wontboot via USB in VM(2).jpg (45.42 KiB) Viewed 368 times

• SG2D USB launch of ISO file - boots to desktop. All expected behavior works including providing persistence at shutdown as prescribed in SAVESPEC file.

QEMU Stanzas

• Via ISO file direct

  Code: Select all

  # qemu-system-x86_64 -name "QP64 vRC9 ISO file" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -cdrom quickpup64_24.01-rc-9.iso

• Via USB

  Code: Select all

  qemu-system-x86_64 -name "QP64 vRC9 ISO from Ventoy or SG2D USB" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime /dev/sdc

Can not install any package with the package manager, it displays messages "package no available". refreshing database do not help. Is something wrong with mirrors? How can I fix this?

mikolaj_q wrote: ↑Thu Jun 27, 2024 8:28 am

Can not install any package with the package manager, it displays messages "package no available". refreshing database do not help. Is something wrong with mirrors? How can I fix this?

Check your internet connection first. I tested Quickpup64 on a VM with active connection, the PPM works fine

Network connection is OK. Packages updater works, but packages manager unfortunetaly do not like at screenshot.
Any idea how can i fix this?

mikolaj_q wrote: ↑Thu Jun 27, 2024 12:58 pm

Network connection is OK. Packages updater works, but packages manager unfortunetaly do not like at screenshot.
Any idea how can i fix this?

What repo did you select on PPM?

UPDATE: It turns out that slackel repo does not update the package database against upstream slackware-current. To fix this problem just edit /var/packages/DISTRO_COMPAT_REPOS file to prioritize the upstream slackware repo

Sorry for being a noob but could you be more specific which line should I move to the top of the list?

mikolaj_q wrote: ↑Fri Jun 28, 2024 10:24 am

Sorry for being a noob but could you be more specific which line should I move to the top of the list?

If you are noob, the easiest way to was look that package in pkgs.org select the package under Slackware category. Copy the download URL. Paste on the browser the press enter key

Update: Slackel repo database was finally updated. Just update the package database and it will just works

Thanks