ludicolo @ ludicolo @lemmy.ml

Posts

25

Comments

114

Joined

9 mo. ago

No it was this concept that never came to be. It's not possible/practical.

https://www.youtube.com/watch?v=oDAw7vW7H0c

Just had my brother in law show me a concept phone where you just put in block modules for the things you want and need in a phone. Want more battery? Take off your camera block module and plug in more battery block modules.

Obviously the concept as presented is near impossible to achieve. I told him that and said we can get close. I showed him framework laptops that are trying to achieve the very thing he wanted (to a certain extent). He said that if they could make that a phone he would switch from his apple ecosystem in a heart beat. The ability to swap for a bigger speaker on the fly for get togethers and parties was tantalizing (big music guy).

Just interesting because even non tech people want this when you sell it to them properly. They don't actually want a walled garden ecosystem that is "simple".

Voyager 👍

It warms my heart seeimg all these 👶 emojis! Welcome all new lemmyheads!

Wow this is one of the most pathetic comments I have ever seen.

"If you haven't figured out how to enjoy the game in two attempts, get fucked buddy! That's your fault for attempting to explore avenues if enjoyment! You need to do it my way, or face the consequences of payment!"

I don't know how we got to not just complacency in these predatory practices, but outright defending them too.

Pretty soon you'll be asking the company to directly shit in your mouth rather than present it on a plate.

My bad sorry should have thought about making an official matrix account and testing there. Based off of what I can tell my ntfy container is working because it works flawlessly with an official matrix account.

That leaves me with two ideas so far, there is something wrong with matrix dendrite container, or my vps coturn server (which I forgot to mention). It looks like traffic is coming through just fine on my co turn server though. I am curious if this is a firewall issue with my co turn server. That would make the most sense given that element call is also not working on element x.

It's weird though because calling works on seperate networks just fine so I had assumed that my co turn server just worked. Odd.

Edit: I think it is the turn server even though my calls are going through. I went to my maytrix url with "/_matrix/client/r0/voip/turnServer" to diagnose webrtc and it says "errcode: 'M_MISSING_TOKEN'" "error: 'missing access token' "

Is this within a config file for ntfy? When I access it through local host it tells me it needs to be accessed through https. Which I setup through cloudflare tunnels and the error went away.

There was no config file generated for my docker container for ntfy.

Edit: I have fixed this error but notifications still do not work.

I was able to get it working with this docker compose!! Thank you!

I can now sign inyo element x and schildi next! The only problem is none of my chats are showing up and when I create a new room it dissapears as soon as I back out into the chats tab.

Any idea on how to fix it? Do I need a seperate sub domain for the sliding sync proxy?

I am using cloudflare tunnels as of right now. I would be very appreciative if I could take a look at your settings!

In other news, shit spewing liar spews more shit and lies to get more of your money.

He thinks they're on the wrong side of history my ass. He doesn't care. He never cared. He will never care. The open source you and I know is completely different than the "open source" this chucklefuck is probably selling you on. "We need to figure out a different open source strategy" should be the biggest indicator here. Take everything he and his circlejerk says with the biggest fucking mountain of salt you can dream of and double it.

THANK YOU ALL!

It was a problem with my docker compose file! I didn't list the needed devices from the jellyfin documentation. I thought the Container was detecting the gpu but it wasn't. Docker exec

<container-name>

Edit: so now it doesnt kick me out saying the playback failed but its just a black screen with 4k media

Edit 2: my bad forgot to enable some transcoding settings in jellyfin lol

This is what thay compose looks like now:

    
 services:
  jellyfin:
    image: jellyfin/jellyfin
    user: 1000:1000
    network_mode: 'host'
    volumes:
      - /DATA/AppData/jellyfin/config:/config
      - /DATA/AppData/jellyfin/cache:/cache
      - /DATA/AppData/jellyfin/media:/media
      - /mnt/drive1/media:/mnt/drive1/media
      - /mnt/drive2/Jellyfin:/mnt/drive2/Jellyfin
      - /mnt/drive3:/mnt/drive3
      - /mnt/drive4/media:/mnt/drive4/media
      - /mnt/drive5/jellyfin:/mnt/drive5/jellyfin
      - /mnt/drive6/jellyfin:/mnt/drive6/jellyfin
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - driver: cdi
              device_ids:
               - nvidia.com/gpu=all
            - /dev/nvidia-caps:/dev/nvidia-caps
            - /dev/nvidia0:/dev/nvidia0
            - /dev/nvidiactl:/dev/nvidiactl
            - /dev/nvidia-modeset:/dev/nvidia-modeset
            - /dev/nvidia-uvm:/dev/nvidia-uvm
            - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools
              count: all
              capabilities: [gpu]


  

Edit: when I try and compose up it says "yaml: lin 30 mapping values are not allowed in this context" when I remove line 30 and 31 the output is "validating /DATA/AppData/jellyfin/docker-compose.yml: services.jellyfin.deploy.resources.reservations.devices.1 must be a mapping"

Output of nvidia-smi on the host:

Output of nvdia-smi on the container:

OCI runtime exec failed: unable to start container process: exec: "nvidia-smi": executable file not found im $PATH: unknown

EDIT:

I tried it again with the jellyfin docker compose command and this is what I get:

Failed to initialize NVML: Unknown Error

Edit 2: I fixed it I am now getting the same output for both!

I tried this and it says:

OCI runtime exec failed: unable to start container process: exec: "nvidia-smi": executable file not found im $PATH: unknown

I ran it as two commands instead of one before and still got that error message.

However, I tried again with a different jellyfin image and the command seems to have ran fine.

Here is a pic of my nvidia-smi output:

I followed this guide and seemed to get it working.

https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

However jellyfin transcoding sttill doesn't work. I have tried adding the "nvidia devices= all" environment variable, it still didn't work.

I tried using the docker conpose from here

https://jellyfin.org/docs/general/administration/hardware-acceleration/nvidia/#configure-with-linux-virtualization

But when I try and run this command: "docker exec -it jellyfin ldconfig sudo systemctl restart docker"

It says the container is restarting and to try again when the container has started.

Casaos is just a server ui for ubuntu to manage docker and other settings:

https://casaos.io/

Here is the output of nvidia-smi (sorry for the picture if my monitor. It's late and I blanking on my lemmy pass and cannot sign in on the pc itself to send a screen cap lol):

I used several different jellyfin images posted in casaos appstore along with the official nvidia documentation. It still does not want to work:

     
services:
  jellyfin:
    image: jellyfin/jellyfin
    user: 1000:1000
    network_mode: 'host'
    volumes:
      - /DATA/AppData/jellyfin/config:/config
      - /DATA/AppData/jellyfin/cache:/cache
      - /DATA/AppData/jellyfin/media:/media
      - /mnt/drive1/media:/mnt/drive1/media
      - /mnt/drive2/Jellyfin:/mnt/drive2/Jellyfin
      - /mnt/drive3:/mnt/drive3
      - /mnt/drive4/media:/mnt/drive4/media
      - /mnt/drive5/jellyfin:/mnt/drive5/jellyfin
      - /mnt/drive6/jellyfin:/mnt/drive6/jellyfin
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
            - /dev/nvidia-caps:/dev/nvidia-caps
            - /dev/nvidia0:/dev/nvidia0
            - /dev/nvidiactl:/dev/nvidiactl
            - /dev/nvidia-modeset:/dev/nvidia-modeset
            - /dev/nvidia-uvm:/dev/nvidia-uvm
            - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools
              count: all
              capabilities: [gpu] 
  

Yes it is a container on ubuntu, it seems to be the official container on the casa os store. It is labled "jellyfin (nvidia gpu)". The gpu seems to be working fine on the host. Ubuntu 20.04

Yeah i have tried tollowing that guide already.

Bro do some research before you come in making outrageous statements.

There are absolutely a wide variety of plug-n-play headsets that just work. Take the valve index for example. I have heard that headset works just fine out of the box. Same with any steamvr relient headset if I am not mistaken.

When you use a headset that depends on third party software that's when a little more setup is required. However we still have options that won't be a massive headache.

Like the cv1 for example, you can use something like openhmd and use your cv1 just fine on steamvr.

And that's also not to say that something like a quest 2/3 isn't hard either. Alvr is easy to install it's just about tweaking proper settings for your network. Which you may alrwady need to do if you've used virtual desktop.

Then there is wivrn. But you get my point.

Linux is more than gaming ready. Ever heard of protondb? Maybe give it a look. If an online game doesn't work that is of fault of the dev/publisher not making the anticheat compatible. Valve has consistently worked with anti-cheat devs like battle eye and easy anti-cheat to make it easy on the dev side to make their anti-cheat version support proton. Yet somehow we have large companies like rockstar not putting in that simple effort.

https://www.engadget.com/arma-3-dayz-proton-battleye-support-224625719.html?guccounter=1

https://www.theverge.com/2024/9/18/24248585/gta-v-steam-deck-battleye

Please stop spreading misinformation. It harms the absolute mountainload of work put in by people who have gotten linux to be where it is now. Get mad and point blame at your game devs/publishers for being so uncooperative.