From: nathanblair <nathanblair@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] rpi-kernel: Support for Raspberry Pi 4
Date: Sun, 19 Jul 2020 02:03:20 +0200 [thread overview]
Message-ID: <20200719000320.p4_h-vpyvUW9UhzlZ_FcstU7B7ajCjWZg7nRz1E08CI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
New comment by nathanblair on void-packages repository
https://github.com/void-linux/void-packages/pull/23541#issuecomment-660533976
Comment:
Also, I did this through alpine on WSL (lol long story - new PC and I haven't gotten my new SSD that I can put a host VoidLinux on XD)
Buuuuuttttttttttttttttttt...I needed to install a non-busybox versions of `tar` _and_ `xz`. It was a little misleading as tar would fail on the last output step (creating the tar of the rootfs and such) but the `*.tar.xz` file would be created. I forgot to pay attention to the fact that `ls` reported a size of 0 for each of the tarballs and when I tried to extract them where they needed to go of course `tar` blew up and I was dumbfounded until I realized the tars were empty 😆
Anyway, just a heads-up!
EDIT: Thus far, I've been unsuccessful with this method. But I don't think that's a fault of the OS and the procedure; my suspicion is that my RPi4 has crapped out or that the HDMI-out port has or...something else. I've got some mSD cards on the way to try an Alpine Linux boot as well as the conventional (ugh systemd) Raspbian.
next prev parent reply other threads:[~2020-07-19 0:03 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 1:52 [PR PATCH] " agausmann
2020-07-13 1:52 ` agausmann
2020-07-13 1:57 ` pbui
2020-07-13 9:26 ` [NOMERGE] " Piraty
2020-07-13 13:14 ` Piraty
2020-07-13 13:15 ` Piraty
2020-07-14 1:38 ` fosslinux
2020-07-14 5:11 ` agausmann
2020-07-14 5:12 ` agausmann
2020-07-14 5:12 ` agausmann
2020-07-14 5:13 ` agausmann
2020-07-14 9:24 ` fosslinux
2020-07-18 19:41 ` nathanblair
2020-07-18 19:55 ` nathanblair
2020-07-18 19:56 ` nathanblair
2020-07-19 0:03 ` nathanblair [this message]
2020-08-09 15:14 ` MGlolenstine
2020-08-09 15:15 ` MGlolenstine
2020-08-09 16:00 ` ericonr
2020-08-09 16:01 ` MGlolenstine
2020-08-09 18:40 ` ericonr
2020-08-09 19:01 ` MGlolenstine
2020-08-16 20:12 ` Yuvalhad12
2020-08-16 22:08 ` MGlolenstine
2020-08-17 7:59 ` agausmann
2020-08-17 8:00 ` agausmann
2020-08-17 8:09 ` MGlolenstine
2020-08-17 16:05 ` PaperMountainStudio
2020-08-17 16:05 ` PaperMountainStudio
2020-08-17 16:08 ` MGlolenstine
2020-08-22 19:31 ` aisecat
2020-08-27 12:12 ` PaperMountainStudio
2020-08-27 13:20 ` aisecat
2020-08-27 13:22 ` MGlolenstine
2020-08-27 13:27 ` aisecat
2020-08-27 15:22 ` PaperMountainStudio
2020-08-27 20:15 ` PaperMountainStudio
2020-08-27 20:43 ` aisecat
2020-08-27 20:54 ` aisecat
2020-08-27 23:12 ` br0qn
2020-08-27 23:14 ` ericonr
2020-08-27 23:43 ` br0qn
2020-08-28 1:37 ` br0qn
2020-08-28 1:45 ` br0qn
2020-08-28 6:50 ` PaperMountainStudio
2020-08-28 7:04 ` PaperMountainStudio
2020-08-28 13:29 ` jsumners
2020-08-28 17:24 ` [PR PATCH] [Updated] " agausmann
2020-08-28 17:25 ` agausmann
2020-08-28 21:18 ` jsumners
2020-08-29 22:07 ` br0qn
2020-08-29 22:15 ` br0qn
2020-08-29 23:31 ` br0qn
2020-08-29 23:33 ` br0qn
2020-08-30 0:54 ` jsumners
2020-08-30 8:38 ` PaperMountainStudio
2020-08-30 16:43 ` jsumners
2020-10-05 18:57 ` Frick-David
2020-10-06 8:17 ` Piraty
2020-10-28 18:51 ` BikyAlex
2020-10-28 19:37 ` agausmann
2020-10-28 19:37 ` agausmann
2020-10-28 19:37 ` agausmann
2020-11-01 20:48 ` Piraty
2020-11-01 20:49 ` Piraty
2020-11-01 20:49 ` Piraty
2020-11-01 20:49 ` [PR PATCH] [Closed]: " Piraty
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=20200719000320.p4_h-vpyvUW9UhzlZ_FcstU7B7ajCjWZg7nRz1E08CI@z \
--to=nathanblair@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).