From: Vagrant Cascadian <vagrant@debian.org>
To: paul <goodoldpaul@autistici.org>, help-guix@gnu.org
Subject: Re: Pinebook Pro boot from NVME
Date: Sat, 28 Oct 2023 14:19:16 -0700 [thread overview]
Message-ID: <87il6qjvhn.fsf@wireframe> (raw)
In-Reply-To: <e4628cb2-f566-5519-c869-ba7a0434d662@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
On 2023-10-12, paul wrote:
> On 10/12/23 06:41, Vagrant Cascadian wrote:
>> On 2023-10-07, paul via wrote:
>>> I'm using tow boot and i have armbian on emmc, guix system on sd card
>>> and guix system on nvme. One really strange behavior happens:
>>>
>>> 1. I choose the nvme option in tow boot
>>> 2. I'm instantaneously presented the U-Boot menu (as opposed to when I
>>> choose the sd card, where I'm also presented u-boot but quite a lot
>>> slower) so I'm pretty sure that the bootloader is correctly read
>>> from the disk
>>> 3. a Guix System loads but when I log in as root and run mount the /
>>> filesystem is mounted on /dev/mmblk1
>> Does it boot to the NVMe partition correctly when you remove the SD
>> card?
> No it does not. If I remove the sd card and don't change anything else
> guix is not booting. I'm attaching [0] a video of the behavior,
> basically the screen stays black forever.
Another thing I vaguely recall is what is the power profile of your NVMe
device? Some draw too much power for the PinebookPro.
I had originally tested two different NVMe; one simply did not work at
all, and one did. There is some more information here:
https://wiki.pine64.org/index.php/Pinebook_Pro_Hardware_Accessory_Compatibility#NVMe_SSD_drives
There is a command nvmectl that you can use to adjust your NVMe to use a
lower power profile by default, but I have not experimented with it
recently, as I ended up just using the NVMe that did not draw much power
out-of-the-box. The high-performance ones, unsurprisingly, tend to draw
more power, so picking one that has a slower speed *might* help.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-10-28 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 9:42 Pinebook Pro boot from NVME paul via
2023-10-12 4:41 ` Vagrant Cascadian
2023-10-12 21:27 ` paul
2023-10-15 6:22 ` Efraim Flashner
2023-10-15 17:21 ` Vagrant Cascadian
2023-10-17 22:02 ` paul via
2023-10-18 10:22 ` Efraim Flashner
2023-10-19 12:30 ` paul via
2023-10-28 21:19 ` Vagrant Cascadian [this message]
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=87il6qjvhn.fsf@wireframe \
--to=vagrant@debian.org \
--cc=goodoldpaul@autistici.org \
--cc=help-guix@gnu.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).