X-Slacko Slim 4.4r49 (unique, stable, and flexible)
This X-Slacko doesn't recognize the exFat USB sticks
This X-Slacko doesn't recognize the exFat USB sticks. Any ideas how can I mount them?
@kuman try to mount manually using this parameter
Code: Select all
mount -t exfat [drive] [mountpoint]
Example:
mount -t exfat /dev/sda1 /mnt/sda1
Please consider adding
Simplecom NW601 Wireless USB
How to use Simplecom NW601 Wireless USB? (Solved)
http://murga-linux.com/puppy/viewtopic. ... 29#1008529
No recent Pups have this incuding,
UPup Bionic Beaver
Bionicpup64
32-bit UPup Cosmic Cuttlefish
X-Slacko Slim
Page one Murga.
http://murga-linux.com/puppy/viewtopic.php?t=114560
::
perdido supplied these with help from Semme.
Both work after a reboot.
However I prefer for banking to boot a pristine Puppy,
add my stored bookmarks, and usually Slimjet and off I go.
http://ibm-pc.org/puppy/rtl8812au_rtl88 ... 4.1.48.pet
http://ibm-pc.org/puppy/rtl8812au-5.1.5_k4.1.48.pet
:::::
Linux Drivers from Simplecom site:
https://www.simplecom.com.au/media/link ... _linux.zip
Many thanks...Chris.
Simplecom NW601 Wireless USB
How to use Simplecom NW601 Wireless USB? (Solved)
http://murga-linux.com/puppy/viewtopic. ... 29#1008529
No recent Pups have this incuding,
UPup Bionic Beaver
Bionicpup64
32-bit UPup Cosmic Cuttlefish
X-Slacko Slim
Page one Murga.
http://murga-linux.com/puppy/viewtopic.php?t=114560
::
perdido supplied these with help from Semme.
Both work after a reboot.
However I prefer for banking to boot a pristine Puppy,
add my stored bookmarks, and usually Slimjet and off I go.
http://ibm-pc.org/puppy/rtl8812au_rtl88 ... 4.1.48.pet
http://ibm-pc.org/puppy/rtl8812au-5.1.5_k4.1.48.pet
:::::
Linux Drivers from Simplecom site:
https://www.simplecom.com.au/media/link ... _linux.zip
Many thanks...Chris.
@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
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
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
The confirmed working sources for the driver cthisbear is talking about are heremistfire 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
https://github.com/zebulon2/rtl8812au
.
mistfire wrote:
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.
I found no errors on those scripts, butif 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
Code: Select all
xset -q
I have placed a script in /root/Startup like this:
Code: Select all
!#/bin/bash
sleep 30
xset +dpms &
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?
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?
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?
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
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?
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
wake noise
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.
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.