We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
[This is an automated message]
As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
fglrx bugs, which now includes a process for upstreaming bugs to AMD.
http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
To transition your bug into the new fglrx-package, we need you
Is this symptom still reproducible in 8.10 beta or later?
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: New => Incomplete
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
You received this bug notification because you are a member of Ub
** Tags added: valid-xorg-conf
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
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.ub
I have the same problem here with Radeon 9550. I fixed it by booting
with Live CD, chroot to my root partition and aticonfig -f --initial
--overlay-type=Xv.
The annoying thing is that sometimes KDE loses its screen resolution
settings, jumps to highest possible (i.e. unusable) resolution and when
** Attachment added: "Broken xorg.conf"
http://launchpadlibrarian.net/11451875/xorg.conf.kubuntusetup
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
** Attachment added: "Working xorg.conf by aticonfig"
http://launchpadlibrarian.net/11451877/xorg.conf
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
Oops, the linux-restricted-modules package is already at version
2.6.22-14. Anyway, the bug is more likely in the program that generates
xorg.conf.
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
You received this bug notification because you are a member of Ub
I too experience this bug. I have an ATI Radeon xpress 200 (RS480), and
when I enable fglrx through the restricted drivers manager, and restart
X, the screen will flicker for several moments and then dump me into
failsafe mode. I copied my xorg.conf file over from my working Feisty
install, and i
This is the old xorg.conf that works.
** Attachment added: "xorg.conf.1"
http://launchpadlibrarian.net/8954621/xorg.conf.1
--
X does not start after 8/22 fglrx update
https://bugs.launchpad.net/bugs/134180
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
This is the new xorg.conf that causes the xserver crash.
System>Administration>Screens and Graphics creates this xorg.conf so it
maybe not be the update script that did it.
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/8954630/xorg.conf
--
X does not start after 8/22 fglrx up
11 matches
Mail list logo
