From: Mack Wallace <mackbw@mapinternet.com>
To: 9front@9front.org
Subject: Re: [9front] 9front on Raspberry Pi 400
Date: Mon, 1 Feb 2021 01:16:10 +0000 [thread overview]
Message-ID: <010001775b29508b-f00eff0b-cb58-4309-9a93-0351e1ebead3-000000@email.amazonses.com> (raw)
In-Reply-To: <26D80F90D2AA2D071991B86445F43BC6@felloff.net>
Ok, cool, we have progress. Keyboard and mouse work now. However, still those pesky sdhc errors.
I tried typing in local!/dev/sdM0/data, it then prompted me for the user account, which I accepted the default, glenda. Upon entering, I get even more sdhc errors, along with an unknown file system.
Also just noticed. We seem to be missing a CPU during detection. Running another time, I see cpu1 and cpu2 detected, but not 3. - After that, I’m consistently detecting cpus 1, 2, and 3.
Mack
127 holes free
0x00500000 0x3e600000 1041235968
1041235968 bytes free
Plan 9
intrsoff: GIC intids [0-31]: 01ff0000 are locked in disable state
intrsoff: GIC intids [0-31]: 0000ffff are locked in enable state
cpu0: 1800MHz ARM Cortex-A72 r0p3
4006M memory: 998M kernel data, 3008M user, 15011M swap
*pciwin: 0x600000000 0x640000000
*pcidmawin: 0x400000000 0x500000000
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 mema:600000000-600100000 1048576 ->1
1 0/0 0c 03 30 1106 3483 0 0:600000004 4096
#l0: genet: 1000Mbps port 0xFFFFFFFFBD580000 irq 189 ea dca632e63357
usbxhci: cpu2: 1800MHz ARM Cortex-A72 r0p3
cpu1: 1800MHz ARM Cortex-A72 r0p3
cpu3: 1800MHz ARM Cortex-A72 r0p3
0x1106 0x3483: port 600000000 size 4096 irq 0
#l0: phy1 id 600d84a2 oui 80361
sdhc: read error intr 2008002 stat 1fff0000
sdhc: read error intr 2008002 stat 1fff0000
...
sdhc: read error intr 2008002 stat 1fff0000
/dev/sdM0: BCM SD Host Controller 02 Version 10
sdhc: read error intr 2008002 stat 1fff0000
...
sdhc: read error intr 2008002 stat 1fff0000
/dev/sdM0/data
bootargs is (tcp, tls, il, local!device)[] local!/dev/sdM0/data
user[glenda:
sdhc: read error intr 2008002 stat 1fff0000
...
sdhc: read error intr 2008002 stat 1fff0000
unknown fstype /dev/sdM0/data
/dev/sdM0: BCM SD Host Controller 02 Version 10
sdhc: read error intr 2008002 stat 1fff0000
...
sdhc: read error intr 2008002 stat 1fff0000
> On Jan 30, 2021, at 2:46 PM, cinap_lenrek@felloff.net wrote:
>
> ok, sorry.... it was my mistake! the sha1sum now matches.
>
> --
> cinap
>
prev parent reply other threads:[~2021-02-01 2:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 17:23 Mack Wallace
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 [this message]
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=010001775b29508b-f00eff0b-cb58-4309-9a93-0351e1ebead3-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).