From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: znavko@disroot.org
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Cannot install Guix 1.0.1 on Asus K50C
Date: Sun, 16 Jun 2019 10:39:53 +0200 [thread overview]
Message-ID: <20190616083953.2ydihmxkq2ji6jll@pelzflorian.localdomain> (raw)
In-Reply-To: <dd6f34f10c9bc0af9a1494c8aa755045@disroot.org>
On Sun, Jun 16, 2019 at 08:17:56AM +0000, znavko@disroot.org wrote:
> Hi, Florian! I have reinit system with config like this:
>
> (initrd-modules (append (list "sata_sis")
> %base-initrd-modules))
>
> where underscore is placed instead of dash: sata_sis.
>
Yes.
> I did not understand where should I type --skip-checks, sorry.
>
Maybe you do not need it. If it fails without --skip-checks, it is
`guix system reconfigure --skip-checks /path/to/your/config.scm`.
Please try without --skip-checks first. It may be a bug if this is
necessary.
> I use BIOS Grub, so I created a separate partition of type BIOS boot and size 76Mb. Am I right of
> its size?
I believe it is sufficient, although you do not need to use a separate
/boot partition.
> Also, may be I need to update by usb flash, cause there is Guix 1.0.1 of age 3 weeks. Might be the
> new image has some bugfixes for me?
>
I do not know if there were changes to kernel modules.
> Please, should I type /dev/sda everywhere in config.scm instead of /dev/sdb? When I boot to usb my ssd disk is showing like /dev/sdb, but when I boot from ssd disk it is /dev/sda, so this config does not work. And this ubiquitous option was not described in manual. I always read:
> "For legacy systems, the target field names a device, like /dev/sda;... "
>
> So, what to do?
>
Please use UUIDs to name the devices, as described in the manual.
Regards,
Florian
next prev parent reply other threads:[~2019-06-16 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 16:45 Cannot install Guix 1.0.1 on Asus K50C znavko
2019-06-15 18:22 ` znavko
2019-06-15 18:54 ` pelzflorian (Florian Pelz)
2019-06-16 8:17 ` znavko
2019-06-16 8:39 ` pelzflorian (Florian Pelz) [this message]
2019-06-16 10:29 ` znavko
2019-06-16 11:16 ` 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=20190616083953.2ydihmxkq2ji6jll@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=znavko@disroot.org \
/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.
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).