Re: drm changes and updating to 12.0
On Mon, Nov 5, 2018 at 10:18 PM Johannes Lundberg wrote: > > On Mon, Nov 5, 2018 at 10:05 PM Carsten Mattner > wrote: >> >> On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg wrote: >> >> > Which Linux version is tracked is listed in the port info. >> > drm-stable-kmod is currently at Linux 4.9 >> > drm-devel-kmod is currently at Linux 4.16 >> >> This is very useful to know. I can't find the Linux kernel version in >> drm-legacy-kmod metadata. Is it a mix of different kernel releases? > > > According to the old, abandoned wiki page it seems to be Linux 3.8. > (zeising: we should add this info to drm-legacy) > https://wiki.freebsd.org/Graphics > > That was developed by the previous graphics team with all different > members (for the kernel drivers) so to be honest I don't know much > details about the old drm code. Thanks for the info. Older drm releases are more reliable on older chips because the Intel devs don't test on older GPUs as much and have introduced major regressions. For instance, Sandy Bridge only works with 0 issues up until 4.1 and is okay'ish on 4.4.x. It's good to know that the 3.8 code is still there though, in case the 4.9 branch (drm-stable-kmod) has too many regressions. That is, up until the regressions (all reported in freedesktop's bugzilla) are fixed in 4.2x.y (or 5.x), hopefully :). tl;dr: thank you for the choice in drm kmods, it's very useful! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Mon, Nov 5, 2018 at 10:05 PM Carsten Mattner wrote: > On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg > wrote: > > > Which Linux version is tracked is listed in the port info. > > drm-stable-kmod is currently at Linux 4.9 > > drm-devel-kmod is currently at Linux 4.16 > > This is very useful to know. I can't find the Linux kernel version in > drm-legacy-kmod metadata. Is it a mix of different kernel releases? > According to the old, abandoned wiki page it seems to be Linux 3.8. (zeising: we should add this info to drm-legacy) https://wiki.freebsd.org/Graphics That was developed by the previous graphics team with all different members (for the kernel drivers) so to be honest I don't know much details about the old drm code. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg wrote: > Which Linux version is tracked is listed in the port info. > drm-stable-kmod is currently at Linux 4.9 > drm-devel-kmod is currently at Linux 4.16 This is very useful to know. I can't find the Linux kernel version in drm-legacy-kmod metadata. Is it a mix of different kernel releases? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Mon, Nov 05, 2018 at 06:56:57PM +, Johannes Lundberg wrote: > The short version is that drm2 in base (/sys/dev/drm2/) have support for hw > up to 2013 (maybe 2014), that's why drm-legacy-kmod is said to support hw > up to that year. drm2 in base supports everything from gen3 to gen6 and did some entrance into gen7 for Intel. Practically it means that the list is G33 chipset graphics (gen3) G45 (gen4), both cover everything that has chipset graphics for Core2, core i5 6xx AKA desktop Westmere (gen5) Sandy/Ivy Bridge (gen6) unstable Haswell (gen7) (I dropped it when upstream had still major stability issues) Broadwell does not work at all, and I am not sure about Atoms even when the same generation of graphics was used by the north bridge. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Mon, Nov 5, 2018 at 5:27 PM Robert Huff wrote: > > Warner Losh writes: > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > > on the system I am using to send this message. I bought it in 2011, > the > > year Sandy Bridge was introduced to production products. > > > > 2013 is "five year old hardware or newer". It's a number I pulled out > of the > > air when trying to nail down the group in describing who should use > what. > > Giving code names would also work. Sandy Bridge and newer, though, is > confusing > > to people. I'd use 2011 as the release date for Sandy Bridge, but then > what > > about the AMD other GPUs? > > > > If there's a better way to message what's supported, I'm all ears. > > Lacking a better plan: is there a list of which card/gpu is > currently known to work with which drm(-kmod) version, perhaps > gathered from those involved with development? (Is this based on work > from Linux? If so, do they have a list?) > Hi Updating the wiki graphics pages is long overdue and we hope to have it refreshed before the 12.0 release. Everything will be explained there in detail together with some compatibility matrix. This has probably been said many times on the mailing list but I feel obligated to try to inform the best I can until we have updated the wiki. The short version is that drm2 in base (/sys/dev/drm2/) have support for hw up to 2013 (maybe 2014), that's why drm-legacy-kmod is said to support hw up to that year. Now, the linuxkpi based ones, drm-stable-kmod and drm-devel-kmod (I'm not including drm-next-kmod because that will go away), potentially could work on hw older than 2013. Initially they didn't but they have been patched to potentially work on same hw as base drm2 but this is barely tested yet. Recently, drm-devel-kmod was patched to work on i386 but this is also not fully tested yet. So, theoretically, if you're running current, drm-devel-kmod could run your 10 years old 32 bit computer's gpu but it's too early to make any guarantees. Please feel free to test. Usually the meta-port, drm-kmod, will choose the best (safest bet) for your system. Which Linux version is tracked is listed in the port info. drm-stable-kmod is currently at Linux 4.9 drm-devel-kmod is currently at Linux 4.16 The best way is lookup what is supported by the Linux version (if anyone know a good site, please share the link). If the hw is supported there, and it's driven by i915, amdgpu or radeon, it should work on FreeBSD as well. If you have any of the _really_ old cards supported by drm1 (what's in /sys/dev/drm/), you'll always need drm-legacy-kmod. We know this transition has been messy and confusing but we're working hard to improve this. /Johannes > > > Respectfully, > > > Robert Huff > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Mon, Nov 5, 2018 at 10:23 AM Robert Huff wrote: > > Warner Losh writes: > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > > on the system I am using to send this message. I bought it in 2011, > the > > year Sandy Bridge was introduced to production products. > > > > 2013 is "five year old hardware or newer". It's a number I pulled out > of the > > air when trying to nail down the group in describing who should use > what. > > Giving code names would also work. Sandy Bridge and newer, though, is > confusing > > to people. I'd use 2011 as the release date for Sandy Bridge, but then > what > > about the AMD other GPUs? > > > > If there's a better way to message what's supported, I'm all ears. > > Lacking a better plan: is there a list of which card/gpu is > currently known to work with which drm(-kmod) version, perhaps > gathered from those involved with development? (Is this based on work > from Linux? If so, do they have a list?) > I believe that list would be hundreds of entries long. That's not exactly useful to put in release notes except as an appendix. I agree having the list somewhere would be good, but having it in a short statement wouldn't be possible. Even just summarizing the major generations would be too long a list, I'd think. Also, we have no clue which GPUs actually work on FreeBSD and which ones should work. With so many graphics GPUs out there, it's impossible for us to test and keep current on all the reports for all of them. There's no infrastructure to do that that would scale to the size of this problem. While most of them should work, we still need fallback instructions for those people who tried it and it didn't work. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
Warner Losh writes: > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > on the system I am using to send this message. I bought it in 2011, the > year Sandy Bridge was introduced to production products. > > 2013 is "five year old hardware or newer". It's a number I pulled out of the > air when trying to nail down the group in describing who should use what. > Giving code names would also work. Sandy Bridge and newer, though, is > confusing > to people. I'd use 2011 as the release date for Sandy Bridge, but then what > about the AMD other GPUs? > > If there's a better way to message what's supported, I'm all ears. Lacking a better plan: is there a list of which card/gpu is currently known to work with which drm(-kmod) version, perhaps gathered from those involved with development? (Is this based on work from Linux? If so, do they have a list?) Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Sun, Nov 4, 2018 at 10:52 PM Kevin Oberman wrote: > On Sun, Nov 4, 2018 at 12:15 PM Niclas Zeising > wrote: > > > On 11/4/18 8:29 PM, Robert Huff wrote: > > > > > > I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300 > > > gpu) which will be updated from 11. to 12.0 once 12 is out > > > and the initial round of bugs are squashed. > > > One system is being done now, to allow time to catch any major > > > problems and then plan the update process. > > > Looking at src/UPDATING, the only thing I don't understand is the > > > whole drm-kmod change. Is there an authoritative write-up on what's > > > going on, how to choose the right drivers for my hardware, and how to > > > do this from source without forcing a fresh install? > > > > > > > We are working on better documentation for this, but the main highlights > > are: In most cases graphics/drm-kmod should suffice, especially on > > somewhat modern hardware. You can also install any of the drm-*-kmod > > ports directly, if you want a specific version. In general graphics > > hardware older than from 2013 requires drm-legacy-kmod instead. > > drm-kmod will also install drm-legacy-kmod on i386. > > > > The same drivers in drm-legacy-kmod is also available in base on 12, so > > you can use the base drivers. This is deprecated however, and not the > > case for 13-CURRENT. > > > > You can install the drivers either from pkg, if you are using the > > GENERIC kernel, or build from ports if you have a customized kernel or > > if you are tracking for instance 12-STABLE or 13-CURRENT. > > > > If you are using drm-legacy-kmod or the base driver with AMD graphics > > cards you might also need to install xf86-video-ati-legacy rather than > > xf86-video-ati. > > > > Regards > > -- > > Niclas Zeising > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge graphics > is supported with VAAPI acceleration by drm-stable-kmod, since it i working > on the system I am using to send this message. I bought it in 2011, the > year Sandy Bridge was introduced to production products. > > In general, when in doubt, I'd try drm-stable-kmod for questionable devices > and fall back to drm-legacy-kmod it it fails. If y0ou use ports, I'd build > both paskages to make it easier to recover if drm-stable-kmod fails. Also, > be sure to make the proper adjustments to /etc/rc.conf as per the package > message. > 2013 is "five year old hardware or newer". It's a number I pulled out of the air when trying to nail down the group in describing who should use what. Giving code names would also work. Sandy Bridge and newer, though, is confusing to people. I'd use 2011 as the release date for Sandy Bridge, but then what about the AMD other GPUs? If there's a better way to message what's supported, I'm all ears. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On Sun, Nov 4, 2018 at 12:15 PM Niclas Zeising wrote: > On 11/4/18 8:29 PM, Robert Huff wrote: > > > > I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300 > > gpu) which will be updated from 11. to 12.0 once 12 is out > > and the initial round of bugs are squashed. > > One system is being done now, to allow time to catch any major > > problems and then plan the update process. > > Looking at src/UPDATING, the only thing I don't understand is the > > whole drm-kmod change. Is there an authoritative write-up on what's > > going on, how to choose the right drivers for my hardware, and how to > > do this from source without forcing a fresh install? > > > > We are working on better documentation for this, but the main highlights > are: In most cases graphics/drm-kmod should suffice, especially on > somewhat modern hardware. You can also install any of the drm-*-kmod > ports directly, if you want a specific version. In general graphics > hardware older than from 2013 requires drm-legacy-kmod instead. > drm-kmod will also install drm-legacy-kmod on i386. > > The same drivers in drm-legacy-kmod is also available in base on 12, so > you can use the base drivers. This is deprecated however, and not the > case for 13-CURRENT. > > You can install the drivers either from pkg, if you are using the > GENERIC kernel, or build from ports if you have a customized kernel or > if you are tracking for instance 12-STABLE or 13-CURRENT. > > If you are using drm-legacy-kmod or the base driver with AMD graphics > cards you might also need to install xf86-video-ati-legacy rather than > xf86-video-ati. > > Regards > -- > Niclas Zeising I'm curious where 2013 comes from. I know that Intel Sandy Bridge graphics is supported with VAAPI acceleration by drm-stable-kmod, since it i working on the system I am using to send this message. I bought it in 2011, the year Sandy Bridge was introduced to production products. In general, when in doubt, I'd try drm-stable-kmod for questionable devices and fall back to drm-legacy-kmod it it fails. If y0ou use ports, I'd build both paskages to make it easier to recover if drm-stable-kmod fails. Also, be sure to make the proper adjustments to /etc/rc.conf as per the package message. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm changes and updating to 12.0
On 11/4/18 8:29 PM, Robert Huff wrote: I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300 gpu) which will be updated from 11. to 12.0 once 12 is out and the initial round of bugs are squashed. One system is being done now, to allow time to catch any major problems and then plan the update process. Looking at src/UPDATING, the only thing I don't understand is the whole drm-kmod change. Is there an authoritative write-up on what's going on, how to choose the right drivers for my hardware, and how to do this from source without forcing a fresh install? We are working on better documentation for this, but the main highlights are: In most cases graphics/drm-kmod should suffice, especially on somewhat modern hardware. You can also install any of the drm-*-kmod ports directly, if you want a specific version. In general graphics hardware older than from 2013 requires drm-legacy-kmod instead. drm-kmod will also install drm-legacy-kmod on i386. The same drivers in drm-legacy-kmod is also available in base on 12, so you can use the base drivers. This is deprecated however, and not the case for 13-CURRENT. You can install the drivers either from pkg, if you are using the GENERIC kernel, or build from ports if you have a customized kernel or if you are tracking for instance 12-STABLE or 13-CURRENT. If you are using drm-legacy-kmod or the base driver with AMD graphics cards you might also need to install xf86-video-ati-legacy rather than xf86-video-ati. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
