Jump to content

OS X compatible motherboard -> QUO

meklort

By meklort,
in New Releases and Updates

 Share
4,397 posts in this topic

Recommended Posts

Jaco2k
Jaco2k
Posted
Posted

Mine shutdown just fine, well there is a diff compared with yosemite, but that is caused by apple "improvements" on ElCrap...

 

if still does not work I have no other idea.

There has to be a difference somewhere - I even have a video of me following every single step you did, including the install media creation and it still does not boot.

 

Last thing before giving up - can you share somewhere the exact binary you used to flash your BIOS?

I am wondering, should I reset the NVRAM also? I have reset the BIOS, even went as far as removing the MOBO battery, besides having shorted the jumper that resets the BIOS, but not sure if this is enough.

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

There has to be a difference somewhere - I even have a video of me following every single step you did, including the install media creation and it still does not boot.

 

Last thing before giving up - can you share somewhere the exact binary you used to flash your BIOS?

I am wondering, should I reset the NVRAM also? I have reset the BIOS, even went as far as removing the MOBO battery, besides having shorted the jumper that resets the BIOS, but not sure if this is enough.

After BIOS update(I use the same released rom here) NVRAM is cleared so no need to do it again.

You never replied on this questions:

1. Did you removed all HDD's except the one you will install Windows?

2. After installation do you try to boot with other hdd's attached?

3. Did you cleanup the mess on other HDD's ESP?

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

So then... The plot thickens - I pulled out yet another HDD (not an SSD) and tried the exact same installer USB stick and install method.
It worked first time!

As I had said while ago, something is up with 1669 BIOS and booting from SSD.

I had two different SSDs that I have now tried and none of them boots:

Crucial MX100 and Samsung EVO 850

What next?

After BIOS update(I use the same released rom here) NVRAM is cleared so no need to do it again.

You never replied on this questions:

1. Did you removed all HDD's except the one you will install Windows?

2. After installation do you try to boot with other hdd's attached?

3. Did you cleanup the mess on other HDD's ESP?

 

1. Only one HDD attached to the system for the last 2 days of investigation, actually, and up until 15 mins ago, only SSD.

2. Installation does not even complete. After the installer copies the files to the SSD (which I wipe before installing) and when it reaches the stage it does the first reboot to continue installation from the HDD (or SSD), it does not succeed in booting from the SSD

3. Other HDDs are not even plugged or being used for 3 days - not a factor in this equation right now

4. Check my other post - I attempted with a spare HDD (not SSD...) and it worked first time. The issue is SSD specific.

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

If you don't answer on my questions I gave up.

 

I have no Crucial MX100 or Samsung Evo 850 to test, but I very doubt is that unless yours are defective...

 

For the rest of us it works on SSD that we have, I have Windows installed also on 2 mSata SSD.

Link to comment
Share on other sites
MattsCreative
MattsCreative
Posted
Posted

So then... The plot thickens - I pulled out yet another HDD (not an SSD) and tried the exact same installer USB stick and install method.

It worked first time!

 

As I had said while ago, something is up with 1669 BIOS and booting from SSD.

 

I had two different SSDs that I have now tried and none of them boots:

 

Crucial MX100 and Samsung EVO 850

 

What next?

 

1. Only one HDD attached to the system for the last 2 days of investigation, actually, and up until 15 mins ago, only SSD.

2. Installation does not even complete. After the installer copies the files to the SSD (which I wipe before installing) and when it reaches the stage it does the first reboot to continue installation from the HDD (or SSD), it does not succeed in booting from the SSD

3. Other HDDs are not even plugged or being used for 3 days - not a factor in this equation right now

4. Check my other post - I attempted with a spare HDD (not SSD...) and it worked first time. The issue is SSD specific.

DO NOT go blaming oz for anything wrong with your SSD i use 4 SSD's in my system as of yesterday one with os x 10.11.3 one with windows 10 Redstone one with linux for building android roms and one for no reason at but for loading games and programs. so if there is an issue it's with the hardware not ozmosis. best get them replaced or scanned in linux for issues

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

DO NOT go blaming oz for anything wrong with your SSD i use 4 SSD's in my system as of yesterday one with os x 10.11.3 one with windows 10 Redstone one with linux for building android roms and one for no reason at but for loading games and programs. so if there is an issue it's with the hardware not ozmosis. best get them replaced or scanned in linux for issues

 

I have two SSDs, one of them brand new - they work and boot just fine with every single BIOS version except 1669. I used the exact same process to create the installation on the brand new Samsung EVO 850 than I did on a some old HDD I had in a shelf. It doesn't even finish the install on the SSD, but it installed first time on the HDD.

 

I think it is a little bit too big coincidence that I have two broken SSDs, with one of them being brand new, out of the box, purchased 3 days ago...

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

I think it is a little bit too big coincidence that I have two broken SSDs, with one of them being brand new, out of the box, purchased 3 days ago...

 

 

If you don't answer on my questions I gave up.

Once again, I am 99.9% sure you SSD's are just fine, but since you refuse to answer on my questions I am done with this subject!

Link to comment
Share on other sites
MattsCreative
MattsCreative
Posted
Posted

I have two SSDs, one of them brand new - they work and boot just fine with every single BIOS version except 1669. I used the exact same process to create the installation on the brand new Samsung EVO 850 than I did on a some old HDD I had in a shelf. It doesn't even finish the install on the SSD, but it installed first time on the HDD.

 

I think it is a little bit too big coincidence that I have two broken SSDs, with one of them being brand new, out of the box, purchased 3 days ago...

check your sata plugs i mean really check next check your bios make sure you have the right revision flashed and as i said run them through linux for errors and answer anything asked of you to get this fixed 

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

Once again, I am 99.9% sure you SSD's are just fine, but since you refuse to answer on my questions I am done with this subject!

Did you bother reading up on my post?

 

Your questions have been answered there for a while already - the board edits the original post if your reply twice in a row...

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

Did you bother reading up on my post?

 

Your questions have been answered there for a while already - the board edits the original post if your reply twice in a row...

Weird for some reason I didn't saw that post LOL & sorry...

The other question is uppon my problem. I really don't want to reinstall my system without guarantee for success. What's your recommandation?

My last option is to do a clean installation...

Since I can't replicate this issue and dumps/logs does not help, I have no other idea.

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted (edited)

I don't freaking get it...

So, this is where I am at:
- I have two test drives: one SSD and one HDD (they are NEVER plugged at the same time - this just for testing HDD install vs SSD install)
- Windows install USB media was created as instructed
- trying to install Windows to SSD fails when you reach the stage the PC reboots first time (black screen after reboot)
- using the exact same USB media and process but installing to HDD works perfect
- trying to restore/clone the working Windows install in HDD to SSD does not work
- installing Ubuntu 15.04 to the SSD works just fine and it boots (it was the last thing I tried)
- reverting BIOS to previous version = SSD windows install works fine and boots.

I am now going to wipe the Linux install from the SSD, revert the BIOS to old version, install Windows with the same process I have been using so far, confirm it boots and then come back to 1669.

So... I am out of ideas soon.
I don't think the SSDs are defective, but maybe they have some compatibility issue with Windows?

 

Update: - Installing Windows now on the SSD with the exact same process and settings but... in the old BIOS. As expected, going perfectly. After it installs, I will update BIOS again back to 1669

Edited by Jaco2k
Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

More to come, but... for now I will put here a log comparison of SSD vs HDD installed with the same method but booting inside 1479

 

This is the SSD Windows in 1479

00:000 00:000 Ozmosis 1.02.1479 RELEASE (2014-09-12 23:27:19 VS2012x86) on 2015-12-19 16:55:18
00:000 00:000 Found Firmware UEFI Spec  :2.31:
00:000 00:000 Found Firmware Vendor     :American Megatrends:
00:000 00:000 Found Firmware Revision   :4.653:
00:000 00:000 BootOrder 03 01
00:000 00:000 BootOrder 03 01
00:000 00:000 Found Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (3A.06.00) Cores 4 Threads 8
00:000 00:000  BusRatio 16 / 35 (37)
00:000 00:000  P-State Coordination Type HW_ALL -> SW_ANY = SW_ANY
00:000 00:000  Disabling Invalid Flex-Ratio F0000 -> E0000 = E0000
00:000 00:000  TurboBusRatio1 39 -> 39 = 39
00:000 00:000  TurboBusRatio2 39 -> 38 = 39
00:000 00:000  TurboBusRatio3 38 -> 37 = 38
00:000 00:000  TurboBusRatio4 37 -> 36 = 37
00:000 00:000  TSC Frequency  3503438430  3503MHz
00:000 00:000  CPU Frequency  3503438400  3503MHz
00:000 00:000  FSB Frequency   100098240   100MHz
00:000 00:000 Detected Aptio 2.x firmware enabling fixes
00:000 00:000 Found 00.01.00.0 Nvidia Graphics Controller [10DE:1187] [1462:2847] rev 161
00:000 00:000 Found 00.6E.00.0 Intel Lan Controller [8086:10F6] [8086:0000] rev 0 94:DE:80:A1:36:23
00:000 00:000 Found 00.70.00.0 Texas Instruments Firewire Controller [104C:823F] [3412:7856] rev 1 00:00:00:00:00:00:00:00
00:000 00:000 Found 00.00.1F.3 Intel SMBUS Controller [8086:1E22] [8086:7270] rev 4
00:001 00:000  Slot 0 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0D15F403"
00:001 00:000  Slot 1 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0D06C3C2"
00:002 00:000  Slot 2 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0F156604"
00:002 00:000  Slot 3 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0F06BFC2"
00:002 00:000 Found 1 GPU Controller
00:002 00:000 Found Storage PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,36CCC8B4-F60A-4A49-97EB-9B00E5AECDC0,0xE1800,0x32000)
00:005 00:002 Found Defaults 99F2839C-57C3-411E-ABC3-ADE5267D960D
00:006 00:001 Validated Boot0003 "Windows Boot Manager"
00:006 00:000  HD(2,GPT,36CCC8B4-F60A-4A49-97EB-9B00E5AECDC0,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x74)
00:006 00:000 Scanning Bootable Devices...
00:007 00:001 Matched Boot0003 "Windows Boot Manager"
00:007 00:000  HD(2,GPT,36CCC8B4-F60A-4A49-97EB-9B00E5AECDC0,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x74)
00:007 00:000 Completed Bootable Device Scan
00:008 00:000 Matched Boot0001 "Built-In EDK Shell"
00:008 00:000  MemoryMapped(0xB,0x5EC8F004,0x5F391003)/FvFile(C57AD6B7-0515-40A8-9D21-551652854E37) (0x30)
00:008 00:000 BootOrder 03 01
01:471 01:463 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,36CCC8B4-F60A-4A49-97EB-9B00E5AECDC0,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi
01:471 00:000 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
01:471 00:000 Using AcpiGeneratorMask 0x08 00001000 Windows
02:128 00:656 RSDP 0x5DAD8000 r2  0x0024 0x80 "ALASKA" 0xE2 0x5DAD8028 0x000000005DAD8070
02:131 00:002 RSDT 0x5DAD8028 r1  0x0040 0x90 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x10013
02:131 00:000 FACP 0x5DAD80D8 r2  0x0084 0x3D "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:131 00:000 FACS 0x5DDF1F40 r0  0x0040 0xA3 "      " "        " 0x0        0x0        0x0
02:131 00:000 DSDT 0x5DAD8160 r2  0x7523 0x74 "ALASKA" "A M I   " 0x12       0x4C544E49 0x20140724
02:131 00:000 APIC 0x5DADF780 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:131 00:000 MCFG 0x5DADF818 r1  0x003C 0x35 "      " "        " 0x1072009  0x5446534D 0x97
02:131 00:000 HPET 0x5DADF858 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
02:131 00:000 SSDT 0x5DADF890 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
02:131 00:000 SSDT 0x5DADFC00 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
02:131 00:000 SSDT 0x5DAE05B0 r1  0x0A92 0x47 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117
02:131 00:000 XSDT 0x5DAD8070 r1  0x005C 0x8B "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:131 00:000 FACP 0x5DADF688 r4  0x00F4 0x2D "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:131 00:000 FACS 0x5DDF1F80 r0  0x0040 0xA1 "      " "        " 0x0        0x0        0x2
02:131 00:000 DSDT 0x5DAD8160 r2  0x7523 0x74 "ALASKA" "A M I   " 0x12       0x4C544E49 0x20140724
02:132 00:000 APIC 0x5DADF780 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:132 00:000 MCFG 0x5DADF818 r1  0x003C 0x35 "      " "        " 0x1072009  0x5446534D 0x97
02:132 00:000 HPET 0x5DADF858 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
02:132 00:000 SSDT 0x5DADF890 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
02:132 00:000 SSDT 0x5DADFC00 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
02:132 00:000 SSDT 0x5DAE05B0 r1  0x0A92 0x47 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117

This is the HDD in 1479:

00:000 00:000 Ozmosis 1.02.1479 RELEASE (2014-09-12 23:27:19 VS2012x86) on 2015-12-19 17:06:05
00:000 00:000 Found Firmware UEFI Spec  :2.31:
00:000 00:000 Found Firmware Vendor     :American Megatrends:
00:000 00:000 Found Firmware Revision   :4.653:
00:000 00:000 BootOrder 03 01
00:000 00:000 BootOrder 03 01
00:000 00:000 Found Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (3A.06.00) Cores 4 Threads 8
00:000 00:000  BusRatio 16 / 35 (37)
00:000 00:000  P-State Coordination Type HW_ALL -> SW_ANY = SW_ANY
00:000 00:000  Disabling Invalid Flex-Ratio F0000 -> E0000 = E0000
00:000 00:000  TurboBusRatio1 39 -> 39 = 39
00:000 00:000  TurboBusRatio2 39 -> 38 = 39
00:000 00:000  TurboBusRatio3 38 -> 37 = 38
00:000 00:000  TurboBusRatio4 37 -> 36 = 37
00:000 00:000  TSC Frequency  3503437120  3503MHz
00:000 00:000  CPU Frequency  3503437105  3503MHz
00:000 00:000  FSB Frequency   100098203   100MHz
00:000 00:000 Detected Aptio 2.x firmware enabling fixes
00:000 00:000 Found 00.01.00.0 Nvidia Graphics Controller [10DE:1187] [1462:2847] rev 161
00:000 00:000 Found 00.6E.00.0 Intel Lan Controller [8086:10F6] [8086:0000] rev 0 94:DE:80:A1:36:23
00:000 00:000 Found 00.70.00.0 Texas Instruments Firewire Controller [104C:823F] [3412:7856] rev 1 00:00:00:00:00:00:00:00
00:000 00:000 Found 00.00.1F.3 Intel SMBUS Controller [8086:1E22] [8086:7270] rev 4
00:001 00:000  Slot 0 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0D15F403"
00:001 00:000  Slot 1 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0D06C3C2"
00:002 00:000  Slot 2 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0F156604"
00:002 00:000  Slot 3 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0F06BFC2"
00:002 00:000 Found 1 GPU Controller
00:002 00:000 Found Storage PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)
00:024 00:021 Found Defaults 99F2839C-57C3-411E-ABC3-ADE5267D960D
00:025 00:001 Purged Boot0003 "Windows Boot Manager"
00:025 00:000  HD(2,GPT,36CCC8B4-F60A-4A49-97EB-9B00E5AECDC0,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x74)
00:026 00:001 Scanning Bootable Devices...
00:046 00:020 Added Boot0000 "Windows Boot Manager"
00:046 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x90)
00:047 00:000 Completed Bootable Device Scan
00:047 00:000 Matched Boot0001 "Built-In EDK Shell"
00:047 00:000  MemoryMapped(0xB,0x5EC8F004,0x5F391003)/FvFile(C57AD6B7-0515-40A8-9D21-551652854E37) (0x30)
00:047 00:000 BootOrder 00 01
01:521 01:474 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi
01:521 00:000 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
01:521 00:000 Using AcpiGeneratorMask 0x08 00001000 Windows
04:788 03:266 RSDP 0x5DAD8000 r2  0x0024 0x80 "ALASKA" 0xE2 0x5DAD8028 0x000000005DAD8070
04:790 00:002 RSDT 0x5DAD8028 r1  0x0040 0x90 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x10013
04:790 00:000 FACP 0x5DAD80D8 r2  0x0084 0x3D "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
04:791 00:000 FACS 0x5DDF1F40 r0  0x0040 0xA3 "      " "        " 0x0        0x0        0x0
04:791 00:000 DSDT 0x5DAD8160 r2  0x7523 0x74 "ALASKA" "A M I   " 0x12       0x4C544E49 0x20140724
04:791 00:000 APIC 0x5DADF780 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
04:791 00:000 MCFG 0x5DADF818 r1  0x003C 0x35 "      " "        " 0x1072009  0x5446534D 0x97
04:791 00:000 HPET 0x5DADF858 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
04:791 00:000 SSDT 0x5DADF890 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
04:791 00:000 SSDT 0x5DADFC00 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
04:791 00:000 SSDT 0x5DAE05B0 r1  0x0A92 0x47 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117
04:791 00:000 XSDT 0x5DAD8070 r1  0x005C 0x8B "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
04:791 00:000 FACP 0x5DADF688 r4  0x00F4 0x2D "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
04:791 00:000 FACS 0x5DDF1F80 r0  0x0040 0xA1 "      " "        " 0x0        0x0        0x2
04:791 00:000 DSDT 0x5DAD8160 r2  0x7523 0x74 "ALASKA" "A M I   " 0x12       0x4C544E49 0x20140724
04:791 00:000 APIC 0x5DADF780 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
04:792 00:000 MCFG 0x5DADF818 r1  0x003C 0x35 "      " "        " 0x1072009  0x5446534D 0x97
04:792 00:000 HPET 0x5DADF858 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
04:792 00:000 SSDT 0x5DADF890 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
04:792 00:000 SSDT 0x5DADFC00 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
04:792 00:000 SSDT 0x5DAE05B0 r1  0x0A92 0x47 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117

This is the HDD in 1669 (I doubt the SSD will boot in 1669, but hey... let's find out)

00:000 00:000 Ozmosis 1.03.1669M RELEASE (2015-11-03 22:35:59 VS2013x86) on 2015-12-19 17:15:27
00:000 00:000 Found Firmware UEFI Spec  :2.31:
00:000 00:000 Found Firmware Vendor     :American Megatrends:
00:000 00:000 Found Firmware Revision   :4.653:
04:021 04:021 BootOrder 00 04 03
04:021 00:000 Found Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (3A.06.00) Cores 4 Threads 8
04:021 00:000  P-State Coordination Type HW_ALL -> SW_ANY = SW_ANY
04:021 00:000  Bus Ratio 16 - 35 (37) Unlocked
04:021 00:000  Disabling Invalid Flex-Ratio F0000 -> E0000 = E0000
04:021 00:000  TSC Frequency  3503445880  3503MHz
04:021 00:000  CPU Frequency  3503445855  3503MHz
04:021 00:000  FSB Frequency   100098453   100MHz
04:021 00:000 Found 00.01.00.0 Nvidia Graphics Controller [10DE:1187] [1462:2847] rev 161
04:022 00:000 Found 00.6E.00.0 Intel Lan Controller [8086:10F6] [8086:0000] rev 0 94:DE:80:A1:36:23
04:022 00:000 Found 00.70.00.0 Texas Instruments Firewire Controller [104C:823F] [3412:7856] rev 1 00:00:00:00:00:00:00:00
04:022 00:000 Found 00.00.1F.3 Intel SMBUS Controller [8086:1E22] [8086:7270] rev 4
04:023 00:001  Slot 0 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0D15F403"
04:023 00:000  Slot 1 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0D06C3C2"
04:024 00:000  Slot 2 8192MB DDR3 SDRAM 1600MHz "Kingston" "KHX1600C10D38G" "0F156604"
04:024 00:000  Slot 3 8192MB DDR3 SDRAM 1333MHz "Kingston" "KHX1600C10D38GX" "0F06BFC2"
04:027 00:002 Found 1 GPU Controller
04:027 00:000 Found Storage PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)
04:037 00:009 Found Defaults 99F2839C-57C3-411E-ABC3-ADE5267D960D
04:045 00:008 Validated Boot0000 "Windows Boot Manager"
04:045 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x90)
04:045 00:000 Purged Boot0004 "UEFI: Generic STORAGE DEVICE 9407"
04:045 00:000  PciRoot(0x0)/Pci(0x1A,0x0)/USB(0x1,0x0)/USB(0x1,0x0)/HD(1,MBR,0x045DB8BB,0x2000,0x39EE000) (0x4C)
04:047 00:002 Validated Boot0003 "UEFI: Built-in EFI Shell "
04:047 00:000  VenMedia(5023B95C-DB26-429B-A648-BD47664C8012) (0x18)
04:047 00:000 Scanning Bootable Devices...
04:073 00:026 Matched Boot0000 "Windows Boot Manager"
04:073 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi (0x90)
04:073 00:000 Completed Bootable Device Scan
04:074 00:000 BootOrder 00 03
05:678 01:604 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,354D5C64-D080-456D-B0CB-959DA1030C2B,0xE1800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi
05:678 00:000 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
05:678 00:000 Using AcpiGeneratorMask 0x08 00001000 Windows
08:199 02:520 RSDP 0x5DEB4000 r2  0x0024 0x82 "ALASKA" 0xE4 0x5DEB4028 0x000000005DEB4070
08:202 00:003 RSDT 0x5DEB4028 r1  0x0040 0x30 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x10013
08:202 00:000 FACP 0x5DEB40D8 r2  0x0084 0x41 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
08:203 00:000 FACS 0x5E1CDF40 r0  0x0040 0xA3 "      " "        " 0x0        0x0        0x0
08:203 00:000 DSDT 0x5DEB4160 r2  0x750C 0x39 "ALASKA" "A M I   " 0x69       0x4C544E49 0x20150818
08:203 00:000 APIC 0x5DEBB768 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
08:204 00:000 MCFG 0x5DEBB800 r1  0x003C 0x71 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x97
08:204 00:000 HPET 0x5DEBB840 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
08:205 00:000 SSDT 0x5DEBB878 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
08:205 00:000 SSDT 0x5DEBBBE8 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
08:205 00:000 SSDT 0x5DEBC598 r1  0x0A92 0x07 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117
08:206 00:000 XSDT 0x5DEB4070 r1  0x005C 0x43 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
08:206 00:000 FACP 0x5DEBB670 r4  0x00F4 0x33 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
08:207 00:000 FACS 0x5E1CDF80 r0  0x0040 0xA1 "      " "        " 0x0        0x0        0x2
08:207 00:000 DSDT 0x5DEB4160 r2  0x750C 0x39 "ALASKA" "A M I   " 0x69       0x4C544E49 0x20150818
08:208 00:000 APIC 0x5DEBB768 r3  0x0092 0xD2 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
08:208 00:000 MCFG 0x5DEBB800 r1  0x003C 0x71 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x97
08:209 00:000 HPET 0x5DEBB840 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
08:209 00:000 SSDT 0x5DEBB878 r1  0x036D 0x3C "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
08:209 00:000 SSDT 0x5DEBBBE8 r1  0x09AA 0x7F "PmRef " "Cpu0Ist " 0x3000     0x4C544E49 0x20051117
08:210 00:000 SSDT 0x5DEBC598 r1  0x0A92 0x07 "PmRef " "CpuPm   " 0x3000     0x4C544E49 0x20051117

Unfortunately, have to confirm the SSD did not boot in 1669, but not sure if now with these logs it is possible to get a little bit further.

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

Based on a guess after reading some other user experiences in a different forum, I switched from AHCI to IDE in 1669 and... SSD booted first time, still in UEFI mode.

 

Any ideas now?

What user experiences and on what forum, link(s)?

 

Now that you did a clean install on ssd with 1479, keep only that ssd in and flash original F2N that comes with motherboard, if works then is one of the changes made to H2N BIOS or Ozmosis.

If works with original F2N, flash H2N 1669 and after the Ozmosis Logo reboot, and keep pressing ESC key until you see a red screen, if boots then is not H2N BIOS changes and is Ozmosis bug.

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

What user experiences and on what forum, link(s)?

 

Now that you did a clean install on ssd with 1479, keep only that ssd in and flash original F2N that comes with motherboard, if works then is one of the changes made to H2N BIOS or Ozmosis.

If works with original F2N, flash H2N 1669 and after the Ozmosis Logo reboot, and keep pressing ESC key until you see a red screen, if boots then is not H2N BIOS changes and is Ozmosis bug.

 

I don't even know anymore - must have read about 50 different threads in forums today about SSDs not booting. One led me to some guy mentioning he could boot in IDE but not in AHCI so, I decided to change to IDE just to see what would happen - it booted.

 

About your request, I need to quickly go out and shop something but will do it as soon as I am back - max in 30 mins.

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

What user experiences and on what forum, link(s)?

 

Now that you did a clean install on ssd with 1479, keep only that ssd in and flash original F2N that comes with motherboard, if works then is one of the changes made to H2N BIOS or Ozmosis.

If works with original F2N, flash H2N 1669 and after the Ozmosis Logo reboot, and keep pressing ESC key until you see a red screen, if boots then is not H2N BIOS changes and is Ozmosis bug.

 

Results:

- H3C (with loaded optimized defaults) - Installed to SSD, booted all without issues

- F2N - Flashed it after H3C without making any changes - Windows booted fine

- H2N (without Ozmosis, disabled via ESC key) - Did not boot. Bug is in H2N source BIOS.

 

Is it possible to get an alternative H3C with the up-to-date Ozmosis?

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

Results:

- H3C (with loaded optimized defaults) - Installed to SSD, booted all without issues

- F2N - Flashed it after H3C without making any changes - Windows booted fine

- H2N (without Ozmosis, disabled via ESC key) - Did not boot. Bug is in H2N source BIOS.

 

Is it possible to get an alternative H3C with the up-to-date Ozmosis?

Finally the bug is located!

It can be one of the updated -ROM's/EFI RAID drivers.

 

Wait for a new release or update your H3C with files from H2N if you cannot wait.

 

P.S. you made an habit to not answer on all my questions...

Link to comment
Share on other sites
Jaco2k
Jaco2k
Posted
Posted

Wait for a new release or update your H3C with files from H2N if you cannot wait.

Is there a guide or instructions for this somewhere? Exactly which BIOs parts should be changed?

 

I have edited one BIOS from a different board while ago just to update a RAID controller BIOS, but that was a long time and tools/process was obviously different.

Link to comment
Share on other sites
alberto21
alberto21
Posted
Posted

Is there a guide or instructions for this somewhere? Exactly which BIOs parts should be changed?

 

I have edited one BIOS from a different board while ago just to update a RAID controller BIOS, but that was a long time and tools/process was obviously different.

Here the one I did some days ago: http://www.mediafire.com/download/cyqxi4mp3ctg6le/Z77MXQUOAOS.H3C.1669M.ROM, it's H3C updated with 1669. I'm currently using it, hope it can help.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...