From: Vagrant Cascadian <vagrant@debian.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix on the ASUS C201PA
Date: Sat, 09 Mar 2019 18:42:29 -0800 [thread overview]
Message-ID: <87va0rzbze.fsf@ponder> (raw)
In-Reply-To: <871s3kjcnj.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
On 2019-03-06, Timothy Sample wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>> On 2019-03-06, Timothy Sample wrote:
>>> I was able to get Guix to boot on an ASUS Chromebook C201PA.
So, I've gotten the kernel to load, but the version of coreboot and/or
depthcharge I have installed seems to ignore the presence of the initrd
(which you had mentioned in your initial mail). I guess I should try
libreboot again, maybe it fixed some other things too...
I did manage to get the rockchip.usb_uart with a hacked up USB cable to
produce a serial console for debugging and actually seeing the kernel
logs rather than them scrolling pass the screen only to give a kernel
panic.
(kernel-arguments '("console=ttyS2,115200" "rockchip.usb_uart"))
Anyone had any luck booting GuixSD without an initrd? I sort of thought
about dumping the initramfs to a partition and trying to work around it
that way...
I've also got patches to pull in u-boot 2019.04-rc3 with a
chromebook_speedy target for installing directly to flash, as well as
one to load from depthcharge. Unfortunately, I still get no
video. Someone's working on porting rockchip.usb_uart to u-boot to make
it easier to see what's going on. Mostly hoping to just get u-boot
support working and forget about depthcharge.
>> I have two big technical frustrations with Depthcharge:
>>
>> It's really hard to debug or select alternate kernels when boot is
>> failing.
>>
>> The kernel+initrd is limited to ~16MB. linux-libre on armhf is about
>> 5MB, and the initrd around 11MB... so it's running pretty close to that
>> limit (Debian initrd's are even larger these days). I even increased the
>> size of the partition to 32MB to see if it would work, but it refused to
>> boot from anything larger than 16MB.
>
> I didn’t know about the image size limit. Guix (with the very spartan
> PrawnOS kernel build) is only 14M, so I guess I was just lucky here.
This may have just been the older libreboot build I once had; I notice
that prawn-os and gentoo seem to work fine with 32MB/64MB kernel boot
partitions. Or maybe some other misunderstanding on my part about why
depthcharge refused to boot it... just now starting to grasp all those
"cgpt" partitioning flags.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-03-10 2:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 7:20 Guix on the ASUS C201PA Timothy Sample
2019-03-06 8:59 ` Vagrant Cascadian
2019-03-06 14:33 ` Timothy Sample
2019-03-10 2:42 ` Vagrant Cascadian [this message]
2019-03-17 6:47 ` Vagrant Cascadian
2019-03-17 15:20 ` Timothy Sample
2019-03-18 5:38 ` Vagrant Cascadian
2019-03-19 7:22 ` Danny Milosavljevic
2019-03-23 16:33 ` Ludovic Courtès
2019-03-23 19:10 ` Mark H Weaver
2019-03-23 21:04 ` Vagrant Cascadian
2019-03-24 18:19 ` Vagrant Cascadian
2019-03-06 12:02 ` swedebugia
2019-03-06 15:46 ` mikadoZero
2019-03-15 11:23 ` Ludovic Courtès
2019-03-15 17:39 ` Timothy Sample
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=87va0rzbze.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).