Laptop Dell XPS 15

From YobiWiki
Jump to navigation Jump to search

Notes about installing a Debian Stretch on a Dell XPS 15

Hardware

Dell XPS 15 model 9550 (variant with touchscreen & PCIe m.2 ssd)

From the configuration list:

  • 6th Generation Intel(R) Core (TM) i7-6700HQ Quad Core (6M Cache, up to 3.5 GHz)
  • 16Go (2x8Go) DDR4 2133MHz
  • 15.6" 4K Ultra HD (3840 x 2160) InfinityEdge touch, Sliver
  • 1To PCIe Solid State
  • DW1830 3x3 802.11ac 2.4/5GHz + Bluetooth 4.1
  • Dell 84 WHr 6-Cell Lithium-Ion Battery
  • Internal US/International Qwerty Backlit Keyboard

From the drivers list:

  • Realtek High Definition Audio ALC3266
  • Realtek RTS5242 PCIe Gen2 CardReader
  • Realtek USB GBE Ethernet Controller
  • ST Microlectronics LNG3DMTR Motion Sensor
  • Intel HD Graphics 530/P530
  • nVIDIA Geforce GTX 960M Graphics

From dmesg (incomplete):

  • BCM20703A1 Bluetooth 4.1 (firmware brcm/BCM-0a5c-6410.hcd)

From lspci -nn: 

00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1910] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) [8086:1901] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:191b] (rev 06)
00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:1903] (rev 07)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 [8086:a160] (rev 31)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H LPSS I2C Controller #1 [8086:a161] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] [8086:a103] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1)
00:1c.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)
00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1)
00:1d.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #15 [8086:a11e] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a14e] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff)
02:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:525a] (rev 01)
04:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd Device [144d:a802] (rev 01)

From lsusb: 

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.            <= touchscreen
Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.                         <= bluetooth
Bus 001 Device 004: ID 0c45:6713 Microdia                               <= webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

From lscpu: 

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 94
Model name:            Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Stepping:              3
CPU MHz:               2847.812
CPU max MHz:           3500.0000
CPU min MHz:           800.0000
BogoMIPS:              5183.88
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush 
dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx 
f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm hwp hwp_notify hwp_act_window hwp_epp 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid 
rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1

Dell Wireless 1830 = BCM43602 + BCM20703A1 (DW1830 Bluetooth 4.1 LE)

BCM43602 PCI ID: 14e4:43ba 

# smartctl -d scsi -i /dev/nvme0n1
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.0-1-amd64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               NVMe
Product:              PM951 NVMe SAMSU
Revision:             7D0Q
Compliance:           SPC-4
User Capacity:        1,024,209,543,168 bytes [1.02 TB]
Logical block size:   512 bytes
Rotation Rate:        Solid State Device
Logical Unit id:      0x0025384cf1b0fd29
Serial number:        S2FZNXAGC03824
Device type:          disk
Local Time is:        Sun Feb 14 22:02:03 2016 CET
SMART support is:     Unavailable - device lacks SMART capability.

Resources

General

I first tried to keep a dual-boot just in case, but once we disable Raid and put SATA in AHCI mode, Windows can't boot anymore. (later I read it could be possible to fix it by rebooting several times Windows till safe mode is kicked in, but it was too late for me.)

Just in case again, one can boot Windows and create a USB recovery.

Bios

  • Secure Boot: disable
  • SATA: switch from Raid to AHCI
  • Boot: not sure it's needed but I disabled Windows boot manager entry and kept the hdd UEFI entry: UEFI: PM951 NVMe SAMSUNG 1024GB, Partition 1
  • POST/Fastboot/Thorough
  • auto os recovery threshold off

I upgraded the BIOS afterwards, no idea if it would have helped if done before the installation...
Grab it here, put it on a USB stick, reboot and select BIOS update on the boot screen (F12).
No need to put it on a bootable DOS, just give the exe to the BIOS update built-in util.
Apparently you can even drop the update on /boot/efi as it's also a FAT partition.

Debian

I kept UEFI so we need a Debian netinstall because liveCD doesn't have UEFI support yet.
But Wi-Fi requires a proprietary firmware: 

https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfmac43602-pcie.bin

so the easiest is to take a Debian netinstall with proprietary firmwares included.
At time of writing Stretch is testing and last release is alpha5: 

http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/stretch_di_alpha5/amd64/iso-cd/

dd the image on a USB stick and boot it.
It will also complain for a missing brcmfmac43602-pcie.txt but we can safely ignore it. (well I think so, but Wi-Fi has troubles now and then under heavy load, see below)

I chose a guided partitionning of the entire disk, with encrypted LVM containing /, /home and swap. But proposed / was a bit too small IMHO (10G) so I deleted and recreated / (50G) and /home.
Initially I tried to add the "discard" option for the partitions which should help on SSD but the kernel reported that "discard" wasn't supported by the disk.

If you want to backup partition table and partitions before destroying everything, it's the right time! 

parted /dev/nvme0n1
print
sgdisk --backup=/some/safe/location/nvme0n1.gpt /dev/nvme0n1

I installed Cinnamon. I don't know for the others but Cinnamon has a nice auto setting to double features on HiDPI screens.

First boot

Once installed, the Debian didn't boot up.
I tried many things but at the end the only thing that worked was to copy Debian EFI to the default one:

Starting the netinstall again, in rescue mode, get a chroot shell, then 

mount /dev/nvme0n1p1 /boot/efi
cd /boot/efi/EFI
mkdir boot
cp debian/grubx64.efi boot/bootx64.efi

I also deleted the Windows files in EFI.

Resource:

FTR things that failed included:

  • Refind couldn't boot at all. Strange as the netinstall could boot...
  • tweaks with efibootmgr, update-grub etc

UPDATE: It might be possible to fix the issue from the BIOS itself, see http://www.dell.com/support/article/us/en/04/SLN297060/en

Status

Working

  • Screen
  • Touchscreen
  • Touchpad
  • Keyboard backlight and media buttons (volume, luminosity, backlight)
  • Wi-Fi (with the proprietary driver, cf installation above)
  • HDMI
  • SD-Card reader
  • Speakers, mic
  • Webcam

Working after manual steps

i915

Screen was working but dmesg was complaining: 

i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1.bin

So I installed that firmware, not sure what it's changed 

sudo apt-get install firmware-misc-nonfree

Optimus

Resources: 

apt-get install bumblebee-nvidia
reboot

Example: 

apt-get install nvidia-settings
optirun -b none nvidia-settings -c :8

This also works for CUDA: 

optirun -b none ./cudaHashcat64.bin -m 500 example500.hash example.dict

Touchpad

Nothing wrong with the touchpad but its default config is a bit painful especially because it's large and my right palm touches it often, even with the option to diable it when typing and because it's "soft" buttons.
I disabled the button area to limit somehow the problem but still you've to get used to first touch and hold before pressing a button to do a drag and drop and not the opposite. 

synclient AreaBottomEdge=4026

To add a middle button: 

synclient RightButtonAreaLeft=3914
synclient RightButtonAreaRight=0
synclient RightButtonAreaTop=4026
synclient RightButtonAreaBottom=0
synclient MiddleButtonAreaLeft=3100
synclient MiddleButtonAreaRight=3873
synclient MiddleButtonAreaTop=4026
synclient MiddleButtonAreaBottom=0

And because I love it: 

synclient CircularScrolling=1

Some doc here and the official one here

Touchscreen

Touchscreen works well but when an external screen is connected, it spans over both screens so e.g. touching the middle of the laptop screen moves the mouse to some middle point of the virtual screen combining both screens.
To fix it, see https://wiki.archlinux.org/index.php/Calibrating_Touchscreen 

# c0 = width of laptop screen / total width
c0=$(bc -l <<< "scale=2; $(xrandr|grep -A1 eDP1|sed '1d;s/x.*//')/$(xrandr|grep '^Screen 0'|sed 's/.*current //;s/ x.*//')")
xinput set-prop "ELAN Touchscreen" --type=float "Coordinate Transformation Matrix" \
   c0 0  0 \
   0  1  0 \
   0  0  1

Bluetooth

Kernel complains about a missing file.
Apparently we can get it from Windows drivers but I don't know where to find them, so I took this one and copied it into /lib/firmware/brcm

Then Bluetooth was recognized but I couldn't pair my WM615 mouse.
After restarting the Bt adaptor, I could finally pair: 

bluetoothctl
 power off
 power on

References:

There is also a possibility to pair directly from bluetoothctl, see https://wiki.archlinux.org/index.php/bluetooth#Bluetoothctl

Small console font

I don't care but if that's an issue for you, from here: 

sudo dpkg-reconfigure console-setup
  • Choose UTF-8
  • Choose the default Combined - Latin, ... option ("Latin" includes the English alphabet)
  • Select the terminus font
  • Select 16x32
  • OK

To apply immediately, open a TTY and run setupcon, else just reboot

Sensors

apt-get install lm-sensors
sensors-detect

Sensors-detect found coretemp which is now loaded via /etc/modules: 

coretemp

Issues

i915

At some points, repetitive failures spamming syslog: 

-----------[ cut here ]------------
ARNING: CPU: 1 PID: 1349 at /build/linux-wxhyRy/linux-4.3.3/drivers/gpu/drm/i915/intel_pm.c:3668 skl_update_other_pipe_wm+0x1b5/0x1c0 [i915]()
ARN_ON(!wm_changed)
odules linked in: sd_mod sg uas usb_storage arc4 ecb md4 cifs cmac algif_hash rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd grace sunrpc fs
PU: 1 PID: 1349 Comm: Xorg Tainted: G        W  O    4.3.0-1-amd64 #1 Debian 4.3.3-7
ardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.01.15 12/18/2015
0000000000000000 0000000074139692 ffffffff812ddcf9 ffff8804ab5276b8
ffffffff81072b1d ffff8804ab5277f4 ffff8804ab527710 ffff8804aba00000
0000000000000000 ffff8800369a4b80 ffffffff81072bac ffffffffa08b31fc
all Trace:
[<ffffffff812ddcf9>] ? dump_stack+0x40/0x57
[<ffffffff81072b1d>] ? warn_slowpath_common+0x7d/0xb0
[<ffffffff81072bac>] ? warn_slowpath_fmt+0x5c/0x80
[<ffffffffa07ea225>] ? skl_update_other_pipe_wm+0x1b5/0x1c0 [i915]
[<ffffffffa07ea3e4>] ? skl_update_wm+0x1b4/0x620 [i915]
[<ffffffffa082c704>] ? gen9_read32+0xf4/0x2c0 [i915]
[<ffffffffa0847bd6>] ? intel_atomic_commit+0x3f6/0x12f0 [i915]
[<ffffffffa060d384>] ? drm_atomic_check_only+0x214/0x540 [drm]
[<ffffffffa060c7f5>] ? drm_atomic_get_crtc_state+0x65/0xc0 [drm]
[<ffffffffa060c7bc>] ? drm_atomic_get_crtc_state+0x2c/0xc0 [drm]
[<ffffffffa058b4a7>] ? drm_atomic_helper_disable_plane+0xe7/0x130 [drm_kms_helper]
[<ffffffffa05fdbed>] ? __setplane_internal+0x25d/0x320 [drm]
[<ffffffff8152c96c>] ? unix_stream_read_generic+0x25c/0x940
[<ffffffff810b599b>] ? mutex_optimistic_spin+0x10b/0x1c0
[<ffffffffa05fddca>] ? drm_mode_cursor_universal+0x11a/0x200 [drm]
[<ffffffffa05fdf2b>] ? drm_mode_cursor_common+0x7b/0x180 [drm]
[<ffffffff81474ab4>] ? ___sys_recvmsg+0x164/0x1f0
[<ffffffffa06019b4>] ? drm_mode_cursor_ioctl+0x54/0x70 [drm]
[<ffffffffa05f3260>] ? drm_ioctl+0x110/0x440 [drm]
[<ffffffffa0601960>] ? drm_mode_setcrtc+0x4e0/0x4e0 [drm]
[<ffffffff810d77cc>] ? enqueue_hrtimer+0x3c/0x70
[<ffffffff810d8227>] ? hrtimer_start_range_ns+0x1d7/0x3d0
[<ffffffff811dfec5>] ? do_vfs_ioctl+0x2a5/0x490
[<ffffffff8107dce7>] ? recalc_sigpending+0x17/0x50
[<ffffffff8107eb4d>] ? __set_task_blocked+0x3d/0x90
[<ffffffff81081361>] ? __set_current_blocked+0x31/0x50
[<ffffffff811e0124>] ? SyS_ioctl+0x74/0x80
[<ffffffff8108157b>] ? SyS_rt_sigprocmask+0x8b/0xc0
[<ffffffff81585df2>] ? system_call_fast_compare_end+0xc/0x67
--[ end trace d9370809ce0073c9 ]---

See https://bugs.freedesktop.org/attachment.cgi?id=121569

Bluetooth

WM615 mouse is now paired but is not smooth, the cursor stops now and then.
I paired it with an Android phone and there it runs very smoothly so the issue is somewhere on the Dell...

Wi-Fi

Wi-Fi tends to disassociate under heavy load, switching to other SSIDs or frequencies (5Ghz<>2.4GHz) and coming back seems to help.
Maybe a proper firmware settings .txt would help?

Examples flooding syslog: 

brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 835 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 639 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 775 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 0 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 210 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 251 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 318 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 790 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 509 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 869 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 711 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 282 (not in use)
brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 247 (not in use)

brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !!
net_ratelimit: 1292 callbacks suppressed

brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
brcmfmac 0000:02:00.0: swiotlb buffer is full (sz: 2048 bytes)
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 52 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 52 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 52 bytes at device 0000:02:00.0
DMA: Out of SW-IOMMU space for 2048 bytes at device 0000:02:00.0

This last one forced me to reboot...

Current firmware available in kernel repo, wiki and in Debian repo is: 

strings /lib/firmware/brcm/brcmfmac43602-pcie.bin |tail -n1
43602a1-roml/pcie-ag-pktctx-splitrx-amsdutx-txbf-p2p-mchan-idauth-idsup-tdls-mfp-sr-proptxstatus-pktfilter-wowlpf-ampduhostreorder-keepalive-srom12-chkd2hdma 
Version: 7.35.177.61 CRC: 55b10cfe Date: Tue 2015-11-10 06:39:55 PST Ucode Ver: 986.122 FWID: 01-ea662a8c

There is a newer version in Dell drivers: 

strings Communications_Driver_6XDK6_WN32_1.555.0.0_A03/Drivers/WinThresh/WL/x64/43602a1rtecdc.bin|tail -n 1
43602a1-roml/pcie-ag-msgbuf-chkd2hdma-ndis-vista-dhdoid-ap-p2p-txbf-pktctx-amsdutx-pktfilter-pno-aoe-ndoe-gtkoe-mfp-proptxstatus-keepalive-sr-ampduretry-d0c-srom12-fbt-assocmgr 
Version: 7.35.240.51 CRC: ee76d57b Date: Thu 2015-11-26 02:39:07 PST Ucode Ver: 986.120 FWID: 01-ed0fd8f3

but with that one it fails to associate to access-points...

Screen blank

When waking from screen off, the screen very often turns on but is entrely black.
And dmesg reports sth like this: 

[drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start channel equalization

See issue here
It might be solved in kernel 4.4, I 'll wait for it to be in Sid.

Workaround1:

  • if there is a remote connection possible, this solves the issue:
DISPLAY=:0.0 xset dpms force off
sleep 1
DISPLAY=:0.0 xset dpms force on

or 

DISPLAY=:0.0 xrandr --output eDP1 --off
sleep 1
DISPLAY=:0.0 xrandr --output eDP1 --auto

Some associated those commands to a shortcut, but this still requires to login properly with a blank screen...
When an external screen is attached, the external screen is not affected.

Workaround2:

  • Close LID (and the machine goes to sleep) and open it again

Mitigation:

  • Prefs / Power management / Turn off the screen + on A/C: never

rfkill button

Rfkill button of the keyboard (Fn+PrtScr) doesn't seem to work, no big deal.

HiDPI

Cinnamon handles it nicely but some applications don't such as Gimp and you end up with a microscopic tools ribbon.
Virtualbox: View/Scale Factor is helpful...

DA200

DA200 is recognized only if it was plugged at boot.
The adapter is actually using DisplayPort.
HDMI output doesn't work, it's recognized by xrandr as 'DP1' as for the VGA.
VGA output works.

When plugged the following hardware gets detected:

lsusb: 

Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp..     <= Ethernet
Bus 004 Device 002: ID 05e3:0617 Genesys Logic, Inc..
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0835:2a01 Action Star Enterprise Co., Ltd. <= Billboard
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The USB Billboard Device Class definition describes the methods used to communicate the Alternate Modes supported by a device container to a host system. More details on Billboard Devices are available in the USB Billboard Device Class specification at the following link: http://www.usb.org/developers/docs/devclass_docs/.

lspci: 

06:00.0 PCI bridge: Intel Corporation Device 1576 (prog-if 00 [Normal decode])
07:00.0 PCI bridge: Intel Corporation Device 1576 (prog-if 00 [Normal decode])
07:01.0 PCI bridge: Intel Corporation Device 1576 (prog-if 00 [Normal decode])
07:02.0 PCI bridge: Intel Corporation Device 1576 (prog-if 00 [Normal decode])
0a:00.0 USB controller: Intel Corporation Device 15b5 (prog-if 30 [XHCI])

lsmod: 

r8152                  49152  0
cdc_ether              16384  0
usbnet                 40960  1 cdc_ether
mii                    16384  2 r8152,usbnet

One can somehow force detection if plugged after boot: 

# echo 1 > /sys/bus/pci/rescan

But for me it works only once then if removed, rescan doesn't remove things and re-plugging doesn't work.
Moreover with kernel 4.3 I hit the bug related to i915 mentioned here and there.
VGA output seems to work without rescan but with kernel 4.5.0, eDP1 becomes noisy. Unplugging VGA fixes the problem immediately.

Kernels

initramfs complains about lvmetad and I'm not sure it's that useful on SSD, so just disabling it:
Edit /etc/lvm/lvm.conf 

use_lvmetad=0

Then stop it 

systemctl stop lvm2-lvmetad

Warning, to compile >=4.4, one needs at least initramfs-tools v0.122 to get the nvme.ko properly loaded and therefore the SSD properly seen.

To compile a vanilla kernel, cf http://www.cyberciti.biz/faq/debian-ubuntu-building-installing-a-custom-linux-kernel/ 

sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc
sudo apt-get install kernel-package
wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.tar.xz
tar xf linux-4.4.tar.xz
cd linux-4.4
cp /boot/config-$(uname -r) .config
make menuconfig
make-kpkg clean
make-kpkg --rootcmd fakeroot --initrd --append_to_version=9-doegox kernel_image kernel_headers -j 7

4.4.0

Testing linux-image-4.4.0-1-amd64 from Debian Experimental:

  • it just doesn't boot, stalls immediately after loading initrd

Testing from vanilla:

  • vanilla 4.4 with config from Debian 4.3.0-1-amd64 and general rule to enable as module whatever was new
cp /boot/config-$(uname -r) .config
make oldconfig
  • Seems better than 4.3, no more issues with i915

Testing from vanilla with config closer to linux-image-4.4.0-1-amd64 (trying to understand why the Debian one doesn't boot):

  • vanilla 4.4 with config from Debian 4.4.0-1-amd64 and adjusting the minimum because apparently 4.4.0-1-amd64 is a 4.4.2
--- config-4.4.0-1-amd64	2016-02-21 16:36:18.000000000 +0100
+++ config-4.4.0-9-doegox	2016-02-22 23:07:13.000000000 +0100
-# Linux/x86 4.4.2 Kernel Configuration
+# Linux/x86_64 4.4.0-9-doegox Kernel Configuration
-CONFIG_MEMCG_DISABLED=y
-CONFIG_X86_X32_DISABLED=y
+CONFIG_FB_NVIDIA=m
+CONFIG_FB_NVIDIA_BACKLIGHT=y
+CONFIG_FB_RIVA=m
+CONFIG_FB_RIVA_BACKLIGHT=y
-CONFIG_GRKERNSEC=y
-CONFIG_GRKERNSEC_PERF_HARDEN=y

I inspected both initrd and besides rivafb.ko and nvidiafb.ko (which are probably useless) there is no diff.
Still, this kernel boots, but the same problem as with 4.5.0 appears:

  • can't config touchpad with synclient

See 4.5.0 for the fix.

4.5.0

Testing linux-image-4.5.0-rc4-amd64 (4.5~rc4-1~exp1) from Debian Experimental:

  • no more issues with i915, no more black screen when screen awakes :)
  • can't config touchpad with synclient
    • solved, see below
  • can't compile DKMS modules
    • solved, see below

Touchpad problem:
This is because touchpad got detected twice, cf /var/log/Xorg.0.log 

[    13.212] (II) config/udev: Adding input device DLL06E4:01 06CB:7A13 Touchpad (/dev/input/event12)
[    13.353] (II) config/udev: Adding input device DLL06E4:01 06CB:7A13 Touchpad (/dev/input/mouse2)
[    13.357] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
[    13.445] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)

See also in dmesg the spurious driver: 

[    0.341039] pnp 00:05: Plug and Play ACPI device, IDs DLL06e4 PNP0f13 (active)
[    8.231092] input: DLL06E4:01 06CB:7A13 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL06E4:01/0018:06CB:7A13.0003/input/input14
[    8.231227] hid-multitouch 0018:06CB:7A13.0003: input,hidraw2: I2C HID v1.00 Mouse [DLL06E4:01 06CB:7A13] on i2c-DLL06E4:01

DLL06E4:01 06CB:7A13 Touchpad must be prevented
=> Add /etc/modprobe.d/synaptics.conf: 

blacklist i2c-designware-platform

Blacklisting i2c-hid a explained elsewhere didn't help me.

DKMS problem:
When installing kernel, one gets such kind of message for each DKMS module to compile: 

Error! Bad return status for module build on kernel: 4.5.0-rc4-amd64 (x86_64)
Consult /var/lib/dkms/.../build/make.log for more information.

And in the log, something about Makefile.ubsan not found.
=> patching /usr/src/linux-headers-4.5.0-rc4-common/Makefile 

--- Makefile	2016-02-23 08:36:50.955634064 +0100
+++ Makefile	2016-02-23 08:37:06.063634513 +0100
@@ -413,7 +413,7 @@
 export HOSTCXX HOSTCXXFLAGS LDFLAGS_MODULE CHECK CHECKFLAGS
 
 export KBUILD_CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS LDFLAGS
-export KBUILD_CFLAGS CFLAGS_KERNEL CFLAGS_MODULE CFLAGS_GCOV CFLAGS_KASAN CFLAGS_UBSAN
+export KBUILD_CFLAGS CFLAGS_KERNEL CFLAGS_MODULE CFLAGS_GCOV CFLAGS_KASAN
 export KBUILD_AFLAGS AFLAGS_KERNEL AFLAGS_MODULE
 export KBUILD_AFLAGS_MODULE KBUILD_CFLAGS_MODULE KBUILD_LDFLAGS_MODULE
 export KBUILD_AFLAGS_KERNEL KBUILD_CFLAGS_KERNEL
@@ -788,7 +788,6 @@
 
 include scripts/Makefile.kasan
 include scripts/Makefile.extrawarn
-include scripts/Makefile.ubsan
 
 # Add any arch overrides and user supplied CPPFLAGS, AFLAGS and CFLAGS as the
 # last assignments

dpkg-reconfigure linux-image-4.5.0-rc4-amd64

It's probably related with a recent attempt to integrate UBSan (undefined behaviour sanitizer (runtime)) in new kernels...

Changes

I'll try a few changes... to be continued

Replacing Broadcom Wi-Fi+BT by an Intel one:

Alternatives to DA200:

Misc

Smartcard reader

Retrieved from "https://wiki.yobi.be/index.php?title=Laptop_Dell_XPS_15&oldid=9969"