ubuntu-x-swat team mailing list archive

[Marien Zwart <m_zwart@xxxxxxxxxxx>]

Public bug reported:

I have an acer aspire 1350 laptop with (from lspci -nn):

01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc.
KM400/KN400/P4M800 [S3 UniChrome] [1106:7205] (rev 01)

Using jaunty it needs the x-updates ppa for X to start at all (at least without an xorg.conf). With x-updates (xserver-xorg-video-openchrome 1:0.2.903+svn741-1build1) it works, but launching an app that uses xv (like totem) crashes that app with a BadAlloc and a complaint that "Bandwidth is insufficient. Check bios memory settings.". Adding some debugging code to the driver revealed that in via_video.c:DecideOverlaySupport width and height (gotten from 
pBIOSInfo->Panel->NativeMode->Width and ->Height) were 0, causing that function to return FALSE by default. After noticing via_mode.c:VIAGetPanelSize is the only function that sets NativeModeIndex without also setting NativeMode I came up with a horrible (duplicating a table) patch that makes xv work (attached).

(VIAGetPanelSize also contains a cosmetic bug: the PanelSizeString array
(used only for logging) is out of sync with the defines in via_bios.h,
so for my 1024x768 it logs "Using panel at 800x600." after correctly
detecting a VIA_PANEL10X7. A slightly better patch could fix that log
message, using the same table needed to set NativeMode->Width and
->Height.)

If you need me to test something feel free to poke me on irc instead of
here for faster response times (I joined #ubuntu-x).

** Affects: xserver-xorg-video-openchrome (Ubuntu)
     Importance: Undecided
         Status: New

-- 
xv does not work (badalloc, using the x-updates ppa)
https://bugs.launchpad.net/bugs/415964
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.