Date: Sat, 6 Oct 2018 06:14:41 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: Radeon HD 7570M: drm: deep frustration with r339186 Message-ID: <f3d4196b-673e-ffcd-391f-675a5ea9feda@gmail.com> In-Reply-To: <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org> References: <93fcf295-1dae-12d4-5530-ef0c55bd8cc2@gmail.com> <0aa72278-c17b-0bd7-1f5b-960366890426@nomadlogic.org> <549ab380-60a8-c919-980a-b5b6a541e3c9@gmail.com> <CAECmPwv7C5=KCiE-7c%2B2TDPOTddSVY7AadME%2BMmVZHMJ58YJ%2Bw@mail.gmail.com> <38395f26-faa5-e56e-6a4c-3e72fbfc2a73@gmail.com> <88d6b0fc-7843-4cb0-dd05-99daf463794e@gmail.com> <afb4bc38-a9ad-2f62-0ac1-704dfefbd475@gmail.com> <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/10/2018 04:16, Pete Wright wrote: > > On 10/5/18 6:34 PM, Graham Perrin wrote: >> On 23/09/2018 08:09, Graham Perrin wrote: >> >>> Re: Suspend, resume, UEFI, CSM, drm-stable-kmod and drm-next-kmod with Radeon HD 7570M >>> … better without drm-next-kmod; and (as expected, given the package message) drm-stable-kmod has known problems with UEFI. >> Now (with r339186) it seems that drm-next-kmod is the only usable option. >> >> However, I'm sorry to say: >> >> - it does feel regressive, compared to working without drm-next-kmod with earlier versions of -CURRENT. >> >> I can no longer find a way to reliably suspend (sleep) the notebook. > > hey Graham - I'm struggling with suspend/resume issues as well on my end with recent 12-ALPHA releases. Thanks, I followed threads such as <https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071408.html>. Also followed <https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070831.html>; for drm / drm2 removal in 12, so I was prepared for some worsening, but unprepared for the current situation. > can you verify that you can suspend/resume without loading the radeonkms.ko … I can not verify, sorry folks. My sense of things earlier this morning: - without a load of radeonkms.ko it is impossible to get a (visible, multi-user) command line – and so, it's impossible to proceed to manually load any additional module. > what was the last version of CURRENT you were able to suspend/resume with? r339174, as far as I can tell. That, with care to use _neither_ drm-stable-kmod _nor_ drm-next_kmod. > i believe johannes lundberg is working on a fix for this issue. Hurrah :-) If it helps to diagnose the underlying cause(s): at one point this morning I'm almost certain that I found myself - with drm-next-kmod without an installation of drm-kmod – and I could not understand how that occurred, because a little earlier it seemed that drm-next-kmod depends upon drm-kmod. ---- Installation of drm-stable-kmod requires removal of drm-kmod. True? (I assume that drm-stable-kmod is still unstable with UEFI for my hardware, but I thought it worth trying.) Thanks, and I might hand around in IRC …
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3d4196b-673e-ffcd-391f-675a5ea9feda>