Jump to content

hp compaq dx2400 microtower Stuck at [EB|#LOG:EXITBS:START]


carsonr
 Share

13 posts in this topic

Recommended Posts

Hello InsanelyMac community,

I am trying to install Hackintosh on a HP Compaq DX 2400, I am stuck at [EB|#LOG:EXITBS:START]. 

 

I'm not sure why, as it was working prior and suddenly stopped working. 

 

UPDATE:

It seems to be that when I have a 4GB memory configuration it will sometimes work; it does not work with an 8GB configuration. This is unique to booting Mac OS, I'm booting windows 10 and ubuntu with no issue.

Pic of it working with 4GBs:

1398109015_Screenshot2022-11-15at2_33_41PM.thumb.png.67b698ec7f28d288d3eefeeb42827553.png

 

My specs:

CPU: Intel Duo Core Quad Q8200
GPU: AMD Radeon R9 255
MOBO: HP IPIBL-L8

 

Any help would be greatly appreciated. My EFI & SysReport is attached.

 

image.thumb.png.7d40bc40256c12c3085aae65a2a29262.png


 

SysReport.zip EFI.zip

Edited by carsonr
Link to comment
Share on other sites

But what system are you trying to install?

Looking at the clover config I want to propose you to set KernelLapic=YES because this is HP while I am not sure what bootloader did you use.

If Clover then preboot.log is desirable to see.

Link to comment
Share on other sites

12 hours ago, Slice said:

But what system are you trying to install?

Looking at the clover config I want to propose you to set KernelLapic=YES because this is HP while I am not sure what bootloader did you use.

If Clover then preboot.log is desirable to see.

An essential detail to leave out - sorry, I am using OpenCore as my bootloader and I am installing Mac OS Monterey.

Link to comment
Share on other sites

12 hours ago, Slice said:

But what system are you trying to install?

Looking at the clover config I want to propose you to set KernelLapic=YES because this is HP while I am not sure what bootloader did you use.

If Clover then preboot.log is desirable to see.

I tried the equivalent setting which is LapicKernelPanic but I still am stuck on the same screen.

Link to comment
Share on other sites

If you have the following items in BIOS setup, set it to Enabled.

- Execute Disable Bit (EDB)
- NX ( No eXecute ) Memory Protection
- XD Execute Disable Bit
- Data Execution Protection
- Memory Execution Protection

 

Also, try setting UnblockFsConnect to True in UEFI - Quirks in Config.plist.

Link to comment
Share on other sites

19 hours ago, shl628 said:

If you have the following items in BIOS setup, set it to Enabled.

- Execute Disable Bit (EDB)
- NX ( No eXecute ) Memory Protection
- XD Execute Disable Bit
- Data Execution Protection
- Memory Execution Protection

 

Also, try setting UnblockFsConnect to True in UEFI - Quirks in Config.plist.

I tried the setting and it did not work. For the BIOS options that appear, I have the set to true.

Link to comment
Share on other sites

3 hours ago, carsonr said:

I tried the setting and it did not work. For the BIOS options that appear, I have the set to true.

 

Try setting DevirtualizeMmio to False and ProvideCustomSlide to True in Booter - Quirks.

If it still does not boot, try setting ForceExitBootServices to True additionally.

Edited by shl628
Link to comment
Share on other sites

16 hours ago, shl628 said:

 

Try setting DevirtualizeMmio to False and ProvideCustomSlide to True in Booter - Quirks.

If it still does not boot, try setting ForceExitBootServices to True additionally.

It's still not budging, I am not sure why it's not working.

 

Trying to see if I can get more bios settings available by making modifying the BIOS to make all settings available.

https://winraid.level1techs.com/t/guide-legacy-amibios8-make-all-compiled-settings-available/37221

Edited by carsonr
Link to comment
Share on other sites

Modding the BIOS didn’t really reveal anything; there are no hidden settings that aren’t available on the BIOS.

 

I would really appreciate some help

or suggestions on what settings to change.

Edited by carsonr
Link to comment
Share on other sites

On 10/4/2022 at 6:19 PM, shl628 said:

 

Try setting DevirtualizeMmio to False and ProvideCustomSlide to True in Booter - Quirks.

If it still does not boot, try setting ForceExitBootServices to True additionally.

I have now figured out that the RAM seems to be causing the issue. 
 

I took out the two sticks I added to make it 8 GB and it seems to run just fine with 4 GBs.

I am wondering if there are any fixes I can apply to make my memory work with 8 GBs as it seems to work fine when booted into windows.

Link to comment
Share on other sites

  • 1 month later...
 Share

×
×
  • Create New...