From owner-freebsd-current@freebsd.org Sat Oct 6 05:14:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38FC410C7616 for ; Sat, 6 Oct 2018 05:14:48 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EDDB82A6B for ; Sat, 6 Oct 2018 05:14:47 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x42b.google.com with SMTP id 63-v6so15412785wra.11 for ; Fri, 05 Oct 2018 22:14:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=5L7xOarly9gYKaK5ioTS1s02c3iCW86oQPI88NxPMRg=; b=KiPbIsXEWU2H5T0iaKnas04HATFji3krkldEKx8m+8RRaC43o4emh5KKBjdj1EJC1o fk2Gv5WKkIaqbOBXiltGBdlqmRKKRoBBvdShE6mwi3bkAei4UdhnGlA8seLf/5zmXptO PUGhVSoaSBLOSQGakD8Oxv6+jrXIsOwQLlvT6voV3lVLqhgi0zJHIECaObvBIvhCM0ZB Zn2LDZasc9VOOYxuXerw61yAp9xgwvxfThb+28yLc0Eee+VKYLyurSn7obiIAGtOBwsP KrjNCvqy9ysHpC+L6BOcOMl9t2bIY0Q8mbfDb+/YQimbiXJln0pPBQjO29yIeECVukFr gIFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=5L7xOarly9gYKaK5ioTS1s02c3iCW86oQPI88NxPMRg=; b=W09wEPCDk/1F1pE3GwGNsyirHXAHhTNTM1plnlqXKnMR2TK/128vYkRCQShRcAHQLk 8O8jQoSIm/en/WbJz51IO7zd+m6IgNU4zyLZcttwSmhhjyJCo5nAkOi3mIRlDNMqxqW3 clvxEiXsi4EoiryA4HiveXCw4f8NfDysgGGEsPEJvFlALqVE0tY5fnrojS6m424ak4qq QVehDPJXH+APxgTfP+3HmK020Mdoc+Atd2OMPFE1mAUedke8i/nD9qJHUoEoMCVfzJEH sDKjaSV/26NdM2zuA2+k+MNEwgel+mzdFJjAS/3AdDBv24NHU5Z9pY+VJkvl294VsCf/ SzpA== X-Gm-Message-State: ABuFfojo9RxeP7lKekc9+5zaR673pI5Zo2Lbw/C5BfP/9cli6v3mWeeW PkjqBAqH0nhrpNOjErT1C4VN5MR8 X-Google-Smtp-Source: ACcGV63AOaivWoR8SJ+uLMIilnIygpJ3JtpHuyaucnl81CZAqWzQQj2lb91kN6Ruc7RNwDhVEg+DsQ== X-Received: by 2002:adf:ade3:: with SMTP id w90-v6mr10071591wrc.73.1538802885224; Fri, 05 Oct 2018 22:14:45 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id p62-v6sm19766884wrc.97.2018.10.05.22.14.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Oct 2018 22:14:43 -0700 (PDT) Subject: Radeon HD 7570M: drm: deep frustration with r339186 To: freebsd-current References: <93fcf295-1dae-12d4-5530-ef0c55bd8cc2@gmail.com> <0aa72278-c17b-0bd7-1f5b-960366890426@nomadlogic.org> <549ab380-60a8-c919-980a-b5b6a541e3c9@gmail.com> <38395f26-faa5-e56e-6a4c-3e72fbfc2a73@gmail.com> <88d6b0fc-7843-4cb0-dd05-99daf463794e@gmail.com> <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org> From: Graham Perrin Message-ID: Date: Sat, 6 Oct 2018 06:14:41 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2018 05:14:48 -0000 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 . Also followed 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 …