I just happened to stumble upon HAM's video and was curious, as I've never had these startup issues with my A1200. But I have a PAL unit (my only PAL Amiga), and I'm noticing everybody reporting issues seems to have an NTSC Amiga. Does that perhaps have something to do with it? Is anyone with a PAL Amiga having these issues with the Mk3 failing to start on its own?
Posts by kevbrice
Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
Don't Panic. Please wash hands.
-
-
https://gitlab.com/MHeinrichs/A500-GraKa
Works like a charm
This is identical to what's on Aminet. 🙂 It also works fine for me, and I'm not aware of anything newer.
-
Great, thanks, Jens.
-
I just upgraded two machines to 3.3.0 and belatedly discovered that if I increase the color depth, the screen becomes unusable upon switching back to the original lower color depth. Here's my repro on two different machines:
- Boot into 1024x768 8-bit
- Test another screen mode, like 1024x768 16-bit or 800x600 32-bit. It displays properly
- Return to the original mode. The picture is unreadable with the wrong colors, necessitating a reboot.
I'm using a GBAPII++ in both. I upgraded the CirrusGD5434 chipset driver when upgrading P96 by selecting Piccolo SD64. If I restore CirrusGD5434.chip from 3.2.4, the regression goes away.
-
Jens To be clear, we're both talking about this open-source card, right? https://gitlab.com/MHeinrichs/A500-GraKa
P96 already ships with the chipset driver for it. It just doesn't ship with the settings for it.
-
How confusing. I didn't think it had its own driver - just a pointer to use the already-bundled CirrusGD5434.chip.
-
Hi! I've got a GBAPII++ card, which uses the P96-bundled Piccolo SD64 driver. However, installing it is a bit of a kludge: you have to first tell P96 you're installing the Piccolo SD64, delete that monitor file, copy in a different monitor file from Aminet, and copy in a different settings/card file from Aminet. Is there any chance the P96 installer could just be enlightened to know about the GBAPII++, especially since it's just adding a card file and no additional drivers? Thanks!
-
That’s a rather different problem than the subject of this thread, no? 🙂 Might be best to start a new one.
That said, I don’t repro with my A2091, but I’ve got a GuruROM in mine. -
vinceb Are you sure you didn't make a typo? I just double-checked with " bigram help", and those are the right command arguments. And here's a post with Jens saying the exact same command five years ago
-
vinceb I may have made a mistake writing that from memory. I’m still not in front of my Amiga now, so you could run “BigRAM ?” to try and identify my mistake. Otherwise I can look later today.
-
vinceb The key is that when you send a configuration to the BigRAM, it completely replaces the old configuration and starts from scratch. So you need to send it one command that sets all configuration options you want, like this:
- Shut down your Amiga
- Set the jumper on the BigRAM to allow changing the configuration
- Run BigRAM <options>
- Shut down your Amiga
- Remove the jumper
The exact command I sent was:
If you were to subsequently send:
that would implicitly turn off maprom. Every option you want needs to be present every time you flash options with the BigRAM tool. I personally find this incredibly unintuitive, and it’s not really explained in the documentation. But if you think about it, that’s the only way it could work given the documentation since there are no command flags to turn off a feature.
You may not want maprom, especially if you’re using MuFastROM. I only added it because it worked around the BigRAM causing my SCSI controller to be dropped. Your mileage may vary. -
It looks like the installer does delete everything.
The reason this doesn't repro on my other A2000 turns out to, in fact, be the different accelerator. The issue is triggered by a confluence of three things:
- Updating graphics.library with AmigaOS 3.2.1
- P96 being activated
- CSA's autoboot driver for the Magnum 40/4 SCSI controller, which gets stored in the RDB
If I take the exact same disk and boot from a different SCSI controller, the crash goes away.
-
It’s one of the options in the installer, yeah. Failing that, can you share an exact list of all files P96 installs so I can delete them?
-
Okay, I will. How do I ensure I’m doing a clean install? Will the uninstaller option get everything?
-
Okay. Is there any sort of diagnostic mode on the P96 side I could enable to possibly catch any information about the crash? A call stack, a faulting task name—anything? I don’t know how to do debugging on the Amiga and only have experience on Windows, where I could just be looking at a memory dump in a debugger.
-
I just installed P96 3.2, and combining it with graphics.library 47.10 still crashes the machine, unfortunately.
-
Okay, sounds good! Looking forward to trying it out.
-
The machine successfully got through twenty passes of AmigaTestKit's RAM test on the system's fast memory, so between that and the specificity of the crash, I think I'm personally satisfied it's not bad RAM.
-
It's got a Magnum 40/4 68040 accelerator with 64MB of RAM on the accelerator, plus an ACE2B. I've only seen it crash when both the new graphics.library and P96 are activated at the same time. Otherwise it's stable. Bad memory seems unlikely, no? I'd love to just give you a crash dump to open in a debugger, but I've been told in the past by others that's not possible. I'm not sure how to debug a crash like this shooting in the dark.
The two working machines are both 030s. One has a 2630 and a BigRAM2630 (you were just helping me with this one crashing because of the BigRAM), and the other is a stock 16MHz A3000.
-
I'm a little puzzled by this one, as I have three Amigas, all running AmigaOS 3.2.1 with P96 3.1.2, and only one of them repros. But:
On my A2000 Rev6, if any P96 monitors are in Devs:Monitors, my machine crashes within 30 seconds of LoadMonDrvs returning. If I comment that out in startup-sequence, the machine crashes when I manually double-click the "Generic" monitor or my ZZ9000's monitor file. It also crashes immediately when opening the P96 preferences app.
If I remove the new graphics.library from the LoadModule directive in startup-sequence, the crash goes away. Is there a bug in P96, or a bug in the new graphics.library? Or both? How might I help narrow it down? I'm not sure where to send this bug, especially since it only repros on one out of my three machines with P96 installed. And one of the two machines that's not crashing, another A2000, has a nearly identical copy of the same boot volume that crashes on the other machine.