WinUAE QEMU PPC

[amigafreak68k]

Originally Posted by FOL

...and 1 and set unit 1 to CDROM bootable.

Hey!

Cool! This works great! I did remember that this never had worked for me on real CSPPC hardware and AmigaOS 3.x

The CD was never auto mount on Kick 3.x

Cool that this works for AmigaOS 4.x

[Toni Wilen]

Test version before next beta:

http://www.winuae.net/files/b/winuae.zip (QEMU stuff is unchanged)

GUI has (stupidly) named "Stopped M68K CPU idle mode" slider. This selects between 3 modes when only PPC CPU is active.

Leftmost: busy loop (like in previous beta), main thread uses 100% CPU all the time.
Middle: partial sleep
Right: Even more sleep

Middle/Right should reduce main thread CPU usage to less than 5% and possibly allows PPC-only emulation with single core CPU. EDIT: Please test even if you have multi-core CPU, reduced heat output and energy usage is also nice goal.

May cause other side-effects, report any weirdness (compared to b16) before beta is released, thanks.

[MickJT]

Can this slider be changed and have effect during emulation?

[Toni Wilen]

Originally Posted by MickJT

Can this slider be changed and have effect during emulation?

Yes

I'm back to tested morphos 1.4.5, next logs tomorrow. Old beta 10 -14 have most interest logs.

[Ami_GFX]

The Qemu PPC emulation definitely works in a single core CPU. I tested it on a 1.8ghz Pentium M laptop. I tried it first with the "Stopped M68K" slider in the middle. I tried OS3.9 and images loaded with WarpDT datatypes just about as fast as on a 1.8 ghz dual core laptop. Imagine PPC was very fast. OS4.0 took around 6 minutes to start but it was usable once it did. It was slow but not unbearably so and some things were slower than others. It took a long time to open a window but once a program was loaded, speed was OK. I ran ImageFX and loaded a couple of large images and there wasn't much delay.

Then I switched to the regular beta16. Not having the "Stopped M68K" slider didn't make that much difference. OS4.0 seemed a minute or so longer to load. Mixed 68K and PPC code in OS3.9 was about the same. There seems to be a delay when the PPC is first started but once it is engaged the first time, the delay is gone.

[thellier]

Celeron E3400 2.6 GHz
Time for booting
Beta 16: IDE 1'45
Beta 16: same but Accelecerator Board SCSI 1'23
this test version:same but 68k slider to Even more sleep 0'50

BRAVO You are a Master programmer :-)

Alain thellier

[thellier]

BTW disabling AGA chipset (I setted it to ECS) works too as OS4 dont use AGA for display

[Toni Wilen]

Timed from emulation start or when PPC starts? I count time from PPC CPU start (color flashes) because M68k boot time depends on m68k settings and JIT shouldn't be enabled.

[mulder77]

One observation with the test version.
When the OS 4.0 kernel has been started, I can't enter the ESM anymore.
I see a workbench screen and the mouse pointer works for some seconds, then it freezes.

With B16 the ESM works just fine.

[mulder77]

Here it takes 36 seconds until OS 4.0 is loaded (background and dock is loaded).
I took the time as soon as the PPC took over.

[thellier]

Timed from emulation start to os4's dock
I agree it include the 68k boot
but anyway is faster with new test version with 68k sleep slider

[Toni Wilen]

About 30 seconds sounds normal.

Everything should be fine if SND% is not worse than without new sleep option and there is no other slowdowns. (Sound is always the first that gets bad if timing is not good enough)

Im test new configuration for morphos 1.4.5. This ios logs from old beta core pearpc & new qemu

Only Old beta 10-14 trying boot mos after reset. After reset hd lead lights.
Beta 15 crashed
Beta 16 hmm, im stoped emulation becouse logs have only unassigned memory read & logs have too many mb after 1 min. emulation

[Toni Wilen]

Originally Posted by Agent_Pl

Im test new configuration for morphos 1.4.5. This ios logs from old beta core pearpc & new qemu

Only Old beta 10-14 trying boot mos after reset. After reset hd lead lights.
Beta 15 crashed
Beta 16 hmm, im stoped emulation becouse logs have only unassigned memory read & logs have too many mb after 1 min. emulation

Sorry but I don't care. I repeat: I don't debug PPC. Someone Else's Problem.

You have to enable max CPU board RAM size to prevent log messages.

[mulder77]

Just fyi, I made a quick mplayer test to get an impression of the current speed.

I ran the mplayer part of this test here: http://www.amiga-news.de/en/news/AN-...-00011-EN.html

I used the mplayer port from os4depot.net, not the MUI version as it claims to depend on 4.1.

It ran for 977 seconds, so roughly 1/6 of the speed of an G4@1GHz.

Of course, AltiVec might give quiet a boost to the performance.

[AnnaWu]

Originally Posted by AnnaWu

I think I go to the limits by using my "none" dual core (or higher) CPU and the Accelerator board SCSI.

AmigaOS 4.0
Accelerator board SCSI

After a while it show me the Kickstart screen. (see the attached screenshot)

2 questions:
1.) Can I use the same hard drive image which was installed by using the IDE controller or is a reinstallation necessary?
2.) Is the config ok? (JIT disabled, MMU disabled, CPU Idle disabled)

PS: The hard drive image with installed AmigaOS 4.0 is working with the IDE controller.

Thanks a lot for the great number of answers.
Beta 16
After a new installation (hard drive image) with the Accelerator board SCSI controller it is working (bootable) by using the single core CPU.

PS: Test version (17.09.2014)
"Stopped M68K CPU idle mode" slider: with the left or middle position the hard drive image won't run, with the right position it is working.

[zouzou]

Yesterday; b16 was firing OS4.1.
- after a reboot ctrl+a+a system is really weird. I have grimreaper poping up in boot process, or just after (so I do "reset" on winuae window).winuae doesn't crash, but sometimes it says last user was not closed properly.
- network I don't know why; but ping doesn't work (no reply), when traceroute works...
- scsi thing is really nice.
- it seems that if i don't attach a hard drive or cdrom in scsi accelerator, then I can't go in cyberstorm boot menu
- it seems that if I do for exemple remove the cdrom is hd&cd config in winuae, it's not always taken into account (better close winuae and relaunch)

still, I hope i would be able to see pc drives at starup (hangs the boot actually), or simply attach a directory from pc side, those things doesn't work actually.

Actually, the only thing I haven't managed to resolve is how to affect more memory to the system, it seems I can add Z3 ram without crashing anything, but it doesn't seems to show up in OS4 (and it was said somewhere in winuar forums that os4 has to be patched, too technic for me^^).

[Toni Wilen]

Originally Posted by AnnaWu

Thanks a lot for the great number of answers.

No answer in 2 days: I forgot to reply.

"Stopped M68K CPU idle mode" slider: with the left or middle position the hard drive image won't run, with the right position it is working.

"Not working" report = you do know what it means. Also, "works for me".

Originally Posted by zouzou

Yesterday; b16 was firing OS4.1.
- after a reboot ctrl+a+a system is really weird. I have grimreaper poping up in boot process, or just after (so I do "reset" on winuae window).winuae doesn't crash, but sometimes it says last user was not closed properly.

Reset working strangely was mentioned in b16 changelog. Fixed in next beta.

- network I don't know why; but ping doesn't work (no reply), when traceroute works...

slirp does not support ICMP protocol, UDP and TCP only.

- it seems that if i don't attach a hard drive or cdrom in scsi accelerator, then I can't go in cyberstorm boot menu

Yes you can, you need to be faster or enable 1s delay option in misc panel. You also may need to press ESC, release it, press it again and keep it pressed.

- it seems that if I do for exemple remove the cdrom is hd&cd config in winuae, it's not always taken into account (better close winuae and relaunch)

Not all options work without restart.

still, I hope i would be able to see pc drives at starup (hangs the boot actually), or simply attach a directory from pc side, those things doesn't work actually.

Hightly unlikely (at least not without support and more), it depends heavily on m68k code being executed by UAE m68k, not some software emulator.

Actually, the only thing I haven't managed to resolve is how to affect more memory to the system, it seems I can add Z3 ram without crashing anything, but it doesn't seems to show up in OS4 (and it was said somewhere in winuar forums that os4 has to be patched, too technic for me^^).

OS4 only support accelerator on board RAM. Emulator can't remove software limits.

[AnnaWu]

"Not working" report = you do know what it means. Also, "works for me".

I meant "Not booting"

To send the log file from the unofficial beta (test version) does not make sense, right?