amdgpu ati radeon NetBSD-current

rvp

pfr but then reverted to "shithouse" reslolution

Not quite--that's just the larger font being used.

I would've said, "Party time!", except:

[    51.995337] panic: unlocking unlocked wait/wound mutex: 0xffffa82fa4fe0d20
[    51.995337] cpu1: Begin traceback...
[    51.995337] vpanic() at netbsd:vpanic+0x183
[    51.995337] panic() at netbsd:panic+0x3c
[    51.995337] linux_ww_mutex_unlock() at netbsd:linux_ww_mutex_unlock+0x9e
[    51.995337] ttm_bo_release() at netbsd:ttm_bo_release+0xf3
[    51.995337] amdgpu_bo_unref() at amdgpu:amdgpu_bo_unref+0x1d
[    51.995337] amdgpu_vm_free_table() at amdgpu:amdgpu_vm_free_table+0x53
[    51.995337] amdgpu_vm_free_pts() at amdgpu:amdgpu_vm_free_pts+0x6a
[    51.995337] amdgpu_vm_fini() at amdgpu:amdgpu_vm_fini+0x28c
[    51.995337] amdgpu_driver_postclose_kms() at amdgpu:amdgpu_driver_postclose_kms+0x133
[    51.995337] drm_file_free() at netbsd:drm_file_free+0x1fb
[    51.995337] drm_close() at netbsd:drm_close+0x60
[    51.995337] closef() at netbsd:closef+0x58
[    52.005335] fd_close() at netbsd:fd_close+0x140
[    52.005335] sys_close() at netbsd:sys_close+0x22
[    52.005335] syscall() at netbsd:syscall+0x1fc
[    52.005335] --- syscall (number 6) ---
[    52.005335] netbsd:syscall+0x1fc:

That's a kernel bug. File a PR (looks like the same issue as @r0ller) after you try the modesetting driver.

pfr I'm assuming this is the line that indicated that amdgpu doees not "take"?

No, just the opposite: it took.

BTW, the modesetting Xorg driver is recommended with DRMKMS. Do you have that config. fragment in place (so that the radeon driver is not tried)?

pfr

rvp BTW, the modesetting Xorg driver is recommended with DRMKMS. Do you have that config. fragment in place (so that the radeon driver is not tried)?

dmesg using modesetting in my xorg.conf
Running startx completely fails and the system automatically reboots.

rvp File a PR

Happy to. But, I'm out of my depth with this stuff..

What exactly am I requesting in the PR?
Where exactly do I submit the PR?
What should I include in the PR?

rvp

pfr dmesg using modesetting in my xorg.conf

Can't see any errors at all there.

pfr Running startx completely fails and the system automatically reboots.

Can you show the /var/log/Xorg.0.log resulting from this instance (ie. save the file before you do startx after the reboot).

pfr

rvp yeeehhhhhh, nope. It's there... But it's empty

pfr

Ok... I had some time away from my computer... 3 months just about. I've re-read over this entire thread again to refresh my memory. My brain hurts, but I still want to fix this!

Seeing as you've identified a kernel bug above, will recompiling the kernel (as suggested earlier in the peace) even solve this issue?

I'm prepared to submit a Problem Report, but having never done that before I may not do it 'properly'..

I've read over the PR Hint's page, but for things like Severity, Priority, Class fields I'm unsure what to enter. I'm guessing for this I'll assign it the sw-bug Class?

Anyway, I'll have a try and see what happens. I greatly appreciate all your support here @rvp 👍️
If I've missed anything in the last few months please do let me know, otherwise wish me luck.

rvp

pfr will recompiling the kernel (as suggested earlier in the peace) even solve this issue?

That's the first thing to do. Then enable sshd; boot using boot -vx (bootloader prompt); save the dmesg output; startx.

If startx crashes, try sshing into the machine to collect any kernel errors. If you can't ssh in, see if the keyboard works by pressing numlock. If it does, try rebooting the system blindly. Type: <space><enter>reboot (or sudo reboot--depending).

If you can reboot the system (instead of having to powering it down to recover), then the previous kernel messages should still be around in memory and a dmesg should be able to retrieve it after a reboot.

r0ller

pfr
There may be already a PR for this: 58032
At least, it's about "machine with amdgpu panics on starting X" and when searching through it I could find a crash dump with the "panic: unlocking unlocked wait/wound mutex" message where our problems also start.

rvp

r0ller As riastradh@ says in the PR, compile the kernel with all these uncommented:

# Diagnostic/debugging support options
options        DIAGNOSTIC       # inexpensive kernel consistency checks
                                # XXX to be commented out on release branch
options        DEBUG            # expensive debugging checks/support
options        LOCKDEBUG        # expensive locking checks/support

pfr

Looks like it worked! 🥳
However, Firefox (and Thunderbird) is now..... Completely transparent... 😐

~ λ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.462674) [GFX1-]: glxtest: DRM device has no render node
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.462674) |[1][GFX1-]: glxtest: Cannot find DRM device (t=0.462784) [GFX1-]: glxtest: Cannot find DRM device
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader
EE ../src/gallium/drivers/radeonsi/si_state_shaders.c:2226 si_build_shader_variant - Failed to build shader variant (type=0)
ac_rtld error: !data || data->d_size != shdr->sh_size
LLVM failed to upload shader

r0ller

pfr
Cool! However, it's not clear to me what made it work for you. I guess not that you compiled the kernel with enabled DIAGNOSTIC, DEBUG and LOCKDEBUG 🙂 Could you please, sum it up?

pfr

Could this possible be due to disabling the radion drivers in the kernel??

Here's some more info... Not sure if it's helpful or not..

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD Radeon RX 570 Series (POLARIS10, DRM 3.36.0, 10.0, LLVM 13.0.0) (0x67df)
    Version: 19.1.17
    Accelerated: yes
    Video memory: 4096MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 3917 MB, largest block: 3917 MB
    VBO free aux. memory - total: 4068 MB, largest block: 4068 MB
    Texture free memory - total: 3917 MB, largest block: 3917 MB
    Texture free aux. memory - total: 4068 MB, largest block: 4068 MB
    Renderbuffer free memory - total: 3917 MB, largest block: 3917 MB
    Renderbuffer free aux. memory - total: 4068 MB, largest block: 4068 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4096 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 3917 MB
OpenGL vendor string: X.Org
OpenGL renderer string: AMD Radeon RX 570 Series (POLARIS10, DRM 3.36.0, 10.0, LLVM 13.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.17
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.17
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.17
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Also...

~ λ firefox --MOZ_LOG=Dmabuf:5
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.520564) [GFX1-]: glxtest: DRM device has no render node
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.520564) |[1][GFX1-]: glxtest: Cannot find DRM device (t=0.520684) [GFX1-]: glxtest: Cannot find DRM device
[Parent 13098: Main Thread]: D/Dmabuf DMABufDevice::Configure()
[Parent 13098: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
[Parent 13098: Main Thread]: D/Dmabuf Failed to load libdrm.so.2, dmabuf isn't available.
[Parent 13098: Main Thread]: D/Dmabuf GbmLib is not available!
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!

EDIT/UPDATE:>>>

So I looked up libdrm in pkgsrc and came accross wip/libdrm-dfbsd.. so I installed this and now firefox seems to work.

Would you look at me go... 😝

YouTube is still pretty janky though... Downloaded videos and movies play fine, but streaming seems pretty weak.

pfr

r0ller my apologies.

I also uncommented the 2 amdgpu lines and commented out the 2 radion lines. That's it.

pfr

But we're not out of the woods yet it seems...

I only just noticed that alacritty fails to launch (since I've switched to LXQt I've been using qt-terminal which woks fine).

~ λ alacritty
libGL error: MESA-LOADER: failed to open radeonsi: /usr/pkg/lib/dri/radeonsi_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/pkg/lib/dri/swrast_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error: Error { raw_code: Some(167), raw_os_message: Some("GLXBadFBConfig"), kind: BadConfig }
~ λ

I suppose because alacritty uses gpu acceleration and what not... but Now I'm beginning to wonder if I should have commented out the Radeon lines in the kernel?

Furthermore, a correction to my above comment about YouTube being janky and slow... I cannot play youtube videos at all. The site loads, but videos just sit there apparently buffering with the little spinny circle forever...

I get this when I open Firefox from the terminal:

~ λ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) [GFX1-]: glxtest: ManageChildProcess failed

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) [GFX1-]: glxtest: libEGL initialize failed
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) [GFX1-]: glxtest: glGetString returned null
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) [GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) |[4][GFX1-]: No GPUs detected via PCI
 (t=0.452081) [GFX1-]: No GPUs detected via PCI

libGL error: MESA-LOADER: failed to open radeonsi: /usr/pkg/lib/dri/radeonsi_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/pkg/lib/dri/swrast_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) |[4][GFX1-]: No GPUs detected via PCI
 (t=0.452081) |[5][GFX1-]: Failed GL context creation for WebRender: 0 (t=1.00338) [GFX1-]: Failed GL context creation for WebRender: 0
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) |[4][GFX1-]: No GPUs detected via PCI
 (t=0.452081) |[5][GFX1-]: Failed GL context creation for WebRender: 0 (t=1.00338) |[6][GFX1-]: FEATURE_FAILURE_WEBRENDER_INITIALIZE_UNSPECIFIED (t=1.00346) [GFX1-]: FEATURE_FAILURE_WEBRENDER_INITIALIZE_UNSPECIFIED
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) |[4][GFX1-]: No GPUs detected via PCI
 (t=0.452081) |[5][GFX1-]: Failed GL context creation for WebRender: 0 (t=1.00338) |[6][GFX1-]: FEATURE_FAILURE_WEBRENDER_INITIALIZE_UNSPECIFIED (t=1.00346) |[7][GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true (t=1.00391) [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.45183) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.451975) |[2][GFX1-]: glxtest: glGetString returned null (t=0.452008) |[3][GFX1-]: glxtest: X error, error_code=2, request_code=153, minor_code=3 (t=0.452037) |[4][GFX1-]: No GPUs detected via PCI
 (t=0.452081) |[5][GFX1-]: Failed GL context creation for WebRender: 0 (t=1.00338) |[6][GFX1-]: FEATURE_FAILURE_WEBRENDER_INITIALIZE_UNSPECIFIED (t=1.00346) |[7][GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true (t=1.00391) |[8][GFX1-]: Fallback WR to SW-WR (t=1.00419) [GFX1-]: Fallback WR to SW-WR                                                                                                                                                       
console.error: ({})                                                                                                                                       
JavaScript error: moz-extension://42a6551e-221a-44d7-aefc-fe903fa11ba3/background.js, line 1: TypeError: null has no properties                           
console.error: "getScreenshot(https://postimgs.org/apple-touch-icon.png) failed:" (new Error("page-thumbnail:error", "resource://gre/modules/BackgroundPageThumbs.sys.mjs", 141))

No GPUs detected via PCI... failed to load driver: radeonsi... Whaaaaaa?

rvp

pfr

~ λ alacritty
libGL error: MESA-LOADER: failed to open radeonsi: /usr/pkg/lib/dri/radeonsi_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/pkg/lib/dri/swrast_dri.so: Undefined PLT symbol "amdgpu_query_video_caps_info" (symnum = 201) (search paths /usr/pkg/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error: Error { raw_code: Some(167), raw_os_message: Some("GLXBadFBConfig"), kind: BadConfig }
~ λ

This indicates a mismatch between libdrm (where amdgpu_query_video_caps_info is implemented) and Mesa/dri. I don't know how you ended up in this mess--prolly due to the WIP package? Both Mesa/dri and libdrm are provided by the base Xorg package (unless you've skipped that entirely and gone with the modular Xorg package).

Uncommenting the debug options in the kernel config can push some class of bugs underground--like cockroaches...ie. doesn't mean they're "fixed". However,

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.462674) [GFX1-]: glxtest: DRM device has no render node

Have you got the standard device files (with the correct perms.) in /dev/dri:

$ ls -l /dev/dri/
total 0
crw-rw----  1 root  wheel  180,   0 Feb 15  2024 card0
crw-rw----  1 root  wheel  180,   1 Feb 15  2024 card1
crw-rw----  1 root  wheel  180,   2 Feb 15  2024 card2
crw-rw----  1 root  wheel  180,   3 Feb 15  2024 card3
crw-rw----  1 root  wheel  180, 128 Jan 31  2024 renderD128
crw-rw----  1 root  wheel  180, 129 Jan 31  2024 renderD129
crw-rw----  1 root  wheel  180, 130 Jan 31  2024 renderD130
crw-rw----  1 root  wheel  180, 131 Jan 31  2024 renderD131
$

Create them using:

$ su -l
# cd /dev
# sh ./MAKEDEV drm0 drm1 drm2 drm3

Then file a PR with the dmesg and Xorg.0.log outputs if it still fails to work (after you get rid of the extra libdrm stuff).

pfr

rvp don't know how you ended up in this mess--prolly due to the WIP package?

Possible, but before installingwip/libdrm-dfbsd firefox was not usable as the screenshot illustrates.

rvp Both Mesa/dri and libdrm are provided by the base Xorg package (unless you've skipped that entirely and gone with the modular Xorg package).

I don't recall doing anything fancy with the install... Is there a way to check?

rvp ave you got the standard device files (with the correct perms.) in /dev/dri

Yep.

~ λ ls -l /dev/dri/
total 0
crw-rw----  1 root  wheel  180,   0 Jun 18 10:57 card0
crw-rw----  1 root  wheel  180,   1 Jun 18 10:57 card1
crw-rw----  1 root  wheel  180,   2 Jun 18 10:57 card2
crw-rw----  1 root  wheel  180,   3 Jun 18 10:57 card3
crw-rw----  1 root  wheel  180, 128 Jun 18 10:57 renderD128
crw-rw----  1 root  wheel  180, 129 Jun 18 10:57 renderD129
crw-rw----  1 root  wheel  180, 130 Jun 18 10:57 renderD130
crw-rw----  1 root  wheel  180, 131 Jun 18 10:57 renderD131

pfr

I'll add that I didn't notice that alacritty wouldn't launch until after I'd installed wip/libdrm-dfbsd in order to fix the firefox issue.

I could perhaps uninstall the wip/libdrm-dfbsd package and then see what other errors I get... however, I anticipate firefox and thunderbird being unusable again. You can see the errors produced by firefox in my comment's above.

rvp

pfr I could perhaps uninstall the wip/libdrm-dfbsd package

Yes.

As I said: this looks like a kernel bug. You should file a PR (after you've tried the modesetting driver--have you?); and until it's fixed you could just turn off GL rendering, as a workaround.

In ~/.xinitrc (or, ~/.xsession):

# for firefox
export MOZ_ACCELERATED=0
export MOZ_WEBRENDER=0

# for all MesaGL (see: https://docs.mesa3d.org/envvars.html)
export LIBGL_ALWAYS_SOFTWARE=true

Or, just go back to the wsfb Xorg driver (which works on top of the DRMKMS-provided framebuffer too) as a last resort.

pfr

rvp after you've tried the modesetting driver--have you?

That's what I am using now, yes.

rvp In ~/.xinitrc (or, ~/.xsession):

Similar to our other discussion, I'm curious to know if it is imperative that I use one of these and not ~/.profile? I have most other environment variables set in my ~/.profile

EDIT

Furthermore, I cannot seem to find where libdrm-dfbsd is installed or how to uninstall it?

bsduck

wip/libdrm-dfbsd

Does NetBSD import drivers from DragonFly BSD?

rvp

pfr Similar to our other discussion, I'm curious to know if it is imperative that I use one of these and not ~/.profile? I have most other environment variables set in my ~/.profile

If you run xdm/xenodm, then env. vars should be set in ~/.xsession. Any PATHs set in ~/.profile will only take effect inside xterms (and that too only if they're configured to run login shells). So, the PATH printed in an xterm will likely be different from the PATH seen by programs started by ~/.xsession (including the WM).

Check what sdorfehs's idea of PATH is using: Ctrl-a :exec echo $PATH > /tmp/path.txt

Might be a good idea to have a ~/.xsession like this:

#!/bin/sh
. ~/.environ        # suck-in env. vars
. ~/.xinitrc        #    "   ~/.xinitrc

Suck in ~/.environ the same way in ~/.profile too, and then all your env. vars. will be in one place (akin to ~/.bash_aliases for aliases and functions).

pfr Furthermore, I cannot seem to find where libdrm-dfbsd is installed or how to uninstall it?

Why doesn't

pkgin -y rm libdrm-dfbsd

work?

pfr

rvp Why doesn't
pkgin -y rm libdrm-dfbsd
work?

~ λ pkgin list | grep libdrm
libdrm-2.4.99        Userspace interface to kernel DRM services
~ λ pkg_info | grep libdrm
libdrm-2.4.99       Userspace interface to kernel DRM services
~ λ pkgin -y rm libdrm-dfbsd
no such installed package libdrm-dfbsd
no packages to delete

Looks like it isn't installed.. but one minute FF was transparent (see the screenshots above to prove it!) and then I went to my handy fzf-pkgsrc.sh script that some cool person wrote, and installed wip/libdrm-dfbsd. It installed without errors. To confirm this I rebooted and FF worked... so I don't know.

As for why I decided to install a dfbsd package, well I don't know exactly, I was just taking stabs in the dark and I'm an idiot I guess 😭

Anyhow, perhaps we can simply move on to the PR?

rvp if you run xdm/xenodm, then env. vars should be set in ~/.xsession

Yep, this is now how it's setup on my OpenBSD system. But on NetBSD (the current machine with the amdgpu) I just use startx and I no longer use sdorfehs on this system, I use exec dbus-run-session -- startlxqt.

So my question should have been more specific: Why would I put env. vars into my ~/.xinitrc over my ~/.profile in this case? -- I currently set everything in ~/.profile and everything appears to work as intended.

Cheers.

« Previous Page Next Page »