[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cirrus (was Re: Release progress, week 10)
From: |
pelzflorian (Florian Pelz) |
Subject: |
Re: cirrus (was Re: Release progress, week 10) |
Date: |
Sat, 17 Dec 2022 20:18:31 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> That hold-up aside, maybe could you also tentatively add the cirrus
> initrd module to the 1.4.0 installation image? I suppose it won’t break
> anything, but it might help with bugs like
> <https://issues.guix.gnu.org/60002>.
I tested the following chance:
diff --git a/gnu/system/install.scm b/gnu/system/install.scm
index 3dd9e0e87b..dfa6db9408 100644
--- a/gnu/system/install.scm
+++ b/gnu/system/install.scm
@@ -507,6 +507,10 @@ (define installation-os
;; Thus, blacklist it.
(kernel-arguments '("quiet" "modprobe.blacklist=radeon,amdgpu"))
+ (initrd-modules (append
+ (list "cirrus")
+ %base-initrd-modules))
+
(file-systems
;; Note: the disk image build code overrides this root file system with
;; the appropriate one.
This makes the installer work on QEMU with '-vga cirrus'.
It also still works under default QEMU (cirrus isn’t default anymore
since QEMU 2.2 according to the docs).
The installer also still works on my:
* Beebox with Intel
* PC with Nvidia
and thanks to the resolution of the
https://issues.guix.gnu.org/60010
it also works on my
* PC with AMD
* laptop with AMD
None is modern hardware, but still, please add cirrus.
Regards,
Florian