Macbook 2.2 & BenQ G2400w

I've recently bought two BenQ G2400W (DVI-HDMI 1900 x 1200 )monitors for use with two different Macbooks 2.2 (Santa Rosa chipset & Leopard).
The problem is this; Whilst I can get the monitors to work over the analogue connection it is impossible to get an image via the DVI or HDMI connectors.I have tried to use four different Mini DVI to DVI connectors as well as DVI cables. The Macbooks have no problem working via the DVI with some Formac displays I also have.
Can anyone help? Thanking you in advance for your time.

I have the same issue, "no signal detected" when using dvi or hdmi. The macbook (2,2 SR) detects g2400w properly only when it's connected to the monitor via dvi and the monitor is set to hdmi in, or vice versa. When I change to dvi in, macbook instantly drops the monitor, and "no signal detected" is displayed on the external monitor. No matter what resolution i choose.
I'm pretty sure it's an issue somehow related to EDID-signal sent by the monitor. And what is strange, there's one way I manage to get anything displayed on the monitor: first i shut down the computer, then plug it to the monitor with dvi, set the monitor to hdmi in, start the mac and close instantly the lid, and then change the monitor settings to dvi in. This way i can see the white startup screen with the gray apple displayed in the middle, which, however, disappears just before the logon screen and "no signal detected", again.
The strangest thing about this is that i somehow managed to get it work ONCE, when testing several times different versions of the routine i described above. I could get it working just as it should, log on and tested hd trailers and such but since the next time i turned the monitor off, it has been as dead as before. Any suggestions???

Similar Messages

  • Cs4PSD InDesign Epson SP1400/PM-G4500 Benq G2400w Colorsync Huey

    Situation: printing a 30pg book from indesign onto my Epson printer.
    Problem: colors are do not match screen, while printing from Ps and Id
    Possible reasons:
    1. non-postscript printer
    2. monitor uncalibrated
    3. settings in colorsync
    4. settings in psd
    5. huey is not insufficient as a monitor calibrator. need another color management hardware: screen-to-papaer matching, thingy???
    6. maybe i need to create new profiles: monitor profile, paper profile
    What i know/ What I have been told/ What I've already performed:
    printing from epson desktop printer:
    1. keep images at RGB
    2. save as eps8bit-but this is for outsourcing to a printer company
    3. if all else fails, when colors don't match, print in illustrator or acrobat
    4. printer head and alignment has been performed numerous times
    5. ink has been changed every 2 -weeks
    6. settings in psd:
    Adobe RGB (1998)
    U.S. Web Coated (SWOP) v2
    7. test printed on epson super fine paper in CS4 PSD
    "document: Epson sRGB" also "document: Adobe RGB (1998)"
    "photoshop determine color"
    "SP 1400 1410 PQIJ"
    Results:  prints still look bad
    What i don't know:
    1. i'm guessing this printer isn't post-script, does it need to be in order to match what i see on screen and on paper
    2. how to create new profiles, do i need to???
    3. CS4 still unstable with epson 1400/ pm-g4500
    4. huey: after calibration in a dark room, creates a monitor profile that has more red tint. is this right?
    Hardware:
    Japan Epson PM-G4500 (U.S. epson Stylus Photo 1400)
    using the epson driver: 12571.dmg -(u.s. driver, i can't read the japanese version), so im using their paper profiles are shown in PSD
    Benq G2400w
    5 default settings: using the sRGB setting: un-edited
    Huey Monitor Calibrator
    ??? 1.0.4 software update, sometimes appears on the desktop menu bar, sometimes not. somewhere it is said i might need to extract files and place into preferences, don't know details, so can't perform this task
    OSx: 10.5.6
    SystemPreferences/Displays/Color/DisplayProfile/ D65 G1.8 A??? turned off Huey and Calibrated by eye
    then applied Huey. it came out to d65 G2.2 A0.00. cannot be edited---Huey GAVE MY MONITOR A MORE RED Tint
    CS4 Psd 11.0.1
    CS4 Indesign 6.0.1
    Colorsync:checking a total of 82 profiles    13 bad files??? don't know if this is relevant to the problem
    when opening file:
    Embedded: Epson sRGB, so I Discard and use Adobe RGB (1998)
    saved as tiff, jpeg, psd
    PSD settings:
    RGB: Adobe (1998)
    CMYK: U.S. SWOP
    Color Management:
    Document (Profile: Adobe RGB (1998)
    Photoshop Manages Colors
    Printer Profile: SP14001410 PQJI ("super fine paper")
    people have mentioned to turn of colorsync to improve color matching. cannot turn of colorsync in psd. it is grayed out and is autmatically selected.
    so, i opened the  "preview" software:
    file/print/colormatching/ the option to choose color sync or epson is there. but i have to select one.
    Suggestions, anyone
    1. Do i need a rips software: ex. Colorbyte's product, "Imageprint" my epson is only a sp 1400/pm g-4500, so is this necessary?
    2. Get a different monitor?
    3. Buy a different monitor calibrator?
    4. Do i need to trash/replace anything in the preferences?
    i know i have a monitor calibration problem, but i also have a printer problem. What should I do? I've seen test screens available on the internet, but I don't want to make corrections just by eyesight. Is this my only option left?

    Rich....answers below you questions.
    --agree, i think the monitor [i have] is for purely gaming. big mistake on my part. i will try to pick-up a huey pro. if i recall correctly, huey pro allows you to edit the profiles. i could be wrong. are there any monitors you suggest, IPS??? i think that's what they're called? i just found a name-drop on the apple web store;p --"eizo"
    If you are serious about color matching, start with a monitor profiling package.  Your monitor may be more than good enough, so save the money.  You'll need a monitor profiling package anyway, so start there.  Then, if that doesn't cut it, get a new monitor.  Unless you are doing high end work and have money to burn, you probably don't need an Eizo.  Nice, but expensive.
    Second, you need an accurate printer profile for your printer/paper/ink combination, and you need to print with the correct settings and profiles.
    -- to tell you the truth, for this project, i will be using non-epson paper. i will research these vendors for their paper profile, if available- Kokuyo. yes, its non-epson, but their are some cool papers out there that are "dying" to be used by someone.
    Profiles provided by paper and/or ink manufacturers vary tremendously.  Even the good ones are only good for printers that closely adhere to the "standard" used to generate the profile.  If your printer happens to be coincide with the standard, great.  But, even then, some profiles are well made and others are not.  Try them and see how they work.  If they work great, fantastic, but you still need to compare your results to a properly calibrated and profiled monitor, otherwise, forget it.
    ...ambient lighting and viewing lights will also affect your perception of the viewed print, so they need to be controlled.
    --I'm using 2 flourescent lights. one, close to the screen to the left and the other a ceiling type for the entire room.  i've tried huey both at night and during the day. checking the monitor,  colors, and prints, i preferably, do during the day.
    You probably have bigger fish to fry, so save the lighting for later.  If you can, look at your prints using filtered daylight (e.g., soft, indirect light from a north facing window, with the sun in the south.  Don't hold the print next to a green or red wall, bright yellow curtains, etc).  Filtered daylight will give you fairly accurate representation of the colors in your print.  When ready for viewing lights, we can talk again.
    ...then you will need a postscript RIP, but that seems unnecessary, especially at this level.
    --i'm trying to stay "low-brow" as long as possible. Is messing with the curves the best work around, so far. the work ahead of me looks daunting. ;p
    Don't get a RIP, especially at this point.  Get the basics handled and it is highly unlikely you will need a RIP.
    I don't have a Huey, but I have heard mixed reviews on them.
    --are there any that you suggest?
    i1 Display is a decent, cost effective package.  Check with www.Chromix.com and see what they suggest.  This package will ONLY profile monitors, not printers.  If you want to generate your own printer profiles, be prepared to spend a lot more money.
      other questions:
    1. are you using color sync throughout your workflow? No...I am working on a PC, which doesn't have colorsync.
    2. there were 19 damaged profiles out of 39 in my color sync. is it important i fix these? Not even sure what this means.  Check with a Mac person.
    3. from what i understand so far, there are profiles for the following:
    a. epson paper
    b. monitor
    c. photoshop/ and illus.
    Am i missing the concept here?
    If all the files in this book were created with an embedded EpsonRGB, theoretically I should print to epson with the printer profile set as: EpsonRGB. its one straight line, but i'm guessing this is one way. i have yet to test it. the other way of course, is to zero out all variables, use working profile when opening in psd and then print... that's what i've got to work out still.
    I am guessing EpsonRGB is probably their captive name for sRGB, but I don't know.  You really need to understand the concepts before getting hung up on details.  Real World Color Management is the place to start.  Typically, you will be dealing with three types of profiles....Monitor profiles so your images display accurately, printer profiles (inkjet, press, etc) which will make sure your colors print accurately, and working space profiles (sRGB, Adobe RGB, ProPhoto RGB, etc).  They all tie together, using a device independent, mathematical model of human vision as the universal translator.  Get the book.
    4. i presume printing the book as a pdf on acrobat is one "work-around" solution.
    It depends what you mean by work-around.  Yes, you can output to PDF, but you still need to make sure you are not screwing up the color by improperly implementing color management.  The principles still apply.  You can hose the color in a PDF too if you don't handle it properly.
    5. from what it sounds like creating a post-script is not necessary, so i'll focus more on the pdf printing in acrobat
    If you are talking about sending a job to a printing press, I'd send InDesign or PDF files to your printer (or Illustrator for simple layouts).  The commercial printer will RIP the file and create plates for the press.  So, you don't have to create postscript yourself.  For simple inkjet prints, you normally don't need a postscript RIP.
    6. come to think of it, i've had problems with printing on cs3, using the above mentioned monitor.
    a. is this right? 1. calibrate the screen first.but how do i tell psd to tell the monitor that its too red: a.) color sync? b.) soft proofing
    Again....Read Real World Color Management.  You need to understand the principles first.  Asking detailed questions without having a solid understanding of principles is the long, hard way.  A monitor profiling package will calibrate and profile your monitor, bringing it back to standard benchmark.  You want consistency and accuracy. 

  • MacBook late '08 + BenQ V2410 ECO via MiniDP to HDMI = SLOW Internet

    Hi
    First of all, I'm really sorry for my bad English.
    My Problem:
    Whenever I connect my MB to the monitor (BenQ V2410 ECO), the internet starts to slow down.
    It's a pain.
    I tested it on my television and the internet didn't slow down.
    What should I do?
    Is my MB or the monitor the problem?
    Thanks,
    Mihael

    Pls help me.

  • BENQ FP241W on Retina Macbook Pro - native resolution not supported?

    Hi there,
    I have tried connecting my BENQ FP241W monitor to my new Macbook Pro with retina display via HDMI.
    The monitor appears to be displaying at only 1600x900 and looks very blurry since the native resolution of the monitor is 1920x1200. I have actually tried this with an older 2009 model macbook pro and the same thing happend, although I was using a dispaly port to HDMI adaptor and never investigated further to the reason the native resolution was not supported.
    Going back to the Retina Macbook and the BENQ FP241W. It gives the following resolution options for scaled: 1080p, 1080i and 1600x900. When I choose 1080p or 1080i it looks the same as 1600x900 i.e very blury and not even close to the sharpness that is capable of the display - true 1080p should look sharper than how it looks selected so I dont believe it is actually displaying 1080p. It also has the option for 'best for display' which I would expect it to show native resolution of 1920x1200 - unfortunately it still apears to be 1600x900.
    Can anyone help me out? Is this a driver issue or something else?
    Thanks
    Rich

    I can sort this out by just using a HDMI > DVI cable which works fine. I think there must just be an issue with the BenQ HDMI input supporting 1920x1200. Its annoying because the screen is also connected to a PC workstation by DVI so it would be good to have the HDMI for the Macbook so I can quickly switch the display by pressing a button instead of having to unplug cables...

  • Using a BENQ E2220HD monitor

    I connected my macbook to a Benq E2220HD I just bought. I works fine except the devices I attach to the USB ports don't seem to be working. No power on a wacom and any external drives do not mount. Is this a case of no drivers for OSX. I've checked out Benq's web site and they don't exactly show a drivers download page. Question is do I need them for this monitor for the other ports?

    Just got to know the monitor a bit better. Everything works fine. :-))

  • Judder using Mplayer... maybe force different resolution/refresh rate?

    Hi!
    (I posted this in the newbie section too, but this is maybe the most appropriate place??)
    I've set up my computer as a media center using Freevo. As the main media player in Freevo I use Mplayer. The setup is working beautifully, but I'm getting some judder and it's a bit annoying. It's most noticable during bright, fast moving scenes.
    So I've been trying to figure out how to remedy this, but it's harder than I thought. My setup is the following:
    AMD 4200+ dual core, 2 gigs ram, Nvidia 7800GTX, 24" LCD and Pioneer LX508D plasma TV, and I'm using CoreAVC as decoder (amazing piece of software )
    When I bought the 24" screen for my computer the sales guy (using windows) forced the resolution to 1920x1080. It looked a bit stretched, but if I could do this in Linux I'd avoid having parts of the picture missing on my TV. Now I have to use 1920x1200 resolution as main X session and since my TV is 1920x1080 parts of the desktop is out of view on my TV. This isn't too big of a deal though cause when playing movies they come out in 1920x1080. It'd be nice though to get the correct aspect ratio between my pc screen and my TV (I've been trying to use Twinview and clone, but it's impossible to use 1920x1200 on the 24" and 1920x1080 on the TV at the same time). I've tried to force my pc screen to use 1920x1080 (since it worked in windows it's supposed to be possible), but when I enable it through xorg.conf the screen goes blank. Using nvidia-settings doesn't give me the option of using 1920x1080 on the 24" at all.
    So what I'm hoping to be able to do is to force the computer screen to use 1920x1080 and a refresh rate of 72Hz. This should eliminate alot of the judder and at the same time I won't have to use the "PC mode" on my TV (PC mode restrict the Hz to max 60Hz). Hopefully the TV will accept the 1920x1080 72Hz as any input and let me use the normal input (and then be able to use 72Hz... or 96Hz for that matter).
    Anyone know how I might be able to do that? I'd really appreciate any help at all since this is the only thing that's not perfect with my setup.

    Ok, I tried to change the xorg.conf file to 72Hz on the TV and it when black again. This is what the xorg.0.log shows:
    X.Org X Server 1.4.2
    Release Date: 11 June 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.25-ARCH i686
    Current Operating System: Linux arch 2.6.25-ARCH #1 SMP PREEMPT Mon Jul 14 15:25:51 UTC 2008 i686
    Build Date: 21 June 2008 05:47:59PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 19 13:36:04 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "X.org Configured"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Videocard0"
    (**) |-->Input Device "Mouse0"
    (**) |-->Input Device "Keyboard0"
    (**) Option "Xinerama" "0"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (WW) The directory "/usr/share/fonts/Type1" does not exist.
    Entry deleted from font path.
    (==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
    (**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (**) RgbPath set to "/usr/share/X11/rgb"
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81e0a60
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 2.0
    X.Org XInput driver : 2.0
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org Video Driver, version 2.0
    (--) using VT number 3
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 1002,5950 card 103c,2a24 rev 10 class 06,00,00 hdr 00
    (II) PCI: 00:02:0: chip 1002,5a34 card 0000,0000 rev 00 class 06,04,00 hdr 01
    (II) PCI: 00:12:0: chip 1002,4379 card 103c,2a24 rev 00 class 01,01,8f hdr 00
    (II) PCI: 00:13:0: chip 1002,4374 card 103c,2a24 rev 00 class 0c,03,10 hdr 80
    (II) PCI: 00:13:1: chip 1002,4375 card 103c,2a24 rev 00 class 0c,03,10 hdr 00
    (II) PCI: 00:13:2: chip 1002,4373 card 103c,2a24 rev 00 class 0c,03,20 hdr 00
    (II) PCI: 00:14:0: chip 1002,4372 card 103c,2a24 rev 11 class 0c,05,00 hdr 80
    (II) PCI: 00:14:1: chip 1002,4376 card 103c,2a24 rev 00 class 01,01,8a hdr 00
    (II) PCI: 00:14:3: chip 1002,4377 card 103c,2a24 rev 00 class 06,01,00 hdr 80
    (II) PCI: 00:14:4: chip 1002,4371 card 0000,0000 rev 00 class 06,04,01 hdr 81
    (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 01:00:0: chip 10de,0091 card 10de,02c2 rev a1 class 03,00,00 hdr 00
    (II) PCI: 02:01:0: chip 13f6,0111 card 153b,1144 rev 10 class 04,01,00 hdr 00
    (II) PCI: 02:03:0: chip 10ec,8139 card 103c,2a24 rev 10 class 02,00,00 hdr 00
    (II) PCI: 02:04:0: chip 1106,3044 card 103c,2a24 rev 80 class 0c,00,10 hdr 00
    (II) PCI: End of PCI scan
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
    [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:2:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
    (II) Bus 1 I/O range:
    [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[b]
    (II) Bus 1 non-prefetchable memory range:
    [0] -1 0 0xfa000000 - 0xfcffffff (0x3000000) MX[b]
    (II) Bus 1 prefetchable memory range:
    [0] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b]
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:20:3), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 2: bridge is at (0:20:4), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 2 I/O range:
    [0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[b]
    (II) Bus 2 non-prefetchable memory range:
    [0] -1 0 0xfde00000 - 0xfdefffff (0x100000) MX[b]
    (II) Bus 2 prefetchable memory range:
    [0] -1 0 0xfdd00000 - 0xfddfffff (0x100000) MX[b]
    (--) PCI:*(1:0:0) nVidia Corporation G70 [GeForce 7800 GTX] rev 161, Mem @ 0xfa000000/24, 0xd0000000/28, 0xfb000000/24, I/O @ 0xef00/7
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) PCI I/O resource overlap reduced 0x00004100 from 0x0000411f to 0x000040ff
    (II) PCI Memory resource overlap reduced 0xe0000000 from 0xe0000000 to 0xdfffffff
    (II) Active PCI resource ranges:
    [0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    (II) Inactive PCI resource ranges:
    [0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    (II) Inactive PCI resource ranges after removing overlaps:
    [0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "record" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded by default.
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
    (II) NVIDIA GLX Module 173.14.09 Thu Jun 5 00:07:40 PDT 2008
    (II) Loading extension GLX
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "xtrap"
    (II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
    (II) Module xtrap: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DEC-XTRAP
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension RECORD
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 1.4.2, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Video Driver
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.3.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.3.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) NVIDIA dlloader X Driver 173.14.09 Wed Jun 4 23:47:25 PDT 2008
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 01:00:0
    (--) Assigning device section with no busID to primary device
    (--) Chipset NVIDIA GPU found
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) resource ranges after probing:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    [36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Option "NoLogo" "true"
    (**) NVIDIA(0): Option "TwinView" "1"
    (**) NVIDIA(0): Option "TwinViewOrientation" "Clone"
    (**) NVIDIA(0): Option "MetaModes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
    (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
    (**) NVIDIA(0): Enabling RENDER acceleration
    (**) NVIDIA(0): TwinView enabled
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0): enabled.
    (II) NVIDIA(0): NVIDIA GPU GeForce 7800 GTX (G70) at PCI:1:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 262144 kBytes
    (--) NVIDIA(0): VideoBIOS: 05.70.02.11.20
    (II) NVIDIA(0): Detected PCI Express Link width: 16X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (--) NVIDIA(0): Connected display device(s) on GeForce 7800 GTX at PCI:1:0:0:
    (--) NVIDIA(0): BenQ G2400W (DFP-0)
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1)
    (--) NVIDIA(0): BenQ G2400W (DFP-0): 310.0 MHz maximum pixel clock
    (--) NVIDIA(0): BenQ G2400W (DFP-0): Internal Dual Link TMDS
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1): 155.0 MHz maximum pixel clock
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1): Internal Single Link TMDS
    (II) NVIDIA(0): Display Devices found referenced in MetaMode: DFP-0, DFP-1
    (II) NVIDIA(0): Assigned Display Devices: DFP-0, DFP-1
    (II) NVIDIA(0): Validated modes:
    (II) NVIDIA(0): "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
    (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
    (--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
    (--) NVIDIA(0): option
    (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    [36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) NVIDIA(0): Initialized GPU GART.
    (II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
    (II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
    (II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
    (II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
    (II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
    (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    (II) NVIDIA(0): Config Options in the README.
    (II) NVIDIA(0): Setting mode "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
    (II) Loading extension NV-GLX
    (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
    (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
    (==) NVIDIA(0): Backing store disabled
    (==) NVIDIA(0): Silken mouse enabled
    (II) Loading extension NV-CONTROL
    (==) RandR enabled
    (II) Setting vga for screen 0.
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (II) Initializing extension GLX
    (**) Option "Protocol" "auto"
    (**) Mouse0: Device: "/dev/input/mice"
    (**) Mouse0: Protocol: "auto"
    (**) Option "CorePointer"
    (**) Mouse0: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons" "yes"
    (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5 6 7"
    (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
    (**) Mouse0: Buttons: 11
    (**) Mouse0: Sensitivity: 1
    (**) Option "CoreKeyboard"
    (**) Keyboard0: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "trustda"
    (**) Keyboard0: XkbModel: "trustda"
    (**) Option "XkbLayout" "no"
    (**) Keyboard0: XkbLayout: "no"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (II) evaluating device (Keyboard0)
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    (II) evaluating device (Mouse0)
    (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
    (--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
    (II) Mouse0: ps2EnableDataReporting: succeeded
    Could not init font path element /usr/share/fonts/Type1, removing from list!
    My xorg.conf looks like this now (I don't know what values to use for HorizSync and VertFresh on my TV, the ones that are in there I just made up ):
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder63) Mon May 19 00:34:28 PDT 2008
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "glx"
    Load "dbe"
    Load "xtrap"
    Load "extmod"
    Load "record"
    Load "freetype"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "trustda"
    Option "XkbLayout" "no"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    Option "Emulate3Buttons" "yes"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "BenQ G2400W"
    HorizSync 31.0 - 94.0
    VertRefresh 50.0 - 85.0
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "PIONEER_PDP."
    # HorizSync 15.0 - 80.0
    # VertRefresh 23.0 - 60.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G70 [GeForce 7800 GTX]"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7800 GTX"
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7800 GTX"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "NoLogo" "true"
    Option "TwinViewOrientation" "Clone"
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "DFP-0"
    Option "metamodes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    I read somewhere that the TV is supposed to be able to show 1080p in 72Hz. But when I try that it goes blank. Maybe it has something to do with the monitor being 1920x1200 and the TV 1920x1080. The monitor won't accept 1920x1080 as resolution so I guess that can only be done in Windows...

  • [Help] wine (AUR) + ATI WoW = crash on launch

    Howdy
    Been using Arch for a long time (came from Gentoo), but not been much of a gamer the last years, for that i had a MS rig with xp then vista.
    I installed the 32-wine from AUR (thanks for that by the way), everything seems ok.
    I downloaded the apropriate installers for WoW, both normal and Burning Crusade.
    Both install fine, and i can "launch" the game from the "desktop shortcut".
    The problem does not start when I hit "play", then my screen all gets "twisted", and everything gets pixelated.
    (Kind of when a game crashes and messes up the screen)
    the only fix i found so far is ctrl+alt+<--" to get back into KDE to get it working again.
    this is run on a 3870 card from ATI, everything else works fine, include compizfusion (turned of when i try to run the game).
    Everything else seems to work fine.
    I assume it is some sort of gfx bug, prolly relates to directx, but i get same result when i use -opengl to launch launcher.exe
    The problem "breaks" everything, even when run in a containerwindow.
    Settings are for xp (winecfg)
    Posting xorg.conf incase there might be something related to that.
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dbe"
    Load "glx"
    Load "dri"
    Load "extmod"
    Load "GLcore"
    Load "record"
    Load "xtrap"
    Load "freetype"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "trustda"
    Option "XkbLayout" "no"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    #DisplaySize 520 320 # mm
    ### Comment all HorizSync and VertRefresh values to use DDC:
    Identifier "Monitor0"
    VendorName "BNQ"
    ModelName "BenQ G2400W"
    HorizSync 31.0 - 94.0
    VertRefresh 50.0 - 85.0
    Option "DPMS"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Option "DRI" "true"
    Identifier "Card0"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Unknown Board"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Running on a 24" monitor @ 1920x1200.
    Any help apriciated.
    Last edited by AllFather (2008-07-21 22:07:38)

    That's a really convoluted xorg.conf (two Screens, two Devices, two Monitors). If you look, you're using aticonfig-Monitor, aticonfig-Screen, and aticonfig-Device. I would try your other entries in different combinations (Screen0, Card0, Monitor0) and try tuning them.
    How did you make that config? Try hwd -xa as well.
    Last edited by Ranguvar (2009-02-19 04:26:41)

  • How do I connect my MacBook Air bought sep13 to a Benq GL2450? monitor?

    How do I connect my MacBook Air bought sep13 to a Benq GL2450? monitor?

    External screens are designed to work as extended displays for your computer's display. It means that menu bars and desktop icons won't appear, and you will only see windows if you drag them to the right part of the computer's display.
    To change this, you have to activate video mirroring > http://support.apple.com/kb/HT5019

  • Problem MacBook and BenQ Projector

    Hi everyone.
    Hopefully someone can help me with this. I just bought a MacBook 2.0Ghz 2 Gig RAM and I tried to have it work with a BENQ PB2140 projector that I have. I used a mini-DVI to S-Video adapter (from Apple) to connect both, uisng the S-video port of the projector. Unfortunately, the screen always flicker, sometimes just a few lines at a times, sometimes much worst. I tried all resolutions and scan rates (50 and 60), etc. I just managed to make it work once, after much trial and error. Of course, upon restart (to make sure that I could duplicate my success) the problem came back and I was never able to fix it. As I wanted to use the MacBook (otherwise a stellar machine: my best notebook ever) to make presentations to clients on the road, I am a bit frustrated and could use some help here guys...Thanks in advance.
    MacBook   Mac OS X (10.4.7)   2.0 Ghz, 2 G RAM
    MacBook   Mac OS X (10.4.7)   2.0 Ghz, 2 G RAM

    If you have used this projector with another computer
    before, is there any clue from those settings?
    I have used the Apple adapter to run S-video into a
    high definition TV. As I recall, I bumped the
    resolution up from whatever it initially defaulted to
    (800 x 600?) to the highest it would allow (1024 x
    768).
    Is NTSC versus PAL an issue? That's on the Color tab
    in Display settings.
    Thanks for the reply. I know the BENQ works great with the S-Video port of a Toshiba Satellite A70 that I would like to sell to keep only the MacBook I will check into the NTSC and PAL thing but I think I already fiddled with that. Ans yes I believe that the highest resolution the BENQ takes is 1024 by 768.

  • Connect Benq projector to early Macbook Air

    Model Benq projector MX518 will not connect to MacBook Air 11" early model using adaptor as suggested by my Mac Dealer with DB9 cord connecting to
    computer No.2 /or Number one, only signal received is desktop imge and tht image is one which was the original from purchase image!
    Might a USB to HDMI or similar connection be preferable?
    Oh and yet another connecting cord???
    Thank YOU

    I'm sitting at my iMac now.
    I clicked:
    Apple Menu -> System Preferences -> Printers and Scanners
    Click +
    It should say under nearby printers the name of your printer.
    When you had the USB cable before you probably 'confused' it because it was already set up you know?
    Hopefully that works for you!
    It reminded me to add my printer here on this computer

  • BENQ FP241W on Retina Macbook Pro

    I have a brand new Retina MBP and a BENQ FP241W and they don't work together using the HDMI port.
    When plugged in the Mac screen flashes and the BENQ is detcted.
    Then the BENQ screen either goes green or red and doesn't show a mirrored screen.
    The display dialog for the BENQ gets detached from its header and then goes blank.
    Anyone have any ideas how to make it work?

    I can sort this out by just using a HDMI > DVI cable which works fine. I think there must just be an issue with the BenQ HDMI input supporting 1920x1200. Its annoying because the screen is also connected to a PC workstation by DVI so it would be good to have the HDMI for the Macbook so I can quickly switch the display by pressing a button instead of having to unplug cables...

  • Benq MP771 projector does not detect my Macbook???

    hello,
    i recently purchased a benq mp771 short throw projector to use with my Macbook (2007). I had been told by the manufacturers that it is not compatible with macbook pros but works with macbooks. I was using osx 10.4 and had no problems using the projector. My hard drive crashed and after replacement it came with osx 10.5. I'm now running with 10.5.8. I have recently tried using the projector with my macbook but it seems unable to detect the laptop. My computer detects the projector no problem. I'm running a DVI to VGA input. It appears that the system upgrade may have made my computer undetectable. I wondered if anyone could offer any possible solutions other than downgrading the osx.
    cheers
    tone

    How are the to computer connected?
    Do y have any idea as to what the 157 kb is since yo say it can'g find the startup disk.
    Does the MacBook Pro work OK?
    Do you have File vault on?

  • Macbook Air 2014 11inch connecting to Benq monitor

    I have just got a new macbook air 11" and plugged into my Benq E2200HD monitor with Belkin mini Display port to HDMI and blue scene on the monitor. My old Macbook uses the same cable, adaptor and monitor and works fine. Then plug into new Macbook Air and only a blue screen, even though in display settings it shows up as as a monitor with the name BenQ E2200HD. Do I need a driver or something? I have 2 mini display port to HDMI and both don't work on the monitor but work on the TVs. Any ideas?

    Hello there, Fuchzzz.
    Great job on doing some great troubleshooting on your own. The following Knowledge Base article offers up some additional information on resetting the resolution as well:
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/ht1573
    Reset the resolution
    Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
    Start up in Safe Mode.
    From the Apple () menu, choose System Preferences.
    Choose Displays from the View menu to open the preferences pane.
    Select any resolution and refresh rate that your display supports.
    Restart your computer.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • Macbook + External Monitor + HD Video = 89 (C) Degrees

    Mid 2008 Macbook, 2.4ghz, 4 gig ram,
    BenQ 1920x1080 monitor via DVI
    How concerned should I be with such a high temperature? The CPU has peaked at 89 degrees but it runs consistently hotter (65-70) on the external monitor.

    Hi, Amanda. 
    I am guessing you are receiving a message: "This movie cannot be played because a display that is not authorized to play protected movies is connected."  To view HD video on an external display, the display must have a digital connection (DVI, DisplayPort, or HDMI) and also support HDCP.  If the monitor is HDCP compliant, then the issue would be related to the connect between the Mac and the monitor.  I would recommend trying with one of the approved digital connectors.
    iTunes: Purchasing and viewing HD videos
    http://support.apple.com/kb/ht3209
    Hope that helps,
    Jason H.

  • I have a macbook pro with lion os. and i want to connect it to my optoma dlp projector. when i connect through a mini display to vga adapter in MBP it detects as OPTOMA XGA but no image on the screen.

    i have a macbook pro. i want to connect it to projector and i have a minidisplay to vga adapter. i could connect my MBP to benq projector successfully and for  all other displays( Monitors). but when i connect it to optoma projector, MBP detects the display as OPTOMA XGA but nothing on bigger screen. i tried changing the resolution and refresh rate also but no changes.
    In my office we got benq projectors , for that it is working very well.(plug and play).
    and also i want to say that there is no problem with the optoma projector seems, because all other windows laptops are working well with that.
    i was struggling with this since one month. i googled it could not find anything supportive for my problem. please help me regarding this. i am new to apple. i hope there must be genius around here.
    thnak you

    Rwogera wrote:
    I couldn't transmit sound either, do i need another cable like Kim said? i mean it cant be transmitted through this HDMI port? as for me i have one of the latest mac pro with intel core i5..tnx
    I need to know which MacBook Pro you have.  Only mid-2010  and later MBP's transmit sound through MiniDisplay Port to HDMI.  I have no information about the Mac Pro, so you might want to go to that Forum and ask there.

Maybe you are looking for