Jump to content
Sign_90

ATI Moblity Radeon HD 3650 on iDeneb 1.3

453 posts in this topic

Recommended Posts

Hi All,

 

I've been lurking/reading this forum for a while waiting for a driver for the ATI Mobility Radeon 3650

I own a Sony FW21J with a 256Mb 3650M. (and also the Intel 5100 WLAN)

 

There are numerous files on this thread, which ones should I try first??

 

Which install disc should I use? XxX, iPC, IDeneb, etc...

 

Is there a HOWTO somewhere to guide me through the the installation???

 

I'm fairly Linux, Unix savvy.

 

HELP :thumbsup_anim:

Share this post


Link to post
Share on other sites
Advertisement

Well I gave up and just brought the lappie to a local private computer store/service thingie. Guy said he'd take a look and I can come back tomorrow evening. Even though I have warranty on the laptop, I think this may be a faster solution. Thanks for the help and advice, will report back asap.

Share this post


Link to post
Share on other sites
Hi All,

 

I've been lurking/reading this forum for a while waiting for a driver for the ATI Mobility Radeon 3650

I own a Sony FW21J with a 256Mb 3650M. (and also the Intel 5100 WLAN)

 

There are numerous files on this thread, which ones should I try first??

 

Which install disc should I use? XxX, iPC, IDeneb, etc...

 

Is there a HOWTO somewhere to guide me through the the installation???

 

I'm fairly Linux, Unix savvy.

 

HELP :)

install any one that is version 10.5.6. after that install the radeon hd drivers then without reinstalling install the kexts that yannick posted.

Share this post


Link to post
Share on other sites
i have the same problem like Samjung, the laptop freeze.

 

So..That means its most likely not harware failure..

 

 

i've a toshiba a300, and i tried to install the "test 1" (package): nothing. With the kexts, i have a strange screen (black and white). :'(

 

 

From a clean install, delete all ati related kexts in system\library\extesions (using osxtools to set permission), then use kexthelper to install YannickD's kexts, reboot. Should work, worked with mine.

quote]

Share this post


Link to post
Share on other sites
Hi,

What happens if you press fn/f8 (or your laptop equivalent) to switch display ?

thx

 

Once booted, it does not do anything at all (Fn-F4 in my case).

Share this post


Link to post
Share on other sites

I would guess that your laptop freeze problems are related to Hibernate mod. I would try and clear the cmos and the memory if at all possible I was told that if you remove the battery during boot it may help with the bios but I am not sure I would recommend it. Samjung please let us know what happens

I am very curious also were you guys running any kinda speedstep or powere manager and how long was the computer running?

Share this post


Link to post
Share on other sites
From a clean install, delete all ati related kexts in system\library\extesions (using osxtools to set permission), then use kexthelper to install YannickD's kexts, reboot. Should work, worked with mine.

quote]

 

I've still a strange screen. ;) i've ideneb 1.4 but on the 1.3 version with the 10.5.6 update i had the same problem.

 

:D

Share this post


Link to post
Share on other sites

have any of you been able to change your graphics resolution via <key>Graphics Mode</key>

<string>1280x800x32</string> ? ive been trying for a while but cant get it to work. if you have gotten it to work, on what kexts?

Share this post


Link to post
Share on other sites

Hi,

 

Actually , for ATI HD Mobility Radeon 2600 , any progess ? ,i have see a kext about this card in 10.5.6 and 10.6,but this working on hackintosh ?

Share this post


Link to post
Share on other sites
have any of you been able to change your graphics resolution via <key>Graphics Mode</key>

<string>1280x800x32</string> ? ive been trying for a while but cant get it to work. if you have gotten it to work, on what kexts?

Okay short answer for you on why this does not work..... If you are on a laptop, and your max resolution under windows is 1280x800 which I am guessing it is based on the above statement then you are stuck at 1024x768 this will not change res until we get a driver done. Those of you who upgraded your LCD at purchase can have some res change but it will still not be 100%

 

P.S. By upgraded LCD I mean in windows you can change to something like 1440 x900 or whatever it is

Share this post


Link to post
Share on other sites

I am using Sony VAIO Fw390 with ATI HD 3650 with Device ID 9591 also. I have try a couple kext listed, and the test one from YakknicD, but still got a blue and black screen.

 

What I try is using OSXTools, and enable GL, and using this line

 

4.) Edit the file

 

/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

 

and make these changes:

 

<key>Kernel Flags</key>

<string>"Graphics Mode"=1920x1200x32</string>

 

5.) Reboot

 

And I got resolution in MAC showing 1500x1040 (something like that)...

 

Waiting for the true Quart and Mirror support to 1920x1080 resolution..

Share this post


Link to post
Share on other sites

update 02-10-09

 

I tried some things last night, no luck, super confused now.

 

I tried to isolate they key difference between the "freeze" at spinning circle on apple boot, and the "corrupted screen" that allows us to still move our mouse (you can see it through the corruption a bit). For the most part it seems randomish. If any of you have tests that produced the "broken-image" sort of corruption where you can still see interation through the corruption with your mouse etc, please zip those up and feed them my way.

 

Anyhow, the peculiar thing about last night is, the simple test of installing lastexiles package and then dumping the final files of YannickD (same files but for the sake of exact replication I'm doing this) with kexthelper and restarting, produces the jagged "I want to work!" screen. But when using those exact same files but adding in the EDID for my LCD (using @0,EDID and @1,EDID) it freezes at the apple with spinning circle. This confuses the hell out out of me since this means that with the EDID being right it freezes and breaks it, but the EDID not being in there at all keeps it working in jagged-mode. This makes me think that its still possible the solution is an EDID related one, I cant imagine another reason why adding the EDID would change it from jagged-corruption with mouse, to nothing at all and frozen circle on apple screen. Before I would have said "well it could be the framebuffer" but the framebuffer obviously frickin' works, as it's working for other people, and it obviously wants to output to our screens or we wouldn't get jagged-{censored} with a working mouse (it means the framebuffer is loaded into memory and that natit is working to control it - and people wouldn't get working qe/ci on their external monitors either, if it was an x2000 problem - everything works, except our internal lcds - so how do we fix that?).

 

The only other problem I can imagine is something in the natit that we need to "steer" int he right direction - some detail in here that I dont understand (there are many of those, haha) - something someone with more experience may be able to tell me. Which brings me to...

 

I want to do a breakdown here, I'll need some help.

 

<key>HD3600</key>
					<dict>
						<key>@0,AAPL,boot-display</key>
						<data>
						AQAAAA==
						</data>
						<key>@0,ATY,EFIDisplay</key>
						<string>TMDSA</string>
						<key>@0,VRAM,memsize</key>
						<data>
						AAAAEAAAABA=
						</data>
						<key>@0,compatible</key>
						<string>ATY,Megalodon</string>
						<key>@0,connector-type</key>
						<data>
						BAAAAA==
						</data>
						<key>@0,device_type</key>
						<string>display</string>
						<key>@0,display-connect-flags</key>
						<data>
						AAAEAA==
						</data>
						<key>@0,display-type</key>
						<string>LCD</string>
						<key>@0,name</key>
						<string>ATY,Megalodon</string>
						<key>@1,VRAM,memsize</key>
						<data>
						AAAAAAAAABA=
						</data>
						<key>@1,compatible</key>
						<string>ATY,Megalodon</string>
						<key>@1,connector-type</key>
						<data>
						AAIAAA==
						</data>
						<key>@1,device_type</key>
						<string>display</string>
						<key>@1,display-type</key>
						<string>NONE</string>
						<key>@1,name</key>
						<string>ATY,Megalodon</string>
						<key>AAPL,EMC-Display-List</key>
						<data>
						AwAAAAAAAAAAAAAAAAAA
						AAYQAAAbkgAAAAAAAAAA
						AAAGEAAAHJIAAAAAAAAA
						AAAABhAAACGSAAAAAAAA
						AAAAAA==
						</data>
						<key>AAPL,aux-power-connected</key>
						<data>
						AQAAAA==
						</data>
						<key>AAPL,backlight-control</key>
						<data>
						AAAAAA==
						</data>
						<key>AAPL00,blackscreen-preferences</key>
						<data>
						AAAACA==
						</data>
						<key>AAPL01,Coherency</key>
						<data>
						AgAAAA==
						</data>
						<key>AAPL01,blackscreen-preferences</key>
						<data>
						AAAACA==
						</data>
						<key>ATY,Card#</key>
						<string>109-B148xx-00</string>
						<key>ATY,Copyright</key>
						<string>Copyright AMD Inc. All Rights Reserved. 2005-2008</string>
						<key>ATY,EFICompileDate</key>
						<string>Dec 18 2007</string>
						<key>ATY,EFIDriverType</key>
						<data>
						Ag==
						</data>
						<key>ATY,EFIEnabledMode</key>
						<data>
						Ag==
						</data>
						<key>ATY,EFIHWInitStatus</key>
						<data>
						AAAAAAAAAAA=
						</data>
						<key>ATY,EFIOrientation</key>
						<data>
						AQ==
						</data>
						<key>ATY,EFIVersion</key>
						<data>
						MDEuMDAuMjM2AA==
						</data>
						<key>ATY,EFIVersionBios</key>
						<string>113-B14801-023</string>
						<key>ATY,FrameBufferOffset</key>
						<data>
						AAAAAIAAAAA=
						</data>
						<key>ATY,HWGPIO</key>
						<data>
						I6hIAA==
						</data>
						<key>ATY,IOSpaceOffset</key>
						<data>
						AAAAAAAAIAA=
						</data>
						<key>ATY,MCLK</key>
						<data>
						ADUMAA==
						</data>
						<key>ATY,MRT</key>
						<string></string>
						<key>ATY,MemRevisionID</key>
						<data>
						AQA=
						</data>
						<key>ATY,MemVendorID</key>
						<data>
						BgA=
						</data>
						<key>ATY,PCIConfigSpace</key>
						<data>
						AhCIlQcAEAAAAAADQAAA
						AAwAAIAAAAAABACikAAA
						AAABIAAAAAAAAAAAAABr
						EKYAAACgkFAAAAAAAAAA
						AAEAAAAAAAAAAAAAAAAA
						AGsQpgABWAMGAAAAABCg
						EQCgjwAAEAgAAAINAAhC
						AAIRAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAIAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAUAgAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AA==
						</data>
						<key>ATY,PlatformInfo</key>
						<data>
						AQAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAA=
						</data>
						<key>ATY,RefCLK</key>
						<data>
						jAoAAA==
						</data>
						<key>ATY,RegisterSpaceOffset</key>
						<data>
						AAAAAJCiAAA=
						</data>
						<key>ATY,Rom#</key>
						<string>113-B1480A-236</string>
						<key>ATY,SCLK</key>
						<data>
						YK4KAA==
						</data>
						<key>ATY,VendorID</key>
						<data>
						AhA=
						</data>
						<key>MVAD</key>
						<data>
						PlyCAP+QAMoAAAAAAAAA
						AHwukAYwBzAAIAAaBDgE
						AwAGABoEkAYAAQAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAA==
						</data>
						<key>device_type</key>
						<string>ATY,MegalodonParent</string>
						<key>model</key>
						<string>ATI Radeon HD 3600</string>
						<key>name</key>
						<string>ATY,MegalodonParent</string>
</dict>

 

Break it down with me. First off, in the <data> blocks, what is contained in them and can we change it?

 

For example:

<key>ATY,MemVendorID</key>

<data>

BgA=

<data>

 

and:

<key>@0,VRAM,memsize</key>

<data>

AAAAEAAAABA=

</data>

 

and:

<key>@1,VRAM,memsize</key>

<data>

AAAAAAAAABA=

</data>

 

I have 256 megs of ram on my card - I noticed these other people have 512 - Do these keys tell osx how much ram a card has? Why is the "vram,memsize" data different for @0 and @1? There are so many strings I dont understand with the above plist, wouldn't all of the above data need to be cusomized for whatever card we have?

 

If someone could do a breakdown of the plist entries above, as best they can, it might help us shape this better.

Share this post


Link to post
Share on other sites

Fuji, i think you might get a better response in the natit forum, lets hope for the best and thanks for continuing your work. let me know if you want me to try something. i also have a 3650 with 256mb ram.

Share this post


Link to post
Share on other sites

ok i just reinstalled the lastexile package, then installed the yannickd kexts, then repaired permissions. got the screen distortion for the first time. when i moved the mouse the distortion did respond. also, i have a resolution switch on this laptop and when i pressed that the screen went to 1024x768 mode (made the screen not streched out and had bars on the side) which makes me think that the drives don't enable acceleration. i also connected the laptop to my external monitor and got the same distortion. ill post pictures of this soon.

Share this post


Link to post
Share on other sites
Good thought Fujilives.

Samjung, did you find out what is wrong with you laptop yet?

Hy!

I find it! It's Hdd.Must be formatet.When i remove hdd, i can acces the bios. I try to delete with Disk utily, but dont work when i put in laptop. Now i delete Hdd with security option -Zero out data, all. I'll back soon with new test for Ati Hd mobility 3470 :(

Share this post


Link to post
Share on other sites

Well I just picked up my laptop again. It was indeed the HDD. I still have all my files and both osx en win7 install. All the guy did was remove my HDD, boot up and he was able to get into the BIOS. Set everything to default and it was good to go :) So in the future everyone know what to do :D

 

@Fuji: What screenshots would you want? My hackintosh is unable to connect to internet (have intel wifi=not working) but perhaps I can upload them from my desktop. Anyway, I still don't have my sound working (worked with Ideneb 1.3), but I still have full res and qe/ql.

Share this post


Link to post
Share on other sites
Well I just picked up my laptop again. It was indeed the HDD. I still have all my files and both osx en win7 install. All the guy did was remove my HDD, boot up and he was able to get into the BIOS. Set everything to default and it was good to go :) So in the future everyone know what to do :D

 

@Fuji: What screenshots would you want? My hackintosh is unable to connect to internet (have intel wifi=not working) but perhaps I can upload them from my desktop. Anyway, I still don't have my sound working (worked with Ideneb 1.3), but I still have full res and qe/ql.

 

Great news! That really is ... I'd someone to have a 'big' issue with their laptop trying to get these frickin' difficult drivers to work :) Seems like these mobility cards are perhaps the most difficult.

 

I wonder if there is someone that can help Fujilives with his request for more info ..... I know I don't have the knowledge, although I'm happy to do as much testing as might be useful.

 

@chopped: I liked the suggestion of trying the natit posts.

 

Keep up the good work guys. I know I"m grateful for your time.

Share this post


Link to post
Share on other sites

Ok this is totally oftopic but I have question for everybody: I want to use wifi on my hackintosh. Right now I have a builtin wifi card from intel (4965). But honestly, I don't want remove that card (the work, warranty --> laptop is from september, have 2 years)but I do have a Cardexpress slot. I know there are wifi cards in this form, does anybody happen to know one which will work? I think I've read something about the Belkin N-1 or something, but those are quiet expensive..

Share this post


Link to post
Share on other sites
my laptop is a :

 

Packard Bell Easynote (EasyNote_ST85-M-018FR ---> FR is french)

ATI Radeon HDMI @ ATI RV635

ATI Mobility Radeon HD 3650 (512 Mo)

ATI Mobility Radeon HD 3650 (M86)

 

Intel® Core™2 Duo CPU T5800 @ 2.00GHz

 

 

" I just tried with a hdmi cable, my screen of my laptop computer is blue "

Share this post


Link to post
Share on other sites
update 02-10-09

 

I tried some things last night, no luck, super confused now.

 

I tried to isolate they key difference between the "freeze" at spinning circle on apple boot, and the "corrupted screen" that allows us to still move our mouse (you can see it through the corruption a bit). For the most part it seems randomish. If any of you have tests that produced the "broken-image" sort of corruption where you can still see interation through the corruption with your mouse etc, please zip those up and feed them my way.

 

Anyhow, the peculiar thing about last night is, the simple test of installing lastexiles package and then dumping the final files of YannickD (same files but for the sake of exact replication I'm doing this) with kexthelper and restarting, produces the jagged "I want to work!" screen. But when using those exact same files but adding in the EDID for my LCD (using @0,EDID and @1,EDID) it freezes at the apple with spinning circle. This confuses the hell out out of me since this means that with the EDID being right it freezes and breaks it, but the EDID not being in there at all keeps it working in jagged-mode. This makes me think that its still possible the solution is an EDID related one, I cant imagine another reason why adding the EDID would change it from jagged-corruption with mouse, to nothing at all and frozen circle on apple screen. Before I would have said "well it could be the framebuffer" but the framebuffer obviously frickin' works, as it's working for other people, and it obviously wants to output to our screens or we wouldn't get jagged-{censored} with a working mouse (it means the framebuffer is loaded into memory and that natit is working to control it - and people wouldn't get working qe/ci on their external monitors either, if it was an x2000 problem - everything works, except our internal lcds - so how do we fix that?).

 

The only other problem I can imagine is something in the natit that we need to "steer" int he right direction - some detail in here that I dont understand (there are many of those, haha) - something someone with more experience may be able to tell me. Which brings me to...

 

I want to do a breakdown here, I'll need some help.

 

<key>HD3600</key>
					<dict>
						<key>@0,AAPL,boot-display</key>
						<data>
						AQAAAA==
						</data>
						<key>@0,ATY,EFIDisplay</key>
						<string>TMDSA</string>
						<key>@0,VRAM,memsize</key>
						<data>
						AAAAEAAAABA=
						</data>
						<key>@0,compatible</key>
						<string>ATY,Megalodon</string>
						<key>@0,connector-type</key>
						<data>
						BAAAAA==
						</data>
						<key>@0,device_type</key>
						<string>display</string>
						<key>@0,display-connect-flags</key>
						<data>
						AAAEAA==
						</data>
						<key>@0,display-type</key>
						<string>LCD</string>
						<key>@0,name</key>
						<string>ATY,Megalodon</string>
						<key>@1,VRAM,memsize</key>
						<data>
						AAAAAAAAABA=
						</data>
						<key>@1,compatible</key>
						<string>ATY,Megalodon</string>
						<key>@1,connector-type</key>
						<data>
						AAIAAA==
						</data>
						<key>@1,device_type</key>
						<string>display</string>
						<key>@1,display-type</key>
						<string>NONE</string>
						<key>@1,name</key>
						<string>ATY,Megalodon</string>
						<key>AAPL,EMC-Display-List</key>
						<data>
						AwAAAAAAAAAAAAAAAAAA
						AAYQAAAbkgAAAAAAAAAA
						AAAGEAAAHJIAAAAAAAAA
						AAAABhAAACGSAAAAAAAA
						AAAAAA==
						</data>
						<key>AAPL,aux-power-connected</key>
						<data>
						AQAAAA==
						</data>
						<key>AAPL,backlight-control</key>
						<data>
						AAAAAA==
						</data>
						<key>AAPL00,blackscreen-preferences</key>
						<data>
						AAAACA==
						</data>
						<key>AAPL01,Coherency</key>
						<data>
						AgAAAA==
						</data>
						<key>AAPL01,blackscreen-preferences</key>
						<data>
						AAAACA==
						</data>
						<key>ATY,Card#</key>
						<string>109-B148xx-00</string>
						<key>ATY,Copyright</key>
						<string>Copyright AMD Inc. All Rights Reserved. 2005-2008</string>
						<key>ATY,EFICompileDate</key>
						<string>Dec 18 2007</string>
						<key>ATY,EFIDriverType</key>
						<data>
						Ag==
						</data>
						<key>ATY,EFIEnabledMode</key>
						<data>
						Ag==
						</data>
						<key>ATY,EFIHWInitStatus</key>
						<data>
						AAAAAAAAAAA=
						</data>
						<key>ATY,EFIOrientation</key>
						<data>
						AQ==
						</data>
						<key>ATY,EFIVersion</key>
						<data>
						MDEuMDAuMjM2AA==
						</data>
						<key>ATY,EFIVersionBios</key>
						<string>113-B14801-023</string>
						<key>ATY,FrameBufferOffset</key>
						<data>
						AAAAAIAAAAA=
						</data>
						<key>ATY,HWGPIO</key>
						<data>
						I6hIAA==
						</data>
						<key>ATY,IOSpaceOffset</key>
						<data>
						AAAAAAAAIAA=
						</data>
						<key>ATY,MCLK</key>
						<data>
						ADUMAA==
						</data>
						<key>ATY,MRT</key>
						<string></string>
						<key>ATY,MemRevisionID</key>
						<data>
						AQA=
						</data>
						<key>ATY,MemVendorID</key>
						<data>
						BgA=
						</data>
						<key>ATY,PCIConfigSpace</key>
						<data>
						AhCIlQcAEAAAAAADQAAA
						AAwAAIAAAAAABACikAAA
						AAABIAAAAAAAAAAAAABr
						EKYAAACgkFAAAAAAAAAA
						AAEAAAAAAAAAAAAAAAAA
						AGsQpgABWAMGAAAAABCg
						EQCgjwAAEAgAAAINAAhC
						AAIRAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAIAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAUAgAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AA==
						</data>
						<key>ATY,PlatformInfo</key>
						<data>
						AQAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAAAAAAA=
						</data>
						<key>ATY,RefCLK</key>
						<data>
						jAoAAA==
						</data>
						<key>ATY,RegisterSpaceOffset</key>
						<data>
						AAAAAJCiAAA=
						</data>
						<key>ATY,Rom#</key>
						<string>113-B1480A-236</string>
						<key>ATY,SCLK</key>
						<data>
						YK4KAA==
						</data>
						<key>ATY,VendorID</key>
						<data>
						AhA=
						</data>
						<key>MVAD</key>
						<data>
						PlyCAP+QAMoAAAAAAAAA
						AHwukAYwBzAAIAAaBDgE
						AwAGABoEkAYAAQAAAAAA
						AAAAAAAAAAAAAAAAAAAA
						AAAAAA==
						</data>
						<key>device_type</key>
						<string>ATY,MegalodonParent</string>
						<key>model</key>
						<string>ATI Radeon HD 3600</string>
						<key>name</key>
						<string>ATY,MegalodonParent</string>
</dict>

 

Break it down with me. First off, in the <data> blocks, what is contained in them and can we change it?

 

For example:

<key>ATY,MemVendorID</key>

<data>

BgA=

<data>

 

and:

<key>@0,VRAM,memsize</key>

<data>

AAAAEAAAABA=

</data>

 

and:

<key>@1,VRAM,memsize</key>

<data>

AAAAAAAAABA=

</data>

 

I have 256 megs of ram on my card - I noticed these other people have 512 - Do these keys tell osx how much ram a card has? Why is the "vram,memsize" data different for @0 and @1? There are so many strings I dont understand with the above plist, wouldn't all of the above data need to be cusomized for whatever card we have?

 

If someone could do a breakdown of the plist entries above, as best they can, it might help us shape this better.

 

use plist editor pro, and you will able to see values correctly. about vram size, in plist editor 0...08 means 128, 0...10 256 and 0...20 means 512 all these values should be written twice (0...08 0...08)

 

Ok this is totally oftopic but I have question for everybody: I want to use wifi on my hackintosh. Right now I have a builtin wifi card from intel (4965). But honestly, I don't want remove that card (the work, warranty --> laptop is from september, have 2 years)but I do have a Cardexpress slot. I know there are wifi cards in this form, does anybody happen to know one which will work? I think I've read something about the Belkin N-1 or something, but those are quiet expensive..

You can buy any usb wifi stick from ebay or other shop

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×