TazPuppy 5.0 rc2
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
@mistfire
The following is the xorg.conf
The following is the xorg.conf
Code: Select all
#barry Kauler 2011
#pre-constructed xorg.conf, for use by /usr/sbin/xorgwizard-automatic
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "synaptics" #loadsynaptics
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
EndSection
# **********************************************************************
# Files section. This allows default font paths to be set
# **********************************************************************
Section "Files"
# Multiple FontPath entries are allowed
FontPath "/usr/share/X11/fonts/misc/"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/TTF/"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Enables mode switching with xrandr
Option "RandR" "on"
# With this, Xorg won't talk to udev to add evdev devices
# and you'll be back with the old Xorg behavior (pre-7.4)...
Option "AutoAddDevices" "false"
# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...
Option "DontZap" "false"
EndSection
# ===============================================================
Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "jp106" #xkbmodel0
Option "XkbLayout" "jp" #xkeymap0
#Option "XkbVariant" "" #xkbvariant0
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
# HorizSync 35-81
# VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
# Option "PreferredMode" "1024x768" #monitor0prefmode
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
Section "Device"
Identifier "Card0"
# Driver "vesa" #card0driver
# VendorName "Unknown Vendor"
# BoardName "Unknown Board"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
# DefaultDepth 24
#Option "metamodes" "1280x800_60 +0+0" #METAMODES_0
Subsection "Display"
# Depth 24 #screen0depth
# Modes "1024x768" #screen0modes
EndSubsection
EndSection
Thanks @thinkpadfreak, this time can you please boot tazpuppy on your computer with synaptics touchpad in pristine state and login as root. Then run this command
This will create xorg.conf.new file in /root folder and post here the xorg.conf.new that was generated.I will compare the two xorg conf files
Code: Select all
Xorg -configure :2
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
@mistfire
It seems there is no such words as "synaptics" in xorg.conf.new.
xorg.conf.new
It seems there is no such words as "synaptics" in xorg.conf.new.
xorg.conf.new
Code: Select all
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" RightOf "Screen1"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/X11/modules"
FontPath "/usr/share/fonts/X11/misc/"
FontPath "/usr/share/fonts/X11/TTF/"
FontPath "/usr/share/fonts/X11/OTF/"
FontPath "/usr/share/fonts/X11/Type1/"
FontPath "/usr/share/fonts/X11/100dpi/"
FontPath "/usr/share/fonts/X11/75dpi/"
EndSection
Section "Module"
Load "dbe"
Load "dri"
Load "dri2"
Load "extmod"
Load "glx"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "kmsdev" # <str>
#Option "ShadowFB" # [<bool>]
Identifier "Card0"
Driver "modesetting"
BusID "PCI:0:1:0"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # <str>
#Option "fbdev" # <str>
#Option "debug" # [<bool>]
Identifier "Card1"
Driver "fbdev"
BusID "PCI:0:1:0"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card2"
Driver "vesa"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "Card2"
Monitor "Monitor2"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
@thinkpadfreak based on the xorg.conf file that you given to me and also based on the puppy's xorgwizard scripts. I made a strategy, upon generating a new xorg file. It probes for synaptic touchpad. If it was detected then a new section for synaptics touchpad append on the newly generated xorg file before splitting it into different configuration.
On my latest experiment I made improvements on alsa automatic configuration as well as on synaptics touchpad.
UPDATE: flsynclient read settings at xorg.conf file not in /etc/xorg.conf.d I need to change strategy
On my latest experiment I made improvements on alsa automatic configuration as well as on synaptics touchpad.
UPDATE: flsynclient read settings at xorg.conf file not in /etc/xorg.conf.d I need to change strategy
I would like an option to have the tmp folder binded from the USB drive instead of residing in ram.
I created a thread about this:
"bind tmp folder to USB instead of having it in pure ram"
I created a thread about this:
"bind tmp folder to USB instead of having it in pure ram"
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
mistfire wrote:
> I make some improvements on Xorg autoconfig.
It may be too late, but ...
One of the Puppy Linux Japanese Forum members suggests making a change in the file /etc/X11/xorg.conf.d/01-ServerFlags.conf.
If Option "AutoAddDevices" is changed to "true," flsynclient starts successfully.
He suspects that, with the above option "false," other files in /etc/X11/xorg.conf.d are not read.
> I make some improvements on Xorg autoconfig.
It may be too late, but ...
One of the Puppy Linux Japanese Forum members suggests making a change in the file /etc/X11/xorg.conf.d/01-ServerFlags.conf.
If Option "AutoAddDevices" is changed to "true," flsynclient starts successfully.
He suspects that, with the above option "false," other files in /etc/X11/xorg.conf.d are not read.
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
mistfire wrote:
> I wonder why Barry set the AutoAddDevices to false on xorg config?
I do not know much about X configuration. I looked into some recent Puppies.
I think older Puppies did not have the directory /etc/X11/xorg.conf.d.
For example, Tahrpup does not have the directory.
Xenialpup does have the directory, but uses xorg.conf (not an empty file).
Option "AutoAddDevices" is set as "false."
UpupBB has the directory, but uses xorg.conf (not an empty file).
Option "AutoAddDevices" is set as "true."
Edit:
The following is a quotation from ftp://www.x.org/pub/X11R7.7-RC1/doc/man ... l#heading5
> I wonder why Barry set the AutoAddDevices to false on xorg config?
I do not know much about X configuration. I looked into some recent Puppies.
I think older Puppies did not have the directory /etc/X11/xorg.conf.d.
For example, Tahrpup does not have the directory.
Xenialpup does have the directory, but uses xorg.conf (not an empty file).
Option "AutoAddDevices" is set as "false."
UpupBB has the directory, but uses xorg.conf (not an empty file).
Option "AutoAddDevices" is set as "true."
Edit:
The following is a quotation from ftp://www.x.org/pub/X11R7.7-RC1/doc/man ... l#heading5
It seems that the way of recognizing devices is changing now.Option "AutoAddDevices" "boolean"
If this option is disabled, then no devices will be added from the HAL or udev backends. Enabled by default.
@thinkpadfreak luckily my pc touchpad was synaptic. I try to use the former method in tazx script and based to your suggestion to set AutoAddDevices. flsynclient now works. So I revert back the tazx back to beta 5 and make some improvements. This time AutoAddDevices is now enabled and upon triggering xorg autoconfig, the display settings of different DE's will be reset.
I got the following error with dropbox (installed via the get-dropbox package)
At the moment I'm trying a different approach. I'm going to try running dropbox in chroot version of asciidog built via:
http://murga-linux.com/puppy/viewtopic. ... 908#996908
my script to create the chroot environment can be found at:
https://pastebin.com/dhyBd8ZH
Note that fredx181's script to build ascii dog must be run twice because the first time it will download the devuan version of debootstap which must be converted to a tazpkg and installed. Once debootstrap is installed the script will build asciidog but I'm missing the function to create the iso at the end of the script. Fortunately, I don't need to create the iso.
My script will then merge the two relevant folders into a ram disk that is capped at 250 mega bytes. If it grows more than this the system swaps it out of memory. The memory footprint will be small though because I'm maximizing the use of binds and symbolic links.
The script is preliminary. I will make a separate post about it once it has been tested more.
I don't think that there is much we can do because the version of glibc is too old on tazpup. It is possible to install a second instance of glibc and I may try that but I think I'll need to compile it.Error
You cannot log in to the Dropbox desktop app because your device is running an unsupported operating system.
You must now be on glibc 2.19 or higher to log back in and use the Dropbox desktop application. We recommend that you update to a supported Linux operating system (Ubuntu 14.04+ or Fedora 21+) or meet the new system requirements.
Additionally, your Dropbox folder will need to be on an ext4-formatted hard drive or partition.
At the moment I'm trying a different approach. I'm going to try running dropbox in chroot version of asciidog built via:
http://murga-linux.com/puppy/viewtopic. ... 908#996908
my script to create the chroot environment can be found at:
https://pastebin.com/dhyBd8ZH
Note that fredx181's script to build ascii dog must be run twice because the first time it will download the devuan version of debootstap which must be converted to a tazpkg and installed. Once debootstrap is installed the script will build asciidog but I'm missing the function to create the iso at the end of the script. Fortunately, I don't need to create the iso.
My script will then merge the two relevant folders into a ram disk that is capped at 250 mega bytes. If it grows more than this the system swaps it out of memory. The memory footprint will be small though because I'm maximizing the use of binds and symbolic links.
The script is preliminary. I will make a separate post about it once it has been tested more.
Last edited by s243a on Sat 03 Nov 2018, 06:33, edited 1 time in total.
I don't think this is fixed yet, but I could be wrong. Anyway I think what needs to be changed iss243a wrote:On previous versions of TazPup, the iron browser was the most capable browser that worked with TazPup. On the latest update it doesn't work. Strace tells me that it is trying to access shared memory.
The strace suggests the following fix:Code: Select all
open("/home/tux/.config/chromium/Default/Visited Links", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory) read(38, "\375\313W@T\31\257p", 8) = 8 clock_gettime(CLOCK_MONOTONIC, {16980, 337363961}) = 0 clock_gettime(CLOCK_MONOTONIC, {16980, 337428181}) = 0 gettimeofday({1539064712, 317493}, NULL) = 0 open("/dev/shm/.org.chromium.Chromium.prKdV8", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EACCES (Permission denied) clock_gettime(CLOCK_MONOTONIC, {16980, 337645474}) = 0 gettid() = 31887 time(NULL) = 1539064712 write(2, "[31887:31887:1009/065832:ERROR:s"..., 151[31887:31887:1009/065832:ERROR:shared_memory_posix.cc(302)] Creating shared memory in /dev/shm/.org.chromium.Chromium.prKdV8 failed: Permission denied ) = 151 access("/dev/shm", W_OK|X_OK) = -1 EACCES (Permission denied) gettid() = 31887 time(NULL) = 1539064712 write(2, "[31887:31887:1009/065832:ERROR:s"..., 116[31887:31887:1009/065832:ERROR:shared_memory_posix.cc(305)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied ) = 116 gettid() = 31887 time(NULL) = 1539064712 open("/proc/self/status", O_RDONLY|O_LARGEFILE) = 58 read(58, "Name:\tiron\nUmask:\t0022\nState:\tR "..., 1024) = 1024 close(58) = 0 write(2, "[31887:31887:1009/065832:FATAL:s"..., 164[31887:31887:1009/065832:FATAL:shared_memory_posix.cc(307)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. ) = 164 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 tgkill(31887, 31887, SIGABRT) = 0 --- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=31887, si_uid=1000} --- +++ killed by SIGABRT +++ Aborted
but I'm not sure that's safe.Code: Select all
write(2, "[31887:31887:1009/065832:FATAL:s"..., 164[31887:31887:1009/065832:FATAL:shared_memory_posix.cc(307)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.
tmpfs /dev/shm tmpfs noexec,nosuid 0 0
Code: Select all
tmpfs /dev/shm tmpfs noexec,nosuid 0 0
@s243a
That was weird. I already set the permission of /dev/shm to 1777 when the system boots up take a look at /etc/rc.d/rc.sysinit that was supposed to be work. May I know where did you get that iron browser? I will try to download it
Also I found something weird on loading the save file (not save folder) in TazPuppy. The /initrd/mnt/dev_save mountpoint cannot be accesed by ordinary user account only the root account can. Even I set the permission to 1777 it still cannot be accesed by ordinary user.
That was weird. I already set the permission of /dev/shm to 1777 when the system boots up take a look at /etc/rc.d/rc.sysinit that was supposed to be work. May I know where did you get that iron browser? I will try to download it
Also I found something weird on loading the save file (not save folder) in TazPuppy. The /initrd/mnt/dev_save mountpoint cannot be accesed by ordinary user account only the root account can. Even I set the permission to 1777 it still cannot be accesed by ordinary user.
@s243a it seems my approach on /dev/shm does not work. I made a test by typing this command
Code: Select all
echo 1 > /dev/shm/file
Just search the tazpup package manager for "iron". I believe that it is called "iron-linux" in the package manager.mistfire wrote:@s243a
That was weird. I already set the permission of /dev/shm to 1777 when the system boots up take a look at /etc/rc.d/rc.sysinit that was supposed to be work. May I know where did you get that iron browser? I will try to download it
Also I found something weird on loading the save file (not save folder) in TazPuppy. The /initrd/mnt/dev_save mountpoint cannot be accesed by ordinary user account only the root account can. Even I set the permission to 1777 it still cannot be accesed by ordinary user.
TazPuppy Beta 6 released
Changes:
* Automatic configuration now works on sound cards. Its alsa configuration is now located at /etc/asound.state
* Improved Xorg autoconfiguration for synaptic touchpads as well as autoconfiguration for backlights.
* Boots more faster due to fixes in sfs load
* /dev/shm permission fixed
* Tazpanel fixed
* 3G modem dialer and PPPOE is now separated application
* With GNOME PPP for dialup support
* Basic hotkey now working (Win key for application menu, CTRL+ALT+DELETE for task manager, and Print Screen for screenshot)
* More fixes
Download: https://drive.google.com/file/d/1uyu5c0 ... sp=sharing
Build kit: https://drive.google.com/file/d/1SOZx6q ... sp=sharing
Changes:
* Automatic configuration now works on sound cards. Its alsa configuration is now located at /etc/asound.state
* Improved Xorg autoconfiguration for synaptic touchpads as well as autoconfiguration for backlights.
* Boots more faster due to fixes in sfs load
* /dev/shm permission fixed
* Tazpanel fixed
* 3G modem dialer and PPPOE is now separated application
* With GNOME PPP for dialup support
* Basic hotkey now working (Win key for application menu, CTRL+ALT+DELETE for task manager, and Print Screen for screenshot)
* More fixes
Download: https://drive.google.com/file/d/1uyu5c0 ... sp=sharing
Build kit: https://drive.google.com/file/d/1SOZx6q ... sp=sharing
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
Mistfire, thank you for various improvements in beta 6.
Now, the synaptics touchpad is recognized and flsynclient starts successfully.
Xorg configuration introduces modesetting driver. I changed xorg.conf to use radeon driver. This does not matter much, I think.
I am glad that sfs_load does not take time at boot.
Before beta 6, I had difficulty enabling the default sound card, because the machine ThinkPad X121e has HDMI output. Now configuring the sound card has become much easier.
However, I am afraid the volume setting is not saved. This seems to be true of some recent versions.
To save the volume setting, I make a link /etc/asound.state pointing to /var/lib/alsa/asound.state. Then I execute the command alsactl store, which seems to save to /var/lib/alsa/asound.state.
Edit
The link got replaced by a new file at reboot. I changed the method as follows:
Now, the synaptics touchpad is recognized and flsynclient starts successfully.
Xorg configuration introduces modesetting driver. I changed xorg.conf to use radeon driver. This does not matter much, I think.
I am glad that sfs_load does not take time at boot.
Before beta 6, I had difficulty enabling the default sound card, because the machine ThinkPad X121e has HDMI output. Now configuring the sound card has become much easier.
However, I am afraid the volume setting is not saved. This seems to be true of some recent versions.
To save the volume setting, I make a link /etc/asound.state pointing to /var/lib/alsa/asound.state. Then I execute the command alsactl store, which seems to save to /var/lib/alsa/asound.state.
Edit
The link got replaced by a new file at reboot. I changed the method as follows:
Code: Select all
# alsactl store
# cp /var/lib/alsa/asound.state /etc/asound.state