Linux - Reddit
947 subscribers
4.52K photos
207 videos
1 file
41.8K links
Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
We are regressing as a species.
https://redd.it/1vm0ck3
@r_linux
Kernel 7.1.8 fixes AMD artifacting issue.

I just wanted to give a headsup about the issue with amd graphics cards flickering and having weird colorful artifacts. No, your GPU is not dying. It was kernel versions 7.1.6 and 7.1.7.

This issue is fixed in 7.1.8. It released in Arch a few hours ago, and I think in Fedora as well.

https://redd.it/1vlve5l
@r_linux
Whats going on with Snapdragon X Elite Linux support?!
https://redd.it/1vm99q3
@r_linux
Want to try Stacking WM, but gnome and kde are too fancy

Hey all I've been using Linux for about a year and a half now and have really been loving it (I'm on void btw).

I have always used Tiling WMs since the beginning, I used Hyprland for a bit, ended up hating it for both the Dev's shadiness but also the absolute incredulous amount of churn. So I switched to Sway, from the very beginning I've only ever used Wayland.

I'm not at a place where I'm content but I am curious about swapping to a stacking WM. I was going to go KDE but, and I'm probably in the minority, I don't really like Kwin, and I actually find KDE to look kinda ugly.

I've been drawn to XFCE which I have installed but not tested yet. It's aesthetic is much more my vibe and classic with all the theming available.

Does Wayland have any compositors in this ball park of stable and consistent but not the usual?

https://redd.it/1vn2oa7
@r_linux
Lumia 1520 Linux update: the audio hardware is finally talking!

Hey everyone,

It's been a minute since I posted an update on the Lumia 1520 mainline Linux project ....and this one ended up being a pretty big step forward.

Last time I posted, the phone was already at a pretty solid baseline... Linux was cold booting reliably, display/touch/buttons were working, USB networking + SSH were stable, suspend/resume was working, battery telemetry and backlight control were in place, etc.

Since then I've been digging into one of the bigger missing pieces: audio....a fucking nightmare lol

At first, I thought it might hit the same wall as WiFi. The Lumia's audio stack uses Qualcomm's ADSP co-processor, and I wasn't sure whether the Windows Phone TrustZone would even allow it to boot.

Turns out it does....

The ADSP now boots successfully, APR communication with it works, and I was able to bring up MSM8974's ADSP managed SLIMbus transport. That led to the actual codec on the phone. And at this point I've confirmed from the hardware itself that the Lumia 1520 uses a Qualcomm WCD9320 / Taiko codec.

Not just inferred from old Qualcomm sources either...Linux is physically enumerating it over SLIMbus and reading its own identification registers back as major ID "0x0102".

The codec actually exposes two separate SLIMbus functions:

PGD - control/register access

IFD - the audio port/channel interface

Both now enumerate independently and get their own logical addresses. From there I built out proper regmap access, power/reset handling, fresh bring-up, non-destructive late adoption, and the beginnings of the codec interrupt support.

The interesting part was the digital core. A large section of the codec's register map kept returning zero, which initially sent me down a rabbit hole looking for the external 9.6 MHz MCLK. I dumped the Lumia's ACPI tables, RPM clocks, all 36 PM8941 GPIOs and all 8 MPPs trying to find where Nokia routed it. That investigation was...."useful", but the clock wasn't actually the blocker.

The real issue was that Linux had never executed Qualcomm's original "wcd9xxx_bring_up()" sequence. Every audio milestone before this had been read only, so the missing initialization stayed hidden.

Once I implemented the downstream bring-up sequence and switched the codec onto its internal RC oscillator, the result was immediate:

87/87 previously inaccessible sentinel registers became readable.

71 matched Qualcomm's documented defaults exactly, and the remaining 16 fall into three consistent register families that appear to be revision-specific differences.

So the chain now looks like:

Linux → ADSP → QRTR/QMI → BAM → SLIMbus NGD → WCD9320 PGD/IFD → regmap → codec core release → internal RCO → digital core accessible

I also mapped the codec's interrupt parent to Lumia TLMM GPIO 72 and validated it electrically idle across direct sampling and suspend/resume testing. I haven't claimed full IRQ support yet because I haven't deliberately generated and cleared a real codec interrupt source.

And just to be clear: there is still no audible sound output yet. I'm not calling audio "working" until PCM data actually reaches an output.

What this does mean is that most of the unknown hardware/transport side of Lumia audio is now gone. What's left is the actual codec/ASoC implementation work: permanent automatic core initialization, nested IRQ handling, DAIs and SLIMbus port configuration, the MSM8974/Lumia machine driver, and then finally a fixed playback route to get the first test tone out of the phone.

I'm deliberately finishing the Lumia's hardware enablement before I start layering my RegenX OS work onto it. I'd rather have a known-good hardware platform first than end up debugging kernel/driver problems and OS layer problems at the same time.

Wi-Fi/BT is still the major documented blocker, charging still needs more work, and modem/camera remain further out.... but audio has gone from "this may require an entirely missing upstream stack" to actual driver development on hardware that is responding exactly where it
Had enough with Windows
https://redd.it/1vo6nyv
@r_linux
just made it to Flathub
https://redd.it/1vodgrr
@r_linux