From: "k.st via 9fans" <9fans@9fans.net>
To: <9fans@9fans.net>
Cc: <9front@9front.org>
Subject: [9fans] 9front on rpi4 rev 1.4
Date: Wed, 23 Jun 2021 05:03:15 -0400 [thread overview]
Message-ID: <CCAVKCASYVR2.G3KS9EYBMFQZ@mu> (raw)
I recently acquired a new 2GB raspberry pi 4, tried to run
the 9front pi3 image on it, and got the exact same
sdhc: readerror intr 2008002 stat 1fff0000
error as mentioned in [1]. Strangely, the image works fine
on an old 4GB rpi 4 I have.
I don't think the memory difference matters here. The only
other difference I could notice is the "revision number" of
the two devices. The old rpi4 (working) is revision 1.2,
linux$ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
Hardware : BCM2711
Revision : c03112
Serial : [REDACTED]
Model : Raspberry Pi 4 Model B Rev 1.2
while the new model (not working) is revision 1.4
linux$ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 126.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 126.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 126.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 126.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
Hardware : BCM2711
Revision : b03114
Serial : [REDACTED]
Model : Raspberry Pi 4 Model B Rev 1.4
I'm not sure about the exact hardware difference between the
two revisions, though one thing I notice is that the older
model seems to have a dedicated EEPROM for VL805 USB firmware
linux$ sudo rpi-eeprom-update
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
LATEST: Thu 29 Apr 2021 04:11:25 PM UTC (1619712685)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Use raspi-config to change the release.
VL805_FW: Dedicated VL805 EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
while the newer model doesn't:
linux$ sudo rpi-eeprom-update
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Tue 16 Feb 2021 01:23:36 PM UTC (1613481816)
LATEST: Thu 29 Apr 2021 04:11:25 PM UTC (1619712685)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
I'm not sure how this affects the booting of 9front. I can
confirm the firmware difference doesn't matter. I downgraded
the newer model's firmware to 03 Sep 2020, still got the
same error.
However, Richard Miller's 9pi image does work on the newer
model. Maybe something needs to be backported to 9front.
I also tried to boot freebsd on this newer model of rpi4 and
ran into a similar issue (works on old model, doesn't work
on new model). There are some discussions on the freebsd
forum that might be related
- https://forums.freebsd.org/threads/stuck-in-u-boot-during-freebsd-13-install-on-raspberry-pi-400.79941/
- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255080
The fix proposed in [2] works, but it doesn't apply to
9front.
Does anyone have any successes with booting 9front on a rpi4
rev 1.4?
- kst
[1]: https://inbox.vuxu.org/9front/0100017720d2f6b4-a93bc058-3523-49a3-99c9-41d030c74716-000000@email.amazonses.com/T/#u
[2]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255080#c15
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T1ea264b2fb0c5c69-M8f51bd53f065577b7e5a1541
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2021-06-23 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:03 k.st via 9fans [this message]
2021-06-23 10:29 ` hiro
2021-06-24 0:21 ` kst via 9fans
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=CCAVKCASYVR2.G3KS9EYBMFQZ@mu \
--to=9fans@9fans.net \
--cc=9front@9front.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).