Jump to content

Klumper

Members
  • Content count

    9
  • Joined

  • Last visited

About Klumper

  • Rank
    InsanelyMac Protégé
  1. Klumper

    6990m QE/CI, but no LVDS; need help with personality

    Thanks, Packo. I'll try that and report back on how it went.
  2. Klumper

    6990m QE/CI, but no LVDS; need help with personality

    Nope. It is recognised, but stays blank. LVDS is the type of connection the internal screen uses. Why 51? According to this bios decoder, it should be 10. I'll try it once I boot Lion back up. I've been using Windows the past few days. BR40793.004 : Clevo P150HM Blackcomb XT Samsung 2GB Subsystem Vendor ID: 1558 Subsystem ID: 5104 Object Header Structure Size: 237 Connector Object Table Offset: 3e Router Object Table Offset: 0 Encoder Object Table Offset: b1 Display Path Table Offset: 12 Connector Object Id [14] which is [LVDS] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [1] which is [DVI_I] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [1] which is [DVI_I] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
  3. Klumper

    6990m QE/CI, but no LVDS; need help with personality

    I'm now using: 02 00 00 00 40 00 00 00 29 05 00 00 10 00 00 05 00 08 00 00 04 02 00 00 00 01 04 00 12 04 01 03 04 00 00 00 14 00 00 00 00 01 00 00 11 02 02 01 00 04 00 00 04 03 00 00 00 01 00 00 21 13 03 02 DVI/HDMI working QE/CI but tearing occurs on both. The LVDS does not work. It is recognized as a 17-inch spdisplays_display. Which is correct, but it stays blank. Using Juncus Framebuffer & AtiPorts = 3 Edit: I've looked at your other post now. I think our best bet is Osmunda. It seems to match quite closely what our cards are. Also where did you get the program that told you what the encoder, etc. was (the one you used before radeon_bios_decode)? Nevermind, I found it on a russian site. Unfortunately, it only confirms that what I had for the LVDS was actually correct so there must be some other issue. Maybe there just isn't any support until new framebuffers come out. Chameleon does not seem to support Osmunda yet though. At least it doesn't appear in the source and I get an error when I set it. ATI6000Controller.kext.zip
  4. Klumper

    6990m QE/CI, but no LVDS; need help with personality

    I forgot to mention, I had that, but the kext I was editing had them out of order and the ports matched the senseids so I thought maybe they had to match for this one. It is still recognized as being the correct port. Since then, I've been working with Fanwort. LVDS is now recognized, but remains blank. av-signal-type is 0x0 if that means anything about the issue. I've been messing with the transmitter and encoder, but so far no luck.
  5. I have DVI fully working, but LVDS is not recognized. I am almost positive that it is assigned to port 0, and the senseid is correct. I've tried changing the control flags, but any changes and none of the graphics work. This also happens when I change the last two entries. This is what I am currently using: 02 00 00 00 00 01 00 00 09 01 00 00 12 04 05 05 <-- LVDS, not recognized 00 04 00 00 00 02 00 00 00 01 00 00 10 00 03 03 <-- HDMI, not working, but it doesn't matter to me 04 00 00 00 14 00 00 00 00 01 00 00 11 02 01 01 <-- DVI, fully working as far as I can tell 00 04 00 00 00 01 00 00 00 01 00 00 21 03 02 02 <-- Not used/not sure what it is 00 04 00 00 00 01 00 00 00 01 00 00 22 05 04 04 <-- Not used/not sure what it is Is there anything I'm doing blatantly wrong? ATOM BIOS Rom: SubsystemVendorID: 0x1558 SubsystemID: 0x5104 IOBaseAddress: 0x0000 Filename: BR40793.004 BIOS Bootup Message: Clevo P150HM Blackcomb XT Samsung 2GB PCI ID: 1002:6720 Connector at index 0 Type [@offset 44696]: LVDS (7) Encoder [@offset 44700]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 44780]: 0x94, OSX senseid: 0x5 Connector at index 1 Type [@offset 44706]: HDMI-A (11) Encoder [@offset 44710]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 44803]: 0x92, OSX senseid: 0x3 Connector at index 2 Type [@offset 44716]: DVI-I (2) Encoder [@offset 44720]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44840]: 0x90, OSX senseid: 0x1 Connector at index 3 Type [@offset 44726]: DVI-I (2) <--- Not actually sure what this is, no other DVI port that I know of Encoder [@offset 44730]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44840]: 0x90, OSX senseid: 0x1 IOService: (Only parts of LVDS & DVI shown) LVDS (I believe) | | | | +-o ATY,Elodea@0 <class AtiFbStub, id 0x1000002ef, registered,$ | | | | | | { | | | | | | "port-number" = 0 | | | | | | "display-type" = "NONE" | | | | | | "connector-type" = 2 | | | | | | "ATY,ActiveFlags" = 1 | | | | | | "IOFBDependentIndex" = 0 | | | | | | "IOFBDependentID" = 18446743524284400384 | | | | | | "ATY,ControlFlags" = 256 | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = 0 | | | | | | "AAPL,iokit-ndrv" = <a06707817fffffff> | | | | | | "AAPL,gray-value" = <c38c6400> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Elodea" | | | | | | "AAPL,boot-display" = <01000000> | | | | | | } DVI (I know) | | | | | | | | | +-o ATY,Elodea@1 <class AtiFbStub, id 0x1000002f0, registered,$ | | | | | | { | | | | | | "display-type" = "LCD" | | | | | | "connector-type" = 4 | | | | | | "ATY,ActiveFlags" = 4 | | | | | | "IOFBDependentIndex" = 1 | | | | | | "IOFBDependentID" = 18446743524284400384 | | | | | | "ATY,ControlFlags" = 20 | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = 2 | | | | | | "AAPL,iokit-ndrv" = <a06707817fffffff> | | | | | | "AAPL,gray-value" = <c38c6400> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Elodea" | | | | | | "port-number" = 2 | | | | | | }
  6. Thanks mykl So... If im trying to update to 10.4.11 I should still use this kernel right?
  7. Yes, the mach_kernel for sse2 is exactly what I need. Yeah that would be great if you can give it to me. By the way how did you update your 10.4.9 to 10.4.11?
  8. Yes I know. Not only does no one have 10.4.8 anymore, but not very many people have Tiger anymore. I know exactly what you mean. I would be glad to make a FTP server and host all kernels and patches etc. on.
  9. I need an 8.9.1 SSE2 kernel to do the update. Unfortunately I cannot find it anywhere online and I was wondering if anyone here had it or knew of a way to get it. Thanks, Landon
×