netkas.org

Archive for the 'Apple' Category

32-bit boot.efi actualy can boot 64-bit kernel

Looks over here – http://forums.macrumors.com/showthread.php?t=1325709. They are patching 32-bit boot.efi to make it loading 64-bit kernel. Obviously such functionality cant be added if it werent present at all. So they just disable the check/lock preventing it. ML on original macpro.

So, greedy Apple, can boot 64-bit kernel on all their macs with 64-bit cpu but decides not to!

Moiuntain Lion Sources released

So, Apple released sources of some components of mountain lion, like xnu kernel.

http://opensource.apple.com/release/mac-os-x-108/

Just for fun, I’ve built 32-bit xnu kernel – http://rghost.ru/39532549

Running openCL on gtx670


more here

long story short – by default opencl doesnt work on gk104 but works on apple’s gk107 from new mbps. Now it works on gk104 (gtx670-gtx690)

Update: obviously ML drivers are much better (still need a patch so)

Enabling OpenCL on 10.7.5/mbp2012 drivers and ML GM

10.7.5/mbp2012 drivers run opencl on Fermi just fine out of box, no more need to enable it binpatching, but..

If you have a card with more than 2 gb of video memory, opencl suddenly gets disabled, wtf?

Here is why: (warning, assembler skills needed for the pic)

basicaly, if your video ram amount > 2GB by at least 1 byte, then you are screwed.

Funny Apple, they decided to control it themselves instead of putting check in the nvidia driver.

But, we can just disable the check and enjoy.

The file you wanna patch is /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL

Just do these two simple patches you can do with any hex editor and you are good to go:

1) for 32-bit part:
find 3d 01 00 00 80 73 e7
replace with 3d 01 00 00 80 90 90

yes, its just last two bytes to disable the check
2) for 64-bit part, for lion
find ff 50 68 48 39 d8 73 e5
replace with ff 50 68 48 39 d8 90 90

for mountain lion
find ff 50 68 4c 39 e0 73 e7
replace with ff 50 68 4c 39 e0 90 90

P.S. doesnt applies to gtx670/gtx680, they have a different problem

MBP2012/10.7.5 nvidia drivers are leaky

The nvidia drivers from mbp2012(and from 10.7.5 beta, they are same) are really leaky one.

For example, yeasterday I had a site with many flash ads openned in opera and bam, kernel (kernel_task, video driver is part of it) eats 690 MB of memory. Normally its around 200mb.

Watching an online video in flash player – 700 mb for kernel_task

Only happens when nvidia card installed, no problem with ati.

Be aware.

11G15 10.7.5 beta update

GPU drivers are exactly same version as in MBP2012’s update pkg.

At least you can use 10.7.5 beta update to get drivers installed the Apple’s way.

Example of ThunderBolt tandem with eGPU

We all was wondering how will apple implement TB on new macpro… well we can continue wondering.

Here is example of possible solution…not

They use lucid virtu mvp i-mode to pass rendered image from external gpu to internal gpu which is connected to TB.

No matter what, it gives performance hit (and lga2011 xeons doesnt have iGPU anyway).

Still interesting video to watch.

MBP 2012 osx news roundup

1) ivy bridge support in kernel
2) geforce gtx6xx drivers, working
3) ati drivers, 69×0 working in macpro
4) intel hd 4000 drivers, not tested
5) usb3 drivers for z77, working

6970 working in Lion

With no patch, msaa works.
All you need is drivers from MBP2012 and three more frameworks from mbp2012:

/System/Library/PrivateFrameworks/GPUSupport.framework
/System/Library/Frameworks/OpenGL.framework
/System/Library/Frameworks/OpenCL.framework

So again, 6970, no coldboot bug, msaa works, itunes doesnt panic, whooooo
smalluxGPU opencl bench causes KP.

Follow the progress here

P.S. you can even get kepler working in Lion same way.

How Retina macbookpro works with screen resolutions

Seems pretty simple
System settings allows you to select 5 screen sizes – 1024 x 640, 1280 x 800, 1440 x 900(default one), 1680 x 1050, 1920 x 1200
Once you select one, it retinezes it (x2 on both dimensions) so you get 2048×1280, 2560×1600, 2880×1800, 3360×2100, 3840×2400

then it upscales (in case of first two) ot downscales(in case of last two) the image to fit 2880×1800.
So blur (in case of upscale) and lost pixels (after downscale) are not that noticable when pixels are small (220 pixel per inch).

« Previous PageNext Page »