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 o
Some related info I found online:
Github bug report:
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/447
Patch linked by the above:
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/commit/2efb9d1248e719474eab91d92d0905f5d3e1d25c
--
You received this
Public bug reported:
/var/log/syslog is flooded with messages of this kind (once per second),
making the log grow at a rate of > 4KB/s or about 350MB per day:
Aug 11 15:10:49 Dobby gnome-shell[1725]: message repeated 3 times: [ Object
Gio.Settings (0x559de3638920), has been already deallocated -
Public bug reported:
DKMS kernel build against linux-headers-4.4.0-63-generic fails. I see
that /usr/src/linux-headers-4.4.0-63-generic is full of broken symlinks:
$ ls -l /usr/src/linux-headers-4.4.0-63-generic
total 1252
drwxr-xr-x 3 root root4096 Feb 9 10:52 arch
lrwxrwxrwx 1 root root
Public bug reported:
I tried installing a daily build of 16.04. Fatal error during
installation: grub failed to install on /dev/sda.
I used custom partition setup to format an existing partition as /
(btrfs) and mounting another existing partition as /home (ext4). I've
never tried btrfs as a root
Installation completed when root as /ext4. Haven't booted into the
installed OS yet. Fingers crossed ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548134
Title:
Os installation fails: grub fail
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949286
Title:
System Crash / Restart
To manage notifications about this
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 bug is a duplicate of bug 830173 ***
https://bugs.launchpad.net/bugs/830173
I don't think this is the same as bug#830173. The complaint with 830173
is about the naming of the Gnash flash plugin and/or confusing update
messages.
My complaint is that my flash plugin alternative changed
I have the same problem. The Shockwave flash 10.1 plugin is actually
gnash. The Adobe flash plugin doesn't show up in Firefox at all.
I found that running "update-alternatives --config mozilla-flashplugin"
can fix the problem by switching the flashplugin alternative from gnash
back to the Adobe fl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869584
Title:
Color selection for Nice and System CPU load are mislabeled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
The color I select for System CPU load is used for displaying Nice CPU
load. And vice versa, the color I select for Nice CPU load is used for
System CPU load.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: indicator-multiload 0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869578
Title:
software-center crashed with SIGSEGV in debListParser::UsePackage()
To manage notifications about this b
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
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Looks more like a Unity problem to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/800649
Title:
Top Taskbar misdisplayed
To manage notifications about this bug go to:
https://bugs.launchpad.net/
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793662
Title:
package fglrx 2:8.780-0ubuntu
Log out and log back in after unchecking capture_before_unmap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/758609
Title:
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 Ubun
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/545257
Title:
gnome-screensaver-gl-helper crashed with SIGS
I'm getting these symptoms ever since I upgraded from Ubuntu 10.10 to
11.04. Before the update the system used to be very stable and stay up
for weeks without rebooting. The only reason to reboot was after
security updates. Now the system tends to randomly hang hard (not ping-
able) about once a we
I have an HP DM1z with an E-350. I've had stability problems with it
under Linux at first, including occasional hangs while suspending and
random hangs when the system was under heavy load. It's been solid for
me since I updated the BIOS to version F.05.
--
You received this bug notification beca
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
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/780144
Title:
Unable to enable fglrx driver since updated to 2.6
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
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I've seen corruption after rotating or resizing the desktop with both
fglrx and the radeon driver on all my test systems. The corruption goes
away once the affected elements on the screen are redrawn in response to
user actions such as opening menus or moving windows. I suspect this is
the same und
@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 i
@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 in
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 s
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 b
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
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/747729
Title:
fglrx crashes X ser
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770669
Title:
package fglrx 2:8.840-0ubuntu4 fail
Why was this queued to fglrx-installer? This is on NVidia hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769911
Title:
System freeze after login in 11.04
--
ubuntu-bugs mailing list
ubunt
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
B
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
Bugs, which is subscribed to Ubuntu.
https://bug
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)
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 bu
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
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
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
When this was bug was first reported 3 years ago, there was no native
driver for my wlan adapter. The ndis-wrapper was the only way to get it
to work and ssb was getting in the way.
At least in my case this bug can be closed, there is now a driver for my
wlan adapter. I don't need the ndis wrapper
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730278
Title:
Xorg fails to start with fglrx in mult-monitor mode wi
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710255
Tit
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684171
Title:
[Amarok] docking all three "content" windows
Bug #671988 has been marked as a duplicate of this one. This bug makes
songs disappear from Squeezebox when their ID3 tags are edited. I have
updated the bug title accordingly.
Should the priority of this bug reconsidered? Maybe wishlist is too low
a priority.
Thanks.
** Summary changed:
- Rhyt
--
Editing ID3 tags leads to files disappearing from Squeezebox (changes file
permissions to 600)
https://bugs.launchpad.net/bugs/671988
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Public bug reported:
Binary package hint: rhythmbox
Editing ID3 tags in Rhythmbox changes the file permissions to 0600
(readable and writable by the owner and nobody else). This leads to the
changed songs disappearing from my Squeezebox since the squeezebox
server loses permissions to read the fi
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
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.1
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
>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 impli
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:
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
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/upg
*** This bug is a duplicate of bug 258139 ***
https://bugs.launchpad.net/bugs/258139
** Description changed:
Binary package hint: evolution
Evolution mangles certain email addresses in message headers. When
replying to such addresses, the resulting emails are undeliverable.
When
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 becaus
--
Evolution mangles certain email addresses, resulting in undeliverable messages
when replying
https://bugs.launchpad.net/bugs/663950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Public bug reported:
Binary package hint: evolution
Evolution mangles certain email addresses in message headers. When
replying to such addresses, the resulting emails are undeliverable.
When I look at the message source, the address looks correct:
To: sw.dl.Linux BG
When I look at the me
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
--
Multi-core load balancing not working properly after suspend to disk
https://bugs.launchpad.net/bugs/661411
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Public bug reported:
CPU: Intel(R) Core(TM) i7 CPU 860, 4 cores, hyperthreading
Symptoms: After suspending to disk load balancing of processes across
CPU cores is not working properly. Runnable processes have to share a
CPU core even if idle CPU cores are available. This is particularly
n
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
Bugs, which is subscr
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-0
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 re
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
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-
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 r
This bug will affect all users installing fglrx on Ubuntu 10.10 using
the Catalyst installer. CCC-LE menu entries will be missing in the
System/Preferences menu until we have implemented a workaround in our
installer.
--
application cache update
https://bugs.launchpad.net/bugs/592671
You received
*** 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 mo
@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/
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.ne
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
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 outp
On Ubuntu 10.04 I'm no longer using the NDIS wrapper. Jockey installs a
proprietary driver for my wireless network adapter.
--
ssb module breaks BCM4328 with ndiswrapper (regression from 2.6.24-10)
https://bugs.launchpad.net/bugs/197558
You received this bug notification because you are a member
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
sou
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 d
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-screens
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
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 yo
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 me
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/
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.
--
fgl
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.la
@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 membe
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
Bugs, which
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
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 t
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 Xserv
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
Bugs, which is subscribed t
@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 Luci
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
ht
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
Bugs, which is s
The fglrx driver saves all used video memory to system memory before
suspending. When you suspend to disk all that memory also has to be
swapped out to the swap partition. If you have a graphics card with lots
of memory and not a lot of available system memory, the saving of video
memory will cause
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
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
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 b
1 - 100 of 180 matches
Mail list logo
