From owner-freebsd-current@freebsd.org Sun Mar 17 21:35: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 7B2AD154B9A3 for ; Sun, 17 Mar 2019 21:35:45 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CC75A922C8 for ; Sun, 17 Mar 2019 21:35:43 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 93c63a1e; Sun, 17 Mar 2019 22:35:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=XHE5rX+ED5IGLpRH3Et1WYgvSxc=; b=okhwUvBrscYCupM0IhZou+MjO3ll tjvYdcs2XExkj3diMJaBVeCqfHMS8zpqcH51k2TAYd68ZATnPekrUVWwQnPKy5tX y1yYd68SgbrhLDP3EBZD7jws7mq0d2MYVUJ49iUOmzuknLqBWNBg0pySzxm6u5iT efbA9qcKQ1mxGGQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=W6OwQerbRXp9hJqJhWMzTMLGtOWSba+UglCCxZKAzhQTZ1CA1+AcNFr3 UdBEZWLDsTH8n8BRJ1aPkJhntWXtSzjcr/efV0zng/YedMQAkFyxaIvYYStDlnwC GwoNyI9ckTYW7kopbcLvWmBiGMDcQti29brQWwancgD8XeY2RWQ= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 3a16cb8e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 17 Mar 2019 22:35:34 +0100 (CET) Date: Sun, 17 Mar 2019 22:35:31 +0100 From: Emmanuel Vadot To: Johannes Lundberg Cc: Greg V , FreeBSD Current Subject: Re: Switching fb backend back to default Message-Id: <20190317223531.b7334327a47f3579eaba98ee@bidouilliste.com> In-Reply-To: <6ea64218-2b6d-fc9a-01b5-ed07bd23c783@gmail.com> References: <95dfadc9-8341-b2a5-7b58-e94f46b5fa90@gmail.com> <1552836887.1930.0@unrelenting.technology> <6ea64218-2b6d-fc9a-01b5-ed07bd23c783@gmail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: CC75A922C8 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=okhwUvBr; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-0.50 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.53)[-0.533,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.81)[-0.814,0]; NEURAL_SPAM_SHORT(0.38)[0.383,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; MX_GOOD(-0.01)[mx-backup.blih.net,mail.blih.net]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.37)[ip: (-1.13), ipnet: 212.83.160.0/19(3.24), asn: 12876(-0.24), country: FR(-0.01)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Sun, 17 Mar 2019 21:35:45 -0000 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 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, 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 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). > > _______________________________________________ > 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