|
Anyone got decent guides on how to get hardware video decode working on Chrome on Wayland on NVidia? The CUDA stuff is installed and all, and I'm using the nvidia-vaapi-driver, setting the VaapiDecoder flag on Chrome, which in turn shows "Hardware accelerated" in chrome://gpu in Video Decode, but the Video Acceleration Information section at the bottom of said page is blank.
|
#
?
May 23, 2024 19:17
|
|
|
|
| # ? May 24, 2024 13:42 |
|
|
mawarannahr posted:It's supposed to be in Rust but with the initial release, who knows! I would be more concerned with bugs and incomplete implementation, personally. Oh I totally won't be touching it until sometime next year probably, maybe play with it in vm before that.
|
|
#
?
May 23, 2024 19:26
|
|
|
WattsvilleBlues posted:It is, but if it performs the same as Ubuntu, I think Kubuntu would be a better fit for my friend since it's more like a Windows experience. I run KDE on a 7 year old laptop that wasn't fast even when it was new. It's no trouble at all for me.
|
|
#
?
May 23, 2024 19:30
|
|
|
Combat Pretzel posted:Anyone got decent guides on how to get hardware video decode working on Chrome on Wayland on NVidia? The CUDA stuff is installed and all, and I'm using the nvidia-vaapi-driver, setting the VaapiDecoder flag on Chrome, which in turn shows "Hardware accelerated" in chrome://gpu in Video Decode, but the Video Acceleration Information section at the bottom of said page is blank. Huh, I had this working (with Vivaldi, but same difference) on my Manjaro install, but looking at it now I have the same thing as you. Are you using a flatpak? edit: and I'm on AMD so it's not a nvidia problem. making it run in X11 mode isn't working either. I think this may be a flatpak problem. Klyith fucked around with this message at 20:09 on May 23, 2024 |
|
#
?
May 23, 2024 20:07
|
|
|
I spent two hours trying to figure out HW acceleration in Firefox with Nvidia until I realized I should really just be using the Intel driver on my Optimus laptop and then it Just Worked Switching from flatpak to native was part of the process though
|
|
#
?
May 23, 2024 20:12
|
|
|
Klyith posted:Huh, I had this working (with Vivaldi, but same difference) on my Manjaro install, but looking at it now I have the same thing as you. Are you using a flatpak?
|
|
#
?
May 23, 2024 20:44
|
|
|
Use nvidia-smi to see if the Chrome process shows up when you're playing a video
|
|
#
?
May 23, 2024 20:45
|
|
|
Any ideas why sound will come out of my headphones connected to my front jack, but not the speakers plugged into my motherboard? Same behavior in both Fedora and OpenSUSE, using GNOME in both. Trying to give Linux another shot but my god I cannot believe it's just all the same problems as 20 years ago.
|
|
#
?
May 23, 2024 21:58
|
|
|
wicka posted:Any ideas why sound will come out of my headphones connected to my front jack, but not the speakers plugged into my motherboard? Same behavior in both Fedora and OpenSUSE, using GNOME in both. Trying to give Linux another shot but my god I cannot believe it's just all the same problems as 20 years ago. https://bugzilla.kernel.org/show_bug.cgi?id=207423#c94 Actually no on a re-read it shouldn't be that at all Tiny Timbs fucked around with this message at 22:08 on May 23, 2024 |
|
#
?
May 23, 2024 22:05
|
|
|
wicka posted:Any ideas why sound will come out of my headphones connected to my front jack, but not the speakers plugged into my motherboard? Same behavior in both Fedora and OpenSUSE, using GNOME in both. Trying to give Linux another shot but my god I cannot believe it's just all the same problems as 20 years ago. I have the same damned problem with Windows, it's always picking some bizarre new combination of my 3 mics and 4 outputs. In Linux, each output device gets an identifier. You need to tell your UI which one to use. How do you do that in the UI? Who frickin' knows! I bet it's equally as logical in the Windows kernel, and the UI obscures it into oblivion with a bunch of ease-of-use things that work really nicely for 75% of users.
|
|
#
?
May 23, 2024 22:06
|
|
|
No, it sees the device fine and sets it as the default. It just doesn't output audio to it.
|
|
#
?
May 23, 2024 22:08
|
|
|
OK. Whew. I think I hate flatpak. Played around with a bunch of flags & command arguments, no dice. Played around with various flatseal permissions, no dice. Played around with some flatseal permissions and arguments at the same time, all GPU acceleration in Vivaldi stopped working entirely. Reset flatseal. It didn't go back to normal. Tried rebooting. Still broken! Tried to reset to defaults with flatpak command line, it says I have no overrides. Play around with other things, find out that it works when I run the command to launch vivaldi from a console window, it works. It's only broken when I run it from the GUI shortcut. The commands I am using in the console and what's in the .desktop file is exactly the same: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=vivaldi com.vivaldi.Vivaldi --ignore-gpu-blocklist ... At this point I say "gently caress this". Find that the instructions to install vivaldi in suse are actually very easy. Do that. It works fine (once I move my profile back out of the flatpack zone into .config). Add --enable-features=VaapiVideoDecodeLinuxGL,VaapiVideoEncoder to the command arguments. 
|
|
#
?
May 23, 2024 22:10
|
|
|
wicka posted:Any ideas why sound will come out of my headphones connected to my front jack, but not the speakers plugged into my motherboard? Same behavior in both Fedora and OpenSUSE, using GNOME in both. Trying to give Linux another shot but my god I cannot believe it's just all the same problems as 20 years ago. Have you tried just adding this extension and checking if you can select it through that? https://extensions.gnome.org/extension/906/sound-output-device-chooser/
|
|
#
?
May 23, 2024 22:12
|
|
|
keep punching joe posted:Have you tried just adding this extension and checking if you can select it through that? Pretty sure this was installed by default. Again, I am not having issues seeing or selecting the device. It just doesn't output audio.
|
|
#
?
May 23, 2024 22:13
|
|
|
wicka posted:No, it sees the device fine and sets it as the default. It just doesn't output audio to it. Maybe your UI isn't honoring the default, then. I mean, we're all just black-box debugging here. I hate computers. Although I do recall a motherboard where if I plugged something into the front 3.5mm jack, it closed a switch that prevented output from going out the back. It wasn't a software thing: it was hardware.
|
|
#
?
May 23, 2024 22:37
|
|
|
cruft posted:I mean, we're all just black-box debugging here. I hate computers. I was mostly hoping this would be a "oh yeah, you have the well known X problem" situation, rather than the unfortunate realization that Linux is still amateur hour.
|
|
#
?
May 23, 2024 22:45
|
|
|
wicka posted:Linux is still amateur hour. Yeah, if you want a Linux kernel but don't want amateur-developed software, you should look into ChromeOS or Android. They're really nice!
|
|
#
?
May 23, 2024 22:50
|
|
|
Figured it out. "Auto mute" was enabled in alsamixer.
|
|
#
?
May 23, 2024 23:33
|
|
|
the amateur ebkac smdh
|
|
#
?
May 23, 2024 23:35
|
|
|
alsa? What is this, 2019?
|
|
#
?
May 23, 2024 23:37
|
|
|
spiritual bypass posted:alsa? What is this, 2019? I'm not aware of any other way of getting sound to speakers in linux at the moment. OSS has been deprecated (must have been, haven't checked) for ... quite a while now.
|
|
#
?
May 23, 2024 23:41
|
|
|
Tiny Timbs posted:the amateur ebkac smdh Are you under the impression that I turned this on or some poo poo?
|
|
#
?
May 23, 2024 23:50
|
|
|
I've definitely had to go into alsamixer and toggle some random poo poo that wasn't exposed in the desktop environment's audio controls, but that was years ago and I have no idea what the state of the audio stack is on my various Linux machines now (and that's how I likes it).
|
|
#
?
May 24, 2024 00:14
|
|
|
Volguus posted:I'm not aware of any other way of getting sound to speakers in linux at the moment. OSS has been deprecated (must have been, haven't checked) for ... quite a while now. I actually don't know how it works now. Is alsa still the final receptacle of the audio stream before actual output? Everything I've had to actually touch in the last few years was Pulse, Pipewire, or Wireplumber
|
|
#
?
May 24, 2024 00:41
|
|
|
spiritual bypass posted:I actually don't know how it works now. Is alsa still the final receptacle of the audio stream before actual output? Everything I've had to actually touch in the last few years was Pulse, Pipewire, or Wireplumber Alsa has the drivers. In the kernel. If that is not there (or doesn't work or is muted or 1 billion other things) ... well, I suppose with pulse/pipewire you can still stream over the network.
|
|
#
?
May 24, 2024 00:48
|
|
|
Bluetooth audio doesn't involve ALSA at all.
|
|
#
?
May 24, 2024 01:24
|
|
|
pseudorandom name posted:Bluetooth audio doesn't involve ALSA at all. Completely forgot about bluetooth. Yeah, that's a different beast.
|
|
#
?
May 24, 2024 03:14
|
|
|
pseudorandom name posted:Bluetooth audio doesn't involve ALSA at all. I had this hot take tirade about Bluetooth, but given its complexity, avoiding kernel space is probably a smart move. I'm pretty sure ALSA will let you register audio sources and sinks from userspace, so the Bluetooth audio service daemon wotzit can probably provide whatever's needed to whatever needs it. I know you can do this with MIDI, at least.
|
|
#
?
May 24, 2024 03:55
|
|
|
Volguus posted:Alsa has the drivers. In the kernel. If that is not there (or doesn't work or is muted or 1 billion other things) ... well, I suppose with pulse/pipewire you can still stream over the network.
|
|
#
?
May 24, 2024 04:00
|
|
|
Vulture Culture posted:Ah, memories. I once ran 20,000 systems with PulseAudio loopback sinks Ok, can you expand on that?
|
|
#
?
May 24, 2024 04:19
|
|
|
|
| # ? May 24, 2024 13:42 |
|
|
Apologies if this is the wrong place entirely to ask this, but I'm struggling and I'm hoping someone with knowledge of create react might be able to help. I was trying to setup this project https://github.com/judahpaul16/gpt-home and didn't think I'd have any issues as it uses a setup script to basically sort everything for you. So I thought even my self with some but not a lot of Linux knowledge would be fine! I even made sure to use Ubuntu Server and a Raspberry Pi 4 - just like the developer - to reduce the chance of issues. The setup script didn't work 100% like the Github page said it would, and would fail, until I installed the dependencies manually then it all worked beautifully and the services etc were setup. The project is useless without the web interface, and as far as I could tell, this isn't set up by default, and the instructions at https://github.com/judahpaul16/gpt-home/tree/main/src/frontend need to be followed to get it up and running and hosted. So - I followed these instructions exactly and ran sudo npm install (I had to actually install npm first), and that ran ok, with a few warnings about depreciated things but no critical errors. Then I ran sudo npm start, and it compiled and started hosting on port 3000 with no errors, it specifically said all is ok. I was then able to connect and see the web page, the Integrations page seemed to work fine, but the event logs page would show an error "JSON.parse: unexpected character at line 1 column 1 of the JSON data" and the settings page would just say "Loading" forever. Additionally if I try and build the project with sudo npm run build, that works ok, but when I serve it with sudo serve -s build, it starts serving fine, but when looking at the web page at localhost:3000 I either get just a directory listing of the files in the frontend/build folder, or I get a screen prompting me to choose a password, but if I try and set one, I get the error "Error hashing password: undefined". I would expect to at least see the same website as when running sudo npm test, even if it's broken. I have absolutely no idea what I could have done wrong or what the problem is. I would imagine if everyone was having this problem, it would be apparent in the Issues section on Github, so I don't think it's a problem with the project in general. If anyone could offer any advice or point me in the right direction to try and get this sorted, I'd be really grateful. Thanks! Debuffed fucked around with this message at 13:33 on May 24, 2024 |
|
#
?
May 24, 2024 13:28
|
|