The moniker -STABLE has nothing to do with the stability of the OS. It's about the stability of the API/ABI.
Handbook: 23.4.2. Using FreeBSD-STABLE
Handbook: 23.4.2. Using FreeBSD-STABLE
agp exports several structures new driver uses. Actually, this thread matter was resolved after agp patching.Only if you actually have an AGP slot. Most modern machines have switched to PCIe.
static void agp_i915_write_gtt(device_t dev, u_int index, uint32_t pte);
It is mentioned, several times, that it's for 12-CURRENT and recently 11-STABLE. What makes you think 11-STABLE includes 11.1-RELEASE?there's not a word about it that it does not work in the release
then, we can try the official 12th STABLE today. and drm-next-kmod is not work on 11. but why do i see such articles as https://www.phoronix.com/scan.php?page=news_item&px=DRM-Next-KMOD-On-FreeBSD-11
?
and there's not a word about it that it does not work in the release
It does work. But there may still be issues to work out. That's the whole point of this exercise.that in a 11 STABLE - drm-next-kmod does not work.
You still don't seem to understand what -STABLE means. There won't be a 12-STABLE until 12.0-RELEASE (tentatively scheduled for January 2019).Now i just still wait 12 STABLE for use a drm-next-kmod.
andLet me stress this again, it does NOT work on 11.1-RELEASE, it is not meant to work on 11.1-RELEASE, it will never be made to work on 11.1-RELEASE(a few months from now).
?It does work
Handbook: 23.4.2. Using FreeBSD-STABLEI obviously don't understand something in your answers
What differs STABLE from RELEASE? STABLE is not a RELEASE?
There's only one -CURRENT and that is, at this time, 12-CURRENT. It will eventually become 12.0-RELEASE and -CURRENT will move to 13-CURRENT. 11-CURRENT doesn't exist anymore since 11.0-RELEASE.In general - if i understood correctly- this port works only in CURRENT versions of FreeBSD at the moment (11 and 12)
It is being tested on 11-STABLE to get it included in the next release; 11.2-RELEASE.a drm-next-kmod are need for a RELEASE, for the correct statement that it works
No.Can I use a drm-next-kmod in FreeBSD 11.1-RELEASE-p6? or not?
Great news, can anyone have a look if there's a DRI render device present for Intel video (ls -l /dev/dri) It would awesome if we could get Intel Quick Sync working
You might need to run X to have it show up from what I can tell.
abishai@sphinx:~ % ls -l /dev/dri
total 0
lrwxr-xr-x 1 root wheel 8 27 февр. 19:29 card0 -> ../drm/0
lrwxr-xr-x 1 root wheel 9 27 февр. 19:29 controlD64 -> ../drm/64
lrwxr-xr-x 1 root wheel 10 27 февр. 19:29 renderD128 -> ../drm/128
Great news, can anyone have a look if there's a DRI render device present for Intel video (ls -l /dev/dri) It would awesome if we could get Intel Quick Sync working
You might need to run X to have it show up from what I can tell.
ls -l /dev/dri
total 0
crw-rw---- 1 root video 0x2d Feb 19 18:35 card0
crw-rw---- 1 root video 0x2c Feb 19 18:35 controlD64
Dell XPS 13 9350 2016 (FHD, i7-6560U), suspend/resume works.What hardware and X?
Oh no, I just read on random sites that it only works when you have X running (which seems odd since ffmpeg have headless working on Linux)?Dell XPS 13 9350 2016 (FHD, i7-6560U), suspend/resume works.
X.Org X Server 1.18.4 Do we have options? I've noticed WAYLAND option for some ports, but disabled it, I'm not in a mood to tinker with something new [yet].
It just found the module late. If you load it first inThere is an error message in dmesg output, but it doesn't seem to affect anything:
Code:drmn0: fb0: inteldrmfb frame buffer device i915/kbl_dmc_ver1_01.bin: could not load firmware image, error 2 [drm] Finished loading i915/kbl_dmc_ver1_01.bin (v1.1)
kld_list=
, the firmware error message should go away.kld_list="/boot/modules/kbl_dmc_ver1_01 /boot/modules/i915kms.ko"
.if ${OPSYS} == FreeBSD && ${OSVERSION} < 1101510
make -C /usr/ports/-V OSVERSION
, I'm sure there's a better way). The only other thing a few minutes of googling found was a list of release numbers and OS versions but the method above seems simpler than finding that list each time.No. It will never be available on FreeBSD 11.1-RELEASE. What I meant was graphics/drm-*-kmod ports are going to be compatible with 11.2-RELEASE whenever it becomes available. The linuxkpi modules were MFC'd some time ago so recent 11.1-STABLE snapshots as well as pre 11.2 images are all capable of using this technology.Do you mean 11.1-RELEASE, or STABLE? Although I already moved my affected machine to 11.2-BETA and will keep it there, rather than CURRENT.
I see in the drm-stable Makefile
Code:.if ${OPSYS} == FreeBSD && ${OSVERSION} < 1101510
Which makes me think it won't run on 11.1-RELEASE. (At least the box I'm looking at shows $OSVERSION at 1101001. The only way I know to get that ismake -C /usr/ports/-V OSVERSION
, I'm sure there's a better way).