Config wouldn’t BLOCK it from being detected, that’s the problem.

Have you checked for a BIOS update recently?

1. To launch apps: Super key, type in name of app, hit enter. That’s it.

2. Window Management: good writeup from that team: https://blogs.gnome.org/tbernard/2023/07/26/rethinking-window-management/ Quick cheat sheet for relevant keys there as well: https://thedroidguy.com/gnome-desktop-keyboard-shortcuts-for-efficient-workflow-and-navigation-1263904

Then I would try the above and make sure you don’t have a mixer confused somewhere.

Okay, so this is one of Asus’s consumer models that fits in the “Windowstop” category, meaning a lot of the hardware is going to be windows-only for various reasons.

It’s got an ALC272 which IS supported, but that doesn’t mean the microphone will be, especially if it’s on the USB bus for whatever reason.

Couple questions:

1. Do other microphones work, just not internal?
2. Does your volume control work as expected
3. Does the webcam work, and does the internal microphone work only when the webcam is engaged?
4. What do apps like Discord or Zoom detect as available for your inputs?

As a test, install pavucontrol and qasmixer. Open pavucontrol, and check ALL the input settings (there are many combos). If nothing there shows activity, launch qasmixer, select the ‘hw’ view on the right, then try selecting different mixers and see if one finally clicks.

If any of these are successful, your mic is detected, and your mixer settings are messed up so it’s not being enabled as an input sink.

If none of these work, you’re going to have to dig restart, then run sudo dmesg and grep through looking for information regarding audio devices, or similar errors to see if it can’t detect it.

From the product specs, it looks like it might have Harmon Kardon speakers, which may also tie into the microphone, and that’s going to be problematic if it’s a USB device for a number of reasons I won’t dive into. Overall, this model just seems to be problematic from digging around. Example: https://www.reddit.com/r/ASUS/comments/160d3wj/asus_creator_laptop_q530v_constant_problems/

What’s the exact model number of this Asus laptop?

Whoops, you are correct. Sorry about that!

deleted by creator

I’m guessing it’s similar to this: https://discuss.kde.org/t/plasma-doesnt-start-when-external-monitors-are-plugged-in/17350

You’re probably on a laptop and have multiple GPUs enabled at the same time. If not, you’re defining Nvidia drivers with something trying to be smart about when to enable the actual outputs or not.

You can either make sure to have the display turned on, or make it super clear to the drivers to always enable a display regardless of whether it detects a display.

It still starts the KDE session, but it’s probably on another term output. Hit ALT+F1 and see if it shows, but it depends on the distro, so it could F1, F6, F7…etc

Well in that log, it actually DOES use the right GPU. There are some other errors you have going on in there though, like you seem to have AV1 encoding selected somewhere in your settings, but this RTX 3070 doesn’t support AV1 encoding (on the fly) AFAIK.

Try launching the app this same, setting all your hardware encoding stuff back to defaults, then see if you can get it working. In these logs it IS picking up the second pipewire display, so that’s good, but launch this way again without AV1 enabled then upload the logs again and let’s see what’s happening.

Missed your logs link, but there’s some hints in there.

You have both an Intel GPU and Nvidia GPU in that laptop, and it’s selecting your Intel while trying to use Nvidia compatible settings. So you need to try and force everything to either work on Nvidia, or everything to work on Intel. It can’t do both without splitting the settings per GPU, which I don’t think is an option in OBS.

There’s a multitude of things going on here probably, but you need some debug logs to find. My guess is because your machine probably has multiple GPUs enabled, it’s picking the inactive one, or you have multiple portal methods install and it’s choosing the wrong.

Can you get some logs?

1. No, you can’t install the drivers manually if they aren’t supported. Nvidia does rolling driver releases removing aged out hardware, and the drivers do not support new versions with older hardware. Same with Windows.

2. Nouveau is the only option you have as far as hardware acceleration goes, but if these are laptops, you’d be better off just using the Intel graphics, because that’s what’s available, and they are very power efficient.

3. Power consumption is immediately bad once you engage the Nvidia hardware. Disable it in the BIOS. You won’t have better performance in any meaningful way, just horrible battery life, especially since these are devices so old the modern drivers won’t support the hardware.

The link literally had today’s date…

Lol. This guy responded only because Phoronix called him out on the allow releases yesterday. I do not think this person can make good on their previous promises of an accelerated development schedule, unfortunately.

What does that even mean?

Mkay

Yeah, download the ISO, use a media writer to put it on any kind of removable media, plug it in, reboot, and you’ll have a fully functional desktop in a few minutes are running in memory. This is the way it should be tested, and it gives you the option to test as many as you want to find the one that fits for you.

The only caveat is that it’s running completely in-memory as I said, so if you plan on testing out installing software to test, keep in mind your usual amount of RAM available will be slightly reduced.

If everything looks great, then you’ll have the ability to install directly, without harming your Windows partition. PLEASE BACK YOUR STUFF UP ANYWAY.

1. Yup.

2. I use Audacity because it’s super simple and has a familiar interface. Ardour is a DAW with way more features and mixing available, but a lot of people just use ONE as well for the “one and done” method. VSTs are going to be hit or miss depending on what they do and how they were written (many are windows-specific), but there are other things available for replacement if needed. Link.

3. NTFS is fine to read from on Linux, but I wouldn’t suggest read/write because NTFS will 100% corrupt itself over time. Stick to either read-only from NTFS and save elsewhere, or copy them to a new destination and work from there.

4. There’s a lot of info on these on Linux. Sounds like support for the Scarlett hit with kernel 6.8, so you’ll be fine there. The Behringer EV1 should be standalone hardware, meaning it does it’s work with the PC.

You can just run a LiveUSB of Fedora or whatever and try all this stuff out to be sure with no commitment. You could also get a second drive cheap and make this easier to test out fully if you really want and make the switch from dual booting a lot safer.

Either way, you have easy options to test all this out before even installing.

Fedora is great if you want a faster rolling release and you’re already familiar with it.

Debian is great if you want a slower release schedule but stable LTS.

Two different use-cases, but both great options.