That is one possibility, but not the only one I think...
Originally Posted by dlanor
Afaik, not all modchips patch the OSDSYS ('on-the-fly')!
Every PS2 modchip is in fact made so as to interfere with some of the ways in which the normal OSDSYS by Sony works, so it is not at all surprising that it can have unwanted side effects for a homebrew modified version of OSDSYS, which is what FMCB is
But still ALL modchips interferre with the original functionality of a PS2, that is true.
Hm,... Normally those scans are done, even before the OSDSYS is started (and thus also the FMCB-KELF, which then again loads and patches the OSDSYS).
This seems to me as a typical case of interference between bootup modchip activity and FMCB activity.
(Both scan for pressed gamepad buttons at the same time)
I guess he had an old uLE-Version on MC (including an old config).
I think it/'uLE' successfully starts in all cases, but hangs on BSOD while uLE's init-stage (where it loads config and so on).
Indeed! I fully agree on that! That's a quite crazy behaviour, but maybe he also just sees it, because the VRAM or better the Framebuffer wasn't cleared, thus showing the logo of the last session... (of course that only applies, if he resettet, shortly after he saw the FMCB-Logo and before something different cleared the frame-buffers again (like a successful uLE-Start might).
That in itself is a modchip bug IMO, as it should not activate OSDSYS that way when requested to direct boot a DEV1 program.
Not sure here,... I think it also could be software-related only, in this case.
Yet another obvious conflict between what the modchip is trying to do and what FMCB is trying to do.
A friend of me has 4busted PS2s, mostly DMS4PRO-chipped, but also with an MI (but it's a FAT SCPH-39004).
I'm not sure exactly what is wrong here, and I have no console with MI chip to experiment with.
I think he would have mentioned it to me within the last 2 1/2 years
But I had similar sympthoms on my own.
I'm sure FMCB is not 100%ly bug-free and black-screens can be caused by the FMCB-Config, but I guess the problem here is indeed uLE.
To be specific: A new uLE and an old config.
Imho,... The MI is probably one of those very few chips, which work (almost) flawless with FMCB.
But I am quite sure that many users exist that use uLE v4.42a with their consoles having MI chips (or MI clones).
Hopefully some of them can clarify the situation, possibly indicating conflicts between FMCB and the MI, and how best to use uLE on such a console.
Agreed on both points.
But generally if you want to use FMCB properly with a modchip, then you should boot with that modchip disabled.
And if you boot with chip enabled its DEV1 usage (if active) should take precedence over any FMCB setup.
Yes! ...and this is how his PS2 should behave too.
For example, I have one console with a DMS4proSE modchip, and if I start it without disabling that chip then FMCB is completely ignored, as the DEV1 boot setting launches uLE directly, without the OSDSYS work that leads to FMCB booting (so there is NO FMCB splash screen displayed). But if I start it first while holding the L1 button, until I see the confirmation message about the disabled chip, and then press the reset button, then this modded console starts FMCB just like a normal unmodded console would, including all abilities to use uLE and other software.
If Autoboot is set to DEV.1, it shouldn't invoke the OSDSYS at all.
It only checks for button-presses before, just so the user has the ability to start into another 'mode'.
Norrmaly yes, but I assume that a CNF is causing the issue here (or it is read in a faulty way, a.k.a. the MC or it's filesystem are bugged/borked).
So for me uLE works fine with that console, regardless of whether I start uLE via DEV1 (chip on) or via FMCB (chip off).
In both cases it starts the same instance of uLE from the same standard location "mc0:/BOOT/BOOT.ELF" (or the other slot).
If your Matrix chip is not capable of doing the same, then it is the chip which is to blame for it, obviously.
I think it could be another fault here,...
The only thing I can think of, offhand, is to get another MC that you use with this chipped console, where you install uLE and the other homebrews you want, but without installing FMCB to it, so that this will not interfere with the bootup process of the MI chip, which seems to be what messes things up for you.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux