Good observation - and it is correct that way, because thus the balance is created. Purely conservative, not moving at all, is death. Purely innovative, wildly growing in all directions, is cancer. None of them could support life.
Good observation - and it is correct that way, because thus the balance is created. Purely conservative, not moving at all, is death. Purely innovative, wildly growing in all directions, is cancer. None of them could support life.
Yes, fundamentals are more or less the same. Just compare with PCR machine which was popular in my days or now. When we show the students they just laugh. Settings are very important (not just settings) but fundamentals is the same.
Exactly. The reason older folks are skeptical of the new hotness is that we've seen so much hype come and go, and often had to pick up the pieces when the whiz-bang new thing blew up in midair.
Too late!
Here is a parody of GNU autotools (not mine) that – I feel – grabs its essence, at least from a user's perspective:
for i in /usr/include/*.h; do echo -n "checking for $i ... "; sleep 1; echo "ok"; done
What's in it? Just remove it. It should autodetect the modesetting driver.
X just looks for the old intel(4) driver by default, doesn't mean it's supposed to be there.
Not relevant any more. FreeBSD 13.1 is now EoL and packages are being built for 13.2 specifically. And, in this case, the DRM driver built for 13.1 worked just fine on 13.2, so this was never an issue to begin with.
Thank you for the ultra fast response.
Section "Device"
Identifier "Card0"
Driver "intel"
EndSectionDriver "intel" with Driver "modesetting".That's fine. I would recommend using that until you get X configured correctly. Makes it easier to test.
Most, if not all, display managers allow you to select the window manager/desktop environment you want to start for that session.
Replacing "intel" with "modesetting" indeed did the trick and startx also works with it. Same with not having a 20-intel.conf file at all. So this file seems to be obsolete. Should the handbook be edited accordingly?
Did you miss this?
I did miss that! ?Did you miss this?
Call For Testing: nvidia-drm kernel module
Hello everyone, I'm happy to announce that the port of Nvidia's DRM driver is now ready for public consumption. Please visit the github repo to grab the latest copy of the driver. Simply follow the installation instructions and load the nvidia-drm.ko kernel module to give it a go. Please post...forums.freebsd.org
Or you could have read the 14.2 errata.
It has to do with changes in the kernel between 14.1 and 14.2. Packages are still being built for 14.1 because it's still supported. This is not an issue for 99.9% of the packages, but kernel modules like the DRM driver are often a problem. This issue resolves itself when 14.1 is EoL and packages are build for 14.2. In the meantime there's a solution by either building the DRM drivers from ports or add a special repository that has the DRM drivers for 14.2.
Which I did and then I installed a fresh ports collection from git and attempted to compile drm-kmod (and also tried drm-61-kmod, since it was recommended in the forums). These both ran into an error and I wasn't able to build the drm-driver from ports. (can't show you the error log since I'm back on archlinux).Or you could have read the 14.2 errata.
FreeBSD 14.2-RELEASE Errata
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.www.freebsd.org
It has to do with changes in the kernel between 14.1 and 14.2. Packages are still being built for 14.1 because it's still supported. This is not an issue for 99.9% of the packages, but kernel modules like the DRM driver are often a problem. This issue resolves itself when 14.1 is EoL and packages are build for 14.2. In the meantime there's a solution by either building the DRM drivers from ports or add a special repository that has the DRM drivers for 14.2.
I'm not an experienced Arch user by any means, neither of Wayland but, perhaps a few things to keep in mind regarding FreeBSD, its support model, graphics drivers development process & Wayland.
