13-2 -> 13.3 amdgpu doesn't work

astyle said:
Packages still being built for a system that is gonna be EoL so soon?
Click to expand...
Yes. And will continue to be built until it's really EoL. It might be EoL soon, but it's still a supported version until the actual EoL date. 13.3 packages will certainly have problems when installed on 13.2, while 13.2 packages will work fine on 13.3. With the notable exception of kernel modules, those are almost always a problem.
 
So building from ports should fix this? Will I be getting into dependency issues with other packages?
 
Yeah, you will.

Linux suffers from the same dependency hell. Building a port on FreeBSD is at least easier than on Linux.
 
Well I would like for someone to say confidently that building the port will really work! :-) Before I get myself into issues....
 
And basically what I'm also hearing is that I should have waited until 13.2 was actually EOL before updating.
 
When all these pkgs updated last month, I thought that was taking care of the 13.3 issues. What was that giant update about then?
 
astyle said:
meaning on the downloadable ISO's?
Click to expand...
Yep, or memory stick images.

Since these packages will only work with that specific FreeBSD kernel (also on the DVD), it makes sense to bundle them there.
Traditionally they would be in the kernel.txz set as a kernel module before we moved over to borrowing Linux's KMS stack, so it would be like a middle ground / compromise.
 
Um, the issue described here was that I need to build drm-kmod specifically for 13.3, since the pkg version is for 13.2!
 
Ha, well, I only switched from ports to pkgs a few years ago.... I spent about 20 years compiling everything, including 'make buildworld' 'make buildkernel' etc.

Do you build a browser in ports? That's where it was becoming a challenge.

And I'm not too keen on mixing ports & pkgs now, but we'll see. I'm also not keen on going a couple of months with no X/browser on my desktop!
 
BTW, why aren't I getting a screen saver in console mode? I did `kldload logo_saver` with no errors, but no screen saving happened either....
 
SirDice said:
This. Keep in mind that packages in the FreeBSD repositories are still being built for 13.2. This isn't an issue for the majority of the packages, but kernel modules like this one are always a bit of a problem. Packages will get build for 13.3 specifically when 13.2 is EoL (at the end of June 2024).
Click to expand...
How many (kernel module) packages (more generally perhaps: those that must be built for a specific major.minor version ) are we talking about approximately?
  1. 50-100
  2. 100-500
  3. 500-5000
  4. 5000-10000
  5. > 10000
 
Erichans said:
How many (kernel module) packages (more generally perhaps: those that must be built for a specific major.minor version ) are we talking about approximately?
Click to expand...
There are probably a couple more but graphics/drm-kmod (plus related ports) and emulators/virtualbox-ose-kmod are the most prominent ones that often give problems during the three month transition period.

In all it's just a handful, less than 50 (of the 40.000+ packages).
 
I'm still not reading a problem with creating specific 13.3 kmod pkgs for the transition period. Why not do it?
 
Because it only affects a handful of packages during a short period. Why spend a lot of resources on that? Resources are finite and already fairly limited?
 
Well OK. It seems like something that'd only take a few minutes, but I understand, sometimes you don't have a few minutes.

I wouldn't be in this situation, I would have waited, but I assimilated pkgs & ports in my mind, so when I saw the warning, I was thinking I just needed to update the pkg. So that's indeed my foolishness.
 
You must log in or register to reply here.
Back
Top