Resolving a crash/reboot

D

dbarron

Ok, I've had a few issues getting FreeBSD 15 installed, but I got past that. I'm relatively new to FreeBSD, but an experienced tech user all my life.
Then my wifi wasn't working. It was simply a matter of blacklisting iwd and correcting the blind type typo of my passphrase (*yeah*).
However, I haven't gotten graphics working well.
I can load amdgpu, and the console display resolution gets higher (hard on older eyes though), but when I try to launch sddm, it crashes, when I try to startplasma-wayland, it cores and reboots the machine.
What steps could I take to validate the display server is working (or not) ? I'd like to most easily validate that before I go chase down plasma or wayland issues.
GPU is (linux inxi -G)
Device-1: Advanced Micro Devices [AMD/ATI] Navi 33 [Radeon RX 7600/7600
XT/7600M XT/7600S/7700S / PRO W7600] driver: amdgpu v: kernel
I believe I've loaded the latest kmods and firmware associated with amd/radeon. Dbus is running and not producing any errors (that i have seen).
 
dbarron said:
FreeBSD 15
Click to expand...
15.0 or 15.1? That distinction is important.

What does pkg version -vRx gpu-firmware show?

dbarron said:
I try to launch sddm, it crashes, when I try to startplasma-wayland,
Click to expand...
Do you want Wayland or Xorg? If you're going for X use startx (as a user) to test, disable the display manager, for now. Then after startx (and likely failing) post your Xorg.0.log. Easily done from the command line cat /var/log/Xorg.0.log | nc termbin.com 9999
 
15.1 sorry.
I would prefer Wayland (less moving parts) but would settle for an X server. I actually tried startx then found I didn't apparently have all the x windows ingredients installed, because it wasn't there. Then I thought, I'd prefer Wayland anyway, and headed down that path.
Since I can't get a graphical environment on BSD, I'm writing from a Linux environment, I'll edit this comment with the output of pkg when I reboot in a bit. Yes, i do not have sddm set to startup automatically.
Edit 1: pkg version -vRx gpu-firmware returns no results. Did I end up with an incomplete install due to no network at the time of installation?
 
Maybe I should reinstall with ethernet connected, now that I know what is required to get through installation successfully and somewhat less flailing aimlessly?|
I installed so many firmware packages (it seemed to me) that I'm not exactly sure where I'm at :0 and know no way to revert to a sane state (is there?)
 
The problem with Wayland on FreeBSD is that you will need a working drm compatible driver. So amdgpu, radeon, i915kms or nvidia must be working for you to have a desktop.
With X (pkg install xorg or xlibre) you can use either the vesa (bios) or framebuffer (uefi) to get a working desktop (as long as composition is disabled).
 
dbarron said:
Maybe I should reinstall with ethernet connected
Click to expand...
No need, it's not going to change anything. Ethernet will make it easier to update and install various other requirements but there's absolutely no need to completely reinstall the OS to make this happen.
 
No, I'm implying you do NOT need to reinstall the OS from scratch to make some configuration adjustments, it's not Windows.
 
dbarron said:
Ok, so is the consensus simply that it's not going to work and I should just forget FreeBSD on this hardware, at least at this time?
Click to expand...
No, your hardware is known to work and will probably work with 15.1 if either you build some required components from source until the relevant packages are fixed or wait until those fixes are in (my current guess is that by September 15 the issues will be fixed).
So, you have at least the following options:
  • Build from source the drm-612-kmod and gpu-firmware-amd-kmod packages and install them, getting a working system
  • Use the OS from terminal (if that's okay for you)
  • Use a non-accelerated DE (including KDE) on X11 until the packages are fixed (i.e. wait but have a working system until the issues are fixed)
  • Use 15.0 (there should be no issues there and your hardware should also be supported barring some known issue/bug)
 
I thank you for providing some clarify on my issues.
While I have 30 years of porting/compiling (on an occasional basis), I think I'll pass maintaining the OS for myself and just wait. It's been interesting jumping through the hoops (I regard it as a challenge) getting it installed. And perhaps the installation issues are related to the graphical driver issues, so it may all be one thing...since a tweak to reduce resolution allowed me to get past the boot loader.
Umm, no, I love the GUI world, I'm very terminal centric and wouldn't want anyone to take my CLI from me, but....GUI has it's place too :) I find I live more in my browser than anything these days.

Interesting that 15.1 has an unresolved support issue vs 15.0?

My purpose has been to evaluate moving myself from Linux to BSD for my primary operating system, it doesn't appear to me that myself/hardware and FreeBSD are a good match at the moment. In fact, I'm not sure, given my experiences, that FreeBSD is ready for the masses, even if I don't consider myself a representative of the masses. I had to find my own resolution to issues getting the installation to run (another thread) successfully, the forums were completely non helpful there. I hate that ChatGPT turned up something that worked after more than a week of things that didn't work. Then apparently regressions between 15.1 and 15.0? I know this isn't Linux, but if an issue like this (which I don't know the details, so I'm making assumptions) were identified, a fix would be more immediately issued.
I sincerely miss the superb documentation in one place of the Arch-Wiki.

However, in all fairness, maybe I can look again at 15.2? (is that the target?) Just for grins, I may give a 15.0 a try.
 
fahrenheit said:
No, your hardware is known to work and will probably work with 15.1 if either you build some required components from source until the relevant packages are fixed or wait until those fixes are in (my current guess is that by September 15 the issues will be fixed).
So, you have at least the following options:
  • Build from source the drm-612-kmod and gpu-firmware-amd-kmod packages and install them, getting a working system
  • Use the OS from terminal (if that's okay for you)
  • Use a non-accelerated DE (including KDE) on X11 until the packages are fixed (i.e. wait but have a working system until the issues are fixed)
  • Use 15.0 (there should be no issues there and your hardware should also be supported barring some known issue/bug)
Click to expand...
And OMG, you are absolutely right about 15.0, the installer runs without any need to tinker. I'm gonna run an install and see what happens...
 
dbarron said:
And OMG, you are absolutely right about 15.0, the installer runs without any need to tinker. I'm gonna run an install and see what happens...
Click to expand...
The issue is that the kernel modules for GPUs are not part of the base system and are ports, and currently are built against a 15.0 kernel which is an issue because there were changes on the 15.1 kernel (to support a newer DRM version, i.e. hardware) that make these 15.0 kernel modules incompatible. The September date is when ports will start being built against 15.1, although the issue should be solved until then (as there is infrastructure in place to have kernel mods for each minor release).

If the issue is not solved until then, on 15.2 you will have the same issue (i.e. you have to build from sources) until the 3 month rollover.
And yes, this is a known issue and is being worked up on. And everyone agrees that it's a pain in the ass :P
 
fahrenheit said:
The issue is that the kernel modules for GPUs are not part of the base system and are ports, and currently are built against a 15.0 kernel which is an issue because there were changes on the 15.1 kernel (to support a newer DRM version, i.e. hardware) that make these 15.0 kernel modules incompatible. The September date is when ports will start being built against 15.1, although the issue should be solved until then (as there is infrastructure in place to have kernel mods for each minor release).

If the issue is not solved until then, on 15.2 you will have the same issue (i.e. you have to build from sources) until the 3 month rollover.
And yes, this is a known issue and is being worked up on. And everyone agrees that it's a pain in the ass :P
Click to expand...
Wait a minute. The kernel syncronized versions of almost all kmods are in FreeBSD-ports-kmods.
What you said belong to the past, even if anyone is free to compile its kmods.
 
I don't know...but I can attest that the 15.0 booted cleanly for me, where 15.1 did not.
I haven't yet determined if the graphics driver works cleanly, because I think I fubar'd the efi boot loader somehow...possibly by keyboard navigation and skipping it *haah*, so I'll rerun the install and watch myself more closely
 
Ok, fresh 15.0 install, and I installed drm-kmod package, loaded it, and my machine rebooted.
Having done nothing else, what should the next thing be? firmware update ? Ideas?
 
dbarron said:
Ok, fresh 15.0 install, and I installed drm-kmod package, loaded it, and my machine rebooted.
Having done nothing else, what should the next thing be? firmware update ? Ideas?
Click to expand...
Can you confirm that you have the drm-66-kmod package (pkg info drm-*kmod) and the gpu-firmware-amd-kmod package (pkg info gpu-firmware*) installed?
 
fahrenheit said:
Can you confirm that you have the drm-66-kmod package (pkg info drm-*kmod) and the gpu-firmware-amd-kmod package (pkg info gpu-firmware*) installed?
Click to expand...
I can confirm drm-66-kmod.
I'm not sure which firmware applies, but I have 324 of them on the system (I think)...since pkg doesn't seem to take wildcards as best I can ascertain?
 
fahrenheit said:
Yes, that is the theory, in practice it's broken right now :P
Click to expand...
I see that drm-66-kmod is well in sync with the kernel but not gpu-firmware-kmod that resides in FreeBSD-ports. I don't think that causes any problem for a minor version increase. Proof is that it doesn't work also for 15.0.

Look in dmesg which firmware is actually loaded. It may help.
 
Ah good point, I can load it w/o a crash. I can't unload it ;) I'll reboot, check it, and edit this post.
Here's what dmesg shows sucessfully loaded:
drmn0: successfully loaded firmware image 'amdgpu/psp_13_0_7_sos.bin'
drmn0: successfully loaded firmware image 'amdgpu/psp_13_0_7_ta.bin'
drmn0: successfully loaded firmware image 'amdgpu/smu_13_0_7.bin'
drmn0: successfully loaded firmware image 'amdgpu/dcn_3_2_1_dmcub.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_pfp.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_me.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_rlc.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_mec.bin'
drmn0: successfully loaded firmware image 'amdgpu/vcn_4_0_4.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_mes_2.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_mes1.bin'
drmn0: successfully loaded firmware image 'amdgpu/gc_11_0_2_imu.bin'
drmn0: successfully loaded firmware image 'amdgpu/sdma_6_0_2.bin'
 
You are doing good ! Keep it up.

When you are finished you are going to find FreeBSD is a MUCH easier system to use and maintain than Linux.

A lot of us (including me) are also long time Linux users as well... so we know :cool:

Good work !
 
You must log in or register to reply here.
Back
Top