(old)Puppy Linux Discussion Forum

Posted: **Mon 29 Jan 2018, 10:31**

amn87,

If your computer is a laptop it could be using the Nvidia Optimus setup.
Basically it uses the Processors Intel Graphics for the normal stuff and Nvidia for high demand stuff.
Puppy is not setup to use this.
Puppy is using the Intel only, unless the computers bios has option to turn this off and only use the Nvidia hardware.

Try this:
In /etc/x11/xorg.conf.d
create an empty text file named 20-intel.conf.
Edit this empty file "20-intel.conf" and add the following content:

Code: Select all

n "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "uxa"
EndSection

Reboot.

Posted: **Mon 29 Jan 2018, 13:23**

Thanks for the response. Optimus is not to blame here as it was launched much later. Atleast with Kodi video playback which was the main issue has been taken care of. Although screen tearing persists elsewhere. The proprietary Nvidia drivers might have helped if nothing else but to tame the high GPU temps. but the links to the Nvidia SFS are broken. The drivers listed on Nvidia website for Linux 64-bit they can't be installed in Fatdog64, right? Although many years back I had installed them in Ubuntu without any modification.

Posted: **Mon 29 Jan 2018, 15:10**

I installed to a 32gb usb-3.0 flash drive:

System: Host: fatdog64-b6a Kernel: 4.14.12 x86_64 bits: 64 Desktop: Openbox 3.5.2 Distro: Fatdog64 Linux 721
Machine: Device: desktop Mobo: Acer model: Aspire X3950 serial: U02C120500059
BIOS: American Megatrends v: P01-A3 date: 05/05/2010
CPU: Dual core Intel Core i3 540 (-MT-MCP-) speed/max: 1333/3067 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.Org 1.19.5 driver: intel Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
OpenGL: renderer: Mesa DRI Intel Ironlake Desktop version: 2.1 Mesa 17.2.8
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W] driver: rt73usb
Drives: HDD Total Size: 531.6GB (0.5% used)
Weather: Conditions: 21 F (-6 C) - Mostly Cloudy Time: January 29, 9:51 AM EST
Info: Processes: 175 Uptime: 1:59 Memory: 866.4/5892.3MB Client: Shell (sh) inxi: 2.3.56

Added dosbox,gkrellm,inxi,Firefox Quantum 58.0.
Configured monitor positions with zarfy.

Works well so far,
Thanks.

Posted: **Mon 29 Jan 2018, 15:31**

Posted: **Mon 29 Jan 2018, 23:56**

I installed to a 32gb SDHC card:

I loaded fd64-devx_721.sfs,kernel-source-4.14.12.sfs, and downloaded NVIDIA-Linux-x86_64-390.25.run
from the nvidia site.The driver was just released today.

video-info-glx 1.5.3 Mon 29 Jan 2018 on Fatdog64 721 Linux 4.14.12 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v0p1 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.19.5
dimensions: 3200x900 pixels (883x251 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 390.25

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz

Seems to be working okay so far.
Thanks.

EDIT: Firefox Quantum is now at 58.0.1

Posted: **Tue 30 Jan 2018, 08:51**

@amn87, if the correct driver version for your nvidia is 340, then I have compiled 340.106 for Fatdog64-721. I uploaded and SFS here https://drive.google.com/open?id=12oXcb ... QXdLxmLHyR
This being an SFS, you need to load it early and to blacklist nouveau. Personally I do it by modifying the kernel line in the boot loader entry for Fatdog64-721, i.e.,

Code: Select all

kernel WHATEVER blacklist=nouveau extrasfs=label:LABEL:PATH-TO/NVIDIA_64_32_4_14_12-340.106-x86_64-1_721.sfs

where you should replace "LABEL" with the partition label of the disk, and "PATH-TO" with the full path of the directory where the SFS file is located in the disk, and "WHATEVER" is whatever is currently in the kernel line.
Note that Fatdog64's initrd supports other ways to specify file locations without partition labels - See FAQ in "Fatdog help".

Posted: **Tue 30 Jan 2018, 11:38**

I've mentioned before about an issue around being unable to kill certain apps - specifically wine / windows apps.

To recap, what would happen was that when running certain windows apps via wine - explorer.exe would start using a very high percentage of CPU. The process could not be killed despite trying everything.

I had not encountered this prior to the moving of spot from /root/ to /home/ in Fatdog v720.

For over a week now, I have used run-as-spot for all wine activities, with 'run-as-spot winecfg' initially to create /home/spot/.wine. All windows apps are run with run-as-spot prefix.

This so far has stopped the issue with explorer.exe resurfacing.

Posted: **Tue 30 Jan 2018, 17:34**

I used 710 until 721 came out, and even then I have been slow to begin with it. So, I am just now giving up on a problem I discovered with 721.
I think I read somewhere of something at least similar in a thread somewhere but I can not find it. I am using a Thinkpad X230T notebook with 16GB system RAM.
Just to get started, I burned 721 on a CD and it seems to work perfectly until I close the screen down. When I lift it back up all seems to look OK except that the wpa-gui shows I have a connection but no IP address is listed. A browser can not connect.
I have tried to find a way around this to no avail. I can "suspend" 721 from the menu and everything will restore OK. Only when I close the display down to the keyboard does this problem occur.
A fresh boot works OK until, again, I close the screen down.
Sorry if this has already been addressed, but I can't find it.

Posted: **Tue 30 Jan 2018, 19:14**

DrDeaf wrote:I used 710 until 721 came out, and even then I have been slow to begin with it. So, I am just now giving up on a problem I discovered with 721.
I think I read somewhere of something at least similar in a thread somewhere but I can not find it. I am using a Thinkpad X230T notebook with 16GB system RAM.
Just to get started, I burned 721 on a CD and it seems to work perfectly until I close the screen down. When I lift it back up all seems to look OK except that the wpa-gui shows I have a connection but no IP address is listed. A browser can not connect.
I have tried to find a way around this to no avail. I can "suspend" 721 from the menu and everything will restore OK. Only when I close the display down to the keyboard does this problem occur.
A fresh boot works OK until, again, I close the screen down.
Sorry if this has already been addressed, but I can't find it.

I have had suspend issues with wpa-gui on one particular Dell laptop for a while. I haven't solved it yet, but I can get around it by right clicking the wpa-gui icon and clicking "restart connection". Have you already tried that?
jamesbond gave me instructions for adding a hook.

jamesbond wrote:The suspend/wakeup script is located at /etc/acpi/actions/suspend.sh. The default contents stops network before suspend, and re-starts it after resume. If network doesn't work well after resume, it might well be the network driver. The usual suggested approach is to unload the network driver ("rmmod module-name") and load it again after suspend.
[quote/]
I still haven't dug into making it work, but I expect it will work in my case when I apply it correctly.

Posted: **Tue 30 Jan 2018, 19:52**

@jake29, I haven't announced it, yet, but I built wine-3.0 SFS. Load it from SFS manager for a test run. Backup spot's wine prefix to be safe. It's working well for me.

Posted: **Tue 30 Jan 2018, 20:33**

Hey dr. Dan, thanks! I had tried killing the connection and scanning again, going through the Control Panel to Network Setup... but I didn't know about this way.
It works here too.

Posted: **Tue 30 Jan 2018, 23:52**

step wrote:@jake29, I haven't announced it, yet, but I built wine-3.0 SFS. Load it from SFS manager for a test run. Backup spot's wine prefix to be safe. It's working well for me.

Thanks for the reply. It would appear I am eternally stuck at Wine 2.7. With Wine 2.8 and newer, significant changes where made to the way speech-support (sapi) is implemented. Wine 2.7 or older uses the WinXP system, anything newer than Wine 2.7 uses the Win7 system.

I cannot make the Text-to-speech (TTS) voices, or the reader app I use everyday to work on anything newer than Wine 2.7. I have tried previously different solutions, and I've tried once again a moment ago. TBH, I don't really need anything newer than Wine 2.7, and I feel that I have resolved the issue mentioned in my last post. I'm very happy with my current Wine setup.

So alas, I will not be joining you in your future adventures with Wine 3.0 and beyond. Unless of course, some new and mind-blowing TTS software arrives that is compatible.

Posted: **Wed 31 Jan 2018, 03:34**

On my Lenovo Thinkpad W510 Fatdog64-721 does not support wifi

Posted: **Wed 31 Jan 2018, 06:23**

@Gordie, perhaps you need to add a kernel module specific to your adapter. In brief, connect to the Internet somehow, start SFS Manager from Control Panel > System, download and load the "additional firmware SFS", depmod the kernel module of your interest (this might be a bit difficult if are inexperienced with depmod), test wifi by clicking "Restart Connection" from the right click menu of the wpa_gui icon in the tray (read Fatdog's Networking help topic for more info). If wifi works then you can make the changes permanent by extracting from the SFS the module files of your interest and adding them to the file system.
Please report the make and model of your wireless adapter so we can add it to the ISO. To keep Fatdog slim the ISO doesn't include all possible firmware but just a selection of mainstream hardware. Occasionally we need to tune the selection. This is better explained in the second post in this thread.
Other people before you have had this problem, so you can search this thread for more tips and additional instructions.

Posted: **Wed 31 Jan 2018, 09:27**

I see, when I shutdown Fatdog 720, sometimes it immediately shows me "Fatdog is shutting down...", but many times it shows me this message after a long time. Till then, screen is black/blank and a single cursor on left top.

Any idea?

My savefile is 4GB ext4. But on Fatdog 611 also my save file was this big and ext4. Then, shutdown was always immediate.

Sincerely,
Srinivas Nayak

Posted: **Wed 31 Jan 2018, 09:43**

What is the best way to add a debian repository to gslapt and which debian version should be added?

Posted: **Wed 31 Jan 2018, 12:31**

Thanks for the link. Got it working. Finally have a ripple-free desktop.
I do have a few issues:
1.I installed Chrome from FD's Control Panel but it does not start at all. Ditto for FF 58? although I had been warned about missing dependencies .
Lxterminal output:
firefox
XPCOMGlueLoad error for file /usr/lib64/firefox-58.0.1/libmozgtk.so:
libgtk-3.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
2. Everytime I boot the Wifi is switched off(the wifi/bt toggle button ihas reverted to the off state). I have to type rfkill unblock all and restart connection to switch wifi on. Is their a way to run it via startup via a script or something?

step wrote:@amn87, if the correct driver version for your nvidia is 340, then I have compiled 340.106 for Fatdog64-721. I uploaded and SFS here https://drive.google.com/open?id=12oXcb ... QXdLxmLHyR
This being an SFS, you need to load it early and to blacklist nouveau. Personally I do it by modifying the kernel line in the boot loader entry for Fatdog64-721, i.e.,
Code: Select all
kernel WHATEVER blacklist=nouveau extrasfs=label:LABEL:PATH-TO/NVIDIA_64_32_4_14_12-340.106-x86_64-1_721.sfs
where you should replace "LABEL" with the partition label of the disk, and "PATH-TO" with the full path of the directory where the SFS file is located in the disk, and "WHATEVER" is whatever is currently in the kernel line.
Note that Fatdog64's initrd supports other ways to specify file locations without partition labels - See FAQ in "Fatdog help".

Posted: **Wed 31 Jan 2018, 15:19**

snayak wrote:I see, when I shutdown Fatdog 720, sometimes it immediately shows me "Fatdog is shutting down...", but many times it shows me this message after a long time. Till then, screen is black/blank and a single cursor on left top.

Any idea?

My savefile is 4GB ext4. But on Fatdog 611 also my save file was this big and ext4. Then, shutdown was always immediate.

1. Other than this "slowdown", does your system not shutdown correctly?
2. How long is the "slowdown"?

My guess is that while the cursor blinks in the top-left corner the system is syncing your disks to prevent data loss. This is normal and it's done on purpose. Depending on your disk cache state, it may take an instant to several seconds, even 20-30 seconds if you just performed a large file transfer to/from a USB stick before shutting down. You could try the following to confirm that syncing is the reason for slow shutdowns.

Before shutdown, on every shutdown, close all applications and open a terminal window. Type sync and press ENTER. When the prompt returns - it may take some several seconds before it does - close the window and perform shutdown. Is the shutdown process slow?

If, by repeating those steps on every shutdown, for several shutdowns, you can observe no slowdowns, then syncing was probably what you interpreted as slow shutdowns before.

Posted: **Wed 31 Jan 2018, 15:32**

Anniekin wrote:What is the best way to add a debian repository to gslapt and which debian version should be added?

Fatdog doesn't have an apt-get package manager, so you can't add a debian repository directly. If you have a specific deb package file, and want to convert it to the Fatdog64 package format, you can right click the deb file icon and select "Convert to Fatdog package format". Be aware that this is a straight format conversion, and debian package control and install scripts are stripped off in the conversion. Notably, the conversion doesn't check for dependencies, that is you will not be informed if you need to also install supporting libraries. This step is typically apt-get's job.

Fatdog64 does have dpkg, another debian package manager. However, it's a cut-down version. I seem to remember someone compiled the full dpkg binary for Fatdog64 and made it available, but I don't recall where. Anyhow, dpkg deals with local files, so again it can't be used to directly interface a debian repository.

edit: the full dpkg package is available in the official Fatdog64 package repository.

Posted: **Wed 31 Jan 2018, 15:57**

amn87 wrote:Thanks for the link. Got it working. Finally have a ripple-free desktop.
I do have a few issues:
1.I installed Chrome from FD's Control Panel but it does not start at all. Ditto for FF 58? although I had been warned about missing dependencies .
Lxterminal output:
firefox
XPCOMGlueLoad error for file /usr/lib64/firefox-58.0.1/libmozgtk.so:
libgtk-3.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

Recent versions of FF and Chrome depend on GTK3. Did you install the gtk3 package before trying to start FF or Chrome?
Those browsers might have other dependencies, I'm not too current. Here's a list of dependencies I made for Opera, which uses Chromium, so it should help you for Chrome at least. Omit libnotify, because I don't think Chrome needs that.

Code: Select all

  at-spi2-atk-2.18.1-x86_64-1
  at-spi2-core-2.18.3-x86_64-1
  gtk3-3.18.7-x86_64-1
  libnspr-4.17-x86_64-1
  libnss-3.33-x86_64-1
  libnotify-0.7.7-x86_64-1

2. Everytime I boot the Wifi is switched off(the wifi/bt toggle button ihas reverted to the off state). I have to type rfkill unblock all and restart connection to switch wifi on. Is their a way to run it via startup via a script or something?

Maybe this script

Code: Select all

#!/bin/dash
sleep 5
rfkill unblock wlan
/etc/init.d/50-Wpagui restart

Put it in /root/Startup/restart-wlan.sh, and make it executable.
This script will be executed each time Xorg starts.

Alternatively, you could disable execution for the script, and call it directly from /etc/rc.d/rc.local:

Code: Select all

dash /root/Startup/restart-wlan.sh

This way the script runs only when Fatdog64 boots up.

(old)Puppy Linux Discussion Forum

Fatdog64-720 and 721 Final [11 Jan 2018]

Fatdog64-720 and 721 Final [11 Jan 2018]

Re: Fatdog64-720 and 721 Final [11 Jan 2018]

Fatdog64-720 and 721 Final [11 Jan 2018]

run-as-spot wine

Re: run-as-spot wine

Re: run-as-spot wine