Posted 07 November 2012 - 03:48 PM
Posted 07 November 2012 - 06:36 PM
Also it's worth trying to swap it for a newer one, not an older one... since we are using a Gigabyte desktop motherboard VBIOS now it's very likely to support higher resolutions.
Posted 07 November 2012 - 08:57 PM
Posted 08 November 2012 - 11:33 AM
download the A11/A12 bioses from dell, run it and before the flash confirmation message comes up copy the winflash (and stock bios) files from your temp directory into a safe place.
Posted 08 November 2012 - 09:56 PM
I was able to troubleshoot .. the module which causes sleep/wake issues for OSX is PlatformSmm.efi and has GUID of CB73C3D9-2F01-4342-AE67-04DDE5264092
If you backport it from A06 to any version higher it will restore proper wake ...
Regarding VESA resolutions try the VBIOS @jkbuha has posted .. it's v2137.0 from a Lenovo laptop.. it carries 1366x768 for my LVDS and others (Inspiron 15R for example), so there's a high chance it will support Full HD as well.
Posted 09 November 2012 - 08:42 AM
Will keep y'all posted...
Posted 10 November 2012 - 12:08 AM
Does anyone know if it's possible to repair Windows Registry from OS X? For some reason my freshly installed W7 dropped dead the next day. As soon as the window logo disappears i encounter a short bluescreen then reset.
Posted 10 November 2012 - 01:07 PM
I'ts a good practice to disable autoreboot after BSOD occurs to be able to read the code.
Posted 11 November 2012 - 12:26 PM
Posted 11 November 2012 - 01:05 PM
You can't format as GPT and run a legacy bootloader (Windows XP/ Chameleon/Chimera/Legacy Installation of 7/8/Ubuntu)
To be able to utilize GTP-formatted hard disk you have to use a UEFI-compliant bootloader, such as Clover-UEFI for OSX and other OSes (which is a little bit finicky for Tiano UEFI, but still works absolutely fine thanks to @dmazar) or Windows Boot Manager (bootmgr.efi) well, for Windows-only obviously.
Posted 11 November 2012 - 02:48 PM
Got it fixed, I had to use another version of chameleon. r2070 from enoch did it for me.
Posted 11 November 2012 - 09:36 PM
Posted 12 November 2012 - 10:55 AM
Mine has stopped working for some reason in 10.8.2 .. I thought it was because of updating to A13, but rolling back to A04 didn't seem to fix it ..
The Fn+F4/F5 won't respond anymore .. I mean they don't adjust brightness any longer, nor the indication appears on screen.
I can set brightness controls from F14/F15 to just F4/F5 from Keyboards Preferences .. but I would like to have it like it was previously..
Any thoughts ?
Try this kext here please: https://dl.dropbox.c...Family.kext.zip
It should parse 0xE005 0xE006 WMI scancodes from the respective keys ..
Posted 12 November 2012 - 11:13 AM
Now, that kext doesn't work for me. Maybe you should give this one a try: https://dl.dropbox.c...Family.kext.zip
Posted 12 November 2012 - 11:15 AM
It worked previously in 10.7 .. and 10.8 if I recall correctly .. but now it just does absolutely nothing. Even debug logging is not showing up ..
Posted 12 November 2012 - 11:25 AM
Posted 12 November 2012 - 11:32 AM
No reaction to key combinations, no output in the IOLog ..
DellWMIController is present in IORegistry, all the keys defined in the wmi keyboard driver are showing up in the KeyMap .. but nothing.
Posted 12 November 2012 - 11:39 AM
Posted 12 November 2012 - 11:57 AM
The system indeed says
(kernel) Can't remove kext com.darwin.driver.IOWMIController; services failed to terminate - 0xdc008018.
Failed to unload com.darwin.driver.IOWMIController - (libkern/kext) kext is in use or retained (cannot unload).
Maybe they have transitioned away from using WMI (for Win 8) for brightness controls and now rely on regular scancodes such as for media-buttons and sound?
This must be hardcoded somewhere inside EC, since I haven't rolled back that part when downgrading back to A04 this has probably stayed .. ? Anyone with the latest bios can confirm this or prove this otherwise ?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users