[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re:Re: mounting "my-home" to /home cannot work again.
From: |
tumashu |
Subject: |
Re:Re: mounting "my-home" to /home cannot work again. |
Date: |
Sat, 14 Jan 2017 20:08:20 +0800 (CST) |
(file-systems (cons* fs-root fs-home fs-backup1 fs-backup2 %base-file-systems))
cannot work !
在 2017-01-14 19:00:35,"David Craven" <address@hidden> 写道:
Hi!
> ------------------------
> [ 12.079023] [drm] Initialized radeon 2.48.0 20080528 for 0000:01:00.0 on
> minor 0
> [ 13.253525] input: HDA Intel MID Mic as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
> [ 13.253746] input: HDA Intel MID Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input19
> [ 13.253983] input: HDA ATI HDMI HDMI/DP,pcm=3 as
> /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
> [ 13.326750] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [ 13.327259] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8b20000, irq=19
> [ 13.446723] ath9k 0000:44:00.0 wlo1: renamed from wlan0
> **Get stuck at this point.....**
> -------------------------
These are generated by the kernel. There must be some stacktrace or
errors from guixsd missing somewhere, maybe when running guix system
reconfigure?
I don't see how an error in the guixsd configuration or a bug in
guixsd would cause the kernel to hang during boot, before entering the
initrd.
The recommended way of adding file-systems to an operating-system
definition according to the guix manual is:
(file-systems (cons* fs-root fs-home fs-backup1 fs-backup2 %base-file-systems))
Can you verify that the working setup kernel is the same one as the
non working setup kernel?
Possibly a relevant commit is 37203715805335131d18ac05ecb0367f222cd065.
HTH!
David