all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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, 16 Mar 2019 23:47:58 -0700	[thread overview]
Message-ID: <874l82ngip.fsf@ponder> (raw)
In-Reply-To: <87va0rzbze.fsf@ponder>

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

On 2019-03-09, Vagrant Cascadian wrote:
> 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...

With libreboot re-installed, it's working for me as well!

I haven't tried just applying the minimal patches and/or configuration
on top of Guix's linux-libre, but that seems like a logical next step...


> 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"))

To be clear, this feature doesn't actually make a serial console over
USB, it somehow "rewires" one of the USB ports to have a ground, rx and
tx serial-ttl pinout. So you pretty much need a custom USB-A plug and
solder/crimp the bare wires to a serial-ttl adapter. Slightly more
details in Documentation/admin-guide/kernel-parameters.txt.


live well,
  vagrant

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

  reply	other threads:[~2019-03-17  6:48 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
2019-03-17  6:47       ` Vagrant Cascadian [this message]
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

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

  git send-email \
    --in-reply-to=874l82ngip.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 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.