#alpinelinux

23 posts · Last used 18h

I have a #Thinkcentre with #OpenBSD. It serves as a host for all my repos. My two laptops, an old #x240 with #alpinelinux and the #t480s with #netbsd, I use for programming. I pull a repo to the laptop of the day, and push when I'm done. Because of the recent issues with #SSH on #alpinelinux I changed all three machines to work with #sshkeys instead of passwords as of yesterday. Apart from the security aspect, it has the added benefit that I don't have to key in my crazy long password whenever I #push or just use #ssh to do cross machine activity. Why didn't I do this long ago?
8
0
0
0
Urgent: Immediately set 'PasswordAuthentication no' in /etc/ssh/sshd_config and restart the sshd service. Make sure you have ssh key authentication or other ways to access your machines. Also make sure to update openssh to the latest version. The openssh fix will be backported all the way back to Alpine 3.16 https://openssh.org/releasenotes.html#10.6p2 #security #AlpineLinux
21
0
40
0
It took a long time, but our #riscv64 builder managed to finish building the community packages. At the worst, it had a backlog of more than 800 packages, but it managed to churn along the last couple of weeks. We had it running on a HiFive P550 for a while. Even though it had faster cores, we had to move it back to the MilkV Pionieer. We're trying some other riscv64 systems as well, to see if they serve as better builders. #AlpineLinux
27
5
13
0
Back at testing whether my RDNA3 card (7800 XT) will behave itself on this system. I'm running kernel 7.1.4 (Alpine linux-stable) so supposedly there are a bunch of fixes since 6.19 -> 7.0 -> 7.1.x. We'll see. Last hour has been solid. No screen artifacts or horizontal aberrations on terminal or web browser windows. When it did occasionally work adequately before it would hard crash to a green screen on one of the monitors after about 24 hours or so. Didn't matter what kernel parameters I put on the kernel cmd line. It's kind of weird as I've been running this card in a different system (same OS, different gen CPU/mobo) successfully but it is a single head system so maybe that's the difference. Some combinations of cobbled together junk just don't work in the PC space. Fingers crossed. #Linux #AMD #amdgpu #RDNA3 #AlpineLinux
1
5
0
0
Replying to

Ok, I think I've got this display card under control - or so it seems. It hasn't crashed since Wednesday.

I guess this is a combo AMD RDNA3 Navi23 and KDE Plasma (+ Wayland?) bug...

I backed out all my Linux kernel command line switches for AMD GPUs and it crashed to green screen in less than a half hour. So, re-adding them stopped that from happening.

... amdgpu.dcdebugmask=0x410 amdgpu.tmz=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 ...

And then the cursor thing is fixed <?!> by adding

KWIN_FORCE_SW_CURSOR=1

Currently this is what is set:

cat /proc/$(pidof kwin_wayland)/environ | tr '\0' '\n' | grep KWIN :

KWIN_DRM_NO_AMS=1 KWIN_DRM_NO_DIRECT_SCANOUT=1 KWIN_FORCE_SW_CURSOR=1

From a user experience point of view I don't see any difference with that software cursor setting.

There's another wrinkle to this that might be a factor but I can't really test around it currently. This is a multi-head machine and one screen is connected via HDMI and one is DP.

Perhaps this wouldn't be a problem if both screens were connected via the same type of connector.

Both screens are set to the same refresh frequency. But, in the display control app one reads back at 60.00 Hz while the other is 60.000 Hz. Minor thing right? But in trying to make this work I've seen references to AMD GPU weirdness in multi-head configurations where the refresh rates were different between screens. Red herring perhaps.

Anyway, don't know if there are (or will be) any people trying to make a RX 5800 XT GPU behave under Linux but this seems to be what worked for me and my dual head setup. I'll update if anything changes.

#Linux #AMD #AMDGPU #KDE #KDEPlasma #Plasma #AlpineLinux #kwin #Wayland

2
2
0
0
What's the general feeling about Alpine Linux as a server OS for docker containers? I currently run Fedora coreOS with podman containers but I've had issues mostly from day one , most resolved now bit it still fights me at least once a week. Well its time for a drastic change. I've used Alpine as a desktop before, but only briefly, so I am familiar with some of it differences bit not all. Is it a good idea? #AlpineLinux#docker #server
3
2
2
0
I love that feeling you get when you finish tuning your Linux desktop box with everything optimized and "just so" and nothing left to mess with or install. Colours, wallpaper, apps, hardware acceleration, menus, widgets/plasmoids, filesystems backed up, etc. Oh, that's just me? Never mind. Carry on. #Linux #AlpineLinux
19
1
5
0
:tux: Alpine Linux 3.24 Improves Installer Experience, Adds COSMIC Desktop Option 「 Alpine Linux 3.24 was christened today as for advancing this lightweight Linux distribution built around musl libc and Busybox. Alpine Linux 3.24 ships with installer improvements with setup-alpine now able to support the Limine boot loader and also having IPv6 handling support. There is also better handling for headless setups 」 https://www.phoronix.com/news/Alpine-Linux-3.24 #alpinelinux #linux #cosmicde #opensource
1
0
1
0
Releases are still pending, but our repositories all received upgraded kernels to address copy.fail (CVE-2026-31431). So make sure you upgrade to the latest available kernels. edge: >= linux-lts-6.18.22 3.23: >= linux-lts-6.18.22 3.22: >= linux-lts-6.12.85 3.21: >= linux-lts-6.12.85 3.20: >= linux-lts-6.6.137 3.l9: >= linux-lts-6.6.137 3,18: >= linux-lts-6.1.170 3.17: >= linux-lts-5.15.204 #AlpineLinux #security
58
9
58
0
Replying to
in practice i think it does not really concern #AlpineLinux the intent of this law is clearly to go after operating systems with app stores
8
7
2
0