You mean a cheese royal?
edinbruh
joined 2 years ago
The common audio chips have lots of input/output pins (for complex surround systems), most of the pins are disabled but you can see them on stuff like hdajackretask. I can see that in my case they are on two separate outputs.
On a sidenote, on some systems the manufacturer doesn't enable some unused pins on the OS side, but leaves them enabled on firmware, which can cause problems. So you can use this kind of software to disable them yourself.
From pavucontrol I can't select the interfaces independently (it's what I used to enable pro audio). And Carla uses jack, so no luck with jack either
Wait, so it's a girl, I assumed that was a boy
Because he's submissive (it's built to serve humans) and breedable (it's horny)
Ubuntu: it's not bad, I just don't like canonical
Manjaro: it starts as arch but more user friendly (by being preconfigured), until it inevitably breaks (being arch) and you end up with a regular arch that you don't know how is configured
Elementary os: it's too elementary os
All those con distros that are just a bunch of reskinned free stuff ask you money for that. Like zorin os
Classic french
Run dmesg and see if you find anything suspicious of the cause. If you find something like "blah blah... Ethernet... Blah blah... Key was rejected by service" or similar, it's due to secureboot.
If this is actually related to secureboot your drivers are most likely not in tree and installed via dkms, so they need to be signed or secureboot won't allow them.
You can setup a machine-owner-key to sign them yourself, and you can setup dkms to automatically sign them using that key. The instructions are on dkms' readme.
After setting up you need to run dkms autoinstall or manually reinstall the drivers to trigger the automatic signing.
Edit: I just noticed you said you deactivated secure boot... I have no clue. But for future reference, you can sign your modules to work with secure boot, it's not a bad idea.
It's not a dumb question. The answer is "it depends", it's mostly a choice. The general rule is that when yo start a project, you choose the language that you think will help you the most, whether that is because you already know the language, or because you have to work with stuff that already use that language, or because the language is better at doing that.
Regarding whether to stick to a language or learn a new one, in general your CS teachers will tell you (and they are correct) that you should not "learn to program in a language" but just "learn to program" and then apply that knowledge to whatever language you need. So, you should always learn languages that are different from the ones you already know in order to learn new paradigms, and then when you need a specific language, just learn the details about it. BUT, even if this way you will be able to use most languages, you will not be "good" at most, so you should also have some languages that you know really well and are experienced in. And for that you should choose the ones that are more useful to you (or maybe useful for your job) or the ones that you like.
FFS! I'm glad I'm not the only one