9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Mack Wallace <mackbw@mapinternet.com>
To: 9front@9front.org
Subject: [9front] 9front on Raspberry Pi 400
Date: Wed, 20 Jan 2021 17:23:52 +0000	[thread overview]
Message-ID: <0100017720d2f6b4-a93bc058-3523-49a3-99c9-41d030c74716-000000@email.amazonses.com> (raw)

I have been trying to get 9 on my recently purchased Raspberry Pi 400, but have been running into some roadblocks. For better or worse, I started with the 9fans group and have managed to get labs 9 working. However, that lacks the 9front tools that I need to do things like rcpu, etc. 

So while I have had a bit of history trying to make this work, I’ll give you the most recent iteration. 

I used balenaEtcher to write the most recent pi3 image to a micro SD card. Upon booting that, I get the following;


127 holes free
0x004f0000 0x3e600000 1041301504
1041301504 bytes free

Plan 9
cpu0: 1500 MHz ARM Cortex-A72 r0p3
4006M Memory: 998M kernel data, 3008M user, 15011M swap
pcienable PCI.0.0.0: pcr 0->7
pcienable PCI.1.0.0: pcr 0->2
bus dev type     vid  did  intl memory
0   0/0 06 04 00 14e4 2711   0  ioa:00000000-00001000 4096 nema:600000000-600100000 1048576 ->1
1   0/0 0c 03 30 1106 3483   0  0:600000007 4096
#l0: genet: 1000Mbps port 0xFFFFFFFFBD580000 irq 189 ea dca632e63357
usbxhci: 0x1106 0x3483: port 600000000 size 4096 irq 0
cpu3: 1500MHz ARM Cortex-A72 r0p3
cpu2: 1500MHz ARM Cortex-A72 r0p3
cpu1: 1500MHz ARM Cortex-A72 r0p3
#l0: phy1 id 600d84a2 oui 80361
sdhc: readerror intr 2008002 stat 1fff0000
	{repeats 15 times}
/dev/sdM0: BCM SD Host Controller 02 Version 10
sdhc: readerror intr 2008002 stat 1fff0000
	{repeats 40 or so times}
/dev/sdM0/data
bootargs is (tcp, tls, il, local!device)[]


In my many times trying different things, I have had a few other errors. However, what I am showing is what I am getting now consistently having done the following.
I’ve replaced the Pi firmware files with the latest at of today. I then added ‘enable_gic=1’ to the config.txt file with no change.

Consistent amongst the previous attempts were the same one or two errors repeated many times, and not keyboard or mouse response (not surprising as the newer Pis need to have their usb firmware uploaded in the kernel). 

In case there were newer updates to the source, I did a sysupdate on a laptop I have with 9 and then tried to cross-compile a new kernel. However, I get a much smaller kernel (only 2.9MB rather than the 4.4MB in the 9front Pi image. I don’t know if this is unexpected. When I try to boot that kernel. The console screen comes up. But after CPU detection, the kernel panics and stops booting. I presume this is a problem with my compilation, (or myself) so I won’t clutter things up here with that kmesg unless asked for it. 

Hope someone has some guidance.


Thanks in advance!

Mack

             reply	other threads:[~2021-01-20 17:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:23 Mack Wallace [this message]
2021-01-23 16:11 ` cinap_lenrek
2021-01-23 21:08   ` Mack Wallace
2021-01-23 21:13   ` Mack Wallace
2021-01-23 23:42     ` cinap_lenrek
2021-01-24 15:01       ` cinap_lenrek
2021-01-26  3:33         ` Mack Wallace
2021-01-26  3:35         ` Mack Wallace
2021-01-26 11:21           ` cinap_lenrek
2021-01-26 12:09           ` cinap_lenrek
2021-01-27  2:32             ` Mack Wallace
2021-01-27 14:30               ` cinap_lenrek
2021-01-27 17:04               ` cinap_lenrek
2021-01-27 17:57               ` cinap_lenrek
2021-01-29 14:58               ` cinap_lenrek
2021-01-30  2:43                 ` Mack Wallace
2021-01-30  5:54                   ` cinap_lenrek
2021-01-30 19:23                     ` Mack Wallace
2021-01-30 19:41                       ` cinap_lenrek
2021-01-30 19:46                       ` cinap_lenrek
2021-02-01  1:16                         ` Mack Wallace

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=0100017720d2f6b4-a93bc058-3523-49a3-99c9-41d030c74716-000000@email.amazonses.com \
    --to=mackbw@mapinternet.com \
    --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).