13-2 -> 13.3 amdgpu doesn't work

[tingo]

Well OK. It seems like something that'd only take a few minutes, but I understand, sometimes you don't have a few minutes.

If you are interested, you could always look into the ports framework, learn how to build ports and packages, and figure out how to add a set of packages for each minor supported version of FreeBSD yourself.
Does it still sound like a job that would take just a few minutes?

 

[monwarez]

Building drm-515-kmod only took 1min14sec on my machine. Having a secondary FreeBSD binary repository for just some kernel module could be done with the existing server resource, it is mostly a matter of doing this kind of setup that could take some maintenance time.

 

[Erichans]

That would be along my lines of thought as well; like I suggested in Optional sub-indexing by minor version for packages.

 

[monwarez]

Also if I recall, another argument was that drm-kmod will be back in base in the future.

 

[Todd McComb]

It did sound temporary back for 13.0....

 

[kpedersen]

Also if I recall, another argument was that drm-kmod will be back in base in the future.

Thats interesting. Is there any link to the discussion of reintroducing it back to base?

 

[monwarez]

Thats interesting. Is there any link to the discussion of reintroducing it back to base?

It was in the devsummit for the 14.0 planning, but I don't recall why it was not in base at the end.

 

[SirDice]

but I don't recall why it was not in base at the end.

Probably because there's still a lot of development work to be done. If it was part of the base then those updates would have to come with an patch or version upgrade of the base OS. A port is much easier to update. Turnaround time is much shorter.

 

[kpedersen]

Probably because there's still a lot of development work to be done. If it was part of the base then those updates would have to come with an patch or version upgrade of the base OS. A port is much easier to update. Turnaround time is much shorter.

Could the same not then be said for i.e wifi drivers?

Specifically why is iwlwifi(4) not a port when in many ways it is following a similar type of development as the Linux DRM stack.

 

[Erichans]

Perhaps, but it may be that for wifi drivers such as iwlwifi(4) it was decided that those are more crucial to a base install as it may be the default way (or even sole way in case of some/most laptops) of communication with the internet to get your pkg(8); you don't have that chicken-and-egg problem with getting kmod graphics drivers.

 

[Todd McComb]

I'll leave you guys to the practicality debate here, but did want to note that I built the port this morning, and it all works. Thanks for explaining what's up, SirDice & other contributors.
Best wishes until my next disaster.

 

[Todd McComb]

Oh, maybe I'll add that I did decide to leave the kld_list for amdgpu commented out in my rc.conf, and just load it at the command line after boot. After all, if I'm not at the console, I don't need it anyway....

 

[kpedersen]

Oh, maybe I'll add that I did decide to leave the kld_list for amdgpu commented out in my rc.conf, and just load it at the command line after boot. After all, if I'm not at the console, I don't need it anyway....

You might still consider loading it. On my machines, I can save around 3-4W of energy with the correct kmod loaded (additionally it potentially exposes some power saving sysctls too).

 

[Todd McComb]

It's my desktop/main computer, so generally speaking, I do have X running there. It's just that in a crash situation or whatever it's not something I need to worry about starting up right away.

 

[Cath O'Deray]

… if I recall, another argument was that drm-kmod will be back in base in the future.

Certainly there was (bridged) discussion in Matrix, which would have been mentioned and referenced from the Forums.

DRM is not in the planning document for 15.0. I should not treat its absence as exclusive.

In the 15.0 context, I reckon that DRM can and should remain in the ports tree.