Ubuntu HowTo: Thinkpad USB 3.0 docking station disconnects and reconnects

Original Source Link

I have a Thinkpad T450s with a USB 3.0 docking station (also Lenovo), running 16.04 LTS. The docking station is connected to a few USB peripherals, ethernet, and a DisplayLink monitor. The station periodically disconnects and then (very quickly, ~1 second) reconnects again. These events typically happen multiple times per day, but I have gone a few days without incident before. As far as I know, all of my relevant drivers (including DisplayLink) are up to date.

My dmesg is also flooded with (I believe unrelated) spam, that comes in constantly whether or not the dock is disconnecting:

[373168.536341] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x4000041, supported mask 0x7400003f
[373168.553436] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x41, supported mask 0x7400003f

Because of the dmesg spam, I don’t currently have a log of the disconnect-reconnect. I will include one when I am able to capture it, but I do not believe it shows anything unusual beyond the list of devices connected to the docking station disconnecting and then reconnecting again.


Edit: The results from dmesg immediately after a disconnect are below:

[499047.292100] usb 3-3: USB disconnect, device number 53
[499047.292104] usb 3-3.1: USB disconnect, device number 55
[499047.294353] cdc_ncm 3-3.1:1.5 enxe04f4359a6b1: unregister 'cdc_ncm' usb-0000:00:14.0-3.1, CDC NCM
[499047.321377] usb 3-3.4: USB disconnect, device number 54
[499047.333135] evdi: [D] evdi_painter_disconnect:611 (dev=1) Disconnected from ffff8801c08dd400
[499047.333139] evdi: [D] evdi_detect:78 Painter is disconnected
[499047.333178] evdi: [W] evdi_painter_disconnect:593 (dev=-1) An unknown connection to ffff8801c08dd400 tries to close us
[499047.333180] evdi: [W] evdi_painter_disconnect:594  - ignoring
[499047.341965] evdi: [D] evdi_detect:78 Painter is disconnected
[499047.379218] evdi: [D] evdi_painter_crtc_state_notify:481 (dev=-1) Notifying crtc state: 3
[499047.379221] evdi: [W] evdi_painter_send_crtc_state:387 Painter is not connected!
[499047.602454] usb 3-3: new SuperSpeed USB device number 56 using xhci_hcd
[499047.717203] usb 3-3: New USB device found, idVendor=17ef, idProduct=1014
[499047.717209] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[499047.717212] usb 3-3: Product: TP USB 3.0 Ultra Dock  
[499047.717214] usb 3-3: Manufacturer: LENOVO                 
[499047.733011] hub 3-3:1.0: USB hub found
[499047.735168] hub 3-3:1.0: 4 ports detected
[499048.148156] usb 3-3.1: new SuperSpeed USB device number 57 using xhci_hcd
[499048.165704] usb 3-3.1: New USB device found, idVendor=17e9, idProduct=4340
[499048.165712] usb 3-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[499048.165716] usb 3-3.1: Product: ThinkPad USB 3.0 Ultra Dock
[499048.165718] usb 3-3.1: Manufacturer: DisplayLink
[499048.165720] usb 3-3.1: SerialNumber: 4551152301011274J1YY
[499048.221380] usb 3-3.1: Warning! Unlikely big volume range (=511), cval->res is probably wrong.
[499048.221383] usb 3-3.1: [15] FU [Lenovo Audio Playback Volume] ch = 6, val = -8176/0/16
[499048.222201] usb 3-3.1: Warning! Unlikely big volume range (=767), cval->res is probably wrong.
[499048.222206] usb 3-3.1: [12] FU [Mic Capture Volume] ch = 2, val = -4592/7680/16
[499048.252543] cdc_ncm 3-3.1:1.5: MAC-Address: e0:4f:43:59:a6:b1
[499048.252548] cdc_ncm 3-3.1:1.5: setting rx_max = 16384
[499048.252663] cdc_ncm 3-3.1:1.5: setting tx_max = 16384
[499048.252913] cdc_ncm 3-3.1:1.5 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3.1, CDC NCM, e0:4f:43:59:a6:b1
[499048.385196] usb 3-3.4: new SuperSpeed USB device number 58 using xhci_hcd
[499048.487299] usb 3-3.4: New USB device found, idVendor=17ef, idProduct=1015
[499048.487303] usb 3-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[499048.487305] usb 3-3.4: Product: TP USB 3.0 Ultra Dock  
[499048.487306] usb 3-3.4: Manufacturer: LENOVO                 
[499048.492208] hub 3-3.4:1.0: USB hub found
[499048.492376] hub 3-3.4:1.0: 4 ports detected
[499049.272800] cdc_ncm 3-3.1:1.5 enxe04f4359a6b1: renamed from usb0
[499049.310745] IPv6: ADDRCONF(NETDEV_UP): enxe04f4359a6b1: link is not ready
[499049.310819] IPv6: ADDRCONF(NETDEV_UP): enxe04f4359a6b1: link is not ready
[499050.607303] cdc_ncm 3-3.1:1.5 enxe04f4359a6b1: 1000 mbit/s downlink 1000 mbit/s uplink
[499050.623303] cdc_ncm 3-3.1:1.5 enxe04f4359a6b1: network connection: connected
[499050.623335] IPv6: ADDRCONF(NETDEV_CHANGE): enxe04f4359a6b1: link becomes ready
[499050.751126] evdi: [W] evdi_painter_disconnect:593 (dev=-1) An unknown connection to ffff8801efe9fe00 tries to close us
[499050.751128] evdi: [W] evdi_painter_disconnect:594  - ignoring
[499050.756546] evdi: [D] evdi_painter_connect:572 (dev=1) Connected with ffff8801efe9fe00
[499050.756549] evdi: [D] evdi_detect:75 (dev=1) Painter is connected
[499050.756608] evdi: [D] evdi_painter_crtc_state_notify:481 (dev=1) Notifying crtc state: 3
[499050.759243] evdi: [D] evdi_detect:75 (dev=1) Painter is connected
[499050.759248] evdi: [D] evdi_painter_get_edid_copy:215 (dev=1) 00 ff ff
[499050.793728] evdi: [D] evdi_painter_mode_changed_notify:505 (dev=1) Notifying mode changed: [email protected]; bpp 32; 
[499050.793730] evdi: [D] evdi_painter_mode_changed_notify:506 pixel format 875713112
[499050.793735] evdi: [D] evdi_painter_crtc_state_notify:481 (dev=1) Notifying crtc state: 0
[499050.793737] evdi: [D] evdi_painter_dpms_notify:468 (dev=1) Notifying dpms mode: 0

Tagged : / / /

Ubuntu HowTo: Ubuntu 16.04 Bluetooth not working and finding devices

Original Source Link

My Ubuntu 16.04 WiFi is not getting connected to my Bluetooth speaker. Even when I try searching for the new device it is not showing anything though the speaker gets connected to my smartphone. My smartphone also doesn’t show my laptop’s Bluetooth though the visibility is on.

enter image description here

I have checked blockage, it says no.

There is a similar problem for Ubuntu 14.04 but the solution doesn’t work for me 16.04.
Bluetooth not detecting any devices

This is the error I get: E: Unable to locate package rtl8723au-bt-dkms

I tested for this:

lsusb; dmesg | egrep -i 'blue|firm'

The output was:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

With lspci -knn | grep Net -A3; lsusb, the output was

03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 

PCIe Wireless Network Adapter [10ec:b723]
DeviceName: Realtek RTL8723BE 802.11b/g/n 1x1Wi-Fi + BT4.0 Combo Adapter
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c]
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 0a)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Also on restarting the bluetooth, it shuts off but does not start.

It’s Ubuntu 16.04 LTS.

Output of cat /etc/apt/sources.list

is deb http://archive.ubuntu.com/ubuntu xenial main universe restricted multiverse

This bluetooth device is not supported by the 4.4 kernel.

Upgrade it to 4.10 by running

sudo apt update
sudo apt install linux-generic-hwe-16.04

Reboot with the new kernel. The BT adapter should work unless there is no firmware.

Update: Your /etc/apt/sources.list doesn’t have xenial-updates for some reason.

You can create a default sources.list. Delete /etc/apt/sources.list by running

sudo rm /etc/apt/sources.list

then go to System Settings -> Software & Updates and enable all repos.

Then you’ll be able to install linux-generic-hwe-16.04.

Tagged : / / /

Ubuntu HowTo: How to turn off the filesystem check message which occures while booting

Original Source Link

What I want to achieve:

I want to customize my complete boot of my Ubuntu 16.04 LTS installation to show the same wallpaper which is actually on my desktop.

What I achieved till now:

  • added the wallpaper to the grub menu by adding the following lines to /etc/deault/grub and doing an update-grub afterwards.

    export GRUB_MENU_PICTURE="/boot/grub/wallpaper.png"
    export GRUB_COLOR_NORMAL="white/black"
    export GRUB_COLOR_HIGHLIGHT="black/white"
  • added the wallpaper to the splash-screen and login screen


When I boot up the picture is showing while in grub, but then I rarely see the splash screen, instead I get an almost blank screen showing the file-system check like following:

/dev/sda1: clean, 201776/60878736 files, 4991277/243040256 blocks

This prevents me from having the boot experience I want to achieve since after that the splash-screen just shortly popping up after that message.


How can I remove this message from showing up so I get a seamless booting with my beloved wallpaper, without switching the file-system check completely off (if possible)?

Silencing boot messages

You should be able to achieve this with the kernel parameter loglevel= or quiet

loglevel=       All Kernel Messages with a loglevel smaller than the
                console loglevel will be printed to the console. It can
                also be changed with klogd or other programs. The
                loglevels are defined as follows:

                0 (KERN_EMERG)          system is unusable
                1 (KERN_ALERT)          action must be taken immediately
                2 (KERN_CRIT)           critical conditions
                3 (KERN_ERR)            error conditions
                4 (KERN_WARNING)        warning conditions
                5 (KERN_NOTICE)         normal but significant condition
                6 (KERN_INFO)           informational
                7 (KERN_DEBUG)          debug-level messages

quiet       [KNL] Disable most log messages

I am not sure at exactly what level this would be hidden (or how quiet you would like your boot to be).


reboot your computer, and at the grub menu hit e to edit the boot parameters.

scroll down to the end of the linux... line using the arrow keys

add desired loglevel parameter or quiet to the end of that line. example:

linux      /vmlinuz-4.4.0-21.generic.efi.signed root=/dev/mapper/encrypted ro loglevel=4


linux      /vmlinuz-4.4.0-21.generic.efi.signed root=/dev/mapper/encrypted ro quiet

when done editing, proceed to boot by pressing F10


To do this, edit /etc/default/grub

edit the line:

uncomment it if needed, and add the desired log level or quiet — for example GRUB_CMDLINE_LINUX_DEFAULT="loglevel=4" or GRUB_CMDLINE_LINUX_DEFAULT="quiet"

and run sudo update-grub

fsck messages

remove fsck from initramfs

fsck is run by default by the initramfs. by removing it and having systemd run fsck we will be able to redirect the output.

see man initramfs and wiki.ubuntu.com/Initramfs for more info on removing fsck from the ramfs.

systemd fsck

From the arch wiki:

Now copy the files systemd-fsck-root.service and [email protected] located at /usr/lib/systemd/system/ to /etc/systemd/system/ and edit them, configuring StandardOutput and StandardError like this:



In Ubuntu, these files are both located in /lib/systemd/system

If the file system is not checked by the initramfs during boot, systemd-fsck-root.service will automatically be run.

see http://manpages.ubuntu.com/manpages/wily/man8/[email protected]

Removing Checking Disks From 20.04 Boot

Installed system

The command line option fsck.mode=skip can be used to skip the disk check when booting Ubuntu 20.04.

The line Checking disks: 0% complete may still come up but fsck will not be run, nor will boot time be increased.

Add fsck.mode=skip to the linux line in grub.cfg just before quiet splash

It is recommended to add the command to grub.cfg by editing /etc/default/grub thus: GRUB_CMDLINE_LINUX_DEFAULT="fsck.mode=skip quiet splash" and then run sudo update-grub.

I have had this problem with a Live USB but not with an installed system.

Persistent USB’s

The command line option fsck.mode=skip can also be used to skip the disk check on persistent USB drives.

The line Checking disks: 0% complete will still come up but fsck will not be run, nor will boot time be increased.

mkusb After the Persistent USB drive is created, open /boot/grub/grub.cfg as root.

  • Add fsck.mode=skip to the Persistent menuentry thus:

linux ($root)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity fsck.mode=skip quiet splash persistent ---

  • Newer versions of mkusb already include this fix

UNetbootin After creating the boot drive, open /boot/grub/grub.cfg as root.

  • Add fsck.mode=skip to the first menuentry for (UEFI boot mode).

  • Open syslinux.cfg as root and add fsck.mode=skip to the default menuentry for (BIOS boot mode).

Rufus After creating the boot drive, open /boot/grub/grub.cfg as root.

  • Add fsck.mode=skip to the Default menuentry for (UEFI boot mode).

  • Open /isolinux/txt.cfg as root and add fsck.mode=skip to the “Try Ubuntu without installing” menuentry, (for BIOS boot mode).

The Try Ubuntu / Install Ubuntu screen can be removed from BIOS boot by overwriting syslinux.cfg with:

default persistent
label persistent
  say Booting an Ubuntu Persistent session...
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper persistent initrd=/casper/initrd quiet splash noprompt --

I too have been experiencing black screen after grub with console logging and a flash of Plymouth splash screen even on a fresh install of 16.04 LTS. Disabling messages is probably not the best thing to do. I Google searched outside of ask Ubuntu and discovered this thread. In comment #18 you’ll find the commands that fixed my issue with out disabling messages.

My procedure for implementing the fix went as follows:

  1. Open Terminal (You will have to be logged in as root)
  2. Type: sudo -i (type your administrator password)
  3. Type: echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
  4. Type: update-initramfs -u
  5. Type: exit (to log out as root).
  6. Close your terminal and reboot your computer.

Now if Plymouth is working properly, proceed with customizing your boot process. If you have tried many attempts to fix the Plymouth splash screen with terminal commands I suggest a fresh install and start over, you may have caused damage to your file system and not be aware of it.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash loglevel=3 console=tty3"

console=tty3 moves fsck output to not default console and keep tty1 clean.

Tagged : / / / /

Ubuntu HowTo: Shutdown hangs on “A stop job is running to for Mysql Community Server”

Original Source Link

I’m using MySQL ver 14.14 Distrib 5.7.17 for Linux (x86_64) on Ubuntu 16.04. Whenever I shutdown Ubuntu, it hangs here.

enter image description here

After 10 minutes, it automatically kills the process (my guess). I ran into this problem many times. I did a clean install a few times, it works for a while, but then starts doing the same thing after a few proper shutdowns.

Pressing Ctrl+Alt+Del 7 times consecutively forces a shutdown. Forcing a shutdown like this corrupted my MySQL data. Has anyone else ran into this problem?

Thats because you got problems with timezone settings:

Got the same issue, found a possible explanation: my cloud provider store time in local timezone (earlier than UTC); at startup MySQL boot first, then NTP, which updates the time to UTC; therefore, MySQL literally “started in the future” (sounds interesting).

Running sudo dpkg-reconfigure tzdata should do the trick

Source: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164/comments/11

Before shutting down your system, try running this to manually shut down the mysql service.

sudo service mysql stop

Alternatively, write a script to automate the process:

sudo service mysql stop
sudo shutdown -h now

Make sure to mark it as executable. Presuming you saved it as a file named shutdown, run this command:

chmod u+x shutdown

Now you can execute your script.


Strangely enough, this worked for me:

sudo dpkg-reconfigure tzdata

possible explanation: my cloud provider store time in local timezone (earlier than UTC); at startup MySQL boot first, then NTP, which updates the time to UTC; therefore, MySQL literally ‘started in the future’

Install mysql-client with

apt-get install mysql-client

That should be sufficient.

This happens to me to when I changed the hostname with :

$ sudo hostnamectl set-hostname my-new-hostname

without stopping the mysql server.

Shut down the pc using command- sudo init 0
Though this sounds stupid but yes, it works. It worked for me and even for you too. Actually the server does not stopped because of not being getting the super administrative privileges. So next time shut down using this command.

If it helps anyone else, this is what has resolved the issue for me on Ubuntu 16.04 LTS. Basically delayed the service startup in the mysql.service file under /lib/systemd/system/
I added
After=lightdm.service and wants=lightdm.service.
(My lightdm.service is itself delayed until domain authentication has taken place)
I guess you could use any other service that you know will start later on in the boot. These service files will also shutdown the services when Ubuntu is shutdown in the reverse order.

I tried running sudo apt-get install mysql*, and after the installation finished everything seems to be working nice and easy now… Both following the user680697’s nice idea and also shutting down or restarting using GUI capabilities(I’m on Ubuntu Mate 16.04).

This is actually a bug in MySQL.

Please see Bug Report: https://bugs.mysql.com/bug.php?id=93708

To solve this issue, just update your MySQL since the fix is in this update ->

[27 May 2019 13:25] Daniel Price
Fixed as of the upcoming 5.7.27, 8.0.17 release, and here’s the changelog entry:

Manually changing the system time while the MySQL server was running
caused page cleaner thread delays.

credits to Daniel Price.

Tagged : / /

Ubuntu HowTo: K20Xm TESLA CUDA drivers (nvidia-430, 440 etc.) failing to install on Dell T7400 and Dell T7500 running Ubuntu 16.04 LTS

Original Source Link

I have two Dell workstations (a Dell T7400 and a Dell T7500), each with 32GB RAM and two nVidia TESLA K20Xm GPUs (one for each machine). The workstations are running Ubuntu 16.04 LTS.

I want to work with Tensorflow and CUDA 10.1 or 10.2 (preferred). However, despite trying multiple times in different ways, I’m unable to get the nVdia GPU and CUDA drivers working.

CUDA drivers for Dell T7500 with nVidia TESLA K20Xm GPU
The first machine, a T7500, had the K20Xm GPU card as well as an old Quadro FX1800 graphics card (working well at high res). I first checked the pre-installation checklist for the -440 release drivers to ensure I have the correct starting point. I downloaded the run file (by selecting the options for OS etc. from the nVidia website), and tried running it from a terminal session with the lightdm service stopped. It initially warned that the “pre-installation script failed”, but reading other forums I continued through this. It then said it detected the old Quadro FX1800 GPU but would ignore it (I felt this promising as I need to use the TESLA K20Xm). I chose yes to DKMS module installation, and then after restart I was unable to log-in (login loop logging me back out immediately). Most forums report the login loop is to be corrected by either removing nVidia drivers or checking permissions on .Xautority and .XICEauthority (both had correct permissions). Removal of the drivers didn’t fix the problem, I had to remove all of the display manager and lightdm packages and re-install, but then I was left without the GPU drivers. I tried the run file installation again, but after having blacklisted Nouveau. The GPU didn’t work (nvidia-smi didn’t run correctly, despite path set) and my display settings were very poor.

Thinking that perhaps the nVidia Quadro FX graphics card was compounding the problem, I replaced this with an ATI Radeon graphics card (“[AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]”). I installed the Radeon drivers and had it running nicely (with high res), and then re-attempted the -440 drivers installation again via run file. When this failed, I then removed everything and tried by adding a PPA and installing using apt-get install nvidia-440 and the CUDA packages, again this did not work. I also tried “ubuntu-drivers autoinstall”, and this didn’t work. This T7500 workstation is now left with broken packages, non-installed GPU and low-res graphics. It appears that the menu bars and icons are now missing from LightDM.

CUDA drivers for Dell T7400 with nVidia TESLA K20Xm GPU
The next machine (which also has a TESLA K20Xm GPU), is a Dell T7400 with an old (but working fine) nVidia Quadro NVS300 (“NVIDIA Corporation GT218 [NVS 300] (rev a2)”). I tried the the CUDA-drivers installation run file, which I understand has options to install drivers, cuda drivers, cuda samples, etc. Again, I first shutdown the lightdm service and blacklisted nouveau. After installation, I experienced similar problems. The graphics drivers were disrupted. I then tried removing the K20 GPU drivers “nvidia-uninstall”, and trying again but using PPA and first 418 and then 430 drivers, again no luck. This workstation also now has the same issue with the login loop.

So my question: i) How does one correctly install the nVidia GPU drivers alongside a graphics card (without disrupting the graphics card drivers as, understandably, the GPU has no graphics port). Also, how does the DKMS work with nVidia drivers, and should I be using that? (All I understand is that it maintains kernal builds which is useful for future updates, re-builds of the kernel).

These two machines are part of a cluster which is running Infiniband without a switch, it was tricky to get this fabric up and running with the Mellanox drivers so I don’t wish to go-about re-installing Ubuntu 16.04 (also a lot of work/configuration has been done since which I don’t want to have to re-do).

Any suggestions would be greatly appreciated, I feel it shouldn’t be so hard!


There are many CUDA installation answers here, but basically, you get your Nvidia drivers from the standard repositories, and avoid all the CUDA dependency nonsense on these obsolete drivers offered by the Nvidia run/deb packages by just taking the deb file and unpacking it (not installing). The 10.x debs just contain other deb files, delete the unwanted Nvidia ones. Then again just unpack them all.

You should wind up with a complete set of the CUDA files (bin and lib) in your local directory, with no package manager tie-in. Change your PATH and LD_LIBRARY_PATH to include them. The one thing you still might need would be the old gcc/g++ version required by CUDA — install them, and simply add links to the old versions in your cuda/bin directory. DO NOT change the system-wide compiler default with the update-alternatives. Your system will update and maintain kernels and Nvidia drivers without issue. You will never get a CUDA update unless you explicitly do it yourself.

Tagged : / / / /

Ubuntu HowTo: sudo sh cuda_9.0.176_384.81_linux.run

Original Source Link

I am trying to install CUDA from cuda_9.0.176_384.81_linux.run file. I ran this command in Ubuntu 16.04.

sudo sh cuda_9.0.176_384.81_linux.run

When I ran the above command, I got the following error message.

sh: 0: Can't open cuda_9.0.176_384.81_linux.run

Unfortunately the guideline in nvidia website mentions .run while it is -run in the file you download. trying following would solve the problem:

sudo sh cuda_9.0.176_384.81_linux-run

Open the terminal, change directories with cd to the directory that contains the cuda_9.0.176_384.81_linux.run file and run this command:

sudo sh ./cuda_9.0.176_384.81_linux.run

I had the problem for another version of Ubuntu, I passed that by removing -run or .run from the end of command as follows:

sudo sh cuda_10.0.130_410.48_linux

Tagged : / /

Ubuntu HowTo: Terminal command to gracefully shutdown Ubuntu

Original Source Link

I am looking for a terminal command to gracefully shutdown Ubuntu. Right now I am using

sudo shutdown -h now

It seems however that this is the cause for some file system corruptions which can only be fixed manually. Attached is one example, however, others on different systems and partitions have been observed and I am not feeling well with fixing them with fsck -fy /dev/sdxx everytime they appear.


Filesystem corruption

FSCK result

Shutdown command does the shutdown gracefully. How did you come to the conclusion that shutting down is causing the problem?

Checkout hard disk repeatedly gets corrupted

  1. You can add the fsck to your GRUB so that you won’t have to do this manually every time.
  2. Backup all your data because this could mean your hard disk is damaged.

with the same software setup

That must be the common denominator. I’ve used shutdown -h now on many systems for >20 years and never had an issue with it. Even on heavily utilised database servers.

What software are you using? I’d suggest that one of your applications is taking too long to shut down or something similar.

Tagged : / /

Ubuntu HowTo: Unknown GPU memory user in nvidia-smi output

Original Source Link

I have an Ubuntu machine (16.04) with a GPU. When running nvidia-smi I get this result (all applications are closed):

| NVIDIA-SMI 440.33.01    Driver Version: 440.33.01    CUDA Version: 10.2     |
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
|  0%   56C    P0    30W / 120W |    358MiB /  6077MiB |      3%      Default |

| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|    0      1253      G   /usr/lib/xorg/Xorg                           166MiB |
|    0      2555      G   compiz                                       144MiB |
|    0     20461      G   ...AAAAAAAAAAAACAAAAAAAAAA= --shared-files    43MiB |

Does somebody know which program is in charge of the last line?

|    0     20461      G   ...AAAAAAAAAAAACAAAAAAAAAA= --shared-files    43MiB |

Tagged : / /

Ubuntu HowTo: Wallch for 16.04

Original Source Link

Wondering if there is a working version of Wallch for 16.04 x64?
The package available doesn’t seem to work – runs, but will not even show the pictures in the config…

The version in the default repositories is not currently compatible with 16.04.
It installs but doesn’t actually work once you set it up.

Adding the repository ppa:wallch/wallch-daily in 16.04 returns a
“This PPA does not support xenial” error.

Install Wallch from this page: http://packages.ubuntu.com/search?suite=xenial&searchon=names&keywords=wallch

Under Download “wallch” just click the APT install button and follow the installer on screen.

Alternatively you can download the 64 bit deb package and install manually with

sudo dpkg -i wallch_4.0-0ubuntu4_amd64.deb

I have it running and displaying BitDay-2 though out the day since it was posted on OMG Ubuntu. I wouldn’t say it runs flawless, but once it’s configured and I ticked Wallpapers on the indicator menu it started cycling the wallpapers I set.

Can you elaborate on the issue you are having?

Edit: Okay this is tricky, here is what I’m currently doing to have wallpapers cycle with this tool and working around it’s current flaws:

  1. Open the application, select the directory in wallpapers, then got to settings an configure the specific interval you want to use as the higher value, and a lower value, it should automatically set the higher value as default.
  2. Close the application.
  3. Open the application with wallch --start, you can do that in Unity via Alt+F2. Only cycle the wallpapers through the indicator menu items previous or next now.
Tagged : /