[SOLVED]uLaunchELF can't boot from Matrix Infinity DEV1 method

[iceflame]

[SOLVED]The problem has been solved. Please read this post

I install FMCB 1.8c on my memory card with 'PlayStation 3 Memory Card Adaptor' and succeed. It works fine on my PS2 Slim console, which version is SCPH-70000cw (v13), without modchip.
I have another PS2 Slim console, which version is SCPH-70000cb (v12), with genuine Matrix Infinity (Green Dot). I use same memory card with FMCB 1.8c on this console and find a weird problem. uLaunchELF 4.42a can't boot from Matrix Infinity DEV1 method.

Boot with FMCB: ( Matrix Logo has been turned off)
a.
1. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.
2. FMCB 1.8c boot successfully and i can see the OSDMENU.
3. Select uLaunchELF from OSDMENU. 'LOADING...' splash screen shows up.
4. Screen goes black and the red LED light on joypad goes out.

b.
1. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.
2. Press and hold R1 button until FMCB splash screen disappear.
3. Screen goes black and the red LED light on joypad goes out.

P.S
1. I tried to plug Plug memory card with FMCB 1.8c in Slot 2 but got the same result.
2. I select Free McBoot Configurator in the OSDMENU. It launched successfully and works fine.

Matrix Infinity DEV1 method: ( Matrix Infinity Firmware is 1.93)
1. Enter the Configuration Menu, hold TRIANGLE & CIRCLE at power on.
2. Change Boot Mode from 'Auto' to 'DEV1'
3. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.
4. Screen goes black and the red LED light on joypad goes out.

List of confirmed info.
1. Matrix Infinity is genuine, not a clone.
2. "mc0:/BOOT/BOOT.ELF" the uppercase naming had been checked and it's correct.
3. uLaunchELF version is 4.42a.
4. Using FMCB 1.8b and boot from Matrix Infinity DEV1 method. I get the same reslut as FMCB 1.8c.

It seems like there is some compatibility problem in path road "mc0:/BOOT/BOOT.ELF"
Why it aways got black screen? What's wrong with Matrix Infinity DEV1 method and how can I solve it?
Any useful information would be appreciated!!!

P.S
I can't use forums Search function now. Whatever I input any key word, I get the same message:

Sorry - no matches. Please try some different terms.

Is this a forum function problem? How can I use the Search function as before?

Best regards

[dlanor]

I install FMCB 1.8c on my memory card with 'PlayStation 3 Memory Card Adaptor' and succeed. It works fine on my PS2 Slim console, which version is SCPH-70000cw (v13), without modchip.
I have another PS2 Slim console, which version is SCPH-70000cb (v12), with genuine Matrix Infinity (Green Dot). I use same memory card with FMCB 1.8c on this console and find a weird problem. uLaunchELF 4.42a can't boot from Matrix Infinity DEV1 method.

Boot with FMCB: ( Matrix Logo has been turned off)
a.
1. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.
2. FMCB 1.8c boot successfully and i can see the OSDMENU.
3. Select uLaunchELF from OSDMENU. 'LOADING...' splash screen shows up.
4. Screen goes black and the red LED light on joypad goes out.

Are you saying FMCB v1.8c is unable to launch uLE, because that is definitely not correct...
When this happens it must be due to some kind of interference between modchip activity and FMCB activity.

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.

b.
1. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.
2. Press and hold R1 button until FMCB splash screen disappear.
3. Screen goes black and the red LED light on joypad goes out.

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)

P.S
1. I tried to plug Plug memory card with FMCB 1.8c in Slot 2 but got the same result.
2. I select Free McBoot Configurator in the OSDMENU. It launched successfully and works fine.

Matrix Infinity DEV1 method: ( Matrix Infinity Firmware is 1.93)
1. Enter the Configuration Menu, hold TRIANGLE & CIRCLE at power on.
2. Change Boot Mode from 'Auto' to 'DEV1'
3. Plug memory card with FMCB 1.8c in Slot 1. Power on the console. Free McBoot Splash Screen shows up.

That in itself is a modchip bug IMO, as it should not activate OSDSYS that way when requested to direct boot a DEV1 program.

4. Screen goes black and the red LED light on joypad goes out.

Yet another obvious conflict between what the modchip is trying to do and what FMCB is trying to do.

List of confirmed info.
1. Matrix Infinity is genuine, not a clone.
2. "mc0:/BOOT/BOOT.ELF" the uppercase naming had been checked and it's correct.
3. uLaunchELF version is 4.42a.
4. Using FMCB 1.8b and boot from Matrix Infinity DEV1 method. I get the same reslut as FMCB 1.8c.

It seems like there is some compatibility problem in path road "mc0:/BOOT/BOOT.ELF"
Why it aways got black screen? What's wrong with Matrix Infinity DEV1 method and how can I solve it?

I'm not sure exactly what is wrong here, and I have no console with MI chip to experiment with.

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.

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.

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.

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.

Any useful information would be appreciated!!!

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.

P.S
I can't use forums Search function now. Whatever I input any key word, I get the same message:

Is this a forum function problem?

Yes of course.

These forums have recently seen a change of ownership, a change of the physical servers, and several forum software updates.
We can count ourselves lucky that anything works at all, let alone so well as it presently does.

How can I use the Search function as before?

I've no clue. And this is not the right place to deal with such things, as it has nothing to do with uLE.

Best regards: dlanor

[TnA]

Are you saying FMCB v1.8c is unable to launch uLE, because that is definitely not correct...
When this happens it must be due to some kind of interference between modchip activity and FMCB activity.

That is one possibility, but not the only one I think...

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

Afaik, not all modchips patch the OSDSYS ('on-the-fly')!
But still ALL modchips interferre with the original functionality of a PS2, that is true.

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)

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).

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).

That in itself is a modchip bug IMO, as it should not activate OSDSYS that way when requested to direct boot a DEV1 program.

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).

Yet another obvious conflict between what the modchip is trying to do and what FMCB is trying to do.

Not sure here,... I think it also could be software-related only, in this case.

I'm not sure exactly what is wrong here, and I have no console with MI chip to experiment with.

A friend of me has 4busted PS2s, mostly DMS4PRO-chipped, but also with an MI (but it's a FAT SCPH-39004).
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.

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.

Imho,... The MI is probably one of those very few chips, which work (almost) flawless with FMCB.

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.

Agreed on both points.

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.

Yes! ...and this is how his PS2 should behave too.
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'.

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.

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).

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.

I think it could be another fault here,...

[iceflame]

Before I reply this post, I want to thank you dlanor and TnA, thanks for your detail information!

I did more tests today and here is the report for the tests. It may be long, but I hope you guys don't be tried of reading this, THANKS!

Before test:
Storing uLaunchELF as "mc0:/BOOT/BOOT.ELF"
To campare the test reslut, I put different version of uLE in different memory card.
memory card without installing FMCB ---- uLE v4.42
memory card with FMCB 1.8c ---- uLE v4.42a

Boot with FMCB: ( Matrix Logo has been turned off, Boot Mode is 'Auto' )
Test a
1. Plug memory card without installing FMCB in Slot 1. Power on the console.
2. Press and hold R1 button, uLE launchs successfully. ( no FMCB splash screen ) uLE v4.42

Test b
1. Plug one memory card without installing FMCB in Slot 1 and the other memory card with FMCB 1.8c in Slot 2. Power on the console.
2. Press and hold R1 button, uLE launchs successfully. ( no FMCB splash screen ) uLE v4.42

Test c
1. Plug one memory card with FMCB 1.8c in Slot 1 and the other memory card without installing FMCB in Slot 2. Power on the console.
2. Press and hold R1 button until FMCB splash screen disappear.
3. Screen goes black and the red LED light on joypad goes out.

Test d
1. Plug one memory card without installing FMCB in Slot 1 and the other memory card with FMCB 1.8c in Slot 2. Power on the console. Do NOT press any button. Free McBoot Splash Screen shows up.
2. FMCB 1.8c boot successfully and i can see the OSDMENU.
3. Select uLaunchELF from OSDMENU. 'LOADING...' splash screen shows up.
4. uLE launchs successfully. uLE v4.42

You can see when every time DEV1 method works, uLE away launch from memory card without installing FMCB in Slot 1. NONE of uLE launched from FMCB 1.8c. I suppose it due to the campatibilty between FMCB(1.8) and Modchip.
But I supposed that Matrix Infinity DEV1 function works fine after I did these four tests above. To proof this point is right. I did more tests for Matrix Infinity DEV1 function.

Matrix Infinity DEV1 method: ( Matrix Infinity Firmware is 1.93)
1. Enter the Configuration Menu, hold TRIANGLE & CIRCLE at power on.
2. Change Boot Mode from 'Auto' to 'DEV1' (that's means Do not press any button after Power on the console)
Repeat four tests above, the resluts are
Test a ---- uLE direct to launch successfully. uLE v4.42
Test b ---- uLE direct to launch successfully. uLE v4.42
Test c ---- NO splash screen shows up. Screen goes black and the red LED light on joypad goes out.
Test d ---- uLE direct to launch successfully. uLE v4.42

When I finish these tests, I suppose that there must be some kind of interference between bootup modchip activity and FMCB activity. So I DISABLE the MI chip.

DISABLE MATRIX INFINITY : Press START on boot.
see the disable screen... now just tap reset to start the ps2 up again and the MI will be disabled.

Boot with FMCB: ( Matrix Infinity is DISABLED )
Test a ---- SONY OSDSYS shows up. No homebrew launched(of course)
Test b ---- uLE launchs successfully. ( after FMCB splash screen ). uLE v4.42
Test c ---- FMCB splash screen disappear. Screen goes black and the red LED light on joypad goes out.
Test d ---- uLE launchs successfully from OSDMENU. uLE v4.42

You can see when every time DEV1 method works, uLE away launch from memory card without installing FMCB in Slot 1 . NONE of uLE launched from FMCB 1.8c.

-------------------------------------------------------------------------------------------------------------------------------
I use other homebrew instead of uLE because of curious. But this let me get a strang reslut.

Storing OPL 0.8 (r590) as "mc0:/BOOT/BOOT.ELF" only for FMCB 1.8c
Repeat four tests metioned above. OPL 0.8 (r590) launched successfully in every tests!
Then I tried other homebrew. Storing SMS and PS2ESDL as "mc0:/BOOT/BOOT.ELF" for FMCB 1.8c. Both of them booted and launched successfully in DEV1 method or from OSDMENU with FMCB in every tests.

-------------------------------------------------------------------------------------------------------------------------------
I did another group test for uLE version.
Storing uLE v4.42a / v4.42 / v4.41 / v4.40 / v4.39 as "mc0:/BOOT/BOOT.ELF" for FMCB 1.8c
None of these version can launch in DEV1 method or from OSDMENU with FMCB.

Another test:
MI chip enabled & Boot Mode is 'Auto'
1. Plug one memory card without installing FMCB in Slot 1 and the other memory card with FMCB 1.8c in Slot 2. Power on the console.
2. Press and hold R1 button, uLE launchs successfully. ( no FMCB splash screen )uLE v4.42
3. Using uLE v4.42 into "mc1:/BOOT/BOOT.ELF" --- Cut 'BOOT.ELF' ---- Paste 'BOOT.ELF' into "mc1:/"
4. Select 'BOOT.ELF' in "mc1:/" and launch it
5. Screen goes black and the red LED light on joypad goes out.

================================================== ===================
Conclusion
After the multi-groups of test, for now it seems that only uLE can't be launched. In my opinion FMCB v1.8c is unable to launch uLE no matter Matrix Infinity is enabled or disabled.
It's little weird, huh.
WHY? How can I solve it?
Any useful information would be appreciated!!!

Best regards

[iceflame]

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).

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.

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).

Thanks for your reply!
Which 'CNF' you mentioned above probably causing the issue? Where can I find it? How to edit or change it?
Please give me a detail guide, thanks!

[TnA]

Interesting!

Now it also seems clear to me, that you pressed the button AFTER your modchip's button-check, that means it was FMCB which already started and wasn't able to start uLE through it's button-launch-feature...
It wasn't your modchip's DEV.1-Feature at all, which you used when you hold the R1-Button, while the FMCB-Screen was shown!
It was your modchip's DEV.1-Feature, when FMCB's logo did NOT show up!

Thanks for your reply!
Which 'CNF' you mentioned above probably causing the issue? Where can I find it? How to edit or change it?
Please give me a detail guide, thanks!

uLE's & FMCB's CNFs are within the 'SYS-CONF'-Folder on the same MC.
You might post both CNFs here.

Either FMCB's CNF has a fault, or the loader a problem with starting the compressed BOOT.ELF of uLE, or uLE's CNF is faulty, but then I guess it wouldn't start at all with other methods like DEV.1 from the same MC.

[iceflame]

@TnA
Thanks for your help! The problem has been solved.
Thanks for your mention, I deleted the old uLE's CNF in the 'SYS-CONF' folder.
I worte the steps and hope it can help others who have the same trouble.

Steps:
1. Plug one memory card without installing FMCB in Slot 1 and the other memory card with FMCB 1.8c in Slot 2. Power on the console.
2. Press and hold R1 button, uLE v4.42 launchs.
3. Using uLE v4.42 into "mc1:/SYS-CONF" --- Delete 'LAUNCHELF.CNF'
4. Select 'BOOT.ELF' in "mc1:/BOOT/BOOT.ELF" and launch it
5. uLE 4.42a launchs successfully. Then I set the configuration and save to a new one.
6. Plug the memory card with installing FMCB 1.8c in Slot 1. Power on the console.
7. Press and hold R1 button, uLE 4.42a launchs successfully.

==========
I find a little trick which can let uLE to search both MCs for the skin. When I try this trick, I assume this let me leave the old uLE-Version on MC which causing the issue
Skinning uLaunchELF v 4.21

Placing the skins on a MC in either slot will work if your Path is set to "uLE:/ skinname.jpg, rather than having a specific location on 1 MC. So when creating a CNF its best to use this path when sharing skin packages.

SKIN_FILE = uLE:/skinname.jpg

I put the 'skinname.jpg' in 'SYS-CONF' folder and edit the 'LAUNCHELF.CNF' follow the tutorial.
It works fine！Now the skins can show up wherever the memory card pluged in slot 1 or slot2.

[TnA]

Glad that's sorted out.
Have fun!

Best regards,
TnA