I see, thanks.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T5da5467097e4eab2-M0fe5284a21a2266220ee5409
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On Thursday, 14 September 2023, adr via 9fans <9fans@9fans.net> wrote:
Hi Richard. I'm surprised by the small number of 9legacy patches you are
> using. Any reason in particular that you could share? I'm preparing a new
> installation and this is a good time to choose the starting point.
>
>
The 9
> I've put a script in contrib/miller/build-9pi.rc which shows the complete
process of building (almost) the 9pi image from the 4th edition ISO. You
can look at that to see what 9legacy patches are applied.
Hi Richard. I'm surprised by the small number of 9legacy patches you are using.
Any reason
> the system loads into the GUI but then hangs moments later and stops
> updating the frame buffer, or the system is hung. Any thoughts on why that
> might have occurred? Is this to do with the watchdog...?
It won't be the watchdog, because this QEMU patch prevents it
from being enabled.
archbcm2
> The thing about 9legacy is I'm not sure what patches to pull and what is or
> isn't stable do you have any recommendations?
I've put a script in contrib/miller/build-9pi.rc which shows the complete
process of building (almost) the 9pi image from the 4th edition ISO. You
can look at that to s
> I didn't realize 9legacy actually had a distribution for some reason I
> thought it was only a patch set applied against the old main line. Glad I
> don't have to pick apart the patch set that (works)...
yes. i was expecting this confusion will arise some day. officially
it's a spoon, nor a fork
Ok I pulled a 9legacy ISO, applied your patch set from this thread above,
and built a 9pi2 kernel. My build now runs as the kernel on a QEMU
raspi2b system.
I didn't realize 9legacy actually had a distribution for some reason I
thought it was only a patch set applied against the old main line. Gla
Yeah it must be patches in 9legacy because pulling the bcm from contrib
and using that does not alone fix the kernel.
Interestingly, I can get a kernel to boot in a raspi1ap emulated image, but
it faults on what I presume is the jump to userland, resets, and auto-boots
the kernel again in an i
> Based on the diffs you supplied, it looks like my bcm
> sources (from the latest r4 ISO) are not the same as yours. I don't use
> 9front. What is the best way to make sure my bcm (and 9) kernel trees are
> the same as your current tree?
A lot has changed in the bcm kernel since the 4th edition I
Took a minute to snarf your 9pi2.qemu off of contrib and run it on my
8.0.0... (it wasn't there last night; depends on when 9pio syncs the web
interface, I suppose)
It runs just peachy. Based on the diffs you supplied, it looks like my bcm
sources (from the latest r4 ISO) are not the same as yours
> I'm using version 8.0.0 of QEMU. What version are you using, Mr. Miller?
I've now reinstalled QEMU from debian unstable, which gives me v8.0.4.
Using the 9pi2.qemu in my contrib, it still boots for me, without any
loop at 0x000c.
--
9fans: 9fans
Perm
> > Maybe do the back & forth off list, unless anyone else is interested?
> I'm very interested in learning both about the process and about the
> result. Unless others object, I'd like to follow along here.
Same. Lurking and learning.
On 9/1/23, Richard Miller <9f...@hamnavoe.com> wrote:
> don.bai...@gmail.com:
...
>> Thanks for responding and adding some patches. I am trying to follow
>> along
>> to make it work, if you don't mind a bit of back and forth :-)
>
> Maybe do the back & forth off list, unless anyone else is interest
don.bai...@gmail.com:
> Hmm, I've applied the patches and built the kernel. I can see the image
> loaded at 0x8001, but it is spinning at address 0x000c; is this a
> sdmmc load loop?
I think that's a trap address. On ARM we re-map the trap vectors away from
address 0 to a high segment.
>
Hmm, I've applied the patches and built the kernel. I can see the image
loaded at 0x8001, but it is spinning at address 0x000c; is this a
sdmmc load loop?
I'm using version 8.0.0 of QEMU. What version are you using, Mr. Miller?
Also, since the SD takes seconds to load and not ms/us, how lo
don.bai...@gmail.com:
> So to get this back on the track of RPI emulated in QEMU … has anyone
> successfully used the Miller image with Q?
After a bit of experimentation, I have done so, for some value of
"successfully".
A few tweaks are required first, because QEMU's emulation of Pi hardware a
So to get this back on the track of RPI emulated in QEMU … has anyone
successfully used the Miller image with Q?
D
> On Aug 26, 2023, at 7:49 AM, hiro <23h...@gmail.com> wrote:
>
> ah no i was wrong. first google result "KVM support is available only
> for 64-bit ARM architecture (AArch64"
> o
Hosting options are quite limited though, there's Hetzner and actually also Arm
Virtual Hardware but I couldn't get 9front running there. And at least on real
hardware running 32 bit on aarch64 seems to work. Also on macOS qemu there's
hardware acceleration. I've tried that as well but I think I
ah no i was wrong. first google result "KVM support is available only
for 64-bit ARM architecture (AArch64"
oh well
On Sat, Aug 26, 2023 at 1:45 PM mkf wrote:
>
> I believe KVM on aarch64 would help aarch64 guests.
> i could be wrong.
>
> On Sat, 26 Aug 2023 13:39:01 +0200
> hiro <23h...@gmail.co
I believe KVM on aarch64 would help aarch64 guests.
i could be wrong.
On Sat, 26 Aug 2023 13:39:01 +0200
hiro <23h...@gmail.com> wrote:
> why do you assume kvm helps with emulating a raspberry?
> kvm helps virtualize amd64 on amd64, and shouldn't be usable for much else.
-
mkf
-
why do you assume kvm helps with emulating a raspberry?
kvm helps virtualize amd64 on amd64, and shouldn't be usable for much else.
On Sat, Aug 26, 2023 at 11:25 AM Philip Silva via 9fans <9fans@9fans.net> wrote:
>
> Hi,
>
> I've only tried qemu with 9front and this got me to a console (the file
Hi,
I've only tried qemu with 9front and this got me to a console (the files in
dos/ are from the image):
EXTRA_ARGS='user=glenda nobootprompt=local!/dev/sdM0/fs virtio nousbrc='
qemu-system-aarch64 -M raspi3b -dtb dos/bcm2711-rpi-4-b.dtb -kernel dos/9PI3
-append "console='1 b9600' core_freq=2
Has anyone gotten Miller's RPI image to boot in QEMU? I'm trying to use -M
raspi1, raspi2, and versatilepb, but nothing boots. I'm using the 9pi
kernel image (both 9pi2 and 9pi4) from contrib and -hda ./9pi.img. Any
advice?
Thanks,
D
--
9fans: 9fans
Permali
23 matches
Mail list logo
