Posted 10 February 2012 - 11:29 AM
Posted 10 February 2012 - 02:59 PM
Boot0 is caused by faulty bootloader or/and bad partition table. Use only MBR partition table, GUID is not working for us (bios limitations)
I think I have a faulty bootloader. I installed off a partition on my MBR hard drive as I have a windows installation sitting side by side.
Posted 10 February 2012 - 06:53 PM
Also, can't get the lock trackpad thing to work, i'm failing to find the event id.. it may also be virtual.
Posted 10 February 2012 - 11:14 PM
Try googling for the 'debug voodoops2keyboard.kext' I will also try again in the meantime as I have found it before..
I would prefer to use the touch keys 2 and 3 for other shortcuts, eg. Sleep, screensaver etc. This may also help you to get the lock trackpad thing to work. Although I suspect that it has something to do with the trackpad driver, rather than the lack of a hotkey. Have you tried remapping it to an existing key, to see if it will lock at all?
Posted 11 February 2012 - 03:10 AM
I tried to load it and get it working on 10.7.3 but for some reason I get stuck on the 'still waiting for root device' error again. Really not sure what could be causing this.. I think I might go back to 10.7.2 as there really aren't any benefits to 10.7.3..
Posted 11 February 2012 - 06:51 AM
Posted 11 February 2012 - 06:54 AM
Did you manage to get the scan codes for the two touch keys?
Perhaps that is waht I WAS remembering, sorry.
Posted 11 February 2012 - 07:07 AM
Posted 11 February 2012 - 09:00 AM
Posted 11 February 2012 - 09:27 AM
Posted 11 February 2012 - 09:29 AM
Posted 11 February 2012 - 11:23 AM
Posted 11 February 2012 - 11:46 AM
Update: Here's a diff kext for the keyboard, it will allow you to assign new functions to the fn + f3 keys and the 3 touch keys. These keys are configured to use the numeric keypad (not found on our laptops) so if you use an usb keyboard and you assign custom events using Better Touch Tool you will trigger them using the 4 6 8 num pad keys.
Archive.zip 153.61KB 16 downloads
Posted 11 February 2012 - 02:21 PM
Edit: Turned out my active partition was Windows not OS X. After setting the active partition to OS X the theme came up as well as all the modules loading (they weren't before).
Posted 11 February 2012 - 02:31 PM
Posted 11 February 2012 - 07:31 PM
Ok thanks. I'm just crippled with the lack of wifi. Does anyone have any recommendations for the best mini-WLAN card to fit?
I bought a cheap Medion P89081 (MD 86498) wlan-n nano usb-dongle.
It works perfectly with the official Realtek RTL8192CU 10.7 Lion drivers from their website
Posted 11 February 2012 - 11:53 PM
Also, it could just be me. But I am noticing some rather strange behavior on my setup. I think it has something to do with my kext cache. Sometimes, after replacing a kext which is giving me errors (which I do via macdrive in windows), then booting with -f to ignore caches, I get stuck on the 'still waiting for root device' error on startup. But then if I boot without -f and just use -v, I observe it reading the kexts upon startup, then it will boot correctly.
To my understanding, -f should just manually read all the kexts, and if they are working corretly, the device should boot. But this doesn't seem to be the case.
Anyone observed this sort of behavior before? After entering the OS and rebuilding caches with kext wizard the OS will boot normally, but it just wont with -f? Very strange..
Also Doix, are the PS2 kexts you edited compatible with VoodooPS2Trackpad? As although I would like to have the extra keys to assign functions to. I would prefer to use the Voodoo trackpad kext, as I find it more suitable. Also I previously had issues with waking from sleep with the ApplePS2 kexts.
Posted 12 February 2012 - 01:10 AM
There is a decent set of instructions for doing this in posts 24-25 of this thread: http://osx86.co/f36/...1960/page3.html
Also, a very minor issue is the brightness. It would be nice to have it functioning as it does in windows. With the minimum and maximum settings available right after boot. I find that after sleeping the display, the minimum brightness is no longer 'dark' enough for night operation. I think there is information on that in the link provided as well.
I realize that I am 'plucking at straws' but with more and more issues being resolved, I figure it is worth pointing out things that can still be improved upon with this machine.
I will have a look at the DSDT mod for the audio and brightness later tonigh when I have time, but I am an amateur at best when it comes to DSDT modding. I figure that you will be able to resolve these issues with far less effort than I will
Posted 12 February 2012 - 09:06 AM
I can't enable audio only with DSDT, it requires binary patching and the "lag" is present on almost all non natively working audio chips.
Brightness thing won't happen, the values are stored in the driver, virtually, not in the acpi.
3 user(s) are reading this topic
1 members, 2 guests, 0 anonymous users