PPP's questions

My bluetooth always worked on this Dell XPS 13 but after a power outage it won't work anymore. I think wifi and bluetooth are in the same pcie module but I'm not sure.

On bluetooth settings it says no dongle.

lz@xps13:~$ lspci
0000:00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01)
0000:00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01)
0000:00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
0000:00:06.0 System peripheral: Intel Corporation Device 09ab
0000:00:07.0 PCI bridge: Intel Corporation Device 9a23 (rev 01)
0000:00:07.2 PCI bridge: Intel Corporation Device 9a27 (rev 01)
0000:00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
0000:00:0d.0 USB controller: Intel Corporation Device 9a13 (rev 01)
0000:00:0d.2 USB controller: Intel Corporation Device 9a1b (rev 01)
0000:00:0d.3 USB controller: Intel Corporation Device 9a1d (rev 01)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
0000:00:12.0 Serial controller: Intel Corporation Device a0fc (rev 20)
0000:00:14.0 USB controller: Intel Corporation Device a0ed (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20)
0000:00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20)
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20)
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20)
0000:00:19.0 Serial bus controller [0c80]: Intel Corporation Device a0c5 (rev 20)
0000:00:19.1 Serial bus controller [0c80]: Intel Corporation Device a0c6 (rev 20)
0000:00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
0000:00:1d.0 PCI bridge: Intel Corporation Device a0b3 (rev 20)
0000:00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20)
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20)
0000:71:00.0 Network controller: Qualcomm Device 1101 (rev 01)
0000:72:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
10000:e0:06.0 PCI bridge: Intel Corporation Device 9a09 (rev 01)
10000:e1:00.0 Non-Volatile memory controller: Toshiba Corporation Device 011a

There's nothing about bluetooth on dmesg.

lz@xps13:~$ sudo dmesg | grep -i blue

nothing.

Ubuntu 20.04

uname -r
5.10.0-1023-oem

UPDATE:

after some reboots:

lz@xps13:~$ sudo dmesg | grep -i blue
[sudo] password for lz: 
[   12.090787] Bluetooth: Core ver 2.22
[   12.090805] Bluetooth: HCI device and connection manager initialized
[   12.090808] Bluetooth: HCI socket layer initialized
[   12.090810] Bluetooth: L2CAP socket layer initialized
[   12.090812] Bluetooth: SCO socket layer initialized
[   12.165009] Bluetooth: HCI UART driver ver 2.3
[   12.165011] Bluetooth: HCI UART protocol H4 registered
[   12.165012] Bluetooth: HCI UART protocol BCSP registered
[   12.165020] Bluetooth: HCI UART protocol LL registered
[   12.165021] Bluetooth: HCI UART protocol ATH3K registered
[   12.165026] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   12.165052] Bluetooth: HCI UART protocol Intel registered
[   12.165082] Bluetooth: HCI UART protocol Broadcom registered
[   12.165087] Bluetooth: HCI UART protocol QCA registered
[   12.165087] Bluetooth: HCI UART protocol AG6XX registered
[   12.165092] Bluetooth: HCI UART protocol Marvell registered
[   13.778233] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.778235] Bluetooth: BNEP filters: protocol multicast
[   13.778239] Bluetooth: BNEP socket layer initialized

but I still see no bluetooth in the settings, it says it couldnt find a bluetooth device

On my Dell XPS 13 9310, when I try to use a secondary HDMI monitor, through an usb-c HDMI adapter, I get these screen glithces, mostly when I click on the other screen, or when I try to scroll the browser on the main screen.

I tried with 2 different USB-C HDMI adapters just to make sure it wasn't a problem with the one I was using.

Ubuntu 20.04

Kernel: 5.10.0-1013-oem

Video: https://imgur.com/a/niwvcV0

This page https://developer.download.nvidia.cn/compute/cuda/repos/ubuntu1804/x86_64/ list lots of drivers.

I need to install the version nvidia-driver-440_440.33.01-0ubuntu1_amd64.deb because my dmesg is saying:

NVRM: API mismatch: the client has the version 440.33, but
NVRM: this kernel module has the version 440.100.  Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.

after I run

docker run --gpus all nvidia/cuda:10.0-base nvidia-smi

So I need the specific version 440.33

I tried downloading and installing:

sudo apt install -y ./nvidia-driver-440_440.33.01-0ubuntu1_amd64.deb 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'nvidia-driver-440' instead of './nvidia-driver-440_440.33.01-0ubuntu1_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver-440 : Depends: libnvidia-gl-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: nvidia-dkms-440 (= 440.33.01-0ubuntu1)
                     Depends: nvidia-kernel-source-440 (= 440.33.01-0ubuntu1) but it is not going to be installed
                     Depends: libnvidia-compute-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: nvidia-compute-utils-440 (= 440.33.01-0ubuntu1) but it is not going to be installed
                     Depends: libnvidia-decode-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: libnvidia-encode-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: nvidia-utils-440 (= 440.33.01-0ubuntu1) but it is not going to be installed
                     Depends: xserver-xorg-video-nvidia-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: libnvidia-cfg1-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: libnvidia-ifr1-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Depends: libnvidia-fbc1-440 (= 440.33.01-0ubuntu1) but 440.100-0ubuntu0.20.04.1 is to be installed
                     Recommends: nvidia-settings but it is not going to be installed
                     Recommends: nvidia-prime (>= 0.8) but it is not going to be installed
                     Recommends: libnvidia-compute-440:i386 (= 440.33.01-0ubuntu1)
                     Recommends: libnvidia-decode-440:i386 (= 440.33.01-0ubuntu1)
                     Recommends: libnvidia-encode-440:i386 (= 440.33.01-0ubuntu1)
                     Recommends: libnvidia-ifr1-440:i386 (= 440.33.01-0ubuntu1)
                     Recommends: libnvidia-fbc1-440:i386 (= 440.33.01-0ubuntu1)
                     Recommends: libnvidia-gl-440:i386 (= 440.33.01-0ubuntu1)
E: Unable to correct problems, you have held broken packages.

On ubuntu bionic from Docker, I'm getting this:

No such file or directory
 #include <filesystem>

on a C++ file that does this:

#if __cplusplus >= 201703L
#include <filesystem>
#endif

when trying to compile with clang 6.0. Unfortunately I cannot move to experimental/filesystem because it's not my library, it's from OpenVPN3. I tried with clang 10 and still got the error.

Ubuntu 20.04 (focal on docker) works! However I wanted to use a more older version to have compatibility with older systems.

This is the output that cmake/make produces when compiling the file that gives the error:

cd /workspaces/libopenvpnclient/build/src && /usr/local/clang/bin/clang++  -DASIO_STANDALONE

 -DHAVE_LZ4 -DLZ4_DISABLE_DEPRECATE_WARNINGS -DMBEDTLS_DEPRECATED_REMOVED -DUSE_ASIO 

-DUSE_OPENSSL -I/workspaces/libopenvpnclient/src/../openvpn3 -I/workspaces/libopenvpnclient

/src/../libtins/include -I/workspaces/libopenvpnclient/src/../asio/asio/include -I/workspaces

/libopenvpnclient/src/../literal_ipaddr -I/workspaces/libopenvpnclient/openvpn3/cmake/..

 -I/workspaces/libopenvpnclient/openvpn3/cmake/../../deps/asio/asio/include  -Wall -Wsign-

compare -Wno-missing-field-initializers -std=c++1z -o CMakeFiles/libopenvpn_example.dir

/OpenVPNClient.cpp.o -c /workspaces/libopenvpnclient/src/OpenVPNClient.cpp

I guess something's wrong with libstdc++ on Ubuntu 18?

Dockerfile:

FROM ubuntu:bionic

RUN export DEBIAN_FRONTEND=noninteractive && apt-get update \
&& apt-get install -y clang-6.0 lldb iptables iproute2 cmake \
build-essential libmbedtls-dev libssl-dev liblz4-dev curl git \
xz-utils wget libncurses5

RUN curl --proto '=https' --tlsv1.2 -o rust.sh https://sh.rustup.rs\
    && /bin/bash rust.sh -y


RUN wget -O clang.tar.xz https://github.com/llvm/llvm-project/releases/download/llvmorg-10.0.0/clang+llvm-10.0.0-x86_64-linux-gnu-ubuntu-18.04.tar.xz \
&& mkdir clang && tar xf clang.tar.xz -C clang --strip-components 1 \
&& mv clang /usr/local/clang

WORKDIR /home/project

ENV PATH="/root/.cargo/bin:${PATH}"
ENV PATH="/usr/local/cmake/bin:${PATH}"

simply changing bionic to focal makes the compilation work.

I generated a backup of my master key and 3 sub keys following this into these archives:

gpg.conf
mastersub.key
openpgp-recovs.d
private-keys-v1.d (contains 4 .key files)
pubring.kbx
random_seed
reader_0.status
sub.key
tofu.db
trustdb.gpg

how can I put those back into my smartcard (yubikey)?

I have a boot video problem Ubuntu 18.04-4 installs in safe graphics mode only, but boots to purple screen where mouse works (NVIDIA) that can be solved by enabling Wayland

How can I enable Wayland? The gear icon wont appear on my login screen. I also tried editing /etc/gdm3/custom.conf and commenting WaylandEnable=... or putting WaylandEnable=true but I dont ever get the gear icon, and also echo $XGD_SESSION_TYPE gives me x11 always even after reboot.

3 days ago I bougth computer parts and put them together. Ubuntu 19.10 would only install in safe graphics mode, but it worked. Then I changed my motherboard and sent the old one back to the seller. The ubuntu continue working. Then I reinstalled ubuntu 19 and now when I boot, I end up in a purple screen where the mouse works, but nothing more. Just purple and mouse. If I use nomodeset I end up in a flickering screen after boot. Flickers from black to almost black.

Ubuntu 18.04.4 will also only install/live boot in safe graphics mode, but after installation, I boot into purple screen with mouse working. I entered the grub menu and added nomodeset to my kernel but when I boot with it I get a flickering screen (from black to almost black) ando nothing more happens.

On more older kernels (4.15.x) I can get up to the login screen, when I put the password I enter a black screen and then HDMI loses signal.

I don't know why it worked on the older motherboard and even worke don the new one. Only after I reinstalled things it stopped working.

If I install with "download proprietary drivers" on, I get it to boot, but into the resolution 1024x768, which I can't change.

But I don't want to use proprietary drivers, I don't want to install aything proprietary in this machine, only in the virtual machines.

UPDATE: I remember what I did! If I plug the GPU in the first slot (and change the motherboard to use video at slot 1) I arrive at the login screen, but if I just log in, I get a black screen. However, if I change, in the small gear icon, to use Wayland instead of Xorg, I can login correctly. Then I can simply put the GPU back into slot 2 and change the motherboard to use video in slot 2. Then everything works!

However, I'd still like to get into the root of these problems, I found that video debugging in linux is very weak and I'd like to understand what is happening, because I really hate installing proprietary drivers.

Just like nvidia has the Nouveau driver alternative for its boards, aren't there alternatives for broadcom/TPLink pcie cards like mine: Ac1300 Archer T6e?

I'm very unconfortable in running proprietary drivers on my Ubuntu, specially the network one, which is the most dangerous and certainly have backdoors.

I know spice is used by virt-manager to control virtual machines. Can I use SPICE to do the same thing but over a fast 5ghz local network? I want to control the machine on the other room but I need it to be really fast, so VNC is out of question.

Reading the spice downloads page there are lots of servers and clients, I'm lost. How can I make SPICE work like VNC? Can I also plug USB things in one computer and use them in another?

How can I remote control my hardware Ubuntu desktop with spice, instead of vnc? has no answers

UPDATE: the intent is to use it with virtual machines in a server on the room

I have an unconventional setup in which nothing is installed, so I installed gnome-control-center, but when I click bluetooth, it says there's no bluetooth devices. However, when I run bluetoothctl I can scan and connect to bluetooth devices.

So what's missing for my bluetooth usb device appear in the control panel?

UPDATE:

ubuntu 18.04

After a lot of upgrading (I think 1000 packages since I didn't upgrade for a long time), I can connect to wireless networks, but I can't ping anything. It says name or service not known. Firefox will immediately fail to load any page.

I even tried my tethered usb connection from my phone which I used a lot and it won't even appear as connected. Even Bluetooth tether won't work.

Some output which might be helpful:

I use ufw firewall but it is disabled.

UPDATE:

I 'fixed' it by adding google DNS servers on resolv.conf. I'm connecting normally but I keep receiving notifications: "network activation failed", but it still works without any problems. Maybe I did not attack the source of the problem. Any ideas?

I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave e this error after 2 weeks of usage. After that, I installed 16.04 and used it for months without any problems, until it produced the same error today. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though.

(I even did some stress tests, by downloading 100s of gb of data lots of times, and having my disk almost full, and I got none of these errors while in 16.04 without updates)

After I run fsck manually, it solves the problem but it happens again after some time.

UPDATE:

It happened again (with the 17.10.1 fresh install with no updates that I was using since the day I started this post. I noticed the problem because I tried to save one of my VMs into disk and it said that my disk was read only. Then I ran:

lz@lz:/var/log$ touch something
touch: cannot touch 'something': Read-only file system


lz@lz:/var/log$ cat syslog
Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0


lz@lz:/var/log$ dmesg
[62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.377374] Aborting journal on device nvme0n1p2-8.
[62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12  capname="net_admin"

I then rebooted and did fsck /dev/nvm.... It asked me about lots of inodes, I did 'yes' to all, and at a moment it stopped.

https://imgur.com/a/cfbPD (this photo shows the entire output, but not much visible) https://imgur.com/a/VFoPB (this one is better but it cuts a bit of the output)

Here's a video of the entire process: https://photos.app.goo.gl/8ZHF3Un1BOsRwjaz1

I'm going to apply the microcode patch as the answer below suggest, but I don't think it has to do with the problem, as this is happening months before meltdown and spectre. And I had never even installed a microcode update.

I still think it has to do with the problem I described on my post. Can somebody give me details about if it was fixed, in which kernels it is fixed? What should I do?

Anyways, I just applied the suggested correction of adding

nvme_core.default_ps_max_latency_us=5500

to the boot parameters. Going to see how the syste behaves with it.

UPDATE: every time I install a new system, it behaves well until I decide to use the software updater! Then it enters in read-only mode :(

I tried with nvme_core.default_ps_max_latency_us=250 and it didn't work

UPDATE: everything seems to work FINE when I install windows. Even the benchmark tests says everything is ok

UPDATE (03/10/2019)

I still have this problem. It happens once a day, but happens a lot when there' s heavy ssd usage.

I tried with a brand new Samsung 960 EVO 2156gb SSD and the problem persists, so it' s not related to the SSD itself. However I made the mistake of buying one of the same brand and related model. I did not test non samsung SSDs.

Both SSDs run perfect on Windows. I even did LOTS of benchmark tests which stressed them a lot. No problems.

I tried ubuntu 16, 18, 19, Debian 10, Linux Mint. All give the same problem. Can somebody help me find the source of the problem? I spent a LOT on this computer and don' t have money to buy a new one.

My grub file now:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""