MX-17.1 on Dell XPS 13

[Jerry3904]

Pfeifend sauber:

Code: Select all

$ sudo update-grub
[sudo] password for jb: 
Generating grub configuration file ...
using custom appearance settings
Found background image: /usr/share/backgrounds/MXLinux/grub/MX-Gold1080P.png
Found linux image: /boot/vmlinuz-4.18.0-14.1-liquorix-amd64
Found initrd image: /boot/initrd.img-4.18.0-14.1-liquorix-amd64
Found linux image: /boot/vmlinuz-4.15.0-1-amd64
Found initrd image: /boot/initrd.img-4.15.0-1-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
done

[fehlix]

Pfeifend sauber:

Code: Select all

$ sudo update-grub
[sudo] password for jb: 
Generating grub configuration file ...
using custom appearance settings
Found background image: /usr/share/backgrounds/MXLinux/grub/MX-Gold1080P.png
Found linux image: /boot/vmlinuz-4.18.0-14.1-liquorix-amd64
Found initrd image: /boot/initrd.img-4.18.0-14.1-liquorix-amd64
Found linux image: /boot/vmlinuz-4.15.0-1-amd64
Found initrd image: /boot/initrd.img-4.15.0-1-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
done

Hmm, something is missing:
Can you check x-bit of/etc/grub.d/30_uefi-firmware

Code: Select all

ls -al  /etc/grub.d/30_uefi-firmware

And if unset, do

Code: Select all

sudo chmod +x /etc/grub.d/30_uefi-firmware
sudo update-grub

Reason: 30_uefi-firmware errored, in some UEFI's and would not allow to boot in into MX after installation.
Thanks

[Jerry3904]

Code: Select all

-rwxr-xr-x 1 root root 1416 Oct 15 08:37 /etc/grub.d/30_uefi-firmware

Remember that I needed to use grub2dos, since no grub would launch after installation.

[fehlix]

Code: Select all

-rwxr-xr-x 1 root root 1416 Oct 15 08:37 /etc/grub.d/30_uefi-firmware

Remember that I needed to use grub2dos, since no grub would launch after installation.

OK, last one, would this reading of UEFI-firmware produce any value

Code: Select all

printf %x \'"$(sudo cat /sys/firmware/efi/vars/OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c/data | cut -b1)"

[Jerry3904]

Code: Select all

$ printf %x \'"$(sudo cat /sys/firmware/efi/vars/OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c/data | cut -b1)"
[sudo] password for jb: 
cat: /sys/firmware/efi/vars/OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c/data: No such file or directory

BTW: with this kernel the laptop suspends correctly, and comes out of it with no residual problems as far as I can see.

[fehlix]

cat: /sys/firmware/efi/vars/OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c/data: No such file or directory
[/code]

Ok, thanks. So the DELL UEFI-fw does not provide an option to boot into fw-setup from Grub,
and in this case was not the issue for not booting into MX in the first place.

[Stevo]

Can you see any difference in the battery life between the Debian backported 4.15 kernel and the Liquorix one?

I can't really see any myself, though it's said that the Liquorix should use more power overall, due to its lower latency and because it uses cpufreq instead of p_state for CPU power control. (Install indicator-cpufreq if you want to have fine-grained control over the CPU speeds with the Liquorix kernel.)

[piperdan]

If you want to disable the touchpad only while typing on the keyboard, you could also try syndaemon
syndaemon -i 1 -d
The one is one second locking time
Possible to put it into startup,

I ended up using this, as other solutions seemed unreliable. Thanks.

This has worked well for me:

Create a bash script "touchpadt.sh"

Code: Select all

cat>touchpadt.sh

Code: Select all

#!/bin/bash

read TPdevice <<< $( xinput | sed -nre '/TouchPad/s/.*id=([0-9]*).*/\1/p' )
state=$( xinput list-props "$TPdevice" | grep "Device Enabled" | grep -o "[01]$" )

if [ "$state" -eq '1' ];then
    xinput --disable "$TPdevice" && notify-send -i emblem-nowrite "Touchpad" "Disabled"
else
    xinput --enable "$TPdevice" && notify-send -i input-touchpad "Touchpad" "Enabled"
fi

Make it executable:

Code: Select all

chmod +x touchpadt.sh

I copied it over to the /usr/bin/ directory, then went to settings > keyboard > application shortcuts to create a new shortcut key that matches my keyboard for the touchpad (F5 in my case).

[fehlix]

This has worked well for me...

Yes, it works, if you have only one touchpad device listed by xinput. For more than one it would need to loop through those attached devices.

[Jerry3904]

I finally figured out that F5 (which here means pressing Fn-F5) was already set up OOTB as a toggle for the touchpad.