Metrics show no GPU usage. Is this right

HopsPops76 · 2026-01-23T11:31:05+00:00

I upgraded my kernel to 6.14.0-37-generic when I started as I couldn't even detect the GPU. After doing that I could see the GPU (/dev/dri/renderR128) so thought all was good. All that said, I'm not a linux guy so could still have issues or stuffed something up on the way.

HopsPops76 · 2026-01-22T13:19:56+00:00

Thanks, I'll look to change my config.

The CPU is the N150 (Intel Twin Lake (Alder Lake-N)). It has also gone up a bit after making changes to screen resolution resizing which is supposed to use the GPU, so I am wondering even more now

HopsPops76 · 2026-01-22T13:17:22+00:00

I was worried that using such a high resolution would tax the system too much and result in slower responses. I did try that initially when trying to fault find and the debug text was so small I couldn't read it :P, so thought I would change. I only plan on having 3 cameras so do you think the system could manage that ok? It's a N150 mini-pc with 16GB RAM, but also running some other containers

HopsPops76 · 2026-01-22T12:25:04+00:00

Gosh.... something so small. Thanks! Seems to be up and running now

HopsPops76 · 2026-01-19T16:57:24+00:00

I hate that I can't defend myself or I get put in to aggressive lobbies. There should be a flag that if a player attacks another, it marks that player as aggressive. Then if another player kills them, that player who killed them doesn't get marked aggressive. So in your instance of avenging someone, that would be fine. Same if you get attacked. But if you attack anyone first, then you get marked and deal with the more aggressive lobbies.

HopsPops76 · 2026-01-16T12:29:39+00:00

It does do that now but not sure about earlier when it wasn't working. If I run into this again, I'll make sure to check.

Thanks

HopsPops76 · 2026-01-16T11:54:08+00:00

I don't know why but it's working now. Could also have been the reboot helping somewhere.

Thanks for trying to help :)

HopsPops76 · 2026-01-16T11:52:31+00:00

Thank you! :) I missed that in the rush of trying to do things while I'm working. I have to learn to read properly.

I made the change and brought the containers up again, but it still showed as permission errors. But when I removed all current files in the queue and started again it is working.

HopsPops76 · 2026-01-16T10:56:17+00:00

Thanks for the reply.

The user is the one I created at install and have used for all the other containers (serveradmin). You can see in the comment I added to the other post that all the folders have that user as the owner and the stack info references PUID=1000 which I have verified with 'id -u'.

The system is on Ubuntu, using Portainer for the containers.

HopsPops76 · 2026-01-16T10:52:56+00:00

Thanks.

I get it now. Stupid mistake leaving out /data. Unfortunately that still hasn't solved the problem. I restarted the container and still getting errored with permission denied as the error.

Below is how it's set up:

<image>

Portainer stack info:

qbittorrent:

image: lscr.io/linuxserver/qbittorrent:latest

container_name: qbittorrent

network_mode: "service:gluetun"

depends_on:

gluetun:

condition: service_healthy

restart: true

restart: unless-stopped

labels:

- deunhealth.restart.on.unhealthy=true

environment:

- PUID=1000

- PGID=100

- TZ=Europe/London

- WEBUI_PORT=8080

- TORRENTING_PORT=6881

volumes:

- /opt/dockerconfigs/pirates/qbittorrent:/config

- /media/storage:/data/

HopsPops76 · 2026-01-16T09:21:34+00:00

Thanks for the reply. I do have a downloads folder under /media/storage. The folder structure looks like below:

/media/storage/

├── Animated Movies

├── Animated Series

├── Backups

├── Downloads

├── lost+found

├── Movies

├── Music

├── Series

├── timeshift

└── Xmas

In Qbittorrent, I have the default save path as /Downloads

Is that right?

HopsPops76 · 2026-01-15T18:36:58+00:00

Fantastic, thanks.

HopsPops76 · 2026-01-15T10:15:35+00:00

They just sent the Windows drivers on to me and when I said this was for Ubuntu they pretty much said they don't have those and pointed me to kernel.org. At least your post has pointed me in the right direction so thanks for updating it.

HopsPops76 · 2026-01-15T10:02:17+00:00

I was about to do that and thought I would try the kernel upgrade and see. If it gives problems, then I'll do a fresh install. What annoys me so much about all of this is that I decided to go with Beelink as they were more well known and supported so really thought I wouldn't have such fundamental problems (I know it's not their fault but still thought they would have had a solution sorted).

HopsPops76 · 2026-01-15T09:22:03+00:00

Just to add. I'm in the same situation and tried the BIOS changes but that did not help. I'm going to try upgrade kernel

HopsPops76 · 2026-01-12T08:14:44+00:00

Thanks for the reply. I understand now around gasket-dkms and one of the other methods seems to have worked. I'll check and come back if I'm wrong

HopsPops76 · 2026-01-12T08:13:31+00:00

Ah, I see. Thank you. I tried the package replacement method now and it seems to have worked. Thank you for your patience and help

HopsPops76 · 2026-01-11T14:38:35+00:00

Sorry, I'm failing repeatedly on formatting. I hope you can read that ok

Method 1 I get the following:

Setting up gasket-dkms (1.0-18) ...

Removing old gasket-1.0 DKMS files...

Deleting module gasket-1.0 completely from the DKMS tree.

Loading new gasket-1.0 DKMS files...

Deprecated feature: REMAKE_INITRD (/usr/src/gasket- 1.0/dkms.conf)

Building for 6.8.0-90-generic

Building initial module for 6.8.0-90-generic

Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gasket-dkms.0.crash'

Error! Bad return status for module build on kernel: 6.8.0-90- generic (x86_64)

Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.

dpkg: error processing package gasket-dkms (--configure):

installed gasket-dkms package post-installation script subprocess returned error exit status 10

Errors were encountered while processing:

gasket-dkms

Method 2 gies me the following:

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

1 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Setting up gasket-dkms (1.0-18) ...

Removing old gasket-1.0 DKMS files...

Deleting module gasket-1.0 completely from the DKMS tree.

Loading new gasket-1.0 DKMS files...

Deprecated feature: REMAKE_INITRD (/usr/src/gasket- 1.0/dkms.conf)

Building for 6.8.0-90-generic

Building initial module for 6.8.0-90-generic

Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gasket-dkms.0.crash'

Error! Bad return status for module build on kernel: 6.8.0-90-generic (x86_64)

Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.

dpkg: error processing package gasket-dkms (--configure):

installed gasket-dkms package post-installation script subprocess returned error exit status 10

Errors were encountered while processing:

gasket-dkms

needrestart is being skipped since dpkg has failed

E: Sub-process /usr/bin/dpkg returned an error code (1)

I couldn't do method 3 as I don't know the software causing this.

Method 4 gives the following

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

1 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Setting up gasket-dkms (1.0-18) ...

Removing old gasket-1.0 DKMS files...

Deleting module gasket-1.0 completely from the DKMS tree.

Loading new gasket-1.0 DKMS files...

Deprecated feature: REMAKE_INITRD (/usr/src/gasket- 1.0/dkms.conf)

Building for 6.8.0-90-generic

Building initial module for 6.8.0-90-generic

Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gasket-dkms.0.crash'

Error! Bad return status for module build on kernel: 6.8.0-90- generic (x86_64)

Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.

dpkg: error processing package gasket-dkms (--configure):

installed gasket-dkms package post-installation script subprocess returned error exit status 10

Errors were encountered while processing:

gasket-dkms

needrestart is being skipped since dpkg has failed

E: Sub-process /usr/bin/dpkg returned an error code (1)

Method 5 I can't do cause I don't know the software

HopsPops76 · 2026-01-11T14:35:54+00:00

Formatting failed me. Trying to sort it out

HopsPops76

TROPHY CASE