(old)Puppy Linux Discussion Forum

@cthisbear

I supposed to consider that however those drivers were kernel modules which was very sensitive to kernel versions. X-Slacko Slim currently uses 4.17.x kernel while the given drivers was for 4.1.x so it is mismatch

firmware drivers will work just fine regardless of kernel version so I will add it to my fdrv collection

Chris, I guess it's not related to me, right?

mistfire wrote:@cthisbear

I supposed to consider that however those drivers were kernel modules which was very sensitive to kernel versions. X-Slacko Slim currently uses 4.17.x kernel while the given drivers was for 4.1.x so it is mismatch

firmware drivers will work just fine regardless of kernel version so I will add it to my fdrv collection

The confirmed working sources for the driver cthisbear is talking about are here
https://github.com/zebulon2/rtl8812au

.

mistfire wrote:

if you are fluent in bash scripting take a look at load-power-cfg and power_gui scripts as well as check-power in /root/Startup

I found no errors on those scripts, but showed that DPMS was disabled at bootup.

I have placed a script in /root/Startup like this:
and now on reboots the monitor shuts down automatically at the given period of time set with ppower tray applet. Problem solved! Thanks!

Side note: if I omit the initial 'sleep 30', dpms stays disabled, maybe because there are other power management scripts running at the same time that interfere with my script.

mistfire,

I got this 2 packages are needed to access exFat:

https://slackbuilds.org/repository/14.1 ... use-exfat/
https://slackbuilds.org/repository/14.1 ... fat-utils/

Can u provide them as dotpets to add to X-Slacko Slim 4.4r23?

mistfire,

When I try to open tar.gz files I started getting this:

GConf error

GConf error: No database available to save your configuration: Unable to store a value at key '/apps/file-roller/general/migrate_directories', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf

What should I do?

@kuman11
Try to boot X-Slacko Slim on its pristine state

New X-Slacko Slim iteration released

Changes:
* Linux kernel 4.9.x
* Modular design. kernel modules now resides in zdrv sfs file. It can now easily swap kernel and kernel modules
* SFS load now supports Porteus (*.lzm and *.xzm) and Slax modules. No need to change file extension to .sfs (Also it can be install as package by using petget)
* Installing Tiny Core Linux extension (*.tce,*.tcel,*.tcem) is now supported by petget
* Improved PPM
* Improved handling of multiple screen
* Improved initrd
* Some bugfixes

Download: https://drive.google.com/file/d/1D-lQfh ... sp=sharing
MD5 Checksum: 5889180893e5f1f4195d69f87a89d4c7

Version 4.4.r24 frugally installed and working well, thank you. I noticed that message 'updating layered sfs... next boot will be faster' is shown on every reboot. Will the next boot ever be faster, and the message go away?

@step probably yes.

Frugal install to HD on Dell Latitude E6400, all seems well, except for a small issue:

Waking from sleep mode produces high pitched beeps from the speakers.
This seems to be a new issue with the latest version.

I've tried disabling the Power Manager, but the problem persists.

@westwest try to swap kernel using kernel of other puppies. Just placed the vmlinuz beside the puppy_xslacko_4.4.sfs and copy the zdrv file of a corresponding puppy beside also the puppy_xslacko_4.4.sfs rename the corresponding zdrv file as zdrv_xslacko_4.4.sfs and you are good to go

My thoughts
I'm glad that some Puppy devs involved in Woof-CE noticed and considered my logic and stuffs here in Puppy Forum.

mistfire,

is the new version compatible with the newest Firefox?

I tried to install the new one on the usb and it failed. Got xslacko_4.4.sfs not found upon rebooting. It reappears constantly. What should i do?

@kuman

Im not sure but you can try to install firefox.

did you put the main sfs files of x-slacko slim in a folder? if yes, specify the foldername on your bootloader settings using this

It takes me to a blue screen w 3 options - save, go to prompt, reboot. I've made a mistake, to put the .iso file in a folder while the others are not. Do i need to put the name of it in brackets? I did it at the prompt & it didn't work. I've not decompressed the .iso too.

How can I go to the initial boot menu to load it to ram, too?

@kuman11 brackets are only placeholder just substitute it with the folder name (without bracket) where the X-Slacko Slim is saved.

If you are using syslinux, just press tab in order to edit the boot settings, press enter to apply. for grub press e edit boot settings, press b or F10 to apply

What about decompressing .iso?