Jump to content

pacops

Members
  • Content count

    6
  • Joined

  • Last visited

About pacops

  • Rank
    InsanelyMac Protégé
  1. Leopard = Vista?

    My take: Both are good OS's, but each excels in what they were intended for. Vista excels in the corporate environment, and Leopard in the personal environment. I myself prefer OSX for personal use, I am an artist and OSX definitely revolves around this area, to an extent. I do find it more enjoyable for daily tasks too such as surfing etc. Leopard has lots of nice new features, though with it's fair share of bugs. I've actually been using Vista on my Macbook Pro much more often recently because of the WiFi bugs in Leopard, which literally drops the WiFi connection every couple minutes making it close to useless. Really waiting for 10.5.2... On the other hand, I'm the head of IT at my company and Windows (and have moved about 90% of our computers to Vista), without any doubt, is far better suited for this task and probably always will be. Trying to manage 50+ Macs in a business environment would be nothing short of hell. Vista overall seems like a much larger upgrade to me than Leopard, although with many more subtle features compared to Leopard. The largest problem with the move to Vista was familiarity, and a few application hiccups, but for the most part was a reasonably easy experience. I really don't think see it appropriate to compare the two as they are so different, and their focuses lie in different areas. Macs are becoming the luxury market of personal computers. Their OS and computer designs make a point a making sure you know that. With something like a 7 percent market share, my guess is this will slowly increase, but it will eventually cap unless Apple intends to shift their priorities. Apple is a company that is aimed at the consumer market, and very few companies will ever make the switch. I do wish Apple would get on the ball with graphics (graphics cards specifically), as for power machines seemingly intended for heavy graphics and entertainment use they continually fail in this area. Unfortunately I don't see this coming anytime soon =( In the end I really don't prefer either, just use which ever I feel is better for the task I'm doing. I have the luxury with my MBP to use both, and I love it.
  2. AppleHDA Solution - Work in progress

    Tried with new patcher says it's unsupported, but here's my dump anyways. Willing to help out in any way I can. -ALC0262 ALC0262.txt
  3. Annoying designs

    Flash sites done poorly, take forever to load and have a slow framerate = ugly flash. Unfortunately, lots of even professional sites do this. I love it when they're quick and smooth.
  4. Getting Laptop Internal LCD to work...

    Well I was able to finally get full resolution w/ MacVidia 1.07 beta drivers(newer versions just resulted in extreme artifacts), although I don't have QE/CI it's much better than a black screen or color banding. I also was able to get AppleBacklightDisplay to register using IOGraphicsFamily from np_'s totest.zip on the laptop display forum, more current versions wouldn't work. I also had to add IODisplayEDID w/ my EDID to the AppleBacklightDisplay dictionary in iographicsfamily for osx to recognize my display config created with np_'s utility. This is progress I guess, or at the least a temp solution... I also attached my ioreg for any curious. LaptopDisplay still seems to do nothing when loaded, and AppleBacklight.kext still doesn't register, tried various versions of it 10.4.5-.9 tosioreg.txt
  5. Getting Laptop Internal LCD to work...

    Here is an IOReg from a Macbook. AppleBacklight.kext kicks in before the graphics drivers, stating that there is a backlight on the display. There are also the entries "AppleBacklightDisplay=1 and AppleDisplay=0" in the IOKitDiagnostics. If there was some way to inject or force AppleBacklightDisplay to be detected on the laptop it could make the backlight work, and force AppleBacklightDisplay to be detected, maybe a method similar to the way Natit works. Before the backlight kext kicks in there is also another entry, PNLF which seems to trigger the backlight kext. +-o PNLF <class IOACPIPlatformDevice, registered, matched, active, busy 0, retain count 7> | | | { | | | "ApplePanelRawBrightness" = 296 | | | "ApplePanelRawTable" = <00003e003e003e003e003e003e003e003e003e004000420044004600480048004a004c004e005 0052005400560058005a005a005c005e00600062006400660068006a006c006c006e007000720074 0760078007a007c007e007e00800082008400860088008a008c008e0090009000920094009600980 9a009c009e00a000a200a200a400a600a800aa00ac00ae00b000b200b400b400b600b800ba00bc00 e00c000c200c400c600c600c800ca00cc00ce00d000d200d400d600d800d800da00dc00de00e000e 00e400e600e800ea00ea00ec00ee00f000f200f400f600f800fa00fc00fc00fe0000010201040106 108010c01100114011a011e0122012801> | | | "compatible" = <"backlight"> | | | "name" = <"APP0002"> | | | "_STA" = 15 | | | "_UID" = "10" | | | } | | | | | +-o AppleIntelPanelA <class AppleIntelPanelA, !registered, !matched, active, busy 0, retain count 5> | | { | | "IODisplayParameters" = {"brightness"={"min"=0,"max"=128},"commit"={"reg"=0}} | | "CFBundleIdentifier" = "com.apple.driver.AppleBacklight" | | "IOClass" = "AppleIntelPanelA" | | "IONameMatched" = "backlight" | | "IOProbeScore" = 2000 | | "ApplePanels" = {"F10P9c57"=<0000003500e200ff>,"F10P9c58"=<0046004600d700ff>,"F10P9c5f"=<0000003e01070128>,"F10P9c5a"=<004c004c00cc00ff>,"F10P9c59"=<004c004c00cc00ff>,"F10P9c5b"=<0000003e01070128>,"F10P9c60"=<0000003500e200ff>,"F10P9c5c"=<0000003e01070128>,"F10P9c61"=<0000003700e700ff>,"Default"=<000007400af7fffe>,"F10P9c56"=<0000003500e200ff>,"F10P9c5d"=<0000003e01070128>,"F10P9c62"=<0000003700e700ff>,"F10P9c5e"=<0000003e01070128>} | | "IOMatchCategory" = "IODisplayParameters" | | "IONameMatch" = "backlight" | | "IOProviderClass" = "IOACPIPlatformDevice" If anyone has any suggestions or ideas, I'm all ears. Thanks And unfortunately, Apple won't release the source to AppleACPIPlatform, which would make this much easier . mb_ioreg.txt
  6. Obviously there is LaptopDisplay, but the development on that seems to have stopped and no resolution for those who have Internal LCDs has come about. Now there are many people who have the internal lcd on their laptop working, but it seem those whose have internal lcds which don't register their EDID information correctly with osx are the ones having the problems. I can get my external display working fine with QE/CI, but as this is a laptop, that just isn't useful. OSX doesn't see the display, nor create a display override for it hence the need for something like LaptopDisplay and it's utility, but these still don't configure osx to see the overrides for many people. You can inject the values DisplayVendorID and DisplayProductID into IOGraphicsFamily's plist directly, but this still doesn't resolve the issue, only forces the display connected to use the settings in the override file. Maybe somehow forcing osx to detect the display as an apple "AppleBacklightDisplay" could fix the issue, what np_ first set out to do, but I haven't figured out how to do this correctly. There are many values which help configure the display seen under /System/Library/Frameworks/IOKit/Headers/graphics/IODisplayTypes.h, but none of these seem to help in the override file. One thing I've tryed is setting the following keys under Natit: [size=2] <key>@0,AAPL,boot-display</key> <integer>1</integer> <key>@0,DisplayProductID</key> <integer>20619</integer> <key>@0,DisplayVendorID</key> <integer>20979</integer> <key>@0,NVDA,EFIDisplay</key> <string>LVDS</string> <key>@0,compatible</key> <string>NVDA,NVMac</string> <key>@0,device_type</key> <string>display</string> <key>@0,display-dither-support</key> <integer>1</integer> <key>@0,display-link-component-bits</key> <integer>6</integer> <key>@0,display-type</key> <string>LCD</string> <key>@0,fboffset</key> <integer>131072</integer> <key>@0,inverter-current</key> <integer>1</integer> <key>@0,name</key> <string>NVDA,Display-A</string> <key>@1,AAPL,boot-display</key> <integer>0</integer> <key>@1,NVDA,EFIDisplay</key> <string>DFP1</string> <key>@1,compatible</key> <string>NVDA,NVMac</string> <key>@1,device_type</key> <string>display</string> <key>@1,display-dither-support</key> <integer>0</integer> <key>@1,display-link-component-bits</key> <integer>6</integer> <key>@1,inverter-current</key> <integer>1</integer> <key>@1,name</key> <string>NVDA,Display-B</string> <key>AAPL,backlight-control</key> <integer>1</integer> <key>AAPL00,Coherency</key> <integer>2</integer> <key>DFP1,EDID</key> <data> AP///////wBR84tQAAAAAA4QAQOAHhN4yq/kq1Q1tSMU T1EjCACVAAEBAQEBAQEBAQEBAQEBqiWgQFGEDDBAIDMA L74QAAAYAAAA/QA7PTY4CgAKICAgICAgAAAA/ABJbnRl cm5hbCBMQ0QKAAAA/gBUT1NISUJBCiAgICAgAKo= </data> <key>LVDS,EDID</key> <data> AP///////wBR84tQAAAAAA4QAQOAHhN4yq/kq1Q1tSMU T1EjCACVAAEBAQEBAQEBAQEBAQEBqiWgQFGEDDBAIDMA L74QAAAYAAAA/QA7PTY4CgAKICAgICAgAAAA/ABJbnRl cm5hbCBMQ0QKAAAA/gBUT1NISUJBCiAgICAgAKo= </data> <key>NVCAP</key> <data> BAABAAAAAwAMAAAAAAAACgAAAAA= </data> <key>NVDA,DeviceID</key> <integer>20619</integer> <key>NVDA,EFIVersion</key> <string>1.3</string> <key>NVDA,VendorID</key> <integer>20979</integer> <key>device_type</key> <string>NVDA,Parent</string> [/size] This seems to get closer, but I still get color banding, and some of these strings just might be incorrect. If natit is loaded with these strings and nvdaresman isnt present, the system halts at the application login window, without the additional strings and nvdaresman the system boots, obviously without res change ect. As soon as nvdaresman is loaded, the colorbanding starts. I've also tried playing with IOProbeScore values under IOGraphicsFamily in an attempt to get it to detect the display as an AppleBacklightDisplay, but nothing seems to help. The problem seems to lie with IOGraphicsFamily, IONDRVSupport, or NVDAResman, but I could be wrong. Probley takes some editing of the source, than just entering values into the .plist files. If anyone has had any success getting their internal lcd to work, please post what you did and or your ioreg. Any help would be greatly appreciated, Thanks System: Toshiba Tecra M7 Intel Core Duo 2.4 Ghz 2GB DDR2 667 Quadro NVS 110M
×