[Ubuntu-x-swat] [Bug 1787845] [NEW] Broken xdriinfo on Ubuntu 18.04 breaks driconf
Public bug reported: driconf doesn't work on Ubuntu 18.04. The reason is that xdriinfo fails with "Screen 0: not direct rendering capable." There appears to be a fix for this upstream: https://cgit.freedesktop.org/xorg/app/xdriinfo/commit/?id=6273d9dacbf165331c21bcda5a8945c8931d87b8 Building my own xdriinfo from the upstream source code fixed the problem for me. Please consider updating xdriinfo for Ubuntu 18.04 to unbreak driconf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-utils 7.7+3build1 Uname: Linux 4.18.0-rc7+ x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 16:23:03 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Vega [Radeon Vega 8 Mobile] [1458:d000] InstallationDate: Installed on 2018-07-23 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-rc7+ root=UUID=78fe8e76-c2c5-4adb-8874-d61d2c583a38 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: x11-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: x11-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1787845 Title: Broken xdriinfo on Ubuntu 18.04 breaks driconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1787845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 949286] Re: System Crash / Restart
Your Xorg log looks like you're using the open-source Radeon driver, not Fglrx. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/949286 Title: System Crash / Restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/949286/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 939858] Re: Switch user does not work
I think the problem is that you're simply running out of video memory. Each user session runs in its own Xserver. Each Xserver needs video memory for various render and display buffers. A number of factors influence video memory usage: * number and size of attached monitors * virtual desktop size * driver features requiring additional video memory per monitor: - monitor rotation - tear-free desktop - OpenGL overlay - stereo 3D * 3D OpenGL applications * composite manager * 2D applications If the system has been running for a while, video memory fragmentation can also prevent successful allocation of the required buffers even if the raw amount of free memory would be sufficient. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/939858 Title: Switch user does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/939858/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 816705] Re: fglrxinfo crashed with SIGSEGV in XF86DRIQueryExtension()
This problem usually occurs when the Mesa libGL is used with our 3D driver or our libGL with the Mesa 3D driver. Please ensure that fglrx is correctly installed and active. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/816705 Title: fglrxinfo crashed with SIGSEGV in XF86DRIQueryExtension() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/816705/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 818263] Re: package fglrx 2:8.821-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
RV350 is not supported by fglrx after 8.59x. Ubuntu 11.04 needs at least fglrx 8.84x. Please use the open-source drivers included in Ubuntu 11.04 for your hardware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/818263 Title: package fglrx 2:8.821-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/818263/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 800649] Re: Top Taskbar misdisplayed
Looks more like a Unity problem to me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/800649 Title: Top Taskbar misdisplayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/800649/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 793576] Re: after update-error loading OS-could not find module ath_pci
There is zero information in this bug report. I don't know what ath_pci is. I don't think it is related to fglrx. You'd find more help in a support forum. I doubt this report is appropriate for a bug tracker. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/793576 Title: after update-error loading OS-could not find module ath_pci ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 758609] Re: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top
This sounds familiar. Unchecking /apps/metacity/general/capture_before_unmap in gconf-editor should solve the issue. Last time I discussed this with Bryce Harrington he assured me that this was a bug in metacity, not in fglrx. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/758609 Title: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 758609] Re: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top
Log out and log back in after unchecking capture_before_unmap. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/758609 Title: natty beta Ubuntu Classic (No effects) SDL|openGL window always on top ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 793662] Re: package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build
Fglrx version 8.780 doesn't support kernel version 2.6.38. You need at least an 8.84-based version of fglrx. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/793662 Title: package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 545257] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()
Why is this being resurrected. This was not a bug to begin with, but more a support request. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/545257 Title: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion() ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 776543] Re: Xorg seg fault
Please try this after installing fglrx: * Uninstall fglrx if it's still installed * rm -rf /etc/ati * Install fglrx again * Reboot Does X start successfully after this? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/776543 Title: Xorg seg fault ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 781406] Re: package fglrx 2:8.840-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
DKMS failed to build the fglrx kernel module for kernel 2.6.39. Kernel 2.6.39 is not supported by fglrx yet. If you're going to use the fglrx driver, you'll need to stick with the stock 2.6.38 kernel until fglrx is updated to support 2.6.39. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/781406 Title: package fglrx 2:8.840-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 778831] Re: Ubuntu doesn't boot to unity or effects without fglrx driver installed
Whoever queued this bug to fglrx, please read the description again. This is not a bug in fglrx, it actually says that fglrx is the only driver that works for this user. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/778831 Title: Ubuntu doesn't boot to unity or effects without fglrx driver installed ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 780144] Re: Unable to enable fglrx driver since updated to 2.6.38-8
You need Catalyst 11.4 or newer (fglrx 8.84 or newer) to support kernel version 2.6.38. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/780144 Title: Unable to enable fglrx driver since updated to 2.6.38-8 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 763005] Re: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl
@robinl: I've seen that problem. The updates very infrequently when there is a high FPS application running, for example glxgears or fgl_glxgears. I believe this is a bug in compiz. Setting Wait for vertical refresh under 3D-More Settings to Always on works around the problem for me because it forces the applications to a lower frame rate which doesn't overwhelm compiz. Do you have any applications running that constantly redraw at a very high frame rate? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/763005 Title: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747729] Re: fglrx crashes X server on startup
@Beat: What's the output for dkms status? Is the kernel module compiled and installed correctly for the -pae kernel? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747729 Title: fglrx crashes X server on startup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747729] Re: fglrx crashes X server on startup
That looks like there is no fglrx kernel module installed for the -pae kernel. Normally DKMS should build the kernel module automatically when you boot your -pae kernel. If that's not happening for some reason, that may be a bug in DKMS. You can manually tell DKMS to build the fglrx kernel module for your -pae kernel with: sudo dkms build -m fglrx -v 8.840 -k 2.6.38-8-generic-pae sudo dkms install -m fglrx -v 8.840 -k 2.6.38-8-generic-pae Then reboot to the -pae kernel. Does that work? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747729 Title: fglrx crashes X server on startup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 763005] Re: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl
The Catalyst Control Center has two vblank settings. One is the global tear-free setting under Display Option. The other one is Wait for vertical refresh under 3D-More Settings. Does it help if you set the latter to Off, unless applications specifies and restart X? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/763005 Title: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747729] Re: fglrx crashes X server on startup
Thanks, Beat, for following up. Your problem seems to be solved, but it's different from the problem originally reported by Vladimir. @Vladimir: I saw the same problem when I updated my developer system from Ubuntu 10.10 to 11.04 earlier today. After running sudo aticonfig --initial -f X could start successfully on my system. Please try if this solves your problem as well. @Ben: your log file doesn't show any useful information regarding fglrx because you were using the Radeon driver at the time. Please also try sudo aticonfig --initial -f, which will fix up your xorg.conf and wipe out any stale settings from the previous driver version. If that still gives you problems, please attach an Xorg.0.log produced with the failing driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747729 Title: fglrx crashes X server on startup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 763005] Re: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl
@robinl: What about the sync-to-vsync setting in CompizConfig Settings Manager (AKA ccsm)? As already reported by other users, this seems to be the main problem leading to poor compositor frame rates on Ubuntu 11.04 with fglrx, regardless of raw hardware performance. Some users with low end or integrated graphics are still experiencing lag even with sync-to-vsync disabled in ccsm. See Nick's report above for example. That's why I was suggesting to try the other vsync and tear-free options in the Catalyst Control Center. You have a fairly powerful discrete graphics card, so I would not expect your system to be affected by long lag as reported by Nick. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/763005 Title: Fglrx with Compiz's Sync to Vblank makes Unity/Compiz plugins to crawl ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 769911] Re: System freeze after login in 11.04
Why was this queued to fglrx-installer? This is on NVidia hardware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/769911 Title: System freeze after login in 11.04 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 770669] Re: package fglrx 2:8.840-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
The 8.840 driver doesn't support kernel 2.6.39. Please use the 2.6.38 kernel included in Ubuntu 11.04. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/770669 Title: package fglrx 2:8.840-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 749921] Re: package fglrx 2:8.840-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
Your DKMS build log indicates that it fails to build an fglrx 8.831 kernel module (Catalyst 11.3 by the looks of it). That version of fglrx is incompatible with your 2.6.38 kernel. Please uninstall fglrx 8.831 before installing fglrx 8.84x. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/749921 Title: package fglrx 2:8.840-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747576] Re: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion()
Please attach your /var/log/Xorg.0.log and /etc/X11/xorg.conf. I suspect that after the update you're not using the fglrx driver in the Xserver for some reason. But the fglrx libGL is active at the same time. The fglrx libGL is incompatible with the open-source X drivers. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747576 Title: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion() ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747729] Re: fglrx crashes X server on startup
Your Xorg log shows that you're using some unusual fglrx options in your xorg.conf. Looks xorg.conf was originally created by a really old version of fglrx. Could you try the following steps to reinitialize the fglrx configuration: 1) Reboot the system, in the boot loader select Recovery mode 2) When prompted, select netroot Drop to root shell prompt with networking 3) In the root shell run aticonfig --initial -f 4) Reboot normally See if that solves your problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747729 Title: fglrx crashes X server on startup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 748883] Re: package fglrx 2:8.840-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
Your DKMS build log shows that it fails to build the 8.821 kernel module (Catalyst 11.2). Make sure you uninstall any previous versions of fglrx before installing fglrx 8.84x. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/748883 Title: package fglrx 2:8.840-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747576] Re: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion()
As I suspected, you're running the radeon 2D driver with the fglrx 3D driver, which don't work together. fglrx is commented out in xorg.conf and replaced with ati. Revert that change, reboot and all should be well. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/747576 Title: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion() ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 734784] Re: desktop crashes out if extra visual effects are applied
If you're running Ubuntu in a virtual machine, this can't be a bug in fglrx. In the virtual machine you can't access the Radeon graphics device directly. So you can't use the fglrx driver. Having fglrx installed without using it can cause problems. So if you have fglrx installed, uninstall it. It's no use to you inside a virtual machine. (There are special cases where you can make a dedicated graphics card directly available to the virtual machine, but then you can't use the same graphics card in the host OS, Windows 7 in your case. I don't think this applies to you). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/734784 Title: desktop crashes out if extra visual effects are applied ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 709505] Re: [MASTER] fglrx failed to install/upgrade due to being incompatible with 2.6.38 kernel
Catalyst 11.2 may have worked with earlier 2.6.38 RCs, but broke with later RCs and the final versions due to the renaming of acquire/release_console_sem to console_lock/unlock. That said, the kernel compatibility is fixed by a small patch. The Xserver is the bigger problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/709505 Title: [MASTER] fglrx failed to install/upgrade due to being incompatible with 2.6.38 kernel ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 730278] Re: Xorg fails to start with fglrx in mult-monitor mode with right-rotated monitor
This problem should be fixed in the 8.80 driver release (Catalyst 10.12 and later). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/730278 Title: Xorg fails to start with fglrx in mult-monitor mode with right-rotated monitor ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 710255] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: попытка перезаписи '/usr/share/fglrx/atigetsysteminfo.sh', котор(ый)ая также находится в пакете xorg-driver
Radeon XPress 1250 is not supported by the current fglrx driver. I recommend you uninstall fglrx and use the open-source radeon driver instead. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/710255 Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: попытка перезаписи '/usr/share/fglrx/atigetsysteminfo.sh', котор(ый)ая также находится в пакете xorg-driver-fglrx 2:8.593-0ubuntu1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 697983] Re: Click Deslkop and systemsettings crashes every time
Looks more like a support request than a bug report. There are no log files or configuration files and no information about the hardware configuration. I don't see any indication in the report that you're using fglrx. But the symptom looks somewhat familiar. It usually happens when you're using a libGL that's incompatible with the driver in use. It could be you're using the Mesa libGL with the fglrx driver or the fglrx libGL with an open-source graphics driver. It could also be that you have fglrx installed but using unsupported hardware. Need more info: * /var/log/Xorg.0.log * /etc/X11/xorg.conf * output of dpkg -l | grep fglrx * output of ls -l /usr/share/ati * output of lspci -vnn -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/697983 Title: Click Deslkop and systemsettings crashes every time ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 684171] Re: [Amarok] docking all three content windows into Amarok main window crashes xserver
Please attach /var/log/Xorg.0.log and /var/log/Xorg.0.log.old just after the Xserver crashed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. https://bugs.launchpad.net/bugs/684171 Title: [Amarok] docking all three content windows into Amarok main window crashes xserver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 662347] Re: multiple monitor config issue. Worked 10.04. Prob 10.10
fglrx doesn't support growing the primary surface at runtime beyond the initial size. You can work around the problem by making the Virtual screen size bigger in your xorg.conf to allocate a larger primary surface during Xserver startup. -- multiple monitor config issue. Worked 10.04. Prob 10.10 https://bugs.launchpad.net/bugs/662347 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 671088] Re: xorg.conf error in fglrx-installer
The same libglx.so is loaded in both cases. It's very unlikely that the change in performance is due to libglx being specified in xorg.conf or not. Just in case, I tried it but I can't reproduce this effect here. Are there any other differences between your test configurations? One thing that has a big influence on 3D performance is desktop effects. Which desktop environment/window manager/ composite manager are you using? -- xorg.conf error in fglrx-installer https://bugs.launchpad.net/bugs/671088 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 669179] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
From the DKMS log: DKMS make.log for fglrx-8.723.1 for kernel 2.6.32-25-generic (x86_64) Sun Oct 31 17:56:22 GMT 2010 AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher Makefile:99: *** mixed implicit and normal rules. Stop. Makefile:99: *** mixed implicit and normal rules. Stop. build failed with return value 2 Do you have a bad version of make installed? What do you get when you run which make? What does make --version report? -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/669179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 669577] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
Ubuntu 10.04 shipped with a 2.6.32 kernel. You upgraded the kernel to 2.6.34. The 8.723 driver doesn't support kernel 2.6.34. Try a current Catalyst release. -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/669577 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 666807] Re: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Your Xorg.0.log shows you're using the Intel driver. So I guess your laptop has Switchable graphics and the Intel graphics device is the one that's enabled by default. The only way for you to use the RadeonHD 4330 under Linux at this time is to disable the Intel graphics in the BIOS setup. If your BIOS setup doesn't have such an option, or if your laptop doesn't have a hardware MUX to connect the Radeon to the display outputs, you're stuck with the Intel integrated graphics under Linux. -- package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/666807 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 666951] Re: package fglrx 2:8.723.1-0ubuntu5 [modified: lib/fglrx/modprobe.conf] failed to install/upgrade: fglrx kernel module failed to build
There are no log files attached that provide any details of the kernel module build failure. However, Rage 128 is not supported by fglrx. Please use the open-source ATI driver included in Ubuntu. -- package fglrx 2:8.723.1-0ubuntu5 [modified: lib/fglrx/modprobe.conf] failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/666951 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 665807] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
You're using kernel 2.6.35, which is not supported by the 8.723 driver version. Furthermore you don't have the matching kernel headers installed. Catalyst 10.10 should work if you install the matching kernel headers to your 2.6.35 kernel. -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/665807 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 663867] Re: package fglrx 2:8.723-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
Catalyst 10.4 is half a year old. It doesn't support Maverick. The 8.780 driver included in Maverick does work though. -- package fglrx 2:8.723-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/663867 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 663567] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
In DKMSBuildLog.txt: /bin/sh: gcc: not found How is that even possible? dkms depends on gcc. Something is severely broken with your system. -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/663567 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 660938] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
The 8.723 fglrx driver you're using doesn't support kernel 2.6.35. -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/660938 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 660679] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
Can't tell what went wrong from the attached log files. Try running this in a terminal window: find /var/lib/dkms/fglrx -name *.log | while read name; do echo === Dump of $name ===; cat $name; done dkms.log and attach the resulting dkms.log to this bug report. -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/660679 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 658170] Re: ati catalyst proprietary display driver not working after upgrade from 10.4 to 10.10 (amd64 ATI Radeon HD 4650)
The hotfix driver doesn't support Ubuntu 10.10 yet. The 8.780 driver included in Ubuntu 10.10 does and it has the same workaround as the hotfix driver. Use the fglrx that comes with Ubuntu 10.10. This is the only driver that supports Ubuntu 10.10 until Catalyst 10.10 is release on amd.com. -- ati catalyst proprietary display driver not working after upgrade from 10.4 to 10.10 (amd64 ATI Radeon HD 4650) https://bugs.launchpad.net/bugs/658170 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 658170] Re: ati catalyst proprietary display driver not working after upgrade from 10.4 to 10.10 (amd64 ATI Radeon HD 4650)
If you didn't install the driver using jockey (the HW manager) you need to run aticonfig --initial and reboot to activate the driver. -- ati catalyst proprietary display driver not working after upgrade from 10.4 to 10.10 (amd64 ATI Radeon HD 4650) https://bugs.launchpad.net/bugs/658170 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 656439] Re: package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build
Looks like you need to install linux-headers-2.6.35-22-generic. fglrx depends on linux-headers|linux-headers-generic, which can be satisfied by different versions of kernel headers. You need to make sure that you have the ones matching the kernel you're actually running. -- package fglrx 2:8.780-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/656439 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 642518] Re: [MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx
For users of Catalyst 10.9, there is now a hotfix release at http://support.amd.com/us/kbarticles/Pages/GPU83ATICatalystLinuxHotfix.aspx. -- [MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx https://bugs.launchpad.net/bugs/642518 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to linux-restricted-modules-2.6.24 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 646301] Re: package fglrx 2:8.780-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
*** This bug is a duplicate of bug 609938 *** https://bugs.launchpad.net/bugs/609938 DKMSBuildLog.txt shows that it's trying to build 8.723. But DkmsStatus.txt shows that 8.780 source code is installed. Is DKMS confused? Or does the real problem occur before DKMS tries to build the kernel module and your DKMSBuildLog.txt is a stale version from a previous attempt to install 8.723? -- package fglrx 2:8.780-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/646301 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 642518] Re: [MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx
@Nicolas Delvaux: Correct. Catalyst drivers on amd.com are not fixed yet. We're working on getting the fix into the next Catalyst release in October. -- [MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx https://bugs.launchpad.net/bugs/642518 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to linux-restricted-modules-2.6.24 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 593272] Re: python2.6 crashed with SIGSEGV in XF86DRIQueryExtension()
Sorry, I had a typo in my request. I need the output of ls -l /usr/lib/libGL* Either way, if you uninstalled fglrx, the problem is gone and no one else has this problem, I guess this bug report can be closed. -- python2.6 crashed with SIGSEGV in XF86DRIQueryExtension() https://bugs.launchpad.net/bugs/593272 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 593272] Re: python2.6 crashed with SIGSEGV in XF86DRIQueryExtension()
This usually happens when the wrong libGL is in use. Either fglrx is installed but a stale libGL is in /usr/lib, or fglrx is installed but not actually in use (not configured in xorg.conf). To know what's going on I'd like to see Xorg.0.log and xorg.conf from an affected system as well as the output of ls -l /usr/lib/ligGL* ls -l /usr/lib/fglrx -- python2.6 crashed with SIGSEGV in XF86DRIQueryExtension() https://bugs.launchpad.net/bugs/593272 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 609938] Re: fglrx fails build on 2.6.35-10-generic
This happens every time Ubuntu updates their kernel and/or Xorg version and leaves the old fglrx driver in place that was never designed to work with those new X.org and kernel versions. Maybe one way to save users this kind of trouble in the future would be to add versioned dependencies to fglrx to make it conflict with kernel or X.org versions newer than what was in the last stable Ubuntu release. This way, if a user explicitly or implicitly updates their X.org or kernel to a new major version, they'd be forced to uninstall fglrx first. -- fglrx fails build on 2.6.35-10-generic https://bugs.launchpad.net/bugs/609938 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 617881] Re: package fglrx-kernel-source 2:8.593-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
You're trying to install our Legacy driver on a current OS. That's not going to work. The last Ubuntu version supported by the legacy driver was Ubuntu 8.10. Your RS690 (Radeon X1200) is not supported by the current proprietary driver. So your only option on current Ubuntu versions is the open source driver. In my experience it works well on RS690 including desktop effects. I recommend you uninstall the proprietary fglrx driver. -- package fglrx-kernel-source 2:8.593-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/617881 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623544] Re: package fglrx-kernel-source 2:8.593-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
The 8.593 driver you're using is the last one that works on R5xx-based cards, such as your X1600. However, that driver doesn't support any Ubuntu version newer than Ubuntu 8.10. On Ubuntu 10.04 your only choice for a graphics driver is the open- source Radeon driver that ships with Ubuntu. That driver should give you desktop effects. It may not work very will with games though. I recommend you uninstall fglrx. Having fglrx installed breaks the Radeon driver. Hope this helps ... -- package fglrx-kernel-source 2:8.593-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/623544 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 545257] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()
You installed fglrx but you didn't configure Xorg to actually use it. You're still using the RADEON driver. Having fglrx installed breaks the open-source 3D driver in the way you're experiencing. To activate fglrx run the following command and reboot: sudo aticonfig --initial -f -- gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion() https://bugs.launchpad.net/bugs/545257 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen
I noticed you're using an nVidia MCP51 chipset. I've seen other reports of our driver hanging systems with that chipset. -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 592783] Re: page fault on read access in libgl.so.1
The problem sounds like it's using the wrong version of libGL.so.1. Check the output of ldd /usr/bin/fgl_glxgears for example. If it uses libGL.so.1 from /usr/lib, that's wrong. If you're using the Ubuntu packages of fglrx, it should be using /usr/lib/fglrx/libGL.so.1 and there should be no /usr/lib/libGL.so*. -- page fault on read access in libgl.so.1 https://bugs.launchpad.net/bugs/592783 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 596620] Re: fglrx from x-updates ppa crashes
Adding a BusID line to the fglrx Device section in xorg.conf should fix this. Just regenerating your xorg.conf with aticonfig --initial -f should take care of this. -- fglrx from x-updates ppa crashes https://bugs.launchpad.net/bugs/596620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 592783] Re: page fault on read access in libgl.so.1
Hmm, I looked at your Xorg.0.log and lspci output. You're using a Mach64-based card. This card is not supported by the fglrx driver. In your case having fglrx installed actually breaks the Mach64 driver. I recommend you uninstall fglrx. That will give you as much functionality and performance as you'll be able to get on this hardware. -- page fault on read access in libgl.so.1 https://bugs.launchpad.net/bugs/592783 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Have you tried it with the latest Catalyst driver (Catalyst 10.6, driver release 8.743)? To update using generated Ubuntu packages, download Catalyst into an empty directory and run ati-driver-installer...run --buildpkg dpkg --install *.deb aticonfig --initial -f and reboot. -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 580392] Re: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build
Kernel version 2.6.33 is not supported by this driver. There are unofficial patches floating around to make fglrx compile on kernel 2.6.33 and 2.6.34, if you're feeling adventurous. -- package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/580392 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 578736] Re: fglrx broken (no 3D, jerky movements scrolling).won't uninstall
Looks like a version mismatch between the kernel module and the user- space X driver. The kernel module seems to come from Catalyst 10.4, the user-space driver comes from the fglrx-package included in Ubuntu. I'd recommend uninstalling all versions of fglrx that you have installed, make sure that dkms doesn't have any old fglrx kernel module versions hanging around and then reinstall the driver, either Catalyst or the driver in Ubuntu, but not both. -- fglrx broken (no 3D, jerky movements scrolling).won't uninstall https://bugs.launchpad.net/bugs/578736 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 577906] Re: No login screen at startup
At this point I see no evidence of a driver bug. Is the problem reproducible after uninstalling fglrx? If yes, it's definitely not a bug in fglrx. -- No login screen at startup https://bugs.launchpad.net/bugs/577906 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
@SunnyDrake: When you install the Catalyst driver from amd.com, make sure you uninstall the fglrx packages included in Ubuntu first. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 577906] Re: No login screen at startup
Your xorg.conf looks like it wasn't generated by aticonfig. Try if running this as root fixes the problem: aticonfig --initial -f -- No login screen at startup https://bugs.launchpad.net/bugs/577906 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 577906] Re: No login screen at startup
Your Xorg.log.auto looks OK. Xorg.log.manu looks incomplete, like the output of the Xserver on the console it was started from. Either way, there is no more crash or segault. The black screen when you start X without any clients connecting to the Xserver is normal. As far as I can tell, the Xserver and graphics driver are working now. Not sure why GDM is still not working. Can you reboot, let GDM fail, reboot again into recovery mode and grab copies of /var/log/Xorg.0.log and /var/log/Xorg.0.log.old? If the Xserver is still crashing with GDM, these log files will show it. -- No login screen at startup https://bugs.launchpad.net/bugs/577906 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 577906] Re: No login screen at startup
I don't see anything wrong with the log files. X starts, apparently in the monitor's native resolution (1920x1080). Then there is a VT switch and finally it looks like a clean shutdown. No evidence of a crash. What exactly are the symptoms of the problem you're observing now? The only unexpected thing is the VT switch. Did you switch VT before copying the log files? -- No login screen at startup https://bugs.launchpad.net/bugs/577906 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
@icosena: make sure you don't have an old version of libGL laying around in /usr/lib. In Ubuntu Lucid there should be no /usr/lib/libGL.so*. If you have any version of libGL left there, try removing it (keep a backup just in case) and see if the problem goes away. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 574644] Re: X will not start and crashes after upgrade from Karmic
Current versions of fglrx don't support Radeon X700 hardware. Only Radeond HD 2xxx and newer is supported. BTW, the same applied to Ubuntu 9.10 and 9.04. You should continue using the Radeon driver. Do not install fglrx on your system. -- X will not start and crashes after upgrade from Karmic https://bugs.launchpad.net/bugs/574644 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 355533] Re: fglrx on Aspire 5672 (Radeon X1400) server freeze at startup
Radeon X1400 is not supported by current fglrx releases. Fglrx currently supports Radeon HD 2xxx and later. -- fglrx on Aspire 5672 (Radeon X1400) server freeze at startup https://bugs.launchpad.net/bugs/355533 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 568963] Re: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
You're using Xserver 1.8. Version 1.8 is not supported by the driver yet. -- package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 https://bugs.launchpad.net/bugs/568963 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 568963] Re: package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Check your apt sources. Maybe you're using some non-standard apt repository that already has Xserver 1.8. -- package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 https://bugs.launchpad.net/bugs/568963 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 567967] Re: Mounting a system from LG's HL-DT-ST DVD-ROM GDR-H30N makes Xorg to freeze
Bryce, Alberto clearly stated that he gets the same symptoms when using NVidia graphics. This is clearly not a bug in fglrx. -- Mounting a system from LG's HL-DT-ST DVD-ROM GDR-H30N makes Xorg to freeze https://bugs.launchpad.net/bugs/567967 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 552644] Re: Lucid Lynx 64 bit nightly build hangs on boot
@Alberto, Matthew: I don't think it's a problem with the kernel module. Matthew's lsmod command actually shows that the kernel module is loaded. The error messages are from the Xorg log. It's the user-space fglrx_drv.so that can't be found. Maybe Xorg isn't looking in the right place for some reason. @Matthew: It would help if you filed a new bug report including all the relevant configuration and log files. You can use ubuntu-bug fglrx from a terminal to compile all the log files automatically. -- Lucid Lynx 64 bit nightly build hangs on boot https://bugs.launchpad.net/bugs/552644 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 568591] Re: Non-proprietary (Ubuntu's default) video driver eventually switches monitor to a fuzzy mode (ATI/AMD video hardware)
If this is a problem with the open-source drivers, it shouldn't be reported against fglrx-installer. -- Non-proprietary (Ubuntu's default) video driver eventually switches monitor to a fuzzy mode (ATI/AMD video hardware) https://bugs.launchpad.net/bugs/568591 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 449867] Re: xrandr reports incorrect maximum screen size
@mback: Your xorg.conf specifies the virtual size as 2048x2048. If you set it to 3200x1200, it should work fine. I guess this bug can be closed as Invalid. -- xrandr reports incorrect maximum screen size https://bugs.launchpad.net/bugs/449867 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 551475] Re: amdcccle settings do not persist lucid
The Catalyst Control Center stores its configuration settings in xorg.conf. If you've used the GNOME monitor applet in the past, it applies its settings when you log in and overrides any settings stored in xorg.conf. Try deleting ~/.config/monitors.xml, log out and log back in. Does that make settings you changed in the Catalyst Control Center effective? -- amdcccle settings do not persist lucid https://bugs.launchpad.net/bugs/551475 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561982] Re: Unusable Area on main screen in 2 screen setup
It could be a bug in Compiz too since the corruption only occurs when compiz is used. If someone reproduces it with fglrx and fails to reproduce it with radeon with the same set of monitors it would show that the problem is likely in fglrx. That would require hardware with 3D support in both fglrx and radeon. -- Unusable Area on main screen in 2 screen setup https://bugs.launchpad.net/bugs/561982 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 563464] Re: Window manager does not load
Your Xorg.log file indicates that you're still using the Radeon driver and DRI is disabled. That's why compiz is not starting. Sounds like you're using your own session startup script. Try replacing compiz with metacity, that way you'll at least be able to move your windows around and get through your finals. Then you can figure our what went wrong with the fglrx installation. I'm quite sure there is already a bug report for the trying to overwrite '/etc/ati/signature' problem. Hope this helps. -- Window manager does not load https://bugs.launchpad.net/bugs/563464 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561982] Re: Unusable Area on main screen in 2 screen setup
Felix, all your statements are correct. xrandr --output CRT2 --left-of DFP4 used after login to get screen on left side. I can not find place in amdcccle to do this move. You should be able to move the monitors around in CCC-LE by drag-and- drop to change their relative positions. -- Unusable Area on main screen in 2 screen setup https://bugs.launchpad.net/bugs/561982 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561982] Re: Unusable Area on main screen in 2 screen setup
The second LCD is an analog TV connected to lower DVI connector with an adapter. Can you confirm what kind of display and connector this is? Is it a TV with SVideo, Composite (1 RCA) or Component video (3 RCA) input? Or is it an LCD monitor with VGA (15-pin D-Sub connector) input? -- Unusable Area on main screen in 2 screen setup https://bugs.launchpad.net/bugs/561982 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561982] Re: Unusable Area on main screen in 2 screen setup
Ok, let me restate the problem: Monitors positioned incorrectly and visual corruption in 2 monitor setup with monitors positioned side by side Your xorg.conf clearly shows that CRT2 should be right of DFP4. But your screenshot shows the opposite positioning. I'm assuming the original screenshot in comment #1 was generated with the xorg.conf in comment #1. Is this correct? -- Unusable Area on main screen in 2 screen setup https://bugs.launchpad.net/bugs/561982 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 552644] Re: Lucid Lynx 64 bit nightly build hangs on boot
@Proxess: This shouldn't be necessary. The fglrx installation disables KMS by blacklisting the radeon kernel module. -- Lucid Lynx 64 bit nightly build hangs on boot https://bugs.launchpad.net/bugs/552644 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561665] Re: fglrx/glx/xorg crashes on boot 10.4 ati x700
X700 is not supported by the current fglrx driver. Your Xorg log file shows that you're actually still using the open-source Radeon driver. Fglrx replaces libGL.so and libglx.so with incompatible versions, which is causing your problems. If you uninstall fglrx the Radeon driver should work without problems. -- fglrx/glx/xorg crashes on boot 10.4 ati x700 https://bugs.launchpad.net/bugs/561665 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561982] Re: Unusable Area on main screen in 2 screen setup
Looks like normal behaviour to me. The CRT uses a lower resolution, so you end up with dead space. You can change the resolution on the CRT to match the vertical size of the DFP. -- Unusable Area on main screen in 2 screen setup https://bugs.launchpad.net/bugs/561982 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561665] Re: fglrx/glx/xorg crashes on boot 10.4 ati x700
Did you reboot after uninstalling fglrx? I highly recommend you do that. Either way, this is not a bug in fglrx. I recommend closing this bug. If your problem persists, report a new bug against the radeon driver and make sure you include log files generated without fglrx installed. -- fglrx/glx/xorg crashes on boot 10.4 ati x700 https://bugs.launchpad.net/bugs/561665 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560364] Re: Random system freeze
This bug was fixed in fglrx-8.723. Please update. -- Random system freeze https://bugs.launchpad.net/bugs/560364 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 555158] Re: glxinfo crashed with SIGSEGV in XF86DRIQueryExtension()
Hi Thiago, your hardware is not supported by the fglrx driver. Only R6xx and later hardware is supported by the current driver version. The problem is that you're using the radeon driver while fglrx is installed. The fglrx libGL and libglx is incompatible with the radeon driver. Uninstall fglrx and the radeon driver should work correctly. -- glxinfo crashed with SIGSEGV in XF86DRIQueryExtension() https://bugs.launchpad.net/bugs/555158 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 546885] Re: glxinfo crashed with SIGSEGV in XF86DRIQueryVersion()
@Nils: You're still using the radeon driver, not fglrx. Run aticonfig --initial -f and reboot to activate fglrx. @Dann: You get this watermark if /etc/ati/signature is not installed correctly. The fact that /etc/ati/control was missing as well indicates that something went wrong during driver installation. -- glxinfo crashed with SIGSEGV in XF86DRIQueryVersion() https://bugs.launchpad.net/bugs/546885 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen
It would be helpful to see an Xorg.0.log file with fglrx active. Both XorgLog.txt and XorgLogOld.txt attached to this bug are with RADEON active. -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561354] Re: unable to drag a windows from one monitor to another
What you're describing is a feature, not a bug. You configured two independent desktops. Use Multi-display desktop with display(s) X to set up an extended desktop that spans both monitors and allows you to drag windows from one to the other. -- unable to drag a windows from one monitor to another https://bugs.launchpad.net/bugs/561354 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560777] Re: fglrx driver fails to load
Looks like you're using an old driver version on a new Xserver. You need the new fgrlx 8.721 or 8.723 packages for fglrx to work on Lucid. -- fglrx driver fails to load https://bugs.launchpad.net/bugs/560777 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560777] Re: fglrx driver fails to load
The latest Catalyst drivers don't support Lucid yet. But Lucid already includes a driver version that does work on Lucid. The package name is fglrx. The control center comes in a separate package fglrx-amdcccle. You can install them using Synaptics or aptitude or whatever your favourite package manager is. I highly recommend you uninstall Catalyst and then install the Ubuntu fglrx packages. Run aticonfig --initial -f to activate fglrx and reboot. Just to stress that point, uninstall Catalyst first by running /usr/share/ati/fglrx-uninstall.sh. Do not install the Ubuntu fglrx package over top of an existing Catalyst installation. Hope this helps. -- fglrx driver fails to load https://bugs.launchpad.net/bugs/560777 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen
The log file just stops half way through the driver initialization. There's no backtrace. There are two possibilities: 1. the Xserver is still spinning at 100% CPU load in the background 2. the system crashed hard and didn't have a chance to write the complete log file to the disk You could try updating to the latest driver that was published on Saturday. That may fix your problem. -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 552644] Re: Lucid Lynx 64 bit nightly build hangs on boot
Xorg.0.log from comment #12 shows that fglrx is not installed correctly: (II) LoadModule: fglrx (WW) Warning, couldn't open module fglrx (II) UnloadModule: fglrx (EE) Failed to load module fglrx (module does not exist, 0) (EE) No drivers available. Fatal server error: no screens found -- Lucid Lynx 64 bit nightly build hangs on boot https://bugs.launchpad.net/bugs/552644 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 556267] Re: Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x08f96410 ***
*** This bug is a duplicate of bug 501551 *** https://bugs.launchpad.net/bugs/501551 According to the attached Xorg.0.log file the user was using the Radeon driver, not fglrx. But the bug is marked as affecting fglrx-installer. Whoever has the authority to fix this bug record, please do so. -- Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x08f96410 *** https://bugs.launchpad.net/bugs/556267 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 552644] Re: Lucid Lynx 64 bit nightly build hangs on boot
The log file says that the fglrx driver module wasn't found. It should have been installed in /usr/lib/xorg/extra- modules/modules/drivers/fglrx_drv.so. If that file doesn't exist, something went wrong during installation. -- Lucid Lynx 64 bit nightly build hangs on boot https://bugs.launchpad.net/bugs/552644 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 432531] Re: Unknown/unaccounted memory leak
Anyone experiencing this problem on Karmic, check if you're affected by https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/501715 The memory leak occurs after system updates that trigger ureadahead to reprofile. Rebooting fixes the problem. A workaround is to reboot the system twice after updates. -- Unknown/unaccounted memory leak https://bugs.launchpad.net/bugs/432531 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
