From owner-freebsd-current@freebsd.org Mon Mar 18 20:06:45 2019 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 20EBE154C92D for ; Mon, 18 Mar 2019 20:06:45 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57A44745CC for ; Mon, 18 Mar 2019 20:06:44 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-ot1-x334.google.com with SMTP id c16so4212507otn.4 for ; Mon, 18 Mar 2019 13:06:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tC24jGGwaFklM6y1GyG5RjjXMHXgTIfbGDU25pHpU9I=; b=cde+xabBUYX4h3f/sxPEQdA5mQCw8F58EuuqdpWNWVU291owikRTmZVwAIgyNic9Dl 3/MEJaMTEMdaiSDI7hb2J/ik85VO3ToLXZzeytJDpFcphragDv8BuX0z+U5x1M2rgBOG uN9umO3XdsamvVdiySZmAnXfJzNwR/apIUEN1PLCjHsWoM2bgkit0MjGwBhB+Unx1Mlu FT5P2va0MMJDx8pFw4uw2sjoYnzAKJ5gwf2ZqKYjokjHOYbEhp7yCBQB6e9otk+XfkOm z43sGitzoPjmRBdStsqfJrGmVvdvm9GVt3fMiGRt1MAg9IdcJcMU3gQQTV+XL0vNdJhw YFPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tC24jGGwaFklM6y1GyG5RjjXMHXgTIfbGDU25pHpU9I=; b=GRgeGuDSn3lzWdLGyhmtahnkWpWxPLakYBi8x4W5unMCpNKMTvo3EUN/hmT8XDhbl3 sE3NWPgqzIwGn3T28Tiwk0NgI4YCnB1hgsF0q1cl+z16slOmzWp4jkKLkLJB0+Zbm+Sq FUFop8c4nunpWb2Ab6ZpZU90GtiEdcvydnxhL70uc4y2sheBuc4W/q5SfcuPX/3NcnlY 3G8Cs2yaMqnNnPUkCA1FmQVxWAKO6MyxbAhVGkYGB1G/cjcEVIE17jybCYzYKO/yJYp/ YIrkvjWfDmyAJ+XplPqfD6RYz/d68a91mUVhEXGzOncSWquEE1ffBoB3JsVT6BpR0Inm mLCQ== X-Gm-Message-State: APjAAAW+aMvbpq1Q/ogo1AXPHH2STH8Yk1nGVst45IQ1IpLvPofXEe6z AKVN7AnjxPVu8JF8hKVrxcmbh+I7dJ17c0rS2zhNmg== X-Google-Smtp-Source: APXvYqxDew71wjeQPkU2LirInk5KCKIvSrDroUZcIb2QvE5V9mI3bGsUAoi7rwt6bW66V9tZozYzlaqelLlOXXT0vvs= X-Received: by 2002:a9d:6b94:: with SMTP id b20mr3820298otq.289.1552939603770; Mon, 18 Mar 2019 13:06:43 -0700 (PDT) MIME-Version: 1.0 References: <95dfadc9-8341-b2a5-7b58-e94f46b5fa90@gmail.com> <1552836887.1930.0@unrelenting.technology> <6ea64218-2b6d-fc9a-01b5-ed07bd23c783@gmail.com> <20190317223531.b7334327a47f3579eaba98ee@bidouilliste.com> In-Reply-To: From: Johannes Lundberg Date: Mon, 18 Mar 2019 20:06:33 +0000 Message-ID: Subject: Re: Switching fb backend back to default To: Oliver Pinter Cc: Emmanuel Vadot , FreeBSD Current , Greg V X-Rspamd-Queue-Id: 57A44745CC X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cde+xabB; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johalun0@gmail.com designates 2607:f8b0:4864:20::334 as permitted sender) smtp.mailfrom=johalun0@gmail.com X-Spamd-Result: default: False [-6.63 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[4.3.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-0.89)[-0.895,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.73)[ip: (-8.72), ipnet: 2607:f8b0::/32(-2.76), asn: 15169(-2.09), country: US(-0.07)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 18 Mar 2019 20:06:45 -0000 On Mon, Mar 18, 2019 at 19:48 Oliver Pinter wrote: > > > On Sunday, March 17, 2019, Johannes Lundberg wrote: > >> On Sun, Mar 17, 2019 at 21:35 Emmanuel Vadot >> wrote: >> >> > On Sun, 17 Mar 2019 16:32:43 +0000 >> > Johannes Lundberg wrote: >> > >> > > >> > > On 3/17/19 3:34 PM, Greg V wrote: >> > > > >> > > > >> > > > On Sun, Mar 17, 2019 at 3:07 PM, Johannes Lundberg >> > > > wrote: >> > > >> Hi >> > > >> >> > > >> I'm working on making i915kms unload properly. I've come to what = I >> > think >> > > >> is the last issue. The drm driver unloads ok, the "efifb" backend >> is >> > > >> restored (according to logs) and vt_efifb_init() is being called >> but >> > the >> > > >> screen (laptop built in display) stays black. The system seems >> > > >> operational otherwise. If I load i915kms again in this state I ge= t >> > back >> > > >> a visible (i915kms) framebuffer. >> > > >> >> > > >> Did we ever have this working so it's known to work? >> > > > >> > > > Recently on the linux kernel mailing list: >> > > > >> > > > http://lkml.iu.edu/hypermail/linux/kernel/1903.1/01162.html >> > > > >> > > > > Of course, once native drivers like i915 or radeon take over, >> such a >> > > > framebuffer is toast... [6] >> > > > >> > > > > [6] >> > linux/drivers/gpu/drm/i915/i915_drv.c::i915_kick_out_firmware_fb() >> > > > > linux/drivers/gpu/drm/radeon/radeon_drv.c::radeon_pci_probe() >> > > > >> > > > So it seems like efifb is not supposed to work after a driver has >> been >> > > > loaded at least once. >> > > > >> > > > >> > > Hmm, well the code is there to handle switching back to the boot tim= e >> > > fb. What I think is happening is that i915 powers off the displays a= t >> > > unload and vt doesn't know how to power on (or that it should). >> > > >> > >> > That and if the display pipeline is de-configured or the resolution >> > changed you cannot reset it to the original state. >> > Unloading drm modules is only useful for testing (and finding leaks). >> >> >> Yeah a normal user would never unload it. Since I mostly ssh to my test >> machines I think I=E2=80=99m fine personally with losing the display whi= le >> unloading. >> >> Keyboard input still works though and at least it doesn=E2=80=99t crash = anymore :) > > > > As workaround, can't you turn on the display with intel_backlight? > AFAIK, that can only adjust brightness. The display panel is completely shut off. >> >> > >> > > >> > > _______________________________________________ >> > > freebsd-current@freebsd.org mailing list >> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > > To unsubscribe, send any mail to " >> > freebsd-current-unsubscribe@freebsd.org" >> > >> > >> > -- >> > Emmanuel Vadot >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> >