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
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
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
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
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.
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:
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
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
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
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
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
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.
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
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.
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
@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
@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:
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
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
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
@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
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
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
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
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
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)
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
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
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.
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
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
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.
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
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
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
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
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
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
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
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:
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
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
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
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
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
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.
--
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
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
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
*** 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
@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
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()
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
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
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
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
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
--
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
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
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
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
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.
--
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
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
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
@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
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
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
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
@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
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
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
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
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
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
@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
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
@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
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
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
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
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.
--
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
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
@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
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
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
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.
--
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
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
@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
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
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
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
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
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
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
*** 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.
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
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
1 - 100 of 121 matches
Mail list logo
