Date: Tue, 28 Jul 2020 20:52:51 +0000 (UTC) From: Kostya Berger <bergerkos@yahoo.co.uk> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: nvidia-driver-390 fails to find screens Message-ID: <74299378.12769233.1595969571331@mail.yahoo.com> References: <74299378.12769233.1595969571331.ref@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Was there any significant change in the base code, so that Nvidia driver su= ddenly can't find usable displays upon the update to r363439 ?Error message= : NVIDIA(GPU-0): Failed to select a display subsystem. =D0=9E=D1=82=D0=BF=D1=80=D0=B0=D0=B2=D0=BB=D0=B5=D0=BD=D0=BE =D0=B8=D0=B7 Y= ahoo =D0=9F=D0=BE=D1=87=D1=82=D1=8B =D0=B4=D0=BB=D1=8F Android From owner-freebsd-current@freebsd.org Wed Jul 29 02:10:48 2020 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 23AB8379AD3; Wed, 29 Jul 2020 02:10:48 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BGcTN08dXz48J2; Wed, 29 Jul 2020 02:10:48 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id DC3A62F193; Wed, 29 Jul 2020 02:10:47 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-lf1-f54.google.com with SMTP id k13so12147050lfo.0; Tue, 28 Jul 2020 19:10:47 -0700 (PDT) X-Gm-Message-State: AOAM530Wa5MbpiJ7n0IVhrPQo9LShY/yyoForlAnch7MXXPqIGv3EPdx nxkSNYBKY7Uo+aLqPVpBnpIAQKJorIbGMIIr6CA= X-Google-Smtp-Source: ABdhPJyWhvSSSw2xQUXvTbic0iYkMxzoa1Spvhmervj0vxambAont5ojg82/jZ/ztPncgQwxHYJGjrVNiZwDkTSVK+8= X-Received: by 2002:a05:6512:14d:: with SMTP id m13mr15980129lfo.173.1595988646167; Tue, 28 Jul 2020 19:10:46 -0700 (PDT) MIME-Version: 1.0 From: Matthew Macy <mmacy@freebsd.org> Date: Tue, 28 Jul 2020 19:10:21 -0700 X-Gmail-Original-Message-ID: <CAPrugNoHssV+yAOBQ8cb4qe7=r53jrcowQ2-T+BB-Zn5HaNJ_g@mail.gmail.com> Message-ID: <CAPrugNoHssV+yAOBQ8cb4qe7=r53jrcowQ2-T+BB-Zn5HaNJ_g@mail.gmail.com> Subject: CFT for vendor openzfs - week 4 reminder + memdisk images To: freebsd-fs <freebsd-fs@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 29 Jul 2020 02:10:48 -0000 On Wednesday, July 8th I issued the initial call for testing for the update to HEAD to vendored openzfs. We'd like to give users roughly a month to test before merging. The tentative merge date is August 17th. Again, I hope it's not terribly controversial to point out that it really rests with users of non amd64 platforms to test to avoid any unpleasant surprises the next time they update their trees following the merge. amd64, i386, and aarch64 memdisk images can be found at: https://people.freebsd.org/~freqlabs/freebsd-openzfs-3d833bea-f10f94aa-2020072900/ If you're using a platform not listed above and would be inclined to test if you had an image to work with, let us know. Alternatively, you can still build following the instructions below. The review for merging in to base can be found at: https://reviews.freebsd.org/D25872 ========================================================== NB: Do NOT zpool upgrade unless you are willing to live without the ability to ever rollback to the legacy zfs kmod. Checkout updated HEAD: % git clone https://github.com/mattmacy/networking.git -b projects/openzfs_vendor freebsd Checkout updated openzfs in to sys/contrib: % git clone https://github.com/zfsonfreebsd/ZoF.git -b projects/openzfs_vendor freebsd/sys/contrib/openzfs Build world and kernel with whatever your usual configuration is. Where possible the openzfs kmod is backward compatible with the cmd utils in HEAD so common operations work with existing tools and the new kmod. In the projects/openzfs_vendor branch of ZoF ozfs libraries are backward compatible with the zfs kmod in HEAD. Although ideally one would test this in a separate boot environment, the interoperability should allow one to rollback without too much difficulty. Thanks in advance for your time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74299378.12769233.1595969571331>