-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to FreeBSD 14.0-CURRENT for better GPU support. #271
Comments
I like this idea, however I'd prefer the system and packages to be upgradeable. Respectively:
Maybe too adventurous. See for example freebsd/drm-kmod#93 As a default for -CURRENT, graphics/drm-kmod is probably safer. |
At this point we still have documented showstoppers that prevent us from going from 12 to 13, let alone 14 |
Fixed whilst testing an upgrade: wulf7/utouch#2 |
@grahamperrin can you please elaborate? What is "utouch_softc's mutex" and how is it related to this ticket? |
Encountered whilst experimentally building and installing 14.0-CURRENT (over 13.0-RELEASE-p3). |
@target-relative you can install 14.0-CURRENT, however – not OS version-specific – you'll probably encounter breakage of helloSystem applications such as the three pictured (2021-06-18) at #267 (comment); probably the four listed at #267 (comment). |
Can graphics/drm-devel-kmod not be compiled from ports on 13-stable? Sorry if this has been answered elsewhere; i've looked but not found anything to suggest it can't. |
This comment has been minimized.
This comment has been minimized.
I am really confused about all the FreeBSD versions that are available and partly supported in parallel. 12.x seems the one where most things work, 13.x is still the new kid on the block where things are broken, and now people are already talking about 14.x... all the while Ports make some (which?) implicit assumptions about the FreeBSD version users are running. |
FreeBSD
We have full support for multiple versions: Support is tiered by platform/architecture:
No, there were release engineering (releng) processes during which things were fixed for all three releases:
Orientationhttps://cgit.freebsd.org/src/log/?h=main
https://cgit.freebsd.org/src/log/?h=stable/13 https://cgit.freebsd.org/src/log/?h=releng%2F13.0
ExampleI built and installed 14.0-CURRENT a few hours ago. Boot environments are normally named, by me, to include the revision.
Taking 08b9cc316a3 from the currently active environment: Ports
Not really. Ignoring FreeBSD 11.4-RELEASE, which is nearly end of life …
– and so on. For example, a few weeks ago I built editors/nano on 13.0-RELEASE-p3 then ran it on 14.0-CURRENT. From https://forums.FreeBSD.org/threads/80117/post-523432:
Nothing OS version-specific in the makefile for editors/nano; nothing OS version-specific in the makefile for www/falkon; and so on. |
The way I think about it is: 11.x and 12.x is legacy but is still production https://www.freebsd.org/releases/ Some things (like *kmod; another one is lsof) need to be built against the relevant kernel sources, in order to run. edit: you'll see from the link I've pasted that point releases have their own EoL, like for example 12.0 |
Undoubtedly. People are often advised to upgrade from 11.4 or 12.2 to 13.0-RELEASE. Downgrade situations are extremely rare. https://old.reddit.com/r/freebsd/comments/pbdyo8/-/hab19cy/ is a rare example of a use case where the installer for 13.0-RELEASE is not usable, so there's a plan to simply install 12.2 then update, then upgrade to 13.0-RELEASE-p4. |
This comment has been minimized.
This comment has been minimized.
Because of drivers, I had to install FreeBSD 13-based helloSystem, and had absolutely no issues there at all. |
It can be built ▶ https://forums.FreeBSD.org/threads/81919/post-531421 |
There is now a (crashing) build based on 14-CURRENT. Maybe someone can figure out what is going on. |
helloSystem/hello#161 (comment)
Some PostscriptIt's now packaged for latest and quarterly. |
Is your feature request related to a problem? Please describe.
It is, limited hardware has fully working graphics hardware. My laptop has a newer iGPU so the version of drm-kmod available does not support it. Switching to the FreeBSD 14.0-CURRENT snapshot allows you to get drm-devel-kmod which supports up to the soon-releasing 12th gen intel chips and tons of AMD and nVidia GPUS.
Describe the solution you'd like
I would like it if helloSystem migrates to FreeBSD 14.0-CURRENT so it can use drm-devel-kmod. This would give better GPU support. It would be nice if you put
exec="mode 0"
in /boot/loader.conf so a GPU not supported by the updated driver support will still run at the monitors resolution and supported GPUs will still have the native resolution before the drivers loads.Describe alternatives you've considered
The only alternative would to be putting
exec="mode 0"
in /boot/loader.conf without the GPU driver which for me at least will force FreeBSD to go to the displays maximum resolution but that would not fix any bugs relating to no hardware acceleration.Additional context
I know both of these work because I used exec="mode 0" in the loader.conf file when I used FreeBSD 13.0-RELEASE (also in helloSystem 0.5 but just entering mode 0 in the loader prompt and not the file) which does not have drivers that support my iGPU and I am currently using FreeBSD 14.0-CURRENT with the exec="mode 0" option in my loader to get a widescreen boot splash and have drm-devel-kmod so I have graphics acceleration.
The text was updated successfully, but these errors were encountered: