Jump to content


  • Content count

  • Joined

  • Last visited

About avian

  • Rank
    InsanelyMac Protégé
  1. d6 working wonderfully here on 2 installs (one yosemite, one mavericks). Is jumbo frames still considered way too low a priority to make it into the v2 builds?
  2. Thanks for the tip regarding Blackmagic Disk Speed Test. I was just copying a 700gb folder over to a linux box via AFP, starting a stopwatch and looking at the "about 2 hours" as a guide, then trying to catch it at the end to stop the stopwatch. Granted I was also trying to test stability of large transfers at the same time, but I do I feel rather silly now. So far after 12 hours of the driver being in place, and a complete/new time machine backup to test it out a bit more, its still solid. Things are looking good. Thanks for your incredible work Meize. Also understood about the jumbo frames. I think its more psychological on my end more than anything, seeing almost all my equipment/switches etc support jumbo frames, it feels a little sad when the old hackintoshes are left out. But if its a major bit of work to implement, then its totally understandable - I'm just glad to have a driver for the i217V thats this stable so far.
  3. Mausi installed on a Gigabyte z97x-ud7th with Intel 217V on Mavericks 10.9.5. So far so good, a few large-ish transfer to check for issues, no problems yet. Out of interest is jumbo frame support something planned for the future?
  4. New Driver for Realtek RTL8111

    I really have nothing to add to the discussion except to say thank you so much for this driver. I installed v1.2.2 after having (different) issues with both the realtek and lnx2mac versions. So far yours seems the most superior in terms of speed, compatibility and stability. An (initial) 400gb time machine backup occurs substantially faster and more reliably now than it did before. Thanks Mieze!
  5. I can also confirm that on 10.9.2 and an Asus P8P67 Pro, that I also have no more issues with large file transfers using Riley Freeman's compiled version. Thanks! EDIT: Ends up that it still crashes, more stable than the 2.5.4 option, but alas no go. Back to 2.4.14 here.
  6. I'm having the same instability issues with 2.5.4d. Lots of kernel[0]: failed to getphysicalsegment in outputPacket messages in system log. It seems to be similar to the other stories in the thread. If I was to stream a HD movie over an AFP (the host being the computer with 2.5.4d installed), I'd be lucky to get an hour into it, before a crash. If one of the developers wants me to test anything out for them let me know, would be glad to help. In the meantime does 2.4.14 work in mavericks? If so I'll try that as a fix for now. PS: The instability seems to be on a gigabyte motherboard, whereas another almost identical osx install on an asus board also using AppleIntel1000E.kext 2.5.4d hasnt had any issues yet.
  7. RealtekR1000 v3

    Absolutely love the driver so far, seems to perform better than the lnx2mac one ive been using for eons. Is there any chance that Jumbo Frames will be supported in the future? I think thats the main thing missing between all the Realtek driver options.
  8. CheeseTank, I know this may sound counter-intuitive, but can you give this a go. Set up the line that corresponds to your LVDS exactly as it should be according to the bios dumps - except make it a DVI port, and for the controlflags make sure it supports Analog/VGA DVI output. Then let me know if the internal screen comes to life. (It may be out of range by default, so you might need to vnc to set a resolution it supports, or use edid overrides). It seems a problem many of us have (including Itansan's post above yours), where even with all the correct data edited into our ati-personality of choice, lvds simply doesn't work.. BUT we can manage to get it working as a crt/vga display. I really hope someone finds a *proper* solution to this soon. There are countless posts with people having the same issue, and without proper LVDS support (instead of of the screen being shown as crt) simple things like dithering for 6-bit screens can't be enabled (i.e. the majority of cheap internal 1366x768 screens)..
  9. Same scenario with a Lenovo y560p (i7-2630QM). Patch worked great here. Thanks flAKed (great work) and lenovo3000 (I wouldn't have tried it if you didn't mention the scenario with your ThinkPad).
  10. ATY_Init questions [6570M issues solved]

    Great stuff. I've experimented a little by reverting back to a default /S/E/Displays/Overrides folder and can say it doesn't work without EDID info added to display overrides here. On a side note I have to say the screen on this lenovo y560p is complete garbage. Almost worth selling the laptop because of the screen alone.
  11. ATY_Init questions [6570M issues solved]

    Sounds like what I was getting, except now I got a perfect screen every boot. Out of interest have you also edited the EDID info and what not in display overrides? I did that before editing ATY_init but not sure if thats helping at all, might try and remove the edits later and see if they were necessary.
  12. ATY_Init questions [6570M issues solved]

    Nah the device-id was being ignored completely (wasn't being looked for in the binary), so changing frame buffers or adding bin_image did nothing. I simply hijacked the 6900 series section (and linked deviceid 68c0 to that section) since its kinda redundant at the moment since they aren't supported, then changed frame buffers and added a rom image etc. Working fantastically well. Just gotta tweak a few settings like 6bit dithering and what not, ill do that tomorrow. Yeah GraphicsEnabler didn't handle my 6570M well at all. Out of interest do you ever get your graphics working right with GraphicsEnabler? Like an occasional boot where it works? If so, during that successful boot dump your ioreg ("ioreg -lw0 > saved_ioreg.txt"). That way you got the majority of info and a bios dump to include in ATY_Init. Anyway what I did was pretty crude. In the binary file inside the kext (ATY_Init/MacOS/ATY_Init) all I did was replace the two mentions of 6719 with the device I wanted to use. Do it with a hex/binary editor like 0xED. Then in the Info.plist file, make the changes you want under the "6900 series" section. So change frame buffer values and display-type, connector-type, put in your ati bios image if you think it'll help. Just don't change the name of the section itself. Like I said, crude, but it works. And works better than the (at this time) latest chimera/chameleon branches compiled with ati.c edited to know about our 6xxx mobility chips.
  13. ATY_Init questions [6570M issues solved]

    Looks like its in the binary itself. Im gonna try hex editing it a bit and see how I go.. Just incase anyone is interested.. Edit: Binary editing worked. Card now posts, just gotta nail the settings in info.plist. If anyone with a lenovo y560p (device 68c0) is interested, ill post the results later if successful.
  14. Hi guys, I got a somewhat silly question, so Im hoping its easy to get an answer. Regarding Netkas's latest version of ATY_init.kext (found here http://netkas.org/?p=880 ). Looking at the Info.plist, I notice there are categories (child entries) along the lines of "5870 Series" and "6800 Series", but within each category I can't see how the actual card is detected. There is the occasional VendorID line, but no obvious deviceid lines or similar. So how is it done? Im hoping to add a section for 6570M and have most of the info needed (via an ioreg dump), and most of it seems to make sense, except I have no idea how to tell it that its device 68c0, or whatever method netkas is using. Any help to get me started would be great, I think I can handle most of the rest myself!
  15. ATI Radeon 6xxx, working QE/CI

    Good card. I just got mine today (the ZDBC version - even though I doubt I'll notice the 40MHz overclock much) and its noticeably faster than the 4870 it replaced in OSX. To to mention ridiculously silent. Thanks to netkas/andy/etc its working perfectly with no crashes in dvd player either.