[Bug 18148] New: Virtual size too big for certain hardware
http://bugs.freedesktop.org/show_bug.cgi?id=18148 Summary: Virtual size too big for certain hardware Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen@suse.de ReportedBy: felipe.contreras@gmail.com QAContact: xorg-team@lists.x.org The default virtual size for Mobility Radeon X1300 is too big, that makes DRI unusable and EXA in turn. For more details see bug #18096. (II) RADEONHD(0): FB: Allocated Offscreen Buffer at offset 0x01908000 (size = 0x00666000) (II) RADEONHD(0): FB: Allocated DRI Back Buffer at offset 0x01F6E000 (size = 0x01900000) (EE) RADEONHD(0): FB: Failed allocating DRI Depth Buffer (25600 KB) (EE) RADEONHD(0): DRI: Failed allocating buffers, disabling -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
http://bugs.freedesktop.org/show_bug.cgi?id=18148
Luc Verhaegen
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #2 from Michel Dänzer
RandR does this for you.
The radeon driver is able to choose different defaults depending on things like the amount of video RAM... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #3 from Luc Verhaegen
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #4 from Alex Deucher
http://bugs.freedesktop.org/show_bug.cgi?id=18148
Felipe Contreras
As I explained in discussions at the time, there's no need to check the accel limits when setting up the FB. EXA takes the various accel limits (blitter limits, texture limits, etc.) into account and with XAA it's probably better to fail to init accel and tell the user what happened than to fail the requested setup.
Looks like manually setting the virtual size could be avoided. As a user, one should not care about this stuff. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #6 from Egbert Eich
http://bugs.freedesktop.org/show_bug.cgi?id=18148
Michal Suchanek
http://bugs.freedesktop.org/show_bug.cgi?id=18148
Felipe Contreras
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #9 from Michal Suchanek
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #10 from Felipe Contreras
Perhaps bandaids for specific cases would but ultimately the root of the problem is the X server's inability to change virtual as required.
For one on Intel the video overlay size seems to be limited by the virtual size (or it is just incidentally the same?) so changing the virtual to larger one when a large video playback is requested would be desirable.
Unfortunately X cannot do that.
It would definitely be nice to have that, but that's no excuse to have this bad behaviour. Lots of things can be done, if the driver find outs the virtual size is too big, well then why not change the virtual size? If you want to be puristic and avoid workarounds then disable EXA when the virtual size is too big, or fail completely and return an error. Having the user wondering why on earth everything is so painfully is low is Not Good(tm). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #11 from Michal Suchanek
It would definitely be nice to have that, but that's no excuse to have this bad behaviour.
Lots of things can be done, if the driver find outs the virtual size is too big, well then why not change the virtual size?
If you want to be puristic and avoid workarounds then disable EXA when the virtual size is too big, or fail completely and return an error.
Having the user wondering why on earth everything is so painfully is low is Not Good(tm).
As explained in comment #6 X is not designed for that either. The memory is divided among several subsystems which are initialized sequentially and do not know about the memory requirements of each other. It would require either some guess which might cause problems in some special cases again or substantial changes to the X configuration and module initialization process. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
https://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #12 from Jeremy Huddleston
https://bugs.freedesktop.org/show_bug.cgi?id=18148
Jeremy Huddleston
participants (1)
-
bugzilla-daemon@freedesktop.org