Jump to content

mackerintel

Members
  • Content count

    122
  • Joined

  • Last visited

About mackerintel

  • Rank
    InsanelyMac Geek
  1. mackerintel

    Hope for AR5007EG?

    disassembler and binary patching
  2. mackerintel

    Hope for AR5007EG?

    Probably you confuse two similar cards: AR5006 and AR5007. AFAIK the first one can be rebranded whereas the second can't. About just bypassing the checks it was the first thing I changed nad it failed then with another error (I/O error if I remember correctly). Making different versions would take a huge amount of time which unfortunately is a scarce resource for me now. What I could do is to release all the intermediary binaries I had. But I fear it would add even more confusion. As whole AR5007 never worked and if you want to continue the work and need the source just use otool -t -v: it's the only source I ever had. I could also release the code I used to inject additional data in sections but this code is ugly and unreadable. Now I happily use AR5008 which needs no modifications, is recognised as Airport, works under all OSes supporting wireless and has opensource drivers. So I would recommend to buy AR5008. AR5007 is somewhat a dead end. I don't say it's impossible but you need to spend a lot of time to make it work. Last sentence may however reveal to be wrong
  3. It was a long time ago that I explained why SSDT override is unnecessary. I repeat in 2 words: put contents of your SSDT to DSDT and add option DropSSDT=y
  4. As time goes by it seems that netkas has never intended to release the source Nowhere. It's only for developers.
  5. iNDi is working on it and has made some spectacular progress
  6. I don't really see the point of this version. SSDT can easily be added to DSDT and then you may specify DropSSDT=y and original SSDTs will be ignored. I said this somewhere in the topic dedicated to DSDT patch but that topic is now way too bloated. About 64k limit, extra and so on: it's already done in experimental chameleon. We're work on some nice features now.
  7. ¡Hola, macgirl! Gracias para tu trabajo. Puedes tambien publicar el source? De preferencio sería en una forma de patch. Gracias
  8. mackerintel

    Custom Boot Screen (chameleon mod)

    Wait for next Chameleon release
  9. mackerintel

    Custom Boot Screen (chameleon mod)

    I post the PNG of original apple logo and stretched version which looks ok after being stretched on wide screens. A nice and simple picture is http://en.wikipedia.org/wiki/File:PNG_tran...nstration_1.png (I use it myself but I stretched it to compensate stretching on wide screen)
  10. mackerintel

    Chameleon with SMBIOS patching

    Here is SMBIOS information from your ioreg: Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: LGA 775 Type: Central Processor Family: Pentium 4 Manufacturer: Intel ID: 76 06 01 00 FF FB EB BF Signature: Type 0, Family 6, Model 23, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Hyper-threading technology) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Xeon(R) CPU E3110 @ 3.00GHz Voltage: 1.2 V External Clock: 333 MHz Max Speed: 3000 MHz Current Speed: 3000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: 0x0007 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M. MacPro1,1: Handle 0x0000, DMI type 4, 35 bytes Processor Information Socket Designation: CPU-B ( 0 ) Type: Central Processor Family: Unknown Manufacturer: Intel(R) Corporation ID: F6 06 00 00 FF FB EB BF Version: Intel(R) Xeon(R) CPU Voltage: 1.6 V External Clock: 333 MHz Max Speed: 2660 MHz Current Speed: 2660 MHz Status: Populated, Enabled Upgrade: ZIF Socket L1 Cache Handle: 0x0003 L2 Cache Handle: 0x0001 L3 Cache Handle: No L3 Cache Serial Number: Not Specified Asset Tag: Unknown Part Number: Not Specified So actually your info is much more complete then in MacPro. Your problem is one of the following: -OSX expects "Intel® Xeon® CPU" and not "Intel® Xeon® CPU E3110 @ 3.00GHz". Most probable -OSX expects "Intel® Corporation" and not "Intel". Unprobable since on my OSX it works and my SMBIOS says "Intel" -Family OSX may expect "Unknown" and not "Pentium 4". Don't think so -OSX checks secondary fields like "Socket type". Don't think so -You have a CPU model which has never been in a mac (notice that there are different Xeons). Second most probable I don't even know if processor name comes from SMBIOS and not from CPUID. If you're interested in checking theese possibilities I'll post a version able to change these values EDIT: I made a version which changes CPU version and even when I set it to "beauty" (just unrelated string) my CPU was still correctly recognised by OSX even if its name wasn't in SMBIOS anymore. So I think OSX uses CPUID for determining CPU model and your CPU has never been in MacPro
  11. Truemobile is usually considered quite bad card. Additionally it doesn't have opensource driver which means bad support under anything other then OSX or windows. I prefer Atheros. I bought "Atheros AR5008e-3NX 802.11a/b/g/n internal mini-pci-express card". This card is similar to ones found in some macbooks and it works as a charm OTB under windows,linux and OSX(vanilla IO80211Family). There are also drivers for solaris, FreeBSD and probably just any OS supporting WLAN at all but since I currently don't have any other OS (then windows, linux and osx) installed I can't test this
  12. mackerintel

    DSDT Patcher

    Acquire (MTX0, 0x0000)->Acquire (MTX0, 0xFFFF) Acquire (MUT0, 0x0FFF)->Acquire (MUT0, 0xFFFF) http://ubuntu-virginia.ubuntuforums.org/sh...ad.php?t=869249
  13. mackerintel

    Removing CPUID checks and decrypting OSX binaries

    Not at all. CPUID is said to be slow instruction. So emulating it isn't much slower. Additionally it's recommended to run cpuid once per program and store its result. If apple follow this convention then there is no performance hit. I really don't see why an app would want to execute CPUID in a loop
  14. mackerintel

    DSDT Patcher

    Just delete this line
  15. Well. It seems that difference between working and not working AR5007 is quite random. My hypothesis: 1) BIOS. Some BIOS probably initialise AR5007 better then others 2) Subdevice. While chipset is done by atheros there are still some components tweaked my "subvendor" 3) DSDT. Some DSDT may bring up AR5007 more nicely 4) EEPROM 5) different ioreg declarations To check this hypothesis we would need output from (under linux): lspci -vvn ath_info -d [address] Where address comes from "Region 0: Memory at ...." line from lspci. And from OSX: ioreg -lw0 And also DSDT dump P.S: you may use -f boot parameter instead of deleting Extensions.mkext
×