Still have a lot to learn
]]>:: running early hook [udev]
Starting systemd-udev version 255-3-1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [resume]
ERROR: resume: no device specified for hibernation
Waiting 10 seconds for device /dev/disk-by-uuid/<uuid....f29>
Waiting 10 seconds for device /dev/disk-by-uuid/<uuid....f29>
ERROR: device 'UUID=<uuid....f29>' not found. Skipping fsck.
:: mounting 'UUID=<uuid....f29>' on real root
mount: /new_root: can't find UUID=<uuid....f29>.
ERROR: Failed to mount 'UUID=<uuid....f29>' on real root
then drops me in recovery shell
Configuration:
- Is an Dell XPS 15 with two NVME.M2 disks, been my daily driver for 2 y, (last pacman -Syu was a 2-3 weeks ago). Disk layout is:
- Disk 1: "/" (OS), swap, and /boot
- Disk 2: /home
- /home, and /swap are LUKS encrypted, partitions in fstab and crypttab specified using UUID labels. Boot process never reach that far though.
Fuller story:
- I ran my computer (a laptop) this morning (off batteries), all was fine, then I "systemctl poweroff" as usual, and close lid, and go to work.
- When I get to work and start the computer the following happens:
- The DELL logo-start screen takes 30 seconds, rather than a few seconds like it usually does.
- But then GRUB finally starts, and I get my usual GRUB menu
- After GRUB starts the OS, then boot process fails, with error message in above code listing.
- Comment: it's not impossible the computer wasn't turned off completely when I closed the lid before heading off to work. I never use suspend or hibernate. Maybe this put it in some state that makes it try to recover when starting, (thus long wait in DELL-logo start screen), then it starts GRUB as usual?
- Interestingly: I've tried putting the OS disk in an older Dell laptop (that only supports one NVME disk), and then it boots just fine off that one (but fails further in to mount the /home partition, since that's on the disk in the other machine, so fully as expected). No complaint about not finding disk, and this is the disk with the OS, swap, and boot partition.
- This means, the OS-disk is not corrupt (that I can tell), the UUID of the swap or "/"-partition hasn't changed, or I would get the same issue when starting the second computer with my OS disk, right?
- I went to the office IT-helpdesk, they installed a new BIOS version (didn't help), however, I guess BIOS was never the issue, since I see the two disks in the BIOS, and BIOS hands off to GRUB just fine like it's supposed to (except the unusual long "DELL"-start screen time)
Since I can't access my /home partition, the situation is quite desperate. Any advice on how to get further on this would be very much appreciated.
I did find this arguing it's a bug in the NVME firmware, but I've been running it like this for years with no trouble. I need to get my OS starting again.
]]>I'm using pipewire, wireplumber and kde plasma.
My speakers are plugged on my monitor. My monitor is plugged via hdmi. The playback device is set as "Digital Stereo (HDMI) Output". Today, i think more playback devices option showed up: digital surround 5.1 and digital surround 7.1. Not sure if they were there or not before.
these are my last 2 updates i made:
[2024-03-18T10:15:30-0300] [PACMAN] Running 'pacman --sync -y -u --'
[2024-03-18T10:15:30-0300] [PACMAN] synchronizing package lists
[2024-03-18T10:15:33-0300] [PACMAN] starting full system upgrade
[2024-03-18T10:15:45-0300] [ALPM] transaction started
[2024-03-18T10:15:45-0300] [ALPM] upgraded aom (3.8.1-1 -> 3.8.2-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded bzip2 (1.0.8-5 -> 1.0.8-6)
[2024-03-18T10:15:45-0300] [ALPM] upgraded e2fsprogs (1.47.0-1 -> 1.47.0-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded libverto (0.3.2-4 -> 0.3.2-5)
[2024-03-18T10:15:45-0300] [ALPM] upgraded ca-certificates-mozilla (3.98-1 -> 3.99-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded libxml2 (2.12.5-1 -> 2.12.6-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded harfbuzz (8.3.0-2 -> 8.3.1-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded librsvg (2:2.57.2-1 -> 2:2.57.3-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded gtkmm3 (3.24.8-1 -> 3.24.9-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded harfbuzz-icu (8.3.0-2 -> 8.3.1-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded libopenmpt (0.7.4-1 -> 0.7.5-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded libpipeline (1.5.7-1 -> 1.5.7-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded nss (3.98-1 -> 3.99-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded pkgconf (2.1.0-2 -> 2.1.1-1)
[2024-03-18T10:15:45-0300] [ALPM] upgraded procps-ng (4.0.4-2 -> 4.0.4-3)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server-common (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server-devel (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server-xephyr (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server-xnest (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] upgraded xorg-server-xvfb (21.1.11-1 -> 21.1.11-2)
[2024-03-18T10:15:45-0300] [ALPM] transaction completed
[2024-03-18T10:15:45-0300] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2024-03-18T10:15:45-0300] [ALPM] running '30-systemd-udev-reload.hook'...
[2024-03-18T10:15:46-0300] [ALPM] running '30-systemd-update.hook'...
[2024-03-18T10:15:46-0300] [ALPM] running '40-update-ca-trust.hook'...
[2024-03-18T10:15:47-0300] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2024-03-18T10:15:47-0300] [ALPM] running 'texinfo-install.hook'...
[2024-03-18T19:58:50-0300] [PACMAN] Running 'pacman -S discord'
[2024-03-19T08:37:19-0300] [PACMAN] Running 'pacman --sync -y -u --'
[2024-03-19T08:37:19-0300] [PACMAN] synchronizing package lists
[2024-03-19T08:37:21-0300] [PACMAN] starting full system upgrade
[2024-03-19T08:37:38-0300] [ALPM] running 'ghc-unregister.hook'...
[2024-03-19T08:37:38-0300] [ALPM] transaction started
[2024-03-19T08:37:38-0300] [ALPM] upgraded lz4 (1:1.9.4-2 -> 1:1.9.4-3)
[2024-03-19T08:37:38-0300] [ALPM] upgraded discord (0.0.45-1 -> 0.0.46-1)
[2024-03-19T08:37:39-0300] [ALPM] upgraded electron28 (28.2.7-1 -> 28.2.7-2)
[2024-03-19T08:37:39-0300] [ALPM] upgraded electron29 (29.1.4-1 -> 29.1.4-2)
[2024-03-19T08:37:40-0300] [ALPM] upgraded haskell-skylighting-format-blaze-html (0.1.1.1-47 -> 0.1.1.2-1)
[2024-03-19T08:37:40-0300] [ALPM] upgraded haskell-skylighting (0.14-7 -> 0.14-8)
[2024-03-19T08:37:40-0300] [ALPM] upgraded haskell-pandoc (3.1.8-9 -> 3.1.8-10)
[2024-03-19T08:37:40-0300] [ALPM] upgraded haskell-pandoc-lua-engine (0.2.1-53 -> 0.2.1-54)
[2024-03-19T08:37:40-0300] [ALPM] upgraded haskell-pandoc-server (0.1.0.5-11 -> 0.1.0.5-12)
[2024-03-19T08:37:40-0300] [ALPM] upgraded libbsd (0.12.1-1 -> 0.12.2-1)
[2024-03-19T08:37:40-0300] [ALPM] upgraded libinih (57-1 -> 58-1)
[2024-03-19T08:37:40-0300] [ALPM] upgraded libmnl (1.0.5-1 -> 1.0.5-2)
[2024-03-19T08:37:40-0300] [ALPM] upgraded libnfnetlink (1.0.2-1 -> 1.0.2-2)
[2024-03-19T08:37:40-0300] [ALPM] upgraded libnetfilter_conntrack (1.0.9-1 -> 1.0.9-2)
[2024-03-19T08:37:40-0300] [ALPM] upgraded pandoc-cli (0.1.1.1-78 -> 0.1.1.1-79)
[2024-03-19T08:37:40-0300] [ALPM] upgraded potrace (1.16-2 -> 1.16-3)
[2024-03-19T08:37:40-0300] [ALPM] upgraded vapoursynth (R65-1 -> R66-1)
[2024-03-19T08:37:40-0300] [ALPM] transaction completed
[2024-03-19T08:37:40-0300] [ALPM] running '30-systemd-update.hook'...
[2024-03-19T08:37:40-0300] [ALPM] running '30-update-mime-database.hook'...
[2024-03-19T08:37:40-0300] [ALPM] running 'ghc-register.hook'...
[2024-03-19T08:37:41-0300] [ALPM] running 'gtk-update-icon-cache.hook'...
[2024-03-19T08:37:41-0300] [ALPM] running 'update-desktop-database.hook'...
If you need more info, ask away!
edit: i already forced the rate at 48000
]]>Yesterday I got myself a cheapo microphone. It works alright on Windows, nothing to say about its quality, because it was very good for it's price. Nevertheless, when I tried it on my Arch machine, it sounds like ASS! I sound like a robot lollll. It's a USB microphone.
It's like my voice break all around and it has cracking and other audio distortion effects.
The microphone itself has 2 controls: volume and echo. Dunno if that has anything to do with this problem, but I wanted to let you know.
alsa-info.sh: https://termbin.com/uq8z
lsusb -v: https://termbin.com/qc5h (the device is 1b3f:2008).
I'm running pipewire as we speak. If any more info/output is needed, just let me know!
]]>You could run a test on an empty file just to make sure cryptsetup itself is working in general.
truncate -s 16M lukstest.img echo -n 123 | cryptsetup luksFormat lukstest.img for i in $(seq 100) do echo -n 123 | cryptsetup open --test-passphrase lukstest.img lukstest && echo OK $? || echo FAIL $? done
Should print OK 100 times.
If that works, it's probably another issue.
Maybe your keyboard is detected late so you end up typing half a passphrase without noticing? Just to make sure the keyboard is alive, press enter on the first attempt before typing it for the 2nd attempt, does that work?
Are you using UUIDs for your devices? Otherwise it could be a mixup (if you got another LUKS container with a different pass, e.g. sda1 vs sdb1).
You could patch cryptsetup to show the passphrase it's trying to use, just for debugging purposes.
Otherwise not really many ideas...
With passwords containing characters such as "@#" it gave an error.
Why is there a problem with symbols?Are you using US keyboard layout or something else?
If you're using non-ascii symbols like § ° it could also be a charset issue.
user@arch ~> setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: us
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
user@arch ~> locale -a
C
C.utf8
en_US.utf8
POSIX
ru_RU.utf8
user@arch ~> locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
So the HDCP handshake fails (it's designed for that, so no big surprise )
Do you have another HDMI cable? Are there any adapters involved?
And most importantly: does the simpledrm device still show up in your journal?
This is the journal :https://0x0.st/XrS8.txt
And i don't have any other HDMI cable
So that my bluetooth will enable automatically when boot
Recently I update my system `sudo pacman -Syu` 1~2 times
Until today I open my computer and found that the bluetooth need me enable manually, every time I boot.
(base) [firestar@Archlinux ~]$ systemctl list-unit-files
UNIT FILE STATE PRESET
proc-sys-fs-binfmt_misc.automount static -
-.mount generated -
boot.mount generated -
dev-hugepages.mount static -
dev-mqueue.mount static -
home-firestar-C.mount generated -
home-firestar-D.mount generated -
proc-sys-fs-binfmt_misc.mount disabled disabled
sys-fs-fuse-connections.mount static -
sys-kernel-config.mount static -
sys-kernel-debug.mount static -
sys-kernel-tracing.mount static -
tmp.mount static -
var-lib-machines.mount static -
gpm.path static -
systemd-ask-password-console.path static -
systemd-ask-password-plymouth.path static -
systemd-ask-password-wall.path static -
session-2.scope transient -
accounts-daemon.service disabled disabled
archlinux-keyring-wkd-sync.service static -
audit-rules.service disabled disabled
auditd.service disabled disabled
autovt@.service alias -
avahi-daemon.service disabled disabled
avahi-dnsconfd.service disabled disabled
blk-availability.service disabled disabled
bluetooth.service enabled disabled
bolt.service static -
btrfs-scrub@.service static -
canberra-system-bootup.service disabled disabled
canberra-system-shutdown-reboot.service disabled disabled
canberra-system-shutdown.service disabled disabled
console-getty.service disabled disabled
The Problem in short:
When PC is normal turned off/shutdown and not disconnected from 230V AC, then Monitor backlight get of/off in a loop every some seconds.
Same behaviour, when I disconnect all DP and HDMI input cables from monitor, and let just the power supply connected.
The cause:
I have next to the table a small audio amplifier, which is driven by an 19V laptop power supply unit. This PSU is always connected to 230V (the amplifier has a on/off switch itself).
Today I found a side effect: When the amplifer PSU is disconnected from 230V, then the Monitor stays off how it should be.
When I just connect the amplifier PSU to 230V and also let the amplifier on/off switch in off-position, then the Samsung Monitor begins to switch on/off the backlight in a loop. The power cable of the amplifier is close to the display port cable.
So it is no problem from graphic card. It's just some kind malfunction with radiation from the amplifier power supply unit.
Topic is solved for me, root cause is not the PC, graphic card or archlinux
colormgr get-devices
but I have no results, while in X11 it shows me "xrandr-Dell Inc.-DELL UP2716D-KRXTR91N517L".
Xrandr is typical for X11 only, so it is not strange that it does not work in Wayland; however on the wiki it is expressly stated to use it under Wayland... Is this a known shortcoming of Wayland? Does it only happen to me?