Skip to content

Instantly share code, notes, and snippets.

Booting `Ubuntu Server Bionic 18.04 (Hikey 970 CE)'
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.78-147538-g244928755bbe (andy@andy-virtual-machine) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Thu May 31 10:58:02 CST 2018
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] earlycon: pl11 at MMIO 0x00000000fff32000 (options '115200')
@lucmann
lucmann / gist:224133c335bb067fbc6d1e22e307400f
Created November 18, 2025 11:23
hikey970 serial error
11月 18 06:52:17 vostro kernel: usb 1-1: new full-speed USB device number 76 using xhci_hcd
11月 18 06:52:17 vostro kernel: usb 1-1: New USB device found, idVendor=04e2, idProduct=1410, bcdDevice= 0.03
11月 18 06:52:17 vostro kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
11月 18 06:52:17 vostro kernel: xr_serial 1-1:1.0: xr_serial converter detected
11月 18 06:52:17 vostro kernel: usb 1-1: xr_serial converter now attached to ttyUSB0
11月 18 06:53:10 vostro kernel: usb 1-1: USB disconnect, device number 76
11月 18 06:53:10 vostro kernel: xr_serial ttyUSB0: Failed to set reg 0x1d: -19
11月 18 06:53:10 vostro kernel: xr_serial ttyUSB0: Failed to set reg 0x03: -19
11月 18 06:53:10 vostro kernel: xr_serial ttyUSB0: xr_serial converter now disconnected from ttyUSB0
11月 18 06:53:10 vostro kernel: xr_serial 1-1:1.0: device disconnected
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
clang
directx-headers
expat
gcc-libs
glibc
libdrm
libelf
libglvnd
libpng
libva

Before:

➜  ~ systemctl --user cat thelounge.service
# /usr/lib/systemd/user/thelounge.service
[Unit]
Description=The Lounge IRC client

[Service]
Type=simple
Environment=THELOUNGE_HOME=~/.thelounge
@lucmann
lucmann / gist:8c9ec2a7dc3a3777185a7a701c570878
Created August 15, 2025 15:03
/lib/systemd/system/clash-proxy.service: systemctl enable clash-proxy
[Unit]
Description=Clash Proxy Autostart
After=network.target network-online.target
[Service]
Type=simple
WorkingDirectory=/home/luc/a/clash-for-linux
User=root
ExecStart=/home/luc/a/clash-for-linux/bin/clash-linux-amd64 -d conf
Restart=on-failure
@lucmann
lucmann / gist:76a471826f027e489424bf14cc4ce4dc
Created August 8, 2025 11:31
daemon/PreferredDisplayServer=legacy-xorg gdm failed to start xorg
This file has been truncated, but you can view the full file.
8月 08 06:30:54 sniper gdm[520]: Gdm: GdmManager: trying to open reauthentication channel for user luc
8月 08 06:30:54 sniper gdm[520]: Gdm: Finding a graphical session for user 1000
8月 08 06:30:54 sniper gdm[520]: Gdm: Considering session '5'
8月 08 06:30:54 sniper gdm[520]: Gdm: Considering session '4'
8月 08 06:30:54 sniper gdm[520]: Gdm: Session '4' is not a graphical session (type: 'unspecified')
8月 08 06:30:54 sniper gdm[520]: Gdm: Considering session '3'
8月 08 06:30:54 sniper gdm[520]: Gdm: Session '3' is not a graphical session (type: 'tty')
8月 08 06:30:54 sniper gdm[520]: Gdm: GdmManager: looking for user session on display
8月 08 06:30:54 sniper gdm[520]: Gdm: GdmSession: starting reauthentication for session 5 for client with pid 1000
@lucmann
lucmann / gist:4ba425b42a1d9060a0756225345e58b9
Created August 7, 2025 14:16
blank console after update gdm to 49.beta
8月 07 06:10:38 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: received VT change event
8月 07 06:10:38 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: VT changed from 1 to 2
8月 07 06:10:38 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring
8月 07 06:10:40 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: received VT change event
8月 07 06:10:40 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: VT changed from 2 to 3
8月 07 06:10:40 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring
8月 07 06:10:42 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: received VT change event
8月 07 06:10:42 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: VT changed from 3 to 4
8月 07 06:10:42 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring
8月 07 06:10:44 sniper gdm[505]: Gdm: GdmLocalDisplayFactory: received VT change event
@lucmann
lucmann / vsc-windows.csv
Last active November 5, 2024 07:55
Visual Studio Code
F2 Rename Symbol
Ctrl-F4 Close Editing File
Ctrl-R Recently Opened
Ctrl-Shift-F Global Search
Ctrl-Shift-J Toggle Search Details box (files to include/exclude)
@lucmann
lucmann / gpu-driver.md
Created October 17, 2024 03:01
notes about gpu drivers
  • Describing on which device the buffer has been allocated on is not enough: on some setups the buffer may have been allocated on one device but may still be directly accessible without any move on another device. For instance, on a split render/display system, a buffer allocated on the display device can be directly rendered to from the render device.