Missing display resolutions (too much memory bandwidth)

Bug #469640 reported by Fawn
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-mga (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: xorg

The key line from the log is:

(II) MGA(0): Not using default mode "1280x1024" (mode requires too much memory bandwidth)

This is a system that was running jaunty just fine at 1280x1024.

I have no xorg.conf

ProblemType: Bug
Architecture: amd64
Date: Sun Nov 1 22:30:19 2009
DistroRelease: Ubuntu 9.10
Package: xorg 1:7.4+3ubuntu7
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-server
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.31-14-server x86_64
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
XsessionErrors:
 (gnome-settings-daemon:5670): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:5670): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:5727): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:5703): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:5702): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-server
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
MachineType: HP ProLiant ML110 G5
Package: xserver-xorg-video-mga 1:1.4.11.dfsg-2ubuntu1
PackageArchitecture: amd64
ProcCmdLine: root=UUID=e2f4c382-22ad-4e91-815a-c523bd1f5673 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-21-server x86_64
UserGroups:

dmi.bios.date: 03/12/2009
dmi.bios.vendor: HP
dmi.bios.version: O15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: ProLiant ML110 G5
dmi.board.vendor: Wistron Corporation
dmi.board.version: NA
dmi.chassis.asset.tag: MC01
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHP:bvrO15:bd03/12/2009:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A:
dmi.product.name: ProLiant ML110 G5
dmi.product.version: NA
dmi.sys.vendor: HP
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-21-server

Revision history for this message
Fawn (fawn) wrote :
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-mga (Ubuntu)
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your bug report. The Xorg.0.log and glxinfo show that DRI is enabled. However compiz might ask for special capabilities that are not met. Did compiz ever work on this card?

Please run "CM_DRY=yes compiz" and paste the output here.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Oops, that answer was for the wrong bug report :)

Anyway, thanks for this report. Can you please provide a log from Jaunty where it worked?

Revision history for this message
Fawn (fawn) wrote :

This was an in-place upgrade. Lucky I have back-ups.

Changed in xserver-xorg-video-mga (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Peter (perivol) wrote :

I just did an in-place upgrade 8.04 LTS -> 10.04 LTS (64 bit) on a machine with a MGA-G200, and this bug is still there (10.04 LTS uses X Server 1.7.6). As a result, I cannot use the 1280x1024 mode, which is really annoying, as it was working fine on 8.04 LTS. Is there any chance that this will get fixed?

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

[This is an automatic notification.]

Hi Fawn,

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 469640

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 469640 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/469640

Changed in xserver-xorg-video-mga (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Fawn (fawn) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Fawn (fawn) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Fawn (fawn) wrote : Dependencies.txt

apport information

Revision history for this message
Fawn (fawn) wrote : Lspci.txt

apport information

Revision history for this message
Fawn (fawn) wrote : Lsusb.txt

apport information

Revision history for this message
Fawn (fawn) wrote : PciDisplay.txt

apport information

Revision history for this message
Fawn (fawn) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Fawn (fawn) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Fawn (fawn) wrote : ProcModules.txt

apport information

Revision history for this message
Fawn (fawn) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Fawn (fawn) wrote : UdevDb.txt

apport information

Revision history for this message
Fawn (fawn) wrote : UdevLog.txt

apport information

Revision history for this message
Fawn (fawn) wrote : XorgLog.txt

apport information

Revision history for this message
Fawn (fawn) wrote : XorgLogOld.txt

apport information

Revision history for this message
Fawn (fawn) wrote : Xrandr.txt

apport information

Revision history for this message
Fawn (fawn) wrote : setxkbmap.txt

apport information

Revision history for this message
Fawn (fawn) wrote : xdpyinfo.txt

apport information

Revision history for this message
Fawn (fawn) wrote : xkbcomp.txt

apport information

Revision history for this message
Peter (perivol) wrote :

I have resolved the problem after comparing the 8.04 LTS and 10.04 LTS Xorg.0.log files. Under 8.04 LTS the MGA driver was defaulting to

(**) MGA(0): Depth 16, (--) framebuffer bpp 16

Under 10.04 LTS it is defaulting to

(**) MGA(0): Depth 24, (--) framebuffer bpp 32

which is the cause of the bandwidth problem. Setting "DefaultFbBpp 24" in the "Screen" section of xorg.conf enables the 1280x1024 mode, but all screen operations are very slow. The combination of "DefaultDepth 16" and "DefaultFbBpp 16" provides completely acceptable performance which is, in fact, a bit faster than under 8.04 LTS.

Revision history for this message
Fawn (fawn) wrote : Re: [Bug 469640] Re: Missing display resolutions (too much memory bandwidth)

Many thanks. This has been a real pain for ages.

Fawn

On Tue, 04 May 2010 12:25 +0000, "Peter" <email address hidden> wrote:
> I have resolved the problem after comparing the 8.04 LTS and 10.04 LTS
> Xorg.0.log files. Under 8.04 LTS the MGA driver was defaulting to
>
> (**) MGA(0): Depth 16, (--) framebuffer bpp 16
>
> Under 10.04 LTS it is defaulting to
>
> (**) MGA(0): Depth 24, (--) framebuffer bpp 32
>
> which is the cause of the bandwidth problem. Setting "DefaultFbBpp 24"
> in the "Screen" section of xorg.conf enables the 1280x1024 mode, but all
> screen operations are very slow. The combination of "DefaultDepth 16"
> and "DefaultFbBpp 16" provides completely acceptable performance which
> is, in fact, a bit faster than under 8.04 LTS.
>
> --
> Missing display resolutions (too much memory bandwidth)
> https://bugs.launchpad.net/bugs/469640
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Bryce Harrington (bryce)
tags: added: hardy
Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-mga (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-mga (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.