Screen + centericq = garbled [solved finally]

ok, so centericq draws borders and things with those ascii box characters.... you know what I'm talking about...
anyway, when running centericq in screen with a status line, the box characters bleed into the status and then corrupt everything in the screen session.... is there anything I'm missing?
I've noticed alot of people like to put huge amounts of term cap/info stuff in their screenrc's - would this have anything to do with it? I have nothing... is this possibly a termcap issue?

I've recently decided to try out screen and centericq and ran into the same problem as mentioned in this thread. When I did alias screen="TERM=screen screen" (I think that was the solution phrakture mentioned), while it did fix the problem with centericq garbling up everything, I ran into another problem.
I have screen set up so that it has a little caption thing in the bottom. When I run screen with that alias, the caption messes up so that the text is messed up to the point where it is not readable (but not garbled in the same way as before). Any ideas why this is happening? (I am using the most recent versions of urxvt, screen, and centericq that you can get through pacman.)

Similar Messages

  • Screen gone garbled

    My screen went garbled, blue and green blotchy with only just able to see the buttons for force quit (one program had cancelled restart)
    Is this the graphics card, the screen (20"LCD Apple), or the Mac?
    Thanks
    Hardware Overview:
    Machine Name: Power Mac G5
    Machine Model: PowerMac7,3
    CPU Type: PowerPC G5 (3.0)
    Number Of CPUs: 2
    CPU Speed: 2.3 GHz
    L2 Cache (per CPU): 512 KB
    Memory: 4 GB
    Bus Speed: 1.15 GHz
    Boot ROM Version: 5.2.4f1
    ATI Radeon X850 XT:
    Chipset Model: ATY,R481
    Type: Display
    Bus: AGP
    Slot: SLOT-1
    VRAM (Total): 256 MB
    Vendor: ATI (0x1002)
    Device ID: 0x4a48
    Revision ID: 0x0000
    ROM Revision: 113-A35804-108
    Displays:
    Cinema Display:
    Display Type: LCD
    Resolution: 1680 x 1050
    Depth: 32-bit Color
    Core Image: Supported
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Quartz Extreme: Supported
    Rotation: Supported
    Display:
    Status: No display connected

    Simon,
    I am having similar problems as can be seen in my thread:
    http://discussions.apple.com/thread.jspa?threadID=533412&tstart=15
    I have been told by MacLover and another very qualified Mac owner that it's very unlikely that the Mac could be at fault (i.e. the logic board or processors causing the screen to appear different shades) and my G5 Quad is in the shop right now. Funny thing was the service tech told me that it could very well be the logic board so go figure? Have you tried a different monitor to see if it happens on there as well? I have been told to check a different monitor (which I did with the same output) and to swap the video card (if you have one) out to see if that solves it. I think both of those options have been mentioned by other posters to your thread. Also, have you tried running the Apple Hardware Test that came with your Mac? It should give you some idea if the video card has issues. Although I could never get past the logic board test on mine due to it hanging on the logic board test and freezing. I guess in that order if you check it with another monitor with the same results it's not the monitor. If you have a swap video card you can try and that doesn't help it "may" very well be something in the Mac. I am no expert but with all this I am learning fast! I feel like the guy that stayed in that hotel chain overnight and now is a Mac repairman! Oh, and there was also a mention of trying a different monitor cable to rule that out as well. I'll let you know how mine fairs out when it comes back and maybe be of more help there.
    Hope this helps.

  • 15" i7 Macbook Pro from early 2011.takes the mac laptop two or three tries to boot successfully. It would turn on, show gray screen, shut down, turn on again, show gray screen, shutdown, and then turn on, show gray screen, before it can finally get

    Hello All,
    I have a 15" i7 Macbook Pro from early 2011. The past few weeks, it has been getting increasingly difficult to get on my computer. It takes the mac laptop two or three tries to boot successfully. It would turn on, show gray screen, shut down, turn on again, show gray screen, shutdown, and then turn on, show gray screen, before it can finally get to the dark gray log-in screen. Even when I finally get logged in to start working, thinking it would be okay now, it shuts down randomly.
    I've ruled out the possibility of a software problem because I've just done a clean re-install of Mac OS X Mavericks on my computer just yesterday.
    I did upgrade the RAM recently, about a month and a half ago, from 4GB to 16GB, I went to the apple store four days after that upgrade to have them do a hardware test, and clean the inside of my laptop, which helped with previous heat issues. When they did the hardware test, the hardware was all registered as fine from their system.
    I've tried resetting the SMC, PRAM, and doing the internet recovery hardware test, but to no avail. I thought I could at least find out what parts needed to be replaced from the hardware test but it seems that when the hardware test is almost finished, the computer just shuts down, So I am unable to see the results.
    My computer is also having battery issues, under battery condition, it says "replace now," parts have been ordered, waiting for arrival. But if the battery health is low, it should still boot up fine, it would just hold a significantly less charge.
    Could this be a hard drive issue?
    Has anyone had similar symptoms and how was it resolved?
    Does anyone know what I can do to alleviate this issue?
    I haven't had time to take it to Apple because I'm currently taking a 21 credit semester academically. I'm an art and design student so my computer is basically the bane of my existence. Help! Any constructive advice is welcomed!
    Thank you so much for your input!
    -Christina C.

    Problem description:
    The Hard Disk is failing.
    EtreCheck version: 2.0.11 (98)
    Report generated November 4, 2014 at 7:59:28 AM EST
    Hardware Information: ℹ️
      MacBook Pro (15-inch, Early 2011) (Verified)
      MacBook Pro - model: MacBookPro8,2
      1 2.2 GHz Intel Core i7 CPU: 4-core
      16 GB RAM Upgradeable
      BANK 0/DIMM0
      8 GB DDR3 1600 MHz ok
      BANK 1/DIMM0
      8 GB DDR3 1600 MHz ok
      Bluetooth: Old - Handoff/Airdrop2 not supported
      Wireless:  en1: 802.11 a/b/g/n
    Video Information: ℹ️
      Intel HD Graphics 3000 - VRAM: 512 MB
      Color LCD 1440 x 900
      AMD Radeon HD 6750M - VRAM: 1024 MB
    System Software: ℹ️
      OS X 10.9.5 (13F34) - Uptime: 0:3:43
    Disk Information: ℹ️
      TOSHIBA MK7559GSXF disk0 : (750.16 GB)
      S.M.A.R.T. Status: Verified
      EFI (disk0s1) <not mounted> : 210 MB
      HDV4 (disk0s2) /  [Startup]: 749.30 GB (712.10 GB free)
      Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
      MATSHITADVD-R   UJ-898 
    USB Information: ℹ️
      Apple Inc. FaceTime HD Camera (Built-in)
      Apple Inc. BRCM2070 Hub
      Apple Inc. Bluetooth USB Host Controller
      Apple Inc. Apple Internal Keyboard / Trackpad
      Apple Computer, Inc. IR Receiver
    Thunderbolt Information: ℹ️
      Apple Inc. thunderbolt_bus
    Gatekeeper: ℹ️
      Mac App Store and identified developers
    Kernel Extensions: ℹ️
      /Library/Application Support/Avast/components/fileshield/unsigned
      [loaded] com.avast.AvastFileShield (2.1.0 - SDK 10.9) Support
      /Library/Application Support/Avast/components/proxy/unsigned
      [loaded] com.avast.PacketForwarder (1.4 - SDK 10.9) Support
    Launch Agents: ℹ️
      [not loaded] com.adobe.AAM.Updater-1.0.plist Support
      [loaded] com.avast.userinit.plist Support
    Launch Daemons: ℹ️
      [invalid?] com.adobe.SwitchBoard.plist Support
      [loaded] com.avast.init.plist Support
      [loaded] com.avast.uninstall.plist Support
      [loaded] com.avast.update.plist Support
      [invalid?] com.perion.searchprotectd.plist Support
    User Launch Agents: ℹ️
      [invalid?] com.avast.home.userinit.plist Support
      [loaded] com.google.keystone.agent.plist Support
      [invalid?] com.jdibackup.ZipCloud.autostart.plist Support
    User Login Items: ℹ️
      None
    Internet Plug-ins: ℹ️
      AdobePDFViewer: Version: 10.1.1 Support
      QuickTime Plugin: Version: 7.7.3
      JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
      Default Browser: Version: 537 - SDK 10.9
    User Internet Plug-ins: ℹ️
      TroviNPAPIPlugin: Version: 1.0 - SDK 10.9 Support
      Google Earth Web Plug-in: Version: Unknown
    Safari Extensions: ℹ️
      Avast Online Security
      Trovi Search for Safari
    3rd Party Preference Panes: ℹ️
      None
    Time Machine: ℹ️
      Time Machine not configured!
    Top Processes by CPU: ℹ️
          16% mds
          7% WindowServer
          1% loginwindow
          1% fontd
          1% com.avast.daemon
    Top Processes by Memory: ℹ️
      120 MB com.avast.daemon
      86 MB Google Chrome
      52 MB Finder
      52 MB WindowServer
      41 MB Google Chrome Helper
    Virtual Memory Information: ℹ️
      13.45 GB Free RAM
      1.34 GB Active RAM
      944 MB Inactive RAM
      1.43 GB Wired RAM
      1.11 GB Page-ins
      0 B Page-outs

  • MacBook Pro 17inch - mid-2010 - screen graphics garbled

    So my screen goes garbled and I have to either turn it off and back on OR (strangely enough) drag one of the application windows around the screen like a dry eraser on a white board - for a while, there's a graphic echo, creating a cool pattern of images of the app window all over the screen, then it eventually starts to act like a dry eraser, cleaning off the 'echoes' and causing the screen to appear as normal.
    So I've seen this discussion before and seen people offer a variety of solutions. Some say it's hardware, and suggest replacing the NVIDIA card, others say try command+option+p+r. Some say it's RAM - I've noticed it does occur more often when my RAM useage is peaking (whilst watching the Activity monitor), but it doesn't always happen like that! I have 8Gb of RAM installed, so not sure how it can happen - anything more than 5 or 6 tabs open on Safari PLUS having Skype open, and the system goes crazy! Whilst the machine is registering 8GB, could it be possible one or both of the 4 GB cards are corrupt?
    I've had the logic board replaced, and the screen replaced. Haven't tried replacing the NVidia card yet.
    Have used Apple for ages but not really a techie, so not sure what info to provide to you awesome tech-heads. I"ve attached some screen-captures ...
    HELP!!!!!!!!!!!!!!!!!!!!

    thenzguitarman wrote:
    could it be possible one or both of the 4 GB cards are corrupt?
    I've had the logic board replaced, and the screen replaced. Haven't tried replacing the NVidia card yet.
    That is strange indeed. Yes, RAM could be at issue. If this is not the original RAM, install it. If it is, remove one module, try running; switch that same module to the other slot, try running; repeat with other module.
    The GPU cannot be replaced. It's soldered onto the logic board; thus, if you've had you logic board replaced, the GPU was replaced.

  • Xorg / catalyst / kernel upgrade - Frozen screen and input [SOLVED]

    I knew it, never upgrade xorg/graphic drivers when using ATI cards, just bless your god when it works and never touch it again. But I got tempted and I did a full system upgrade, and now... my xorg is broken.
    I'm using ATI proprietary drivers catalyst 8.12-1 with xorg 1.5.3-3. My card is an ATI x1950 pro.
    It used to work perfectly, but since the update, when i startx I just get a terminal (because of my .xinitrc) in fullscreen without my window manager getting launched, and my mouse in the middle of the screen; and nothing responds the mouse won't move, even ctrl+alt+backspace won't work. I have to ssh on my machine and 'killall X'.
    I tried starting off with a default config (using aticonfig --initial -f), but still the same problem.
    I have a dual screen setup.
    I disabled AIGLX and Composite, but no success.
    If I fail to repair this, since I made a backup of my pacman database, I could revert it right ?
    Please help us, us pwned ATI users !
    Here is the /var/log/Xorg.0.log
    X.Org X Server 1.5.3
    Release Date: 5 November 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.27-ARCH i686
    Current Operating System: Linux fatale 2.6.27-ARCH #1 SMP PREEMPT Mon Dec 8 22:01:01 UTC 2008 i686
    Build Date: 05 December 2008 09:10:55PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    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 Dec 13 03:36:24 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Xorg Configured"
    (**) |-->Screen "ScreenSamsung" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Card0"
    (**) |-->Input Device "Keyboard0"
    (**) |-->Input Device "PS/2 Mouse"
    (**) Option "AllowMouseOpenFail" "true"
    (**) Option "Xinerama" "true"
    (**) Option "AIGLX" "false"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (**) Xinerama: enabled
    (WW) The directory "/usr/share/fonts/PEX" does not exist.
    Entry deleted from font path.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
    (WW) The directory "/usr/share/fonts/ttf/western" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
    Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/TrueType" 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:unscaled,
    /usr/share/fonts/misc,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/75dpi,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/100dpi,
    /usr/share/fonts/Type1,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (**) Extension "Composite" is disabled
    (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
    (WW) Disabling Keyboard0
    (WW) Disabling PS/2 Mouse
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81d5900
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 4.1
    X.Org XInput driver : 2.1
    X.Org Server Extension : 1.1
    X.Org Font Renderer : 0.6
    (II) Loader running on linux
    (--) using VT number 7
    (--) PCI:*(0@1:0:0) ATI Technologies Inc RV570 [Radeon X1950 Pro] rev 0, Mem @ 0xe0000000/0, 0xf5000000/0, I/O @ 0x00008000/0, BIOS @ 0x????????/131072
    (--) PCI: (0@1:0:1) ATI Technologies Inc RV570 [Radeon X1950 Pro] (secondary) rev 0, Mem @ 0xf5010000/0
    (II) System resource ranges:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[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 - 0x00000000 (0x1) IX[b]
    (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) "dri" will be loaded. This was enabled by default and also specified in the config file.
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 7.4.0, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 1.1
    (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: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 7.4.0, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (--) AIGLX enabled
    (II) Loading extension GLX
    (II) LoadModule: "type1"
    (WW) Warning, couldn't open module type1
    (II) UnloadModule: "type1"
    (EE) Failed to load module "type1" (module does not exist, 0)
    (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.5.3, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.6
    (II) Loading font FreeType
    (II) LoadModule: "record"
    (WW) Warning, couldn't open module record
    (II) UnloadModule: "record"
    (EE) Failed to load module "record" (module does not exist, 0)
    (II) LoadModule: "fglrx"
    (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
    (II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
    compiled for 1.4.99.906, module version = 8.56.4
    Module class: X.Org Video Driver
    (II) Primary Device is: PCI 01@00:00:0
    (WW) Falling back to old probe method for fglrx
    (II) ATI Proprietary Linux Driver Version Identifier:8.56.4
    (II) ATI Proprietary Linux Driver Release Identifier: 8.561
    (II) ATI Proprietary Linux Driver Build Date: Dec 1 2008 14:55:43
    (WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
    (WW) Video driver ABI version of the X server is 4.1
    (--) Assigning device section with no busID to primary device
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
    (--) Chipset Supported AMD Graphics Processor (0x7280) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
    (II) AMD Video driver is running on a device belonging to a group targeted for this release
    (II) AMD Video driver is signed
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[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 - 0x00000000 (0x1) IX[b]
    (II) fglrx(0): pEnt->device->identifier=0x9377518
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (II) fglrx(0): === [atiddxPreInit] === begin
    (II) Loading sub module "vgahw"
    (II) LoadModule: "vgahw"
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 0.1.0
    ABI class: X.Org Video Driver, version 4.1
    (II) fglrx(0): PCI bus 1 card 0 func 0
    (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    (==) fglrx(0): Default visual is TrueColor
    (**) fglrx(0): Option "dri" "true"
    (**) fglrx(0): Option "KernelModuleParm" "agplock=0"
    (**) fglrx(0): Option "RingSize" "8"
    (**) fglrx(0): Option "EnableDepthMoves" "yes"
    (**) fglrx(0): Option "UseInternalAGPGART" "no"
    (**) fglrx(0): Option "DPMS" "true"
    (II) fglrx(0): Loading PCS database from /etc/ati/amdpcsdb
    (II) fglrx(0): 10BitPixelFormat disabled by default
    (==) fglrx(0): RGB weight 888
    (II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
    (==) fglrx(0): Gamma Correction for I is 0x06419064
    (==) fglrx(0): Gamma Correction for II is 0x06419064
    (==) fglrx(0): Buffer Tiling is ON
    (II) Loading sub module "fglrxdrm"
    (II) LoadModule: "fglrxdrm"
    (II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
    (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
    compiled for 1.4.99.906, module version = 8.56.4
    ABI class: X.Org Server Extension, version 1.1
    (--) fglrx(0): Chipset: "Radeon X1950 Series" (Chipset = 0x7280)
    (--) fglrx(0): (PciSubVendor = 0x1462, PciSubDevice = 0x0762)
    (--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
    (--) fglrx(0): Linear framebuffer (phys) at 0xe0000000
    (--) fglrx(0): MMIO registers at 0xf5000000
    (--) fglrx(0): I/O port at 0x00008000
    (==) fglrx(0): ROM-BIOS at 0x000c0000
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Loading /usr/lib/xorg/modules//libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.0.0
    ABI class: X.Org Video Driver, version 4.1
    (II) fglrx(0): Primary V_BIOS segment is: 0xc000
    (**) fglrx(0): Option "mtrr" "on"
    (II) Loading sub module "vbe"
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.1.0
    ABI class: X.Org Video Driver, version 4.1
    (II) fglrx(0): VESA BIOS detected
    (II) fglrx(0): VESA VBE Version 3.0
    (II) fglrx(0): VESA VBE Total Mem: 16384 kB
    (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
    (II) fglrx(0): VESA VBE OEM Software Rev: 9.13
    (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
    (II) fglrx(0): VESA VBE OEM Product: RV570
    (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
    (II) fglrx(0): ATI Video BIOS revision 9 or later detected
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 12, (OK)
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 12, (OK)
    drmOpenByBusid: drmOpenMinor returns 12
    drmOpenByBusid: drmGetBusid reports PCI:1:0:0
    (II) fglrx(0): Using adapter: 1:0.0.
    (II) fglrx(0): [FB] MC range(MCFBBase = 0xc0000000, MCFBSize = 0x10000000)
    (--) fglrx(0): Video RAM: 262144 kByte, Type: DDR3
    (II) fglrx(0): PCIE card detected
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000090, disabled=0x00000000
    (II) fglrx(0): Connected Display1: CRT on secondary DAC [crt2]
    (II) fglrx(0): Display1 EDID data ---------------------------
    (II) fglrx(0): Manufacturer: NUL Model: 1 Serial#: 1
    (II) fglrx(0): Year: 2001 Week: 1
    (II) fglrx(0): EDID Version: 1.3
    (II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    (II) fglrx(0): Sync: Separate
    (II) fglrx(0): Max Image Size [cm]: horiz.: 31 vert.: 23
    (II) fglrx(0): Gamma: 1.00
    (II) fglrx(0): DPMS capabilities: StandBy Suspend; RGB/Color Display
    (II) fglrx(0): First detailed timing is preferred mode
    (II) fglrx(0): redX: 0.597 redY: 0.343 greenX: 0.316 greenY: 0.566
    (II) fglrx(0): blueX: 0.153 blueY: 0.131 whiteX: 0.310 whiteY: 0.328
    (II) fglrx(0): Supported VESA Video Modes:
    (II) fglrx(0): 720x400@70Hz
    (II) fglrx(0): 640x480@60Hz
    (II) fglrx(0): 640x480@72Hz
    (II) fglrx(0): 640x480@75Hz
    (II) fglrx(0): 800x600@56Hz
    (II) fglrx(0): 800x600@60Hz
    (II) fglrx(0): 800x600@72Hz
    (II) fglrx(0): 800x600@75Hz
    (II) fglrx(0): 1024x768@60Hz
    (II) fglrx(0): 1024x768@70Hz
    (II) fglrx(0): 1024x768@75Hz
    (II) fglrx(0): Manufacturer's mask: 0
    (II) fglrx(0): Supported additional Video Mode:
    (II) fglrx(0): clock: 65.0 MHz Image Size: 304 x 228 mm
    (II) fglrx(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1184 h_border: 0
    (II) fglrx(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
    (II) fglrx(0):
    (II) fglrx(0):
    (II) fglrx(0): Monitor name:
    (II) fglrx(0): EDID (in hex):
    (II) fglrx(0): 00ffffffffffff003aac010001000000
    (II) fglrx(0): 010b0103081f1700caf0649857519127
    (II) fglrx(0): 214f54afce0001010101010101010101
    (II) fglrx(0): 010101010101641900a0400026301888
    (II) fglrx(0): 360030e410000018000000fe000a2020
    (II) fglrx(0): 20202020202020202020000000fe000a
    (II) fglrx(0): 202020202020202020202020000000fc
    (II) fglrx(0): 000a202020202020202020202020000e
    (II) fglrx(0): End of Display1 EDID data --------------------
    (II) fglrx(0): Connected Display2: DFP on secondary TMDS [tmds2i]
    (II) fglrx(0): Display2 EDID data ---------------------------
    (II) fglrx(0): Manufacturer: SAM Model: 1e5 Serial#: 1212821817
    (II) fglrx(0): Year: 2006 Week: 7
    (II) fglrx(0): EDID Version: 1.3
    (II) fglrx(0): Digital Display Input
    (II) fglrx(0): Max Image Size [cm]: horiz.: 38 vert.: 30
    (II) fglrx(0): Gamma: 2.20
    (II) fglrx(0): DPMS capabilities: Off
    (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    (II) fglrx(0): First detailed timing is preferred mode
    (II) fglrx(0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
    (II) fglrx(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
    (II) fglrx(0): Supported VESA Video Modes:
    (II) fglrx(0): 720x400@70Hz
    (II) fglrx(0): 640x480@60Hz
    (II) fglrx(0): 640x480@67Hz
    (II) fglrx(0): 640x480@72Hz
    (II) fglrx(0): 640x480@75Hz
    (II) fglrx(0): 800x600@56Hz
    (II) fglrx(0): 800x600@60Hz
    (II) fglrx(0): 800x600@72Hz
    (II) fglrx(0): 800x600@75Hz
    (II) fglrx(0): 832x624@75Hz
    (II) fglrx(0): 1024x768@60Hz
    (II) fglrx(0): 1024x768@70Hz
    (II) fglrx(0): 1024x768@75Hz
    (II) fglrx(0): 1280x1024@75Hz
    (II) fglrx(0): 1152x870@75Hz
    (II) fglrx(0): Manufacturer's mask: 0
    (II) fglrx(0): Supported Future Video Modes:
    (II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    (II) fglrx(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    (II) fglrx(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    (II) fglrx(0): Supported additional Video Mode:
    (II) fglrx(0): clock: 108.0 MHz Image Size: 376 x 301 mm
    (II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    (II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    (II) fglrx(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
    (II) fglrx(0): Monitor name: SyncMaster
    (II) fglrx(0): Serial No: HMEL205539
    (II) fglrx(0): EDID (in hex):
    (II) fglrx(0): 00ffffffffffff004c2de50139314a48
    (II) fglrx(0): 0710010380261e782ade95a3544c9926
    (II) fglrx(0): 0f5054bfef8081808140714f01010101
    (II) fglrx(0): 010101010101302a009851002a403070
    (II) fglrx(0): 1300782d1100001e000000fd00384c1e
    (II) fglrx(0): 510e000a202020202020000000fc0053
    (II) fglrx(0): 796e634d61737465720a2020000000ff
    (II) fglrx(0): 00484d454c3230353533390a20200056
    (II) fglrx(0): End of Display2 EDID data --------------------
    (WW) fglrx(0): More than one displays are connected,so clone mode is enabled
    (II) fglrx(0): Primary Controller - DFP on secondary TMDS
    (II) fglrx(0): Secondary Controller - CRT on secondary DAC
    (II) fglrx(0): Internal Desktop Setting: 0x00000008
    (II) fglrx(0): POWERplay version 3. 1 power state available:
    (II) fglrx(0): 1. 574/682MHz @ 0Hz [enable load balancing]
    (==) fglrx(0): QBS disabled
    (==) fglrx(0): FAST_SWAP disabled
    (==) fglrx(0): PseudoColor visuals disabled
    (==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) fglrx(0): Center Mode is disabled
    (==) fglrx(0): TMDS coherent mode is enabled
    (II) fglrx(0): Total of 24 modes found for primary display.
    (--) fglrx(0): Virtual size is 1280x1024 (pitch 0)
    (**) fglrx(0): *Mode "1280x1024_mine": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    (II) fglrx(0): Modeline "1280x1024_mine"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
    (**) fglrx(0): Default mode "1280x1024_mine": 109.6 MHz (scaled from 0.0 MHz), 63.7 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1280x1024_mine"x60.0 109.62 1280 1336 1472 1720 1024 1024 1026 1062 +vsync (63.7 kHz)
    (**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    (II) fglrx(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
    (**) fglrx(0): *Mode "1280x1024": 109.6 MHz (scaled from 0.0 MHz), 63.7 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1280x1024"x60.0 109.62 1280 1336 1472 1720 1024 1024 1026 1062 +vsync (63.7 kHz)
    (**) fglrx(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 (60.0 kHz)
    (**) fglrx(0): Default mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1280x768"x60.0 79.50 1280 1344 1472 1664 768 771 778 798 +hsync (47.8 kHz)
    (**) fglrx(0): Default mode "1280x720": 74.5 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 +hsync (44.8 kHz)
    (**) fglrx(0): Default mode "1280x720": 60.5 MHz (scaled from 0.0 MHz), 37.0 kHz, 50.0 Hz
    (II) fglrx(0): Modeline "1280x720"x50.0 60.46 1280 1328 1456 1632 720 721 724 741 +hsync (37.0 kHz)
    (**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
    (II) fglrx(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 +hsync (53.7 kHz)
    [.. Millions of ModeLine's..]
    (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.5.3, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (==) fglrx(0): NoAccel = NO
    (II) Loading sub module "xaa"
    (II) LoadModule: "xaa"
    (II) Loading /usr/lib/xorg/modules//libxaa.so
    (II) Module xaa: vendor="X.Org Foundation"
    compiled for 1.5.3, module version = 1.2.0
    ABI class: X.Org Video Driver, version 4.1
    (**) fglrx(0): NoDRI = NO
    (II) Loading sub module "fglrxdrm"
    (II) LoadModule: "fglrxdrm"
    (II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
    (==) fglrx(0): Capabilities: 0x00000000
    (==) fglrx(0): CapabilitiesEx: 0x00000000
    (==) fglrx(0): cpuFlags: 0x8000001d
    (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    (**) fglrx(0): Ring buffer size: 8 MB
    (**) fglrx(0): KernelModuleParm: "agplock=0"
    (II) fglrx(0): [pcie] 262144 kB allocated
    (II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
    (==) fglrx(0): UseFastTLS=0
    (==) fglrx(0): BlockSignalsOnLock=1
    (II) fglrx(0): Direct rendering enabled
    (II) fglrx(0): AC Adapter is used
    (II) fglrx(0): Interrupt handler installed at IRQ 16.
    (II) fglrx(0): Exposed events to the /proc interface
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
    (II) fglrx(0): detected X.org 7.4.3.0
    (II) Loading extension ATIFGLRXDRI
    (II) fglrx(0): doing DRIScreenInit
    (II) fglrx(0): DRIScreenInit for fglrx driver
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 13, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 13, (OK)
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 13, (OK)
    drmOpenByBusid: drmOpenMinor returns 13
    drmOpenByBusid: drmGetBusid reports PCI:1:0:0
    (II) fglrx(0): [drm] DRM interface version 1.0
    (II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
    (II) fglrx(0): [drm] added 8192 byte SAREA at 0x4d000
    (II) fglrx(0): [drm] mapped SAREA 0x4d000 to 0xb7af0000
    (II) fglrx(0): [drm] framebuffer handle = 0x4e000
    (II) fglrx(0): [drm] added 1 reserved context for kernel
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0): Name: fglrx
    (II) fglrx(0): Version: 8.56.4
    (II) fglrx(0): Date: Dec 1 2008
    (II) fglrx(0): Desc: ATI FireGL DRM kernel module
    (II) fglrx(0): Kernel Module version matches driver.
    (II) fglrx(0): Kernel Module Build Time Information:
    (II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.27-ARCH
    (II) fglrx(0): Build-Kernel MODVERSIONS: no
    (II) fglrx(0): Build-Kernel __SMP__: no
    (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
    (II) fglrx(0): [drm] register handle = 0x0004f000
    (II) fglrx(0): DRI initialization successfull!
    (II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01004000
    (II) fglrx(0): FBMM initialized for area (0,0)-(1280,3280)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 1280 x 2256
    (==) fglrx(0): Backing store disabled
    (II) Loading extension FGLRXEXTENSION
    (II) Loading extension ATITVOUT
    (**) fglrx(0): DPMS enabled
    (**) fglrx(0): Textured Video is enabled.
    (II) LoadModule: "glesx"
    (II) Loading /usr/lib/xorg/modules//glesx.so
    (II) Module glesx: vendor="X.Org Foundation"
    compiled for 1.4.99.906, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension GLESX
    (II) fglrx(0): GLESX enableFlags = 80
    (II) fglrx(0): GLESX is enabled
    (**) fglrx(0): Option "XaaNoOffscreenPixmaps" "true"
    (II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
    Screen to screen bit blits
    Solid filled rectangles
    8x8 mono pattern filled rectangles
    Solid Lines
    Dashed Lines
    Setting up tile and stipple cache:
    32 128x128 slots
    14 256x256 slots
    5 512x512 slots
    (II) fglrx(0): Acceleration enabled
    (II) LoadModule: "amdxmm"
    (II) Loading /usr/lib/xorg/modules//amdxmm.so
    (II) Module amdxmm: vendor="X.Org Foundation"
    compiled for 1.4.99.906, module version = 1.0.0
    ABI class: X.Org Server Extension, version 1.1
    (WW) fglrx(0): Option "AccelMethod" is not used
    (WW) fglrx(0): Option "AccelDFS" is not used
    (WW) fglrx(0): Option "GARTSize" is not used
    (WW) fglrx(0): Option "BufferSize" is not used
    (WW) fglrx(0): Option "UseFBDev" is not used
    (WW) fglrx(0): Option "ColorTiling" is not used
    (WW) fglrx(0): Option "RenderAccel" is not used
    (WW) fglrx(0): Option "SubPixelOrder" is not used
    (WW) fglrx(0): Option "DynamicClocks" is not used
    (WW) fglrx(0): Option "PCI:1:0:0" is not used
    (II) fglrx(0): X context handle = 0x1
    (II) fglrx(0): [DRI] installation complete
    (==) fglrx(0): Silken mouse enabled
    (==) fglrx(0): Using hardware cursor
    (==) RandR enabled
    (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 SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (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
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 14, (OK)
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 14, (OK)
    drmOpenByBusid: drmOpenMinor returns 14
    drmOpenByBusid: drmGetBusid reports PCI:1:0:0
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0
    (II) fglrx(0): Shutdown CMMQS
    (II) fglrx(0): [drm] removed 1 reserved context for kernel
    (II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x4d000 at 0xb7af0000
    Thanks :)
    edit: weird thing (or not) but DPMS (or whatever it is, the thing that turns off my monitor after some time) seems to work, altough moving the mouse or pressing the keyboard doesn't wake up the screen. Has this something to do with my mouse and keyboard not being recognized by xorg ?
    edit2: omg yes it is ! I added:
    urxvtc -e 'screen'
    so when I startx an un-window-managered fullscreen terminal launches with a screen session, and if I ssh on it I can type in this terminal from another computer, and the screen actually displays what I'm typing, so that's definitely an input problem !
    Final Edit: Well all solved, concerning the "frozen" stuff, it was just that my keyboard and mouse weren't detected because of the new hotpulg thingy (check http://wiki.archlinux.org/index.php/Xor … otplugging for more info, or just add 'hal' to your rc.conf), then restored my original xorg.conf, rebooted and it all went back to normal (: ). Hope this helps.
    Last edited by arsenist (2008-12-13 03:28:42)

    Has this something to do with my mouse and keyboard not being recognized by xorg
    Hmm, I wonder what it would reveal if someone read the news? http://www.archlinux.org/news/424/
    Even your Xorg.0.log is telling you the problem.
    (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
    (WW) Disabling Keyboard0
    (WW) Disabling PS/2 Mouse
    Last edited by jacko (2008-12-13 03:28:40)

  • Screen display garbled when downloading a file

    In FF 5 I often get a garbled screen display when dowloading a file (by garbled I mean that the display is broken into numerous rectangles; the display appears to be similar to that of a driver/monitor/card not being compatible). The display will sometimes correct itself if I minimize and then maximize FF, but not always.
    The problem does not occur in IE, Opera, Safari, Chrome, nor in any other program.
    Could a plugin possibly be the cause? I can work around the problem simply by not using FF for downloads, but I wanted to pass along the information if it might be a bug in FF5.
    Here is a screenshot: http://firstimpressions.websitedesigningamarillo.com/firefoxscreenshotcropped.jpg

    Thanks for the info! Yea, I thought my video card was dying when I first saw it. The driver is the latest, and everything else looks ok too.
    Over the past couple of hours I disabled all plug-ins and extensions, and still had the problem. I chose to down-grade to verison 4 which now works fine. Version 3 was also a good choice but I use the HTML validator that requires version 4 (world's absolute best add-on ever for my use).
    I'm guessing that my video card isn't playing nice with FF5, so until I upgrade the card I will stick with FF4. I installed a new theme and now I'm happier than ever with FF. :)

  • Has anyone got the screen flick problem solved?

    as above thanks.
    (i am starting to get irritated of the flicking screen)

    finally got my computer back with more problems than I sent it in with I think. They put in a new logic board, battery, and super drive. I no longer can see my serial number in the about this mac window. also, the battery is loose and sometimes the meter reads 0% and sometimes it will not turn on. I dont know what the deal is. The people that fixed it are in the middle of selling the store so I dont feel like deeling with them for a while until they get all moved. I might just call applecare in the morning or something. I hate this, I am having the worst luck with all my electronics lately.

  • Does anyone know why- when I iport a one minute video project into Final Cut X from I Movie the resolution that looked alright in IMovie full screen becomes worst in final cut, full screen...but clear when it is in still position?

    Does anyone know why- when I import a one minute video project into Final Cut X from I Movie the resolution that looked alright full screen in I Movie instantly becomes worst on full screen in Final Cut X...but clear again when I stop it to still position?

    I'm new to video editing but I think I recall seeing an option in FCPX which lets you choose the video quality for the preview window. I think the window reduces the quality when playing back for performance reasons and so perhaps that is why it seems to have less quality when moved over to FCPX? Just a possibility, I'm sure one of the more experienced users can confirm or deny this theory.

  • Log & Capture Screen not opening and Final Cut Pro just quits! HELP!

    Hi everyone,
    I've been searching through the forums and reading up on similar issues but to no avail my problem still exists and I'm about to put a hammer to my computer. I have a G5 Mac at work and use my G4 for home use. Earlier today I was at work and was capturing my footage perfect using my Canon XH A1 using firewire and everything went well. Later on in the day when working on my G4, using the same settings and equipment from earlier, when I hit apple+8 it shows that the program is understanding my command but after a min without a screen appearing, final cut pro just quits. Now I've tried everything from deleting my preferences, final cut user data, you name it and I've tried yet still not able to get the screen to capture. I've even tried switching the firewire port just in case its a bad connection and still nothing. Can someone help me out so my computer can live to see another day.
    Thank You
    Message was edited by: Jason81

    You updated to 10.5?
    What FCP 5 version are you running -5.0 or 5.1?
    You need 5.1 if you have Mac OS X 10.5.
    Also, get rid of the Norton AV -it's a terrible resource hog and interferes with everything.
    I would go as far as to suggest Norton is trying to check the incoming data from your video capture.
    Turn it off at least, and see if there is any improvement.
    If you must use AV to avoid passing something to Windows users, get a free copy of ClamXav. It can be set to check only incoming stuff like Mail and downloads. Has a very small footprint and is only active when it should be. I use ClamXav myself as I often deal with FTP transfers.

  • Grey screen after update (Solved)

    I solved this one myself eventually, but it took several hours.
    After updating one of the MacBook Pros in my office, the computer was stuck at the grey screeb (Apple Logo and spinning wheel) and would not progress.
    1) First I rebooted the computer (no luck)
    2) Then I booted from an install DVD and checked for errors (no errors reported)
    3) Then I did a "repair permissions", which did find and repair some permissions
    3a) Then I repeated the "verify disk" which again reported no errors.
    4) Then I rebooted in safe mode, but it still would not progress past the grey screen.
    5) Then I rebooted in verbose mode, and saw the error that LoginWindow was crashing.
    6) I rebooted in Single User Mode, since I am familiar with Unix and Linux.
    I looked in the /Library/Logs/CrashReporter/ folder, and there were a LOT of files with loginwindow-timestamp-computername.dump where timestamp is the date/time of the crash and computername is the name of the computer.
    The most recent of these reports that a library /usr/lib/libbz2.1.0.dylib is missing.
    I looked on a different MacBook Pro, and behold ls -l tells me that libbz2.1.0.dylib should be a symbolic link to libbz2.1.0.5.dylib (the newer file DOES exist on the machine that will not boot)
    The following steps will be "scary" for anyone not familiar with Unix / Linux command line, but they resulted in the computer booting
    mount -w /
    (remount the hard disk with write permissions)
    cd /usr/lib
    (change to the folder with the missing file pointer)
    ln -s libbz2.1.0.5.dylib libbz2.1.0.dylib
    (create the missing symbolic link)
    reboot
    (command to restart the computer)
    and IT WORKED
    The computer in question is now working, and reports that it is running version 10.5.8

    Hello,
    I've had this problem twice, and each occurred after a security update.
    What helped me was the following:
    -Take out your powercord and your battery. Press the power button for about 5 seconds.
    -Then, insert your battery and powercord, start the computer, and hold down AppleCTRL+PR.
    From what I understand, one of these two steps resets the power management system on the macbook.
    After you perform these two steps, your computer may still hang at the grey screen with the apple logo. However! Let it hang for about 5-10 minutes and it will automatically restart, and boot properly.
    You can also try calling Apple support on your friend's behalf ... they were more than helpful.
    Blackbook Core Duo   Mac OS X (10.4.9)  

  • How It Was Fixed (Possible Software Bug Not Hardware): Getting the iMac Screen/Menus Garbled and/or Yellow Circle Before Getting Into Finder Issues?

    Hi. Possible fix done to my late- 2009 iMac's screen/graphics issue that may work God willing, hopefully for most [In my case it sometimes had that yellow circle that appears before it goes to the Finder but mostly it was a messed up desktop and menus (unreadable mostly) after months, prayers and weeks of fixing it; recommended to be read entirely first coz' it's a bit complicated (like a lot of subplots). If uncomfortable to try coz' it involved a GPU stress test, contact your authorized Apple service center for their advice]. I had an iMac (late 2009) screen garbling a few hours ago (was weeks ago when it resurfaced until it got worse that it's at every boot on Mavericks):
    †        I booted to Snow Leopard USB external (my back-up OS) drive then run the first    person shooter at redeclipse.net. I set everything to max, including the display, resolution and graphics setting with fullscreen and v-sync on. I then refreshed it which brought it back to normal (I then tested it's stability with GPUTest 0.7 with Furmark for 15 minutes). * if the display options have been set to max before, bring it back to the default then refresh and then max it again Possibly any games that's has the graphic settings (or more advanced) of Red Eclipse could work (other free ones are Xonotic and Open Arena which are based on Quake 1 or 3s engine I believe).
    Optional but not recommended (have warrantied if that's still available or have it repaired at authorized service centers):
    If that doesn't work, review articles and videos on how to open an Intel iMac and get an iPhone/iPad/another way to get to the 'net ready for research (I opened mine very carefully on the right side with a cutter with blade extended far prying it carefully then I inserted a flat end, sturdy plastic used for mixing epoxy then removed the cutter carefully to let the plastic mixing tool do the prying) to see if the cable connected to the logicboard which is on top of, is connected (mine was detached but I'm not sure if the adjusting and tilting of the screen overtime for 2 & 1/2 years, detached it) then do † above again.
    It could to be a software problem, a possible Apple ATI driver bug that takes overtime to surface (2 1/2 years it resurfaced because this started in my case after upgrading to Lion when Apple coded things mostly from the ground up. Snow Leopard didn't have this problem). 
    Thank you for your time. Have a great upcoming sunday mass/great upcoming weekend. I hope this helps.
    God bless, Rev. 21:4, Matt. 16:18

    Does an external display also act in a similar manner as the internal one?
    Some earlier Intel-based iMacs had graphic processor card issues; not sure what
    the symptoms of the majority of them were, but some had odd patterns, others
    went black, and some would range from OK to totally unusable. Among others.
    So there is a chance the graphic processor may be going out; or just the circuitry
    that controls the backlight. An inverter may be weak or other circuit to the display
    could be wearing out.
    http://www.apple.com/retail/geniusbar/
    If you have access to an Apple Store with Genius bar, they can perform some kinds
    of diagnostic tests there even though the computer is out-of-warranty; that may be
    of help to narrow down the cause of the symptoms you've noticed. They may not be
    able to repair it, however, at an Apple Store; as it is rather old by today's standard.
    An Apple Authorized Service Provider could do repairs and testing on older models
    the Apple Store's Genius and other may not be set up to handle due to vintage.
    Find an Apple Authorized Service Provider
    Visit an Apple Retail Store
    There is a country locator page to help find either of the above in regions outside
    of the US & Canada, not sure how the above links would work; and it appears my
    bookmarks to the country locator page may not be accessible now to post here.
    You may be able to get an idea about what kinds of parts support the display
    function by name by looking into an iFixit.com repair guide for your iMac series.
    Hopefully the parts supporting the display are the reason it is dimming down, as
    a graphic processor failure likely would exhibit other behaviors than just dimming.
    PS: I see you've added content to your thread after I'd started working on this
    & the answer likely is a hardware repair; professional testing is worth the time
    and you seem to have at least one other thread on the same topic....
    Good luck & happy computing!
    edited 2x

  • Screen capture blurry in final cut, but not Motion

    I screen captured something from the internet using snapz pro (I tried DV-ntsc, h.264, and now using 'none'). It looks great when its motion, but after render, looks bad in final cut. I tried bringing the file into motion and then exporting a loss-less from there and then bringing into final cut, but its the same problem of being blurry.
    the video was captured 4x3, though its larger than 720x480. Thats one of the reasons I threw it into Motion, because it would standardize the size in the case that final cut didnt like it. I need to get rid of the blur. help.
    eric

    Also, if your file is LARGER in Motion, as you said, and then you drop it into a DV sequence, not only will it shrink, but it will inherit the DV 5:1 compression.
    What size are you using in Motion? What settings? If you want it to look that good in FCP, you need to use the same settings in FCP. If you are adding it to a DV sequence, then you will have to live with the DV compression. OR, try it in a DV50 sequence. Better compression, higher bit rate.
    Shane

  • Multiple Color Screens in iMovie or Final Cut Pro?

    So I am doing some video editing for a project at school. I am using a green screen as a background. I wrapped some things in blue duct-tape in order to blue-screen them. Is there anyway I can use both a blue screen and a green screen in one clip? I have iMovie and Final Cut Pro. I am new to Final Cut Pro so I am not 100% sure about all of its features. If these programs cannot, are there any movie editing programs that do? Thanks for your time. My goal is to have a green screened background while blue screening fake swords and stuff to make them look "light-sabery".

    does your hardware fullfill the min. specs. for any of both apps...?
    and, why not FCE4 .. 199$?
    socalled Ken Burns Effect/KB is done more intutive (=convenient) in iM.. have a look: http://www.apple.com/ilife/tutorials/#imovie-making-29
    soundtracks.. 'options' are limited in iM08, but as owner of iM08 you're allowed a free download of iMHD6.. which offers 2.5 audio tracks..
    zoom-in is part of KB..
    fade=transition .. iM08, iMHD6, FCP/E...
    +mix video with a still in one corner or vica versa+ no in iMHD6, yepp in iM08, for sure in FCE/P
    what is your delivery media...? DVD quality is in iM08 less than in others apps.. therefor, integration into .mac is in iM08 better..
    consider usage of a 3rd party, specialized app as Photo2Movie or PhotoMagico..

  • Why did my title screens disappear after I finalized the movie?

    I added a title screen to the begining and the end of my movie.  I added them as a sepreate clip.  Why did they not show up after I finalized the video?  Please help. I'm using imove 11.

    Hi
    • Free space on Start-Up (Mac OS) Hard Disk. How much ?
    (others do not count - at all)
    Yours Bengt W

  • Contacts app not on my home screen how to solve, Contacts app not on my home screen how to solve

    Contacts app is not on my newly purchased 4s iPhone home screen. Why? And please how do I resolve this? Thanks in anticipation!

    You can move it where ever you want it. By default, it's in the Utilites folder. Tap and hold the icon until it starts to wiggle then drag it to where you want it.

Maybe you are looking for

  • How to add a second wireless network in my house..

    Hello, I have Verizon FIOS with the supplied Actiontec wireless modem/router M1424WR. This current setup works perfectly and has since I got it about 5 months ago. Note that all of my computers connect wirelessly. Here is what I would like to do and

  • IDevices Periodically Lose Connection to iTunes Server

    Periodically, our Apple TVs and iOS devices seem to lose "knowledge" of our iTunes server.  This has worked fairly reliably in the past, but seems more problematic now (I'm not sure if this is due to Yosemite or some other update).  There have been n

  • Possible to overwrite parse method in DOM with SAX Handler?

    Hi, Is it possible to overwrite the parse method within DOM? What a want to do is:      private Node parseXml( String text ) throws SAXParseException, SAXException, IOException, ParserConfigurationException           SAXParserFactory factory = SAXPar

  • [JS] (CS2) (CS3) Test for container

    Hello, I would like to make sure that whatever I have selected (app.selection) is the container and NOT the content, regardless of what the selection is (Item or Text). I know if you have multiple selections, you can only have objects and that is fin

  • How can I get the Task information..? Remedy for error "-200089"

    Hello, I am using PCI-6229 for the application, and VB6 for application development. We have a policy to create the tasks and associated channels using Measurement and Automation Explorer. I want to know can I retrieve the information of the tasks th