hirschme's questions

I have had a stable install of Nvidia drivers 410.78 working with my Nvidia Quadro RTX4000 Graphic Cards on my Ubuntu 18.04 for over a year now. Because of previous bad experiences with automatic upgrades breaking the system, I blacklisted any upgrades to the graphic drivers.

Today I rebooted my computer, after which the whole link to nvidia drivers and the GPUs seems to be lost. Nvidia-smi doesn't find any drivers

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

there is no folder /proc/driver/nvidia (only /proc/driver/rtc ), the program NVIDIA X Server Settings shows nothing at all.

I checked /var/log/dpkg.log and /var/log/apt/history.log for any unattended upgrades related to the graphic drivers but I see none.

This is really upsetting as whenever it has happened before, I ended up having to practically install everything from scratch, a process which is painful and very time consuming.

Is there any way I can find out what happened? Where did the nvidia drivers go? Why the reboot destroy/replaced them? And most importantly, how can I revert back to the way the system was an hour ago? Any pointers and help much appreciated.

Edit: output of "dkms status"

nvidia, 410.78, 4.15.0-1027-oem, x86_64: installed
nvidia, 410.78, 4.15.0-1101-oem, x86_64: installed
oem-ethernet-intel-igb-lp1805326-5.3.5.22, 0.1, 4.15.0-1027-oem, x86_64: installed
oem-ethernet-intel-igb-lp1805326-5.3.5.22, 0.1, 4.15.0-1101-oem, x86_64: installed

Output of zgrep 'install ' /var/log/dpkg.log* | sort | cut -f1,2,4 -d' ' | grep linux

/var/log/dpkg.log.10.gz:2020-03-18 06:57:16 linux-oem-headers-4.15.0-1076:all
/var/log/dpkg.log.10.gz:2020-03-18 06:57:21 linux-headers-4.15.0-1076-oem:amd64
/var/log/dpkg.log.10.gz:2020-03-18 06:57:24 linux-modules-4.15.0-1076-oem:amd64
/var/log/dpkg.log.10.gz:2020-03-18 06:57:30 linux-image-4.15.0-1076-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-11 07:01:17 linux-oem-headers-4.15.0-1069:all
/var/log/dpkg.log.11.gz:2020-02-11 07:01:20 linux-headers-4.15.0-1069-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-11 07:01:22 linux-modules-4.15.0-1069-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-11 07:01:27 linux-image-4.15.0-1069-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-20 06:41:24 linux-oem-headers-4.15.0-1073:all
/var/log/dpkg.log.11.gz:2020-02-20 06:41:28 linux-headers-4.15.0-1073-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-20 06:41:30 linux-modules-4.15.0-1073-oem:amd64
/var/log/dpkg.log.11.gz:2020-02-20 06:41:35 linux-image-4.15.0-1073-oem:amd64
/var/log/dpkg.log.1:2020-12-03 06:47:23 linux-oem-headers-4.15.0-1103:all
/var/log/dpkg.log.1:2020-12-03 06:47:30 linux-headers-4.15.0-1103-oem:amd64
/var/log/dpkg.log.1:2020-12-03 06:47:33 linux-modules-4.15.0-1103-oem:amd64
/var/log/dpkg.log.1:2020-12-03 06:47:45 linux-image-4.15.0-1103-oem:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:38 linux-modules-5.4.0-58-generic:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:40 linux-image-5.4.0-58-generic:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:41 linux-modules-extra-5.4.0-58-generic:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:45 linux-hwe-5.4-headers-5.4.0-58:all
/var/log/dpkg.log.1:2020-12-13 06:59:45 linux-image-generic-hwe-18.04:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:50 linux-headers-5.4.0-58-generic:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:52 linux-headers-generic-hwe-18.04:amd64
/var/log/dpkg.log.1:2020-12-13 06:59:53 linux-generic-hwe-18.04:amd64
/var/log/dpkg.log.12.gz:2020-01-08 06:17:31 linux-oem-headers-4.15.0-1066:all
/var/log/dpkg.log.12.gz:2020-01-08 06:17:35 linux-headers-4.15.0-1066-oem:amd64
/var/log/dpkg.log.12.gz:2020-01-08 06:17:37 linux-modules-4.15.0-1066-oem:amd64
/var/log/dpkg.log.12.gz:2020-01-08 06:17:42 linux-image-4.15.0-1066-oem:amd64
/var/log/dpkg.log.12.gz:2020-01-31 06:48:19 linux-oem-headers-4.15.0-1067:all
/var/log/dpkg.log.12.gz:2020-01-31 06:48:22 linux-headers-4.15.0-1067-oem:amd64
/var/log/dpkg.log.12.gz:2020-01-31 06:48:24 linux-modules-4.15.0-1067-oem:amd64
/var/log/dpkg.log.12.gz:2020-01-31 06:48:30 linux-image-4.15.0-1067-oem:amd64
/var/log/dpkg.log:2021-01-06 06:59:19 linux-modules-5.4.0-59-generic:amd64
/var/log/dpkg.log:2021-01-06 06:59:23 linux-image-5.4.0-59-generic:amd64
/var/log/dpkg.log:2021-01-06 06:59:24 linux-modules-extra-5.4.0-59-generic:amd64
/var/log/dpkg.log:2021-01-06 06:59:32 linux-hwe-5.4-headers-5.4.0-59:all
/var/log/dpkg.log:2021-01-06 06:59:37 linux-headers-5.4.0-59-generic:amd64
/var/log/dpkg.log:2021-01-08 06:53:27 linux-modules-5.4.0-60-generic:amd64
/var/log/dpkg.log:2021-01-08 06:53:29 linux-image-5.4.0-60-generic:amd64
/var/log/dpkg.log:2021-01-08 06:53:29 linux-modules-extra-5.4.0-60-generic:amd64
/var/log/dpkg.log:2021-01-08 06:53:33 linux-hwe-5.4-headers-5.4.0-60:all
/var/log/dpkg.log:2021-01-08 06:53:37 linux-headers-5.4.0-60-generic:amd64
/var/log/dpkg.log:2021-01-15 06:15:31 linux-modules-5.4.0-62-generic:amd64
/var/log/dpkg.log:2021-01-15 06:15:35 linux-image-5.4.0-62-generic:amd64
/var/log/dpkg.log:2021-01-15 06:15:36 linux-modules-extra-5.4.0-62-generic:amd64
/var/log/dpkg.log:2021-01-15 06:15:46 linux-hwe-5.4-headers-5.4.0-62:all
/var/log/dpkg.log:2021-01-15 06:15:56 linux-headers-5.4.0-62-generic:amd64
/var/log/dpkg.log.2.gz:2020-11-12 06:29:47 linux-oem-headers-4.15.0-1101:all
/var/log/dpkg.log.2.gz:2020-11-12 06:29:55 linux-headers-4.15.0-1101-oem:amd64
/var/log/dpkg.log.2.gz:2020-11-12 06:29:58 linux-modules-4.15.0-1101-oem:amd64
/var/log/dpkg.log.2.gz:2020-11-12 06:30:08 linux-image-4.15.0-1101-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-14 06:24:07 linux-oem-headers-4.15.0-1099:all
/var/log/dpkg.log.3.gz:2020-10-14 06:24:16 linux-headers-4.15.0-1099-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-14 06:24:19 linux-modules-4.15.0-1099-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-14 06:24:28 linux-image-4.15.0-1099-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-21 06:30:41 linux-oem-headers-4.15.0-1100:all
/var/log/dpkg.log.3.gz:2020-10-21 06:30:47 linux-headers-4.15.0-1100-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-21 06:30:50 linux-modules-4.15.0-1100-oem:amd64
/var/log/dpkg.log.3.gz:2020-10-21 06:30:59 linux-image-4.15.0-1100-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-03 06:31:11 linux-oem-headers-4.15.0-1094:all
/var/log/dpkg.log.4.gz:2020-09-03 06:31:15 linux-headers-4.15.0-1094-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-03 06:31:17 linux-modules-4.15.0-1094-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-03 06:31:22 linux-image-4.15.0-1094-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-09 06:47:10 linux-oem-headers-4.15.0-1096:all
/var/log/dpkg.log.4.gz:2020-09-09 06:47:14 linux-headers-4.15.0-1096-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-09 06:47:16 linux-modules-4.15.0-1096-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-09 06:47:22 linux-image-4.15.0-1096-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-23 06:43:07 linux-oem-headers-4.15.0-1097:all
/var/log/dpkg.log.4.gz:2020-09-23 06:43:11 linux-headers-4.15.0-1097-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-23 06:43:13 linux-modules-4.15.0-1097-oem:amd64
/var/log/dpkg.log.4.gz:2020-09-23 06:43:18 linux-image-4.15.0-1097-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-04 06:23:47 linux-oem-headers-4.15.0-1091:all
/var/log/dpkg.log.6.gz:2020-07-04 06:23:52 linux-headers-4.15.0-1091-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-04 06:23:55 linux-modules-4.15.0-1091-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-04 06:24:00 linux-image-4.15.0-1091-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-23 06:08:13 linux-oem-headers-4.15.0-1093:all
/var/log/dpkg.log.6.gz:2020-07-23 06:08:21 linux-headers-4.15.0-1093-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-23 06:08:24 linux-modules-4.15.0-1093-oem:amd64
/var/log/dpkg.log.6.gz:2020-07-23 06:08:30 linux-image-4.15.0-1093-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-02 06:19:59 linux-oem-headers-4.15.0-1081:all
/var/log/dpkg.log.7.gz:2020-06-02 06:20:05 linux-headers-4.15.0-1081-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-02 06:20:08 linux-modules-4.15.0-1081-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-02 06:20:15 linux-image-4.15.0-1081-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-10 06:22:46 linux-oem-headers-4.15.0-1087:all
/var/log/dpkg.log.7.gz:2020-06-10 06:22:51 linux-headers-4.15.0-1087-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-10 06:22:54 linux-modules-4.15.0-1087-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-10 06:22:59 linux-image-4.15.0-1087-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-27 06:15:50 linux-oem-headers-4.15.0-1090:all
/var/log/dpkg.log.7.gz:2020-06-27 06:15:54 linux-headers-4.15.0-1090-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-27 06:15:57 linux-modules-4.15.0-1090-oem:amd64
/var/log/dpkg.log.7.gz:2020-06-27 06:16:02 linux-image-4.15.0-1090-oem:amd64
/var/log/dpkg.log.8.gz:2020-05-01 06:20:04 linux-oem-headers-4.15.0-1080:all
/var/log/dpkg.log.8.gz:2020-05-01 06:20:08 linux-headers-4.15.0-1080-oem:amd64
/var/log/dpkg.log.8.gz:2020-05-01 06:20:11 linux-modules-4.15.0-1080-oem:amd64
/var/log/dpkg.log.8.gz:2020-05-01 06:20:16 linux-image-4.15.0-1080-oem:amd64
/var/log/dpkg.log.9.gz:2020-04-08 06:01:20 linux-oem-headers-4.15.0-1079:all
/var/log/dpkg.log.9.gz:2020-04-08 06:01:23 linux-headers-4.15.0-1079-oem:amd64
/var/log/dpkg.log.9.gz:2020-04-08 06:01:25 linux-modules-4.15.0-1079-oem:amd64
/var/log/dpkg.log.9.gz:2020-04-08 06:01:30 linux-image-4.15.0-1079-oem:amd64
/var/log/dpkg.log.9.gz:2020-04-16 14:03:23 libselinux1:i386

It seems that between then 6 and 15 of January 2021, the kernel 5.4 was installed. This was the first reboot since, so its the possible culprit.

uname -r
5.4.0-62-generic

This is my third time trying to install Wine on Ubuntu 16.04 to install a .msi windows program (Ableton live 10).

I followed these steps:

  739  sudo dpkg --add-architecture i386
  740  sudo add-apt-repository ppa:wine/wine-builds
  741  sudo apt-get update
  742  sudo apt-get install --install-recommends winehq-devel
  743  winecfg

Everything goes well and as it should (no error messages). But then on trying to install the Setup.msi file nothing happens and this error prompts:

wine msiexec /i ./Setup.msi 

0050:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0078:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114
0024:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet

I can't find any relevant links for solving these error messages for ubuntu. Looks like it needs some vulkan drivers of some kind. This is never mentioned in any installation tutorials (and I would really like to avoid installing extra graphic drivers, as I have no intention of gaming on this system).

Any hints, suggestions appreciated..!

EDIT:

After installing vulkan with

sudo apt install vulkan-utils

The error is now:

0078:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114
00bc:fixme:file:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
00bc:fixme:file:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
00bc:fixme:file:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
0024:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet

Whenever I inserted an external drive through USB, the computer would automatically mount this on /media/ , making it accessible to anyone.

From one day to another, without any apparent explanation, I need sudo rights to mount anything. And after mounting, every drive changes its access permissions to root. So for example after I mounted a SD card, now no camera or recorder can access it anymore as it is now protected.

How could this have happened? And how can I reverse this to the standard format, where anything is mounted automatically?

PS: I am looking for answers hopefully not having to modify the fstab file, as this has led to booting errors in the past.

Output of

pkaction --action-id org.freedesktop.udisks2.filesystem-mount --verbose


  description:       Mount a filesystem
  message:           Authentication is required to mount the filesystem
  vendor:            The Udisks Project
  vendor_url:        https://github.com/storaged-project/udisks
  icon:              drive-removable-media
  implicit any:      auth_admin
  implicit inactive: auth_admin
  implicit active:   yes

I bought a new computer, a precision tower 7920 with Quadro RTX 4000 GPUs. Because the nvidia driver installation is so complicated, I ordered the machine with Ubuntu (as it was supported by Dell and comes pre-installed).

However from the very first time I turned the computer on it won't boot, getting stuck at

Starting Gnome Display Manager

showing no error messages, but not moving forward from that point. Just like in this question: GUI does not start

It looks like the graphic drivers aren't installed properly. I could start debugging this. But my concern is: Should I even consider that Dell would send a new computer that is incapable of booting? Is this an 'exchange the product' case?

If I want to merge / combine multiple spreadsheets into one master spread sheet, I can just manually add them in LibreOffice. However this becomes cumbersome when dealing with a large number of sheets (>50).

Is there any way to automatize this, giving a list of spreadsheets as inputs and merging them all in one step?

EDIT:

All spreadsheets are in the same format: Same number of columns and rows, and same names.

Using disk utilities or parted I can format an external drive to exFAT, but I can't find the way to specify the allocation unit size.

The only option that looks promising is on the command line tool mkexfatfs

-s sectors-per-cluster

"Number of physical sectors per cluster (cluster is an allocation unit in exFAT). Must be a power of 2, i.e. 1, 2, 4, 8, etc. Cluster size can not exceed 32 MB. Default cluster sizes are: 4 KB if volume size is less than 256 MB, 32 KB if volume size is from 256 MB to 32 GB, 128 KB if volume size is 32 GB or larger. "

However I don't understand how to practically use this option to set an allocation unit size of, say, 2048 B.

How can this be done?

I had Ubuntu 14 running for months and everything was working fine until some automatic package upgrades made my laptop inoperable.

I am trying to install Ubuntu 18 now, but trying ubuntu live from the USB freezes everything after some seconds. Similarly, I cannot install Ubuntu because the install process freezes. The Ubuntu USB works fine as I just used it to succesfully install it in another laptop.

How can I start debugging this issue?

I recently did a fresh install of 16.04 on the solid state drive, leaving a 1.8 TB unallocated partition on the internal HDD.

Somehow I can't access this partition on /dev/sda/ and also can't mount it:

sudo mount /dev/sda /media/sda/

mount: wrong fs type, bad option, bad superblock on /dev/sda,
       missing codepage or helper program, or other error

sudo fdisk -l

Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A9243158-8BFD-4A7F-BF8B-E9F415F4573D

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048    1050623   1048576   512M EFI System
/dev/nvme0n1p2   1050624  966858751 965808128 460.5G Linux filesystem
/dev/nvme0n1p3 966858752 1000214527  33355776  15.9G Linux swap


Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 50BEB1BE-9E9E-4F9A-8F7C-E3A7BA81A788

Gparted shows /dev/sda/ as unallocated space.

Do I have to perform some type of disk repair? Or should I just allocate that space using Gparted?

Before trying to reinstall Ubuntu 16.04 all over again, erasing previous OS (Ubuntu 18.04), I did some modifications to efibootmgr.

Installation was made on the SSD (NVMe drive), and not in the Harddrive, which is giving me all kinds of trouble. All in UEFI.

The new install cannot boot because the boot files are "missing". The changes I made to efibootmgr before are still there even after complete erasing of the previous disks and complete reinstall. What I changed was adding entries grub-NVMe and boot-NVMe (see How to set mount point of boot partition to /boot/efi?). These entries are still there along with new ones, and overall all looks pretty messy.

Now the entries of efibootmgr -v are the following

efibootmgr -v

BootCurrent: 100C
Timeout: 1 seconds
BootOrder: 0000,0007,0009,0008,0006,000A,000B,0001,0002,0004,0005
Boot0000* ubuntu    HD(1,GPT,c58d6abb-383b-4281-   bb6d-4296ca698224,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* grub  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002* boot  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* grub-NVMe VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005* boot-NVMe VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* Diskette Drive          BBS(Floppy,,0x0)..GO..NO[.......+.D.i.s.k.e.t.t.e.  .D.r.i.v.e.........................rN.D+..,.\...........BO
Boot0007* M.2 PCIe SSD  BBS(HD,,0x0)..GO..NO........u.M...2. .P.C.I.e. .S.S.D....................A.............................q.........8..Gd-.;.A..MQ..L.E.I.7.7.M.0.0.0.1.1.0.8.0.7.K.0.K........BO
Boot0008* Hard Drive    BBS(CDROM,,0x0)..GO..NO........o.H.a.r.d. .D.r.i.v.e....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .4.Z.8.Z.L.X.9.1........BO
Boot0009* USB Storage Device    BBS(PCMCIA,,0x0)..GO..NO........m.U.S.B. .S.t.o.r.a.g.e. [email protected].;.A..MQ..L.3.7.2.7.0.9.4.6.7.7.5.9.1.5.2.6.2.9.2.4.2........BO
Boot000A* CD/DVD/CD-RW Device   BBS(USB,,0x0)..GO..NO........o.C.D./.D.V.D./.C.D.-.R.W. .D.e.v.i.c.e....................A...........................>..Gd-.;.A..MQ..L.Z.K.H.3.1.8.2.8.0.4. .4. . . . . . . . ........BO
Boot000B* NetWork   BBS(Network,,0x0)..GO..NO........o.N.e.t.W.o.r.k.........................rN.D+..,.\[email protected].;.A..MQ..L.Q.u.a.l.c.o.m.m. .A.t.h.e.r.o.s. .B.o.o.t........BO

Could this setting might be the reason why Ubuntu can't boot? How can I reset efibootmgr to a "normal" looking one, if necessary?

blkid:

/dev/nvme0n1p1: UUID="ABAB-B1AB" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c58d6abb-383b-4281-bb6d-4296ca698224"
/dev/nvme0n1p2: UUID="da07a979-a548-4e38-9133-e543bc486a07" TYPE="ext4" PARTUUID="8cf26198-05be-4f47-aad7-44045c44b460"
/dev/sdc1: LABEL="UBUNTU 16_0" UUID="B6D7-AAC4" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="cb704399-f613-41df-9175-a42e3d645032"

I can only run Ubuntu Live from a USB, as the installation of Ubuntu does no boot. I am trying to set the correct entries for the whole procedure to work, because no matter how I install Ubuntu, fstab, grub and efibootmgr have weird entries which do not reset.

The goal is being able to install ubuntu on the SSD (nvme0n1p1) on an UEFI system, no dual boot, no data to lose, and make it work, avoiding the error "no boot device found"

efibootmgr -v

BootCurrent: 100C
Timeout: 1 seconds
BootOrder: 0000,0007,0009,0008,0006,000A,000B,0001,0002,0004,0005
Boot0000* ubuntu    HD(1,GPT,c58d6abb-383b-4281-bb6d-4296ca698224,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* grub  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002* boot  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* grub-NVMe VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005* boot-NVMe VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* Diskette Drive    BBS(Floppy,,0x0)..GO..NO[.......+.D.i.s.k.e.t.t.e. .D.r.i.v.e.........................rN.D+..,.\...........BO
Boot0007* M.2 PCIe SSD  BBS(HD,,0x0)..GO..NO........u.M...2. .P.C.I.e. .S.S.D....................A.............................q.........8..Gd-.;.A..MQ..L.E.I.7.7.M.0.0.0.1.1.0.8.0.7.K.0.K........BO
Boot0008* Hard Drive    BBS(CDROM,,0x0)..GO..NO........o.H.a.r.d. .D.r.i.v.e....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .4.Z.8.Z.L.X.9.1........BO
Boot0009* USB Storage Device    BBS(PCMCIA,,0x0)..GO..NO........m.U.S.B. .S.t.o.r.a.g.e. [email protected].;.A..MQ..L.3.7.2.7.0.9.4.6.7.7.5.9.1.5.2.6.2.9.2.4.2........BO
Boot000A* CD/DVD/CD-RW Device   BBS(USB,,0x0)..GO..NO........o.C.D./.D.V.D./.C.D.-.R.W. .D.e.v.i.c.e....................A...........................>..Gd-.;.A..MQ..L.Z.K.H.3.1.8.2.8.0.4. .4. . . . . . . . ........BO
Boot000B* NetWork   BBS(Network,,0x0)..GO..NO........o.N.e.t.W.o.r.k.........................rN.D+..,.\[email protected].;.A..MQ..L.Q.u.a.l.c.o.m.m. .A.t.h.e.r.o.s. .B.o.o.t........BO

Notice how there are a lot of entries on efibootmgr, and most of them point to no existing partition (99e27e... not in my blkid list, not to mention Boot0007 to 000B).

cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=da07a979-a548-4e38-9133-e543bc486a07 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=ABAB-B1AB  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p3 during installation
UUID=1aa6ab58-4338-4c34-941d-6a9ee82046dc none            swap    sw              0       0

lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sr0          11:0    1  1024M  0 rom  
loop0         7:0    0   1.5G  1 loop /rofs
sdc           8:32   1   7.5G  0 disk 
└─sdc1        8:33   1   7.5G  0 part /cdrom
sda           8:0    0   1.8T  0 disk 
nvme0n1     259:0    0   477G  0 disk 
├─nvme0n1p3 259:3    0  15.9G  0 part 
├─nvme0n1p1 259:1    0   512M  0 part 
└─nvme0n1p2 259:2    0 460.5G  0 part 

/boot/efi is empty, so on efibootmgr, trying to boot from Boot0000 ubuntu /EFI/ubuntu/shimx64.efi surely wont work, as there is no such file nor folder. Dont understand why this is empty.

sudo parted /dev/nvme0n1p1 print

Model: NVMe Device (nvme)
Disk /dev/nvme0n1p1: 537MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  537MB  537MB  fat32

I feel the main issues are the empty /efi/ folder without shimx64.efi file, and the weird other entries on efibootmgr.

Any help on how to achieve stable settings?

Installation of Ubuntu 16.04 through bootable USB fails on my UEFI system (no dual boot, previously only Ubuntu installed).

I see on gparted, that the partition table on the boot partition is set to msdos, which apparently is not recommended and should be GPT.

So how can I change this, and why did the ubuntu installation fail to do this?

Installing ubuntu 16.04 from a bootable USB generates an unbootable system.

Upon inspection through the USB install, I see that the installed OS has no /boot/efi partition nor files.

Is the ubuntu installation performing installation in legacy mode? If so, how can this be explicitly changed?

I am following these instructions, and similarly this one.

I downloaded the BIOS update executable and put it into a USB drive, then after reboot I select BIOS update, where a GUI asks me to select the file. This is where I get stuck, as I cannot figure out how to select the file and continue:

Upon booting from a CD or USB with an Ubuntu iso to reinstall everything, an error appears

[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)

I have, as suggested, installed intel-microcodes and rebooted

sudo apt-get install intel-microcode

intel-microcode is already the newest version (3.20180425.1~ubuntu0.17.10.1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

After rebooting, error still there...

What can I do?

I have two ubuntu installed in my system, one on the SSD (nvme0n1p1), and one on the Harddrive (sda1).

After upgrade to 17.10, ubuntu on the SSD wont boot, not being able to find file '/boot/vmlinuz-4.13.0-041300-generic', although the files are there. (See error: file '/boot/vmlinuz-4.13.0-041300-generic' not found , how to create?)

I see now on gparted, that the partition containing these files is not mounted correctly, so grub cannot see the files.

Where as for the other OS installed in the harddrive, which is working fine, gparted shows:

On start, grub also complaints that "22ac8da-d6..." partition was not found. This is how the SSD partition is apparently mounted.

I guess I should change the mount settings, so nvme0n1p1 has /boot/efi/ as the mount point, and have nvme0n1p2 on / , in other words, exactly how the partitions are set on the harddrive (sda1, sda2).

Any help on how I can do this?

the content of /etc/fstab shows that /boot/efi/ was previously on nvme0n1p1

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=22ac8da3-d60a-46db-811d-a09ce5538215 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C1DE-5B29  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

And the output of blkid:

/dev/nvme0n1: PTUUID="eb5c38b1-7f71-4b49-a4e9-9e6ab2c9b6a4" PTTYPE="gpt"
/dev/nvme0n1p1: UUID="C1DE-5B29" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="5b57c19c-750b-457a-89f1-87130509735e"
/dev/nvme0n1p2: UUID="22ac8da3-d60a-46db-811d-a09ce5538215" TYPE="ext4" PARTUUID="2e1b8924-98f4-4821-8f48-8452620182b8"
/dev/sda1: UUID="DF5C-3936" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="2798e3ca-54f4-4528-8753-0b516c1a749c"
/dev/sda2: UUID="d37fc604-163d-4e04-83de-88993c28e419" TYPE="ext4" PARTUUID="a1331af1-a3e0-4f4e-846c-2ae70d53cb26"

Output of lsblk -f , which agrees with display of gparted:

NAME        FSTYPE LABEL UUID                                 MOUNTPOINT
sda                                                           
├─sda1      vfat         DF5C-3936                            /boot/efi
└─sda2      ext4         d37fc604-163d-4e04-83de-88993c28e419 /
sr0                                                           
nvme0n1                                                       
├─nvme0n1p1 vfat         C1DE-5B29                            
└─nvme0n1p2 ext4         22ac8da3-d60a-46db-811d-a09ce5538215 /media/lukas/22ac8da3-d60a-46db-811d-a09ce5538215

In summary: How can I set the Mount Point of /dev/nvme0n1p1 to /boot/efi/ ?

The error message upon booting on 17.10 in nvme0n1p1 is:

error: failure reading sector 0x3b9e12a0 from 'hd2'
error: failure reading sector 0x3b9e1200 from 'hd2'
error: failure reading sector 0x0 from 'hd2'
error: failure reading sector 0x3b9e12a0 from 'hd2'
error: failure reading sector 0x3b9e1200 from 'hd2'
error: failure reading sector 0x0 from 'hd2'
error: no such device: 22ac8da3-d60a-46db-811d-a09ce5538215 
error: file '/boot/vmlinuz-4.13.0-041300-generic' not found
error: you need to load the kernel first

Output of efibootmgr -v

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0008,0009
Boot0000* ubuntu    HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* grub  HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\ubuntu\grubx64.efi)
Boot0002* boot  HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\Boot\bootx64.efi)
Boot0008  Onboard NIC (IPV4)    PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(14b31f18c7f5,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0009  Onboard NIC (IPV6)    PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(14b31f18c7f5,0)/IPv6([::]:<->[::]:,0,0)..BO

Boot-Info summary:

http://paste.ubuntu.com/p/bG54zn47VZ/

boot/efi/EFI/ubuntu/grub.cfg on both the SSD and HD are the same:

search.fs_uuid d37fc604-163d-4e04-83de-88993c28e419 root hd0,gpt2 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

UPDATES from suggestions of Oldfred:

Current output of efibootmgr -v

BootOrder: 0003,0000,0001,0002,0008,0009
Boot0000* ubuntu    HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* grub  HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\ubuntu\grubx64.efi)
Boot0002* boot  HD(1,GPT,2798e3ca-54f4-4528-8753-0b516c1a749c,0x800,0x100000)/File(\EFI\Boot\bootx64.efi)
Boot0003* Ubuntu-NVMe   HD(1,GPT,5b57c19c-750b-457a-89f1-87130509735e,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0008  Onboard NIC (IPV4)    PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(14b31f18c7f5,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)..BO
Boot0009  Onboard NIC (IPV6)    PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(14b31f18c7f5,0)/IPv6([::]:<->[::]:,0,0)..BO

/boot/efi/EFI/ubuntu/grub.cfg on NVMe:

search.fs_uuid 22ac8da3-d60a-46db-811d-a09ce5538215 root hd0,gpt2 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

/boot/efi/EFI/ubuntu/grub.cfg on HDD:

search.fs_uuid d37fc604-163d-4e04-83de-88993c28e419 root hd0,gpt2 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

I had ubuntu 17.04 after the upgrade period ended. I could not upgrade to 17.10 because my sources.list was outdated and could not update because it was not maintaned anymore.

Therefore I replaced my sources.list with a copy of one that could function to upgrade the distro. I copied and pasted it. Upgrade to 17.10 went fine.

Nevertheless, this "artificial" sources.list stayed the same. I would like to get it to look like the default sources.list for 17.10, can anyone explain me how I can do this, or at least paste a version for 17.10 so I can manually replace it?

My sources list:

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the  Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
# deb http://us.archive.ubuntu.com/ubuntu/ zesty universe
# deb-src http://ca.archive.ubuntu.com/ubuntu/ zesty universe
# deb http://us.archive.ubuntu.com/ubuntu/ zesty-updates universe

## EOL upgrade sources.list
# Required
deb http://us.archive.ubuntu.com/ubuntu artful main restricted universe multiverse
deb http://us.archive.ubuntu.com/ubuntu artful-updates main restricted universe multiverse
deb http://us.archive.ubuntu.com/ubuntu artful-security main restricted universe multiverse

When I open software & updates, I do not have the option to choose the canonical partner repositories.

sudo apt-get install linux-headers-$(uname -r) 

Returns:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package linux-headers-4.10.0-42-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'linux-headers-4.10.0-42-generic' has no installation candidate

I suspect that this might be the problem behind the failed installation of new nvidia drivers.

Any ideas how to solve?

Some maybe helpful info:

uname -r

4.10.0-42-generic

dpkg-query -s linux-headers-$(uname -r)

dpkg-query: package 'linux-headers-4.10.0-42-generic' is not installed and no information is available

sudo apt list --installed | grep headers

libxmu-headers/artful,artful,now 2:1.1.2-2 all [installed,automatic]
linux-headers-4.13.0-41/artful-updates,artful-updates,artful-security,artful-security,now 4.13.0-41.46 all [installed,automatic]
linux-headers-4.13.0-41-generic/artful-updates,artful-security,now 4.13.0-41.46 amd64 [installed,automatic]
linux-headers-4.13.0-43/artful-updates,artful-updates,artful-security,artful-security,now 4.13.0-43.48 all [installed,automatic]
linux-headers-4.13.0-43-generic/artful-updates,artful-security,now 4.13.0-43.48 amd64 [installed,automatic]
linux-headers-generic/artful-updates,artful-security,now 4.13.0.43.46 amd64 [installed]

I have downloaded and installed CUDA several times, and every time it fails to pass the test samples deviceQuery and checkBandwidth. Also tensorflow is never listing the GPU between accessible devices, only the CPU.

My current nvidia driver is 384.111, where as the upgraded version 384.130 always generates a library mismatch on nvidia-smi and makes ubuntu unbootable.

Every time I try to install CUDA 9.0 with the .run file, which is the only way to install it without upgrading the nvidia drivers, it finishes with an "incomplete install message.". Runs on the tests are always negative, with the following output:

Installing CUDA 9.0 .deb with dpkg from the nvidia website https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&target_distro=Ubuntu&target_version=1710&target_type=deblocal it also upgrades the nvidia driver.

How can I install CUDA 9.0 for Ubuntu 17.10, with nvidia 384.111 without upgrading to 384.130, so that it correctly performs on the sample tests and allows tensorflow-gpu to access the graphic-card?

PS: Whenever I say "it fails", the error message is always "UNKNOWN ERROR"

The graphics card in my system is a NVIDIA GeForce GTX 1080

Previously I had installed nvidia-384 version 384.130, which I downgraded to 384.111

nvidia-smi corroborates this:

nvidia-smi

However apt show and aptitude show still keep showing the old version

apt show nvidia-384

aptitude show nvidia-384

aptitude shows the correct currently installed. But still lists 384.130 as the current version.

I am having a lot of issue installing a deep learning environment in ubuntu 17.10 (CUDA 9.0, gcc 6, cuDNN 7). So I am trying to make everything detect the correct nvidia driver version.

Why this incoherence between package versions? Are the drivers likely incorrectly installed?

ls | grep 'NC022.*nii'

Shows me all the files containing NC022 and nii.

But when I try to move them using

mv NC022.*nii NC022/

It complains that

mv: cannot stat 'NC022.*nii': No such file or directory

This happens also if I try this (as seen in other answers).

mv -t NC022 'ls | grep 'NC022.*nii''

I am struggling to see what the error is, as I have the feeling of having done exactly the same thing numerous times without errors...

How can I move all files matching a pattern into a folder?

Example of partial ls output for first command:

NC022_Background1_Raw import  W325.39 L290.nii
NC022_Background2_Copy (2) of Raw import  W325.39 L290.nii
NC022_Background3_Raw import  W1103.50 L551.nii
NC022_Mask1_mask_air.nii

In Ubuntu 17.04, image viewer suddenly does not want to display images anymore. It opens the file, but shows a blank screen, with black flickers when moving the mouse. All other programs are working fine (GIMP, inkscape, etc).

As image viewer came with the ubuntu installation I cannot find the package name to uninstall it and reinstall. Any help?