Moderator: Forum moderators
rockedge wrote: ↑Thu Feb 02, 2023 3:55 pmWhat a gray and boring design theme
Just like my nickname.
There was a time I had a 1967 Volkswagen Beetle. Looked just like a red plain '67 Bug. Many found out the car was incredibly fast and were very surprised because it looked so.....plain.....
I had put a Porsche engine and brakes in it.
Drove the local police nuts.
Herbie? I remember a guy around who had a small Chevy Firenza with a V8 Ford Mustang engine.
Oddly enough, I also thought about Herbie In the 90s, Disney films (old) were shown in Russia on Friday evenings.
The Love Bug, Herbie Rides Again
A lot of things: Not Quite Human, I-Man, Hard Time On Planet Earth, The Last Electric Knight, The Three Lives of Thomasina, Bride of Boogedy, Nikki Wild Dog of the North 
Fossapup OS, Ryzen 5 3600 CPU, 64 GB RAM, GeForce GTX 1050 Ti 4 GB, Sound Blaster Audigy Rx with amplifier + Yamaha speakers for loud sound, USB Sound Blaster X-Fi Surround 5.1 Pro V3 + headphones for quiet sound.
The engine was too heavy for the body
Scavenged a rear axle assembly from a Porsche 914 and installed extra stiff hydraulic shocks that supported the extra engine weight.
Good in the snow with the engine right on top of drive wheels. Like a Porsche 911 the Bug had massive under-steer so go slow into curves and a big punch coming out. Could do good drifts. Transmission was more heavy than the original but it was 6 speed instead of 4
Just thought I'd mention this in case it helps. I just booted up KLV-Airedale. I don't know what the difference in pulse-audio is between that OS's and this ones, but KLV-Airedale was easily able to play the youtube linked on this post, https://www.forum.puppylinux.com/viewto ... 140#p80140 WITH sound from MikeWalsh's portable Iron and Slimjet. Actually, the entire pulse-audio setup seem easier to use. If not for F96-CE, keep that in mind while developing Jammy.
... Volkswagen Beetle ...
I remember a BUG that toured the drag-strips in US Pennsylvania back in the 70s. Though it wasn't red, it drove the Chevy-Ford boys 'nuts' as it was much too quick and unsuspecting!
Same setup as you. Amazing to see 
rockedge wrote: ↑Thu Feb 02, 2023 2:21 am@bigpup I went through great lengths to rebuild the kernel. I do not know what is going on but I can tell you the vmlinuz and modules are from the same build as the sources and vise-versa
I see that the version original kernel compile occured in a Slacko and what I compiled was done in a F96
did you start with a fresh download of F96-CE ??? The kernel is completely changed from the original. Download the most recent and use the most recent kernel sources. They will match.
Now that I know everything is new and you have to do everything over.
I downloaded everything that was in the first post on February 02 2023 and installed to a new frugal install.
Tried compiling a Nvidia graphics driver using a Nvidia run package from their web site.
This time it worked and the driver is compiled and installed.
Using it now.
So this set of the F96-CE ISO, devx sfs, and kernel sources sfs work.
I guess this is a good test to see if the 3 different parts will match and work together.
So every new version posted in the first post, I will test to make sure compiling is still working.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
My desktop
.
.
.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup really nice desktop design! Like the wallpaper a lot as well. How is F96-CE behaving?
Still checking programs offered by Quickpet Fossa
Steam is the only one so far that just would not run.
I remember 666philb had a hard time ever getting it to run in Fossapup64 9.5.
Did some kind of magic with the pet package for it.
But that magic is not working for F96-CE.
That background image is the animal Fossa.
The fossa is a slender, long-tailed, cat-like mammal that is endemic to Madagascar.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
F96-CE not recognized by Puppy Installers
@bigpup
Hello,
Neither Bionicpup64 8.0 frugal or Dpup Stretch32 7.5 frugal using either YAPI or Puppy Installer can find F96-CE .iso.
Both Bionicpup64 and Dpup Stretch can find the .isos for Bionicpup64 or Dpup-Stretch32.
The iso it isn't found no matter where I place the F96-CE .iso anywhere on sda1 or sda2.
The UEIF installer needs FAT 32 as drive format.
I have the drive set up with two ext4 partitions.
The drive is a Sandisk Ultra Flair USB 3.0.
I also tried several old Sandisk Cruzers 2.0 drives with same negative results.
The machine is a Dell Inspiron N7010 with 2.0 USB ports.
Anything else I can screenshot or tell you?
Thank you in advance,
Sky
You do need to have the partition it is on mounted, before trying to access the ISO.
So, if the sda2 partition is mounted and you still get the error.
YaPI installer and some of the older Puppy installer programs are coded to work with ISO's with pup in their name.
Yapi was coded to work with the names used for Puppy versions at the time it was developed.
Anything with pup in the name, was one general way to know, it was Puppy Linux.
Try renaming the F96-CE.iso to F96pup-CE.iso
This is an idea, I have not tried it.
I have moved on to only doing installs using Frugalpup Installer.
viewtopic.php?t=337
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Try renaming the F96-CE.iso to F96pup-CE.iso
This is an idea, I have not tried it.
I have moved on to only doing installs using Frugalpup Installer.
viewtopic.php?t=337
Thank you bigpup.
Yes, receiving stick mounted.
Bionicpup64/YAPI did not find F96-CE.iso renamed 'F96pup-CE.iso.
Bionicpup64/ Puppy Installer/Universal installer did not find F96-CE.iso renamed 'F96pup-CE.iso.
Bionicpup64/frugalpup-38 cannot find mounted drive.
I did not use StickPup v38 as it's for a fat32 partition. I want two ext4 partitions, one for Puppy and one for storage.
Sky
I will run a test installing F96-CE using a Bionic64-8 to install to a USB stick drive using one of the supplied Puppy Linux installer utilities.
The F96-CE.iso is not being "seen" by any of the Puppy installers in Bionic64 is the problem?
@rockedge
Yes
Also, I tried with most recent Dpup Stretch 7.5. using all the installer options except Frugalpup Installer as suggested by @bigpup .
Good Evening,
I was able to make a puppy stick of F96-CE.iso using f2Stickpup fat32 "with large Linuxf2fs partition' while using Dpup Stretch 7.5. as the Distro.
I am writing from it now. However, I am confused as to what I have. There is terminology that is new to me.
What is a f2fs partition?
Can I store private data on sda2 like I used to on ext4 on my previous setups?
Will that keep the save-file from becoming bloated?
The initial presentation looks so elegant! I look forward to investigating F96 tonight.
Thank you for your patience with me as I learn this new installer.
Sky
Hello @Sky Aisling "f2fs' is a filesystem format of a partiton that performs the same duties as does FAT/NTFS/EXT2/EXT4/etc. It was designed specifically to take advantage of memory sticks although it will also work with SDcards/microSDcards/HDDs/SSDs/ and other physical storage devices.
You can read more by reviewing on Wikipedia searching for f2fs
Hope this is helpful
Sky Aisling wrote: ↑Wed Feb 08, 2023 5:07 pm@bigpup
Try renaming the F96-CE.iso to F96pup-CE.iso
This is an idea, I have not tried it.
I have moved on to only doing installs using Frugalpup Installer.
viewtopic.php?t=337Thank you bigpup.
Yes, receiving stick mounted.
Bionicpup64/YAPI did not find F96-CE.iso renamed 'F96pup-CE.iso.
Bionicpup64/ Puppy Installer/Universal installer did not find F96-CE.iso renamed 'F96pup-CE.iso.
Bionicpup64/frugalpup-38 cannot find mounted drive.
I did not use StickPup v38 as it's for a fat32 partition. I want two ext4 partitions, one for Puppy and one for storage.
Setup Installers1.png
Sky
What also needs to be mounted is the location of the ISO.
I tried using YaPI.
I did it by right clicking on the F96-CE.iso
Select YaPi from the right click menu.
That starts YaPI at the place where you select the drive to install to.
That worked for me and did an install.
---------------------------------------------------------------------------------------------------------------------------------------------
Bionicpup64/frugalpup-38 cannot find mounted drive.
If the drive partition is already mounted that the iso is on. (it must be first mounted before using Frugalpup Installer)
Select iso as the source.
The navigation window, that pops up for you to use, to locate and choose the ISO, is a little confusing.
First you click on file system.
Then /mnt
Then the partition of the drive where the iso is located.
Etc.........
I was able to use Frugalpup Installer and do an install.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup @rockedge @Clarity What an elegant new puppy! Thank you all who participated in creating this distro. Who are the architects of this work? edit: Ah! I see @radky has done it again!
I'm preparing to make a Puppy stick to give as a gift to our local computer repair store. The tech there runs a Meerkat mini pc personally (among other machines). I'm thinking he'd have fun with fast moving F96-CE on the fast moving Meerkat mini pc.
Now, which of the many installers to use?
@bigpup I'll start with your suggestion of YAPI in the manner you suggest.
Sky
Hello.
The following are some of my observations.
1. The volume of sound is not saved. /etc/asound.state is not updated when the OS shuts down. It does not seem that the setting of alsa is restored when the OS boots.
2. The hwclock seems to be set to utc even though I unchecked the item in quick setup.
3. The mouse pointer freezes after the OS wakes up from "sleep" (the suspend state). This issue may be hardware-dependent.
Does anyone experience the first two issues?
I can confirm 1. and 2.
Checking or unchecking the item in Quick setup doesn't seem to change anything.
EDIT: To be exact:
This only applies if the time zone is not changed!
If I by default set "GMT+8 (Perth, Singapore, Hong Kong)" change to "Australia/Perth ." .
then the time changes to local time.
In my case minus 8 hours
1. The volume of sound is not saved.
Cannot confirm, the volume setting on my computer is saved between boots.
Thanks
wizard
Big pile of OLD computers
Thank you for the reply.
I set "Asia/Tokyo," and "utc" is unchecked. But I have had to adjust the clock every time I reboot into another puppy.
So I added the following command to /etc/rc.d/rc.shutdown:
Code: Select all
hwclock --systohc --localtimeThank you for the reply.
Did you change the volume from the default value?
/etc/asound.state was updated only when I executed the following command:
Code: Select all
alsactl -f /etc/asound.state storeAnd the setting was restored only when I executed the following command after booting:
Code: Select all
alsactl -f /etc/asound.state restoreDid you change the volume from the default value?
Yes, using the volume control in the JWM tray.
wizard
Big pile of OLD computers
thinkpadfreak wrote: ↑Mon Feb 13, 2023 3:16 amHello.
1. The volume of sound is not saved. /etc/asound.state is not updated when the OS shuts down. It does not seem that the setting of alsa is restored when the OS boots.
---
@thinkpadfreak
Pulseaudio is relatively new for Puppy Linux and the setup options are primarily by command line (no GUI).
To set your audio output device and hopefully retain those settings after rebooting, you could try the following:
1 - To test the following, first disable any ALSA control scripts you may have created.
2 - Right-click the tray volume control applet and select Preferences -> Output Devices
3 - Select your preferred audio output device and click the 'Set as fallback' icon to set this as your default (and preferred) output device
4 - Enter the following in a terminal:
Code: Select all
pactl info | grep -i 'default sink'For my system, this returns the following:
Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
5 - To save your preferred (default) audio output device, add the 'sink name' directive to /root/.config/pulse/default.pa. This file does not exist in F96, so you must create it and add the appropriate 'include' call to the system-wide pulseaudio config file: /etc/pulse/default.pa (note the period symbol preceding the 'include' statement in the example below).
6 - To save your preferred audio volume for the selected output device (for example, 70% of maximum), you could add the 'sink volume' directive to /root/.config/pulse/default.pa.
For my system, /root/.config/pulse/default.pa would be something like this:
Code: Select all
.include /etc/pulse/default.pa
pactl set-default-sink alsa_output.pci-0000_00_1b.0.analog-stereo
pactl set-sink-volume 0 70%7 - Reboot
Thanks for the reply.
I wonder if this issue is hardware-dependent.
Thanks for the explanation.
I am not familiar with pulseaudio, but I did only these on Jammypup64 9.7b / 9.8 by Grey, and I got sound as I preferred.
I use alsactl command on F96-CE as I stated in the previous post, and I think this method is simpler.
thinkpadfreak wrote: ↑Mon Feb 13, 2023 3:16 am2. The hwclock seems to be set to utc even though I unchecked the item in quick setup.
@thinkpadfreak
Do you see this issue only in the current iteration of F96-CE, or perhaps also in other recent Pups such as vanilla Dpup or S15Pup?
Concerning quicksetup of F96, the most recent Woof-CE commit of Oct 22, 2022 for quickset has a small change to fix the locale combobox under Wayland, but I see no difference in the implementation of the HWCLOCKTIME and DEFAULT_UTC variables. Maybe @dimkr could help us understand your bug report for F96.
S15Pup64 has no problem as to the hwclock setting.
The last version of Vanilla Dpup I use is 9.2.21, and it has the same issue.