u/Pioneer_11

I bought a serval ws from system76 last year and at the time they advertised that while it came with the closed source Insyde BIOS coreboot would be available "once development for the new intel platform is complete" (see wayback machine page [1]) we're now almost a year on and a new intel platform has dropped since then (300 series) yet there still isn't coreboot support for these laptops and the system76 page has dropped the promise of coreboot (see [2] the modern webpage for the same laptop).

I would also note that COSMIC has had a known but for over 6 months which keeps the GPU on when unplugged resulting in horrible (<2hrs) battery life [3] and it's still not even not even made it to the TODO list. Which strikes me as very poor for something I and a lot of other people payed a lot off money for assuming good PopOS support.

[1]

https://web.archive.org/web/20250531194908/https://system76.com/laptops/serw14/configure#tab-tech-specs

[2]

https://system76.com/laptops/serval-ws

[3]

https://github.com/orgs/pop-os/projects/27/views/1?filterQuery=gpu

Hi all,

I'm trying to run an nvidia gpu in a dev container for bevy. I've the nvidia container toolkit and the test container at the end of the instructions here ( https://podman-desktop.io/docs/podman/gpu ) is giving the nvidia-smi printout as expected.

I've currently got this dockerfile and devcontainer.json up and running (FYI I am using the zed editor) though for some reason I don't understand rust fails to download the `stable` toolchain so after downloading I have to run `rustup default stable` to add it.

Dockerfile:

FROM fedora:latest

RUN dnf -y update && dnf -y install gcc \

sudo \

gcc-c++ \

libX11-devel \

systemd-devel \

wayland-devel \

libxkbcommon-devel \

alsa-lib-devel \

mesa-dri-drivers \

mesa-vulkan-drivers \

mesa-libGL \

mesa-libGLU \

mesa-libGLU-devel \

mesa-libEGL \

mesa-libEGL-devel \

vulkan-loader \

vulkan-loader-devel \

vulkan-tools \

python3-pip \

git

ARG user=appuser

ARG group=appuser

ARG uid=1000

ARG gid=1000

RUN groupadd -g ${gid} ${group} -f

RUN useradd -u ${uid} -g ${group} -m ${user}

RUN usermod -aG wheel ${user}

# Add appuser to video and render groups to access GPU devices (/dev/dri)

RUN usermod -aG video,render ${user}

RUN echo "${user} ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/${user} && \

chmod 0440 /etc/sudoers.d/${user}

# Create the /run/user directory structure as root before switching user

# This directory must exist in the container so devcontainer.json can bind-mount

# the host's Wayland socket into it. Set permissions to match host user.

RUN mkdir -p /run/user/${uid} && \

chown ${uid}:${gid} /run/user/${uid} && \

chmod 700 /run/user/${uid}

USER ${uid}:${gid}

# install default rust toolchain

RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | RUSTUP_INIT_SKIP_PATH_CHECK=1 sh -s -- -y --default-toolchain stable

# Ensure cargo is in PATH

ENV PATH="/home/${user}/.cargo/bin:${PATH}"

CMD [ "bash" ]

Devcontainer.json

{

"name": "GPU devcontainer",

"build": {

"dockerfile": "dockerfile",

"context": "."

},

"args": {

"uid": "${id -u}",

"gid": "${id -g}"

},

"containerEnv": {

"XDG_RUNTIME_DIR": "/run/user/${id -u}",

"WAYLAND_DISPLAY": "${localEnv:WAYLAND_DISPLAY}",

"DISPLAY": ":0",

},

"mounts": [

{

"source": "${localEnv:XDG_RUNTIME_DIR}",

"target": "/run/user/${id -u}",

"type": "bind"

}

],

"runArgs": [

"--device",

"/dev/dri",

"--device",

"/dev/snd",

"--ipc",

"host",

"--env",

"XDG_RUNTIME_DIR=/run/user/${id -u}",

"--env",

"WAYLAND_DISPLAY=${localEnv:WAYLAND_DISPLAY}",

"--env",

"DISPLAY=:0",

// "--gpus",

// "all"

],

"customizations": {

"zed": {

"extensions": ["git-firefly", "cargo-tom", "toml"]

}

}

}

However, apart from that assuming `--gpus` `"all`" is commented out in the devcontainer.json file I can use this container to build and run bevy apps (though they use software rendering and are thus very slow). Though I do get some `VK_ERROR_INCOMPATIBLE_DRIVER` errors in the bevy log on startup

```
TU: error: ../src/freedreno/vulkan/tu_knl.cc:369: failed to open device /dev/dri/renderD128 (VK_ERROR_INCOMPATIBLE_DRIVER)

TU: error: ../src/freedreno/vulkan/tu_knl.cc:369: failed to open device /dev/dri/renderD129 (VK_ERROR_INCOMPATIBLE_DRIVER)
```

If I instead uncomment `"--gpus"` `"all"` in then bevy find my nvidia gpu but the program crashes with a bunch of vulkan rendering issues.

If anyone knows what is going on here could you please let me know what's happening and how I fix it. Thanks

Hi all,

I'm trying to learn what I need to build some CFD software in bevy. One of the big bits I need to know for this is how to efficiently make plots of surfaces, grids and procedurally generated meshes (*).

I thought I'd have a go at updating bevy plot https://github.com/eliotbo/bevy_plot as a starting point, given the requirements are similar, but the code currently seems to be all kinds of broken (despite the presence of cargo releases and examples) and nothing runs. (edit: I checkout through the commits and now suspect the fella that built it got part way through updating from 0.7 to 0.15.1 and then abandoned it, which would explain it being broken and also unfortunately mean it's way more out of date than I thought)

Does anyone know what's up with bevy plot and/or another good example of how to run this kind of stuff in bevy?

Thanks

* These mesh are generated by the software (with some user input) dependant on a bunch of criteria relating to the available computational power (CFD problems can take minutes on a laptop to days on a supercomputer depending on complexity) and a bunch of mathematical constraints. A basic overview with some images of the kind of visualisations I want to render can be found here https://cfdland.com/mesh-types-in-cfd-a-comprehensive-guide/