My hardware: a Compaq laptop with Cyberblade/i1 and a 800x600 LCD, but using an
With resolutions higher than 1024x768, mplayer displays any video garbaged
xvinfo reports that the "maximum XvImage size" is 1024x1024 - so maybe that's
However, I tried changing resolution on the fly with xrandr to just about any
resolution, and it was still garbaged.
I also tried setting "cybershadow" to "on", "display" to "crt" only, and also
tried switching to another virtual console and back to X after xrandr to maybe
reset some more registers...
I guess since xvinfo reports a 1024x1024 limit, I can't use Xv with higher
resolutions, but I don't know if changing to 1024x768 with xrandr should work or
Here's some more info, which can basically be ignored...
The LCD is 800x600, but I set the laptop to use the external port only (LCD is
turned off) - plus, in 1024x768 Xv works ok, so the 800x600 doesn't seem to be
I tried reconfiguring the X server, ended up regeneration a completely new
config file, and still the problem was always the same - >1024x768 fails.
Other that Xv, the X works fine with the higher resolutions (upto 1856x1392).
I tried almost every resolution possible, 1280x960, 1280x1024, 1400x1050 (with
and without the "Display1400" option), 1600x1200, 1792x1344, 1856x1396 - none
works. Only 1024x768 and lower works.
I've tried both with 24bit and with 16bit depths, no difference.
I tried using a "virtual" size, and without - no difference.
many chipsets cannot do overlays over a certain resolution or refresh rate due
to bandwidth limitations. This is espcially true on integarted chipsets like
i8xx and prosavages. I suspect you are running to this limitation.
(In reply to comment #1)
I have no problem with any limit. However, I would like two things:
1) To be able to go to the higher resolution and back, and use Xv again in the
lower resolution (it did work there on the first place).
2) To understand what exactly is the limit.
This is a duplicate of #736. See comment #10 for explainations.
The fix is here :
Closing. Believed to be fixed in 6.9/7.0 RC2.