Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About Fujilives

  • Rank
    InsanelyMac Protégé
  1. PCEFI v9 Installer

    after using this tool I cannot find my com.apple.boot.plist file. If I mash f8 as its booting I can still get to the partition selection menu, choose the proper partition, and boot. Is there a simple way to fix this? Currently my solution is just to use the XXX distro that has pcefi 9 already, and it works great - but it'd be nice to have a good "post installation method" that worked smoothly.
  2. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    This will probably be my last post on this topic for a long time again. For those of you with other model video cards that use a different internal display connector (i.e. the toshiba 300~ series laptops) you can add your card's id to the kext files and stand a chance at having things work - odds are looking in your favor. However, for the majority of people, the connector inside laptops with these cards seems to not work with megalodon framebuffer. Last night I was up til 5 am (I have to be to work at 8, so I'm @ work right now and tired as hell), with the help of dark, sg, ridgeline, and most importantly Joe (thank you so much for the guidance) I was able to install snow-leopard's newest release to see if the video-drivers would be of any use. You should note that with 0 changes to the kexts, my id (3650 mobility) was in the x2000 kext and it tried to load with no injectors or anything as a result. However, snow kernal panicked with a message about not being able to find something it needed "@0" with the framebuffer it was using - so presumably we have the same problem we have had in 10.5 leapard, where it cant find the proper display to output to. I dont know enough about these things to take this any further, and when I ask questions to the people who I think might know, I feel like I am violating thier space and wasting thier time (I'm pretty sure they feel like that), which I do not want to do. I was going to make a small blog and put a step by step guide and if needed, a video tutorial on how to get QE/CI going from scratch if I could get things to work - but no such luck I will mess with things a bit more and give you guys a zip of (presumably useless) ati files from the newest snow leo before I stop so you can mess with them if you want, but I'd wager the video kexts will not be backwards compatable at all - but it'll at least be something for people to play with.
  3. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    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.
  4. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    np, broken hardware is a more important problem than our dream-world video drivers, osx86 should not brick hardware as far as I know, so hopefully you get your stuff up and running. Now back to the video-card stuff, I was looking around in the 10.5.6 update they said they fixed some issues with monitors scrambling, I look inside the package and I see there was a "displays" folder, and inside that is an "overrides" folder, with what looks like specific monitor overrides like what I tried to add to the natit file. What I am curious about, is the same thing I keep asking over and over (I can't seem to get an answer) - am I doing the overrides right, I am pretty sure I am not and if display overrides have a chance in hell of fixing our problem, I'd like to know the right way to do it before I dismiss it as a possible solution. Anyhow, looking at these overrides in the update, I see this: I cant help but think that maybe I should make a whole displayoverride file seperately, or wonder if IODisplayEDID is the key I need to be using instead of typing in into the natit like I was. At least this makes me think I obtained the edid properly, they look very smilar.
  5. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    ohhhhhhhh I was under the impression you could get in to the bios. Two things. 1) very likely that its just doing a self-test, mine does that and its annoying as hell but meh. Just boot it up and let it sit there for like 5 minutes and see if she goes. 2) if it doesnt go after waiting it out for several minutes, the only other thing I can think of is removing the cmos battery for your bios, startingy your laptop, letting it go through the boot process, turning off your laptop, and putting the cmos battery back in. For the record, the cmos battery is not the same as the laptop battery, cmos battery is usually the size of a watch battery and can usually be removed by taking off a panel on the bottom of the laptop (usually has like one screw, sometimes they put it in by the ram etc). The cmos battery will keep a very small charge applied to your bios so that it can perserve the settings you change when the rest of your computer's power is killed. Starting up withuot a cmos battery will reset the bios to defaults.
  6. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    First off, those kinds of sleep issues are pretty common, lots of people have various solutions to the issue, even regular apple laptops can have similar issues - that might be a trial and error until you find a solution that works for you. Secondly, Working QE/CI in another lappy? Frickin tight, when you DO get it working again post us up some screenshots please ^^/ And finally, what do you mean it freezes at post? Bios post, or are you referring to osx-verbose freeze. If its osx-verbose freeze the solution is just to reinstall osx86. If your problem is freezing at bios post, but you can boot into bios setup options then its not a bios problem. If I had to guess, about the only thing that could cause a bios-level halt on a machine that was just working would be a bad master boot record - or in this case possibly a bad install of chameleon or some other bootloader. When I first installed the xxx version of osx86 10.5.6, I ran into some issues where I couldn't get past boot on the second install, I just changed the boot order to cd first, then put in the xxx cd, used disk-utility, reformatted my disks, and when I installed the next time I choose the other chameleon option on the disk under "additional bootloaders" (the one with dsdt stuff, note: I didnt do any dsdt stuff) and it fixxed my issues and let me see both osx disks on my system and my windows boot partition. Long story short, I'd guess that you have to change the boot order to CD first in the bios so that cd boots first, then use either a windows or osx disk to reformat the drive.
  7. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    I've got osx set up on the lappy, I was able to perserve my workstation, create an osx install on one partition, and create a carbon-copy for fast-repair when stuff breaks on another identical partition - I installed XxX x86 10.5.6 Install Disc Universal Final and just chose the dsdt chameleon so I could choose boot options easily and keep my windows partitio, so I at least have an up to date distro to work with. After several tests I am no better off than I was back in November, I tried a bunch of stuff with the edid for my lcd but saw no noticable differences, but even now I dont know if I am approaching that correctly or with the right expectations, there is still a lot I dont understand. There was one test in particular I did tonight that showed... not neccesarily promise, but different results. With this test it went to scrambled screen like normal, but then it did something odd. It flashed blue, then flashed to show some purple in the middle of the screen (presumably something else distorted) and then went back to a scrambled screen that was 'lighter' - I moved my mouse up to the left corner of the screen and I could sort of see it in the scrambles, I clicked the corner and saw the screen change letting me know the menu dropped down, this is all through massively scrambled stuff, but you could still kind of just "tell" - hit escape and it went back to how it was etc. The computer was functional, it was 'trying' to output to the internal lcd, it just didn't know how to display it to that lcd. No clue where to go from there, if that is any sort of step in the right direction - maybe someone has had similar experiences on other different cards that they were able to resolve with some steps I could tie into this. Anyhow, I'm live with osx86 again and since its not hurting my system any longer, I see no reason to remove it - I will be able to continue testing on and off as new ideas arise, but I cannot be super dedicated to this project, as I am very obsessive about these things, it overwhelms me and I cant stop hammering possible solution after possible solution trying to resolve the issues. Right now, for example, its going on 3 am, and I should have been in bed about 6 hours ago when the GF went to bed - so... yeah, cant keep that up, not healthy. Night all, keep me posted with changes you discover.
  8. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    I might try to install all this stuff again this weekend, god I hate to do this and lose my render station for nothing as I surely will ><
  9. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    For sake of ease I'm changing some naming in natit stuff, so should someone get things loaded with any particular test, I'll be able to tell which ones worked in the system profiler. All of my tests will not include the frameworks that go with them, its too hard for me to throw that stuff together at work with limited time - so for now, for all of these tests, install lastexile's package, and then, before you click restart, install these "test" kexts with the osx aplication 'kexthelper' as it will eliminate permission issues, then restart. 1) --> Lastexile's complied package of my november test 2 <-- 2) --> fuji1 kexts <-- In this test, I added 3400 series and 3670 to the plist, so natit should control your cards now. I know I dont have it listed as M80etc series in the plist, but for the sake of testing I feel this is best right now, since our success with the current ones is the non mobility setup also. There is something extremely screwed up that I did in this test, since someone expressed to us that the edid changes I made may have helped thier internal lcd show up, I decided to remove all the entries that I could see pointing to DVI / LCD displays and change th em -ALL- to LVDS the best I could, I have no idea what I'm doing with that stuff, so its sort of just me scewing around and hoping something works. IDK, lots of screwed up stuff, give it a shot.
  10. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    wait what? This actually let your monitor work even though it was designed for my lcd? Is this supposed to happen? Maybe we need to put your specific edid in there? Am I even doing the EDID thing right? And I really dont know what MVAD is, I just left it there (debated replacing it with the lvds) because I figured whoever put that stuff in there before me is a {censored}load better at this stuff than I am. EDIT: Actually wait, are you even using our Natit file? I know ours doesnt have 3470 - or the 3450 for that matter, listed in the natit file. You'd have to add: <key>0xwhateveryouridis-I'll look it up later</key> <dict> <key>asic</key> <string>RV635</string> <key>entriesToAddKey</key> <string>HD3600</string> <key>name</key> <string>Mobility Radeon HD 3470(test)</string> </dict> but with your ID, in place of where my scribbles are. I have to go scrape off my car and get to work - I'll look into it more there if I get time.
  11. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    I dont know if I did this right, if I had to guess I'd say I did it wrong, this is my first edid entry. I used phonix tool and moninfo and got the same string for both, so I took that string and exported it as hex, then converted from hex to base64 and entered the data into the plist. I am not on a mac right now (well technically I am, but on the windows side of things) but I can give you the relavant information I changed - if you are on a dell studio 17 you should try this and see if it helps - if not, I am too new to this edid thing to know if it stands a chance in hell of helping you - and thats if this is even done right or anything even remotely useful. in the HD3600 key, scroll down to where it says <key>MVAD</key> - starting with that line, replace down to the bottom of that key with the following: <key>MVAD</key> <data> PlyCAP+QAMoAAAAAAAAA AHwukAYwBzAAIAAaBDgE AwAGABoEkAYAAQAAAAAA AAAAAAAAAAAAAAAAAAAA AAAAAA== </data> <key>LVDS,EDID</key> <data> AP///////wBMo0NUAAAA AAASAQOQJRd4Cof1lFdP jCcnUFQAAAABAQEBAQEB AQEBAQEBAQEB2ECANHGw LUAwIDYAb+YQAAAa2ECA NHGwLUAwIDYAb+YQAAAa AAAA/gBKMjc2Q4AxNzBD VAogAAAAAAAAAAAAAAAA AAYBCiAgAMY= </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> Don't know if it will help anyone, but I wanted the information out there in case people needed to use it. The EDID part with information for my internal lcd was: AP///////wBMo0NUAAAA AAASAQOQJRd4Cof1lFdP jCcnUFQAAAABAQEBAQEB AQEBAQEBAQEB2ECANHGw LUAwIDYAb+YQAAAa2ECA NHGwLUAwIDYAb+YQAAAa AAAA/gBKMjc2Q4AxNzBD VAogAAAAAAAAAAAAAAAA AAYBCiAgAMY= The <key>LVDS,EDID</key> I THINK is what is used to tell the framebuffer that its an LCD and that it should use the included EDID data. From reading I see that megalodon doesnt support LVDS so I dont think this will work, but again, I wanted this out there to see if I am on the right track and see if people could benefit from it. Fujilives
  12. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    What laptop does he have? Internal display or DVI/VGA connected display?
  13. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    From another great thread that goes over framebuffers, I see that: @Aidass, or anyone else out there who can please help me out here ^^ Megalodon is a driver that is only built for DVI+VGA - so why does it work with YannickD's internal laptop display? Is the limitation of DVI+VGA overcome somehow? I see your name pop up in the thread I pulled that megalodon information from Aidass, so if there is any chance you could shed some light for me I would appreciate it! I'm downloading some newer distributions and am willing to try some things to get everything going again if I can learn enough to have new things worthy of trying - I will not however, try if I don't have some good things to start from that I have never tried before (I'll be wiping my current render machine to do this if so which will suck). A few things: EDID - I dont really understand the importance of this, how to work with it, or how to implement "new" EDIDs. From what I have read I see they EDID's by definition are "Extended display identification data (EDID) is a data structures provided by a computer display to describe its capabilities to a graphics card". And it looks like if I have windows installed I can pull the EDID from working display via a windows application (it looks like a lot of people use the program 'moninfo'?). I then can somehow take that EDID information from, lets say, Moninfo, export it as text, copy a text-block from it, and paste it into Natit (or other similar injectors) as a key - and it will give OSX and my graphics card instructions on what to do with the monitor and enable its features (backlight etc)? Am I on track here? Natit - Where would I put the EDID information (that I can presumably pull from moninfo on windows) inside Natit to make it function properly, the natit plist I have is huge (the one from test 2 at the start of this thread) and I dont know where it would go. Finally - will any of this even help? Is what I just described above able to 'enable' the internal laptop display, and would it actually allow me to run osx on my laptop display with hardware acceleration? If not what is the point of this all because I think I am completely missing it! Is this a lost cause with the megalodon driver because of our internal display, and somehow YannikD's internal display is hooked up differently and registers as a "regular" dvi/vga monitor and thats why his works? Is there any way we can fake that to OSX if so - or are we forever doomed to non qe/ci in our laptops? Also - I am very much a visual learner, I am a graphic artist and video editor - because these are also the ways I perfer to teach - if there are already visual step-by-steps of these things - please direct me to them ^^
  14. ATI Moblity Radeon HD 3650 on iDeneb 1.3

    While I really dont get how to pull and change EDID stuff (I'm trying to read on it now) - this looks like you've made at least some sort of progress. I decided to take a detour to apple's own support forums and came accross this: "sudo pmset -a lidwake 0" Apple users were having a "black screen" problem where it would do basically the same thing - computer would wake from sleep and hard drives would come on - but the backlight wouldn't kick in - so they were saying they had to do a variety of things - some found this to be the solution. Aparently that forced the "sleep when lid is closed" and "wake when lid is open" feature to "off" (1 instead of 0 turns it back on). They said to test if it worked, they closed the lid, put the computer to sleep, and then opened the display and it should not wake up, then you should have to press a key to wake it up. From what I gather though, its not even detecting as a laptop diaplay, so I doubt it'll fix it for you, just a shot in the dark for you. Others said they had to remove usb mice, then put it to sleep and wake it up - just getting the "mac" problems out of the way first. Also note, Aidass is using the 2400, which is basically a "supported" card more or less, and is not the same as the 3600 mobility, so while I'm glad he's making progress, his problems and solutions will probably not be our problems and solutions - so please don't get confused when we are talking about progress for a 3600 mobility and someone with a completely different card chimes in with success
  15. Your servers fail

    I must admit taking the extra time to put that to video made me laugh.