From owner-freebsd-current@freebsd.org Mon Mar 18 19:48:36 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 077F4154C001 for ; Mon, 18 Mar 2019 19:48:36 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw1-xc34.google.com (mail-yw1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (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 B5BFE73258 for ; Mon, 18 Mar 2019 19:48:34 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw1-xc34.google.com with SMTP id j66so13920911ywc.10 for ; Mon, 18 Mar 2019 12:48:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HHN1a/vCrEiE6Xyu8lBlY3LECzIGrSSXAKeebvJ4lN8=; b=QuwOUqRyijCRszC4umQ+ofw/fM9DBqDXlvhoJ9G30eyUOTk0YV0uPjDApdO9IseaKJ 6sfg0uqiFylJvUBLik3B3HV7suclIR4hayWhHz2X4MMFEACrhI1/L9oobYcrQCOsDYMS rvVu03DY+JuFpN9ZUoJBErqps0z2POfo6su2c4CsUS7Ib8a3Q9/fVGEQZMiEf7mX4FVU r1ThQJePI63PSOfI4+Mmpvy8HYLVnMsU+jk9PHFw8MFJhB+kwlpxMgTNSO2ONTDarkWj jwrJnKlGW2qkQnLVnnkfsiS6SkHOjiaM16rYDmpkwMQyNHW6F8t3bacVXqsLgN4rwEjQ yi5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HHN1a/vCrEiE6Xyu8lBlY3LECzIGrSSXAKeebvJ4lN8=; b=d+cQ/J2mb0crljHzAwml4Txl6qXc4Y4vbVj6GY5PYfr5UHtmv3E/Vd9UVetD/TPrdy tbcJY4HZz5KxAHxScHidL9g/WUPcqKgupStW7RHm6RACVKFHGK/U8Rs+pWlqdhMztJjM yGZufUwissCDVOkFjnWht3vpgsWztgTasjoEdiwMJLxKL4vrmtTRLQ3/InOUBJP3qIe2 cIUNByIE7lp7dSaruiJtyncBn2KUAljxVxGLf6IkglFJjrj2KmES3pELU5/tr+vmKXBl HNsk7T5crPdmiQqrMpKO0NQes8NXScgcuqyau678S14jVulbcrNw1ItKqe1F+0JSI6Zd VRww== X-Gm-Message-State: APjAAAX+Vix1CPMJ8PCvsOeXaQ7YHqAq5p1flpmx41XNIGVsJWpZNAnN JX6brkIfUlsSoSXIrvEYTcJDMMBQg/xnWWnpjOcqoA== X-Google-Smtp-Source: APXvYqx9Uk1iI80SNMKP+reuubJe89ip8AeLd8pZUlTFZ98rBNOsBKOdvCbI6IhBCR6gbEybG0IlayGfP419SeNU/3E= X-Received: by 2002:a25:af8a:: with SMTP id g10mr15972685ybh.486.1552938513653; Mon, 18 Mar 2019 12:48:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a5b:b0e:0:0:0:0:0 with HTTP; Mon, 18 Mar 2019 12:48:33 -0700 (PDT) In-Reply-To: References: <95dfadc9-8341-b2a5-7b58-e94f46b5fa90@gmail.com> <1552836887.1930.0@unrelenting.technology> <6ea64218-2b6d-fc9a-01b5-ed07bd23c783@gmail.com> <20190317223531.b7334327a47f3579eaba98ee@bidouilliste.com> From: Oliver Pinter Date: Mon, 18 Mar 2019 20:48:33 +0100 Message-ID: Subject: Re: Switching fb backend back to default To: Johannes Lundberg Cc: Emmanuel Vadot , FreeBSD Current , Greg V X-Rspamd-Queue-Id: B5BFE73258 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hardenedbsd.org header.s=google header.b=QuwOUqRy; spf=pass (mx1.freebsd.org: domain of oliver.pinter@hardenedbsd.org designates 2607:f8b0:4864:20::c34 as permitted sender) smtp.mailfrom=oliver.pinter@hardenedbsd.org X-Spamd-Result: default: False [-5.97 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[hardenedbsd.org:s=google]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[hardenedbsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[hardenedbsd.org:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; RCVD_IN_DNSWL_NONE(0.00)[4.3.c.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]; NEURAL_HAM_SHORT(-0.90)[-0.900,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; IP_SCORE(-2.56)[ip: (-7.90), ipnet: 2607:f8b0::/32(-2.76), asn: 15169(-2.09), country: US(-0.07)] 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 19:48:36 -0000 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 b= ut > > the > > > >> screen (laptop built in display) stays black. The system seems > > > >> operational otherwise. If I load i915kms again in this state I get > > 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, suc= h > 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 time > > > fb. What I think is happening is that i915 powers off the displays at > > > 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 whil= e > unloading. > > Keyboard input still works though and at least it doesn=E2=80=99t crash a= nymore :) As workaround, can't you turn on the display with intel_backlight? > > > > > > > > > > _______________________________________________ > > > 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.org= " >