From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing
Date: Sun, 17 Nov 2019 09:02:30 +0900 [thread overview]
Message-ID: <97C9B1C68E00FDE011306B2CA8588800@hera.eonet.ne.jp> (raw)
In-Reply-To: 90CF5F74EED92E387C5F75BBC29B8621@antares-labs.eu
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
Ok, this is my present settings and the output results.
/sys/src/9/bcm/pi2wifi:
dev
root
cons
swap
env
pipe
proc
mnt
srv
shr
dup
arch
ssl
tls
cap
fs
ether netif
ip arp chandial ip ipv6 ipaux iproute netlog nullmedium pktmedium inferno
draw screen swcursor
mouse mouse
uart gpio
gpio gpio
sd
usb
# dtracy
link
loopbackmedium
ethermedium
archbcm2
sdhost
usbdwc
# etherusb
ether4330 emmc
ip
tcp
udp
ipifc
icmp
icmp6
ipmux
misc
armv7
uartmini
uartpl011
sdmmc emmc
dma
vcore
vfp3 coproc
irq
# wifi
# dtracysys
# dtracytimer
port
int cpuserver = 0;
boot boot #S/sdM0/
local
tcp
tls
bootdir
/$objtype/bin/paqfs
/$objtype/bin/auth/factotum
/$objtype/bin/aux/wpa
/lib/firmware/brcmfmac43430-sdio.bin
/lib/firmware/brcmfmac43430-sdio.txt
/lib/firmware/brcmfmac43455-sdio.bin
/lib/firmware/brcmfmac43455-sdio.txt
/lib/firmware/brcmfmac43455-sdio.clm_blob
bootfs.paq
boot
====out put====
many lines of
#xxx: 4330: 10 Mbps port 0x0 irq -1 ea 000000000000
...
998M memory: 403M kernel data, 595M user, 3573M swap
cpu1: 1200MHz ARM Cortex-A53 r0p4
cpu2: 1200MHz ARM Cortex-A53 r0p4
cpu3: 1200MHz ARM Cortex-A53 r0p4
ether4330: chip 43430 rev 1 type 1
ether4330: firmware ready
ether4330: addr <my rpi3's MAC address>
ether3220: no response to sdio access: ocr=0
ether3220: no response to sdio access: ocr=0
ether3220: no response to sdio access: ocr=0
/dev/sdM0: BCM SDHost Controller
/dev/sdM0/data
/dev/sdM0/dos dos
/dev/sdM0/fs hjfs
/dev/sdM0/nvram
/dev/sdM0/plan9
bootargs is (tcp, tls, il, local!device) [tls]
user[glenda]: sys
ipconfig: ...
ipconfig: can't start IPv6 on /net/ether0
emmccmd: need to reset Cmdinhibit intr 0 stat 1ff0106
emmccmd: need to reset Datinhibit intr 0 stat 1ff0106
emmcio: timeout intr 208010 stat 1ff0106
ether4330: sdiorwext fail: i/o error
ipconfig: no success with DHCP
/bin/tlsclient: dial tcp!<my file server's IP address>!17020: no route
mount: can't open #s/boot: '#s/boot' file does not exist
mount -c #s/boot /root: mount 267: open
---
return to login prompt
[-- Attachment #2: Type: message/rfc822, Size: 2165 bytes --]
From: rgl@antares-labs.eu
To: 9front@9front.org
Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing
Date: Sat, 16 Nov 2019 11:04:35 +0100
Message-ID: <90CF5F74EED92E387C5F75BBC29B8621@antares-labs.eu>
hi kenji,
> However, to get the / filesystem from a file server to boot the system,
> which is in my case, how I can preset the factotum for wpapsk before the root filesystem
> mounted? To mount the root I need to connect to the file sever, but I have no wifi setup yet.
for that you will need to add the credentials to the bootfs.paq that's
embedded in the kernel. if your card needs some firmware, make sure
you have it in /lib/firmware before you mk and deploy the new kernel.
you'll find everything you need in /sys/src/9/boot. i actually wanted
to do this some time ago, but i ended up with a standalone
installation on the laptop.
please tell us how it goes. :)
-rodri
next reply other threads:[~2019-11-17 0:02 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 0:02 kokamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-27 2:18 kokamoto
2019-12-05 5:19 kokamoto
2019-11-21 1:14 kokamoto
2020-05-31 8:51 ` Iruatã Souza
2020-06-01 23:07 ` kokamoto
2019-11-20 0:20 kokamoto
2019-11-21 0:23 ` hiro
2019-11-20 0:09 kokamoto
2019-11-18 9:45 umbraticus
2019-11-17 23:34 kokamoto
2019-11-17 23:37 ` Kurt H Maier
2019-11-17 18:33 cinap_lenrek
2020-06-20 11:39 ` Iruatã Souza
2019-11-17 6:23 kokamoto
2019-11-17 0:04 kokamoto
2019-11-16 16:48 cinap_lenrek
2019-11-16 10:04 rgl
2019-11-16 9:29 kokamoto
2019-11-16 1:08 cinap_lenrek
2019-11-15 9:13 kokamoto
2019-11-15 6:58 rgl
2019-11-15 2:27 ori
2019-11-15 2:18 kokamoto
2019-11-15 0:21 kokamoto
2019-11-04 0:55 kokamoto
2019-10-21 4:19 kokamoto
2019-10-20 7:38 ori
2019-10-20 6:15 kokamoto
2019-10-20 0:37 cinap_lenrek
2019-10-20 9:13 ` Steve Simon
2019-10-20 13:48 ` hiro
2019-10-19 23:07 kokamoto
2019-10-19 0:13 kokamoto
2019-10-17 10:15 kokamoto
2019-10-16 23:29 kokamoto
2019-10-15 3:53 kokamoto
2019-09-30 0:31 kokamoto
2019-09-29 1:17 kokamoto
2019-09-29 4:27 ` Sean Hinchee
2019-09-29 20:43 ` hiro
2019-09-28 0:54 kokamoto
2019-09-28 18:48 ` Ethan Gardener
2019-09-28 19:43 ` Julius Schmidt
2019-09-28 23:35 ` hiro
2019-09-28 0:10 kokamoto
2019-09-28 1:24 ` Julius Schmidt
2019-09-28 7:43 ` hiro
2019-09-27 1:51 cinap_lenrek
2019-09-27 4:58 ` Roman Shaposhnik
2019-09-27 1:28 cinap_lenrek
2019-09-27 1:48 ` Roman Shaposhnik
2019-09-27 1:06 kokamoto
2019-09-27 10:22 ` Julius Schmidt
2019-09-26 14:35 cinap_lenrek
2019-09-26 9:58 kokamoto
2019-09-26 12:12 ` hiro
2019-09-26 3:50 kokamoto
2019-09-26 6:44 ` hiro
2019-09-26 0:04 kokamoto
2019-09-24 23:19 kokamoto
2019-09-24 22:45 cinap_lenrek
2019-09-24 21:51 kokamoto
2019-09-24 21:30 kokamoto
2019-09-24 21:22 kokamoto
2019-09-24 11:13 cinap_lenrek
2019-09-24 5:24 kokamoto
2019-09-23 17:24 cinap_lenrek
2019-09-23 1:44 cinap_lenrek
2019-09-23 2:00 ` Kenji Okamoto
2019-09-23 1:41 kokamoto
2019-08-23 20:16 cinap_lenrek
2019-08-21 14:35 cinap_lenrek
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=97C9B1C68E00FDE011306B2CA8588800@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).