Message-ID: <5d8ced1d-4155-454a-bfc5-93960be04f1b@net-c.cat>
Date: Thu, 10 Aug 2023 18:03:29 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Reply-To: github-siiky@net-c.cat
Subject: Re: Help installing in data mode
Content-Language: en-GB
To: ~alpine/users@lists.alpinelinux.org, steffen@sdaoden.eu
References: <28a77818-9007-469a-94d6-c421e0591b0e@net-c.cat>
 <20230808211438.UPazY%steffen@sdaoden.eu>
From: siiky <github-siiky@net-c.cat>
In-Reply-To: <20230808211438.UPazY%steffen@sdaoden.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the reply!

> hm, seems to me you want an EFI partition like
> 
>    /dev/nvme0n1p1      2048     534527    532480   260M EFI System
> 
> no?  And then an efibootmgr entry like
> 
>    Boot0001* kent HD(1,GPT,5d6d756b-5de2-4e5d-b043-8d4ae1bb6eb0,0x800,0x82000)/File(\ideapad-stage1.efi)root=/dev/nvme0n1p1 rootfstype=vfat init=/kent.sh

I'll make a UEFI install on the board itself, but since I was having 
problems running QEMU with UEFI I settled for a BIOS install on the VM. 
In the meantime I may have found how to run QEMU with UEFI on Debian.

> Hmm, i do have only one AlpineLinux VM with EFI at the moment,
> 
>    /x/vm/img/alp-2022-3#vmsys=aarch64#vmcpu=cortex-a57#vmmachine=virt#vmefi.qcow2
> 
> let's see.
> 
>    #?0(0.40 1/69)|alp-2022-aarch64:steffen$ fdisk -l
>    Disk /dev/vda: 8192 MB, 8589934592 bytes, 16777216 sectors
>    16644 cylinders, 16 heads, 63 sectors/track
>    Units: sectors of 1 * 512 = 512 bytes
> 
>    Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
>    /dev/vda1    2,0,33      262,1,33          2048     264191     262144  128M ef EFI (FAT-12/16/32)
>    /dev/vda2    262,1,34    489,10,26       264192   14944255   14680064 7168M 83 Linux
>    /dev/vda3    489,10,27   260,1,1       14944256   16777215    1832960  895M 82 Linux swap
> 
>    $ mount|grep vda1
>    /dev/vda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
> 

Is this a data install or a sys install? Do you happen to remember (or 
have documented somewhere) how you got it running?

I guess that, other than which setup-* commands can be used to achieve 
what I need, more importantly, I'm failing to understand how the pieces 
fit together. (TBH I have never had to learn about BIOS/EFI, 
bootloaders, etc, so I'm a noob in this area)

I don't yet understand much of the details you've shared, but I suspect 
(and hope) they will make more sense to me and prove to be useful 
eventually! :)

siiky