- Joined
- Oct 19, 2011
- Messages
- 51
- Mac
- Classic Mac
- Mobile Phone
Hi! I'm really glad to have made it to 10.7.2 and be able to boot and have most functionality!
Video display is not ideal. I only have 1028x768 resolution. My "real mac" with the same monitor allows lots of choices, one of which being my preferred 1360x768. Youtube videos won't display though the pages load fine and I can hear the audio fine. Now, I just tried out a DVD for kicks, but DVD Player says:
There was an initialization error
A valid video device could not be found for playback. [-70017]
After reading lots of threads/suggestions, I have used the Mac Mini system definition via MultiBeast's Customization options.
My BIOS is revision 11, the DSDT Database only has previous versions ending with 10 at the time I'm writing. I had extracted the attached DSDT VeryModernDSDT.AMLfor MultiBeast's User DSDT option when building from 10.6.3-->10.6.8 and it's entirely possible this is the main problem with my lack of complete video support at this time - I'm not an expert at any of this to be sure.
Here's what my System Report says about graphics/display. Interestingly, the window's title bar says Mac Mini but the status/info bar at the bottom of the window says "[User]'s Mac Pro" (that's where it shows a "tree" of where you're browsing in the system report, be it in Hardware-USB-USB High-Speed Bus, Network-Locations, etc). Everywhere I know to look, it's identified as a Mac Mini except there, and I think maybe since that's probably what was first defined on initial install before I did more reading and used MultiBeast to change to Mac Mini, maybe the original just stuck. "About this Mac" shows Mac mini Mid 2011 for what it's worth:
Display:
Type: GPU
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x0112
Revision ID: 0x0009
Kernel Extension Info: No Kext Loaded
Displays:
Display:
Resolution: 1024 x 768
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
From terminal [oh, there's that mac pro business again - I think it's only in name], here's the information I saw requested in other posts about video troubles:
admins-mac-pro:~ admin$ ioreg |grep ATY
admins-mac-pro:~ admin$ bdmesg |grep Framebuffer
Read HFS+ file: [hd(0,2)/System/Library/Extensions/AppleIntelIntegratedFramebuffer.kext/Contents/Info.plist] 2307 bytes.
Read HFS+ file: [hd(0,2)/System/Library/Extensions/ATIFramebuffer.kext/Contents/Info.plist] 2342 bytes.
the ioreg didn't give anything back but the prompt.
I had in the past played around with MultiBeast's Miscellaneous - FakeSMCPlugins - Motherboard Plugins and its ACPIMonitor.kext, IntelCPUMonitor.kext and SuperIOFamily.kext FakeSMC plugins are indeed in my /Extra/Extensions but as I write this, I realize they are not in my /System/Library/Extensions
Here's what's in my org.chameleon.Boot.plist:
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>npci=0x2000</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>device-properties</key>
<string>4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600051c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001</string>
that last one is so that my onboard Ethernet would work correctly in order to get to the App Store from 10.6.8 and purchase the Lion installer.
Besides the video question, I have an ancillary concern. I had considerable difficulty getting to this point with 10.7.2 (some of the story is detailed on this thread http://tonymacx86.com/viewtopic.php?f=169&t=43693&p=279303#p279303) so I want to be better informed so as to avoid those troubles again. I think that the MultiBeast-packaged bootloader was a factor in my troubles, as I really only saw a difference after installing Chimera 1.7.0. If I use MultiBeast again with UserDSDT or anything that might alter the bootloader, could I then run the stand-alone installer for Chimera 1.7.0 and feel safer rebooting?
Thanks very much.
Video display is not ideal. I only have 1028x768 resolution. My "real mac" with the same monitor allows lots of choices, one of which being my preferred 1360x768. Youtube videos won't display though the pages load fine and I can hear the audio fine. Now, I just tried out a DVD for kicks, but DVD Player says:
There was an initialization error
A valid video device could not be found for playback. [-70017]
After reading lots of threads/suggestions, I have used the Mac Mini system definition via MultiBeast's Customization options.
My BIOS is revision 11, the DSDT Database only has previous versions ending with 10 at the time I'm writing. I had extracted the attached DSDT VeryModernDSDT.AMLfor MultiBeast's User DSDT option when building from 10.6.3-->10.6.8 and it's entirely possible this is the main problem with my lack of complete video support at this time - I'm not an expert at any of this to be sure.
Here's what my System Report says about graphics/display. Interestingly, the window's title bar says Mac Mini but the status/info bar at the bottom of the window says "[User]'s Mac Pro" (that's where it shows a "tree" of where you're browsing in the system report, be it in Hardware-USB-USB High-Speed Bus, Network-Locations, etc). Everywhere I know to look, it's identified as a Mac Mini except there, and I think maybe since that's probably what was first defined on initial install before I did more reading and used MultiBeast to change to Mac Mini, maybe the original just stuck. "About this Mac" shows Mac mini Mid 2011 for what it's worth:
Display:
Type: GPU
Bus: Built-In
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x0112
Revision ID: 0x0009
Kernel Extension Info: No Kext Loaded
Displays:
Display:
Resolution: 1024 x 768
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
From terminal [oh, there's that mac pro business again - I think it's only in name], here's the information I saw requested in other posts about video troubles:
admins-mac-pro:~ admin$ ioreg |grep ATY
admins-mac-pro:~ admin$ bdmesg |grep Framebuffer
Read HFS+ file: [hd(0,2)/System/Library/Extensions/AppleIntelIntegratedFramebuffer.kext/Contents/Info.plist] 2307 bytes.
Read HFS+ file: [hd(0,2)/System/Library/Extensions/ATIFramebuffer.kext/Contents/Info.plist] 2342 bytes.
the ioreg didn't give anything back but the prompt.
I had in the past played around with MultiBeast's Miscellaneous - FakeSMCPlugins - Motherboard Plugins and its ACPIMonitor.kext, IntelCPUMonitor.kext and SuperIOFamily.kext FakeSMC plugins are indeed in my /Extra/Extensions but as I write this, I realize they are not in my /System/Library/Extensions
Here's what's in my org.chameleon.Boot.plist:
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>npci=0x2000</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>device-properties</key>
<string>4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600051c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001</string>
that last one is so that my onboard Ethernet would work correctly in order to get to the App Store from 10.6.8 and purchase the Lion installer.
Besides the video question, I have an ancillary concern. I had considerable difficulty getting to this point with 10.7.2 (some of the story is detailed on this thread http://tonymacx86.com/viewtopic.php?f=169&t=43693&p=279303#p279303) so I want to be better informed so as to avoid those troubles again. I think that the MultiBeast-packaged bootloader was a factor in my troubles, as I really only saw a difference after installing Chimera 1.7.0. If I use MultiBeast again with UserDSDT or anything that might alter the bootloader, could I then run the stand-alone installer for Chimera 1.7.0 and feel safer rebooting?
Thanks very much.