help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot install Guix 1.0.1 on Asus K50C


From: znavko
Subject: Re: Cannot install Guix 1.0.1 on Asus K50C
Date: Sun, 16 Jun 2019 08:17:56 +0000

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.

I did not understand where should I type --skip-checks, sorry.

Also, I am not sure partitioning is right:

Disk /dev/sdb: 59.6 GiB, 64023257088 bytes, 125045424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AB9A165C-BB51-8C47-813D-10219657F602

Device Start End Sectors Size Type
/dev/sdb1 2048 157695 155648 76M BIOS boot
/dev/sdb2 157696 105625599 105467904 50.3G Linux filesystem
/dev/sdb3 105625600 125045390 19419791 9.3G Linux swap

I use BIOS Grub, so I created a separate partition of type BIOS boot and size 
76Mb. Am I right of
its size? And I fulfilled this:

parted /dev/sdb set 1 bios_grub on

as it is described here:
https://www.gnu.org/software/grub/manual/grub/html_node/BIOS-installation.html#BIOS-installation

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?

The result of initialization and reboot is the next. Boot stops on locksource 
as it was before. And above I see this:

isci: Intel(R) C600 SAS Controller Driver - version 1.2.0 
ext2s_checks_if_mount: Can't check if filesystem is mounted due to missing mtab 
e2fsck: No such file or directory while trying open /dev/sdb2 
Possibly non-existent device?
File system check on /dev/sdb2 failed
Spawning Bourne-like REPL.
GNU Guile 2.2.4

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?

This is my config:

(operating-system (host-name "antelope") (timezone "Europe/Moscow") (locale 
"en_US.utf8")
                  (bootloader (bootloader-configuration 
                                (bootloader grub-bootloader) 
                                (target "/dev/sdb")))
                  (file-systems (cons (file-system 
                                        (device "/dev/sdb2") 
                                        (mount-point "/") 
                                        (type "ext4")) 
                                %base-file-systems))
                  (swap-devices '("/dev/sdb3"))

                  (initrd-modules (append (list "sata_sis")
                                          %base-initrd-modules))

June 15, 2019 6:54 PM, "pelzflorian (Florian Pelz)" <address@hidden> wrote:

> On Sat, Jun 15, 2019 at 06:22:00PM +0000, address@hidden wrote:
> 
>> I've changed config. Added initrd-modules that guix offered to me. And I 
>> reinitialized system.
>> […]
>> ERROR: In procedure open-file: No such file or directory:
>> "/gnu/store/qvhashahsh-linux-modules/sata-sis.ko"
> 
> It is looking for sata-sis.ko, but the file is called sata_sis.ko.
> 
> I remember <https://issues.guix.info/issue/31598>.
> 
> Does this solution help, i.e. using sata_sis in initrd-modules and
> perhaps using --skip-checks as described there?
> 
> Regards,
> Florian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]