Unable to kill X using Catalyst drivers
My problem is that once I'm in X I can't drop back to the console. The computer starts in console and then I start X manually with "startx". That all works but once I'm there, I can't back out. I'm using XFCE and I've tried ctrl+alt+F2-F6. That just leaves me with a black screen but I'm able to go back to X using ctrl+alt+F1. I've also tried hitting the "Log Out" button and that just leaves me at a completely black screen with no way that I know of to get back to X or get to a console. My only recourse there was to ctrl+alt+delete to reboot the system (which didn't give any output until after it rebooted). I'm using the Catalyst 13.2 Beta drivers from catalyst-test in the AUR. This all worked flawlessly when using the open source drivers.
the sad clown wrote:Why don't you just kill the end process in .xinitrc?
Not sure what you mean by that. Anyway, I narrowed the problem down to that AUR package catalyst-test. The Catalyst 13.1 from [community] doesn't have this issue.
Similar Messages
-
[Solved] X11 has purple tint when using catalyst-test drivers
Hey guys, so I turned the TV on for my HTPC last night hoping to watch some anime. But when it turned on the screen had a purple tint! I tried to do some debugging over SSH from my phone while in bed, but decided to just go to sleep instead.
Tonight I narrowed down the problem a bit, it's certainly related to the catalyst drivers (No problems when using xf86-video-ati).
I'm noticing warnings from various programs that look like
libpng warning: iCCP: known incorrect sRGB profile
Taking a screenshot using `scrot` and viewing it the screen looks fine..
Here's my xorg.conf (which is just the default genearted by aticonfig --initial)
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
I suspected that it might have been a package upgrade, but downgrading packages that looked like they might have been the problem didn't solve anything.
Any ideas?
Edit: Just tried with xorg1.13 with Catalyst 13.4 (stable).. same problem.
Edit 2: After starting and then stopping X this problem happens in the framebuffer too.. hmmm (It doesn't happen during boot time or during initial login, it's not a bad cable connection!)
Edit 3: The problem does not occur when using the VGA d-sub output, only when using the HDMI output
Edit 4: Here's my Xorg.0.log
[ 1826.112]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 1826.112] X Protocol Version 11, Revision 0
[ 1826.112] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 1826.112] Current Operating System: Linux htpc 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64
[ 1826.112] Kernel command line: initrd=\initramfs-linux.img root=UUID=03f6bfa4-7815-4841-8386-5545dfa4cd33 ro loglevel=0 nomodeset
[ 1826.112] Build Date: 01 July 2013 10:48:42AM
[ 1826.112]
[ 1826.113] Current version of pixman: 0.30.0
[ 1826.113] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1826.113] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1826.113] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 22 08:39:14 2013
[ 1826.113] (==) Using config file: "/etc/X11/xorg.conf"
[ 1826.113] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 1826.113] (==) ServerLayout "aticonfig Layout"
[ 1826.113] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
[ 1826.113] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
[ 1826.114] (**) | |-->Device "aticonfig-Device[0]-0"
[ 1826.114] (==) Automatically adding devices
[ 1826.114] (==) Automatically enabling devices
[ 1826.114] (==) Automatically adding GPU devices
[ 1826.114] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 1826.114] Entry deleted from font path.
[ 1826.114] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1826.114] Entry deleted from font path.
[ 1826.114] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1826.114] Entry deleted from font path.
[ 1826.114] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1826.114] Entry deleted from font path.
[ 1826.114] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 1826.114] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1826.114] Entry deleted from font path.
[ 1826.114] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 1826.114] (==) FontPath set to:
/usr/share/fonts/misc/
[ 1826.114] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1826.114] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1826.114] (II) Loader magic: 0x7fdc20
[ 1826.114] (II) Module ABI versions:
[ 1826.114] X.Org ANSI C Emulation: 0.4
[ 1826.114] X.Org Video Driver: 14.1
[ 1826.114] X.Org XInput driver : 19.1
[ 1826.114] X.Org Server Extension : 7.0
[ 1826.117] (--) PCI:*(0:0:1:0) 1002:964a:1565:1707 rev 0, Mem @ 0xc0000000/268435456, 0xfef00000/262144, I/O @ 0x0000f000/256
[ 1826.117] Initializing built-in extension Generic Event Extension
[ 1826.117] Initializing built-in extension SHAPE
[ 1826.117] Initializing built-in extension MIT-SHM
[ 1826.117] Initializing built-in extension XInputExtension
[ 1826.117] Initializing built-in extension XTEST
[ 1826.117] Initializing built-in extension BIG-REQUESTS
[ 1826.117] Initializing built-in extension SYNC
[ 1826.117] Initializing built-in extension XKEYBOARD
[ 1826.117] Initializing built-in extension XC-MISC
[ 1826.117] Initializing built-in extension SECURITY
[ 1826.117] Initializing built-in extension XINERAMA
[ 1826.117] Initializing built-in extension XFIXES
[ 1826.117] Initializing built-in extension RENDER
[ 1826.117] Initializing built-in extension RANDR
[ 1826.117] Initializing built-in extension COMPOSITE
[ 1826.117] Initializing built-in extension DAMAGE
[ 1826.117] Initializing built-in extension MIT-SCREEN-SAVER
[ 1826.117] Initializing built-in extension DOUBLE-BUFFER
[ 1826.117] Initializing built-in extension RECORD
[ 1826.117] Initializing built-in extension DPMS
[ 1826.117] Initializing built-in extension X-Resource
[ 1826.117] Initializing built-in extension XVideo
[ 1826.117] Initializing built-in extension XVideo-MotionCompensation
[ 1826.117] Initializing built-in extension XFree86-VidModeExtension
[ 1826.117] Initializing built-in extension XFree86-DGA
[ 1826.117] Initializing built-in extension XFree86-DRI
[ 1826.117] Initializing built-in extension DRI2
[ 1826.117] (II) "glx" will be loaded by default.
[ 1826.117] (II) LoadModule: "glx"
[ 1826.117] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1826.117] (II) Module glx: vendor="Advanced Micro Devices, Inc."
[ 1826.117] compiled for 6.9.0, module version = 1.0.0
[ 1826.118] Loading extension GLX
[ 1826.118] (II) LoadModule: "fglrx"
[ 1826.118] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 1826.134] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[ 1826.134] compiled for 1.4.99.906, module version = 13.10.10
[ 1826.134] Module class: X.Org Video Driver
[ 1826.134] (II) Loading sub module "fglrxdrm"
[ 1826.134] (II) LoadModule: "fglrxdrm"
[ 1826.134] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 1826.134] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[ 1826.134] compiled for 1.4.99.906, module version = 13.10.10
[ 1826.134] (II) AMD Proprietary Linux Driver Version Identifier:13.10.10
[ 1826.134] (II) AMD Proprietary Linux Driver Release Identifier: UNSUPPORTED-13.101
[ 1826.134] (II) AMD Proprietary Linux Driver Build Date: May 23 2013 15:49:35
[ 1826.134] (++) using VT number 4
[ 1826.136] (WW) Falling back to old probe method for fglrx
[ 1826.150] (II) Loading PCS database from /etc/ati/amdpcsdb /etc/ati/amdpcsdb.default
[ 1826.154] ukiDynamicMajor: found major device number 250
[ 1826.154] ukiDynamicMajor: found major device number 250
[ 1826.154] ukiOpenByBusid: Searching for BusID PCI:0:1:0
[ 1826.154] ukiOpenDevice: node name is /dev/ati/card0
[ 1826.154] ukiOpenDevice: open result is 9, (OK)
[ 1826.154] ukiOpenByBusid: ukiOpenMinor returns 9
[ 1826.154] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
[ 1826.156] (--) Chipset Supported AMD Graphics Processor (0x964A) found
[ 1826.156] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:1) found
[ 1826.156] (II) AMD Video driver is running on a device belonging to a group targeted for this release
[ 1826.156] (II) AMD Video driver is signed
[ 1826.157] (II) fglrx(0): pEnt->device->identifier=0xcf8900
[ 1826.157] (II) fglrx(0): === [xdl_xs114_atiddxPreInit] === begin
[ 1826.157] (II) Loading sub module "vgahw"
[ 1826.157] (II) LoadModule: "vgahw"
[ 1826.157] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 1826.157] (II) Module vgahw: vendor="X.Org Foundation"
[ 1826.157] compiled for 1.14.2, module version = 0.1.0
[ 1826.157] ABI class: X.Org Video Driver, version 14.1
[ 1826.158] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
[ 1826.158] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 1826.158] (==) fglrx(0): Default visual is TrueColor
[ 1826.158] (**) fglrx(0): Option "DPMS" "true"
[ 1826.158] (==) fglrx(0): RGB weight 888
[ 1826.158] (II) fglrx(0): Using 8 bits per RGB
[ 1826.158] (==) fglrx(0): Buffer Tiling is ON
[ 1826.158] (II) Loading sub module "fglrxdrm"
[ 1826.158] (II) LoadModule: "fglrxdrm"
[ 1826.158] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 1826.158] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[ 1826.158] compiled for 1.4.99.906, module version = 13.10.10
[ 1826.161] ukiDynamicMajor: found major device number 250
[ 1826.162] ukiDynamicMajor: found major device number 250
[ 1826.162] ukiOpenByBusid: Searching for BusID PCI:0:1:0
[ 1826.162] ukiOpenDevice: node name is /dev/ati/card0
[ 1826.162] ukiOpenDevice: open result is 12, (OK)
[ 1826.162] ukiOpenByBusid: ukiOpenMinor returns 12
[ 1826.162] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
[ 1826.162] (**) fglrx(0): NoAccel = NO
[ 1826.162] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
[ 1826.162] (--) fglrx(0): Chipset: "AMD Radeon HD 6530D" (Chipset = 0x964a)
[ 1826.162] (--) fglrx(0): (PciSubVendor = 0x1565, PciSubDevice = 0x1707)
[ 1826.162] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
[ 1826.162] (--) fglrx(0): Linear framebuffer (phys) at 0xc0000000
[ 1826.162] (--) fglrx(0): MMIO registers at 0xfef00000
[ 1826.162] (--) fglrx(0): I/O port at 0x0000f000
[ 1826.162] (==) fglrx(0): ROM-BIOS at 0x000c0000
[ 1826.163] (II) fglrx(0): AC Adapter is used
[ 1826.163] (II) fglrx(0): AMD Video BIOS revision 9 or later detected
[ 1826.163] (--) fglrx(0): Video RAM: 524288 kByte, Type: DDR3
[ 1826.163] (II) fglrx(0): PCIE card detected
[ 1826.163] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
[ 1826.163] (WW) fglrx(0): board is an unknown third party board, chipset is supported
[ 1826.163] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x20000000)
[ 1826.163] (II) fglrx(0): RandR 1.2 support is enabled!
[ 1826.163] (II) fglrx(0): RandR 1.2 rotation support is enabled!
[ 1826.163] (==) fglrx(0): Center Mode is disabled
[ 1826.163] (II) Loading sub module "fb"
[ 1826.163] (II) LoadModule: "fb"
[ 1826.163] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1826.164] (II) Module fb: vendor="X.Org Foundation"
[ 1826.164] compiled for 1.14.2, module version = 1.0.0
[ 1826.164] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1826.164] (II) Loading sub module "ddc"
[ 1826.164] (II) LoadModule: "ddc"
[ 1826.164] (II) Module "ddc" already built-in
[ 1826.293] (II) fglrx(0): Output DFP1 using monitor section aticonfig-Monitor[0]-0
[ 1826.293] (II) fglrx(0): Output CRT1 has no monitor section
[ 1826.293] (II) Loading sub module "ddc"
[ 1826.293] (II) LoadModule: "ddc"
[ 1826.293] (II) Module "ddc" already built-in
[ 1826.293] (II) fglrx(0): Connected Display0: DFP1
[ 1826.293] (II) fglrx(0): Display0: Failed to get EDID information.
[ 1826.294] (II) fglrx(0): EDID for output DFP1
[ 1826.294] (II) fglrx(0): Manufacturer: EXP Model: 901 Serial#: 1
[ 1826.294] (II) fglrx(0): Year: 2004 Week: 0
[ 1826.294] (II) fglrx(0): EDID Version: 1.3
[ 1826.294] (II) fglrx(0): Digital Display Input
[ 1826.294] (II) fglrx(0): Max Image Size [cm]: horiz.: 115 vert.: 65
[ 1826.294] (II) fglrx(0): Gamma: 2.20
[ 1826.294] (II) fglrx(0): DPMS capabilities: Off
[ 1826.294] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 1826.294] (II) fglrx(0): First detailed timing is preferred mode
[ 1826.294] (II) fglrx(0): redX: 0.618 redY: 0.351 greenX: 0.280 greenY: 0.605
[ 1826.294] (II) fglrx(0): blueX: 0.152 blueY: 0.063 whiteX: 0.312 whiteY: 0.329
[ 1826.294] (II) fglrx(0): Supported established timings:
[ 1826.294] (II) fglrx(0): 640x480@60Hz
[ 1826.294] (II) fglrx(0): 800x600@60Hz
[ 1826.294] (II) fglrx(0): 1024x768@60Hz
[ 1826.294] (II) fglrx(0): Manufacturer's mask: 0
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
[ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 27.0 MHz Image Size: 4 x 3 mm
[ 1826.294] (II) fglrx(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
[ 1826.294] (II) fglrx(0): Monitor name: EP-HDMI-RX
[ 1826.294] (II) fglrx(0): Ranges: V min: 59 V max: 61 Hz, H min: 15 H max: 46 kHz, PixClock max 85 MHz
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
[ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
[ 1826.294] (II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
[ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 1826.294] (II) fglrx(0): Supported detailed timing:
[ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
[ 1826.294] (II) fglrx(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 1826.294] (II) fglrx(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 1826.294] (II) fglrx(0): Number of EDID sections to follow: 1
[ 1826.294] (II) fglrx(0): EDID (in hex):
[ 1826.294] (II) fglrx(0): 00ffffffffffff001710010901000000
[ 1826.294] (II) fglrx(0): 000e0103807341782a7c119e59479b27
[ 1826.294] (II) fglrx(0): 10505421080001010101010101010101
[ 1826.294] (II) fglrx(0): 010101010101011d007251d01e206e28
[ 1826.294] (II) fglrx(0): 550010090000001e8c0ad08a20e02d10
[ 1826.294] (II) fglrx(0): 103e9600040300000018000000fc0045
[ 1826.294] (II) fglrx(0): 502d48444d492d52580a2020000000fd
[ 1826.294] (II) fglrx(0): 003b3d0f2e08000a20202020202001ab
[ 1826.294] (II) fglrx(0): EDID vendor "EXP", prod id 2305
[ 1826.294] (II) fglrx(0): Using EDID range info for horizontal sync
[ 1826.294] (II) fglrx(0): Using EDID range info for vertical refresh
[ 1826.294] (II) fglrx(0): Printing DDC gathered Modelines:
[ 1826.294] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz eP)
[ 1826.294] (II) fglrx(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 1826.294] (II) fglrx(0): Printing probed modes for output DFP1
[ 1826.294] (II) fglrx(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz eP)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080"x60.0 74.25 1920 2008 2052 2200 1080 1085 1095 1125 interlace +hsync +vsync (33.8 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080"x50.0 74.25 1920 2448 2492 2640 1080 1085 1095 1125 interlace +hsync +vsync (28.1 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1920x1080"x59.9 74.18 1920 2008 2052 2200 1080 1085 1095 1125 interlace +hsync +vsync (33.7 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1776x1000"x59.9 148.35 1776 1864 1908 2200 1000 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
[ 1826.294] (II) fglrx(0): Modeline "1776x1000"x50.0 74.25 1776 2304 2348 2640 1000 1005 1015 1125 interlace +hsync +vsync (28.1 kHz ez)
[ 1826.294] (II) fglrx(0): Modeline "1776x1000"x59.9 74.18 1776 1864 1908 2200 1000 1005 1015 1125 interlace +hsync +vsync (33.7 kHz ez)
[ 1826.294] (II) fglrx(0): Modeline "1680x1050"x60.0 148.50 1680 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1680x1050"x59.9 148.35 1680 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1400x1050"x60.0 148.50 1400 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1400x1050"x59.9 148.35 1400 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 1826.294] (II) fglrx(0): Modeline "1600x900"x59.9 148.35 1600 1864 1908 2200 900 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
[ 1826.294] (II) fglrx(0): Modeline "1280x1024"x60.0 148.50 1280 2008 2052 2200 1024 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "1280x1024"x59.9 148.35 1280 2008 2052 2200 1024 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "1440x900"x59.9 148.35 1440 1864 1908 2200 900 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
[ 1826.295] (II) fglrx(0): Modeline "1280x960"x59.9 148.35 1280 1864 1908 2200 960 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
[ 1826.295] (II) fglrx(0): Modeline "1280x768"x59.9 148.35 1280 1864 1908 2200 768 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
[ 1826.295] (II) fglrx(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "1152x648"x50.0 74.25 1152 1592 1632 1980 648 653 658 750 +hsync +vsync (37.5 kHz ez)
[ 1826.295] (II) fglrx(0): Modeline "1152x648"x59.9 74.18 1152 1262 1302 1650 648 653 658 750 +hsync +vsync (45.0 kHz ez)
[ 1826.295] (II) fglrx(0): Modeline "800x600"x50.0 74.25 800 1720 1760 1980 600 725 730 750 +hsync +vsync (37.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "720x480"x50.0 74.25 720 1720 1760 1980 480 725 730 750 +hsync +vsync (37.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "640x480"x50.0 74.25 640 1720 1760 1980 480 725 730 750 +hsync +vsync (37.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1826.295] (II) fglrx(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1826.295] (II) fglrx(0): EDID for output CRT1
[ 1826.295] (II) fglrx(0): Output DFP1 connected
[ 1826.295] (II) fglrx(0): Output CRT1 disconnected
[ 1826.295] (II) fglrx(0): Using exact sizes for initial modes
[ 1826.295] (II) fglrx(0): Output DFP1 using initial mode 1280x720
[ 1826.295] (II) fglrx(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 1826.295] (II) fglrx(0): Display dimensions: (1150, 650) mm
[ 1826.295] (II) fglrx(0): DPI set to (28, 28)
[ 1826.295] (II) fglrx(0): Adapter AMD Radeon HD 6530D has 2 configurable heads and 1 displays connected.
[ 1826.295] (==) fglrx(0): PseudoColor visuals disabled
[ 1826.295] (II) Loading sub module "ramdac"
[ 1826.295] (II) LoadModule: "ramdac"
[ 1826.295] (II) Module "ramdac" already built-in
[ 1826.295] (==) fglrx(0): NoDRI = NO
[ 1826.295] (==) fglrx(0): Capabilities: 0x00000000
[ 1826.295] (==) fglrx(0): CapabilitiesEx: 0x00000000
[ 1826.295] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
[ 1826.295] (==) fglrx(0): UseFastTLS=0
[ 1826.295] (II) fglrx(0): Shadow Primary option: ShadowPrimary is enabled
[ 1826.295] (--) Depth 24 pixmap format is 32 bpp
[ 1826.295] Loading extension ATIFGLRXDRI
[ 1826.295] (II) fglrx(0): doing swlDriScreenInit
[ 1826.295] (II) fglrx(0): swlDriScreenInit for fglrx driver
[ 1826.295] ukiDynamicMajor: found major device number 250
[ 1826.295] ukiDynamicMajor: found major device number 250
[ 1826.295] ukiDynamicMajor: found major device number 250
[ 1826.295] ukiOpenByBusid: Searching for BusID PCI:0:1:0
[ 1826.295] ukiOpenDevice: node name is /dev/ati/card0
[ 1826.295] ukiOpenDevice: open result is 13, (OK)
[ 1826.295] ukiOpenByBusid: ukiOpenMinor returns 13
[ 1826.295] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
[ 1826.295] (II) fglrx(0): [uki] DRM interface version 1.0
[ 1826.295] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:0:1:0"
[ 1826.295] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x7a000
[ 1826.295] (II) fglrx(0): [uki] mapped SAREA 0x7a000 to 0x7ff504c21000
[ 1826.295] (II) fglrx(0): [uki] framebuffer handle = 0x7b000
[ 1826.295] (II) fglrx(0): [uki] added 1 reserved context for kernel
[ 1826.295] (II) fglrx(0): swlDriScreenInit done
[ 1826.295] (II) fglrx(0): Kernel Module Version Information:
[ 1826.295] (II) fglrx(0): Name: fglrx
[ 1826.295] (II) fglrx(0): Version: 13.10.10
[ 1826.295] (II) fglrx(0): Date: May 23 2013
[ 1826.295] (II) fglrx(0): Desc: AMD FireGL DRM kernel module
[ 1826.296] (II) fglrx(0): Kernel Module version matches driver.
[ 1826.296] (II) fglrx(0): Kernel Module Build Time Information:
[ 1826.296] (II) fglrx(0): Build-Kernel UTS_RELEASE: 3.9.9-1-ARCH
[ 1826.296] (II) fglrx(0): Build-Kernel MODVERSIONS: yes
[ 1826.296] (II) fglrx(0): Build-Kernel __SMP__: yes
[ 1826.296] (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
[ 1826.296] (II) fglrx(0): [uki] register handle = 0x0007c000
[ 1826.296] (II) fglrx(0): DRI initialization successfull
[ 1826.296] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x0102c000
[ 1826.297] (==) fglrx(0): Backing store disabled
[ 1826.297] Loading extension FGLRXEXTENSION
[ 1826.297] (**) fglrx(0): DPMS enabled
[ 1826.297] (II) fglrx(0): Initialized in-driver Xinerama extension
[ 1826.297] (**) fglrx(0): Textured Video is enabled.
[ 1826.297] (II) LoadModule: "glesx"
[ 1826.297] (II) Loading /usr/lib/xorg/modules/glesx.so
[ 1826.298] (II) Module glesx: vendor="X.Org Foundation"
[ 1826.298] compiled for 1.4.99.906, module version = 1.0.0
[ 1826.298] Loading extension GLESX
[ 1826.298] (II) fglrx(0): GLESX enableFlags = 592
[ 1826.298] (II) fglrx(0): GLESX is enabled
[ 1826.298] (II) LoadModule: "amdxmm"
[ 1826.298] (II) Loading /usr/lib/xorg/modules/amdxmm.so
[ 1826.298] (II) Module amdxmm: vendor="X.Org Foundation"
[ 1826.298] compiled for 1.4.99.906, module version = 2.0.0
[ 1826.324] Loading extension AMDXVOPL
[ 1826.324] Loading extension AMDXVBA
[ 1826.324] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):
[ 1826.326] (II) fglrx(0): Enable composite support successfully
[ 1826.326] (WW) fglrx(0): Option "VendorName" is not used
[ 1826.326] (WW) fglrx(0): Option "ModelName" is not used
[ 1826.326] (II) fglrx(0): X context handle = 0x4
[ 1826.326] (II) fglrx(0): [DRI] installation complete
[ 1826.326] (==) fglrx(0): Silken mouse enabled
[ 1826.326] (==) fglrx(0): Using HW cursor of display infrastructure!
[ 1826.327] (II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
Last edited by EvanPurkhiser (2013-07-22 13:14:56)This was fixed by changing the "Pixel Format" in the catalyst control center to "RGB (Full RGB)".. Somehow it got changed to "YcBcr".
I removed the /etc/ati/amdpcsdb file that the fglrx driver likes to put settings in and did a fresh reinstall of catalyst-test and everything looks good now. Really no idea how the pixel profile got changed. Also noticed that my resolution was much lower than it should have been (which for some reason doesn't affect XBMC which runs in native resolution no matter what?), but that was an easy fix of adding Mode "1920x1080" to my Display section in xorg. -
I have business catalyst website imported in Dreamweaver. But I am unable to find or use database for it. Please help me into this
You might find better help here: Dreamweaver & Business Catalyst
Additional Info: Dreamweaver Help | Dreamweaver-Business Catalyst integration -
System freeze when using catalyst driver and xorg 1.16
As the title says, my computer freezes up when using the catalyst drivers. This happens even when I haven't run startx (happens even when I ssh). Typically I would check my syslog after a crash, right? However, I don't see a syslog in /var/log. How would I go about troubleshooting this?
EDIT:
Okay I discovered journalctl . I ran journalctl --since=today and the point in time at which my computer froze and had to be rebooted was blank. Here is the relevant part of the log...
Feb 26 21:56:47 kodi systemd[554]: Starting Default.
Feb 26 21:56:47 kodi systemd[554]: Reached target Default.
Feb 26 21:56:47 kodi systemd[554]: Startup finished in 11ms.
-- Reboot --
Feb 26 22:04:36 kodi systemd-journal[141]: Runtime journal is using 8.0M (max allowed 84.6M, trying to leave 127.0M free of 838.9M available → current limit 8
Feb 26 22:04:36 kodi systemd-journal[141]: Permanent journal is using 64.0M (max allowed 2.7G, trying to leave 4.0G free of 22.3G available → current limit 2.
Feb 26 22:04:36 kodi systemd-journal[141]: Time spent on flushing to /var is 1.152ms for 2 entries.
My computer froze at about 22:03. That portion is missing from the log so I have no way of knowing what caused the freeze.
EDIT2:
I should also mention that I recently upgraded so I'm running kernel 3.18.6-1-ARCH. Will the catalyst drivers work with this kernel? I did not have a problem with the old kernel, which I think was 3.16
Last edited by necbot (2015-02-27 02:34:49)necbot wrote:I should also mention that I recently upgraded so I'm running kernel 3.18.6-1-ARCH. Will the catalyst drivers work with this kernel? I did not have a problem with the old kernel, which I think was 3.16
First of all - I'm AMD APU user but I've not used Catalyst for a long time, then please be carefull with my opinion. When we can read on Release note, the latest Catalyst driver works with:
- Xorg/Xserver 7.4 and above (up to 1.16)
- Linux kernel 2.6 or above (up to 3.17)
- glibc version 2.2 or 2.3
- POSIX Shared Memory (/dev/shm) support is required for 3D applications
see: http://support.amd.com/en-us/kb-article … Notes.aspx but on AUR we can read, that this driver is for linux < 3.19 (then kernel 3.18 is supported). This is possible because lano1106_fglrx-13.8_proc.patch but, of course, it's not official, upstream patch. From the other hand, I know that Ubuntu's users has seriously problem with Catalyst on Xorg 1.16. -
HOW TO: Install LATEST ATI CATALYST drivers
So ATI/AMD doesn't consistently update the "BootCamp" drivers and as a gamer I want utmost performance out of what I have (of course without OCing). Therefore, I went searching for a solution and found it and I will explain it here, step by step. Forgive me if this has already been posted. Note that I did this in XP and NOT Vista.
1. Download the latest CATALYST drivers from here:
http://game.amd.com/us-en/drivers_catalyst.aspx?p=xp/radeonx-xp
2. Open the driver software as if you were going to install it and let it extract to its default directory. Take note of what that directory is as you will need to know that file path for later. Once it extracts it will move on to an installation. Stop/cancel the installation the first chance you get.
3. REMOVE your currently installed ATI drivers. There are two ways to do this:
-1. If you downloaded the actually CATALYST Software Suite, there will be a program in the folder to where it extracted called "AtiCimUn" that will remove your drivers.
-2. Google "remove ATI drivers" and I think it's the first link that tells you a detailed step by step method of removing the drivers.
4. Restart after successfully removing the drivers.
5. Download MobilityModder here: http://www.driverheaven.net/modtool.php
-If you scroll closer to the bottom of that page, there will be a download link AND instructions for the PROPER method of installing MobilityModder.
6. Run MobilityModder
7. Browse to the directory where the drivers are installed.
8. Click "Modify"
9. When the modification is complete, close MobilityModder and Right Click on "My Computer" then click on Properties
10. Click the "Hardware" tab
11. Click on Device Manager
12. At least one device should have a yellow circle with a black question mark in it. For me, Windows saw it as a "VGA Controller". Right click it and click "Update Drivers"
13. It will ask you some stuff about if you want Windows Update to look for drivers, say "No not this time" and click next
14. Select "Install from a list or specific location{Advanced) and click next
15. Select "Don't search, I will choose the driver to install"
16. Click on the "Have Disk" button
17. Browse to the folder where the ATI drivers were extracted to (MobilityModder will have rewritten the modified files to the same location)
18. The specific file you are looking for is a Configuration file whose icon looks like a white notepad with a yellowish cog that has some metal rod going through it. Click on it and click "open"
19. At this point Windows should recognize which card you have specifically, if not, it will have the entire list of cards that driver can update. If you run into that, just find it in the list.
20. Let windows copy the files, if it tells you that the drivers are not digitally signed, say "continue anyway". It's just an effect of the MobilityModder modifying the files and since it doesn't have a certificate, it's not considered signed.
21. When it's done click finish.
22. Restart
23. Happy new drivers
I'm thinking you might be able to skip the MobilityModder part and just skip straight to directing Windows right to where the drivers are instead of having to mod the files. I'm not sure if it works because I haven't done it but you're welcome to try. If it doesn't work it just means you have to use MobilityModder.
I hope this helps.Update: After using the method described above the drivers did install successfully however, when I loaded some games I noticed that they did not take up the whole screen. No amount of changing the resolution solved the problem.
So I completely removed the drivers and loaded unmodified drivers. I had to find my x1600 from the list and there were actually two but I just took the first one. I let Windows copy the files after warning that it can't confirm they were for my hardware. After a restart I tried my games again and they were taking up the whole screen as they did when I had BootCamps outdated drivers.
So I can say that you CAN skip steps 5-9 (the steps for the mobility modding). You'll just have to find your drivers and some of them do show up multiple times. I'm probably going to try the other x1600 listing just to see what happens. I'm not sure if there's a difference between the same listings (mine was Radeon x1600 followed by another Radeon x1600) but I'm assuming there is or else ATI would put so many >.< -
[Solved]Installed AMD Catalyst drivers. Are they activated?
This must be a really stupid question.
I have installed the Catalyst drivers from the repo, but in KinfoCenter I'm getting something else:
It's not a VMware installation, it's alongside Windows.
So, am I using the Catalyst drivers or not?
Thanks.
Last edited by archie0 (2012-07-10 19:21:22)ewaller wrote:
archie0:
Those pictures are a little larger than permitted by our policy. I usually only concern myself with the byte count, rather than the pixel count. Don't worry about these, but, in the future, please use thumbnails. You can embed image tags to the thumbnail inside of url tags to the full size image. This will display the thumbnail and give the reader the option to click through to the larger image.
Many of our members are on slow or metered links. Thanks
I'm sorry but the image is just 125KB, and that's not much at all, even for a slow connection.
Anyways, is there a bug in KinfoCenter? How does it read those values? I would like to try them manually. Thanks
Last edited by archie0 (2012-07-08 06:21:47) -
Unable to kill the concurrent program
Hi
I have two cocnurrent programs say TEST_PROG1, TEST_PROG2.
if i am submitting TEST_PROG1 then oracle session id and oracle process id are popluating in fnd_concurrent_requests table
where as if iam doing the same with TEST_PROG2 then oracle session id and oracle process id are populating as null.
Is there any configuration problem with the second problem?
And if i amtrying to kill the request of TEST_PROG2, Using the below query
SELECT s.SID,
s.serial#,s.audsid,r.oracle_session_id
FROM fnd_concurrent_requests r,
gv$session s
WHERE 1 =1
AND r.request_id = 2998345;
AND r.oracle_session_id = s.audsid(+);
AND r.request_date > TRUNC(SYSDATE-1)
AND r.status_code NOT IN ('C','E','D','X');
which is returning null .But iam using serial#, audsid to kill the session
using
l_sql := 'alter system kill session '''|| l_sid || ','||l_serial_number||'''';
but iam unable to kill the session as thwy are getting null from the above sql.
Please help me to resolve this.
Thanks
SatyaHI
Followed the link shared and in one of your replied i found the below
I am not sure why there are no values stored in FND_CONCURRENT_REQUESTS table (for some columns) when you submit such reports, and I believe if this is resolved you will be able to see the trace files generated. So, is it possible to register any of these custom reports in one of the standard responsibilities and see if the values in the table are populated and/or the trace file get generated then?
I have added my concurrent program to US HRMS Reports & Processes request group. But still the same problem
Thanks
Satya -
[SOLVED] Rebuild catalyst drivers automatically if kernel updated?
Hi
I use the catalyst proprietary drivers, and I read on the catalyst wiki page that it is possible to automatically rebuild (?) the drivers if the kernel was updated, to prevent the drivers not working on reboot. However, the wiki makes absolutely no sense to me.
I need help installing catalyst_daemon, because I think that catalyst_daemon is the daemon that checks if a rebuild needs to be done. However, simply entering:
pacman -S catalyst-daemon
does nothing, because it complains that catalyst and catalyst-daemon are in conflict.
What do I need to install, and how do I need to configure it, so that fglrx or the catalyst drivers are automatically rebuilt so that I don't get a black screen upon rebooting.
Thanks in advance
Last edited by sheomualjy (2012-04-22 06:22:07)Oh, that sounds good. If I were to use catalyst-hook, would I simply install catalyst-hook? Do I need to add anything else?
EDIT: I just noticed that catalyst-hook also conflicts with catalyst. I am assuming that is for the same reason as you just said, so I am assuming I would remove catalyst to make way for catalyst-hook
Last edited by sheomualjy (2012-04-22 03:59:13) -
CUPS, HP PSC 2355 and "Unable to get list of printer drivers: Unknown"
Hey fellow Archers!
The Introduction
The other day, I installed ArchLinux for the ARM processor on my GoFlex Home. Straight away I installed samba, got it set up and everything works like a charm with explosive transfer-rates compared to the old factory-firmware. Also put on a mysql server to centralize my xbmc database and pyload to download large files without having to have my laptop opened all the time. Have to admit, this Arch Linux is a glorious world!
The Setup
Well, after this positive input, now comes my problem. I wanted to share our printer on our LAN, so I did a little search to quickly find CUPS. Installed it together with all the dependencies, like foomatic, python (which was installed as pyload uses it) and all that stuff.
Changed the /etc/cups/cupsd.conf to listen on 0.0.0.0 and started the daemon.. Woohoo! Turned on the printer, opened the web interface, went to administration -> add printer and selected one of the printers available from this list:
Local printers
CUPS-PDF (Virtual PDF Printer)
HP PSC 2350 series USB MY5BNF4423KJ HPLIP (HP PSC 2350 series)
Seriel port #1
HP PSC 2350 series (HP PSC 2350 series)
HP Fax (HPLIP)
Before I proceed, I want to say that I have tried the following with both of the PSC-entries.
The Problem
Now, i selected the printer and just let the default values be, pressed continue and got this error message:
"Unable to get list of printer drivers: Unknown"
Well, googled it a bit and tried to blacklist lsusb, as well as chmod /dev/bus/usb/001/002 to 665 (even 777). Still the same error message. Also tried to install the printer with hp-setup -i which let me pick a ppd myself; didn't work either. Gave me an error message saying that it was unable to add the printer to cups. I have run out of options, and the almighty sir Google wont give me any solutions other than those which I have tried.
I even get this error message when I try to add cups-pdf (which I also installed oc).
Kind regards,
Rasmus Dencker
Last edited by dencker90 (2011-12-30 17:53:10)Hey fellow Archers!
The Introduction
The other day, I installed ArchLinux for the ARM processor on my GoFlex Home. Straight away I installed samba, got it set up and everything works like a charm with explosive transfer-rates compared to the old factory-firmware. Also put on a mysql server to centralize my xbmc database and pyload to download large files without having to have my laptop opened all the time. Have to admit, this Arch Linux is a glorious world!
The Setup
Well, after this positive input, now comes my problem. I wanted to share our printer on our LAN, so I did a little search to quickly find CUPS. Installed it together with all the dependencies, like foomatic, python (which was installed as pyload uses it) and all that stuff.
Changed the /etc/cups/cupsd.conf to listen on 0.0.0.0 and started the daemon.. Woohoo! Turned on the printer, opened the web interface, went to administration -> add printer and selected one of the printers available from this list:
Local printers
CUPS-PDF (Virtual PDF Printer)
HP PSC 2350 series USB MY5BNF4423KJ HPLIP (HP PSC 2350 series)
Seriel port #1
HP PSC 2350 series (HP PSC 2350 series)
HP Fax (HPLIP)
Before I proceed, I want to say that I have tried the following with both of the PSC-entries.
The Problem
Now, i selected the printer and just let the default values be, pressed continue and got this error message:
"Unable to get list of printer drivers: Unknown"
Well, googled it a bit and tried to blacklist lsusb, as well as chmod /dev/bus/usb/001/002 to 665 (even 777). Still the same error message. Also tried to install the printer with hp-setup -i which let me pick a ppd myself; didn't work either. Gave me an error message saying that it was unable to add the printer to cups. I have run out of options, and the almighty sir Google wont give me any solutions other than those which I have tried.
I even get this error message when I try to add cups-pdf (which I also installed oc).
Kind regards,
Rasmus Dencker
Last edited by dencker90 (2011-12-30 17:53:10) -
[SOLVED]Are X11 and AMD catalyst drivers friends again?
last time i installed linux on my laptop X11 had dropped support fro amd catalyst drivers (proprietary video card drivers), did amd do something about it? did X11 team reconsider? can i use the catalyst drivers on X11 again now? my laptop and it's stupid APU or "dual graphics" aren't playing so nice with the open source radeon drivers.
Last edited by rabcor (2013-06-20 19:16:00)If wine supported skype, i would be more dead set on using linux than using the amd proprietary drivers.
The reason this isn't a big deal to me is mostly because i only use this laptop for 3 things, regardless of OS. Teamspeak 3, Skype, Playing Videos.
I have it set up on a dual boot because neither windows nor linux seem to be reliable on this laptop, the reason is hardware-side, this APU is driving me nuts.
The reason i'm having problems with the radeon drivers is that even if i set my computer to disable the "switchable graphics" on boot it sometimes seems to randomly re-enable it without even notifying me. The reason this is bad is because the switchable graphics cause my laptopt to overheat. If this happens in windows it usually just enters hibernation mode while the heat levels are just barely critical, in linux however it keeps running for a while at critical levels before it'll finally just overeat. I'm hoping that the AMD proprietary drivers can help me solve this on the linux side.
Whichever operating system i can manage to make stop ever using the switchable graphics (thus preventing all overheating) will be the one i will use in the end, but i'm not in any big rush, windows is working decently for me on the laptop right now, and i can patiently wait for the amd proprietary drivers to support X again, since i don't interact much with the computer at all anyways. Using linux would mostly just be to make the laptop look better. Linux seems to be the more likely one to succeed with this task in the end however (because i can optimize/customize it a whole lot more than i ever could windows, and because i'm scared of updating the catalyst drivers in windows because my laptop has often just completely broken upon catalyst driver update in windows.) -
ATI catalyst drivers not working properly in Mac Pro late 2013
Hi, I have a 6-core Mac Pro late 2013 with two D500 ATI graphics cards and installed Windows 8.1 Pro through bootcamp. I have installed the bootcamp drivers while in windows installation, however there is a problem opening the Fire Pro drivers (catalyst drivers). I get a message that says something like "there is no option to change so the software will not run". I also tried to download the ATI drivers directly from their site, but still get the same problem.
This poses a problem for me since I need windows for a specific lighting design software that I work with -Dialux-, and it uses Open GL, which doesn't seem to work in my configuration. Does anyone have any similar problem or solution?
Please help. Thanks.Does the reader show up under USB in System Report?
If the reader is working properly both the reader and an inserted card will show up. -
Troubles installing catalyst drivers
Hi
I have given up having overheating graphics cards, and have decided to switch to the proprietary catalyst drivers for my dual radeon 6870 cards. However, every time I try to install them, something goes wrong and X ends up breaking, or dbus-launch does not work, or whatever.
I have been following the instructions on the arch wiki, and have been using the method where I add the [catalyst] repository to my pacman.conf file.
For my fifth attempt at installing them, I have decided to ask for other peoples assistance. Can someone please give me a step by step guide for how to install the drivers, configure them correctly, and add whatever I need to add to my rc.conf to get the modules to start correctly. Basically, could someone please tell me everything I need to know in order to correctly set up the catalyst drivers. The fantastic arch wiki does not seem to help me in this case...
Thanks in advance,
James*face-palm* Wow, I really feel like an idiot now!
Thanks earsplit, I actually did not notice that section! I thought, in my rush to get X working, that installing the drivers would be all that is necessary! I must have been accustomed to merely installing the xf86-video-ati driver and forgetting about it.
I think my problems have been solved now. I believe my issues stemmed from not blacklisting the radeon module, and not loading the fglrx module! I think it works now.
One last question, before I shut up:
in my /etc/X11/xorg.conf file, there is a section which, by default, reads:
Section "Module"
EndSection
I added load "fglrx" to it, meaning mine now looks like this:
Section "Module"
load "fglrx"
EndSection
Is that all I need to add? Am I missing something? Do I even need to add that at all?
Thanks guys, once this is sorted, I will mark this as solved!
James -
Distorted Screen e350 Chipset Catalyst Drivers
Hi All,
I had a go at loading Arch on my e350 based system yesterday with the idea of having a minimal environment running XBMC, VirtualBox and an Apache server. After a successful install I attempted to install the proprietary Catalyst drivers via the AUR which appeared to go OK. However after running 'aticonfig --initial' and then running startx I was greeted by a less than visually impressive display. When moving the cursor or even typing the screen distorts almost like a tear, I thought that this might be a quirk of running a minimal xterm interface so I then tried to install XBMC.
XBMC suffered from the same distortion/tearing as xterm but additionally the screen resolution was too low to actually cover the whole screen even though XBMC was purportedly outputting at 1080p. When viewing the system info section of XBMC the CPU utilization seemed all over the place and in addition things like CPU and GPU temp just weren't available. This leads me to believe that the catalyst drivers aren't working even though the fglrx modules are loaded and XBMC was able to do sound over HDMI - which I thought was only available through the catalyst drivers? I'm really not sure what to do because there appears to be no way to debug the issue. I've tried re installing the catalyst drivers multiple times now.
The only perhaps useful bit of information was an error that was displayed when ending the x session, something about the display with device id not being found.
I'd really appreciate any help anyone can provide....
Thanks in advance.
BTW. Bravo on the captcha system on the registration page - never seen one like that before!
Last edited by dominic7il (2013-12-20 13:15:32)Yes I've just tried enabling the tear free setting and no difference. I've also tried the OSS drivers (now vdpau is supported) which seem to give a much better result (in xterm at least). Unfortunately XBMC doesn't even load up with those drivers it just flashes black back and forth between the terminal. It's a nightmare - really appreciate any help about now.
-
Gnome 3 striped panel using Catalyst driver
I'm currently using the properietary ati catalyst driver by necessity, not choice. The open source driver does not have good power management and in particular will not control the fan properly. This is a well known bug and has been acknowledged on this and other forums often. Honestly, the only reason I can think of for anybody using the open source ati driver is if they 1) have an old gpu 2) are using a desktop pc and don't notice the sound 3) notice the sound and heat but know no better. After installing gnome 3, the panel ends up looking like this:
which isn't even my screenshot. This was posted on a stackexhange forum and the solution provided was to simply use the open source drivers.
I'm hoping that someone here has found the correct solution, although I'm not even sure if one exists yet. It's just incredibly strange that gnome 3 would have this sort of problem when no other panel I know of, including Unity, does.I have seen enough of this. Conclusion is, if you have to use Catalyst (properietary), forget about GNOME Shell for a while. Not only that top panel, but also there exists several corruptions here and there with Mutter(?) + Catalyst. Use the fallback mode if you can't get any further, or better use Compiz+Cairo-Dock to completely replace the GNOME window manager in GNOME/GTK3.
Even if you can get the shell working, it's not worth using it at this stage. Check later. -
X fails with new catalyst drivers
I'm running 64bit arch and i just upgraded to the new catalyst drivers from AUR (9.4). When I try to run xorg now, it fails (screen just goes black and I can't switch to any of the vcs or kill X). The X log file says that it can't load the glx module because it doesn't exist. I'm not entirely clear on modules and how they work, but what should I do to try and get X working?
Gratias vobi ago!
Last edited by Qvintvs (2009-03-28 17:08:54)I'm running a Radeon HD 4870 x2. I've been trying some things, and now I dont get the missing glx error. I do get these errors:
(EE) Failed to load module "dri2" (module does not exist, 0)
(EE) Failed to load module "record" (module does not exist, 0)
(EE) fglrx(0): Unknown EDID version 0
Though it appears that X keeps going past all three of these. Here's my entire log: http://pastebin.com/f5153ff39 . Here's the xorg.conf file aticonfig generated with the unused device, monitor, and screen sections commented out: http://pastebin.com/f1e765d83 .
Any help on where to go next would really be appreciated, I've been at this for over a day now.
jun, I think the wiki discourages getting the drivers from the amd site directly, though given the success (or lack thereof) I'm having with the AUR drivers, I can't say (personally) that they're any better.
Last edited by Qvintvs (2009-03-29 19:18:06)
Maybe you are looking for
-
How can I display an animated graphic in a PDF file or slide show?
I have a simple animated graphic comprising eight layers in a PSD file created in Photoshop. Can I create a version of this which can be included in a PDF file or a slideshow. I do not want to display it on the web. Any suggestions would be welcome.
-
Upload Material master with long text using LSMW
Hello, i want ot upload material master data via MM01 using LSMW in following views: basic data 1 ,2, purchasing, purchase order text, plant data 1,2. i have to upload long text in purchase order text with length more then 132 char. (approx 700 char
-
Hello all! (JDev 11 ADF BC) I try to use af:Treetable component based on view. In jsf page i have af:treetable and simple button. Button updating some info in my view. I need to refresh af:treetable component..I do this with partial trigger..All work
-
Hi, I am new to this bpel.I want to ask a basic question regarding bpel fault handling management frmawork .. My BPELProcess1 has just a throw activity with receive and reply activity.and I throw a bindingfault there. Then I added two xml files(fault
-
I've not received a crash ID