From: Simon South <simon@simonsouth.net>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Building installation image for ROCK64
Date: Sun, 12 Apr 2020 12:19:59 -0400 [thread overview]
Message-ID: <87eessisls.fsf@simonsouth.net> (raw)
In-Reply-To: <877dyl7mn0.fsf@yucca> (Vagrant Cascadian's message of "Sat, 11 Apr 2020 14:12:03 -0700")
Vagrant Cascadian <vagrant@debian.org> writes:
> This might avoid playing whack-a-mole with arbitrarily complex sets of drivers:
>
> (kernel linux-libre-arm64-generic)
> (initrd-modules '())
Thanks, Vagrant. That definitely got me further, though the machine
still fails to finish booting:
[ 0.243248] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
[ 0.243264] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
[ 0.243279] rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv on device rockchip-pinctrl
[ 0.243291] reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main thread
GC Warning: Couldn't read /proc/stat
Welcome, this is GNU's early boot Guile.
Use '--repl' for an initrd REPL.
loading kernel modules...
loading '/gnu/store/6a4pyi34awj0jkd6ipl39dylj675ipxm-system/boot'...
ERROR: In procedure open-file:
In procedure open-file: No such file or directory: "/var/run/utmpx"
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
GNU Guile 2.2.6
Copyright (C) 1995-2019 Free Software Foundation, Inc.
I assume the missing file is the actual reason for the failure and
whatever's going on with the voltage-regulator drivers is unimportant
for now. Any chance something in the output above rings a bell?
I'll start diagnosing from here---it's probably time to write a real
"operating-system" definition for this machine and see what a newly
generated image contains.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-04-12 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 19:48 Building installation image for ROCK64 Simon South
2020-04-11 21:12 ` Vagrant Cascadian
2020-04-12 16:19 ` Simon South [this message]
2020-04-26 14:31 ` Simon South
2020-04-26 17:09 ` Vagrant Cascadian
2020-04-27 13:19 ` Simon South
2020-04-27 17:22 ` Vagrant Cascadian
2020-04-12 10:18 ` Pierre Langlois
2020-04-12 10:27 ` Pierre Langlois
2020-04-12 16:25 ` Simon South
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=87eessisls.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=help-guix@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.
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).