Valentyn's questions

I have found few questions(1,2) and articles on the web about how to control fan speed. However, it seems that Lenovo ThinkPads need to be configured differently(1). However, there is nothing about ThinkStations. Did anyone try to get fan speed control on ThinkStation? If Yes, did it work and how did you set it up?

Here what I have tried:

Running sudo sensors-detect shows only one sensor

#----cut here----
# Chip drivers
coretemp
#----cut here----

Following instruction at here, installed thinkpad

$ sudo apt-get install thinkfan
Reading package lists... Done
Building dependency tree       
Reading state information... Done
thinkfan is already the newest version (0.9.3-2).
The following packages were automatically installed and are no longer required:
  linux-headers-4.15.0-51 linux-headers-4.15.0-51-generic linux-headers-4.15.0-55 linux-headers-4.15.0-55-generic
  linux-image-4.15.0-51-generic linux-image-4.15.0-55-generic linux-modules-4.15.0-51-generic linux-modules-4.15.0-55-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded.

but I cannot load the module

$ sudo modprobe thinkpad_acpi
modprobe: ERROR: could not insert 'thinkpad_acpi': No such device

Here is the output from sensors-detect

$ sudo sensors-detect 
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: LENOVO 30X50045XX [ThinkStation P330]
# Board: LENOVO 3138
# Kernel: 4.15.0-101-generic x86_64
# Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (6/158/10)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): Yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Yes
/dev/port: Operation not permitted

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): Yes
/dev/port: Operation not permitted

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Y
/dev/port: Operation not permitted

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Found unknown SMBus adapter 8086:a323 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): yes 
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x58
Probing for `Analog Devices ADT7462'...                     No
Probing for `Andigilog aSC7512'...                          No
Client found at address 0x5c
Probing for `Analog Devices ADT7462'...                     No
Probing for `SMSC EMC1072'...                               No
Probing for `SMSC EMC1073'...                               No
Probing for `SMSC EMC1074'...                               No
Client found at address 0x73
Probing for `FSC Poseidon I'...                             No
Probing for `FSC Poseidon II'...                            No
Probing for `FSC Scylla'...                                 No
Probing for `FSC Hermes'...                                 No
Probing for `FSC Heimdal'...                                No
Probing for `FSC Heracles'...                               No
Probing for `FSC Hades'...                                  No
Probing for `FSC Syleus'...                                 No

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x58
Probing for `Analog Devices ADT7462'...                     No
Probing for `Andigilog aSC7512'...                          No
Client found at address 0x5c
Probing for `Analog Devices ADT7462'...                     No
Probing for `SMSC EMC1072'...                               No
Probing for `SMSC EMC1073'...                               No
Probing for `SMSC EMC1074'...                               No
Client found at address 0x73
Probing for `FSC Poseidon I'...                             No
Probing for `FSC Poseidon II'...                            No
Probing for `FSC Scylla'...                                 No
Probing for `FSC Hermes'...                                 No
Probing for `FSC Heimdal'...                                No
Probing for `FSC Heracles'...                               No
Probing for `FSC Hades'...                                  No
Probing for `FSC Syleus'...                                 No

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus misc (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes


Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: DPDDC-C (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DPDDC-D (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DPDDC-E (i2c-8)
Do you want to scan it? (yes/NO/selectively): y


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)

I am trying to install the wxPython 4 on my Ubuntu 18.04 machine.

sudo pip install wxpython

I get this warning first

    The directory '/home/user/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/user/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

and eventually error

Command "/usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-SyaTU1/wxpython/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-bzIjlK/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-SyaTU1/wxpython/

I had similar problem with wxPython3 and the solution was to install it with get

sudo apt-get install python-wxgtk-3.0

I also was able to install wxPython 4 for Python 3 but not for Python 2.7 (instructions)

Also, I am very confused why it takes so much CPU to install wxpython

sudo pip install wxpython

Why does the newest version of Ubuntu (18.04) have 8 years old x11vnc?

My question is more specific than posted here and I have gotten an answer to it.

Ubuntu version:

user:~/$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04 LTS
Release:    18.04
Codename:   bionic

I have installed the x11vnc:

sudo apt-get install x11vnc -y

Later I discovered the version is 8 years old.

X11vnc version

29/07/2018 17:15:54 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 3283

So, I checked sources for the Ubuntu 18.04 and I see that the newest cersion is not available.

b-ii-6@b-ii-6:~/$ apt-get source x11vncReading package lists... Done
Need to get 2,868 kB of source archives.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe x11vnc 0.9.13-3 (dsc) [2,000 B]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe x11vnc 0.9.13-3 (tar) [2,854 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/universe x11vnc 0.9.13-3 (diff) [12.5 kB]
Fetched 2,868 kB in 0s (6,632 kB/s)
dpkg-source: info: extracting x11vnc in x11vnc-0.9.13
dpkg-source: info: unpacking x11vnc_0.9.13.orig.tar.gz
dpkg-source: info: unpacking x11vnc_0.9.13-3.debian.tar.xz
dpkg-source: info: applying 0001-Fix-openssl-1.1.x-detection.patch
dpkg-source: info: applying 0002-Support-openssl-1.1.0.patch
dpkg-source: info: applying 10_usepkgconfig.diff
dpkg-source: info: applying do-not-run-dbus-launch.patch
dpkg-source: info: applying enforce-bash.patch
dpkg-source: info: applying java_target_source.patch

The current available version on the github is x11vnc 0.9.15 2018-02-04

I have originally set up x11vnc server according to main source or also repeated here.

The server seems to start properly, see below.

    user:~$ sudo systemctl status x11vnc.service
● x11vnc.service - Start x11vnc at startup.
   Loaded: loaded (/lib/systemd/system/x11vnc.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-08-08 13:22:39 EDT; 9min ago
 Main PID: 2312 (x11vnc)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/x11vnc.service
           └─2312 /usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxrecord -noxfixes -noxdamage -shared -norc -aut

However, I get the message "The connection was refused by the computer" if I try to connect to it.

I have found that the port 5900 is not open: the command

sudo lsof -i :5900,3389

results in nothing

Does anyone know what could have happened?

I have 3 Dell Latitude computers on which I have installed Ubuntu. The installation was done from the same source stick, was done several days apart and I have followed home developed protocol ( a list of things to install and commands to run int he terminal).

Even though, I have followed the same protocol I have gotten different behaviour from these machines. One of the problems that bother me the most is that the X11VNC server I have installed following a recipe from main source or also repeated here, fails after ~ 24 hours. When this happens, one of the core is completely consumed by the x11vnc server.

I could access the computer via ssh and here is some information.

I don't know what is the difference between installations and configurations of these computers and why x11vnc server fails after some time. I would appreciate any followup question you might have. I will be updating the question with all new information I will find.

OS:

username:~$  lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04 LTS
Release:    18.04
Codename:   bionic

X11vnc version

29/07/2018 17:15:54 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 3283
29/07/2018 17:15:54 XOpenDisplay("") failed.
29/07/2018 17:15:54 Trying again with XAUTHLOCALHOSTNAME=localhost ...
29/07/2018 17:15:54 
29/07/2018 17:15:54 *** XOpenDisplay failed. No -display or DISPLAY.
29/07/2018 17:15:54 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
29/07/2018 17:15:54 *** 1 2 3 4 
29/07/2018 17:15:58 *** XOpenDisplay of ":0" successful.
29/07/2018 17:15:58 
29/07/2018 17:15:58 Using X display :0
29/07/2018 17:15:58 rootwin: 0x191 reswin: 0x3400001 dpy: 0xc6189f90

before: sudo systemctl restart x11vnc

x11vnc.service - Start x11vnc at startup.
   Loaded: loaded (/lib/systemd/system/x11vnc.service; enabled; vendor preset: e
   Active: active (running) since Fri 2018-07-27 17:52:36 EDT; 1 day 22h ago
 Main PID: 1604 (x11vnc)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/x11vnc.service
           ├─1604 /usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxreco
           └─1606 /usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxreco

Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46 client_count: 1
Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46 Client 137.187.82
Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46 Statistics       
Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46  TOTALS          
Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46 Statistics       
Jul 28 10:10:46 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:10:46  TOTALS          
Jul 28 10:15:47 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:15:47 idle keyboard:   
Jul 28 10:37:22 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:37:22 Got connection fr
Jul 28 10:37:22 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:37:22   other clients:
Jul 28 10:37:22 icarus-ii-50 x11vnc[1604]: 28/07/2018 10:37:22      128.231.4.12
~
~

After: sudo systemctl restart x11vnc

    x11vnc.service - Start x11vnc at startup.
   Loaded: loaded (/lib/systemd/system/x11vnc.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-07-29 16:37:40 EDT; 28min ago
 Main PID: 30404 (x11vnc)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/x11vnc.service
           ├─30404 /usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxrecord -noxfixe
           └─30405 /usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxrecord -noxfixe

Jul 29 17:03:35 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:35 Enabling full-color cursor u
Jul 29 17:03:35 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:35 Enabling NewFBSize protocol 
Jul 29 17:03:35 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:35 Switching from ZRLE to hexti
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 rfbProcessClientNormalMessag
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 rfbProcessClientNormalMessag
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 rfbProcessClientNormalMessag
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 rfbProcessClientNormalMessag
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 Enabling full-color cursor u
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 Enabling NewFBSize protocol 
Jul 29 17:03:36 icarus-ii-50 x11vnc[30404]: 29/07/2018 17:03:36 Switching from hextile to ZR
lines 1-19/19 (END)

here is the record of 100% CPU consumption by VNC server

top - 18:53:15 up 2 days,  1:01,  2 users,  load average: 1.39, 1.45, 1.41
Tasks: 261 total,   2 running, 192 sleeping,   0 stopped,   1 zombie
%Cpu(s):  3.0 us, 10.3 sy,  0.0 ni, 86.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  8031704 total,  2470912 free,  4375192 used,  1185600 buff/cache
KiB Swap:  2097148 total,  2097148 free,        0 used.  3068456 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                 
30405 root      20   0  154924  34324  22212 R 100.0  0.4  48:41.74 x11vnc