no /devdri/card0

Y

yvw_from_da_hills

hello,

FreeBSD 14.2 release
intel integrated graphics, 11 gen, tiger lake iris gen2

I had a working laptop destop system.

Now i decided to make a clean install of the FreeBSD. I learned that there is a new 'desktop-install' utility and gave it a try.

In the process of testing that X11 will start up, I got (EE) open /dev/dri/card0: no such file or directory.

I had grahics working before. The DRM was operable by the means of libdrm at least.

the installer had installed drm-kmod and firmware for the GPU.

the question is, is it somehow a misconfiguration issue? I do have /devdrm/0 in my system. I do not have /dev/dri directory.

P.S Maybe creating a directory in /dev, with a simlinks to /dev/drm/n, will help? But since /dev is a special directory, I do not know how to create and simlink within it.
 
hello, SirDice,

what is web docu for the process? where can i see this catch with packages and their version?

no offence, we had our projects built as whole. **or not**. now i begining thinking about it. no no, as a whole... surely.

there is a docu about versioning?

thanks
 
yvw_from_da_hills said:
there is a docu about versioning?
Click to expand...
Probably on the mailing lists somewhere, but you can figure out how this works. All -RELEASE versions point to pkg.freebsd.org/${ABI}/quarterly by default. That ${ABI} variable translates to FreeBSD:14:amd64 on FreeBSD 14.x amd64. As you can see there's only a major version to distinguish between versions. Which means all 14.x versions are using the exact same repository.

As 14.1 is still supported the packages on the package repositories are built for 14.1. This is fine for 99.9% of the packages, userspace applications should all work on 14.2 without problems (due to enforced ABI stability). Kernel modules however can be quite finicky, especially the DRM drivers. Those often have to compiled for the exact kernel version or they'll fail to load, or worse, crash the machine.

yvw_from_da_hills said:
no offence, we had our projects built as whole. **or not**.
Click to expand...
You need to realize FreeBSD is built as a "whole", but the ports/packages are a completely separate entity, it does not follow the same release cycle as the base OS for example (it has no release cycle, at all). All versions on all architectures use the exact same ports tree. So applications like Apache have the same version across all supported FreeBSD versions and architectures. This is quite different from most Linux distributions, where LinDist 1.0 might have Apache 2.2 and LinDist 2.0 may have Apache 2.4. For us it is perfectly fine to have FreeBSD 13.4 with Apache 2.4 and PHP 8.4 and a FreeBSD 14.2 with Apache 2.4 and PHP 8.0.
 
Thank you, SirDice, for the explanation,

One more thing to explain please. If I build from source, not a kernel related port, what is a way to ask 'pkg' to prefer binary dependantcy list? i.e to use binary builds of packages the port depends on? I've build opencv, and it was some hour.
 
You must log in or register to reply here.
Back
Top