From: aisecat <aisecat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] rpi-kernel: Support for Raspberry Pi 4
Date: Thu, 27 Aug 2020 15:20:02 +0200 [thread overview]
Message-ID: <20200827132002.3LwJpoeRku4kwPusr0WqD0uCFHkxTFcOxYZN3w-AgVE@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: 857 bytes --]
New comment by aisecat on void-packages repository
https://github.com/void-linux/void-packages/pull/23541#issuecomment-681944401
Comment:
@PaperMountainStudio At this point I'm just not sure what would be different between our setups, I tried following the instructions above exactly and got a working image. If your /boot partition contains the correct kernel, dts, and the latest firmware, it should work, there's nothing really special required to boot void. Unless something went wrong with your build environment, I would start trying different SD cards. Did you try using the same SD card with void that boots the 64bit Raspberry Pi OS?
Then if the problem is not the SD card, I would make a fresh build environment and also make very sure that the mkplatformfs script pulls in the locally built kernel package, and not the one from a remote repo.
next prev parent reply other threads:[~2020-08-27 13:20 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
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 [this message]
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=20200827132002.3LwJpoeRku4kwPusr0WqD0uCFHkxTFcOxYZN3w-AgVE@z \
--to=aisecat@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).