HW Brand new Gateway SX2800 running Intel® G45/G43 Express Chipset
SW ideneb 10.5.5
I tried doing this but my PC boots into a blue screen and remains there. I tried safe mode by doing F8 and -x but it still comes back to the blue screen.
Tienneke suggested deleting AppleIntelGMAX3100.kext. How do I do that? Can I do it coming to the command prompt after hitting F8? Some details would help
Yes, it is possible.. I'll give you step by step instructions:
- mount -uw
- cd /System/Library/Extensions
- mv *your device ID*AppleIntelGMAX3100.kext /
You might notice I put mv instead of rm (move instead of delete), just so you could very easily try if you need the kext again. The script doesn't touch the standard AppleIntelGMAX3100, so there's no need moving that away.
What device ID do you have? (if you boot into graphics mode do the following: apple icon (top left corner of your screen) --> about this mac --> more info --> Graphics, look at the right column, there'll be a line stating your device ID..)
So lucky,Its work for me,But another problem come,the cursor disappeared,So ,what to do next?
That's an issue that we have not been able to pinpoint yet. It appears consistently on laptops with 2 graphics cards (lenovo T500, got an integrated GMA X4500 and a dedicated radeon), and on some other pc's too.. We can't yet help you, the best solution is making your cursor bigger (in system preferences). There'll be a point where the cursor reappears (it'll be quite big)
BTW, great work; getting there.
I have an Asus P5Q-EM; the device id is
00:02.0 VGA compatible controller : Intel Corporation Eaglelake Integrated Graphics Controller [8086:2e22] (rev 03)
then I noticed this:
00:02.1 Display controller : Intel Corporation Eaglelake HECI Controller [8086:2e23] (rev 03)
I'm thinking this is probably the HDMI side of the on-board?
I've yet to play with this enough to know if the mac side even sees the HDMI, but that would be Sweet!
It's really a community effort, a great community.
The two devices are most probably the graphics controller and the graphics memory controller, that has a different device ID (got that from coldequation).. If you want to know more about that, you can read all about it in the linux device docs for X4500 (coldequation gave me the infos, but really was not so interested that I would read through it
Okay, here's my process and results so far:
HW: Asus P5Q-EM with x4500 integrated on-board
Comes up fine in 1024x768; no adjustments available.
System Profiler reports:
VRAM (Total): 64 MB of Shared System Memory
Vendor: Intel (0x8086)
Device ID: 0x2e22
Revision ID: 0x0003
Kernel Extension Info: No Kext Loaded
Resolution: 1024 x 768
Depth: 32-Bit Color
Core Image: Software
Main Display: Yes
Quartz Extreme: Not Supported
I first ran the script by itself, free of any additional arguements (I had previously put the lspci.txt at root)
Script ran fine; found the ID, created the kext, and gave me the "This is not a tested (stock 10.5.7) AppleIntelGMAX3100 version, but it might work anyway." I am running an iDeneb-based vanilla kernel install, updated to 10.5.7
Repaired permissions, rebooted, got the nice blue screen, followed by a blank dead screen, and my monitor giving me the "out of range" comment
Said "hmmm...."; deleted the kext and boot back into the stock driver.
DL's the 10.5.7 combo update, used Pacifist to replace the stock apple driver. Rebooted (for grins), ran the script again; same error message (so is the script seeing the "stock" apple driver correctly?)
booted into superuser, moved the stock apple driver out to a folder at root (to make sure somehow it and the modified kexts were separated), and rebooted again with -f.
Same result; dead black screen.
Any ideas or suggestions appreciated; I am curious about the error message coming out of the script after re-installing the known 10.5.7 kexts from the combo update...
THis would be really nice to get working, as the accepted graphics workaround for the P5Q family has been a pci card...and those nvidias are about as quiet as a 747 coming in low over your house...
UPDATE: THe chipset I'm using is a G45, and so the graphics unit is really an X4500HD...could it be that this is significantly different enough from the X3100 driver set that it isn't getting it done?
Well, great we fount somebody with X4500HD.. Up till now we only tested on X4500MHD, the mobile version. It can be interesting if you would want to do more testing, but the testing is best to happen in the non-genius bar thread ( http://www.insanelym...howtopic=129744
). It seems that our method might not work directly for X4500HD, but maybe with a little fiddling?
(I'm mostly over optimistic