Jump to content

pctmac

Members
  • Content count

    46
  • Joined

  • Last visited

About pctmac

  • Rank
    InsanelyMac Protégé
  1. I guess this is a message from the Bios, not from Clover. Awaiting I understand how to upload files so that you get my config.plist and the debug file recorded when booting from USB (thus you can see lot of things), I also tried to boot from my disk activating the debug: it hangs again but rebooting with my Mavericks partition and trying to access to the debug file on the disk, I saw it empty: so my guess is that it hangs before Clover boot, thus it does not start the record in the debug file. Again, I do not see the text "b1f init " message, I just see the cursor moving to the end of this message, but no message and then cursor dissapear. What I do not understand is why it boots from USB and not from my disk? What changes in the MBR Boot and PBR Boot between disk and USB ?
  2. I suspect there is a scan issue: if too many partition are active or with bootloader, Clover might be lost. So I decided to try disabling the scan features and create custom entries for the disks. i modified my config as per attached config.plist Then I booted with debug and find the attached log from the USB: I am still able to boot to El Capitan but it looks like it's still scanning all entries even if it display only the 3 entries created + the Apple Recovery (but the Legacy Windows and Clover entries are no more there. EDIT: I am unauthorized to upload files. How can I do ?
  3. Detailled view: Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device partition=C: description Windows Boot Manager locale fr-FR inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {b7524836-2bc1-11e3-ba33-8c3f126cc8f1} resumeobject {b7524835-2bc1-11e3-ba33-8c3f126cc8f1} displayorder {b7524836-2bc1-11e3-ba33-8c3f126cc8f1} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 30 Windows Boot Loader ------------------- identifier {b7524836-2bc1-11e3-ba33-8c3f126cc8f1} device partition=C: path \Windows\system32\winload.exe description Windows 7 locale fr-FR inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence {b7524837-2bc1-11e3-ba33-8c3f126cc8f1} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {b7524835-2bc1-11e3-ba33-8c3f126cc8f1} nx OptIn Looks like it does read only my disk0
  4. Thanks. Already done. As I have a USB Stick with clover which works well (network, sound, sleep are ok), I have copied all the config to the EFI partition on disk3. To me, problem is before the loader gets to read files on EFI.
  5. Hi I am facing issue on booting my El Capitan install with my old GA-H67MA-USB3-B3 mobo which has a Bios F8 (so NO UEFI) and 4 disks. My disks are used as follow: /dev/disk0 : SSD, MBR, 1 partition active, NTFS and bootable with Windows 64: my default boot disk in my Bios. /dev/disk1 : GUID, NTFS, 1 partiton, not bootable, used to store my Windows Data /dev/disk2 : SSD, GUID, HFS, 1 partition, bootable with Chimera and Mavericks /dev/disk3 : GUID, HFS, 3 partitions, try to boot with Clover, Mavericks (backup) and El Capitan (test) + Mac Data I boot Windows by default and hit F12 to boot from disk2 when I want to use MacOS. I have succesfully installed El Capitan on second partition of disk3, installed Clover on this and when I boot with Clover by hitting F12 and selecting disk3: it hangs ! Here is what I have done : I have installed El Capitan on partition 3 of my disk3 following this guide: #####: Install OS X El Capitan on Any Supported Intel-based PC I then created a USB Clover test drive in legacy mode and I am able to boot from this stick, then choose El Capitan on disk3 who boot and run properly from this USB: I know have a proper Clover config (DSDT, config.plist, kexts, etc) which demonstrate I can boot El Capitan with clover on my PC. It also provides the files I am copying on the clover install on the disk. I then installed Clover on my disk3 in the EFI partition (installed in ESP) using legacy mode, as for the USB stick above, and copied the config from the working USB stick. When I boot and hit F12 to choose my disk3, I just have the "Loading Operating System" message and then a black screen: no quick boot0af line message I have when booting from the USB, nothing. It's stuck, I have to power down to reboot. Reading the Clover WIKI, I am in Option A, using legacy bios, the sequence will be: Option A: BIOS-based PC (old motherboards) BIOS>MBR>PBR>boot>CLOVERX64.efi>OSLoader According to this I should install «boot» in MBR sector: boot0 - searches for an active partition in the MBR and passes control to its PBR sector. Hybrid GPT/MBR layout is possible. However if the filesystem is pure GPT, boot0 passes control to the EFI partition, further referred to as boot0af (active first). Then in the PBR Sector of the EFI partition: Partition Boot Record (PBR) is a boot sector located in the beginning of each partition on a storage device. The phase two loader is stored here. PBR has the information of its partition's file system and may find and load the boot file and pass the control to it. So I should install «boot1f32» - supports FAT32. This file system is able to be written at the booting stage thus very well suited for boot loader installation. It is possible to use it as a EFI partition or on a USB flash drive (USB sticks are usually sold pre-formatted in FAT32). If I look at the Clover_Install_Log.txt file (see below), I have boot0af installed on MBR and boot1f32 installed on PBR of the EFi one, so everything should be fine ! What I do not understand is where does it hangs: at MBR or PBR level ? Here my Clover Install log file: Clover EFI installer log - Sun Nov 1 18:07:50 CET 2015 Installer version: v2.3k r3320 EFI bootloader ================================================== ==== /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *128.0 GB disk0 1: Windows_NTFS Windows7 128.0 GB disk0s1 Volume UUID: 9EEFB5D4-2511-4929-B5CA-DFF91F9BD55B /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *3.0 TB disk1 1: Microsoft Reserved 134.2 MB disk1s1 | Disk / Partition UUID: 87B61FC4-989C-4408-BFB9-1E4AE8A9E042 2: Microsoft Basic Data Win7Data 3.0 TB disk1s2 Volume UUID: 7EE9CE0E-01FB-49AC-ABB4-C36C962FE623 | Disk / Partition UUID: 424F4DD1-0D84-478F-A9E5-5A2A57C5E5C2 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *256.1 GB disk2 1: EFI EFI 209.7 MB disk2s1 | Volume UUID: 0E239BC6-F960-3107-89CF-1C97F78BB46B | Disk / Partition UUID: ED3D07EE-A02C-48B8-9ACF-9F0AFE81BB76 2: Apple_HFS Mavericks-SSD 255.7 GB disk2s2 | Volume UUID: D758C9BA-6E45-3068-B09D-0EF5E7B879EE | Disk / Partition UUID: 233D9A3C-06E2-4B63-ABD3-66F465807069 /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk3 1: EFI EFI 209.7 MB disk3s1 | Volume UUID: 9098615F-4F76-387C-94DE-60B40E333D52 | Disk / Partition UUID: C184A63F-58C6-44F4-9A6B-6F04FF06C3BF 2: Apple_HFS Mavericks 10.9.5 195.8 GB disk3s2 | Volume UUID: C4C62A5B-46C2-3A6B-8724-600077D9EA6C | Disk / Partition UUID: A96679D2-8B84-48BC-9B61-30D659332222 3: Apple_HFS El Capitan 10.11.1 195.3 GB disk3s3 | Volume UUID: 7F81B42E-0346-335B-8FA9-5341EA8417FD | Disk / Partition UUID: 82A6D379-8065-4EA8-B234-6273CD17FEDD 4: Apple_Boot Recovery HD 650.0 MB disk3s4 | Volume UUID: 0886E734-3603-362F-984E-B5FC37013F36 | Disk / Partition UUID: D1737F85-7CA5-4960-8A38-8507AA0A82A9 5: Apple_HFS MacData 1.6 TB disk3s5 | Volume UUID: 9E6E1842-C6A5-305C-8C08-60926E8CD8F8 | Disk / Partition UUID: C3AA55B4-8FFE-41A6-9962-FFF5350DFA14 ================================================== ==== Backing up EFI files Backing up stage2 file /Volumes/El Capitan 10.11.1/EFIROOTDIR/boot to /Volumes/El Capitan 10.11.1/EFI-Backups/r3292/2015-11-01-18h07/boot Backing up /Volumes/El Capitan 10.11.1/EFIROOTDIR/EFI folder to /Volumes/El Capitan 10.11.1/EFI-Backups/r3292/2015-11-01-18h07/EFI No Active Partition Stage 0 - Writting boot0af to /dev/disk3 /Volumes/El Capitan 10.11.1/usr/local/bin/fdisk440 -u -f /Volumes/El Capitan 10.11.1/usr/standalone/i386/boot0af -y /dev/disk3 Stage 1 - Writting boot1f32 to /dev/rdisk3s1 dd if=/dev/rdisk3s1 count=1 bs=512 of=/tmp/origbs boot volume format is FAT32 cp /tmp/boot1f32 /tmp/newbs dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc dd if=/tmp/newbs of=/dev/rdisk3s1 Stage 2 - Written boot6 (x64) to /Volumes/ESP/boot Theme 'tonymacx86' (defined in config.plist) not found ! Using default theme 'embedded' ================================================== ==== =========== Clover EFI Installation Finish =========== ================================================== ==== I tried the following: I have marked EFI partition on disk3 as active as apparently it solve an issue quite similar: Clover efi BIOS boot - no bootable device solution But I saw No change. I have reformated the EFI partition on disk3 as FAT32, was not sure it was already the case or not but I did it, re-installed Clover but still no change. Then I have disconnected disk0 (the one booting Windows) and Bingo, I have the attached menu ! So apparently, there is a conflict with the disk0 and the active Windows partition. I also notice this is very very very slow before it display this menu, compared to Chimera. I also notice that my disk2 with Chimera/mavericks did not show up in the list. In the menu, I have: Boot Windows from Legacy HD2: this is my Disk1 with Windows DATA: how can I remove this entry from the menu ? Boot Clover from EFI: do not know what this is entry is. If I try, I've got 2 messages, b1F : init then b1f: error and I need to reboot Boot mac OS X from Mavericks 10.9.5: not tested yet as I have to copy the kexts for 10.9 in Clover Boot mac OS X from El Capitan 10.11.1: it works as from my USB stick. If I reconnect my disk0, it hangs again if I try to boot from disk3. So remainging questions: I am correct when I say I must use Option A: BIOS-based PC (old motherboards) :BIOS>MBR>PBR>boot>CLOVERX64.efi>OSLoader ? is Clover able to manage 2 active MBR partition on 2 disks (disk 0 and disk 3 in my case) ? If not, how should I do? why boot is so slowwww? Thanks for your help
  6. As promised, some news: problem solved My video card is working properly under Lion 10.7.2. Issue was to run in 32 bits and to change PCI root id. So final config is the following: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>arch=i386 npci=0x2000 darkwake=0 PCIRootUID=1</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>Timeout</key> <string>2</string> <key>Legacy Logo</key> <string>Yes</string> <key>EthernetBuiltIn</key> <string>Yes</string> <key>GenerateCStates</key> <string>Yes</string> <key>GeneratePStates</key> <string>Yes</string> <key>UseKernelCache</key> <string>Yes</string> </dict> </plist>
  7. Hi Guys Back to my issue, I have some news. I was at a point where I was completely unable to even boot a Lion on my PC. So I restarted from scratch. Use [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] to create a USB with Lion 10.7.0 on it. Boot on USB, install (fine) then restart on USB and try to launch my new install from disk: I got a KP. Then I retried and from USB [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] force option -f -v arch=i386. This time, I was able to boot and guess what, I had full res and QE/CI activated!!!!! So it means to me my card is supported in 32bits in Lion without any editing. But ... I try then to complete the install with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] 4.2.1 with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] (no DSDT) and forcing to use a 32 bits org.chameleon.Boot.plist. I then rebooted from hard disk and again I loose the full res: I was at 1024x768 max. I tried to boot again from USB [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] then to choose my HD with same parameters as before but no QE/CI.... Then I tried again from my HD and find this in dmesg: Kext com.apple.driver.AppleHDAController - library kext com.apple.iokit.IOGraphicsFamily not found. Can't load kext com.apple.driver.AppleHDAController - failed to resolve library dependencies. Kext com.apple.driver.AppleHDAController failed to load (0xdc00800e). Failed to load kext com.apple.driver.AppleHDAController (error 0xdc00800e). Couldn't alloc class "AppleHDAController" Kext com.apple.GeForce7xxx - library kext com.apple.NVDAResman.G7xxx not found. Can't load kext com.apple.GeForce7xxx - failed to resolve library dependencies. Kext com.apple.GeForce7xxx failed to load (0xdc00800e). Failed to load kext com.apple.GeForce7xxx (error 0xdc00800e). Kext com.apple.GeForce - library kext com.apple.NVDAResman not found. Can't load kext com.apple.GeForce - failed to resolve library dependencies. Kext com.apple.GeForce failed to load (0xdc00800e). Failed to load kext com.apple.GeForce (error 0xdc00800e). Couldn't alloc class "NVLegacyKernel" Couldn't alloc class "NVKernel" While files are of course on the HD. My boot file was the following: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key> <string>Yes</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>arch=i386 npci=0x2000 darkwake=0</string> <key>Legacy Logo</key> <string>Yes</string> <key>Timeout</key> <string>2</string> <key>GenerateCStates</key> <string>Yes</string> <key>GeneratePStates</key> <string>Yes</string> </dict> </plist> So i tried to add UseKernelCache=Yes and this time I have no errors in dmesg about loading Nvidia kexts, but still no QE/CI. So I m quite lost: why I was able to run QE/CI & full res once when booting from [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] with arch=i386 and now I am unable to get it again? Is there an order in the parameters in the org.chameleon.Boot.plist ? Thanks for your help EDIT: Just looked at the USB and find that [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] use PCIRootUID=1: tried that and it works!!! So I will check tomorrow with a fresh install on 10.7.2 to confirm this is solved. As a first explanation, I was not booting in 32 bits and missing this PCIRootUID=1 (which is strange as I am not sure I have it on SL)
  8. Yes, tried with arch=i386 but still KP. What I do not understand is: this id card was in SL 10.6.8 drivers and this was working, this id card is still in Lion 10.7.2 drivers and it does KP So as I am not sure it should work, I am questioning to pursue debugging or to give up ?
  9. Hi all I am running an MSI Nvidia 6600GT / 128Mo and have no QE/CI nor full resoltution (stuck at 1280x768) under Lion 10.7.2. It's working great under SL 10.6.8 with full res (1680x1050x32) and QE/CI, so I am now wondering if the 6600 series (NV43) are supported under Lion or not? I did not find the confirmation, as I did for SL. If I run the same org.chameleon.Boot.plist as in SL, I got a KP in NVDANV40HALG7xxx.kext whith Chimera or Chameleon. (running NV40HAL.kext under SL). My card id 0x0140 is listed in the NVDANV40HalG7xxx.kext but not in NVDAResmanG7xxx.kext. (on Snow Leopard, it was NVDAResman.kext et NVDANV40HAL files) So if the card is in NVDANV40HalG7xxx.kext, does it means it should work ? What means the 'G7xxx' added at the end of each name on Lion drivers ? That is works only starting Geforce G7xxx series ? My config: GA-P43-ESG3 4Go, Nvidia 6600GT with monitor on VGA port. Thanks for your help
  10. DSDT Auto-Patcher

    Ok. I will search for native resolution. To test, I have installed RC5 r650 (BTW, I have 1280x768 instead of 1280x800 .... not too bad) and use P/C-States in boot.plist But I still have the error ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized What log should I look for or test should I do ?
  11. DSDT Auto-Patcher

    Dell Latitude E6400: Intel Mobile Core 2 Duo P8700 @ 2.53Ghz, 4Gb RAM, Video Intel GMA 4500MHD 1Gb Ram (id 8086:2a42 Rev B3), Intel Wifi 5100 AGN, Intel 82567LM, SATA Intel 82801IB/IR/IH (ICH9 Family), Audio IDT HD (id 111D:76B2 Chip 92HD75B3). When you write search: this is for the native resolution or for the error on C-state? For the resolution, the Deviato is by far the most easy one: I do not remember something else: do you ?
  12. DSDT Auto-Patcher

    ok, much better: no KP anymore. Still an error: ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized VID2: Not usable I made an error in my previous post: as added in my previous post, I am not using the Chameleon RC5 yet as I am using the Deviato's RC4 mod to get my LCD native resolution. So If I want to get p/c states via RC5, how can I still get my native resolution on my Video ? (since it's not supportted by SL) EDIT: just ran your script: here the result rigth now with your dsdt file and the error above: send_me.zip
  13. DSDT Auto-Patcher

    Just tried to boot with your file but I got a KP with the error "NO HPETS available ... CPUs configured incorrectly....." Strange as I tried by just changing your file. Any idea? Other question on power management: with my own file, I had powermanagement in the dsdt file and DrapSSDT=Yes in com.apple.boot.plist file. With your file, should I keep it (did you add pstates et cstates in dsdt?) or do I need to use the "GeneratePStates"="Yes and GenerateCStates"="Yes" in com.apple.boot.plist to get Chameleon to load p/c states in DSDT table? Please note I am using the Deviato's mod of Chameleon RC4 to get the native resolution of my display. thx
  14. [Install] Dell Latitude E6400 E6500

    Hi Can you advise the exact model of E6400 you are using with each component. Mine is the following E6400 : Intel Mobile Core 2 Duo P8700 @ 2.53Ghz, 4Gb RAM, Video Intel GMA 4500MHD 1Gb Ram (id 8086:2a42 Rev B3), Intel Wifi 5100 AGN, Intel 82567LM, SATA Intel 82801IB/IR/IH (ICH9 Family), Audio IDT HD (id 111D:76B2 Chip 92HD75B3). Thanks EDIT Feb 9th I finally got the time to restart my tests. @jichi: thanks for your pm, I got your files. Where do I stand ? I have a fresh install 10.6.3, updated to 10.6.5 with trackpad, ethernet working. Wifi still not (normal, Intel 5100). I have not yet updated to 10.6.6, not sure it is necessary? Issues I am still facing: 1/ I have the following error message at boot: WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 4 p-states, using default stepper instead FakeSMC: key not found BEMB, length - 1 ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized Any idea why I do have theses errors and how to fix them? EDIT2: I am using an SMBIOS.plist with a MacBookPro4.1. So I try the one from Jichi who is with a MacBookPro3.1 and the result is now the following: FakeSMC: key not found BEMB, length - 1 ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized VID2: Not usable virtual bool IOHIDEventSystemUserClient::initWithTask(task*, void*, UInt32): Client task not privileged to open IOHIDSystem for mapping memory Any idea? @jichi: apparently, you have modified the FakeSMC.kext: any reasons for that ? 2/ I had to install EvOreboot.kext to be able to shutdown. Otherwise, I was stuck on the blue screen with the "waiting circle icon" . Normal? 3/ Sound is working (including + & - key on the keyboard) with VoodooHDA_261_HP_HDX18.kext.zip but the mute key does not work. Same for you ? 4/ VoodooBattery does not load: I have the following error message, the kext is in /E/E: com.apple.kextd[10]: Failed to load /Extra/Extensions/VoodooBattery.kext - (libkern/kext) authentication failure (file ownership/permissions). Any idea? EDIT: I installed the kext in /S/L/E and it works. Solved. Thanks for your help EDIT Feb 14th I have tried with a dsdt file provided by MadLon from this site. I now have my Dell booting but I still get the error ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized. @all: question for all of you running your E6400/E6500 with a dsdt file : can you check your dmesg and confirm weather or not you get the same error as me? If not, do you confirm you have C and P states enabled? Thanks
  15. La productivé sur m(h)ack ?

    Bjr J'utilise un Hackintosh depuis 3 mois sous SL très stable et plutot content d'apprendre un nouvel OS. Il est aussi en dual boot Win7. Moi ce qui me manque le plus ce sont les raccourcis claviers: quand je fais de l'éditions, les Home pour debut de ligne, End pour fin de ligne, Ctrl-Fleche pour se déplacer de mot en mot, les shift fleche gauche ou droite, Ctrl-Home/End pour début/fin de page, etc A chaque fois il faut prendre la souris. C'est clairement un manque ou j'ai loupé qque chose?
×