GNU bug report logs -
#41120
uvesafb service is unsupported on aarch64
Previous Next
Reported by: Efraim Flashner <efraim <at> flashner.co.il>
Date: Thu, 7 May 2020 05:41:01 UTC
Severity: normal
Merged with 48393
Done: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
Bug is archived. No further changes may be made.
Full log
Message #17 received at 41120 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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
[0001-installer-Do-not-load-uvesafb-on-non-x86-install-ima.patch (text/plain, attachment)]
This bug report was last modified 2 years and 287 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.