Arch Linux

wannadanna

Member

Registered: 2024-11-14

Posts: 2

Audio and sddm issues after Arch install

Hi everyone!

Yesterday i finished my first manual Arch install after using EOS for a year.

Everything runs smooth, but i have 2/3 issues that i cannot resolve by googling or arch wiki (maybe im just blind, sorry then).

1. Audio doesnt play from the AUX slot of my PCIe soundcard, except when i put the "Analog Output" to "Stereo Headphones" manually after every boot in QasMixer.
I had to do the same in EOS, but only once and then i could remove the qastools package and it would work every single boot. Here i have to put it every boot in QasMixer.

2.Login with sddm is kinda scuffed. I use 2 screens, and i can enter my password on both screens, but only on my physical left screen it actually logs me in after entering the password. Also sddm randomly aligns my screens every boot, but it doesnt matter which one it considers to be the "left" screen, because its always my physical left screen. I have experienced this every time i booted into sddm, because i am used to look at my right screen first always (also it puts my mouse and keyboard prompt on the right login screen (physical) ALWAYS)

a third issue, which isnt really that much of an issue is, that Arch doesnt start my network connection (LAN) on startup by itself and thus i enabled dhcpcd to start my network adapter on boot. this causes the boot to take 10 extra seconds because in the boot screen it stops when starting the adapater and this will then take several seconds to complete. was seemless on EOS and maybe its an easy fix i dont see.

journalctl -b here:
https://pastebin.com/xJX87v48

I hope i provided sufficient information about my issues so you could help me!
Thanks in advance.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,289

Re: Audio and sddm issues after Arch install

In the future please only make one thread per topic.

For the audio issue, you'll want to do the change and after run

sudo alsactl store #alsa-utils

which should lead to it getting restored in the future.  Should that not help post the outputs of

sudo fuser -v /dev/snd/*
aplay -lL
amixer -c0 #Replace the 0 with the index you get from aplay -l

in [ code ] [ /code ] tags without the spaces.

The SDDM issues are somewhat known with current versions of the breeze theme/constellations with Qt 6.8, for generally ensuring correct screen setup you might want to run some preparatory xrandr commands or so: https://wiki.archlinux.org/title/SDDM#L … ed_display

The third issue, Arch generally doesn't start anything itself and you're expected to set up what you want. EOS will have defaulted to NetworkManager most likely, which you could also set up (and disable dhcpcd if you do so) or otherwise check the dhcpcd wiki for how to enable the service without invoking the startup delay: https://wiki.archlinux.org/title/Dhcpcd … ow_startup

Also your journal shows that your locale setup is incomplete, make sure you configure some language, at the very least you will always want en_US regardless + whatever other language you prefer: https://wiki.archlinux.org/title/Locale … ng_locales (generally read the rest of that page regarding setting a language as well) -- and since you're running plasma, be weary of the following caveat: https://wiki.archlinux.org/title/Locale … g_language

And as noted, you might not have "wikied well enough"

Last edited by V1del (2024-11-14 13:48:52)

wannadanna

Member

Registered: 2024-11-14

Posts: 2

Re: Audio and sddm issues after Arch install

First of all, thank you, i will only post 1 thread per issue in the future.

sudo alsactl store #alsa-utils

This just returns "sudo: alsactl: command not found".
Edit: nevermind, just installed the package alsa-utils.

Ill see to seting up networkmanager instead. Was already thinking about it. Will this nuke something if i keep dhcpcd? Or i shall i just remove it?

Last edited by wannadanna (2024-11-14 13:48:52)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,289

Re: Audio and sddm issues after Arch install

you can just remove it (or keep it) but at the very least you must ensure the service you enabled is disabled again otherwise networkmanager and dhcpcd will fight for who gets to control the ethernet device