Puppy Linux Discussion Forum

Added to repository: btop advanced system monitor, see https://github.com/aristocratos/btop

Download and install .deb:
64bit: https://github.com/doglinux/bulldog/raw ... _amd64.deb
32bit: https://github.com/doglinux/bulldog/raw ... 1_i386.deb

Or install with synaptic, or with apt:

apt update
apt install btop

Run from terminal btop or btop --help for options

EDIT: One hour later, re-uploaded deb packages, fixed a small mistake.
EDIT2: I've tried this on Buster and Fossa too now, but doesn't run, error, so my guess is that it will only run on very new systems such as Bullseye or Sid.

*** Updated mklive-bullseye ***

Attached script at First Post
Also appimages updated, see: https://debiandog.github.io/MakeLive/Re ... yedog.html

Changes:
- When running with -cli, a menu will show for choice of Desktop environment and additional options
- When running with -gui, added 'Settings' tab for to select additional options
This way less questions are being asked during the build, and IMHO it looks more professional
EDIT: When using -cli, the packages install list can only be modified by using a text-editor (after DE choice), so I'd say that using -gui is still more convenient.

Many thanks to @misko_2083 for providing his magical bash-menu concept viewtopic.php?p=36765#p36765
Wasn't easy to adapt, you gave me some homework study, Misko!

Fred

Running with -cli : (bash-menu)

Running with -gui :

Very nice.

I'll try it out later.

fredx181 wrote: ↑Sun Sep 26, 2021 11:38 am

Many thanks to @misko_2083 for providing his magical bash-menu concept viewtopic.php?p=36765#p36765
Wasn't easy to adapt, you gave me some homework study, Misko!

Fred

Running with -cli : (bash-menu)
2021-09-26_12-43-46.gif

Running with -gui :
2021-09-26_15-18-00.png
2021-09-26_12-37-51.gif

It's looking good Fred.
Sorry I couldn't help, Covid and lungs infection.
I'm still in the hospital attached to the oxygen.
But I am doing better now. No fever any more.

misko_2083 wrote: ↑Sun Oct 03, 2021 6:06 pm

fredx181 wrote: ↑Sun Sep 26, 2021 11:38 am

Many thanks to @misko_2083 for providing his magical bash-menu concept viewtopic.php?p=36765#p36765
Wasn't easy to adapt, you gave me some homework study, Misko!

Fred

Running with -cli : (bash-menu)
2021-09-26_12-43-46.gif

Running with -gui :
2021-09-26_15-18-00.png
2021-09-26_12-37-51.gif

It's looking good Fred.
Sorry I couldn't help, Covid and lungs infection.
I'm still in the hospital attached to the oxygen.
But I am doing better now. No fever any more.

Oh..., that's bad. Wish you all the best, Misko !
Hopefully you can recover soon.

Fred

@ fredx and rcrsn51
Its good bye from me for a while, my laptop has expired finally.
I could see it coming, 7 yrs old and I have read laptops are only made to last 3 yrs. At 22.2 cents a day to use it I am not complaining.
Some keys on the keyboard started playing up so I bought a Odroid and aPi 4 as backup for when the time came.
Any thing like geany that had a blinking curser, the curser filled the page with dotted lines, had to pull the plug in it. The grub menu just kept tumbling on boot up and had to take pot luck to see what distro loaded. Fatdog would not load at all so I pulled the laptop apart to see what it looked like.
The Mate desktop is the best desktop for me, its the 'systems monitor' in the tray that makes all the difference. Can have one for each for the cpu and internet, change the colours, speed very configurable.
Though I did miss rox filer, I did install rox on my odroid but can not configure as can in puppy, so it did not work for me, puppys build of rox is unbeatable. Thanks for the work you put into puppy.

Does the build script work well with Devuan ?it has been learnt of that Devuan was released.

helloworld wrote: ↑Sat Oct 16, 2021 5:53 am

Does the build script work well with Devuan ?it has been learnt of that Devuan was released.

Not this script, but mklive-chimaera should still work (I just tested):
viewtopic.php?p=26733#p26733
But -as I understood- if you cannot download anything from Github, it obviously doesn't work.

fredx181 wrote: ↑Sat Oct 16, 2021 8:41 am

helloworld wrote: ↑Sat Oct 16, 2021 5:53 am

Does the build script work well with Devuan ?it has been learnt of that Devuan was released.

Not this script, but mklive-chimaera should still work (I just tested):
viewtopic.php?p=26733#p26733
But -as I understood- if you cannot download anything from Github, it obviously doesn't work.

I can make access to github by a proxy which helps me to bypass the censorship

helloworld wrote: ↑Sat Oct 16, 2021 2:53 pm

fredx181 wrote: ↑Sat Oct 16, 2021 8:41 am

helloworld wrote: ↑Sat Oct 16, 2021 5:53 am

Does the build script work well with Devuan ?it has been learnt of that Devuan was released.

Not this script, but mklive-chimaera should still work (I just tested):
viewtopic.php?p=26733#p26733
But -as I understood- if you cannot download anything from Github, it obviously doesn't work.

I can make access to github by a proxy which helps me to bypass the censorship

Ok, but, trying to understand, out of curiosity, do you need to edit the script by changing every wget or apt command pointing to Github then to use a proxy, seems very inconvenient to me, or.. what would you need to do then to run the build script properly ?
EDIT: And why is it that you need to use proxy ? (again, just curious)

fredx181 wrote: ↑Sat Oct 16, 2021 5:28 pm

helloworld wrote: ↑Sat Oct 16, 2021 2:53 pm

fredx181 wrote: ↑Sat Oct 16, 2021 8:41 am

Not this script, but mklive-chimaera should still work (I just tested):
viewtopic.php?p=26733#p26733
But -as I understood- if you cannot download anything from Github, it obviously doesn't work.

I can make access to github by a proxy which helps me to bypass the censorship

Ok, but, trying to understand, out of curiosity, do you need to edit the script by changing every wget or apt command pointing to Github then to use a proxy, seems very inconvenient to me, or.. what would you need to do then to run the build script properly ?
EDIT: And why is it that you need to use proxy ? (again, just curious)

well,if you are in a censorship environment,you will have willing to find any way to bypass it.get a proxy app,run it on a device ,set it to listen 0.0.0.0,let your puppy machine make access to that device.
some proxy apps can set global proxy in linux,just run them,you can transparently access git .
If you have a router supporting being flashed into a free firmware,then install the proxy apps which support being installed on the free firmware,ler your router do the job.

Hi Fred.
How to use and configure pulseaudio instead of alsamixer in bullseye build?
Thank you.

recobayu wrote: ↑Thu Nov 04, 2021 5:38 am

Hi Fred.
How to use and configure pulseaudio instead of alsamixer in bullseye build?
Thank you.

Don't know much about it, but what works for me is (very basic, assuming you run the system as "root"):
- Install pulseaudio apt install pulseaudio
- Start it as root pulseaudio --start (you'll get a warning, but it works) (pulseaudio running as root is not standard)
Now pulseaudio is activated you can adjust basically the volume with alsamixer, but more advanced is "pavucontrol"
Install: apt install pavucontrol and run from menu.
To start pulseaudio at boot, you can add a little script in /root/Startup containing:

#!/bin/sh
pulseaudio --start

Perhaps others with more knowledge can comment about using pulseaudio with more possibilities.

Fred

*** Some changes and fixes ***

Changes and fixes made in the repositories. No changes for the build script necessary.

- Fixed that "obkey" (keybinds editor) probably didn't run with a new build, updated to new version, had to do with python-gi (python2 based package) not available anymore.

- Fixed that "repo configuration" (package repo-conf) didn't work as it should when the build is with systemd enabled.

- New "youtube-viewer" package v3.9.6 (latest) (includes "gtk-youtube-viewer"), this the best version IMO so far I've seen (edit: btw, one extra dependency added is "fonts-symbola"):
-- Not dependent anymore on youtube-dl (or, nowadays, yt-dlp) for playing, as well as for downloading videos.
-- Video play starts very fast now (with previous versions it was rather annoying how slow it started, I thought earlier that it could have to do with the player, e.g. "mpv" but apparently not).
(note that the package includes configuration, so existing in /root/.config/youtube-viewer will be overwritten, if preferred make a backup first of /root/.config/youtube-viewer)

- Added 'pipe-viewer" package, should replace "straw-viewer" (deprecated), also by developer "trizen" https://github.com/trizen?tab=repositories

- Updated "youtube-get3" (download from YouTube) package to v1.5.3, now using "yt-dlp" instead of "youtube-dl" (it doesn't seem to be developed anymore)

Install with synaptic or with apt (from terminal e.g. apt update; apt install obkey repo-conf youtube-viewer).

EDIT: Added new "youtube-viewer", "youtube-get3" and 'pipe-viewer" also to the Busterdog repo.

Fred

I'm back. errr, no I'm not, coming from my Pi 4. It's impossible to buy a ryzen 3 or 5 in indo china, when a ryzen 5 1400 (about year 2017) came up omline I bought it and a low end $65 A320 chipset board. I cannot get it to boot. So I changed to GPT file system, got through rcrsn51 howto, still no boot. Here is the converted grub.cfg's.

menuentry "StarterKit+Mate-remaster-amd64-2 on sda2" {
search --no-floppy --fs-uuid --set=root 7794fa0f-7186-43a0-ba1a-894809ee68bf
linux /EMPTY/live/vmlinuz1 edd=off noauto from=UUID:7794fa0f-7186-43a0-ba1a-894809ee68bf/EMPTY changes=UUID:7794fa0f-7186-43a0-ba1a-894809ee68bf/EMPTY
initrd /EMPTY/live/initrd1.xz
}
error messages
cant find command find
cannot find 7794fa bla bla bla the uuid
cannot find /vmlinuz
you need to load the kernel first

menuentry "Puppy dpupbuster64 8.0.0 (sda3)" {
find --set-root uuid ()
d7a176f0-d27a-4b5d-bc91-e658a79b3f7d
linux /vmlinuz pdrv=d7a176f0-d27a-4b5d-bc91-e658a79b3f7d pmedia=atahd pfix=fsck waitdev=3
initrd /initrd.gz
}
error message you need to load the kernel first

This is a backup copy of an older fatdog. on msdos partitions.
title Fatdog64 (sda1)
find --set-root uuid () C104-5F78
kernel /vmlinuz pdrv=C104-5F78 pmedia=atahd pfix=fsck waitdev=3 #savefile=none
initrd /initrd
error messages selected item cannot fit into memory
This is the error message of all the msdos fs's.
frex bullseye remaster
dpupos-amd-64
latest fatdog 64
There was one error message 'grub4dos memory 157mb' or something similar, I did not write it down! Probably why I get the 'fit into memory' message.
Any clues, thanks.

Just guessing.

Maybe try the from as just "from=/" or with a trailing "/".

FWIW, these are the auto generated samples from the Debian Dog install program that I saved.

title Debian-PorteusDog  -  changes to /live/ sysvinit
 uuid 8778c5fe-442d-4627-aec2-5b0de8fxxx
 kernel /StretchDog64FromHP/live/vmlinuz1 from=/ noauto changes=/StretchDog64FromHP/live/
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Always Fresh sysvinit
 uuid 8778c5fe-442d-4627-aec2-5b0dexxx
kernel /StretchDog64FromHP/live/vmlinuz1 from=/ nomagic base_only norootcopy
initrd /StretchDog64FromHP/live/initrd1.xz

title Debian-PorteusDog  -  Copy to RAM sysvinit
 uuid 8778c5fe-442d-4627-aec2-5b0de8xxx
 kernel /StretchDog64FromHP/live/vmlinuz1 noauto from=/ copy2ram
 initrd /StretchDog64FromHP/live/initrd1.xz

Is this a UEFI-compatible board?

How did you set it up the first time when the hard drive was in MBR format? By putting it in legacy mode and using Grub4Dos?

In what way did it fail to boot?

If that failed , then switching to GPT probably isn't going to solve the problem.

If you couldn't get it to boot, how did you switch the hard drive to GPT? Can you boot it off a flash drive?

Are you sure that you have the correct RAM in this thing?

dancytron,
Thanks for help, the menu.1st for msdos has to be converted to grub2 for GPT partitions. That the part I cannot get to work on a SSD drive with GPT.
rcrsn51,
The secure boot choice's are windoze UEFI mode and other os, I choose other os. In boot device control I choose legacy OPROM, whatever OPRAM is!!

If you couldn't get it to boot, how did you switch the hard drive to GPT? Can you boot it off a flash drive?

I was able to boot Fred's mate from a original lexor usb flash drive about 15 year old, write speed 3mb/sec, took 2 and half minuted to load but it always got there until borked it some how trying to do conversions of its menu.1st. I cant get back the magic formula of menu.1st again to boot this board. While I had it working I could not get the right formula to boot from a SSD in msdos mode so I changed to GPT. Now I have neither. Now I will reload Fred's mate to the slow lexar again and work on getting it to boot again.
Ram is TEAM ELITE AMD CPU 3200 8GB amd cpu 3200 is a ryzen 3 with graphics on board the cpu. My ryzen 5 has no grafics on board, dont know if that is the problem.

"While Pup/Dog people continue to use Grub4Dos and MBR drives, the mainstream Linux world has moved ahead with GPT partitioning and GRUB2."
If I cant get GPT to work on SSD then I will go back to msdog and grub4dog. But I would rather have GPT, like mt Everest 'because its there'

I don't understand.

Do you still have the UEFI firmware in Legacy Mode? When you switched to GPT, did you also install the GRUB2 bootloader?

Or did you just convert the menu.lst file to grub.cfg format?

I'm afraid I don't understand either.

I thought it was a simple formatting issue and most of those can be solved by trial and error.

You are doing something else...

rcrsn51,
I am using legacy mode, it is called 'otheros' against 'windoze UEFI mode' I take 'otheros' to be legacy mode. Secure boot turned off.
Yes the grub 2 squashfs was loaded, I remember stage 1 and 2. Your howto said to put them in sda but thats the drive one is running on so I put them in sdb and it makes the /boot/grub/grub2.cfg file then I convert the grubmenu.txt file made in the first install and paste it into grub2.cfg.

menuentry "StarterKit+Mate-remaster-amd64-2 on sdb2" {
search --no-floppy --fs-uuid --set=root 7794fa0f-7186-43a0-ba1a-894809ee68bf
linux /EMPTY/live/vmlinuz1 edd=off noauto from=UUID:7794fa0f-7186-43a0-ba1a-894809ee68bf/EMPTY changes=UUID:7794fa0f-7186-43a0-ba1a-894809ee68bf/EMPTY
initrd /EMPTY/live/initrd1.xz
}

Tried this from dancytron's idea. ( and a hundred other)
menuentry "Puppy fredx-64 (sda2)" {
find --set-root uuid () 7794fa0f-7186-43a0-ba1a-894809ee68bf
kernel /EMPTY/live/vmlinuz1 from=/ noauto
changes=/EMPTY/live/
initrd /EMPTY/live/initrd1.xz
}

I have a slow flash drive that I made Freds Mate desktop on when my laptop was still working but have hosed it somehow now all work on GPT is halted until I get Freds Mate running again.
I have been able to get Fatdog running by running it from initrd-nano. There was one error message in msdos mode 'grub4dos 157mb memory' so I tried initrd-nano and it worked. But must have a bad download, Eztables wont load properly, it does not shutdown properly after trying to turn on the firewall and I have to pull the plug. However I am going to try load your grub2.squashfs into Fatdog to see if I can get your installer working again. Then see if I can Fred Mate working in msdos again.

spotted wrote: ↑Tue Nov 23, 2021 12:15 pm

Your howto said to put them in sda but thats the drive one is running on so I put them in sdb and it makes the /boot/grub/grub2.cfg file then I convert the grubmenu.txt file made in the first install and paste it into grub2.cfg.

How did you have the machine booted when you were doing this? Off a flash drive?

Is sdb a second hard drive in the machine or is it the flash drive?

Even if you boot off a flash drive, sda should still be the internal hard drive. You could tell them apart by looking at their sizes.

Is your flash drive broken because you accidentally put GRUB2 onto it?

How did you have the machine booted when you were doing this? Off a flash drive?

Yes, it is a flash drive I used as a backup drive when I first started using your and Freds debians on the now trashed laptop when I was learning how to install your debians.

Is sdb a second hard drive in the machine or is it the flash drive?

The second drive 'sdb' is a SSD and your howto worked, I have the GPT part all done. You said make a flash grive first to use the installer but I had the flash drive already from before and it worked, until I borked it, now I cant get the magic back.

Is your flash drive broken because you accidentally put GRUB2 onto it?

No, not a grub2.cfg, it was still msdos because I was still trying to boot in msdod mode at the time.
Now have the original grubmenu.txt thats put in EMPTY when first installed on the laptop but changing the UUID number.

title StarterKit+Mate-remaster-amd64-2 on sda2
uuid 229421a7-0d64-410a-9f3f-ddd457e1f61f
kernel /EMPTY/live/vmlinuz1 edd=off noauto from=UUID:229421a7-0d64-410a-9f3f-ddd457e1f61f/EMPTYchanges=UUID:229421a7-0d64-410a-9f3f-ddd457e1f61f/EMPTY
initrd /EMPTY/live/initrd1.xz

Can you see anything wrong with it?
I get the new uuid from gparted-sda2-information, copy and paste into menu.1st. It should 'just work', I must have something wrong in BIOS settings.
I disabled fast boot didnt fix anything.
legacy usb support set to enable
usd device set to enable
In secure boot options 'other os' (legacy I guess?)
and 'windows UEFI mode'
I choose 'other os'
Secure boot might be the problem child.
From secure boot help.
'other os', select this option to get optimized functions when booting on windows non UEFI mode and microsoft non-compliant operating systems.
My take from this is that secure boot cant be turned off completely, still giving 'optimized functions' in legacy mode. Your self, BK, James Bond say 'turn it off'.
Is this the reason grub4dos is setting ram to 157 mb in an error message that only poped up once, wish I had wrote the full error message down.
I can start Fatdog in 'initrd-nano' mode, but in 'initrd' mode I get
'selected item cannot fit into memory'
Suggests to me that the wording in menu.1st is correct to get this far and something from secure boot is limiting ram in grub4dos to 157mb maybe.

I'm sorry that this has not worked properly for you. I have some final thoughts. Read #6 first.

1. I am still confused by the sda/sdb situation. Is the machine with the Ryzen CPU a laptop or a desktop? Does it have two internal drives? Where is sda? How does this situation have anything to do with sdb? If it has two drives, which one has the GRUB2 bootloader?

2. I believe that your best option is to boot in UEFI mode instead of Legacy. The Starter Kit thread has a recipe for making a UEFI-compatable flash drive. Or get a UEFI-compatible Puppy ISO and burn it to a flash drive.

3. I don't understand your comments about the borked flash drive. Does it not work anymore with regular BIOS/MBR machines? There is nothing in the GPT procedures that would have changed it.

4. Before you tried switching to GPT, did this machine ever boot off a hard drive? How are you getting the gparted information if the machine won't boot?

5. How do you have Fatdog running? By booting off a flash drive? From a hard drive install?

6. You keep posting a menu.lst entry. Where is this GRUB menu located? Somewhere on the hard drive? On a flash drive? Are you trying to boot using Grub4Dos but to a GPT-structured drive? That won't work.

rcrsn51
Made a discovery.
A quick reply for now. Making GPT partitioning on the internal SSD is working fine, did all that while flash drive was working. Just cant get it to boot. All of the last post above is getting the flash drive working. I have discovered that when making 'usbmarker' in Easy os 'usbmarker ' is made as a shell script instead of a blank file. ( touch usbmarker) This may be the problem child. So will change to Fatdog to see how usbmarker fares there. But Fatdog has a problem also on this board. I have downloaded it twice and the problem is that eztables is broken on this board so I will not be going online with it.
I never ever thought about trying UEFI, once I get a flash drive booting I shall read up your work on UEFI. I shall keep in touch, thanks

rcrsn51
Success with UEFI errr, sort of
In another go figure moment Freds Remaster + mate desktop still will not kick in BUT his original Bullseye does. yippie!!! I used your UEFI Secure boot to my slow drive to do it.
I use hdmi to a tv. The grub2 screen text is tiny and faint, like greyed out. Had to wait until night time and turn the lights out and get up close with my byfocal normal glasses to read it.
Here is the error message for Freds Remaster + Mate that does not boot.

error invalid xxxx number (xxxx is unreadable)
you have to load the kernel first

Before you tried switching to GPT, did this machine ever boot off a hard drive? How are you getting the gparted information if the machine won't boot

It's my bad for not saying that it is Freds Remaster + Mate that is NOT booting in my first post after coming back. Sorry for that, it has caused a lot of confusion. Easy os ( on a flash drive) and Fatdog (on a different flash drive) boot in (msdos) but the BIOS or the mother board dont like Fatdog, xztables does not work.

6. You keep posting a menu.lst entry. Where is this GRUB menu located? Somewhere on the hard drive? On a flash drive?
It is on the slow flash drive. Did a rebuild of it with Fatdog (gparted - device - create partition table - msdos) and the 'touch usbmarker' part now works properly using Fatdog' With Easy Os the 'usbmarker' file turns into a shell script. I have the 'live' folder from both Freds Remaster Mate and his origional Bullseye. I hash the 'live' folder I DO not want to load. Original Bullseye loads Remaster + Mate does not load.
What is the bug that causes 'usbmarker' in Easy os to become a 'shell script'
Is this bug doing something to the grub.cfg text when booting Remaster + Mate that stops it booting up, is it a BOIS or motherboard bug???

@spotted

Similar situation for me, perhaps this helps you, just got a brand new modern laptop now so have to deal with UEFI (no legacy boot option), turned off secureboot, made two partitions, 1st: FAT32 and 2nd: ext4 (partition table: gpt).

From ReadMe-UEFI:

For manual (copying) USB install UEFI-boot, copy the folders EFI, boot, live, and the file grub.cfg to the root (/) of a FAT32 formatted partition, e.g. /mnt/sdb1.
And it should boot, no bootloader install stuff required.

Did that on first HDD partition for Bullseye install , edited grub.cfg (pointed to changes on the ext4 partition) and it boots fine.

The files are in an ISO created with the build script, if chosen UEFI, but separate archive (ISO-UEFI skeleton) is here:
https://github.com/DebianDog/MakeLive/r ... efi.tar.gz
(to add above mentioned files/folders to your mate-remaster install perhaps, if not done already)

@spotted: The "touch usbmarker" command is only needed to create a dummy file used by this menu entry:

title Starter Kit on USB
find --ignore-floppies --set-root /usbmarker
kernel /live/vmlinuz1 edd=off noauto copy2ram from=/
initrd /live/initrd1.xz

Otherwise, it is irrelevant. Because it is a blank file on a fat32 partition, some OS's will identify it as a script instead of a text file. Some Puppies also do this. It has no effect on booting.

@fred: It would make more sense to keep your fat32 EFI System Partition small and put the "live" folder in the ext partition. This is why the Multi Installer exists.

I have always contended that the simplest way to run a UEFI machine is in UEFI mode. But community members who have drunk the anti-UEFI-anti-SecureBoot-anti-GRUB2 koolaid refuse to believe this.

@spotted: I hate to bring this up again, but does any of this discussion have anything to do with the hard drive and its GPT setup?

@spotted: I hate to bring this up again, but does any of this discussion have anything to do with the hard drive and its GPT setup?

Sorry rcrsn51, my bad again.
I used your UEFI Secure boot to my slow drive to do it.
It should read -my slow FLASH drive-
Now half working as it boots into Freds original Bullseye.

"touch usbmarker" is working fine now, I use Fatdog instead of Easy to make the flash drive.

Fredx
Now I write about the GPT SSD, internal.
Built the rcrsn51 way with 'live' in sda2.
It half works Fred. But like the slow flash drive only your original Bullseye works. BIOS set to UEFI only and it just booted, didnt ask for any shim keys.

error invalid xxxx number Could this be invalid magic number. I have a faint recollection of seeing that before.

Hi Fred.
I try to use pcmanfm as desktop instead of rox when I build bullseye jwm. I comment a line in the file /root/startup-jwm

#/usr/bin/rox -p ${HOME}/.config/rox.sourceforge.net/ROX-Filer/pinbd-OB &

and add

pcmanfm --desktop &

. And it works. I can make pcmanfm as my desktop. But now the problem is, my conky and volumeicon's background is not right. like in the attachment. And when I right click on the desktop, the volumeicon is gone. How to fix that? How to not use rox at all? so just jwm and pcmanfm.
Thank you.