ThelVadam

joined 1 year ago
[–] ThelVadam@programming.dev 3 points 2 months ago

Yeah, they do have a forum where you may find better direct download links, but you need to sign up and sign-ups are locked and only unlock once a month or so.

They also have a torrent-specific site but that one also requires an account and is pretty much always locked from what I’ve seen.

[–] ThelVadam@programming.dev 3 points 2 months ago* (last edited 2 months ago) (2 children)

I haven’t gone there in a while, but a good few years ago I found cgpersia ~~whoch~~ which had a whole bunch of tutorials and asset packs.

Don’t know if they’re still reliable though.

[–] ThelVadam@programming.dev 10 points 4 months ago

It does provide you with access to the IoT LTSC or LTSC editions which I believe would still allow you to skip the need to set up a Microsoft account.

I could be wrong on that detail, it’s been a while.

[–] ThelVadam@programming.dev 1 points 5 months ago

Currently on linux-zen, up to date (6.13.2.zen1-1)

[–] ThelVadam@programming.dev 1 points 5 months ago (2 children)

I’ve tried following this guide and the one on Arch’s Wiki to no avail, but I’m sure I could’ve messed something up somewhere somehow.

I think I’ve ruled out the issue being loopback specific, because even trying to use the Line In as intended (eg: joining a Discord call with the Line In set as the microphone), no audio comes through.

The motherboard is pretty recent, recent enough that it seems it doesn’t have Linux compatible drivers for Bluetooth, so I wouldn’t be surprised if my audio issues stemmed from the same problem. That, or the motherboard doing this weird jack-to-usb bridge…

[–] ThelVadam@programming.dev 1 points 5 months ago (4 children)

QasMixer is listing the same devices as alsamixer. Two Speaker lines: PCM, 0 and PCM, 1 Three Capture lines: Line, Mic, Analog In

All are enabled and unmuted.

Tinkering with it and so far nothing with QasMixer is yielding any results.

7
submitted 5 months ago* (last edited 5 months ago) by ThelVadam@programming.dev to c/linux4noobs@programming.dev
 

Hey all, I have a bit of a weird issue I’ve been struggling to fix for a little while now and am hoping a kind soul here might have the knowledge to help me figure it out.

A couple of years ago i switched from a single-system-dual-display setup to dual-system-single-display (as in one screen per system). I’ll spare the long winded explanation for it, but the gist of it is that the new system (a Mac Mini) is connected to the original, main system (custom built PC) via the motherboard’s audio jack so I can get the audio from both systems to play on the same speakers. That way the main PC focuses on the game or whatever else i’m doing, while the Mac Mini focuses on tools/streams/movies/etc. and both share the same set of speakers.

So it goes: Mac Mini (audio out) > (line in) Main PC (audio out) > Speakers

The way I had it work on Windows was by simply going to the audio settings, going to the Line In item’s properties, and checking the “listen to this device” box.

On Linux (Arch, KDE 6 if that helps at all), it was as simple as running either pactl load-module module-loopback or pw-loopback and it would work the same way as Windows out of the box.

Problem is, my motherboard (Asus TUF Gaming X570-Pro (Wi-Fi)) in the main PC died recently, so I had to get a new one (Asus ROG STRIX X870-F Gaming Wifi), and ever since, I’ve been unable to get audio loopback to work even after a clean, fresh install. Listening to device on Windows works fine still but I’m looking to completely get rid of Windows.

By default, running pw-loopback with no tinkering (which worked on the previous build) cut the audio from the main PC and replaced it by what sounds like slow steps in a very echo-y cave.

With a bit of tinkering trying to follow online guides and documentations which i’ve since undone (but the changes remained somehow) it changed to just duplicating the main PC audio with a tiny bit of delay (or at least the audio from one app on the main PC).

One thing I’ve noticed is that when I boot up my main PC, a couple of errors do show up:

Hub 10-0:1.0: config failed, hub doesn’t have any ports! (err -19)
hid-generic 0003:1532:0292.0008: No inputs registered, leaving
Bluetooth: hci0: Opcode 0x0c03 failed: -16

While seemingly unrelated to my loopback issue (hid error being my keyboard), looking those up made me realize that the motherboard IS fairly new and therefore driver support might be lacking (specifically the Bluetooth error, which I don’t care much about in all honesty), which might potentially be the root cause of loopback not working as expected.

Here are the results of some commands I see are asked about often when troubleshooting the same problem: ‘lspci | grep -i audio’

01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1)
73:00.1 Audio Device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller

Neither seems to be the motherboard (the first one being my 3060 Ti which I don’t pull audio from, the second looking like the CPU’s (AMD Ryzen 7 9700X) iGPU.

‘journalctl -p err’, or simply ‘journalctl’ don’t return anything relating to audio (essentially only returns the same keyboard and bluetooth errors mentioned above).

‘pactl info’ does return something interesting which might be the cause of the issue:

Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 128
Tile Size: 65472
User Name: thelvadam
Host Name: CoreDynamics
Server Name: PulseAudio (on PipeWire 1.2.7)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left, front-right
Default Sink: alsa_output.usb-Generic_USB_Audio-00.analog-stereo
Default Source: alsa_input.usb-Generic_USB_Audio-00.analog-stereo
Cookie: 6a69:7312

The weird thing is that the Sink and Source are labeled as usb-Generic_USB_Audio despite being the audio jack ports on the back of the motherboard. Maybe I’m just dumb. The motherboard BIOS settings do have an option for “USB Audio Controller” which is enabled by default under Advanced > Onboard Devices Configuration, but disabling it completely disables any and all audio devices.

I also tried using alsamixer to see if anything was disabled. I found a “Microhone” and “Line In” that were disabled, enabled them, but no change.

Does anyone have any idea why I can’t get audio loopback to work again? I’ll gladly provide more system info if I didn’t provide enough.

Thanks in advance!

[–] ThelVadam@programming.dev 22 points 1 year ago

Our Lord Gaben is a Benevolent God.

[–] ThelVadam@programming.dev 24 points 1 year ago* (last edited 1 year ago) (2 children)

Weren’t there a few (ex?) employees that came forward shortly after the initial accusations surfaced and confirmed it was true?

I could be misremembering things but I also vaguely recall the initial accusations being backed up with receipts. Wasn’t there an Imgur album with a whole bunch of screenshots of conversations proving the accusations weren’t made up? Or am I confusing two completely different situations together?

I didn’t follow the situation super closely, and moved on and forgot about it until I saw this post.

Edit: looks like i was indeed wrong and confusing two separate situations.

[–] ThelVadam@programming.dev 12 points 1 year ago* (last edited 1 year ago) (1 children)

Current owner of 4 and a half years (love the car, it’s not perfect but then again nothing is, but the company is ass and don’t even get me started on the CEO).

In my experience, Tesla will only force an update if it contains a “recall” hotfix. The car requires to be connected to a WiFi network to download the update (it won’t use the onboard data even if you pay for the premium plan).

I’ve seen people claim that the car will automatically download an update on its own if it sits ignored long enough (even without WiFi or premium data plan), but I’ve had an update sit for 3 months and my car never attempted to download/install it on its own so I’m not sure what “long enough” means.

If you really wanted to, I’m sure you could completely prevent it from phoning home by pulling a fuse or finding the data antenna and disconnecting it, but I never looked into it myself.

Edit: My car also puts a 2min countdown on the screen when you start an update, that should give anyone plenty of time to leave the vehicle.