126 replies to this topic

[attacknick]

very nice. thanks OP

[TIPSotto]

Nice app..thanks will try it out

[Brahim B]

nice
thnx
info sent

[BlackCH]

How the database would handle patched kexts (LegacyHDA plist kexts or patched binaries)?

[el coniglio]

BlackCH, on Jun 7 2010, 04:45 PM, said:

How the database would handle patched kexts (LegacyHDA plist kexts or patched binaries)?

Right now it will only evaluate the CFBUndleName and version to identify the kext. If a patched version has the same bundle/version it will take as the original.

I am planning to allow multiple instances of the same kext when the download feature is ready (when you select the download button, it will list the available kexts and its description), so people can download a patched version for a specific device or situation.

Soon I'll release a new version of the client with the capability of selecting which kexts the "Transmit data" is going to send information, so if a kext is loaded and linked but isn't working as it was supposed to be, the user can unselect it.

[blackosx]

This is a good idea. Good work.
I have just submitted my data

[johnnyknt]

Very Very Nice can't wait for the download functionality to start working this will be my only place to find kexts.... keep up the good work

[el coniglio]

A new version has been released (0.3), now the app allows the user to unselect those kexts which aren't working or doesn't want to submit.

The download and upload in the navigation interface are now working and some new features were added.

[donkey]

thanks!

[node]

El Coniglio,

Posted a request for your help here:

http://www.insanelym...p;#entry1496395

Can you have a look at it please, and post your reply either here, or there. Thanks

[XLR]

Does it works on the same principle as OSX86Tools and RebelEFI?

[rednous]

nice and handy app  
contributed

[xWaLeEdOoOx]

uh thank you,, very usefull

[valv]

keep up the good work.

[aylamrin]

Awesome app.
Info sent ...
Many thanks !

[spannernick]

Thanks works great,just what we need..

Info sent..

[GLXOZ]

Perfect work!!!

[scrax]

I have a question, what about different ID injected by dsdt?
Because i've some strange value that differ from the lspci -nn i get from linux:

SystemInfo results:

10de;nVidia Corporation;0aab;MCP79 PCI Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ac4;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ac7;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ac7;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ac7;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ac6;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0a89;MCP79 Memory Controller;Memory controller;RAM memory
10de;nVidia Corporation;0aa0;MCP79 PCI Express Bridge;Bridge;PCI bridge
10de;nVidia Corporation;0ab0;MCP79 Ethernet;Network controller;Ethernet controller
10de;nVidia Corporation;0aa9;MCP79 EHCI USB 2.0 Controller;Serial bus controller;USB Controller
10de;nVidia Corporation;0aa7;MCP79 OHCI USB 1.1 Controller;Serial bus controller;USB Controller
10de;nVidia Corporation;0aa6;MCP79 EHCI USB 2.0 Controller;Serial bus controller;USB Controller
10de;nVidia Corporation;0aa5;MCP79 OHCI USB 1.1 Controller;Serial bus controller;USB Controller
10de;nVidia Corporation;0aa3;MCP79 Co-processor;Processor;Co-processor
0a98;Unknown device;10de;Unknown vendor;Memory controller;RAM memory
10de;nVidia Corporation;0aa2;MCP79 SMBus;Serial bus controller;SMBus
10de;nVidia Corporation;0aa4;MCP79 Memory Controller;Memory controller;RAM memory
10de;nVidia Corporation;0a88;MCP79 Memory Controller;Memory controller;RAM memory
10de;nVidia Corporation;0a80;MCP79 Host Bridge;Bridge;Host bridge

lscpi -nn in linux:

00:00.0 Host bridge [0600]: nVidia Corporation MCP79 Host Bridge [10de:0a80] (rev b1)  [b]0a82[/b]
00:00.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a88] (rev b1)
00:03.0 ISA bridge [0601]: nVidia Corporation MCP79 LPC Bridge [10de:0aac] (rev b2)	[b]0aae[/b]
00:03.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0aa4] (rev b1)
00:03.2 SMBus [0c05]: nVidia Corporation MCP79 SMBus [10de:0aa2] (rev b1)
00:03.3 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a89] (rev b1)
00:03.4 RAM memory [0500]: nVidia Corporation Device [10de:0a98] (rev b1)
00:03.5 Co-processor [0b40]: nVidia Corporation MCP79 Co-processor [10de:0aa3] (rev b1)
00:04.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa5] (rev b1)
00:04.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1)
00:06.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1)
00:06.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1)
[b]00:08.0 Audio device: nVidia Corporation Unknown device 0ac0 (rev b1)[/b]
00:09.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Bridge [10de:0aab] (rev b1)
00:0a.0 Ethernet controller [0200]: nVidia Corporation MCP79 Ethernet [10de:0ab0] (rev b1)
00:0b.0 SATA controller [0106]: nVidia Corporation MCP79 AHCI Controller [10de:0ab8] (rev b1)
[i]00:0c.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0ac4] (rev b1) -
[/i]00:10.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0aa0] (rev b1)
00:15.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0ac6] (rev b1)
00:16.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1)[i]
00:17.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) -
00:18.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) -[/i]
03:00.0 VGA compatible controller [0300]: nVidia Corporation C79 [GeForce 9300 / nForce 730i] [10de:086c] (rev b1) 
[b]02:00.0 VGA compatible controller: nVidia Corporation Unknown device 0861 (rev b1)[/b]

the italic part are not present in the lspci of an original MacMini3,1 (same chipset); the bold value are different ID or device not listed on my card but used in the MacMini (the ID of the MAcMini are injected via DSDT in my hack)


EDIT: I don't understand why this string:
0a98;Unknown device;10de;Unknown vendor;Memory controller;RAM memory
i've checked and ioreg can see it right

[oldnapalm]

Hi scrax,

the difference from lspci is because System Info gets the device and vendor IDs from IOReg, and if you inject the "device-id" property via DSDT it will show in IOReg instead of the original ID.

About the "0a98;Unknown device;10de;Unknown vendor;Memory controller;RAM memory", looks like the vendor and device IDs are inverted. Can you please run this command and send us the result?

ioreg -l -w 0 | grep -E "(CFBundleIdentifier|device-id|vendor-id|pciclass)"

Thanks.

[scrax]

oldnapalm, on Jun 29 2010, 10:42 PM, said:

Hi scrax,

the difference from lspci is because System Info gets the device and vendor IDs from IOReg, and if you inject the "device-id" property via DSDT it will show in IOReg instead of the original ID.

About the "0a98;Unknown device;10de;Unknown vendor;Memory controller;RAM memory", looks like the vendor and device IDs are inverted. Can you please run this command and send us the result?

ioreg -l -w 0 | grep -E "(CFBundleIdentifier|device-id|vendor-id|pciclass)"

Thanks.

Are you sure? Because the ioregistryexplorer device Ids are not the one i get from system info, but wait, in the ioreg result they are not changed (by DSDT injection)... uhm I'm a bit confused, and so I can't explain well what is happening so i'll attach all my stuff so you can check it by yourself if it could be useful for this project

In the result.txt i've put, the info you asked from ioreg, plus the actual lspci -nn (it shows the original ID not the ones modded by DSDT ones)
 results.txt.zip   18.13K   10 downloads
 scraxZotac.ioreg.zip   378.44K   6 downloads
 Schermata_2010_06_29_a_18.07.47.png   116.14K   102 downloads

Last note, in IORegistryExplorer 980a is not inverted
 Schermata_2010_06_30_a_16.43.37.png   85.33K   107 downloads
DSDT part relative to TRIM:

Device (TRIM) {  Name (_ADR, 0x00030004) }

(yes nothing more )