Technically it’s supported, but there are no GUI elements merged yet so it all has to be done pretty manually
Has anyone had any issue with getting pulse/alsa to see the microphone in Arch? I have not ever been able to get it to detect the internal one. It worked fine with a USB sound card. I have not seen it brought up anywhere that I looked so far, so I wonder if I just missed something somewhere perhaps?
2 Likes
First of all, sorry for the late reply.
I’m using SDDM, so if you are not, YMMV. I installed fprint and libfprint, and followed the instructions in the Arch wiki (Fprint and SDDM) to modify /etc/pam.d/system-local-login and /etc/pam.d/kde to set pam_fprintd.so as sufficient and I also made sure pam_unix.so try_first_pass likeauth nullok was sufficient (first) in /etc/pam.d/system-local-login, to give the ability to use my password if the fingerprint doesn’t work (damn shower-fingers!) and then the last thing I did was enroll my fingerprints. $ fprintd-enroll will do that, or you can specify which fingers you want individually (check the fprint docs for more info).
This works flawlessly for me (except for the aforementioned shower-fingers) and I’m happy to offer more info for those interested.
3 Likes
Having the same issue as @Arsal_Asif but I am on the newest kernel: 5.14.14-arch1-1. I have WiFi working, but bluetooth does not work. I am running GNOME on Grub.
I tried downgrading to 5.12.15 but that did not fix my bluetooth issue. I can confirm bluetooth is running via systemctl but GNOME bluetooth settings do not work.
Any help is appreciated.
1 Like
After an update, now bluetooth works after cold boots. Warm boots still cause bluetooth to not work properly in gnome.
I was having major power problems, the laptop was actually hot. I was getting 2 hours of battery life.
I’ve installed tlp and the laptop is now cool to the touch.
Do this:
pacman -S tlp
systemctl start tlp
systemctl enable tlp
Now your frame.work isn’t a toaster.
5 Likes
Running Manjaro KDE Plasma, kernel 5.14.10. Bluetooth is still crazy spotty for me. Works once every 10 startups, maybe, and when it’s not working no controllers are detected when I scan with bluetoothctl. Idk what to do, and still pretty new to Linux. Any pointers?
2 Likes
Is there any way to control or monitor charging wattage? For instance to charge slower overnight or while the laptop is sleeping?
1 Like
This should be added to the Known Issues
1 Like
I’m not completely certain about this, but the Bluetooth on my laptop does not work when I boot straight from a restart or reboot, and rarely after waking from suspend. So a stop-gap solution could be to avoid doing restarts when you need Bluetooth, and when you do need to restart, instead shutdown and power on.
Don’t quote me on this, its just something I’ve seen when I’m using Arch.
2 Likes
This seems to be a pretty universal experience. Further discussion about this issue can be found in this thread.
2 Likes
After installing Windows 10 on a secondary drive, my fingerprint reader does not work anymore. I enrolled my fingerprint in Windows, booted back into Arch, and my finger no longer works. I attempted to remove and then re-enroll my finger but now when I try, fprintd service crashes after the first scan. I am running GDM, and have tried both via CL and in the gnome settings gui.
I uninstalled and reinstalled fprintd and libfprint, no luck after that. Any help would be appreciated!
1 Like
I often have to rmmod and modprobe btusb on two of my Lenovo laptops running Arch and Intel 8260 wifi/bt cards. Do you get BT back if you run those commands?
1 Like
After executing:
modprobe -r btusb
modprobe btusb
Nothing happened. Bluetooth remained off. Ironically, bluetooth.service is still running.
2 Likes
According to the “bug” report, it is expected that you will be prompted to enter your password if you log in using biometrics. This is because of the GNOME keyring which cannot be unlocked using the fingerprint sensor. According to the developer:
That is the expected behaviour. The keyring contains sensitive data, it is encrypted and a fingerprint cannot be used as an encryption key.
Thus the only method to decrypt the keyring is by entering your password. This definitely an inconvenience when initially logging into your machine, but is necessary to maintain security.
A paradigm shift I’ve taken is to use your password to login once you boot up (this also unlocking the keyring), then using biometrics when signing into your computer from sleep.
Do check out this article briefly explaining the GNOME keyring: Explained! The Concept of Keyring in Ubuntu Linux
1 Like
To anyone having issues with the fingerprint reader after having installed Windows on a secondary drive, here’s a link to a guide that helped me get it working again!
1 Like
I got Arch Linux installed. One issue, there seems to be an issue with IWD 1.19. It crashed every time I tried to connect to a wifi network. The thing is, the live environment comes with 1.18, so everything would look OK in the live environment but when I booted from the installed environment Wifi would not work. I downgraded the installed environment to 1.18 and it worked. NetworkManager seems to work fine.
Is anyone else having issues with the upgrade to kernel 5.15.2? After updating this morning, running into constant random GPU hangs. Getting errors like [drm] GPU HANG: ecode 12:1:85dffffb, in sddm-greeter, but sometimes it’s in Xorg or in QSGRenderThread or in plasmashell. Sometimes it will freeze before login, sometimes plasma starts normally and it freezes randomly (usually when opening a program, like firefox), but most times it freezes during xorg or plasma initialization. I’m running plasma/x11, but since it sometimes freezes during SDDM I’m not sure if that matters.
Downgrading the kernel to 5.14.16 seems to have worked, although I am seeing weird visual artifacts in Firefox that I’m not sure were there before.
Update: Visual artifacts in 5.14.16 were fixed by installing xf86-video-intel and configuring as suggested on the arch wiki. Still seeing GPU hangs on 5.15.2 with the new config, though.
Another update: It looks like maybe Plasma disables some compositing features if it detects a GPU crash, which is probably why I started noticing visual artifacts after rolling back.
3 Likes
@mcdoogs I am seeing the same thing. 5.15.2 makes plasma utilities unsuable, causing GPU HANGs. I downgraded all the way to 5.14.9 and am not seeing any visual artifacts nor hangs.
Looks like the i915 driver got messed up on last release.
3 Likes
I’m guessing it’s the same as this issue. Although they’re encountering it in just SDDM, might be some difference between hardware or distro letting us get to plasma occasionally
2 Likes