USB live MX Linux on surface pro 7 with Win 11

[j2mcgreg]

I think that in this case, @Eadwine Rose's memory was faulty. I seem to remember that @dolphin_oracle has stated that our Live System won't work with SystemD, so it's not included. However this option is included in the installed version.

[dolphin_oracle]

the live system on MX 23.6 can use systemd with the init=/lib/systemd/systemd boot parameter added. there will be some error messages on shutdown, but its good enough for doing installs if necessary.

[Eadwine Rose]

Oh.. well.. it used to be in the menu. And I know for a fact. I didn't know it was removed from there, I don't check that every time. All I know is there is talk of removing it completely, but did not think that would be the case for the current versions.

[richb]

I think that in this case, @Eadwine Rose's memory was faulty. I seem to remember that @dolphin_oracle has stated that our Live System won't work with SystemD, so it's not included. However this option is included in the installed version.

I run SystemD with kDE. Make snapshots of my system about twice a month and a Live USB. Maybe I am not understanding what you are saying.

[Nokkaelaein]

Oh.. well.. it used to be in the menu. And I know for a fact. I didn't know it was removed from there, I don't check that every time. All I know is there is talk of removing it completely, but did not think that would be the case for the current versions.

You are mixing up the live booting menu with the menu of the installed system. There has never been a "boot using systemd" type of entry anywhere in the stock MX Linux live booting menu.

Second, yep consider this a confirming anecdote from here as well, the live system works very nice with systemd. Through the years I've installed a live booting MX system on USB devices literally hundreds of times. Lately, I've been using a systemd-only version for my own such system for months now. When you author an ISO with MX Snapshot on a systemd-only installation, the ISO (and subsequent live booting system) will be a systemd one, no questions asked. And it works quite beautifully. Have been using a live system like that literally daily since February.

[j2mcgreg]

I think that in this case, @Eadwine Rose's memory was faulty. I seem to remember that @dolphin_oracle has stated that our Live System won't work with SystemD, so it's not included. However this option is included in the installed version.

I run SystemD with kDE. Make snapshots of my system about twice a month and a Live USB. Maybe I am not understanding what you are saying.

Before I wrote that, I checked a stock MX 23.6 XFCE stick and there was no option to switch to a SystemD kernel for a live session. dolphin_oracle clarified in post #12 that it could be achieved with an added boot parameter.

[richb]

I think that in this case, @Eadwine Rose's memory was faulty. I seem to remember that @dolphin_oracle has stated that our Live System won't work with SystemD, so it's not included. However this option is included in the installed version.

I run SystemD with kDE. Make snapshots of my system about twice a month and a Live USB. Maybe I am not understanding what you are saying.

Before I wrote that, I checked a stock MX 23.6 XFCE stick and there was no option to switch to a SystemD kernel for a live session. dolphin_oracle clarified in post #12 that it could be achieved with an added boot parameter.

Yes I misunderstood. There is no systemD boot option and the Live runs sysvinit.

[andrewedmondson]

Thanks Dolphon_Oracle, though this has to be typed in before each boot.

I can install MX Linux on the Surface 7 but the problem is with the touch screen, so I followed the instructions from Github to install the surface pro kernel.
It completed this but with errors. I have attached the terminal report below.

I checked that the new kernel had been created and is persisting on the USB but rebooting does not bring me to the blue screen where the key for the new kernel is inserted.
I used sudo apt install linux-surface-secureboot-mok for this.

Curiously, the virtual touch keyboard works before MX Linux starts up.

Code: Select all

$ echo "deb [arch=amd64] https://pkg.surfacelinux.com/debian release main" \
        | sudo tee /etc/apt/sources.list.d/linux-surface.list
deb [arch=amd64] https://pkg.surfacelinux.com/debian release main
demo@mx1:~
$ wget -qO - https://raw.githubusercontent.com/linux-surface/linux-surface/master/pkg/keys/surface.asc \
    | gpg --dearmor | sudo dd of=/etc/apt/trusted.gpg.d/linux-surface.gpg
4+1 records in
4+1 records out
2233 bytes (2.2 kB, 2.2 KiB) copied, 0.740668 s, 3.0 kB/s
demo@mx1:~
$ sudo apt update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease                       
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease                                      
Hit:3 http://deb.debian.org/debian bookworm InRelease                                              
Hit:4 https://mxrepo.com/mx/repo bookworm InRelease                                                
Get:5 https://pkg.surfacelinux.com/debian release InRelease [1,836 B]      
Get:6 https://pkg.surfacelinux.com/debian release/main amd64 Packages [26.6 kB]
Fetched 28.4 kB in 4s (7,336 B/s)   
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
152 packages can be upgraded. Run 'apt list --upgradable' to see them.
demo@mx1:~
$ sudo apt install linux-image-surface linux-headers-surface libwacom-surface iptsd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libwacom-bin-surface libwacom-common-surface libwacom2-surface libwacom9-surface
  linux-headers-6.14.2-surface-1 linux-image-6.14.2-surface-1
The following packages will be REMOVED:
  libwacom-common libwacom9
The following NEW packages will be installed:
  iptsd libwacom-bin-surface libwacom-common-surface libwacom-surface libwacom2-surface
  libwacom9-surface linux-headers-6.14.2-surface-1 linux-headers-surface
  linux-image-6.14.2-surface-1 linux-image-surface
0 upgraded, 10 newly installed, 2 to remove and 152 not upgraded.
Need to get 101 MB of archives.
After this operation, 552 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://pkg.surfacelinux.com/debian release/main amd64 libwacom9-surface amd64 2.15.0-1 [27.5 kB]
Get:2 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-common-surface amd64 2.15.0-1 [181 kB]
Get:3 https://pkg.surfacelinux.com/debian release/main amd64 iptsd amd64 3.0.1-1 [956 kB]          
Get:4 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-bin-surface amd64 2.15.0-1 [17.5 kB]
Get:5 https://pkg.surfacelinux.com/debian release/main amd64 libwacom2-surface amd64 2.15.0-1 [22.9 kB]
Get:6 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-surface amd64 2.15.0-1 [1,870 B]
Get:7 https://pkg.surfacelinux.com/debian release/main amd64 linux-headers-6.14.2-surface-1 amd64 6.14.2-surface-1 [10.4 MB]
Get:8 https://pkg.surfacelinux.com/debian release/main amd64 linux-headers-surface amd64 6.14.2-surface-1 [2,458 B]
Get:9 https://pkg.surfacelinux.com/debian release/main amd64 linux-image-6.14.2-surface-1 amd64 6.14.2-surface-1 [89.8 MB]
Get:10 https://pkg.surfacelinux.com/debian release/main amd64 linux-image-surface amd64 6.14.2-surface-1 [2,474 B]
Fetched 101 MB in 36s (2,827 kB/s)                                                                 
dpkg: libwacom9:amd64: dependency problems, but removing anyway as you requested:
 libinput10:amd64 depends on libwacom9 (>= 2.0.0).
 libinput-bin depends on libwacom9 (>= 2.0.0).

(Reading database ... 279427 files and directories currently installed.)
Removing libwacom9:amd64 (2.6.0-1) ...
Selecting previously unselected package libwacom9-surface.
(Reading database ... 279424 files and directories currently installed.)
Preparing to unpack .../libwacom9-surface_2.15.0-1_amd64.deb ...
Unpacking libwacom9-surface (2.15.0-1) ...
(Reading database ... 279426 files and directories currently installed.)
Removing libwacom-common (2.6.0-1) ...
Selecting previously unselected package libwacom-common-surface.
(Reading database ... 278973 files and directories currently installed.)
Preparing to unpack .../0-libwacom-common-surface_2.15.0-1_amd64.deb ...
Unpacking libwacom-common-surface (2.15.0-1) ...
Selecting previously unselected package iptsd.
Preparing to unpack .../1-iptsd_3.0.1-1_amd64.deb ...
Unpacking iptsd (3.0.1-1) ...
Selecting previously unselected package libwacom-bin-surface.
Preparing to unpack .../2-libwacom-bin-surface_2.15.0-1_amd64.deb ...
Unpacking libwacom-bin-surface (2.15.0-1) ...
Selecting previously unselected package libwacom2-surface.
Preparing to unpack .../3-libwacom2-surface_2.15.0-1_amd64.deb ...
Unpacking libwacom2-surface (2.15.0-1) ...
Selecting previously unselected package libwacom-surface.
Preparing to unpack .../4-libwacom-surface_2.15.0-1_amd64.deb ...
Unpacking libwacom-surface (2.15.0-1) ...
Selecting previously unselected package linux-headers-6.14.2-surface-1.
Preparing to unpack .../5-linux-headers-6.14.2-surface-1_6.14.2-surface-1_amd64.deb ...
Unpacking linux-headers-6.14.2-surface-1 (6.14.2-surface-1) ...
Selecting previously unselected package linux-headers-surface.
Preparing to unpack .../6-linux-headers-surface_6.14.2-surface-1_amd64.deb ...
Unpacking linux-headers-surface (6.14.2-surface-1) ...
Selecting previously unselected package linux-image-6.14.2-surface-1.
Preparing to unpack .../7-linux-image-6.14.2-surface-1_6.14.2-surface-1_amd64.deb ...
Unpacking linux-image-6.14.2-surface-1 (6.14.2-surface-1) ...
Selecting previously unselected package linux-image-surface.
Preparing to unpack .../8-linux-image-surface_6.14.2-surface-1_amd64.deb ...
Unpacking linux-image-surface (6.14.2-surface-1) ...
Setting up linux-headers-6.14.2-surface-1 (6.14.2-surface-1) ...
Setting up iptsd (3.0.1-1) ...
Setting up libwacom-common-surface (2.15.0-1) ...
Setting up libwacom9-surface (2.15.0-1) ...
Setting up linux-image-6.14.2-surface-1 (6.14.2-surface-1) ...
dkms: running auto installation service for kernel 6.14.2-surface-1.
/usr/sbin/dkms.mx autoinstall --kernelver 6.14.2-surface-1
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Warning: The /var/lib/dkms/8812au/5.13.6/6.14.2-surface-1/x86_64/dkms.conf for module 8812au include
s a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.14.2-surface-1 KVER=6.14.2-surface-1...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.14.2-surface-1 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.14.2-surface-1/x86_64/dkms.conf for module rtl8821cu i
ncludes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.14.2-surface-1 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
update-initramfs: Generating /boot/initrd.img-6.14.2-surface-1
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bmg_dmc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/xe2lpd_dmc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/xe3lpd_dmc.bin for module i915
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
dpkg: error processing package linux-image-6.14.2-surface-1 (--configure):
 installed linux-image-6.14.2-surface-1 package post-installation script subprocess returned error e
xit status 1
Setting up linux-headers-surface (6.14.2-surface-1) ...
dpkg: dependency problems prevent configuration of linux-image-surface:
 linux-image-surface depends on linux-image-6.14.2-surface-1 (= 6.14.2-surface-1); however:
  Package linux-image-6.14.2-surface-1 is not configured yet.

dpkg: error processing package linux-image-surface (--configure):
 dependency problems - leaving unconfigured
Setting up libwacom-bin-surface (2.15.0-1) ...
Setting up libwacom2-surface (2.15.0-1) ...
Setting up libwacom-surface (2.15.0-1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for udev (1:252.6-1mx23+1) ...
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Errors were encountered while processing:
 linux-image-6.14.2-surface-1
 linux-image-surface
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: Select all

demo@mx1:~
$ sudo apt install linux-surface-secureboot-mok
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  linux-surface-secureboot-mok
0 upgraded, 1 newly installed, 0 to remove and 152 not upgraded.
2 not fully installed or removed.
Need to get 5,474 B of archives.
After this operation, 18.4 kB of additional disk space will be used.
Get:1 https://pkg.surfacelinux.com/debian release/main amd64 linux-surface-secureboot-mok amd64 20250420-1 [5,474 B]
Fetched 5,474 B in 4s (1,313 B/s)                       
Selecting previously unselected package linux-surface-secureboot-mok.
(Reading database ... 295258 files and directories currently installed.)
Preparing to unpack .../linux-surface-secureboot-mok_20250420-1_amd64.deb ...
Unpacking linux-surface-secureboot-mok (20250420-1) ...
Setting up linux-surface-secureboot-mok (20250420-1) ...

The secure-boot certificate has been installed to

    /usr/share/linux-surface-secureboot/surface.cer

It will now be automatically enrolled for you and guarded with the password

    surface

SKIP: /usr/share/linux-surface-secureboot/surface.cer is already enrolled
To finish the enrollment process you need to reboot, where you will then be
asked to enroll the certificate. During the import, you will be prompted for
the password mentioned above. Please make sure that you are indeed adding
the right key and confirm by entering 'surface'.

Note that you can always manage your secure-boot keys, including the one
just enrolled, from inside Linux via the 'mokutil' tool.

Setting up linux-image-6.14.2-surface-1 (6.14.2-surface-1) ...
dkms: running auto installation service for kernel 6.14.2-surface-1.
/usr/sbin/dkms.mx autoinstall --kernelver 6.14.2-surface-1
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Warning: The /var/lib/dkms/8812au/5.13.6/6.14.2-surface-1/x86_64/dkms.conf for module 8812au include
s a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.14.2-surface-1 KVER=6.14.2-surface-1...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.14.2-surface-1 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
Sign command: /lib/modules/6.14.2-surface-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.14.2-surface-1/x86_64/dkms.conf for module rtl8821cu i
ncludes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.14.2-surface-1 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
update-initramfs: Generating /boot/initrd.img-6.14.2-surface-1
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bmg_dmc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/xe2lpd_dmc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/xe3lpd_dmc.bin for module i915
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
dpkg: error processing package linux-image-6.14.2-surface-1 (--configure):
 installed linux-image-6.14.2-surface-1 package post-installation script subprocess returned error e
xit status 1
dpkg: dependency problems prevent configuration of linux-image-surface:
 linux-image-surface depends on linux-image-6.14.2-surface-1 (= 6.14.2-surface-1); however:
  Package linux-image-6.14.2-surface-1 is not configured yet.

dpkg: error processing package linux-image-surface (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.14.2-surface-1
linux-image-surface
E: Sub-process /usr/bin/dpkg returned an error code (1)
demo@mx1:~
$ ^C
demo@mx1:~
$

[andrewedmondson]

Here is a screenshot of the Boot folder.

[j2mcgreg]

@andrewedmondson
When you post long tracts of output as in post #18, please encase them in code tags which makes them easier to read and navigate here in the forum. If you click on the pencil icon (edit), you can see how I did it for you this time.