all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: RISCV porting effort
Date: Tue, 15 Jun 2021 15:37:25 +0300	[thread overview]
Message-ID: <YMifBdauxYctLbwB@3900XT> (raw)
In-Reply-To: <87lf7c0wnu.fsf@yucca>

[-- Attachment #1: Type: text/plain, Size: 3836 bytes --]

On Mon, Jun 14, 2021 at 06:00:21PM -0700, Vagrant Cascadian wrote:
> On 2021-06-14, Efraim Flashner wrote:
> > On Sun, Jun 13, 2021 at 10:24:13AM -0700, Vagrant Cascadian wrote:
> >> On 2021-06-07, Efraim Flashner wrote:
> >> > Last week my HiFive Umatched¹ board came
> >> ...
> >> > Ubuntu has an image for the board² which booted up just fine and I'm
> >> > using, since I didn't want to spend too long getting Debian to run on
> >> > the board.
> >> 
> >> I, on the other hand, went straight for Debian, of course! I stole the
> >> vendor kernel and u-boot and built a Debian rootfs... and after a few
> >> tries got it running.
> >> 
> >> live well,
> >>   vagrant
> >
> > Do you have notes on what you did? Right now I was thinking of taking
> > the Ubuntu image, keeping /boot with their kernel and u-boot and
> > replacing the rest of it with Debian. (And copying the device-tree dtb
> > files to /boot/firmware/kernel-version)
> 
> I didn't take notes, but off the top of my head something like this:
> 
>   Booted the OE image that shipped with it on the microSD
> 
>   add partition for new rootfs (cfdisk /dev/mmcblk?)

Not a bad idea. I tried flashing a new SD card with their 2021.05 image
but it gave me kernel panics over the serial console so I reflashed it
with 2021.03. Actually, after flashing it I deleted everything in
/dev/sda4 and did debootstrap there and left extlinux setup as-is.

>   mkfs.ext4 /dev/mmcblkXpY
>   mount -o noatime /dev/mmcblkXpY /mnt
> 
>   git clone https://salsa.debian.org/installer-team/debootstrap
>   cd deboostrap
>   sudo DEBOOTSTRAP_DIR=$(pwd) ./deboostrap --arch=riscv64 sid /mnt http://deb.debian.org/debian-ports

I added --include=openssh-server,sudo

>   echo 'UUID=...  / ext4 errors=remount-ro 0 1' > /mnt/etc/fstab
>   echo 'tmpfs /tmp tmpfs defaults,nosuid,nodev 0 0' >> /mnt/etc/fstab
> 
>   sudo chroot /mnt adduser vagrant --gecos ,,,
>   sudo chroot /mnt adduser vagrant sudo
>   sudo chroot /mnt passwd vagrant
> 
>   add another entry to /boot/extlinux/extlinux.conf using the
>   appropriate root=/dev/mmcblkXpY and/or root=UUID=...
> 
> Probably missed something, but that's the jist.

You forgot to mention what password you used ;P jkjk

echo "unmatched" > /etc/hostname
cat >>/etc/network/interfaces <<EOF
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
EOF

> Then, to build guix...
> 
>   git clone https://salsa.debian.org/debian/guix/
>   cd guix
>   git remote add originguix https://git.savannah.gnu.org/git/guix.git
>   git fetch
>   git format-patch -o debian/patches originguix/master..originguix/wip-riscv
>   # add new patches to debian/patches/series
>   
>   # adjust debian/rules and debian/control to use guile-3.0...
> 
>   # build the package!
>   DEB_BUILD_OPTIONS='nocheck parallel=5' sbuild --chroot-mode=unshare -d UNRELEASED -c sid 
> 
> Upgrading to use guile-3.0 required a manually rebuilt guile-gnutls
> against guile-3.0 as well...
> 
> Just pushed debian/wip-riscv64 to https://salsa.debian.org/debian/guix/
> if you want to look at my most recent attempt.
> 
> Notably, this is just the wip-riscv patches applied against guix 1.3.0;
> maybe building against guix master will be more successful?
> 
> 
> live well,
>   vagrant

I'm actually thinking of moving my reprepro setup off my g4 and hosting
it on my desktop (where I can get my gpg key more easily) and then
rsyncing it up to my server. If I setup pbuilder on the hifive unmatched
then I'll add those packages to the ones I already have online.



-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-06-15 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  7:09 RISCV porting effort Efraim Flashner
2021-06-07 15:37 ` Christopher Lemmer Webber
2021-06-08 13:43 ` Ludovic Courtès
2021-06-08 22:28   ` Gabriel Wicki
2021-06-10 13:22     ` Efraim Flashner
2021-06-11 21:07     ` Ludovic Courtès
2021-06-10 13:20   ` Efraim Flashner
2021-06-11 22:07     ` Ludovic Courtès
2021-06-18 13:05     ` RISCV porting effort (now in stock @mouser) Gabriel Wicki
2021-06-11 11:16 ` RISCV porting effort Efraim Flashner
2021-06-13 17:24 ` Vagrant Cascadian
2021-06-14  7:27   ` Efraim Flashner
2021-06-15  1:00     ` Vagrant Cascadian
2021-06-15 12:37       ` Efraim Flashner [this message]
2021-06-13 21:21 ` Christopher Baines
2021-06-20 15:37   ` Ludovic Courtès
2022-06-16  1:46     ` Pjotr Prins
2022-06-16 18:12       ` Maxim Cournoyer
2022-06-17 16:08       ` Ludovic Courtès
2022-06-17 22:52         ` Pjotr Prins
2022-06-20  7:45           ` Pjotr Prins
2022-06-22 13:37             ` Ludovic Courtès
2022-06-22 15:19               ` Ekaitz Zarraga
2022-06-28  8:54                 ` Efraim Flashner
2022-06-30 12:01                   ` Ludovic Courtès
2022-07-03  9:07                     ` Efraim Flashner
2022-06-24  6:37               ` Pjotr Prins

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YMifBdauxYctLbwB@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.