[HD 4850] X server chooses unsupported screen depth

Bug #366879 reported by Felix Geyer
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Karmic by mclaud2000

Bug Description

I installed the fglx driver from ubuntu-x-swat X updates PPA (2:8.602-0ubuntu1~xup~1).

X Server fails to start with the following error message in Xorg.0.log:
(II) fglrx(0): Creating default Display subsection in Screen section
 "Default Screen" for depth/fbbpp 8/8
(EE) fglrx(0): Given depth (8) is not supported by fglrx driver

Adding DefaultDepth 24 to the Screen section of xorg.conf solves the problem.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 02)
     Subsystem: ASUSTeK Computer Inc. Device [1043:82d3]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV770 [Radeon HD 4850] [1002:9442]
     Subsystem: ATI Technologies Inc Device [1002:0502]

Revision history for this message
Felix Geyer (debfx) wrote :
Revision history for this message
Felix Geyer (debfx) wrote :
Revision history for this message
Felix Geyer (debfx) wrote :
Bryce Harrington (bryce)
Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
summary: - X server chooses unsupported screen depth
+ [HD 4850] X server chooses unsupported screen depth
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in fglrx-installer (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Felix Geyer (debfx) wrote :

I installed fglrx 2:8.620-0ubuntu1~jaunty and libdrm2 2.4.11+git20090519.f355ad89-0ubuntu0sarvatt~jaunty on jaunty.
The new version doesn't resolve the bug.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Luigi Maselli (grigio) wrote :

Still this problem on rc w 4850+fglrx

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Felix,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 366879

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 366879 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/366879

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.