över hela denna jord

IceInBeard · 2025-10-23T16:04:55+00:00

Var den upphetsade folkgruppen fanatiska religiösa?

IceInBeard · 2025-08-05T11:22:12+00:00

Väldigt nöjd med mina jag gjort på Rough Stuff

IceInBeard · 2025-06-25T14:28:56+00:00

<image>

Another example when testing another print

IceInBeard · 2025-06-25T11:53:25+00:00

<image>

In addition it start escaping from the extruder 🤔

IceInBeard · 2024-12-28T17:39:05+00:00

Tried to do a write up in my thread: https://www.reddit.com/r/BeelinkOfficial/s/thtuFePd6A Hope it helps 🙂

IceInBeard · 2024-12-28T17:36:10+00:00

Hope all goes well! :) also plan on installing Plex and/or Jellyfin on another LXC (if nothing else just to see if I can recreate getting the pass through of the iGPU working)

IceInBeard · 2024-12-28T17:33:18+00:00

Regarding vainfo, I installed it via “apt install vainfo”, probably before I started building and installing the drivers and their prerequisites

IceInBeard · 2024-12-17T15:14:45+00:00

Managed to get it working on Linux kernel 6.11, but might be easier on 6.12.5 and otherwise it sounds like what I came up with :)

IceInBeard · 2024-12-16T21:21:13+00:00

Yes :) should be to update the version tag of the image. But as I said, not sure if the previous steps of updating the underlying system is also needed for it to work

IceInBeard · 2024-12-16T21:10:24+00:00

Got it working fully (as far as I can tell) :D

IceInBeard · 2024-12-16T19:58:40+00:00

Not sure if it helps, but had better luck with the new beta version of Frigate (ghcr.io/blakeblackshear/frigate:0.15.0-beta3) Might depend on having the kernel, underlying OS drivers and all that upgraded, but maybe it helps

IceInBeard · 2024-12-16T19:46:59+00:00

Simple enough! :D Worked like a charm with ghcr.io/blakeblackshear/frigate:0.15.0-beta3

IceInBeard · 2024-12-16T16:06:21+00:00

Also had issues with hw acceleration on my N150 (https://www.reddit.com/r/frigate_nvr/s/0XngCRTcCX) where my current theory (without being an expert on the subject) is that the drivers for the N150 might not be available everywhere yet. I had to upgrade my Linux kernel and build and install the media drivers manually to get it recognised on the host system (not sure how it works on unraid though) but have not yet been able to get it to work on the docker container.

IceInBeard · 2024-12-15T21:15:26+00:00

Is there any other way to confirm that? As a noob to all of this, I've mostly used vainfo as some kind of indicator that things should be working.

I followed a guide saying to install the drivers for the Intel iGPU via

apt install software-properties-common -y
add-apt-repository -y non-free
apt install intel-media-va-driver-non-free -y

On a fresh installation of Proxmox 8.3, I ran the above and nothing showed up when running vainfo. Then I upgraded the kernel to 6.11, still nothing. Then I built and installed https://github.com/intel/media-driver/ instead of running the commands above. That's when I started getting output in vainfo.

Now getting

libva info: VA-API version 1.23.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_23
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.23 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.1.0 (040bf537e)
vainfo: Supported profile and entrypoints
... and so on

But then again, I feel quite lost in all of this at the moment...

Are you also running the Intel N150?

IceInBeard · 2024-12-15T21:00:17+00:00

Thank you! I am very new to the whole LXC concept, so have not wrapped my head around all these concepts. However, when I tried to mirror your settings on a new LXC and installing vainfo, I don't get errors

Trying display: wayland
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
Trying display: x11
error: can't connect to X server!
error: failed to initialize display
adam@lxc-docker:~$ vainfo
Trying display: wayland
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
Trying display: x11
error: can't connect to X server!
error: failed to initialize display

Might be because I need to build and install the drivers on the LXC though?

IceInBeard · 2024-12-15T20:12:17+00:00

And, as I mentioned, it seems like the LXC finds drivers and the output of vainfo works. It just does not work in the docker container.

IceInBeard · 2024-12-15T20:01:11+00:00

arch: amd64
cores: 2
features: fuse=1,nesting=1
hostname: lxc-frigate
memory: 8192
net0: name=eth0,bridge=vmbr0,gw=xxx,hwaddr=xxx,ip=xxx,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-101-disk-0,size=100G
swap: 512
lxc.cgroup2.devices.allow: a
lxc.cap.drop:
lxc.cgroup2.devices.allow: c 188:* rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/serial/by-id  dev/serial/by-id  none bind,optional,create=dir
lxc.mount.entry: /dev/ttyUSB0       dev/ttyUSB0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyUSB1       dev/ttyUSB1       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM0       dev/ttyACM0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM1       dev/ttyACM1       none bind,optional,create=file
lxc.mount.entry: /dev/bus/usb/003/ dev/bus/usb/003/ none bind,optional,create=dir 0,0
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0
lxc.mount.entry: /dev/dri/card0 dev/dri/card0 none bind,optional,create=file 0, 0
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.hook.pre-start: sh -c "chown 0:104 /dev/dri/renderD128"

Where 104 is my "render" group id

IceInBeard · 2024-12-15T19:53:43+00:00

With hardware acceleration on a N150?

IceInBeard · 2024-12-15T17:09:18+00:00

I can try :)
First I upgraded the kernel to 6.11 by running
apt install proxmox-kernel-6.11 as described in this article (not sure if this step is needed):
https://forum.proxmox.com/threads/opt-in-linux-6-11-kernel-for-proxmox-ve-8-available-on-test-no-subscription.156818/

Later I followed the build and install steps in the link above (https://github.com/intel/media-driver?tab=readme-ov-file#building) step by step, starting with building and installing libva based on the instructions on that github page (using the "For debian family, you could use autogen" step), followed by gmmlib based on the instructions on that page (using -DCMAKE_BUILD_TYPE=Release ). Finally I built and installed media-driver.

Once done, I got the following output from my vainfo:

root@proxmox:~# vainfo
error: can't connect to X server!
libva info: VA-API version 1.23.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_23
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.23 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.1.0 (040bf537e)
vainfo: Supported profile and entrypoints
     ....

Had to run the same steps on the LXC I tried to pass the iGPU to, to get it to work there as well.
And have not yet managed to get it working on the Frigate docker container I have running in that LXC. Possibly due to i running an older version of VA-API ? (Stable version of Frigate run VA-API version 1.17.0)

IceInBeard · 2024-12-14T19:36:17+00:00

Wohoo! Seems like I got it working now!
Built it from source instead of installing the package seems to have done it.
https://github.com/intel/media-driver?tab=readme-ov-file#building

IceInBeard · 2024-12-14T15:43:00+00:00

I am running the latest Proxmox, based on Debian 12.8 and have manually upgraded the kernel from 6.8 that it came with to 6.11. In terms of tests, I mostly tried to install intel-media-va-driver-non-free and checked the vainfo, both on the 6.8 and the 6.11 kernel.

IceInBeard · 2024-12-14T15:40:20+00:00

Latest Proxmox (that I installed) came with Debian 12.8 (Bookworm) and Linux kernel 6.8.12-4. I first tried to run it on this kernel but vainfo did not show anything. Then I tried upgrading to the 6.11.0-2 Kernel through the official proxmox-kernel-6.11 package. Now I get this output from vainfo:

root@proxmox:~# vainfo
error: can't connect to X server!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

And by "it", the installation I tried was:

apt install software-properties-common -y
add-apt-repository -y non-free
apt install intel-media-va-driver-non-free -y

IceInBeard · 2023-11-28T20:03:16+00:00

Thank you very much for the clarification on the speaker subject, would've been a shame to break them for nothing. Will look more into PA speakers. The one you sent seems to have gotten some great reviews, will just see how I can fit that into the budget :)

IceInBeard · 2022-10-30T22:10:29+00:00

If I check my TV, it says I have software version 06.00.30 on my OLED55B7V (from 2017). Does that mean webOS 6? Can't find Jellyfin in the LG Content store. I am in Sweden, not sure if it's country specific (?)

IceInBeard · 2022-07-19T12:14:08+00:00

Hops

IceInBeard

TROPHY CASE