From nobody Sat Oct 16 21:24:56 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 10BDE1801B2A for ; Sat, 16 Oct 2021 21:25:10 +0000 (UTC) (envelope-from carlj@peak.org) Received: from smtp.email-protect.gosecure.net (smtp.email-protect.gosecure.net [208.80.203.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.email-protect.gosecure.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HWx4N6j1kz3FLV for ; Sat, 16 Oct 2021 21:25:08 +0000 (UTC) (envelope-from carlj@peak.org) Received: from envoy14.neonova.net ([137.118.58.100]) by smtp.email-protect.gosecure.net ({770115aa-f1b1-11eb-87ca-11230400d9b0}) via TCP (outbound) with ESMTP id 20211016212501434_00003548 for ; Sat, 16 Oct 2021 14:25:01 -0700 X-RC-FROM: X-RC-RCPT: Received: from bay.localnet (unknown [199.58.99.76]) (Authenticated sender: carlj@peak.org) by envoy14.neonova.net (Postfix) with ESMTPA id 4HWx493WxFz9tLP for ; Sat, 16 Oct 2021 17:24:57 -0400 (EDT) Received: from carlj by bay.localnet with local (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1mbrAm-0005lo-75 for freebsd-arm@freebsd.org; Sat, 16 Oct 2021 14:24:56 -0700 From: Carl Johnson To: freebsd-arm@freebsd.org Subject: Re: X11 on Pi 4 References: Date: Sat, 16 Oct 2021 14:24:56 -0700 In-Reply-To: (Bernd Walter's message of "Sat, 16 Oct 2021 22:04:03 +0200") Message-ID: <86r1ckbr2v.fsf@bay.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (berkeley-unix) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-MAG-OUTBOUND: greymail.email-protect.gosecure.net@137.118.58.100/32 X-Rspamd-Queue-Id: 4HWx4N6j1kz3FLV X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=peak.org; spf=pass (mx1.freebsd.org: domain of carlj@peak.org designates 208.80.203.2 as permitted sender) smtp.mailfrom=carlj@peak.org X-Spamd-Result: default: False [-3.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; SH_EMAIL_DBL_DONT_QUERY_IPS(0.00)[0.0.0.0:email]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:208.80.200.0/21]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[peak.org,none]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:14618, ipnet:208.80.202.0/23, country:US]; MIME_TRACE(0.00)[0:+] X-ThisMailContainsUnwantedMimeParts: N Bernd Walter writes: > On Sat, Oct 16, 2021 at 09:51:54PM +0200, Bernd Walter wrote: >> I'm trying to get X11 runing on the Pi4. >> So far I don't get a signal on the screen. >> I'd tried both HDMI ports. >> FreeBSD mentions: >> VT(efifb): resolution 592x448 >> ... >> fb0: on simplebus0 >> fb0: keeping existing fb bpp of 32 >> fbd0 on fb0 >> WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 14.0. >> VT: Replacing driver "efifb" with new "fb". >> fb0: 592x448(592x448@0,0) 32bpp >> fb0: fbswap: 1, pitch 2368, base 0x3eaf5000, screen_size 1060864 > > Ok, there was hdmi_safe=1, now I see the resultion. > However, the screen still has no signal. > >> Is there some kind of initialisation missing from u-boot? >> I noticed that raspbian on the Pi4 also leave the screen disabled >> until X starts. >> Unfortunately starting X on FreeBSD doesn't change anything. I don't know if this is your problem, but FreeBSD doesn't seem to initialize HDMI unless it connects to a monitor at boot. That means that you have to have a monitor plugged in when it boots up, and the monitor has to be turned on. If you boot up without a monitor plugged in, then I don't know any way to turn the HDMI output on, other than rebooting. -- Carl Johnson carlj@peak.org