    
# lsmod | grep radeon
radeon               1888256  9
video                  77824  2 amdgpu,radeon
i2c_algo_bit           12288  2 amdgpu,radeon
drm_suballoc_helper    12288  2 amdgpu,radeon
drm_display_helper    266240  2 amdgpu,radeon
drm_ttm_helper         12288  2 amdgpu,radeon
ttm                   102400  3 amdgpu,radeon,drm_ttm_helper
drm_kms_helper        253952  3 drm_display_helper,amdgpu,radeon
drm                   749568  16 gpu_sched,drm_kms_helper,drm_exec,drm_suballoc_helper,drm_display_helper,drm_buddy,amdgpu,radeon,drm_ttm_helper,ttm,amdxcp

1y ago

[Solved] Can't connect to host after enabling WireGuard tunnel

Jump

user_naa @lemmy.world 1y ago

I left PostUp as is and didn't try removing -o))

1y ago

Running Arch in chroot

Jump

user_naa @lemmy.world 1y ago

What Systemd compatibility I need to run Graphics session?

1y ago

Running Arch in chroot

Jump

user_naa @lemmy.world 1y ago

If you're using an Intel chip look into GVT-g and consider running Arch from a VM, that'll be the closest thing to native.

I want to start clear Arch Wayland session on one my ttys and want to Arch have full direct hardware access.

The unfortunate thing about running an Arch container from a Debian host is that you're relying on an older kernel

I use latest Linux-libre on my Debian machine and everything works well.

If you are very, very lucky Arch will just work inside the container, but IME that's fairly rare as systemd often has breaking changes over several releases (and Arch tends to be at least several releases ahead of Debian.)

As I mentioned earlier I tried running Archbox. It is basically script to easy set up chroot. The main problem was that compositor couldn't connect to Wayland socket.