Guix sd startup fails to initialize AMD Radeon RX 560

  • Open
  • quality assurance status badge
Details
6 participants
  • Brice Waegeneire
  • Danny Milosavljevic
  • Boris A. Dekshteyn
  • Mathieu Othacehe
  • pelzflorian (Florian Pelz)
  • Ryan Osborne
Owner
unassigned
Submitted by
Ryan Osborne
Severity
normal
R
R
Ryan Osborne wrote on 4 May 2020 19:03
(address . bug-guix@gnu.org)
CAL=gfr52ggeRhKz8iVGY0AGi-AFPR1ZfxR682DiadU6UfSPv3A@mail.gmail.com
Same error with and without "modprobe.blacklist=radeon".
The installation medium works with the console, but it causes the installed
system to be unable to finish booting.
dmesg included as attachment

--
Ryan Osborne.
Attachment: file
Attachment: dm2
B
B
Boris A. Dekshteyn wrote on 5 May 2020 03:58
(address . bug-guix@gnu.org)
87tv0v6t3h.fsf@gmail.com
Ryan Osborne <r.asdert@gmail.com> writes:

Toggle quote (4 lines)
> Same error with and without "modprobe.blacklist=radeon".
> The installation medium works with the console, but it causes the installed system to be unable to finish booting.
> dmesg included as attachment

Try add "nomodeset" to kernel parameters.

--
WBR, Boris Dekshteyn
R
R
Ryan Osborne wrote on 5 May 2020 14:39
nomodeset
(address . 41082@debbugs.gnu.org)
87sggezhc4.fsf@gmail.com
nomodest allows the system to boot, but when it boots the framebuffer
and X don't seem to work.
Attachment: dm3
--
test signature
M
M
Mathieu Othacehe wrote on 6 May 2020 08:56
(name . Ryan Osborne)(address . r.asdert@gmail.com)
874kstd00f.fsf@gmail.com
Hello,

Thanks for reporting! It has been discussed on IRC, and booting the same
machine with integrated graphics works.

While uvesafb allows us to get framebuffer support in the
installer, the installed system will blackscreen or fail to boot with
those AMD GPUs.

Should we propose the installation of uvesafb service in the
installation? Or detect that it is currently used and force its install?

Florian, WDYT?

Thanks,

Mathieu

Ryan Osborne <r.asdert@gmail.com> writes:

Toggle quote (280 lines)
> nomodest allows the system to boot, but when it boots the framebuffer
> and X don't seem to work.
>
>
> [ 0.000000] Linux version 5.4.38-gnu (nixbld@) (gcc version 7.4.0 (GCC)) #1 SMP 1
> [ 0.000000] Command line: BOOT_IMAGE=/gnu/store/kygqk99rl8g66j9z125gnx4cyp7m9a5v-linux-libre-5.4.38/bzImage --root=/dev/mapper/cryptroot --system=/gnu/store/6hsgwcwzlyybim96i1jdp9hymsfj2sgf-system --load=/gnu/store/6hsgwcwzlyybim96i1jdp9hymsfj2sgf-system/boot modprobe.blacklist=usbmouse,usbkbd quiet nomodeset
> [ 0.000000] KERNEL supported cpus:
> [ 0.000000] Intel GenuineIntel
> [ 0.000000] AMD AuthenticAMD
> [ 0.000000] Hygon HygonGenuine
> [ 0.000000] Centaur CentaurHauls
> [ 0.000000] zhaoxin Shanghai
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
> [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
> [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
> [ 0.000000] BIOS-provided physical RAM map:
> [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
> [ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cca94fff] usable
> [ 0.000000] BIOS-e820: [mem 0x00000000cca95000-0x00000000cca9bfff] ACPI NVS
> [ 0.000000] BIOS-e820: [mem 0x00000000cca9c000-0x00000000cd44bfff] usable
> [ 0.000000] BIOS-e820: [mem 0x00000000cd44c000-0x00000000cd710fff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000cd711000-0x00000000dde9bfff] usable
> [ 0.000000] BIOS-e820: [mem 0x00000000dde9c000-0x00000000ddf27fff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000ddf28000-0x00000000ddf42fff] ACPI data
> [ 0.000000] BIOS-e820: [mem 0x00000000ddf43000-0x00000000de970fff] ACPI NVS
> [ 0.000000] BIOS-e820: [mem 0x00000000de971000-0x00000000deffefff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000defff000-0x00000000deffffff] usable
> [ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000021effffff] usable
> [ 0.000000] NX (Execute Disable) protection: active
> [ 0.000000] SMBIOS 2.8 present.
> [ 0.000000] DMI: LENOVO 10B00005US/, BIOS FCKT50AUS 04/03/2014
> [ 0.000000] tsc: Fast TSC calibration using PIT
> [ 0.000000] tsc: Detected 3192.712 MHz processor
> [ 0.001552] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
> [ 0.001553] e820: remove [mem 0x000a0000-0x000fffff] usable
> [ 0.001558] last_pfn = 0x21f000 max_arch_pfn = 0x400000000
> [ 0.001561] MTRR default type: uncachable
> [ 0.001562] MTRR fixed ranges enabled:
> [ 0.001563] 00000-9FFFF write-back
> [ 0.001563] A0000-BFFFF uncachable
> [ 0.001564] C0000-CFFFF write-protect
> [ 0.001565] D0000-E7FFF uncachable
> [ 0.001565] E8000-FFFFF write-protect
> [ 0.001565] MTRR variable ranges enabled:
> [ 0.001567] 0 base 0000000000 mask 7E00000000 write-back
> [ 0.001567] 1 base 0200000000 mask 7FF0000000 write-back
> [ 0.001568] 2 base 0210000000 mask 7FF8000000 write-back
> [ 0.001569] 3 base 0218000000 mask 7FFC000000 write-back
> [ 0.001569] 4 base 021C000000 mask 7FFE000000 write-back
> [ 0.001570] 5 base 021E000000 mask 7FFF000000 write-back
> [ 0.001570] 6 base 00E0000000 mask 7FE0000000 uncachable
> [ 0.001571] 7 disabled
> [ 0.001571] 8 disabled
> [ 0.001571] 9 disabled
> [ 0.001854] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
> [ 0.001984] total RAM covered: 8176M
> [ 0.002302] Found optimal setting for mtrr clean up
> [ 0.002302] gran_size: 64K chunk_size: 32M num_reg: 6 lose cover RAM: 0G
> [ 0.002584] e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
> [ 0.002587] last_pfn = 0xdf000 max_arch_pfn = 0x400000000
> [ 0.008697] found SMP MP-table at [mem 0x000fcd40-0x000fcd4f]
> [ 0.018390] check: Scanning 1 areas for low memory corruption
> [ 0.018394] Using GB pages for direct mapping
> [ 0.018396] BRK [0xd7c01000, 0xd7c01fff] PGTABLE
> [ 0.018397] BRK [0xd7c02000, 0xd7c02fff] PGTABLE
> [ 0.018398] BRK [0xd7c03000, 0xd7c03fff] PGTABLE
> [ 0.018420] BRK [0xd7c04000, 0xd7c04fff] PGTABLE
> [ 0.018421] BRK [0xd7c05000, 0xd7c05fff] PGTABLE
> [ 0.018531] BRK [0xd7c06000, 0xd7c06fff] PGTABLE
> [ 0.018558] BRK [0xd7c07000, 0xd7c07fff] PGTABLE
> [ 0.018643] BRK [0xd7c08000, 0xd7c08fff] PGTABLE
> [ 0.018786] BRK [0xd7c09000, 0xd7c09fff] PGTABLE
> [ 0.018822] RAMDISK: [mem 0x3674f000-0x3739efff]
> [ 0.018825] ACPI: Early table checksum verification disabled
> [ 0.018827] ACPI: RSDP 0x00000000000F0450 000024 (v02 LENOVO)
> [ 0.018830] ACPI: XSDT 0x00000000DDF2D088 000094 (v01 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018834] ACPI: FACP 0x00000000DDF3D8F0 00010C (v05 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018837] ACPI: DSDT 0x00000000DDF2D1B0 010739 (v02 LENOVO TC-FC 00001320 INTL 20120711)
> [ 0.018839] ACPI: FACS 0x00000000DE96F080 000040
> [ 0.018841] ACPI: APIC 0x00000000DDF3DA00 000072 (v03 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018843] ACPI: FPDT 0x00000000DDF3DA78 000044 (v01 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018844] ACPI: LPIT 0x00000000DDF3DAC0 00005C (v01 LENOVO TC-FC 00001320 AMI. 00000005)
> [ 0.018846] ACPI: SLIC 0x00000000DDF3DB20 000176 (v01 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018848] ACPI: MSDM 0x00000000DDF3DC98 000055 (v03 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018850] ACPI: SSDT 0x00000000DDF3DCF0 000539 (v01 LENOVO TC-FC 00001320 INTL 20120711)
> [ 0.018852] ACPI: SSDT 0x00000000DDF3E230 000AD8 (v01 LENOVO TC-FC 00001320 INTL 20120711)
> [ 0.018854] ACPI: MCFG 0x00000000DDF3ED08 00003C (v01 LENOVO TC-FC 00001320 MSFT 00000097)
> [ 0.018855] ACPI: HPET 0x00000000DDF3ED48 000038 (v01 LENOVO TC-FC 00001320 AMI. 00000005)
> [ 0.018857] ACPI: SSDT 0x00000000DDF3ED80 00036D (v01 LENOVO TC-FC 00001320 INTL 20120711)
> [ 0.018859] ACPI: SSDT 0x00000000DDF3F0F0 0034E1 (v01 LENOVO TC-FC 00001320 INTL 20091112)
> [ 0.018861] ACPI: BGRT 0x00000000DDF425D8 000038 (v00 LENOVO TC-FC 00001320 AMI 00010013)
> [ 0.018863] ACPI: DMAR 0x00000000DDF42610 000080 (v01 LENOVO TC-FC 00001320 INTL 00000001)
> [ 0.018868] ACPI: Local APIC address 0xfee00000
> [ 0.018928] No NUMA configuration found
> [ 0.018928] Faking a node at [mem 0x0000000000000000-0x000000021effffff]
> [ 0.018931] NODE_DATA(0) allocated [mem 0x21effa000-0x21effdfff]
> [ 0.018948] Zone ranges:
> [ 0.018949] DMA32 [mem 0x0000000000001000-0x00000000ffffffff]
> [ 0.018950] Normal [mem 0x0000000100000000-0x000000021effffff]
> [ 0.018951] Device empty
> [ 0.018951] Movable zone start for each node
> [ 0.018952] Early memory node ranges
> [ 0.018952] node 0: [mem 0x0000000000001000-0x000000000009cfff]
> [ 0.018953] node 0: [mem 0x0000000000100000-0x00000000cca94fff]
> [ 0.018954] node 0: [mem 0x00000000cca9c000-0x00000000cd44bfff]
> [ 0.018954] node 0: [mem 0x00000000cd711000-0x00000000dde9bfff]
> [ 0.018955] node 0: [mem 0x00000000defff000-0x00000000deffffff]
> [ 0.018955] node 0: [mem 0x0000000100000000-0x000000021effffff]
> [ 0.019064] Zeroed struct page in unavailable ranges: 13459 pages
> [ 0.019065] Initmem setup node 0 [mem 0x0000000000001000-0x000000021effffff]
> [ 0.019066] On node 0 totalpages: 2083693
> [ 0.019066] DMA32 zone: 14190 pages used for memmap
> [ 0.019067] DMA32 zone: 21 pages reserved
> [ 0.019068] DMA32 zone: 908141 pages, LIFO batch:63
> [ 0.027939] Normal zone: 18368 pages used for memmap
> [ 0.027941] Normal zone: 1175552 pages, LIFO batch:63
> [ 0.038832] ACPI: PM-Timer IO Port: 0x1808
> [ 0.038834] ACPI: Local APIC address 0xfee00000
> [ 0.038839] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> [ 0.038849] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> [ 0.038850] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> [ 0.038851] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> [ 0.038852] ACPI: IRQ0 used by override.
> [ 0.038852] ACPI: IRQ9 used by override.
> [ 0.038854] Using ACPI (MADT) for SMP configuration information
> [ 0.038855] ACPI: HPET id: 0x8086a701 base: 0xfed00000
> [ 0.038859] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; /*(DEBLOBBED)*/
> [ 0.038861] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
> [ 0.038875] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
> [ 0.038876] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
> [ 0.038876] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
> [ 0.038877] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
> [ 0.038877] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
> [ 0.038878] PM: Registered nosave memory: [mem 0xcca95000-0xcca9bfff]
> [ 0.038879] PM: Registered nosave memory: [mem 0xcd44c000-0xcd710fff]
> [ 0.038880] PM: Registered nosave memory: [mem 0xdde9c000-0xddf27fff]
> [ 0.038881] PM: Registered nosave memory: [mem 0xddf28000-0xddf42fff]
> [ 0.038881] PM: Registered nosave memory: [mem 0xddf43000-0xde970fff]
> [ 0.038882] PM: Registered nosave memory: [mem 0xde971000-0xdeffefff]
> [ 0.038883] PM: Registered nosave memory: [mem 0xdf000000-0xf7ffffff]
> [ 0.038883] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
> [ 0.038884] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
> [ 0.038884] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
> [ 0.038885] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
> [ 0.038885] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
> [ 0.038885] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
> [ 0.038886] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
> [ 0.038886] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
> [ 0.038887] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
> [ 0.038887] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
> [ 0.038887] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
> [ 0.038889] [mem 0xdf000000-0xf7ffffff] available for PCI devices
> [ 0.038889] Booting paravirtualized kernel on bare hardware
> [ 0.038892] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
> [ 0.038897] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4 nr_node_ids:1
> [ 0.039029] percpu: Embedded 53 pages/cpu s178520 r8192 d30376 u524288
> [ 0.039034] pcpu-alloc: s178520 r8192 d30376 u524288 alloc=1*2097152
> [ 0.039035] pcpu-alloc: [0] 0 1 2 3
> [ 0.039052] Built 1 zonelists, mobility grouping on. Total pages: 2051114
> [ 0.039053] Policy zone: Normal
> [ 0.039054] Kernel command line: BOOT_IMAGE=/gnu/store/kygqk99rl8g66j9z125gnx4cyp7m9a5v-linux-libre-5.4.38/bzImage --root=/dev/mapper/cryptroot --system=/gnu/store/6hsgwcwzlyybim96i1jdp9hymsfj2sgf-system --load=/gnu/store/6hsgwcwzlyybim96i1jdp9hymsfj2sgf-system/boot modprobe.blacklist=usbmouse,usbkbd quiet nomodeset
> [ 0.039147] You have booted with nomodeset. This means your GPU drivers are DISABLED
> [ 0.039147] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
> [ 0.039148] Unless you actually understand what nomodeset does, you should reboot without enabling it
> [ 0.039497] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
> [ 0.039680] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
> [ 0.039717] mem auto-init: stack:byref_all, heap alloc:on, heap free:off
> [ 0.042574] Calgary: detecting Calgary via BIOS EBDA area
> [ 0.042576] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
> [ 0.060675] Memory: 8083152K/8334772K available (14339K kernel code, 1525K rwdata, 4184K rodata, 1916K init, 2584K bss, 251620K reserved, 0K cma-reserved)
> [ 0.060681] random: get_random_u64 called from __kmem_cache_create+0x46/0x570 with crng_init=0
> [ 0.060757] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
> [ 0.060767] Kernel/User page tables isolation: enabled
> [ 0.060777] ftrace: allocating 41677 entries in 163 pages
> [ 0.074199] rcu: Hierarchical RCU implementation.
> [ 0.074200] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
> [ 0.074201] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
> [ 0.074202] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
> [ 0.076242] NR_IRQS: 16640, nr_irqs: 456, preallocated irqs: 16
> [ 0.076457] spurious 8259A interrupt: IRQ7.
> [ 0.079840] Console: colour VGA+ 80x25
> [ 0.079883] printk: console [tty0] enabled
> [ 0.079896] ACPI: Core revision 20190816
> [ 0.079988] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
> [ 0.080000] APIC: Switch to symmetric I/O mode setup
> [ 0.080001] DMAR: Host address width 39
> [ 0.080002] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
> [ 0.080005] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap d2008c20660462 ecap f010da
> [ 0.080006] DMAR: RMRR base: 0x000000dee8f000 end: 0x000000dee9dfff
> [ 0.080007] DMAR-IR: IOAPIC id 8 under DRHD base 0xfed90000 IOMMU 0
> [ 0.080008] DMAR-IR: HPET id 0 under DRHD base 0xfed90000
> [ 0.080008] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
> [ 0.080227] DMAR-IR: Enabled IRQ remapping in x2apic mode
> [ 0.080228] x2apic enabled
> [ 0.080234] Switched APIC routing to cluster x2apic.
> [ 0.080621] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> [ 0.100000] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2e056531aca, max_idle_ns: 440795249676 ns
> [ 0.100003] Calibrating delay loop (skipped), value calculated using timer frequency.. 6385.42 BogoMIPS (lpj=12770848)
> [ 0.100005] pid_max: default: 32768 minimum: 301
> [ 0.100023] LSM: Security Framework initializing
> [ 0.100027] Yama: becoming mindful.
> [ 0.100048] AppArmor: AppArmor initialized
> [ 0.100050] TOMOYO Linux initialized
> [ 0.100087] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
> [ 0.100099] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
> [ 0.100107] *** VALIDATE tmpfs ***
> [ 0.100207] *** VALIDATE proc ***
> [ 0.100249] *** VALIDATE cgroup1 ***
> [ 0.100249] *** VALIDATE cgroup2 ***
> [ 0.100288] mce: CPU0: Thermal monitoring enabled (TM1)
> [ 0.100299] process: using mwait in idle threads
> [ 0.100301] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
> [ 0.100301] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
> [ 0.100303] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
> [ 0.100304] Spectre V2 : Mitigation: Full generic retpoline
> [ 0.100305] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
> [ 0.100305] Speculative Store Bypass: Vulnerable
> [ 0.100308] TAA: Vulnerable: Clear CPU buffers attempted, no microcode
> [ 0.100308] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
> [ 0.100440] Freeing SMP alternatives memory: 28K
> [ 0.210141] smpboot: CPU0: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (family: 0x6, model: 0x3c, stepping: 0x3)
> [ 0.210202] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
> [ 0.210207] ... version: 3
> [ 0.210208] ... bit width: 48
> [ 0.210208] ... generic registers: 8
> [ 0.210208] ... value mask: 0000ffffffffffff
> [ 0.210209] ... max period: 00007fffffffffff
> [ 0.210209] ... fixed-purpose events: 3
> [ 0.210210] ... event mask: 00000007000000ff
> [ 0.210236] rcu: Hierarchical SRCU implementation.
> [ 0.210833] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
> [ 0.210865] smp: Bringing up secondary CPUs ...
> [ 0.210917] x86: Booting SMP configuration:
> [ 0.210918] .... node #0, CPUs: #1 #2 #3
> [ 0.211187] smp: Brought up 1 node, 4 CPUs
> [ 0.211187] smpboot: Max logical packages: 1
> [ 0.211187] smpboot: Total of 4 processors activated (25541.69 BogoMIPS)
> [ 0.211187] devtmpfs: initialized
> [ 0.211187] x86/mm: Memory block size: 128MB
> [ 0.211187] PM: Registering ACPI NVS region [mem 0xcca95000-0xcca9bfff] (28672 bytes)
> [ 0.211187] PM: Registering ACPI NVS region [mem 0xddf43000-0xde970fff] (10674176 bytes)
> [ 0.212125] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
> [ 0.212130] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
> [ 0.212172] pinctrl core: initialized pinctrl subsystem
> [ 0.212247] PM: RTC time: 12:25:05, date: 2020-05-05
> [ 0.212302] NET: Registered protocol family 16
> [ 0.212368] audit: initializing netlink subsys (disabled)
> [ 0.212372] audit: type=2000 audit(1588681505.132:1): state=initialized audit_enabled=0 res=1
> [ 0.212372] cpuidle: using governor ladder
> [ 0.212372] cpuidle: using governor menu
> [ 0.212372] ACPI: bus type PCI registered
> [ 0.212372] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> [ 0.212372] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
> [ 0.212372] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
> [ 0.212372] PCI: Using configuration type 1 for base access
> [ 0.212372] core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
> [ 0.212449] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
> [ 0.212993] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
> [ 0.212993] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
> [ 0.212993] ACPI: Added _OSI(Module Device)
> [ 0.212993] ACPI: Added _OSI(Processor Device)
> [ 0.212993] ACPI: Added _OSI(3.0 _SCP Extensions)
> [ 0.212993] ACPI: Added _OSI(Processor Aggregator Device)
> [ 0.212993] ACPI: Added _OSI(Linux-Dell-Video)
> [ 0.212993] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
> [ 0.212993] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
> [ 0.222912] ACPI: 5 ACPI AML tables successfully acquired and loaded
> [ 0.224122] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
> [ 0.224627] ACPI: Dynamic OEM Table Load:
> [
This message was truncated. Download the full message here.
P
P
pelzflorian (Florian Pelz) wrote on 6 May 2020 10:19
(name . Mathieu Othacehe)(address . m.othacehe@gmail.com)
20200506081905.5yfdk3j7y237fdj2@pelzflorian.localdomain
On Wed, May 06, 2020 at 08:56:48AM +0200, Mathieu Othacehe wrote:
Toggle quote (5 lines)
> Should we propose the installation of uvesafb service in the
> installation? Or detect that it is currently used and force its install?
>
> Florian, WDYT?

Yes, IMHO there should be a uvesafb-service-type. Copying the uvesafb
service from the installer into the config.scm should work (but the
video resolution should be adjusted, probably something higher than
1024x768 is supported by the system).

We could add a uvesafb-service-type to its own gnu/services/….scm.
Autodetection of the best usable resolution via v86d:testvbe could be
added (however the best resolution usable with uvesafb may be less
than the screen’s resolution).

One way such a uvesafb-service-type could work is exactly like in the
installler. Would it be right to add a uvesafb service that runs
modprobe itself?

Another way is to extend etc-service-type for this the way I wrote at
Extending other services seems cleaner, but in the discussions by
Brice Waegeneire and Danny Milosavljevic (I put them in Cc) they were
not really satisfied with etc-service-type.

Toggle quote (13 lines)
> When the dust has settled on the kernel-module-configuration-service
> discussed by Brice Waegeneire and Danny Milosavljevic
> <https://lists.gnu.org/archive/html/guix-patches/2020-04/msg00272.html>,
> a proper uvesafb service can be added. Then I can make and test one
> and it could also be used in the installer. That would be the clean
> solution. In particular, it could detect the resolution to use for
> uvesafb automatically by running the attached code testvbe.scm as
> root. But how to run that code depends on the
> kernel-module-configuration-service if/when it exists. (I did not
> know how to extend etc-service-type with a file created at runtime not
> build time, but maybe kernel-module-configuration-service works
> differently anyway.)

Regards,
Florian
D
D
Danny Milosavljevic wrote on 6 May 2020 16:57
(name . Mathieu Othacehe)(address . m.othacehe@gmail.com)
20200506165730.48292398@scratchpost.org
Hi,

On Wed, 06 May 2020 08:56:48 +0200
Mathieu Othacehe <m.othacehe@gmail.com> wrote:

Toggle quote (3 lines)
> Should we propose the installation of uvesafb service in the
> installation? Or detect that it is currently used and force its install?

Since we don't have a previous generation to go back to, I'd prefer the first
generation to be one that actually works. So the latter.

If that's not what is wanted, one can always go into config and reconfigure
the system. If *that* doesn't boot, one can just reboot and select the
previous generation in the bootloader.

So I'd be in favor of the installer creating a system as close as possible
to the installer's own boot configuration.

Compared to that, if one created a system with a configuration different
to the installer's own boot media, maybe the system won't boot at all.
What do you do then?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl6y0FoACgkQ5xo1VCww
uqWNvAf/ZALMFEQCvAAgqaIhCUdbYN1YVeyjuqeypTfxdrhGCM1j70Hymy1fZRmb
Lpqt0mViYVNPOewlj35hfUefPY4ko99V4bHecAEitWH6Xv3qQLoDioW2uFbY/c7O
4oEcY+vOSI5T0yCR3DpAErIo7uYMLOU9kWEFR55Yw08D7R3kpygOK09J0KAqcm5q
n21FH+avq+IKBbSEX/CEd7b9f51NNSveTOkOesqZ87Z+1JTTWyTVNVYL5mMcuH2N
pBGv5mzl5aSfPugFAM82k8i5snWA4QX+v1vwwbdP3Um7wbE18LCj9nBMYfNNsxuV
uD7E6duYamEX49aBaTI1Ww23v7TkjA==
=RdBp
-----END PGP SIGNATURE-----


D
D
Danny Milosavljevic wrote on 6 May 2020 22:53
20200506225311.597322f0@scratchpost.org
Hi,

On Wed, 6 May 2020 10:19:05 +0200
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:

Toggle quote (9 lines)
> (but the video resolution should be adjusted, probably something higher than
> 1024x768 is supported by the system).

> We could add a uvesafb-service-type to its own gnu/services/….scm.

> Autodetection of the best usable resolution via v86d:testvbe could be
> added (however the best resolution usable with uvesafb may be less
> than the screen’s resolution).

That could maybe cause something not to work too.

I know I keep harping on that, but our generation feature only helps if there
actually is a previous generation to go back too. So any "improvement" to
what the installer did, which obviously worked if Guix boots up, could also
cause the finished installation not to work--and without recourse.

(Hmm, but then there's nothing preventing us from reconfiguring twice in the
installer)

Toggle quote (4 lines)
> One way such a uvesafb-service-type could work is exactly like in the
> installler. Would it be right to add a uvesafb service that runs
> modprobe itself?

Why not have uvesafb-service-type extend kernel-module-loader-service-type
and give it a module to load unconditionally?
That would make the whole thing more declarative, which we usually want in
Guix.

If that's not possible, sure, the uvesafb service could also modprobe stuff
on its own.

Toggle quote (6 lines)
> Another way is to extend etc-service-type for this the way I wrote at
> <https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00320.html>.
> Extending other services seems cleaner, but in the discussions by
> Brice Waegeneire and Danny Milosavljevic (I put them in Cc) they were
> not really satisfied with etc-service-type.

Well, it's okay--but we could also make a proper service that would allow
other guix services to specify what kernel module configuration they expect
and also guix to find and report conflicts in the global view.

I think it's the right thing to do since the Linux kernel (and the hardware)
keeps global state.
So the programs that run in user space have to kinda negotiate what global state
is okay for everyone. That negotiation is a lot easier for Guix to do if
it actually knows what is what, as opposed to an opaque etc directory that could
be anything.

Maybe that's premature and we could use etc-service-type in the mean time.
However, if a kernel-module-configuration-service appeared later then users
would have to migrate to it manually. Not great.

Toggle quote (5 lines)
> > kernel-module-configuration-service if/when it exists. (I did not
> > know how to extend etc-service-type with a file created at runtime not
> > build time, but maybe kernel-module-configuration-service works
> > differently anyway.)

I think Brice already had a nice mockup for the design, but I don't know whether
Brice plans to do it or not. Brice?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl6zI7cACgkQ5xo1VCww
uqX9Cgf9EV8/5PQoPpfRCthcNqRvmM2tNRZgRIxzOYFCTu2sccxkCstZ1PmmM90C
IJHKbi0B6yyuUJTdR1Lgps2vRgS7ID8Omoai+0gl0AIJd/MkWKeAQAbRkenKfBpM
8OWpUNwhwRQuh0/zJyOXUhbN+W5IT3DvcvMTczd5icOSQeI6D2LHaQGZ16ABm3Ke
EE1+TI7i/etymfHh9//2fUQrmBxH5oUsYPamhk34276M0icDaT6A0LoyIYkSmE04
K8x+fsqe/vDUr+r57BrHJC8ACe4BW2AbWALNnu5bmpOntW/b0cSPx1cyaoIflA/0
PBkEAqiTdz84ojpLZIlg0VzjIlw1lQ==
=K10y
-----END PGP SIGNATURE-----


B
B
Brice Waegeneire wrote on 10 May 2020 21:44
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
0f7d5d9a5755698baaf1a69df4f1fddb@waegenei.re
Hello,

On 2020-05-06 20:53, Danny Milosavljevic wrote:
[...]

Toggle quote (15 lines)
> Maybe that's premature and we could use etc-service-type in the mean
> time.
> However, if a kernel-module-configuration-service appeared later then
> users
> would have to migrate to it manually. Not great.
>
>> > kernel-module-configuration-service if/when it exists. (I did not
>> > know how to extend etc-service-type with a file created at runtime not
>> > build time, but maybe kernel-module-configuration-service works
>> > differently anyway.)
>
> I think Brice already had a nice mockup for the design, but I don't
> know whether
> Brice plans to do it or not. Brice?

I don't have code for the kernel-module-configuration-service yet but
since use
cases for this service come up every few weeks it may be time to
implement it.
I'll work on it in the coming days.

Cheers,
- Brice
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 41082@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 41082
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch