Date: Tue, 26 Jan 2021 13:55:38 +0100 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: Toomas Soome <tsoome@me.com> Cc: Graham Perrin <grahamperrin@gmail.com>, freebsd-current@freebsd.org Subject: Re: DRM and Radeon Message-ID: <aca2ad21-af08-3b34-bb59-7aa57de6df21@plan-b.pwste.edu.pl> In-Reply-To: <5DFFA1C6-EBC3-4C22-B678-45BA48C9ECF1@me.com> References: <24590.137.690675.515036@jerusalem.litteratus.org> <68acb1a8-fcf8-a065-70d5-061669e2f70b@daemonic.se> <24591.35500.33066.12845@jerusalem.litteratus.org> <20210126070211.GB43439@FreeBSD.org> <fd462bcf-d631-9034-88d2-727c7ecc9e8e@gmail.com> <4933479c-b5a6-fa2e-09be-f5a0190d6f1b@plan-b.pwste.edu.pl> <5DFFA1C6-EBC3-4C22-B678-45BA48C9ECF1@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 26.01.2021 o=C2=A010:15, Toomas Soome pisze: > > >> On 26. Jan 2021, at 10:18, Marek Zarychta=20 >> <zarychtam@plan-b.pwste.edu.pl=20 >> <mailto:zarychtam@plan-b.pwste.edu.pl>> wrote: >> >> W dniu 26.01.2021 o=C2=A008:58, Graham Perrin pisze: >>> On 26/01/2021 07:02, Alexey Dokuchaev wrote: >>> > Re: loading drm crashes system >>> > =E2=80=A6 There are known issues with Radeon cards, they were quite= well >>> > supported a year ago, then something got broken. I've promised to >>> > bisect this and find the cause, but there were several >>> > syscall-related changes in -CURRENT though the course of the last >>> > year, so bisecting just the kernel is not enough (machine won't get= >>> > to login prompt if the userland does not match), which cripples the= >>> > process. >>> > >>> > I still intend to take this quest, just not sure when. :( >>> > >>> > ./danfe >>> Any cards in particular? >>> <https://old.reddit.com/r/freebsd/comments/kyoxmc/freebsd_quarterly_s= tatus_report_fourth_quarter/gjiw3y3/=20 >>> <https://old.reddit.com/r/freebsd/comments/kyoxmc/freebsd_quarterly_s= tatus_report_fourth_quarter/gjiw3y3/>>=20 >>> =E2=80=93 whilst I didn't mention Radeon there, for me it _was_ the R= adeon=20 >>> story that seemed to improve a few months ago. >>> <https://bsd-hardware.info/?id=3Dpci:1002-6841-103c-17a9=20 >>> <https://bsd-hardware.info/?id=3Dpci:1002-6841-103c-17a9>>; AMD Thames= =20 >>> [Radeon HD 7550M/7570M/7650M] >> >> >> >> For example old RS880 [Radeon HD 4200]. After deprecation of=20 >> graphics/drm-fbsd12.0-kmod I found that it is still supported fine on = >> 12-STABLE with legacy /boot/kernel/radeonkms.ko from the base. While=20 >> trying the driver from graphics/drm-fbsd12.0-kmod I was not able to=20 >> use this card with gdm, only startx or x11/slim worked. On 13-ALPHA=20 >> this card still works fine with deprecated graphics/drm-legacy-kmod. >> >> > > Does X11 cliegdm start X in specific way? I mean, afaik, gdm is nt as=20 > any other, so the question would be, how does gdm get Xorg started,=20 > what is different compared to startx etc? Might it be about gdm user=20 > permissions to access drm devices? > > my 2cents.. > toomas Thanks for the clue, I added user gdm to the group video, but nothing=20 changed. Gdm starts, after some delay, but there is no visible username/ password = prompt or it's beyond the viewable area, on the other hand, the viewable = area seems to fit the screen correctly. To start gdm I have to wait a=20 while until something happens with the resolution of text in the=20 console. I have to mention that with this driver, the vty console=20 resolution changes a while after loading the driver and starting all=20 services (usually it lasts one minute or less after services startup)=20 and after this time the text on vty can be seen in a kind of window=20 covering: on first monitor 50% of the screen in left upper corner and on = the second monitor, the viewable area of text console exceeds screen=20 dimensions, but on both the text in console looks blurry. Please don't get it wrong it's nether=C2=A0 EFI nor boot loader problem s= ince=20 this is an old machine with BIOS only and I am booting FreeBSD on this=20 with GRUB2 (booting, not chainloading). With /boot/kernel/radeonkms.ko=20 or radeonks.ko from deprecated graphics/drm-legacy-kmod everything looks = fine on vty on both monitors and login and password prompt for gdm=20 appears correctly. So this is not only gdm issue. I have tested drm-current-kmod with fresh 14-CURRENT sources and indeed, = it panicked for me. I have installed deprecated drm-legacy-kmod and it=20 works fine with this old HW and 14-CURRENT. While writing this post I am using: FreeBSD 14.0-CURRENT #3 main-c256281-g25cdacf79b0 drm-legacy-kmod-g20200825 gpu-firmware-kmod-g20201213 --=20 Marek Zarychta
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aca2ad21-af08-3b34-bb59-7aa57de6df21>