Date: Mon, 13 Apr 2020 09:29:05 +0200 From: Niclas Zeising <zeising@freebsd.org> To: Andrea Venturoli <ml@netfence.it>, x11@FreeBSD.org Subject: Re: Users of x11-drivers/xf86-video-ati-legacy Message-ID: <9352b468-9f09-ad30-0b9e-acd896cadb17@freebsd.org> In-Reply-To: <c36ed3ba-1aad-ad70-1f90-1fa1f9370b59@netfence.it> References: <ef0ba8bc-e029-1918-5747-941fd9a3f2ae@freebsd.org> <16c93a1a-cc60-b9a5-da48-889f48aa6005@netfence.it> <d1133d52-0edd-aeae-afc0-32c4339c99b0@netfence.it> <c36ed3ba-1aad-ad70-1f90-1fa1f9370b59@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-04-12 17:21, Andrea Venturoli wrote: > On 2020-04-12 09:54, Andrea Venturoli wrote: >> On 2020-04-11 16:43, Andrea Venturoli wrote: >> >> Some more info as I investigate: >=20 > I tried some debugging and what I think is happening is that the root=20 > windows get created and painted black (through pixman, with SSE=20 > instructions). > However at about 300kB into the buffer (which should be around 900kB)=20 > that segfaults. > Is it possible that the memory is allocated wrong/in the wrong place? >=20 > I went into the BIOS: I can choose to use the GPU's own memory, memory=20 > shared from main RAM or both. Also if memory should be mapped below or=20 > above 4G. > Those settings do not seem to make any difference, however. >=20 >=20 > The above is with drm-kmod-legacy (or drm from base). >=20 > xf86-video-ati-legacy seems to work with drm-fbsd12.0-kmod, instead=20 > (which, OTOH gives different problems). Hi! Thank you for helping out and testing, unfortunately there is not much=20 to do if it does not work. I don't have the time or hardware to get an=20 older xf86-video-ati to maybe build with xserver 1.20. The reason xf86-video-ati-legacy works with drm-fbsd12.0-kmod is that=20 the updated kmod uses newer APIs etc. At one point, xf86-video-ati was=20 updated to make these work, and when we updated xf86-video-ati in ports=20 to the latest version to get support for more modern hardware,we had to=20 create xf86-video-ati-legacy for use with drm-legacy-kmod. This was=20 always one of those stop-gap measures. >=20 >=20 >=20 > To recap the various combinations. >=20 > With X.Org 1.19.6 + drm from base + xf86-video-ati-legacy everything=20 > worked fine. Yes, because the things that ati-legacy uses that caused it to break was=20 changed between xserver 1.19 and 1.20. >=20 > Now on to 1.20.8, drm from base or drm-kmod-legacy +=20 > xf86-video-ati-legacy: I get a crash. >=20 > Moving to drm-fbsd12.0-kmod, I completely lose HDMI output and DVI=20 > output doesn't work properly (screen flashes continuously, unless I=20 > reduce full resolution): I have to use VGA output (sigh). >=20 > I also tried xf86-video-ati (non legacy): everything seems the same,=20 > except the machine will sometimes hang. > (I have not experienced an hang *yet* with xf86-video-ati, but it's bee= n=20 > to short a time to conclude anything). Is this with drm-kmod or drm-legacy-kmod? >=20 >=20 >=20 > So I guess your patch works, at least in some cases. It's possible the=20 > problems I'm having are not due to xf86-video-ati-legacy, but to some=20 > other component. >=20 > =C2=A0bye & Thanks > =C2=A0=C2=A0=C2=A0=C2=A0av. Regards --=20 Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9352b468-9f09-ad30-0b9e-acd896cadb17>