Date: Sat, 20 Jul 2019 11:50:18 +0300 From: Greg V <greg@unrelenting.technology> To: freebsd-current@freebsd.org,Evilham <contact@evilham.com> Subject: Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485 Message-ID: <405A85A9-1076-4D68-BB85-45D5062BED15@unrelenting.technology> In-Reply-To: <3b186187-c9f6-46d2-939a-eceb6fa0359c@yggdrasil.evilham.com> References: <CAG%2B4yk=DU9o=5oEaFgZ91pufwyUtY9wH1AAhsqG-RhTkB3Zsug@mail.gmail.com> <3b186187-c9f6-46d2-939a-eceb6fa0359c@yggdrasil.evilham.com>
index | next in thread | previous in thread | raw e-mail
On July 20, 2019 1:54:47 AM GMT+03:00, Evilham <contact@evilham.com> wrote: > it even suspends and resumes back to X Wow, that's great news! Desktop Ryzen+Vega doesn't (not that I need suspend very much on desktop haha) >- xbacklight doesn't work, neither does intel-backlight because > it's AMD Since it's a Thinkpad, do the brightness keys work anyway? Does acpi_ibm work? >Serious issue: >I was just debugging this right now, more infos with a proper bug >report will come, but I think the system encounters a deadlock >sometimes with the drm-kmod / amdgpu which results in a kernel >panic. If you're on the packaged drm-kmod v4.16, it's amazing that Raven GPU works at all. You should try drm-v5.0 from git. >kld_list="amdgpu" It even works when loaded this early? Interesting. Do you also not have the EFI framebuffer conflict? i.e. without disabling vt.syscons, everything just works reliably?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?405A85A9-1076-4D68-BB85-45D5062BED15>