SysInfo reports AGA as does set patch. No AGA!
 

A4000 with 40.68 roms, WB3.1, and Buster v11. PICASSOIV with last firmware, Cyberstorm Mk1 68060 with last official updates, Tocatta.

All Amiga screen options in Prefs are NON AGA. Games and apps complain they can't open AGA screens.

??

AFAIK aga chipset will get activated by c:setpatch command in your startup-sequence.

just start it in the cli/shell and post the results here. inlc version string:
version c:setpatch

Setpatch is running and when running again
It says it's already on.

lol?! how would games and demos with custom boot loaders work exactly?

I wonder if the 68040 and 68060 library files from Phase5 might be causing an issue?

see attached image, and read here, for example.

you can try the MmuLib from aminet.

I'm seeing what you're showing in that image. Yet no AGA.

By using the hardware to check for AGA chipset. System friendly software does rely on Setpatch for that!

Battery damage side-effect? SetPatch under A4000 detects AGA differently than A1200.

http://eab.abime.net/showthread.php?t=75663

Sadly looking more and more batteey damage. At least there's some redundacy with the ECS. Forward thinking in design? Heh.

I had no idea it had to be enabled for WB, it seems a bit silly to have to enable it with software it should be the default status. You learn something new everyday!

It's possibly for improved compatibility with older ECS software when booting from floppy. AGA software that doesn't use the OS doesn't need to have it enabled by SetPatch so it doesn't make a difference there.

As Toni says, it sounds like motherboard damage unfortunately...

Believe it or not but even the early boot menu doesn't display right if you enable AGA before it gets displayed. We tried this in the Vampire test cores with AGA enabled right after power up / reset. It turned out that the early boot menu only displays fine if you start in ECS mode. I think the reason was the DMA fetch mode and the copper lists being set up wrong for the wide AGA fetch mode.

And why did you tried to enable AGA before Early-Startup-Menu?

Because we naively thought that an AGA machine is an AGA machine right from the start.

I would say an AGA machine is an AGA machine right from the start and I guess the average user too. However, what was the reason/goal for enable AGA before Early-Startup-Menu? E.g. have AGA screenmodes available for the menu? Other interesting stuff?

Not sure we are on the same page. The Apollo Team is currently implementing AGA as part of the Vampire Card for A500 and A600. This means that Vampire equipped A500s and A600s will not only have a superfast 68080 processor, RTG capabilities, 128 MB of lightning fast RAM and some more but will soon also have AGA capabilities. In one early test core this AGA add-on was running in AGA mode right from power-up which made us find out that this is not the way of doing it.

It seemed to be an interesting bit of information that even the very system itself cannot deal with that thus showing a messed up early startup Screen which is why I wanted to share this.

So now I need to sell my A4000 with its, PicassaIV, Tocatta, and 64mb 50mhz 68060 for an A500 and an Apollo card? :)

Karma.

no AGA on A4k.. well Batteryleakage have damaged the board. a (quite easy) repair is needed to be done.