Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About GhaleonX

  • Rank
    InsanelyMac Protégé
  1. Final thoughts on Windows 8: awful

    I lol'd at this answer. Of course, I had read the article before I saw the 'post' option. Perhaps I should have said "The way this review is written doesn't really focus on what the author didn't like, but rather how much they didn't like it". Also, out of those 62.4 million results you mention, I'll bet 62.39 million of them are a result of searching for anything containing the words "windows", "8", "is", and "{censored}". If you search with that whole phrase in quotes, then it should only search for something with that exact phrase (not variations), but by that wording, you're most likely to only find more reviews that are lacking the details I wanted. Furthermore, I'm not interested in searching the web for why people might hate an unreleased OS - when I see a post that is linked to IM's front page that posts a review of it, yet doesn't really go in depth about the experience, really leaves me with the question "was this just to bash windows intentionally"? From my own Windows 8 experience, I have very few (if any) qualms. The only major difference is the start menu being changed into the 'metro launcher', which still holds all the stuff the start menu would, and you can still type something (notepad or cmd, for example) just like in windows 7. There's better integration for getting frameworks for programs you might install (not everything, but more than my Windows 7 Ultimate desktop does). I also happen to like the look and feel of the 'metro' versions of apps like IE and WMP, but as I'm using a preview edition, there are some bugs, but thankfully the standard versions of every program is still present. Windows Explorer is virtually identical in look and operations to Windows 7's version, so I'm not seeing how people can get lost. Maybe the big issue is just they miss the look of windows 7 (because again, the functionality of the start menu still exists in the same way for the metro launcher, it just looks different)? Actually, *I* asked why many people thought Windows 8 was "{censored}" - apparently someone else felt the same way I did about the reply before I read it
  2. I work with a RME Fireface 800, too When we first got it we had some issues with it, but after updating the RME to the latest firmware, everything was good to go after reloading our configuration settings. If you have not already updated your RME's firmware, I'd suggest doing that FIRST. That being said, if you already have the current firmware, and if all your other firewire devices work flawlessly, I'd suggest trying the RME on another computer and seeing if you run into problems. The problem you describe, however, suggests to me that you may have some DSDT fixing to do. FWIW, I've seen many audio problems (even with other external interfaces like mbox2) that will not go away until you have a proper enough DSDT to have proper IRQ routing (main problem area is HPET). In fact, I've seen many people who end up getting a real Mac for audio production because of problems with their hackintosh. You should only use a hackintosh for professional work if it's very thorough, and of course, very vanilla.
  3. Final thoughts on Windows 8: awful

    I don't see how people can complain about 8 and praise 7 - is it the change in the start menu/metro that's just offputting to you? I've been playing with W8 since the first CP was released on their website, and for the most part, it's not very different from 7; Windows explorer works the same way. I kinda like the metro versions of WMP and IE, but (fortunately) even if I didn't, the 'legacy' versions are also present, and can be pinned to the taskbar or shortcutted or whatever, just as in the past. I really don't see the downside to W8, but am interested to know what exactly is causing people to get upset about it.
  4. HWSensors

    This also seems to work nicely for NCT677F (same chip you have) on my ASRock X58 Extreme6. I did multiple readings from my BIOS and the voltage values seem to fall within the range I obtained from there, so if they're not exact, they're at least accurate. My BIOS doesn't give me Aux 3.3v however, so I'm not sure if that seems right or not. Temperatures might need adjusting, unless my CPU/NB gains at least 10C from the BIOS until OSX loads - we should probably check with an external sensor of some kind, and I may even try and fine-tune voltage readings with a multimeter (if I find the time). Thanx for sharing!
  5. HWSensors

    I'm not sure if I understand correctly, because I'm failing to see where *exactly* you got the vraw values for 5V and 12V; It seems as though you're saying that should be the value that I currently have reporting from HWMonitor, but the screenshot you provide suggests otherwise. I obtained a dump from both Open Hardware Monitor, and HWMonitor (both in Windows), but I couldn't find your 'vraw' values in what you posted there, either. I obtained my vref values from my BIOS: vcore - ~1.240 + 3.30 V - 3.216 + 5.00 V - 5.064 +12.00 V - 12.830 Another downer about the reports I got from Windows is that neither program recognizes my chip as NCT6775F; instead, Open Hardware Monitor detects it as NCT6771F, and HWMonitor detects NCT6771for LPCIO and then NCT6776 for hardware monitors. Everest says W83677HG / NCT6771F. I'm including what I've got so far. HWMonitor.txt voltages.txt sensors.txt
  6. HWSensors

    I have Nuvoton NCT6775F which is partially working with this. Anything I can do to help bring full support?
  7. Intel GMA4500 / GL 4x Express Chipset

    Would be great if we could figure out a way to get qe/ci working. Has anyone tried modifying chameleon's GraphicsEnabler?
  8. ASRock X58 Extreme 6 Vanilla Install

    Original post updated. Files should be good for Snow Leopard/Lion/Mountain Lion!
  9. I'm definitely interested in something like this!
  10. GeForce 6200 LE - possible to enjoy s-video?

    I decided to re-obtain NVEnabler, and now it's working. S-video, hurray (thanx, Krazubu)! Unfortunately, I still have two issues to deal with: Wake from sleep after long periods DVDs with average bitrate have jumpy video I can put the system to sleep and wake it just fine immediately, but if I leave it for an hour or so and try to turn on, the system powers, but there is no display, and no sign of waking other than the fans spinning. The skipping issue could be due to only being 128MB card, but I'd think that *should* be sufficient for DVD playback (I'll try to verify in windows later).
  11. GeForce 6200 LE - possible to enjoy s-video?

    Still playing with things... I changed my NVCAP value, and took the 2nd display (@1) out of it (since I've only got one VGA and the s-video should just be a mirror)... still no s-video display, but I've got QE/CI/Res change still. I ran a program called 'specy' in windows on this computer and it said the AGP slot number was 4 - I tried using (_SUN, 0x04) under (GFX0), but System Profiler just says PCI3 for slot. I moved that entry under Device (AGP) and now on my PCI Cards list it lists 'pci-bridge' and type 'PCI-to-PCI Bridge' (I added a DSM entry to change the type to read 'PCI-to-AGP Bridge' instead, but I believe that's only cosmetic). Here's the current GFX section of my DSDT: Device (AGP) { Name (_ADR, 0x00010000) Name (_SUN, 0x04) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "device_type", Buffer (0x12) { "PCI-to-AGP Bridge" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Device (GFX0) { Name (_ADR, 0x01000000) Name (_SUN, One) Method (_DSM, 4, NotSerialized) { Store (Package (0x16) { "device-id", Buffer (0x04) { 0x20, 0x02, 0x00, 0x00 }, "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@0,display_cfg", Buffer (0x08) { 0x03, 0x01, 0x00, 0x00 }, "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x01, 0x00, 0x00, 0x00, 0x03, 0x00, /* 0008 */ 0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "NVPM", Buffer (0x20) { /* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0018 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x08 }, "device_type", Buffer (0x0D) { "NVDA,GeForce" }, "model", Buffer (0x1B) { "Nvidia GeForce 6200 128 MB" }, "rom-revision", Buffer (0x0E) { "5.44.A2.03.02" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } It'd be awesome if I could find an ioreg and dsdt from a g4 powermac or something... I'd like to see if I can't get it using AGP drivers (even though they're for PPC architecture... worth toying with tho)
  12. GeForce 6200 AGP on SL

    I have the same gfx card on an older (ich4 that thinks it's ich8) chipset, and got it working fine (mostly). GraphicsEnabler should work just fine from nearly any chameleon revision. If it does, you can grab the values it's using from ioreg and plug them into your dsdt, though if you use all the same values, I'm not sure what the advantage of using it over GraphicsEnabler would be. You can click on my sig (Shuttle SB51G link) and see a dsdt of mine (though I've revised it 30 times since posting it) if you want something that should at least get it 'working', and you can adjust it to your liking after that. Has anyone ever got S-Video working on this card? I can't seem to get it by any means, and I've tried everything I can think of. I'd also like to get System Profiler to report this is on AGP, but I'm not sure what values to inject for that - using AGPGart will change what system profiler says, but doesn't work w/ the dsdt entry (yet, at least... or I'm doing something wrong with agpgart)
  13. New AGPGart

    Hello slice, and thanx for all your hard work! I have attempted to use various versions of your AGPGart kext and am not having much luck (2.7.0 gives me hope; 2.7.1 seems not to work for me). I've been using DSDT injection for graphics, but if I get AGPGart to load, I cannot use DSDT injection, GraphicsEnabler, NVCAP string in boot.plist, or hex string in boot.plist. I did manage to get resolution working with a combination of dsdt injection + nvcap string, but perhaps I'm doing some things wrong. I must admit, I don't fully understand how I should go about adjusting the values of AGPGart, so I may be messing up on that end. Additionally, out of all the aforementioned ways I have to get graphics working (full qe/ci etc), s-video doesn't work for any of them. Here's my system specs: 845G / ICH4 (spoofed as ICH8 for several devices) eGeforce 6200 LE 128MB AGP Pentium 4 Northwood (SSE2-only) 2GB DDR Ram (Chameleon detects as 0mb, and profiler has trouble seeing it, too) If it'd help to look at my DSDT, ioreg, or other system info, I have all those files posted in this thread - (I've only changed a few minor things to the DSDT, like removing the secondary display tags since it's only got 1 vga port). My AGPGart Info.plist has the following in it: <key>AGP_Base</key> <integer>0xf0000000</intiger> .. <key>AGP_Mode</key> <integer>4294967295</integer> .. <key>IOAGPFlags</key> <integer>1</integer> Here's a list of all the combinations I tried. If I boot with... AGPGart + no injections/enablers = I get VESA graphics + System Profiler reports AGP as 256MB AGPGart + DSDT GFX = I get black screen w/ movable cursor, then flashes blue then black again w/ smaller cursor AGPGart + Graphics Enabler = I get VESA only + System Profiler reports AGP as 256MB AGPGart + NVCAP in boot.plist = VESA + Profiler reports 256 AGPGart + NVCAP in boot.plist + GraphicsEnabler = Profiler reports 256 AGPGart + NVCAP in boot.plist + DSDT Injection = Screen goes blue, then black w/ smaller cursor than res boots AGPGart + NVCAP in boot.plist + NVCAP Hex = No display at all AGPGart + NVCAP + Hex + GraphicsEnabler = No display at all AGPGart + NVCAP + Hex + GraphicsEnabler + DSDT = full res (no QE/CI) but profiler crashes on graphic displays AGPGart + NVCAP + Hex + DSDT = full res (no QE/CI) and profiler crashes when selecting 'Graphics / Displays' AGPGart + Hex = no display AGPGart + Hex + GraphicsEnabler = no display AGPGart + Hex + GraphicsEnabler + DSDT = full res (no QE/CI) + Profiler crashes on 'displays' AGPGart + Hex + DSDT = full res (noQE/CI) + profiler crash I just went back and tried booting w/ just the hex and/or nvcap in my boot.plist (no dsdt injection, and no agpgart), and apparently they don't work - I must've made it wrong (d'oh), but I'm keeping all the data in case it helps someone point me in the right direction of things. How I (improperly, albiet) made my NVCAP/Hex: 1) Downloaded GPU-Z in windows and saved the video card's bios (NV44.bin) 2) Renamed to NV44.rom and used NVCAP Maker 1.4 3) Used gfxutil to convert NVCAP to hex. So either GPU-Z didn't dump the bios properly, or NVCAP Maker can't read it for my card. I'm out of cigarettes now, so I'll post this as I run to the store *Update* I used a different utility to dump the BIOS and got a diff NVCAP value - still no change. Hrmm...
  14. GeForce 6200 LE - possible to enjoy s-video?

    I spent nearly my whole day yesterday trying to find a way to get AGPGart to work: I tried a few different base values, but only 0xf0000000 seems to work; (not sure how to do the math on this one) I tried a few different versions; only 2.7.0 seems to work for me AGPGart loads, but no QE/CI I used GPU-Z in windows to dump my video card's bios, renamed the .bin to .rom and ran thru NVCAP Maker 1.4, and tried both making a .hex for device-properties, and using <key>NVCAP_0222 (not at the same time). No QE/CI when AGPGart loads whether I use DSDT Injection, GraphicsEnabler, NVCAP, or device-properties. Guess I'll play with it a bit more later, tho.
  15. Wow, I'm SO very sorry for overlooking your question - if you're still needing an answer, my recommendation is to use nawcom's mod cd with a retail OS X disc (not one that came with a computer, as those are more hardware-specific). Once you have an install you can boot into, you can start cleaning up the dsdt if you're interested.