slacko64-8.2.1-alpha-alpha-beta+0 (slacko64-8.2.2 by norgo)

baldronicus · Post by **baldronicus** » Mon Jun 21, 2021 8:52 am

Hi @Ramachandra Iyer . I'm butting in where I shouldn't, but there are some more questions.
From your replies, I guess the problem is with a new HP laptop, with a built in Nvme SSD. You indicate that it is used in a Dual Boot environment. I presume this means the "original" Windows 10 installation is still present. If this is the case is Fast Boot disabled? I am not familiar with dual booting Windows 10, but I have read that this can sometimes be an issue (I presume it is disabled since you have been dual booting before, but have to ask).
You also indicate that Antix Linux boots without difficulty. I get the impression that it is also installed on the laptop. Is this correct?
If so, you might be able to use Antix Linux to obtain the lspci -nnk info that 01micko has indicated might help.
Did you install Slacko using Antix, Windows or by running Slacko live?
If you can run Slacko live then you might be able to obtain the lspci -nnk info directly from the live Slacko, which might be of even more help than the Antix Linux info.

Thanks.

Post by **bigpup** » Mon Jun 21, 2021 9:48 am

Was Windows 10 shutdown as a normal shutdown?
Not in hibernate?
Hibernate does not completely release control of the drive to Puppy Linux booting.

Ramachandra Iyer · Post by **Ramachandra Iyer** » Tue Jun 22, 2021 7:04 am

Sir

Original windows 10 is available for booting. Fast boot disabled. Antix Linux installed in another ext4 partition. I have installed the slacko by booting slacko live usb and used slacko installer for frugal installation in separate partition. I used to shutdown windows completely. ( No hibernation).

Some of the error while booting from SSD is given below:
Slacko64 Puppyt 8.2.1

Waiting 5 seconds for slow storage devices
Finding puppy main sfs file
Dumping last ime of /tmp/bootinit.log

/pupy -slacko64 8.2.1 sfs not found

Ramachandra Iyer · Post by **Ramachandra Iyer** » Tue Jun 22, 2021 7:23 am

Please see the lspci nnk output after booting slacko64 from usb

~$ lspci -nnk
0000:00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9a04] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a78] (rev 01)
DeviceName: Onboard IGD
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: i915
Kernel modules: i915
0000:00:04.0 Signal processing controller [1180]: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant [8086:9a03] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
0000:00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator module [8086:9a11] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller [8086:9a0b]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: vmd
Kernel modules: vmd
0000:00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: xhci_hcd
0000:00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM [8086:a0ef] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 [8086:a0e8] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 [8086:a0e9] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
0000:00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-LP Management Engine Interface [8086:a0e0] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: mei_me
Kernel modules: mei_me
0000:00:1c.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI Express Root Port #8 [8086:a0bf] (rev 20)
Kernel driver in use: pcieport
0000:00:1d.0 System peripheral [0880]: Intel Corporation Device [8086:09ab]
Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:1f.0 ISA bridge [0601]: Intel Corporation Tiger Lake-LP LPC Controller [8086:a082] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci
0000:00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-LP SMBus Controller [8086:a0a3] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller [8086:a0a4] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:87fd]
Kernel driver in use: intel-spi
Kernel modules: intel_spi_pci
0000:01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822]
DeviceName: Realtek Wireless LAN + BT
Subsystem: Hewlett-Packard Company Device [103c:85f7]
Kernel driver in use: rtw_8822ce
Kernel modules: rtw88_8822ce
10000:e0:1d.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI Express Root Port #9 [8086:a0b0] (rev 20)
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: SK hynix BC511 [1c5c:1339]
Subsystem: SK hynix Device [1c5c:0000]
Kernel driver in use: nvme
~$

Ramachandra Iyer · Post by **Ramachandra Iyer** » Tue Jun 22, 2021 7:24 am

my refind.conf

timeout 10
textonly on
textmode 0
showtools shutdown,reboot,firmware
#scan_all_linux_kernels off
#scanfor manual,internal
scanfor manual
menuentry "Slacko64" {
volume "slacko"
loader /slacko/vmlinuz
initrd /slacko/initrd.gz
ostype Linux
options "root=/dev/nvme0n1p6 ro"
}
menuentry "Antix (nvme5)" {
volume "rootantiX19"
loader /boot/vmlinuz-5.10.27-antix.1-amd64-smp
initrd /boot/initrd.img-5.10.27-antix.1-amd64-smp
ostype Linux
options "root=/dev/nvme0n1p7 ro"
}
menuentry "Windows 10" {
volume SYSTEM
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
}

greengeek · Post by **greengeek** » Tue Jun 22, 2021 7:57 am

When you are trying to boot from nvme is the bootable usb stick still inserted?

Ramachandra Iyer · Post by **Ramachandra Iyer** » Tue Jun 22, 2021 9:01 am

No Sir. What is the purpose. This is internal harddisk installation (frugal)

baldronicus · Post by **baldronicus** » Tue Jun 22, 2021 9:36 am

Hi again @Ramachandra Iyer . A few more things. Would you have written the last line of the /tmp/bootinit.log from memory, or is there a typo in there? When I was just successfully booting Slacko live, the entry for the sfs file looked different (although it did flash past quickly).

I don't know if you can use Puppy specific boot parameters in refind. Hence, it might be best to wait for someone who knows these things to provide an opinion on the following:

Perhaps it might help if you added pdrv=slacko to the boot parameters. (I think the partition label it is on is "slacko" from your entries). Please note that there are no parentheses in the parameter entry.

Is Slacko installed in it's own subdirectory?
If so, then maybe also adding psubdir= with the name of the sub-directory, might also help?

I have bold typed the parameters, but you wouldn't, of course.

Thanks.

PS- I am butting in again, but I think Greengeek might have been asking about the usb stick in order to confirm that it wasn't plugged in. If my understanding is correct, there can sometimes be problems when there are two flash memory based sources active at the same time, when attempting to boot off one of them.

rcrsn51 · Post by **rcrsn51** » Tue Jun 22, 2021 11:33 am

@Ramachandra Iyer: You asked for help with this issue in the Starter Kit section, then never returned.

You have a bootable slacko flash drive. So you could run the deblive-multi-installer off it using a Starter Kit ISO and do an nvme install.

Based on my own work with nvme drives, this has a good chance of working. It would also help to identify the problem in slacko.

There is no point in asking for help if you won't use the help you are given.

Ramachandra Iyer · Post by **Ramachandra Iyer** » Wed Jun 23, 2021 4:16 am

rcrsn51

Sir, Can you elaborate "deblive-multi-installer off it using a Starter Kit ISO and do an nvme install". Please note that I am an end user only. Please explain simple manner.

rcrsn51 · Post by **rcrsn51** » Wed Jun 23, 2021 10:36 am

Ramachandra Iyer wrote: ↑Wed Jun 23, 2021 4:16 am
rcrsn51

Sir, Can you elaborate "deblive-multi-installer off it using a Starter Kit ISO and do an nvme install". Please note that I am an end user only. Please explain simple manner.

If you want help with Starter Kit tools, you should go back to your request for help in that thread.

baldronicus · Post by **baldronicus** » Wed Jun 23, 2021 8:33 pm

Hi again @Ramachandra Iyer . I think I missed some stuff earlier.

The Slacko part of the refind configuration you gave earlier:

menuentry "Slacko64" {
volume "slacko"
loader /slacko/vmlinuz
initrd /slacko/initrd.gz
ostype Linux
options "root=/dev/nvme0n1p6 ro"
}

Is "slacko" (without quotes) the label of the partition on which you have installed Slacko?
Is "slacko" (again without quotes) also the name of the sub-directory in which the installer has placed the files?
I'm a bit rusty with use of the installer, but I would have expected something more like "slacko64-8.2.1", or so.

If you can boot Slacko live again (unless you are already sure of things) then you could check the the name of the sub-directory, and the label of the partition (if there is one- you could use GParted to check the label- although I suspect that you already know that).

In order to avoid confusion between the "slacko"s, the following is based on a situation where the label of the partition is "slacko" (again without quotes) and the sub-directory in which the Slacko files have been placed is "slacko64-8.2.1" (again without quotes).

menuentry "Slacko64" {
volume "slacko"
loader /slacko64-8.2.1/vmlinuz
initrd /slacko64-8.2.1/initrd.gz
ostype Linux
options "root=/dev/nvme0n1p6 pdrv=slacko psubdir=slacko64-8.2.1 ro"
}

As noted before, I am not familiar with refind. The above is what I expect might be worth a try (with the variables changed to match your exact situation, of course).

Thanks.

Ramachandra Iyer · Post by **Ramachandra Iyer** » Thu Jun 24, 2021 4:00 am

Dear baldronicus

Sir

As suggested by you, I will let you know the results after testing the same. Now I am in workplace and no access to my laptop.

Thanks for your suggestion.

Ram

baldronicus · Post by **baldronicus** » Thu Jun 24, 2021 7:18 am

Hi @01micko . Thanks for Slacko64-8.2.1.

Laptop: A4 9 series processor in a HP laptop- worked very nicely, thank you. The 2 barks were loud and clear and the system shutdown cleanly. This system has had a bit of a difficult history at times. One of the symptoms of trouble was not shutting down.

Desktops: Unfortunately I have run into a problem on three (3) desktop machines that I have tried it on. One has an ASUS motherboard, another an MSI, and the last an Asrock. The ASUS and MSI boards have B-450 chipsets and the Asrock an 880G. They are all running in CSM mode, and all have Radeon R7-240 graphics cards. The ASUS and MSI have MSI cards, the Asrock an HIS card.

They all boot and reach Quick Setup/First Run (I apologise for mixing terms). Then all input from the USB mouse and USB keyboard is lost. I don't know if it is significant, but in most (maybe all) cases the cursor has been resting on the keyboard numlock selection line, with the explanatory text info box open (I think this might really just be a default position). Quick Setup/First Run indicates that the ati driver is in use, and the indicated screen resolution is correct. It all looks good except for the loss of function.

I was messing up a lot of things last night (as Bigpup can attest ). However, I think I tried booting with nomodeset, and also tried the radeon and vesa options in xorgwizard, on one machine. This morning I also tried unplugging and re-inserting the USB plugs on another. All with no success. I can try again if you want me to. The third machine has older hardware, and the result there has led me to think it might involve either CSM or the Radeon cards (or both). If you want me check other stuff please just let me know.

Thanks (another great tome, apologies).
[Edit- Only to correct incorrect description of the problem to keep things tidy. Following a re-jig of the deck chairs on the Titanic, I tried Slacko64-8.2.1 again, on the machine with the 980 (not 880) based Asrock motherboard. This time with a HDMI connection to a Samsung monitor. All fine. No lock up. Hence it appears that the problems might have been with HDMI connections to Benq GW2270 and 2280 monitors. Again, not worrying with this, just correcting info.
Thanks.]
[Another Edit- I am an idiot and didn't think of the mouse. I was using the same type of mouse (a Genius one) with all three machines that had problems. A swap of the mouse on one of the machines confirmed that it was the problem, not any interaction with graphics cards and monitors etc.. Just the simple mouse, D'oh. Thanks.]

01micko · Post by **01micko** » Thu Jun 24, 2021 7:49 am

Hi @baldronicus thanks for testing.

TBH, I'm not happy with the 5.10.x series kernels as is Pat Volkerding who has bumped slackware-current to 5.12.x so I might follow suit for 8.2.2

I have have had a few lockups on the ASUS/ryzen board and 5.4 seems more stable. I will produce 3 sets of kernels for next release and post them for testing.

On another front, my NVMe drive arrived today and in a matter of minutes I installed, formatted and installed 8.2.1 built from latest woof, so it isn't identical to the one in the first post but the kernel configuration is, but bumped up to the latest patch level. Running sweetly, blazingly fast with grub2 - I'll post he stanza

Code: Select all

menuentry "Puppy slacko64 8.2.1" {
    insmod ext2
    search --no-floppy --fs-uuid --set  fac65aa2-84bf-4dde-949c-75fefeac5e29
    echo "Loading vmlinuz"
    linux /pups/vmlinuz pmedia=atahd pdrv=NVPUP psubdir=/pups pfix=fsck,fsckp,trim TZ=AEST-10
    echo "Loading initrd.gz"
    initrd /pups/initrd.gz
}

So I can only deduce that there is something wrong with @Ramachandra Iyer 's refind configuration. @rcrsn51 any ideas??

baldronicus · Post by **baldronicus** » Thu Jun 24, 2021 8:35 am

Thanks @01micko . Good that the NVMe is successful. Hopefully I won't get into trouble with the company, but "Is fast, is good" .
Thanks again.

hundido · Post by **hundido** » Thu Jun 24, 2021 11:09 am

@01micko Thank you for this slacko. I just made a USB stick with it tonight. I love it. I'm newer to puppy, and I really like this one.

@davids45 In your post, you have a picture of a crossword puzzle with a menu. In the menu is "night mode". Is that a blue light filter? It's missing in my menus. How do I put it there? Thank you for those pictures.

slacko64-8.2.1 first impressions:

It booted easily. I wish it defaulted to 1024x768 or even lower resolution on first boot up. I'm low vision and higher resolutions and smaller fonts are really challenging for me. Making the fonts larger systemwide and lowering the resolution worked, though, so now it's perfect.

I'm hoping for an awesome blue light filter that I can set to 1800k or lower. I'd like to learn to program one if it doesn't exist already.

I made a theme out of awesome things other people did that's probably my favorite desktop theme ever, called Eye Care 2. How do I share it here, if it's not already available to you all?

: Desktop2.jpg (108.82 KiB) Viewed 2517 times

I don't think the screen shot application is working, though. Does the picture just look like a bunch of lines to you, too?

hundido · Post by **hundido** » Fri Jun 25, 2021 2:52 am

I broke it. I pressed the save button to save downloading brave. Then before that was done, I went to changing the themes some more. It got stuck saving and changing the theme for a long time. Eventually I decided to hard power off the computer. My slacko stick won't boot anymore.

Time to remake it. Back to gparted, then frugal pup.

Ramachandra Iyer · Post by **Ramachandra Iyer** » Sat Jun 26, 2021 3:36 am

Dear baldronicus

I have applied your suggestions in the refind entry. Still it is not booting from internal hard disk. Is it possible to install hard disk (other than frugal method) through puppy installer. Is is possible to select particular partition or it will install entire disk. Due to fear I have not attempted that option in Puppy Installer option.

davids45 · Post by **davids45** » Sat Jun 26, 2021 3:39 am

G'day hundido,

@davids45 In your post, you have a picture of a crossword puzzle with a menu. In the menu is "night mode". Is that a blue light filter? It's missing in my menus. How do I put it there? Thank you for those pictures.

The Guardian cryptic puzzle was being viewed by a pdf viewer in a small window (not full screen). Is it the pdf viewer you're wanting details about?

I took a screen-shot (jpg) of this with Take-A-Shot using the window shot option (again not a full screen shot).

I probably then used Gimp to scale the jpg file to suit the size limits for this web-site.

I uploaded the jpg using the Attachments tab for this page (below this post).

David S.

baldronicus · Post by **baldronicus** » Sat Jun 26, 2021 11:16 pm

Hi @Ramachandra Iyer .

I have applied your suggestions in the refind entry. Still it is not booting from internal hard disk. Is it possible to install hard disk (other than frugal method) through puppy installer. Is is possible to select particular partition or it will install entire disk. Due to fear I have not attempted that option in Puppy Installer option.

Drats. Is it still not finding the .sfs file, or has the failure message changed?

It has been a while since I have used the installer (I tend to cheat and just copy the (what I think are) relevant files to a sub-directory). I don't know if the installer would even offer a full installation option these days. Frugal method is the default for Puppy, and I think trying to go to a full install at this stage would only complicate things, especially since the main reason for using a full install in the past has been a lack of ram, which won't apply in your case.

I have to admit that I am out of my league. My suggestions have essentially been attempts to apply parameters that I use with Grub to rEFInd, which may not be appropriate.

[EDIT- From reading some of your posts again, had you used the installer to make the frugal install, or had you done what I tend to do, and just copied the files across?]

The entry for psubdir that 01micko has, in the config he has provided, is different to the suggestion I had made. Maybe try adding the "/" in front of the sub-directory name in your config.
Maybe try adding this change, and check 01micko's entry again, for anything else that I might have missed.

Presumably the laptop is booting in UEFI mode,and has GPT partitions. [EDIT- maybe ignore the pmedia option for now. Apparently it might cause problems if it doesn't match with how the computer BIOS sees things.]

If I recall correctly Antix is installed on an ext4 partition, but Slacko is on a Fat32 one? Is there a reason you don't want to use ext4 for Slacko? Part of the reason for asking this is that I don't know how the rEFInd parameters treat things. If the OStype is given as Linux, is it expecting a Linux filesystem (although it is, at least, attempting to start, so maybe this isn't the problem)? Have you booted earlier Slacko installations on FAT32 filesystems with rEFInd before? I'm probably "barking up the wrong tree" with this question since EFI uses FAT32 as it's filesystem, but have to ask.

If all of the above still fails, could you please boot Slacko live, then check and provide the following (leave the USB stick in for the moment, as we will need to access the info from it)?:

a) Using GParted, check the labels on the both the Antix partition and the one you have slacko on.
If memory serves, I think the Antix one will be in capitals [EDIT- on reading again, it is lowercase in your config, and it works, and I might be getting mixed up with MXLinux]. Could you please provide the label of the partition Slacko is installed on, exactly as it appears in GParted? If there isn't one, please indicate so.
b) If there is no label on the partition with Slacko on it, could you right-click on that partition, select Information, and then copy the UUID (that I think will be displayed at the bottom of the dialog box) to a text file, that you can save, in case the info is needed later? Make sure that it is complete, and that leading or trailing entries haven't been missed.
c) Close GParted, and click on the desktop icon to mount the partition with Slacko on it. This should have opened the File Manager, displaying the contents of that partition. Is there a sub-directory? If so, what is it's name? If not, and all the files are "loose" on the partition, please indicate so.
d) If the sub-directory is present, are there any other files displayed with the sub-directory? If so, could you provide the names of those files?
e) The following is a check to make sure that things have copied across OK. They probably have, but it doesn't hurt to make sure. If the sub-directory is present, then go into it. If not, then apply the following with respect to the loose files. Open the desktop entry for the USB stick, and arrange things so that you can see, and select, items in both File Manager windows.
Some of the files on the USB will not have been copied to the NVMe, this is normal. However, all the .sfs files, and the vmlinuz and initrd.gz files should be present on both. If an .sfs file is missing on the NVMe, then copy it across from the USB (I doubt one will be, but have to mention it, just in case). Check that the names of all the files on the NVMe are consistent with those on the USB. Then check the file sizes by right-clicking on each respective file and selecting "Count".

[EDIT]- f) Actually, is there an empty text file on the NVMe called either "gpthd" or "atahd"? If so, try adding the pmedia= parameter to suit. I know I had suggested leaving it out, above. However, if the installer has identified things, then it might be worth trying it.

Although I have probably missed something, again, this is all I can think of at the moment.
Thanks.

baldronicus · Post by **baldronicus** » Sun Jun 27, 2021 5:49 am

Hi again, @Ramachandra Iyer . Please accept my apologies for the two posts, but this is an update that may, or not be relevant. I actually tried installing Slacko64-8.2.1 on an MSI Cubi-N in UEFI mode. Although I have briefly used it before, I had forgotten that the FrugalPup installer would be the default, and, as usual, was "living in the past". The "defined" initial sub-directory names aren't present either.

It did boot and runs well, but that was with Grub2, not rEFInd.

I presume that you have installed Slacko either by just copying selected files across, or by using only the "Puppy" button (i.e. not the "Boot" button as well) in FrugalPup. In my case FrugalPup copied across all the .sfs.files and the vmlinuz and initrd.gz files, which is what you would have probably done if manually copying them. It did, however add a blank text file named "AUTOSAVE", which, I suspect, is a flag regarding saves. I don't think it would impact the boot problem.

[Edit- removed potentially dangerous info that was wrong, as I hadn't read things properly. Should have tried reading at least twice before posting.]

Thanks.

Ramachandra Iyer · Post by **Ramachandra Iyer** » Sun Jun 27, 2021 6:53 am

Refind in separate partition is very safe. If not required just delete the partition. i dont want disturb windows 10.This idea got from easyos. I feel inherent issue with puppy linux while booting new nvme ssd. easyos also not booting from SSD. Is it possible to full install on separate partition. I would like to test full install. Only new kernels detecting the hard disk. Even though, not booting from internal hard disk. Sorry for the trouble.

01micko · Post by **01micko** » Sun Jun 27, 2021 9:34 am

Ramachandra Iyer wrote: ↑Sun Jun 27, 2021 6:53 am
Refind in separate partition is very safe. If not required just delete the partition. i dont want disturb windows 10.This idea got from easyos. I feel inherent issue with puppy linux while booting new nvme ssd. easyos also not booting from SSD. Is it possible to full install on separate partition. I would like to test full install. Only new kernels detecting the hard disk. Even though, not booting from internal hard disk. Sorry for the trouble.

Full install is a bad idea. We need to work through your problems logically, but we give up on this version for now. I intend to post 8.2.2 with 5.12 kernel soon.

Happy days!

hundido · Post by **hundido** » Wed Jul 07, 2021 10:13 pm

How does one install Keybase on this puppy?

Clarity · Post by **Clarity** » Sun Aug 01, 2021 9:12 am

Anyone know if there is a Slacko Menu entry to do an immediate Session-Save function?

Thanks in advance if you can identify.

Post by **bigpup** » Sun Aug 01, 2021 9:46 pm

Clarity wrote: ↑Sun Aug 01, 2021 9:12 am
Anyone know if there is a Slacko Menu entry to do an immediate Session-Save function?

I assume you want this for Slacko, running in pupmode 13, where you have to click on the desktop save icon or do a shutdown, to update the save.
In pupmode 12 operation, the save is auto updated, as things change.

I made this .desktop file to run the same thing the desktop save icon does.

Download it and place it in /usr/share/Applications

Save the change.

Run fixmenus, in a terminal, to get it showing in the menu.
May need to just do a save and a reboot, to get it showing.

It will be in menu->System

Note:
Rename file, removing .gz from end.
Had to add .gz to name, so it would attach.

update save.desktop.gz: (215 Bytes) Downloaded 70 times

peebee · Post by **peebee** » Sun Aug 15, 2021 8:19 pm

Slacko-8.2.2

dpkg-deb needs an update to handle zstd debs

Clarity · Post by **Clarity** » Mon Aug 16, 2021 7:40 pm

peebee wrote: ↑Sun Aug 15, 2021 8:19 pm
Slacko-8.2.2 ...

The 1st 2 posts of this thread only direct us to v8.2.1

Is there a way to get the v8.2.2 release for testing?

dimkr · Post by **dimkr** » Thu Sep 16, 2021 5:42 pm

Here's the memory consumption of a clean desktop, between 32-bit Slacko 7.x (kernel 4.19.x) and 8.x (kernel 5.10.x) built with woof-CE from 2 days ago. Both builds use GTK+ 2 and the two virtual machines are identical, so it's an apples-to-apples comparison.

: 7.png (54 KiB) Viewed 2455 times

: 8.png (58.29 KiB) Viewed 2455 times

Most of the difference comes from PulseAudio, and without it, it's a tiny 10 MB difference.

I find it amazing that Slackware 14.2 was released in 2016, and Slacko's RAM consumption hasn't changed much for 5 years.

Puppy Linux Discussion Forum

slacko64-8.2.1-alpha-alpha-beta+0 (slacko64-8.2.2 by norgo)

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0

Re: slacko64-8.2.1-alpha-alpha-beta+0