From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 41120@debbugs.gnu.org
Subject: bug#41120: uvesafb service is unsupported on aarch64
Date: Thu, 7 May 2020 16:55:11 +0200 [thread overview]
Message-ID: <20200507145511.zfw5474uzecs2oum@pelzflorian.localdomain> (raw)
In-Reply-To: <20200507081234.GJ2359@E5400>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
On Thu, May 07, 2020 at 11:12:34AM +0300, Efraim Flashner wrote:
> I haven't tested the produced image, but the following builds without
> trying to also build v86d
>
> (start
> (if (and (and (string-suffix? "linux-gnu" %host-type)
> (or (string-prefix? "x86_64" %host-type)
> (string-prefix? "i686" %host-type)))
> (file-exists? "/dev/fb0"))
> #~(lambda ()
> ;; uvesafb is only supported on x86 and x86_64.
> (invoke #+(file-append kmod "/bin/modprobe")
> "uvesafb"
> (string-append "v86d=" #$v86d "/sbin/v86d")
> "mode_option=1024x768"))
> #~(lambda () #t)))
This way uvesafb is started unconditionally on x86_64, even when it is
not needed, leading to video corruption on some boots in QEMU.
I have more success with moving the file-exists check into the
#~(lambda …) like the attached patch. But I’m not sure it really
fixes ARM builds.
I tested via
qemu-system-x86_64 -m 1024 -smp 1 -enable-kvm -nic user,model=virtio-net-pci -boot menu=on,order=d -drive media=cdrom,file=/gnu/store/0cgbp4y7awk4spg49ajw077xyzk24fi0-iso9660-image
and on hardware. With QEMU, uvesafb is needed if and only if
nomodeset is passed as a kernel parameter.
Now how to build an ARM image for QEMU?
Sorry I left such a mess with uvesafb.
Regards,
Florian
[-- Attachment #2: 0001-installer-Do-not-load-uvesafb-on-non-x86-install-ima.patch --]
[-- Type: text/plain, Size: 2301 bytes --]
From 13fd2b590e37095ed4213d7bb85422b48deab9c6 Mon Sep 17 00:00:00 2001
From: Florian Pelz <pelzflorian@pelzflorian.de>
Date: Thu, 7 May 2020 13:26:19 +0200
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: [PATCH] installer: Do not load uvesafb on non-x86 install images.
Fixes <https://bugs.gnu.org/41120>.
Suggested by Efraim Flashner <efraim@flashner.co.il>.
* gnu/system/install.scm (uvesafb-shepherd-service): Do not build x86-only
v86d helper unconditionally.
---
gnu/system/install.scm | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/gnu/system/install.scm b/gnu/system/install.scm
index 6435c1bff4..ad8a84091c 100644
--- a/gnu/system/install.scm
+++ b/gnu/system/install.scm
@@ -299,16 +299,18 @@ the user's target storage device rather than on the RAM disk."
(documentation "Load the uvesafb kernel module if needed.")
(provision '(maybe-uvesafb))
(requirement '(file-systems))
- (start #~(lambda ()
- ;; uvesafb is only supported on x86 and x86_64.
- (or (not (and (string-suffix? "linux-gnu" %host-type)
- (or (string-prefix? "x86_64" %host-type)
- (string-prefix? "i686" %host-type))))
- (file-exists? "/dev/fb0")
- (invoke #+(file-append kmod "/bin/modprobe")
- "uvesafb"
- (string-append "v86d=" #$v86d "/sbin/v86d")
- "mode_option=1024x768"))))
+ (start
+ (if (and (and (string-suffix? "linux-gnu" %host-type)
+ (or (string-prefix? "x86_64" %host-type)
+ (string-prefix? "i686" %host-type)))
+ (file-exists? "/dev/fb0"))
+ #~(lambda ()
+ ;; uvesafb is only supported on x86 and x86_64.
+ (invoke #+(file-append kmod "/bin/modprobe")
+ "uvesafb"
+ (string-append "v86d=" #$v86d "/sbin/v86d")
+ "mode_option=1024x768"))
+ #~(lambda () #t)))
(respawn? #f)
(one-shot? #t))))
--
2.26.1
next prev parent reply other threads:[~2020-05-07 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 5:40 bug#41120: uvesafb service is unsupported on aarch64 Efraim Flashner
2020-05-07 7:06 ` Mathieu Othacehe
2020-05-07 8:05 ` Efraim Flashner
2020-05-07 8:12 ` Efraim Flashner
2020-05-07 14:55 ` pelzflorian (Florian Pelz) [this message]
2020-05-07 14:58 ` pelzflorian (Florian Pelz)
2020-05-08 9:09 ` Mathieu Othacehe
2020-05-13 12:50 ` Mathieu Othacehe
2020-05-14 8:16 ` Ludovic Courtès
2020-05-15 22:43 ` Ludovic Courtès
2021-12-29 2:30 ` Leo Famulari
2021-12-29 8:20 ` Efraim Flashner
2021-12-29 22:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-04 23:03 ` Pavel Shlyak
2022-08-05 12:59 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200507145511.zfw5474uzecs2oum@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=41120@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).