Bare-metal testing done using same process steps identified in VM testing.
All of what was explained, seen in the VM, exist in the bare-metal tests...no differences.
Moderator: Forum moderators
Bare-metal testing done using same process steps identified in VM testing.
All of what was explained, seen in the VM, exist in the bare-metal tests...no differences.
Clarity wrote: Wed Dec 13, 2023 3:40 amMinor Questions
What command/utility indicates Wayland operations in effect?
Is the Desktop>"Settings Manager" the replacement for the older Control Panel? If so, when its window opens on desktop should it read Settings Manager vs just 'Settings'?
Is there a summary setup utility similar to FirstRUN available?
@Clarity
Nothing at this moment. Just a preparation for Wayland
I made some modifications on the desktop files of Puppy core application in order to make it visible on XFCE Settings Manager which acts as Control Panel. XFCE Settings Manager reads a special category in order to make it visible to the Settings Manager
Yes but it is not enable yet.
What is your neighbor computer? Linux or Windows?
Both types of SMB servers
Since @01micko introduced this in his SAMBA packaging, it doesn't matter in any of my testings from the past. The command finds all on the LAN.
I did note with a recent PUP or DOG that if you have a local SAMBA server active, say via the SSM utility, it will report that too along with the other LAN SMB servers.
Hope this is helpful.
P.S. I noticed this 'findsmb' issue on bare-metal on local LAN.
Clarity wrote: Wed Dec 13, 2023 12:24 pmThe SSM's window looks like this on both VM and bare-metal.QP64vRC8 via SG2D(2).jpg
I finally fixed that error. For now here is the workaround
BTW: This has happened also on other apps, but cannot tell you which of them right now.
FYI
This request is for anyone with an nVidea video card.
HOW to turn on nvidia support vesus OOTB Vesa/Nouveau?
Clarity wrote: Thu Dec 14, 2023 11:56 pmThis request is for anyone with an nVidea video card.
HOW to turn on nvidia support vesus OOTB Vesa/Nouveau?
You may look on these wikis regarding using official nVidia linux drivers.
https://wiki.archlinux.org/title/NVIDIA
https://wiki.gentoo.org/wiki/NVIDIA
Install MTPaint from the PPM repository version 3.40 in "QuickPup64 23.01 RC8" but when I executed it I asked for the libopenjpg.so.5 . So I made the pet libopenjpg.so.5.pet and there was luck and worked at the first.
QuickPup64 24.01 RC1 released:
Changes:
Download: https://drive.google.com/file/d/1pcsnzJ ... qqBJU86twD
MD5 Checksum: 6d03e77a5097a055bef4f15c1b5f8c71
Including Bare-Metal via SG2D this PUP is booting to desktop, can update, and powers down without issues.
Note: I have not had a chance to check if QP64 picks up his prior session without user intervention of boot. (In other words, when ISO is launched no user Menu stanza interruption. thus the PUP finds his session as he boots based on the directions in the SAVESPEC file.)
And, when that is verified, I will also test to check to verify QP64 will boot via Ventoy USB. ... Later
Update from prior post. Testing for QP64 v2401 SAVESPEC processing for session management as well as some desktop operations.
Launched ISO file, pristine, from SG2D to desktop, made initial tailoring and when to shutdown to save. I am using a different modern PC (2019 Intel) for this test.
Configuration
8GB
i5 Intel
SG2D USB with ISO files
4K TV as monitor
SAVESPEC file present in folder along with ISO files
Finding
Allowed QP64 v2401 Menu for a default boot to desktop
As this is a pristine boot with NO prior sessions on the Persistence drive, the First-RUN did not present itself as expected on desktop with WoofCE PUPs
AT desktop, minor changes to system
Shutdown
The system indicates matching drive (from SAVESPEC), it is NOT matching the folder for placement of the Session.
This required a manual change to add "/Sessions" to the location for saving (this is specified in the SAVESPEC). This is a bug as the path for saving needs to match SAVESPEC directions). SAVESPEC contains
Code: Select all
SS_ID='Persistence'
SS_DIR='/Sessions'
SS_MEDIA='atahd'
Thus path offered should have been "/Sessions/QuickP..."
This is important as the location, upon reboot, that the PUP is to look for prior session is what is pointed to by SAVESPEC.
Additional findings
Upon reboot, taking the defaults at boot-time as before the system boots finding its prior session to desktop without issue.
This time I took the desktop's offer to update the system. Updates complete with a final message that "Pipewire" was installed! I see, also in the menu, you've included 'Helvum' for visualization of pipewire connections in this version of QP64.
PrtScrn key does NOT work requiring a hunt for an app to capture screen.
SAMBA Simple Management works
'findsmb' cli command does not show LAN units that are sharing content
Thunar's 'Browse Network' does not show LAN units that are sharing content
Added @ETP's "Get Latest Chrome Version v15" PET to install Chrome. Chrome installed from QP64's Internet Menu section
There is no "default image editor" when you right click on an image and select the option
Used PPM to install QEMU v802. But this errror results.
Question: should this be using python3?
.
PPM locks up reqiring to kill it
Clarity wrote: Wed Jan 31, 2024 8:58 am...
And, when that is verified, I will also test to check to verify QP64 will boot via Ventoy USB.
Launched QP64 v2401 ISO file from Ventoy USB on bare-metal. System boots to desktop, but, as with all the other WoofCE PUPs, it is NOT using the SAVESPEC file's contents. Further, this phenom also will not allow the PUP to save the session in a folder on the Persistence partition.
As reported in other threads when testing WoofCE PUPs, this attachment, below, of the "lsblk" is an indicator that the QP64 also has the problem where one can see that the ventoy partition is shown when it seen in the listing. This partition is locked in INIT in such a way that QP64 cannot get to the SAVESPEC for proper processing of SAVESPEC directions.
I do understand that with WoofCE PUPs as they are currently generated will not resolve this.
This phenom does not exist in other non-WoofCE forum 'animal' families in Puppyland.
QuickPup64 24.01 RC2 released
Changes:
Download: https://drive.google.com/file/d/1dQ4y2Z ... AJM3FkXIJy
MD5 Checksum: 512aee13305f14004b87bb4eccaecd25
Google is refusing to serve this iso at the time of this posting claiming that too many users have attempted to download it. I had never seen such a message from google before.
step wrote: Mon Feb 12, 2024 9:09 pmGoogle is refusing to serve this iso at the time of this posting claiming that too many users have attempted to download it. I had never seen such a message from google before.
Reuploaded here...
I am using the latest Chrome browser. I am not having that problem and cannot confirm.
With the massive changes happening with EVERYONE from IBM to Apple to MS to Google to ... Everyone is stepping their game up since the beginning of the year.
Browsers (Mozilla, Opera, Edge, Chrome, etc) are all over the place with updates to the new internet phenomenons. There efforts and movements to additional compute systems is slowing everyone down on the internet as well as seeing some connection-download efforts across the board. Hopefull this is merely temporary; but ???
FYI
Hello @mistfire
On bare-metal via boot launchers launching the v2401rc2 ISO file
Note: After ISO file is launched, no user intervention required from Menu to desktop.
No keyboard use after PUP start its Menu until desktop arrival. It boot directlys to desktop from Ventoy v1.0.97 in ventoy's GRUB mode.
Known WoofCE problem when launched via Ventoy: But session will NOT save to valid location
It also boots to desktop via SG2D with NO issues. The desktop operates without hiccups, rapidly. AND session wil save in SAVESPEC location. The indicator of this is by listing 'lsblk' and notice the 'sdf' disk entry.
But, I still cannot get the PPM to update as it stops requiring to 'kill' it (see attached PDF below).
I will test again, later on another of the test PCs and report bootings. As well,too, I will test in KVM VMs.
Request
Are there any published steps for using the nvidia to replace nouveau?
QuickPup64 24.01 RC3
Download: https://drive.google.com/file/d/1IliZLp ... fqjebdrVM7
MD5 Checksum: dd49f4ca84482e9ce31d1d2f269ae683
Downloaded the ISO file to a Ventoy USB. 1st tests in a VM
Code: Select all
qemu-system-x86_64 -name "QP64 vRC3 via Ventoy by MistFire" -enable-kvm -smp 2 -m 2G -vga std -device AC97 -net nic -net user -rtc base=localtime /dev/sdf
Results
ISO file only - boots
Ventoy launch - fails to Grub console
SG2D launch - boots
QuickPup64 24.01 RC4 released
Changes:
* Pupsave file now uses ext4 by default. But still can load ext2/ext3 formatted pupsave file
* Pupsave file creation now moved to shutdown process instead of from shutdownconfig script. That shutdownconfig will simply create answer file on how to make puppy save file
* ext2/ext3 mounting will now use ext4 driver
* Linux kernel 6.8.4 (NOTE: 6.x is now the minimum kernel version requirement of QuickPup64)
* Added curlew media converter
* Added gearlever for managing AppImages
* GMetronome replaced GTick
* Improved blue recorder (screen recording app)
* Fixed critical PPM bug where the desktop environment hangs upon detecting duplicate package to be installed
* Xorg related config functions was moved from xwin to rc.sysinit
* More bugfixes
Download: https://1drv.ms/u/s!As14nV96TZw0gX4I1xP ... T?e=NzSZZn
Mirror: https://teraboxapp.com/s/1V8JBvtxmf2ng4T4yHRUjVA
MD5 Checksum: 3a367519ff3dc9e3d9b9de0d28da3991
(FIXED BROKEN URL)
Hi Mistfire
Thanks for new release.. Just to comment in order to use terabox downkoad service, it ask to install desktop app, or apk on mobile device, please note.
Regards
Pika
Bionic 32 bits repo: https://superbot.me/filetobot/168859#
Fossa 64 bits repo: https://superbot.me/filetobot/139122#
Attempt to download from your Google Drive results in the following:
'
Opening post update, maybe?
@Clarity @Pikaxhu @step
Reuploaded via OneDrive
https://1drv.ms/u/s!As14nV96TZw0gX4I1xP ... T?e=NzSZZn
Google was keep flagging my uploads on Google Drive as malware even though the upload was harmless and just a distro
Dear Mistfire
Thanks for your quick reply / reaction...
Another backup for your ISO, for telegram users at:
https://t.me/filetobot?start=6770096d_16208081
Direct link upon private request, for non tg users too.
Regards
Pikaxhu
Bionic 32 bits repo: https://superbot.me/filetobot/168859#
Fossa 64 bits repo: https://superbot.me/filetobot/139122#
Results ... Moved to RC5's announcement area of this thread
Dear Mistfire
FYI: Booted latest iso on my dual core
##### root@puppypc29459
####### -----------------
##O#O## OS: QuickPup64 24.01 x86_64
####### Host: Dell Inc. 0G848F
########### Kernel: 6.8.4-lxpup64
############# Uptime: 7 mins
############### Shell: bash 5.2.26
################ Resolution: 1366x768
################# DE: Xfce 4.18
##################### WM: Xfwm4
##################### WM Theme: Default
################# Theme: Adwaita-dark [GTK2/3]
Icons: papirus-lite [GTK2/3]
Terminal: xfce4-terminal
Terminal Font: Monospace 12
CPU: Pentium T4400 (2) @ 2.200GHz
GPU: Intel Mobile 4 Series Chipset
Memory: 1591MiB / 2950MiB
Frugal install on ext3 pupsave folder
- pkg / pkg2 doesn't have repo list available, after 1st boot. Do we need to setup...?
- Internet wizard doesn't offer usual connection tools ( SNS, Frisbee, Network Wizard) as first option
- Wifi reconnect after first boot was not automatic.. I"ll double check and confirm.
Hope this helps
Regards
Pika
Bionic 32 bits repo: https://superbot.me/filetobot/168859#
Fossa 64 bits repo: https://superbot.me/filetobot/139122#
@Mistfire
pmedia bootstanza problem:
Pmedia=ataflash, booting stop at "create ramdisk(1262M)...." pls see screenshot.
Pmedia=atahd, I can see only cursor(blank desktop).