ATI Linux Driver Beta testers

Well good news for ATI users, ATI is activly seeking people to help beta test linux CATALYST drivers....
Here is a link to find out more info and fill out an app
ATI linux Driver Beta tester info
forgot here is the link to get the app make sure if you e-mail it to use LINUX in the subject line
Application
Never mind the powered by part

maybe i wont have to use my nvidia TNT2 any more now...

Similar Messages

  • I need a few beta testers

    I have the title creation macro working.
    This macro is run from a Microsoft Word document. I wrote it on Office 2003 but it should work on newer versions. It runs on 2003 because I have the compatibility pack.
    Here is how it works:
    You create a title in Premiere Pro using the font and positioning that you want to use. Get it just right. (One line of text only though.)
    Change the text of the title to "xyz" without the quotes.
    Export the title as a title. (*.prtl)
    Open the MS Word document and either type in the text you want to use or paste it in from another document.
    I limited it to 9999 titles but I doubt that will inconvenience anyone. (I actually only tested it to 9990). That many titles takes quite a while though. (55 minutes) Heck, it takes quite a while to import that many into Premiere Pro for that matter.
    Once you have the text in place (make sure that there isn't a blank line at the end or you will get an empty title), you just double-click where it says to double-click.
    It will ask you which is the master file you want to make copies of. Then it will ask you for the file name and location you want to use for the copies. It will append the numbers 0001 through 9999
    Then it proceeds to make your copies using each line of text for a new title.
    When it is finished, just import the titles into Premiere Pro and drag drop to the timeline. Or automate to sequence.
    Deceptively simple. I didn't write much of the code. I understand it, but only after studying what was kindly given to me by a master VBA guy on a VBA forum. Kind of like if you were a newbie around here and Jim Simon or Ann Bens offered to edit your video for you after you asked a question. It was phenomenal. Although it might have been more like what I did for the people I created intros for. Not sure just how much effort he had to put into it. But it sure works great and the code is simple, and clean.
    OK? So now I need a few beta testers before I just throw it out there to the world of Premiere Pro users. If you would like to take it for a test drive, let me know in this thread.
    If you are concerned about letting a macro run on your system, prevent it from running and just read the text from the Visual Basic Editor yourself. You will see that it doesn't do anything sinister.Then allow it the next time.
    Just do me one favor. If you change the code to make it better, please share it with everyone.
    Thanks,
    Steven Gotz
    http://www.stevengotz.com

    Really? 272 views of this post at the time I write this and nobody wants to create multiple titles based on a single title using text from an external program?
    Wow!
    We see the question all the time, and yet nobody wants to try it out?
    OK. I will just wait until somebody asks again and offer the untested solution. Seriously, this is not the response I expected. Not after years of seeing requests for this feature.

  • Linux-Driver Feedback

    Hello!
    I am working on an embedded linux box targeted for measuring data and presenting the stuff over the web -> acting as webserver.
    We had several problems with the Linux-Version of niDAQmx-base and nivisia, I hope those can be fixed in the next version of the Linux-Driver package:
    * NVISIA is based on those ugly automatic installers, which are completly useless of you do not use an RPM based distribution (common on embedded systems).
    * even the C-only drivers link against libX11, libXext and liblvmesa - whats this? On many systems those libraries are not present at all - and many computers measuring do not even have a CRT.
    * No error messages at all (grrr!!!): If you use e.g. daqlistdevices you do not get any error - it just does not find any devices. It seems it does load libX11 or some libraries like that at runtime - and does not print out any error messages at all - even the /tmp/blabla-error files are empty.
    We use it conjunction with nivisia, no errors - never.
    Not even a single line - thats not funny!!
    Conclusion: We needed about 3 days to get our USB-6008 to work, with hours of studying strace-logs (shows syscalls made by application). 3 Days!! With better error messages and maybe distribution-independent packages this could have been done in 2 hourse.
    The current software package looks more like a "hey buy NI stuff - we have linux support"...
    Please fix this, lg Clemens Eisserer
    PS: However to not only complain about issues, the idea to use usbdevfs is really great!Message Edited by Linuxhippy on 04-11-2005 02:13 AM
    Message Edited by Linuxhippy on 04-11-2005 02:14 AM
    Message Edited by Linuxhippy on 04-11-2005 02:15 AM

    * Its not possible to use the c-interface
    as through JNI library with Java.
    I normally created a shared-library exposing some features to the java-world, but as soon as I linked this shared-library (linking was enough, even if nothing of was used) java really crashed hard at startup.
    I wasn't even able to kill it with "kill -15", I really had to terminate it hard.
    I do not know exactly where this comes from, but I assume it is nut possible to load any shared libaries that link to the c-interface at runtime - I do not know wether this is threading-dependent or not.
    waw - this all is just crap!

  • I cannot use the managed driver beta on Mono

    Managed driver beta has been released. However, I cannot use it on Mono, which is a Dot Net Environment on Linux.
    The fata exception is type load fail...
    So I want to know what else dll the managed driver depends.
    Look forward for your reply.
    Mikes

    Mono isn't supported by the beta nor will it be supported in the first production release. Oracle will consider supporting Mono in a release after the first production release.

  • ATI display driver rollback

    I have desktop running Enterprise Linux server 2.6.18-164. Recently I installed ATI display driver on it. After that I am not able to restart my machine. Is there any way to roll back the recent driver changes???

    You can try to boot in text mode (no graphics) and check /etc/X11 directory. Usually, whenever a change in graphics settings occurs, the system makes a backup of the original configuration file (xorg.conf) and then applies the new settings. So, you can try to replace the current configuration file (xorg.conf) with the old one (xorg.conf.backup), if it exists...
    kido

  • [SOLVED] ATI Catalyst Driver Issues

    I'm sure issues with these drivers get posted often, but I'm honestly not entirely sure how to search for this.  I installed the base system with no issues, but when it came to adding a DE, I had some issues.  I tried several times to install the catalyst drivers for my radeon hd 6800.  I installed from the official repository using:
    #pacman -S catalyst-dkms catalyst-utils
    I had no luck starting X server after that so I tried installing from Vi0l0's unnoficial repository.  This caused X Server to seg fault every time I attempted to start it. 
    I'm a little confused on how I am even using gnome at this point considering I have not successfully installed a graphics driver.
    I blacklisted radeon and uninstalled catalyst and somehow was able to start X Server.  I'm obviously using a lame driver considering every time I move a console window around it moves at around 2 FPS. 
    How can I successfully install the proprietary fglrx/catalyst drivers?
    Last edited by instantaphex (2012-12-10 04:49:49)

    Thanks for the replies.  It's been a busy week and I have to move my desktop into the kitchen to get internet access because I'm also having ndiswrapper issues.  Here is my Xorg.0.log
    [ 6.208]
    X.Org X Server 1.13.0
    Release Date: 2012-09-05
    [ 6.208] X Protocol Version 11, Revision 0
    [ 6.208] Build Operating System: Linux 3.6.3-1-ARCH x86_64
    [ 6.209] Current Operating System: Linux archbox 3.6.9-1-ARCH #1 SMP PREEMPT Tue Dec 4 08:04:10 CET 2012 x86_64
    [ 6.209] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=8c2fca85-5d82-4e80-9492-3ffe9e0760e5 ro quiet
    [ 6.209] Build Date: 08 November 2012 07:09:29PM
    [ 6.209]
    [ 6.209] Current version of pixman: 0.28.0
    [ 6.209] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 6.209] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 6.209] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 9 06:53:08 2012
    [ 6.231] (==) Using config file: "/etc/X11/xorg.conf"
    [ 6.231] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 6.233] (==) ServerLayout "aticonfig Layout"
    [ 6.233] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
    [ 6.233] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
    [ 6.233] (**) | |-->Device "aticonfig-Device[0]-0"
    [ 6.233] (==) Automatically adding devices
    [ 6.233] (==) Automatically enabling devices
    [ 6.233] (==) Automatically adding GPU devices
    [ 6.246] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 6.246] Entry deleted from font path.
    [ 6.266] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 6.266] Entry deleted from font path.
    [ 6.266] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 6.267] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 6.267] Entry deleted from font path.
    [ 6.267] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 6.267] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 6.267] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 6.267] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 6.267] (II) Loader magic: 0x7fcc40
    [ 6.267] (II) Module ABI versions:
    [ 6.267] X.Org ANSI C Emulation: 0.4
    [ 6.267] X.Org Video Driver: 13.1
    [ 6.267] X.Org XInput driver : 18.0
    [ 6.267] X.Org Server Extension : 7.0
    [ 6.270] (--) PCI:*(0:1:0:0) 1002:6739:174b:174b rev 0, Mem @ 0xd0000000/268435456, 0xfd5c0000/131072, I/O @ 0x0000ce00/256, BIOS @ 0x????????/131072
    [ 6.270] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 6.270] Initializing built-in extension Generic Event Extension
    [ 6.270] Initializing built-in extension SHAPE
    [ 6.270] Initializing built-in extension MIT-SHM
    [ 6.270] Initializing built-in extension XInputExtension
    [ 6.270] Initializing built-in extension XTEST
    [ 6.270] Initializing built-in extension BIG-REQUESTS
    [ 6.271] Initializing built-in extension SYNC
    [ 6.271] Initializing built-in extension XKEYBOARD
    [ 6.271] Initializing built-in extension XC-MISC
    [ 6.271] Initializing built-in extension SECURITY
    [ 6.271] Initializing built-in extension XINERAMA
    [ 6.271] Initializing built-in extension XFIXES
    [ 6.271] Initializing built-in extension RENDER
    [ 6.271] Initializing built-in extension RANDR
    [ 6.271] Initializing built-in extension COMPOSITE
    [ 6.271] Initializing built-in extension DAMAGE
    [ 6.271] Initializing built-in extension MIT-SCREEN-SAVER
    [ 6.271] Initializing built-in extension DOUBLE-BUFFER
    [ 6.271] Initializing built-in extension RECORD
    [ 6.271] Initializing built-in extension DPMS
    [ 6.271] Initializing built-in extension X-Resource
    [ 6.271] Initializing built-in extension XVideo
    [ 6.271] Initializing built-in extension XVideo-MotionCompensation
    [ 6.271] Initializing built-in extension XFree86-VidModeExtension
    [ 6.271] Initializing built-in extension XFree86-DGA
    [ 6.271] Initializing built-in extension XFree86-DRI
    [ 6.271] Initializing built-in extension DRI2
    [ 6.271] (II) "glx" will be loaded by default.
    [ 6.271] (II) LoadModule: "glx"
    [ 6.307] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 6.325] (II) Module glx: vendor="Advanced Micro Devices, Inc."
    [ 6.325] compiled for 6.9.0, module version = 1.0.0
    [ 6.326] Loading extension GLX
    [ 6.326] (II) LoadModule: "fglrx"
    [ 6.326] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
    [ 6.497] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
    [ 6.498] compiled for 1.4.99.906, module version = 9.0.2
    [ 6.498] Module class: X.Org Video Driver
    [ 6.499] (II) Loading sub module "fglrxdrm"
    [ 6.499] (II) LoadModule: "fglrxdrm"
    [ 6.499] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 6.513] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 6.513] compiled for 1.4.99.906, module version = 9.0.2
    [ 6.513] (II) AMD Proprietary Linux Driver Version Identifier:9.00.2
    [ 6.513] (II) AMD Proprietary Linux Driver Release Identifier: 9.00.11
    [ 6.513] (II) AMD Proprietary Linux Driver Build Date: Sep 20 2012 11:56:16
    [ 6.513] (++) using VT number 1
    [ 6.513] (WW) Falling back to old probe method for fglrx
    [ 6.541] (II) Loading PCS database from /etc/ati/amdpcsdb /etc/ati/amdpcsdb.default
    [ 6.555] ukiDynamicMajor: failed to open /proc/ati/major
    [ 6.555] ukiDynamicMajor: failed to open /proc/ati/major
    [ 6.569] (--) Chipset Supported AMD Graphics Processor (0x6739) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:0:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:2:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:4:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:9:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:10:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:0) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:2) found
    [ 6.576] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
    [ 6.577] (II) AMD Video driver is running on a device belonging to a group targeted for this release
    [ 6.577] (II) AMD Video driver is signed
    [ 6.577] (II) fglrx(0): pEnt->device->identifier=0x1cfb770
    [ 6.578] (II) fglrx(0): === [xdl_xs113_atiddxPreInit] === begin
    [ 6.578] (II) Loading sub module "vgahw"
    [ 6.578] (II) LoadModule: "vgahw"
    [ 6.578] (II) Loading /usr/lib/xorg/modules/libvgahw.so
    [ 6.591] (II) Module vgahw: vendor="X.Org Foundation"
    [ 6.591] compiled for 1.13.0, module version = 0.1.0
    [ 6.591] ABI class: X.Org Video Driver, version 13.1
    [ 6.591] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    [ 6.591] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 6.591] (==) fglrx(0): Default visual is TrueColor
    [ 6.591] (**) fglrx(0): Option "DPMS" "true"
    [ 6.592] (==) fglrx(0): RGB weight 888
    [ 6.592] (II) fglrx(0): Using 8 bits per RGB
    [ 6.592] (==) fglrx(0): Buffer Tiling is ON
    [ 6.592] (II) Loading sub module "fglrxdrm"
    [ 6.592] (II) LoadModule: "fglrxdrm"
    [ 6.592] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 6.592] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 6.592] compiled for 1.4.99.906, module version = 9.0.2
    [ 6.596] ukiDynamicMajor: failed to open /proc/ati/major
    [ 6.596] ukiDynamicMajor: failed to open /proc/ati/major
    [ 6.596] (**) fglrx(0): NoAccel = NO
    [ 6.596] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
    [ 6.596] (--) fglrx(0): Chipset: "AMD Radeon HD 6800 Series " (Chipset = 0x6739)
    [ 6.596] (--) fglrx(0): (PciSubVendor = 0x174b, PciSubDevice = 0x174b)
    [ 6.596] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
    [ 6.596] (--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
    [ 6.596] (--) fglrx(0): MMIO registers at 0xfd5c0000
    [ 6.596] (--) fglrx(0): I/O port at 0x0000ce00
    [ 6.596] (==) fglrx(0): ROM-BIOS at 0x000c0000
    [ 6.619] (II) fglrx(0): Primary V_BIOS segment is: 0xc000
    [ 6.621] (II) Loading sub module "vbe"
    [ 6.621] (II) LoadModule: "vbe"
    [ 6.621] (II) Loading /usr/lib/xorg/modules/libvbe.so
    [ 6.622] (II) Module vbe: vendor="X.Org Foundation"
    [ 6.622] compiled for 1.13.0, module version = 1.1.0
    [ 6.622] ABI class: X.Org Video Driver, version 13.1
    [ 6.622] (II) fglrx(0): VESA BIOS detected
    [ 6.622] (II) fglrx(0): VESA VBE Version 3.0
    [ 6.622] (II) fglrx(0): VESA VBE Total Mem: 16384 kB
    [ 6.622] (II) fglrx(0): VESA VBE OEM: AMD ATOMBIOS
    [ 6.622] (II) fglrx(0): VESA VBE OEM Software Rev: 13.12
    [ 6.622] (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2010, AMD Technologies Inc.
    [ 6.622] (II) fglrx(0): VESA VBE OEM Product: BARTS
    [ 6.622] (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
    [ 6.662] (II) fglrx(0): AMD Video BIOS revision 9 or later detected
    [ 6.662] (--) fglrx(0): Video RAM: 1048576 kByte, Type: GDDR5
    [ 6.662] (II) fglrx(0): PCIE card detected
    [ 6.662] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
    [ 6.662] (WW) fglrx(0): board is an unknown third party board, chipset is supported
    [ 6.662] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x40000000)
    [ 6.662] (EE) fglrx(0): Fail to init MGPU configuration:0x0!
    [ 6.662] (II) fglrx(0): RandR 1.2 support is enabled!
    [ 6.662] (II) fglrx(0): RandR 1.2 rotation support is enabled!
    [ 6.662] (==) fglrx(0): Center Mode is disabled
    [ 6.662] (II) Loading sub module "fb"
    [ 6.662] (II) LoadModule: "fb"
    [ 6.662] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 6.663] (II) Module fb: vendor="X.Org Foundation"
    [ 6.663] compiled for 1.13.0, module version = 1.0.0
    [ 6.663] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 6.663] (II) Loading sub module "ddc"
    [ 6.663] (II) LoadModule: "ddc"
    [ 6.663] (II) Module "ddc" already built-in
    [ 6.783] (EE) fglrx(0): ASYNCIO service has not started yet while register message handler for DAL
    [ 6.785] (II) fglrx(0): Output DFP1 using monitor section aticonfig-Monitor[0]-0
    [ 6.785] (II) fglrx(0): Output DFP2 has no monitor section
    [ 6.785] (II) fglrx(0): Output DFP3 has no monitor section
    [ 6.785] (II) fglrx(0): Output DFP4 has no monitor section
    [ 6.785] (II) fglrx(0): Output DFP5 has no monitor section
    [ 6.785] (II) fglrx(0): Output DFP6 has no monitor section
    [ 6.785] (II) fglrx(0): Output DFP7 has no monitor section
    [ 6.785] (II) fglrx(0): Output CRT1 has no monitor section
    [ 6.785] (II) Loading sub module "ddc"
    [ 6.785] (II) LoadModule: "ddc"
    [ 6.785] (II) Module "ddc" already built-in
    [ 6.785] (II) fglrx(0): Connected Display0: CRT1
    [ 6.785] (II) fglrx(0): Display0: Failed to get EDID information.
    [ 6.785] (II) fglrx(0): EDID for output DFP1
    [ 6.785] (II) fglrx(0): EDID for output DFP2
    [ 6.785] (II) fglrx(0): EDID for output DFP3
    [ 6.785] (II) fglrx(0): EDID for output DFP4
    [ 6.785] (II) fglrx(0): EDID for output DFP5
    [ 6.785] (II) fglrx(0): EDID for output DFP6
    [ 6.785] (II) fglrx(0): EDID for output DFP7
    [ 6.785] (II) fglrx(0): EDID for output CRT1
    [ 6.785] (II) fglrx(0): Manufacturer: ACR Model: 53 Serial#: 2456821854
    [ 6.785] (II) fglrx(0): Year: 2009 Week: 27
    [ 6.785] (II) fglrx(0): EDID Version: 1.3
    [ 6.785] (II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    [ 6.785] (II) fglrx(0): Sync: Separate
    [ 6.786] (II) fglrx(0): Max Image Size [cm]: horiz.: 34 vert.: 27
    [ 6.786] (II) fglrx(0): Gamma: 2.20
    [ 6.786] (II) fglrx(0): DPMS capabilities: StandBy Suspend; RGB/Color Display
    [ 6.786] (II) fglrx(0): First detailed timing is preferred mode
    [ 6.786] (II) fglrx(0): redX: 0.648 redY: 0.339 greenX: 0.292 greenY: 0.603
    [ 6.786] (II) fglrx(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 6.786] (II) fglrx(0): Supported established timings:
    [ 6.786] (II) fglrx(0): 720x400@70Hz
    [ 6.786] (II) fglrx(0): 640x480@60Hz
    [ 6.786] (II) fglrx(0): 640x480@67Hz
    [ 6.786] (II) fglrx(0): 640x480@72Hz
    [ 6.786] (II) fglrx(0): 640x480@75Hz
    [ 6.786] (II) fglrx(0): 800x600@56Hz
    [ 6.786] (II) fglrx(0): 800x600@60Hz
    [ 6.786] (II) fglrx(0): 800x600@72Hz
    [ 6.786] (II) fglrx(0): 800x600@75Hz
    [ 6.786] (II) fglrx(0): 832x624@75Hz
    [ 6.786] (II) fglrx(0): 1024x768@60Hz
    [ 6.786] (II) fglrx(0): 1024x768@70Hz
    [ 6.786] (II) fglrx(0): 1024x768@75Hz
    [ 6.786] (II) fglrx(0): 1280x1024@75Hz
    [ 6.786] (II) fglrx(0): 1152x864@75Hz
    [ 6.786] (II) fglrx(0): Manufacturer's mask: 0
    [ 6.786] (II) fglrx(0): Supported standard timings:
    [ 6.786] (II) fglrx(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 6.786] (II) fglrx(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 6.786] (II) fglrx(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 6.786] (II) fglrx(0): Supported detailed timing:
    [ 6.786] (II) fglrx(0): clock: 108.0 MHz Image Size: 338 x 270 mm
    [ 6.786] (II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 6.786] (II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 6.786] (II) fglrx(0): Ranges: V min: 56 V max: 76 Hz, H min: 31 H max: 80 kHz, PixClock max 145 MHz
    [ 6.786] (II) fglrx(0): Monitor name: Acer V173
    [ 6.786] (II) fglrx(0): Serial No: LE10D0928502
    [ 6.786] (II) fglrx(0): EDID (in hex):
    [ 6.786] (II) fglrx(0): 00ffffffffffff00047253005e207092
    [ 6.786] (II) fglrx(0): 1b13010368221b78ca3dc5a6564a9a25
    [ 6.786] (II) fglrx(0): 125054bfef80714f8140818001010101
    [ 6.786] (II) fglrx(0): 010101010101302a009851002a403070
    [ 6.786] (II) fglrx(0): 1300520e1100001e000000fd00384c1f
    [ 6.786] (II) fglrx(0): 500e000a202020202020000000fc0041
    [ 6.786] (II) fglrx(0): 63657220563137330a0a0a0a000000ff
    [ 6.786] (II) fglrx(0): 004c45313044303932383530320a001d
    [ 6.786] (II) fglrx(0): Printing probed modes for output CRT1
    [ 6.786] (II) fglrx(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 6.786] (II) fglrx(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1152x864"x60.0 108.00 1152 1328 1440 1688 864 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1280x768"x60.0 108.00 1280 1376 1488 1800 768 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1280x720"x60.0 108.00 1280 1376 1488 1800 720 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1024x768"x70.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "800x600"x72.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "800x600"x56.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "640x480"x72.0 31.50 640 656 696 832 480 481 484 520 -hsync -vsync (37.9 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "640x480"x67.0 27.28 640 664 728 816 480 481 484 499 -hsync +vsync (33.4 kHz e)
    [ 6.786] (II) fglrx(0): Modeline "640x480"x60.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.786] (II) fglrx(0): Output DFP1 disconnected
    [ 6.786] (II) fglrx(0): Output DFP2 disconnected
    [ 6.786] (II) fglrx(0): Output DFP3 disconnected
    [ 6.786] (II) fglrx(0): Output DFP4 disconnected
    [ 6.786] (II) fglrx(0): Output DFP5 disconnected
    [ 6.786] (II) fglrx(0): Output DFP6 disconnected
    [ 6.786] (II) fglrx(0): Output DFP7 disconnected
    [ 6.786] (II) fglrx(0): Output CRT1 connected
    [ 6.786] (II) fglrx(0): Using exact sizes for initial modes
    [ 6.786] (II) fglrx(0): Output CRT1 using initial mode 1280x1024
    [ 6.786] (II) fglrx(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 6.786] (II) fglrx(0): DPI set to (96, 96)
    [ 6.786] (II) fglrx(0): Eyefinity capable adapter detected.
    [ 6.786] (II) fglrx(0): Adapter AMD Radeon HD 6800 Series has 6 configurable heads and 1 displays connected.
    [ 6.786] (==) fglrx(0): PseudoColor visuals disabled
    [ 6.786] (II) Loading sub module "ramdac"
    [ 6.786] (II) LoadModule: "ramdac"
    [ 6.786] (II) Module "ramdac" already built-in
    [ 6.786] (==) fglrx(0): NoDRI = NO
    [ 6.786] (==) fglrx(0): Capabilities: 0x00000000
    [ 6.786] (==) fglrx(0): CapabilitiesEx: 0x00000000
    [ 6.786] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    [ 6.786] (==) fglrx(0): UseFastTLS=0
    [ 6.786] (II) fglrx(0): Shadow Primary option: ShadowPrimary is enabled
    [ 6.786] (--) Depth 24 pixmap format is 32 bpp
    [ 6.786] (EE) fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible.
    [ 6.786] (WW) fglrx(0): ***********************************************************
    [ 6.786] (WW) fglrx(0): * DRI initialization failed *
    [ 6.786] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
    [ 6.787] (WW) fglrx(0): * 2D and 3D acceleration disabled *
    [ 6.787] (WW) fglrx(0): ***********************************************************
    [ 6.787] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x10000000
    [ 6.796] (II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
    [ 6.796] (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1280) (front color buffer - assumption)
    [ 6.796] (II) fglrx(0): Largest offscreen area available: 1280 x 6911
    [ 6.797] (==) fglrx(0): Backing store disabled
    [ 6.797] Loading extension FGLRXEXTENSION
    [ 6.797] (**) fglrx(0): DPMS enabled
    [ 6.798] (II) fglrx(0): Initialized in-driver Xinerama extension
    [ 6.798] (WW) fglrx(0): Textured Video not supported without DRI enabled.
    [ 6.798] (II) LoadModule: "glesx"
    [ 6.798] (II) Loading /usr/lib/xorg/modules/glesx.so
    [ 6.863] (II) Module glesx: vendor="X.Org Foundation"
    [ 6.863] compiled for 1.4.99.906, module version = 1.0.0
    [ 6.863] Loading extension GLESX
    [ 6.863] (II) fglrx(0): GLESX enableFlags = 576
    [ 6.867] (II) LoadModule: "amdxmm"
    [ 6.868] (II) Loading /usr/lib/xorg/modules/amdxmm.so
    [ 6.878] (II) Module amdxmm: vendor="X.Org Foundation"
    [ 6.878] compiled for 1.4.99.906, module version = 2.0.0
    [ 6.878] (EE) fglrx(0): XMM failed to open CMMQS connection.(EE) fglrx(0):
    [ 6.878] (EE) fglrx(0): XMM failed to initialize
    [ 6.878] (WW) fglrx(0): No XV video playback available
    [ 6.878] (II) fglrx(0): Enable composite support successfully
    [ 6.878] (WW) fglrx(0): Option "VendorName" is not used
    [ 6.878] (WW) fglrx(0): Option "ModelName" is not used
    [ 6.878] (==) fglrx(0): Silken mouse enabled
    [ 6.878] (==) fglrx(0): Using HW cursor of display infrastructure!
    [ 6.879] (II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 6.939] (--) RandR disabled
    [ 6.968] (II) AIGLX: Screen 0 is not DRI capable
    [ 6.968] [glesx] __glESXExtensionInit: No GL ES2.0 capable screen found!
    [ 6.968] (II) fglrx(0): Setting screen physical size to 338 x 270
    [ 7.220] (II) config/udev: Adding input device Power Button (/dev/input/event13)
    [ 7.220] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.220] (II) LoadModule: "evdev"
    [ 7.221] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 7.232] (II) Module evdev: vendor="X.Org Foundation"
    [ 7.232] compiled for 1.13.0, module version = 2.7.3
    [ 7.232] Module class: X.Org XInput Driver
    [ 7.232] ABI class: X.Org XInput driver, version 18.0
    [ 7.232] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.232] (**) Power Button: always reports core events
    [ 7.232] (**) evdev: Power Button: Device: "/dev/input/event13"
    [ 7.232] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.232] (--) evdev: Power Button: Found keys
    [ 7.232] (II) evdev: Power Button: Configuring as keyboard
    [ 7.232] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input13/event13"
    [ 7.232] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 7.232] (**) Option "xkb_rules" "evdev"
    [ 7.232] (**) Option "xkb_model" "evdev"
    [ 7.232] (**) Option "xkb_layout" "us"
    [ 7.268] (II) config/udev: Adding input device Power Button (/dev/input/event12)
    [ 7.268] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.268] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.268] (**) Power Button: always reports core events
    [ 7.268] (**) evdev: Power Button: Device: "/dev/input/event12"
    [ 7.268] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.268] (--) evdev: Power Button: Found keys
    [ 7.268] (II) evdev: Power Button: Configuring as keyboard
    [ 7.268] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input12/event12"
    [ 7.268] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 7.268] (**) Option "xkb_rules" "evdev"
    [ 7.268] (**) Option "xkb_model" "evdev"
    [ 7.268] (**) Option "xkb_layout" "us"
    [ 7.268] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=3 (/dev/input/event14)
    [ 7.268] (II) No input driver specified, ignoring this device.
    [ 7.268] (II) This device may have been added with another device file.
    [ 7.269] (II) config/udev: Adding input device Logitech Optical USB Mouse (/dev/input/event0)
    [ 7.269] (**) Logitech Optical USB Mouse: Applying InputClass "evdev pointer catchall"
    [ 7.269] (II) Using input driver 'evdev' for 'Logitech Optical USB Mouse'
    [ 7.269] (**) Logitech Optical USB Mouse: always reports core events
    [ 7.269] (**) evdev: Logitech Optical USB Mouse: Device: "/dev/input/event0"
    [ 7.269] (--) evdev: Logitech Optical USB Mouse: Vendor 0x46d Product 0xc016
    [ 7.269] (--) evdev: Logitech Optical USB Mouse: Found 3 mouse buttons
    [ 7.269] (--) evdev: Logitech Optical USB Mouse: Found scroll wheel(s)
    [ 7.269] (--) evdev: Logitech Optical USB Mouse: Found relative axes
    [ 7.269] (--) evdev: Logitech Optical USB Mouse: Found x and y relative axes
    [ 7.269] (II) evdev: Logitech Optical USB Mouse: Configuring as mouse
    [ 7.269] (II) evdev: Logitech Optical USB Mouse: Adding scrollwheel support
    [ 7.269] (**) evdev: Logitech Optical USB Mouse: YAxisMapping: buttons 4 and 5
    [ 7.269] (**) evdev: Logitech Optical USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 7.269] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.0/usb8/8-1/8-1:1.0/input/input0/event0"
    [ 7.269] (II) XINPUT: Adding extended input device "Logitech Optical USB Mouse" (type: MOUSE, id 8)
    [ 7.269] (II) evdev: Logitech Optical USB Mouse: initialized for relative axes.
    [ 7.269] (**) Logitech Optical USB Mouse: (accel) keeping acceleration scheme 1
    [ 7.269] (**) Logitech Optical USB Mouse: (accel) acceleration profile 0
    [ 7.269] (**) Logitech Optical USB Mouse: (accel) acceleration factor: 2.000
    [ 7.269] (**) Logitech Optical USB Mouse: (accel) acceleration threshold: 4
    [ 7.269] (II) config/udev: Adding input device Logitech Optical USB Mouse (/dev/input/mouse0)
    [ 7.269] (II) No input driver specified, ignoring this device.
    [ 7.269] (II) This device may have been added with another device file.
    [ 7.269] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event1)
    [ 7.269] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 7.269] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
    [ 7.269] (**) Logitech USB Keyboard: always reports core events
    [ 7.269] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event1"
    [ 7.269] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31c
    [ 7.269] (--) evdev: Logitech USB Keyboard: Found keys
    [ 7.269] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
    [ 7.269] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.0/usb8/8-2/8-2:1.0/input/input1/event1"
    [ 7.269] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 9)
    [ 7.269] (**) Option "xkb_rules" "evdev"
    [ 7.269] (**) Option "xkb_model" "evdev"
    [ 7.269] (**) Option "xkb_layout" "us"
    [ 7.270] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event2)
    [ 7.270] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 7.270] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
    [ 7.270] (**) Logitech USB Keyboard: always reports core events
    [ 7.270] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event2"
    [ 7.270] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31c
    [ 7.270] (--) evdev: Logitech USB Keyboard: Found absolute axes
    [ 7.270] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to exist.
    [ 7.270] (--) evdev: Logitech USB Keyboard: Found keys
    [ 7.270] (II) evdev: Logitech USB Keyboard: Forcing relative x/y axes to exist.
    [ 7.270] (II) evdev: Logitech USB Keyboard: Configuring as mouse
    [ 7.270] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
    [ 7.270] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.0/usb8/8-2/8-2:1.1/input/input2/event2"
    [ 7.270] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 10)
    [ 7.270] (**) Option "xkb_rules" "evdev"
    [ 7.270] (**) Option "xkb_model" "evdev"
    [ 7.270] (**) Option "xkb_layout" "us"
    [ 7.271] (II) evdev: Logitech USB Keyboard: initialized for absolute axes.
    [ 7.271] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1
    [ 7.271] (**) Logitech USB Keyboard: (accel) acceleration profile 0
    [ 7.271] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
    [ 7.271] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
    [ 7.272] (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event10)
    [ 7.272] (II) No input driver specified, ignoring this device.
    [ 7.272] (II) This device may have been added with another device file.
    [ 7.273] (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event11)
    [ 7.273] (II) No input driver specified, ignoring this device.
    [ 7.273] (II) This device may have been added with another device file.
    [ 7.273] (II) config/udev: Adding input device HDA ATI SB Line (/dev/input/event4)
    [ 7.273] (II) No input driver specified, ignoring this device.
    [ 7.273] (II) This device may have been added with another device file.
    [ 7.274] (II) config/udev: Adding input device HDA ATI SB Rear Mic (/dev/input/event5)
    [ 7.274] (II) No input driver specified, ignoring this device.
    [ 7.274] (II) This device may have been added with another device file.
    [ 7.274] (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event6)
    [ 7.274] (II) No input driver specified, ignoring this device.
    [ 7.274] (II) This device may have been added with another device file.
    [ 7.275] (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event7)
    [ 7.275] (II) No input driver specified, ignoring this device.
    [ 7.275] (II) This device may have been added with another device file.
    [ 7.275] (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event8)
    [ 7.275] (II) No input driver specified, ignoring this device.
    [ 7.275] (II) This device may have been added with another device file.
    [ 7.276] (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event9)
    [ 7.276] (II) No input driver specified, ignoring this device.
    [ 7.276] (II) This device may have been added with another device file.
    [ 7.276] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 7.276] (II) No input driver specified, ignoring this device.
    [ 7.276] (II) This device may have been added with another device file.
    [ 7.279] (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
    [ 7.287] (II) fglrx(0): EDID vendor "ACR", prod id 83
    [ 7.287] (II) fglrx(0): Using EDID range info for horizontal sync
    [ 7.287] (II) fglrx(0): Using EDID range info for vertical refresh
    [ 7.287] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 7.287] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 7.287] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 7.287] (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 7.288] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 10.785] (II) fglrx(0): EDID vendor "ACR", prod id 83
    [ 10.785] (II) fglrx(0): Using hsync ranges from config file
    [ 10.785] (II) fglrx(0): Using vrefresh ranges from config file
    [ 10.785] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 10.785] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 10.785] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 10.786] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 23.739] (II) fglrx(0): EDID vendor "ACR", prod id 83
    [ 23.739] (II) fglrx(0): Using hsync ranges from config file
    [ 23.739] (II) fglrx(0): Using vrefresh ranges from config file
    [ 23.739] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 23.739] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 23.739] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 23.739] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 24.928] (II) fglrx(0): EDID vendor "ACR", prod id 83
    [ 24.928] (II) fglrx(0): Using hsync ranges from config file
    [ 24.928] (II) fglrx(0): Using vrefresh ranges from config file
    [ 24.928] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 24.928] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 24.928] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 24.928] (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 24.929] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 27.583] (II) fglrx(0): EDID vendor "ACR", prod id 83
    [ 27.583] (II) fglrx(0): Using hsync ranges from config file
    [ 27.583] (II) fglrx(0): Using vrefresh ranges from config file
    [ 27.583] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 27.583] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 27.583] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 27.583] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    I'll try out the suggestions you guys have given and update.

  • How to load linux driver module in java

    Hi
    I am currently trying to load a Linux driver module dynamically from java to enable some kind of wireless communication using the System.load() method. But unfortunately, the module is a .ko file rather than a dynamic loadable library .so file in Linux, So that when I try to load this module, I get an error:
    Can't load IA 32-bit .so on a IA 32-bit platform
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1647)
    at java.lang.Runtime.load0(Runtime.java:769)
    at java.lang.System.load(System.java:968)
    at test.main(test.java:10)
    I wonder if this error is caused purely by the type of file or there might be some other reasons? It seems that all the linux drivers are .ko files, can any one help me to figure out a way of loading such linux drivers?
    Thank you
    Song

    Can any one give me some hint?
    I am thinking about one possible solution: write a c program to load this module, then compile the c program to be a shared object library, and use jni to load this shared object library.
    Does this work?
    Thank you

  • Nokia Map and Drive+ Beta on Lumina 920 Feedback

    So I took my new phone down to MD/DC area in the last few days and here are a few things that I would like to post as my feedback on what would be nice to have, fixes, etc.  [I used both my new Lumia 920 and my wife's Samsung Galaxy Note 2 as comparsion).
    1. Highest priority for me is that the routes from Here.net need to be able to sync down to the phone.  Nothing more is more important then this because when you have a custom route that you want to use (for example, to route around high traffic or potential high traffic areas).
    2. Extremely disappointed that a new road in MD (MD 200) was not used by the Drive+ and didn't even show up on the map on my Lumia 920 while it was used and did show up on Google map.  This road is a toll road and is over a year old already.  [And yes, I have enabled toll road in the navigation as well as selected 'faster route' as the routing to use under smart routing].  I cannot stressed how disappointed I am to not see Nokia Map have this route at all.
    3. Allow route changes on the Nokia Drive+ app.  As good as pre-planned trip and using Here.net, there are just tmes that it's much better to allow us to change the route based on latest condition.
    4. Never once did I see ANY traffic updates at all on both the Map and Drive+ Beta.  When it does shows on my wife's Google's Map/Navigation.
    5. I love that under Drive+, it tells you which lane to get into ahead of when you need to make a turn or merge onto another way. However, the flip side of that is that there's no way to know which road you're currently on.  This is probably more important for when you're in an area with a lot of highway/local way intersections.  Also, it would be great if it also will display the next major 'road' that you will be getting onto.
    So far I'm happy with some of the functionality and disappointed in some of Nokia Map and Drive+ and I have about a week left to decide to either stay with WP9 and Nokia or do I want to switch back to Android and Google Map.

    hi there,
    As this is a user to user forum only, if you wish to leave feedback with Nokia regarding their products and services, you can do so directly by clicking the Nokia Support link at the bottom of this page.

  • Help updating ATI graphics driver in bootcamp Windows 8.1 on iMac (Retina 5K, 27-inch) with 4 GHz Intel core i7, 16 GB 1600 MHz DDR3 and AMD Radeon R9 M295x 4096MB

    Help updating ATI graphics driver in bootcamp Windows 8.1 on iMac (Retina 5K, 27-inch) with 4 GHz Intel core i7, 16 GB 1600 MHz DDR3 and AMD Radeon R9 M295x 4096MB

    Of note there is a new AMD Catalyst Omega driver released earlier in the week that brings 5K resolution to AMD graphics cards. Here is the link (support.ad.com/en-us/download) to the AMD site. But none of these work with my iMac (Retina 5K, 27-inch, Late 2014), Windows 8 bootcamp.
    Please advise.
    Thanks in advace.

  • HERE Drive + Beta constantly crashes after upgrade...

    After i upgraded to Here Drive + Beta on my Lumia 920, the app constantly crashes when i start it!
    I have tried to restart the phone, uninstall the app, and reinstall....but it still crashes! The other Here-apps is ok, and works fine!
    Didn't anyone at Nokia tested this properly before releasing the upgrade!!!???
    I hope you guys at Nokia have an upgrade to fix this problem quickly because one of the main reasons that i bought a Nokia again was the Maps and Drive function with offline maps!!
    Solved!
    Go to Solution.

    Update!
    Today i reset my Lumia 920 back to factory settings, and for a short while.... the Here Drive worked all fine....
    But suddenly... the error came back, and Here Drive was starting to crash again!
    And by the way... restoring the phone is a pretty big job!
    Especially when this happens also:
    http://www.wpxbox.com/how-to-fix-downloading-application-error-code-8000ffff-after-windows-phone-8-r...
    I think the word i'm looking for is.....**bleep**!
    So i really hope that Nokia understand the frustration this is for me and other owners and come up with a quick fix!

  • HERE Drive Beta with Traffic updates Lumia 920

    Why can't i use Traffic updates in the HERE Drive + Beta..?? How can see the traffic info while using the navigation on my Lumia 920..?? i had this with my Nokia N8... 

    I recently got the update to Here Drive+ Beta and now have Here Drive+ with My Commutes. I think the possiblities are fantastic with the My Commutes feature but so far in the Dallas, TX area whenever I start My Commutes is always says "Couldn't update traffic" I have uninstalled and reinstalled the application but it will not show me any traffic updates during my communte.
    I recently discovered that if I put the app in 2d mode it will show me traffic updates but as soon as I start My Commutes the traffic information disappears.
    Is anyone else experiencing this same issue?
    Nokia Lumia 920

  • ATI Display Driver

    I am trying to install the the ATI Display Driver package for a T500 without any of the applications that are included with it. In other words, I only want to install the drivers and nothing else like the Catalyst Control Center, etc.
    When I try to do a customized install,  I cannot uncheck any of the boxes I don't want installed. It seems like it is all or nothing. what's customizable about that?
    Is there a way to do what I want?
    Thanks

    You could ignore the fact that catalyst control center is installed and just remove CCC from startup (under HKLM\.....\Run in registry) when Windows is starting. Or you could uncompress the package and just install the driver by going into device manager and choose to update driver the driver then select the directory where you uncompressed the package.
    -gan

  • Amd/ati video drive

    Question.. i'm having a problem with my AMD/ATI VIDEO DRIVE.. It has been suggested to uninstall the program.. will my laptop run properly or how do i resolve this issue.. i no longer have a warranty it is almost 4 years old...

    Your graphics card(and most hardware) requires drivers to run efficiently. If you do not have proper drivers installed your graphics card may run at full performance and overheat. The best thing to do is go to the AMD website and download the latest drivers for your graphics card.  
    Btw what problem are you facing?

  • Beta testers wanted - Refactoring (and more) for FB4

    ElementRiver is excited to announce that our new professional add-on to Flash Builder 4 is now in beta.
    SourceMate adds many features to Flash Builder including refactoring, code generation, code snippets and much more.
    We're looking for beta testers.  If you're using FB Beta2 or later we would like to invite you to our free beta trial.
    http://www.elementriver.com/sourcemate
    thanks,
    Chris Gross
    President
    ElementRiver - creators of the Potomac framework
    www.elementriver.com

    Thanks for your replies so far. I am working on the menu
    system at the moment and will post screenshots within the next few
    days. I am struck by how easy to use the Flickr API is together
    with FlashLite, it really is a pleasure working with it. The harder
    part is scripting the application itself, not the API as I first
    thought.
    Regards,
    Matthias

  • Is the hard drive better in the MacBook Pro that the Air version?

    Is the hard drive better in the MacBook Pro that the Air version? What are the negatives?

    That is a question only Apple can answer and the purchaser must decide if the price is worth it.  Apples pricing for upgrades in the past has often been such that third party RAM and HHDs/SSDs were less expensive.  However those options are no longer available with the retina MBPs.
    Ciao.

Maybe you are looking for

  • Photoshop wont open .mp4 video file

    When i try to open an mp4 video photoshop prompts me that i need a quicktime version 7.1 or higher , i have 7.7.1 I have photoshop CS5 extended which as far as i know should be able to open .mp4 files. Any ideas? This is what i get

  • How do you select an object that is directly under another object?

    How do you select an object that is directly under another object? I was working from a template and I wanted to make a text box the same size as a column box that was put there in order to keep the text in the confines of the paper that is was being

  • Image Ultra Builder 4.0: "An error occurred while connecting to server: Check the server"

    Ladies & gentlemen  I am using evaluation version of ImageUltra Builder 4.0 for Windows XP. Both server and console have been installed on the same machine. When I try to add a new repository, then after pressing the final "Finish" button I get the m

  • Which group by function to use in following case?

    Table name: PVH | Processid | Name | Timechanged | Value | | 268436769 | filecount | 10/1/2008 2:59:01.006000 AM | 0 | | 268436769 | filecount | 10/1/2008 2:45:33.004000 AM | 100 | I want "value" where max(timechanged) and groupby appianprocessid and

  • Inspection lot PGI for STO-Quality management

    Sirs, I have a query. I have an FG where i am using an STO to transfer the material from 1 plant to another. Here i have inspection type 08 assigned in the master. I have assigned the origin 08 to the delivery type NL hence when i save the OBD (not p