Thursday 23 March 2017

DisplayLink - Dell MKS14b dock with Fedora 24

Very pleased to report success on connecting my TP300LA running Fedora 24 to a USB 3.0 DisplayLink dock. This would be a very handy way of connecting monitors. At present I can only use the laptop with a monitor connected to its HDMI port.

Fedora 4.9.13-101.fc24.x86_64

Dock: Dell MKS14b

Installed the displaylink-rpm driver following the instructions posted for Fedora 25 by reypm at this post. He experienced some issues while attempting to install the DisplayLink driver on Fedora 25. I faced not issues on Fedora 24.

Driver rpm link: displaylink-rpm - 1.3.43-2.x86_64.rpm

# Checking the status of displaylink.service after installing the driver [root@tp300la displaylink-driver-1.2.65]# systemctl status displaylink.service ● displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled) Active: inactive (dead)

Connected the USB 3.0 cable from the dock after installing the DisplayLink driver and checking the displaylink.service was active

Plugging in the USB cable from the dock

[root@tp300la displaylink-driver-1.2.65]# systemctl status displaylink.service ● displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled) Active: active (running) since Thu 2017-03-23 13:41:57 GMT; 5min ago Process: 24805 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS) Main PID: 24822 (DisplayLinkMana) Tasks: 26 (limit: 512) CGroup: /system.slice/displaylink.service └─24822 /usr/libexec/displaylink/DisplayLinkManager
[ 5043.605949] usb 1-1.3: New USB device found, idVendor=0451, idProduct=8044 [ 5043.605951] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=1 [ 5043.605952] usb 1-1.3: SerialNumber: NNNNNNNNNNNN [ 5043.606309] usb 1-1.3: Not enough bandwidth for new device state. [ 5043.606315] usb 1-1.3: can't set config #1, error -28 [ 5043.669754] usb 2-1.3: new SuperSpeed USB device number 19 using xhci_hcd [ 5043.681922] usb 2-1.3: New USB device found, idVendor=0451, idProduct=8046 [ 5043.681924] usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5043.682440] usb 2-1.3: Not enough bandwidth for new device state. [ 5043.682447] usb 2-1.3: can't set config #1, error -28 [ 5043.745725] usb 1-1.4: new low-speed USB device number 32 using xhci_hcd [ 5043.826237] usb 1-1.4: New USB device found, idVendor=046d, idProduct=c016 [ 5043.826242] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 5043.826245] usb 1-1.4: Product: Optical USB Mouse [ 5043.826247] usb 1-1.4: Manufacturer: Logitech [ 5043.826793] usb 1-1.4: Not enough bandwidth for new device state. [ 5043.826806] usb 1-1.4: can't set config #1, error -28 [ 5044.050445] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff96485851e000 tries to close us [ 5044.050447] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 5044.063811] evdi: [D] evdi_painter_connect:443 (dev=1) Connected with ffff96485851e000 [ 5044.063813] evdi: [D] evdi_detect:75 (dev=1) Painter is connected [ 5044.063852] evdi: [D] evdi_painter_crtc_state_notify:360 (dev=1) Notifying crtc state: 3 [ 5044.064608] evdi: [D] evdi_detect:75 (dev=1) Painter is connected [ 5044.064612] evdi: [D] evdi_painter_get_edid_copy:192 (dev=1) 00 ff ff [ 5044.099866] evdi: [D] evdi_painter_mode_changed_notify:376 (dev=1) Notifying mode changed: 1920x1200@60; bpp 32; [ 5044.099868] evdi: [D] evdi_painter_mode_changed_notify:377 pixel format 875713112 [ 5044.099873] evdi: [D] evdi_painter_crtc_state_notify:360 (dev=1) Notifying crtc state: 0 [ 5044.099876] evdi: [D] evdi_painter_dpms_notify:347 (dev=1) Notifying dpms mode: 0 [ 5044.280517] evdi: [D] evdi_detect:75 (dev=1) Painter is connected [ 5044.280520] evdi: [D] evdi_painter_get_edid_copy:192 (dev=1) 00 ff ff

disconnecting the USB cable from the dock

[ 5102.015916] usb 1-1: USB disconnect, device number 29 [ 5102.015920] usb 1-1.2: USB disconnect, device number 30 [ 5102.063364] usb 1-1.3: USB disconnect, device number 31 [ 5102.063491] usb 1-1.4: USB disconnect, device number 32 [ 5102.122400] xhci_hcd 0000:00:14.0: Cannot set link state. [ 5102.122405] usb usb2-port1: cannot disable (err = -32) [ 5102.122410] usb 2-1: USB disconnect, device number 17 [ 5102.122411] usb 2-1.1: USB disconnect, device number 18 [ 5102.123103] cdc_ncm 2-1.1:1.5 enp0s20u1u1i5: unregister 'cdc_ncm' usb-0000:00:14.0-1.1, CDC NCM [ 5102.143956] usb 2-1.3: USB disconnect, device number 19 [ 5102.145449] evdi: [D] evdi_painter_disconnect:483 (dev=1) Disconnected from ffff96485851e000 [ 5102.145452] evdi: [D] evdi_detect:78 Painter is disconnected [ 5102.145488] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff96485851e000 tries to close us [ 5102.145490] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 5102.147704] evdi: [D] evdi_detect:78 Painter is disconnected [ 5102.177013] evdi: [D] evdi_painter_crtc_state_notify:360 (dev=-1) Notifying crtc state: 3 [ 5102.177019] evdi: [W] evdi_painter_send_crtc_state:266 Painter is not connected! [ 5102.194840] audit: type=1130 audit(1490277065.997:5177): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5102.348666] evdi: [D] evdi_detect:78 Painter is disconnected
[root@tp300la displaylink-driver-1.2.65]# systemctl status displaylink.service ● displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor p Active: inactive (dead)

Screenshots coming soon

ASUS TP300LA specs

I should really have posted this information a while back since I am referring to this laptop in my blog posts. That would help readers understand better my Fedora experience on this laptop

Here are the details of my ASUS TP300LA laptop.

Asus TP300LA Touch Convertible Laptop
  • Intel Core i5-5200U 2.2GHz,
  • 6GB RAM,
  • 500GB HDD -> replaced with a Sandisk 960GB SATA III SSD
  • 13.3" HD Touch,
  • Webcam,
  • Bluetooth
  • Operating System - original - Windows 8.1 Home

Operating System

Fedora 24 x64 dual booting with Windows 10 (upgraded from Windows 8.1). Windows 10 is rarely used.

Wednesday 12 October 2016

profile-sync-daemon on Fedora 24

Background

PSD is designed to manage browser profile(s) in tmpfs and to periodically sync back to the physical disc, thereby reducing writes to SSDs. This is useful where there is ample spare RAM on the system.

Installing profile-sync-daemon

profile-sync-daemon was not available in Fedora repositories at the time. To build and install it

Download the source from https://github.com/graysky2/profile-sync-daemon

[mochapenguin@dv6tqe psd]su -
[root@dv6tqe psd]# git clone https://github.com/graysky2/profile-sync-daemon.git
[root@dv6tqe psd]# cd profile-sync-daemon/
[root@dv6tqe profile-sync-daemon]# make
Setting version
[root@dv6tqe profile-sync-daemon]# make install
Installing main script...
install -p -d "/usr/bin"
install -p -m755 common/profile-sync-daemon "/usr/bin/profile-sync-daemon"
install -p -m755 common/psd-overlay-helper "/usr/bin/psd-overlay-helper"
ln -s profile-sync-daemon "/usr/bin/psd"
install -p -d "/usr/share/zsh/site-functions"
install -p -m644 common/zsh-completion "//usr/share/zsh/site-functions/_psd"
install -p -d "/usr/share/psd/browsers"
install -p -m644 common/psd.conf "/usr/share/psd/psd.conf"
cp common/browsers/* "/usr/share/psd/browsers"
Installing manpage...
install -p -d "/usr/share/man/man1"
install -p -m644 doc/psd.1 "/usr/share/man/man1/psd.1"
install -p -m644 doc/psd-overlay-helper.1 "/usr/share/man/man1/psd-overlay-helper.1"
gzip -9 "/usr/share/man/man1/psd.1"
gzip -9 "/usr/share/man/man1/psd-overlay-helper.1"
ln -s psd.1.gz "/usr/share/man/man1/profile-sync-daemon.1.gz"
Installing systemd files...
install -p -d "/usr/lib/systemd/user"
install -p -m644 init/psd.service "/usr/lib/systemd/user/psd.service"
install -p -m644 init/psd-resync.service "/usr/lib/systemd/user/psd-resync.service"
install -p -m644 init/psd-resync.timer "/usr/lib/systemd/user/psd-resync.timer"    
    

First run

When profile-sync-daemon is run for the first time, it outputs the following:

[mochapenguin@dv6tqe ~]$ psd p
First time running psd so please edit /home/mochapenguin/.config/psd/psd.conf to your liking and run again.

[mochapenguin@dv6tqe ~]$ psd p
Profile-sync-daemon v6.25 on Fedora 24 (Workstation Edition)

 Systemd service is currently active.
 Systemd resync-timer is currently active.
 Overlayfs v23 is currently active.

Psd will manage the following per /home/mochapenguin/.config/psd/psd.conf:

 browser/psname:  firefox/firefox
 owner/group id:  mochapenguin/1000
 sync target:     /home/mochapenguin/.mozilla/firefox/fu8u7xk0.default
 tmpfs dir:       /run/user/1000/mochapenguin-firefox-fu8u7xk0.default
 profile size:    14M
 overlayfs size:  
 recovery dirs:   none

 browser/psname:  google-chrome/chrome
 owner/group id:  mochapenguin/1000
 sync target:     /home/mochapenguin/.config/google-chrome
 tmpfs dir:       /run/user/1000/mochapenguin-google-chrome
 profile size:    5.8M
 overlayfs size:  
 recovery dirs:   none

Usage

More information on profile-sync-daemon usage can be found on Arch Linux Profile Sync Daemon page

Sunday 11 September 2016

Fedora 24 on HP dv6tqe

Power saving

See my posts on power management:



Power Management with Fedora 24 - Preparation

I dabbled with Power Management on my HP dv6tqe laptop. Here's what I have been learning.

Preparing to monitor. Install the required monitors/sensors.

Install lm_sensors

lm_sensors installation

[mochapenguin@dv6tqe ~]$ sudo dnf install lm_sensors
Last metadata expiration check: 2:27:57 ago on Sun Sep 11 01:35:12 2016.
Dependencies resolved.
================================================================================
 Package                Arch          Version               Repository     Size
================================================================================
Installing:
 lm_sensors             x86_64        3.4.0-4.fc24          fedora        145 k
 lm_sensors-libs        x86_64        3.4.0-4.fc24          fedora         46 k

Transaction Summary
================================================================================
Install  2 Packages

Total download size: 191 k
Installed size: 483 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): lm_sensors-libs-3.4.0-4.fc24.x86_64.rpm  407 kB/s |  46 kB     00:00    
(2/2): lm_sensors-3.4.0-4.fc24.x86_64.rpm       988 kB/s | 145 kB     00:00    
--------------------------------------------------------------------------------
Total                                           122 kB/s | 191 kB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Installing  : lm_sensors-libs-3.4.0-4.fc24.x86_64                         1/2 
  Installing  : lm_sensors-3.4.0-4.fc24.x86_64                              2/2 
  Verifying   : lm_sensors-3.4.0-4.fc24.x86_64                              1/2 
  Verifying   : lm_sensors-libs-3.4.0-4.fc24.x86_64                         2/2 

Installed:
  lm_sensors.x86_64 3.4.0-4.fc24       lm_sensors-libs.x86_64 3.4.0-4.fc24      

Complete!
---

Run sensors-detect to prepare a configuration for your system.

[mochapenguin@dv6tqe ~]$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Hewlett-Packard HP Pavilion dv6 Notebook PC [058D100000244720001620100] (laptop)
# Board: Hewlett-Packard 1657
# Kernel: 4.7.2-201.fc24.x86_64 x86_64
# Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (6/42/7)

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): 
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): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found `ITE IT8518E Super IO'                                
    (no support yet)

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): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

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): 
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus panel (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 dpb (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): yes

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

Next adapter: Radeon i2c bit bus 0x90 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x91 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x92 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x93 (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x94 (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x95 (i2c-12)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x96 (i2c-13)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: Radeon i2c bit bus 0x97 (i2c-14)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: SMBus I801 adapter at 6040 (i2c-15)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)


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)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
Unloading i2c-dev... OK
---

Install hddtemp

[mochapenguin@dv6tqe ~]$ sudo dnf install hddtemp
[sudo] password for mochapenguin: 
Last metadata expiration check: 2:52:34 ago on Sun Sep 11 01:35:12 2016.
Dependencies resolved.
================================================================================
 Package        Arch          Version                       Repository     Size
================================================================================
Installing:
 hddtemp        x86_64        0.3-0.35.beta15.fc24          fedora         60 k

Transaction Summary
================================================================================
Install  1 Package

Total download size: 60 k
Installed size: 134 k
Is this ok [y/N]: y
Downloading Packages:
hddtemp-0.3-0.35.beta15.fc24.x86_64.rpm         355 kB/s |  60 kB     00:00    
--------------------------------------------------------------------------------
Total                                            43 kB/s |  60 kB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Installing  : hddtemp-0.3-0.35.beta15.fc24.x86_64                         1/1 
  Verifying   : hddtemp-0.3-0.35.beta15.fc24.x86_64                         1/1 

Installed:
  hddtemp.x86_64 0.3-0.35.beta15.fc24                                           

Complete!

Check out the sensors

[mochapenguin@dv6tqe ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +47.0°C  (crit = +99.0°C)

radeon-pci-0100
Adapter: PCI adapter
temp1:            N/A  (crit = +120.0°C, hyst = +90.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +47.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:         +47.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:         +47.0°C  (high = +86.0°C, crit = +100.0°C)
Core 2:         +46.0°C  (high = +86.0°C, crit = +100.0°C)
Core 3:         +44.0°C  (high = +86.0°C, crit = +100.0°C)

Tuesday 26 July 2016

Installing apps on Fedora 24

Telegram

Download Telegram for Linux. The downloaded file was tsetup.version.number.tar.xz

I am following the approach of installing additional software in the /opt folder. Untar it to /opt.

tar zxf tsetup.version.tar.xz -C /opt

The files are unzipped to /opt/Telegram and the file to execute is /opt/Telegram/Telegram

Typically, the permissions would be as below:

[mochapenguin@dv6tqe ~]$ ls -las /opt total 20 4 drwxr-xr-x. 5 root root 4096 Jul 26 15:16 . 4 dr-xr-xr-x. 18 root root 4096 Jul 25 11:12 .. 4 drwxr-xr-x. 3 root root 4096 Jul 24 21:04 google 4 drwxr-xr-x. 4 root root 4096 Jul 25 20:18 Simplenote-linux-x64-102 4 drwxrwxr-x. 2 root root 4096 Jul 25 20:14 Telegram

Create a desktop launcher file as specified below:

~/Desktop/Telegram.desktop
#!/usr/bin/env xdg-open [Desktop Entry] Type=Application Encoding=UTF-8 Name=Telegram Comment=Telegram Messenger Exec=/opt/Telegram/Telegram Icon=/home/mochapenguin/.TelegramDesktop/tdata/ticons/icomute_22_0.png Terminal=false

Saturday 18 June 2016

Inateck 2.5 Inch USB 3.0 Hard Drive Enclosure External SATA HDD and SSD Case - Optimized for 9.5mm 7mm 2.5" SSD, Tool Free (FE2002)

Purchased another USB 3.0 hard disk enclosure [Inateck 2.5 Inch USB 3.0 Hard Drive Enclosure External SATA HDD and SSD Case - Optimized for 9.5mm 7mm 2.5" SSD, Tool Free (FE2002)]

dmesg
[18230.601026] usb 1-7: new high-speed USB device number 2 using ehci-pci [18230.718914] usb 1-7: New USB device found, idVendor=174c, idProduct=55aa [18230.718921] usb 1-7: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [18230.718926] usb 1-7: Product: ASM1153E [18230.718930] usb 1-7: Manufacturer: Inateck [18230.718934] usb 1-7: SerialNumber: 123456789111 [18230.830322] usbcore: registered new interface driver usb-storage [18230.838751] scsi host4: uas [18230.839585] usbcore: registered new interface driver uas [18230.840569] scsi 4:0:0:0: Direct-Access Inateck ASM1153E 0 PQ: 0 ANSI: 6 [18230.842579] sd 4:0:0:0: Attached scsi generic sg2 type 0 [18230.843552] sd 4:0:0:0: [sdb] Spinning up disk... [18231.844019] ..ready [18232.848344] sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB) [18232.848351] sd 4:0:0:0: [sdb] 4096-byte physical blocks [18232.850332] sd 4:0:0:0: [sdb] Write Protect is off [18232.850340] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00 [18232.851660] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [18232.921374] sdb: sdb1 [18232.924707] sd 4:0:0:0: [sdb] Attached SCSI disk

Shall be updating more details about the product as I get used to it. Watch this space!