update of graphics/drm-next-kmod to Linux 4.11 level for recent

[Johannes M Dieterich]

Dear all,

Please CC me as I am not subscribed.

On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.

We have tested this on a range of hardware ourselves:
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris

Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
patches, please do so at our development github:

https://github.com/FreeBSDDesktop/kms-drm

We absolutely do welcome contributions!

Johannes

[Ronald Klop]

Post by Johannes M Dieterich
Dear all,
Please CC me as I am not subscribed.
On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris
Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
https://github.com/FreeBSDDesktop/kms-drm
We absolutely do welcome contributions!
Johannes

Nice work. It might be nice to edit the linux 4,9 reference from pkg-descr.

Regards,
Ronald.

[Jan Bramkamp]

Post by Johannes M Dieterich
Dear all,
Please CC me as I am not subscribed.
On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris
Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
https://github.com/FreeBSDDesktop/kms-drm
We absolutely do welcome contributions!
Johannes

Thx for your hard work. The drm-next-kmod port enabled me to finally
replace my ageing Thinkpad X220 with newer hardware.

The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod
port introduced a regression which causes Xorg on my T470s running
12-current from a few days ago to fail at startup stating that it didn't
find any screen.

[Pete Wright]

Post by Jan Bramkamp

Post by Johannes M Dieterich
Dear all,
Please CC me as I am not subscribed.
On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris
Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
https://github.com/FreeBSDDesktop/kms-drm
We absolutely do welcome contributions!
Johannes

Thx for your hard work. The drm-next-kmod port enabled me to finally
replace my ageing Thinkpad X220 with newer hardware.
The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod
port introduced a regression which causes Xorg on my T470s running
12-current from a few days ago to fail at startup stating that it
didn't find any screen.

(removing freebsd-stable@ from this reply since this is a current system)

interesting, so Xorg complains about no displays being present if i
understand correctly?

can you verify that the i915 module is being loaded at boot, kld stat
should show something like this:
$ kldstat |grep i915
 7    1 0xffffffff82f38000 11f615   i915kms.ko

If it is present, can you also verify that you are a member of the
"video" group?  And failing that it will be helpful to post your dmesg
and Xorg.log.0 to help triage this.

Cheers,
-pete

[Pete Wright]

Hello Pete, sorry I’m on trip so i cannot output the logs in proper
way. About i915 kernel module please refer to screen shot. 
I can confirm that i915 module is not getting loaded normaly at system
startup, so kldstat shows nothing. 
Yes, the user is already in video group. (Generally didnt changed
anything on system config, just updated pkg and this happend)

thanks for posting the screen shot - it looks like your kernel and world
may not be recent enough to load the kld.  i'd suggest pulling the
latest code from svn or git for 12-CURRENT then removing and
reinstalling the drm-next-kmod pkg after you have booted into this fresh
checkout.

that's the first thing that comes to my mind when seeing that your
kernel is unable to handle these modules.  you also may want to remove
the drm-next-kmod package and ensure there are no artifacts left behind
in /boot/modules/ that were installed via the pkg, then re-install from
the upstream pkg servers.

hope this helps,
-pete

[Hadi Rezaee]

Thanks Pete, i’ll try your solution. But just wanted to report back the
system current revision: r329639

Post by Pete Wright

Hello Pete, sorry I’m on trip so i cannot output the logs in proper
way. About i915 kernel module please refer to screen shot.
I can confirm that i915 module is not getting loaded normaly at system
startup, so kldstat shows nothing.
Yes, the user is already in video group. (Generally didnt changed
anything on system config, just updated pkg and this happend)

thanks for posting the screen shot - it looks like your kernel and world
may not be recent enough to load the kld. i'd suggest pulling the
latest code from svn or git for 12-CURRENT then removing and
reinstalling the drm-next-kmod pkg after you have booted into this fresh
checkout.
that's the first thing that comes to my mind when seeing that your
kernel is unable to handle these modules. you also may want to remove
the drm-next-kmod package and ensure there are no artifacts left behind
in /boot/modules/ that were installed via the pkg, then re-install from
the upstream pkg servers.
hope this helps,
-pete
--
Pete Wright
310.309.9298

[Pete Wright]

Post by Hadi Rezaee
Thanks Pete, i’ll try your solution. But just wanted to report back
the system current revision: r329639

sounds great, let me know how it looks.

i suggest we move the rest of this discussion to the
freebsd-***@freebsd.org list so we don't SPAM the -current list.

cheers!
-pete

[Hadi Rezaee]

Hey Pete,
Thanks for the help, updated to newer revision (r330133) and it resolved
the problem :)

Post by Pete Wright

Post by Hadi Rezaee
Thanks Pete, i’ll try your solution. But just wanted to report back
the system current revision: r329639

sounds great, let me know how it looks.
i suggest we move the rest of this discussion to the
cheers!
-pete
--
Pete Wright
310.309.9298

[Pete Wright]

Hello there,
My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my
graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But now
it getting failed. Tried to build from source, but same result.
Laptop model: Lenovo E470

(removing stable since this is a potential issue on CURRENT)

we'll need more details to help triage and hopefully fix this issue. 
what errors are you seeing?  are you having problems loading the driver,
or is Xorg having issues?

-pete

[Jan Bramkamp]

Hello there,
My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my
graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But
now it getting failed. Tried to build from source, but same result.
Laptop model: Lenovo E470

I just updated both the 12-current base system and the
graphics/drm-next-kmod port on my Thinkpad T470s. The resulting system
works except for the already documented regression in the VA API
affecting hardware accelerated video playback in mpv.