Debian «Lenny»: Unable to set graphic acceleratiion with VIA K8M800 unichrome chipset

juanjavier_xxx · 03-18-2010, 12:17 PM

Got a Packard Bell desktop with

Code:

~$ lspci | grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] (rev 01)

...video chipset installed. So far I am unable to set video acceleration working.

I googled around, nothing useful found really. Whatever I find, stucks. Downloading source from www.openchrome.org fails to build. Posting to openchrome mailing lists
did not find...nobody answers me.

Code:

~$ cat /var/log/Xorg.0.log | grep driver
        X.Org XInput driver : 2.0
(II) Loading /usr/lib/xorg/modules/drivers//openchrome_drv.so
        ABI class: X.Org XInput driver, version 2.0
        ABI class: X.Org XInput driver, version 2.0
(!!) VIA Technologies does not support this driver in any way.
(II) [drm] loaded kernel module for "via" driver.

Then tried to build from source, but to no avail.

Code:

In file included from via_priv.h:30,
                 from via_driver.h:68,
                 from via_accel.c:42:
via_drm.h:117: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:122: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:127: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:151: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:214: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:239: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:249: error: expected specifier-qualifier-list before ‘__u32’
via_drm.h:260: error: expected specifier-qualifier-list before ‘__u32’
via_accel.c: In function ‘viaAccelDMADownload’:
via_accel.c:1726: error: ‘drm_via_dmablit_t’ has no member named ‘sync’
via_accel.c:1726: error: ‘drm_via_dmablit_t’ has no member named ‘sync’
via_accel.c:1735: error: ‘drm_via_dmablit_t’ has no member named
‘mem_addr’
via_accel.c:1737: error: ‘drm_via_dmablit_t’ has no member named
‘mem_addr’
via_accel.c:1745: error: ‘drm_via_dmablit_t’ has no member named
‘num_lines’
via_accel.c:1746: error: ‘drm_via_dmablit_t’ has no member named
‘num_lines’
via_accel.c:1747: error: ‘drm_via_dmablit_t’ has no member named
‘num_lines’
via_accel.c:1754: error: ‘drm_via_dmablit_t’ has no member named
‘mem_addr’
via_accel.c:1755: error: ‘drm_via_dmablit_t’ has no member named
‘line_length’
via_accel.c:1756: error: ‘drm_via_dmablit_t’ has no member named
‘mem_stride’
via_accel.c:1757: error: ‘drm_via_dmablit_t’ has no member named
‘fb_addr’
via_accel.c:1758: error: ‘drm_via_dmablit_t’ has no member named
‘fb_stride’
via_accel.c:1759: error: ‘drm_via_dmablit_t’ has no member named ‘to_fb’
via_accel.c:1760: error: ‘drm_via_dmablit_t’ has no member named
‘num_lines’
via_accel.c: In function ‘viaExaUploadToScreen’:
via_accel.c:1997: error: ‘drm_via_dmablit_t’ has no member named
‘line_length’
via_accel.c:1998: error: ‘drm_via_dmablit_t’ has no member named
‘num_lines’
via_accel.c:1999: error: ‘drm_via_dmablit_t’ has no member named
‘fb_addr’
via_accel.c:2000: error: ‘drm_via_dmablit_t’ has no member named
‘fb_stride’
via_accel.c:2001: error: ‘drm_via_dmablit_t’ has no member named
‘mem_addr’
via_accel.c:2002: error: ‘drm_via_dmablit_t’ has no member named
‘mem_stride’
via_accel.c:2003: error: ‘drm_via_dmablit_t’ has no member named ‘to_fb’
via_accel.c:2012: error: ‘drm_via_dmablit_t’ has no member named ‘sync’
via_accel.c:2012: error: ‘drm_via_dmablit_t’ has no member named ‘sync’
via_accel.c: In function ‘viaFinishInitAccel’:
via_accel.c:2601: error: ‘drm_via_mem_t’ has no member named ‘context’
via_accel.c:2602: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2603: error: ‘drm_via_mem_t’ has no member named ‘type’
via_accel.c:2608: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2609: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2615: error: ‘drm_via_mem_t’ has no member named ‘offset’
via_accel.c:2622: error: ‘drm_via_mem_t’ has no member named ‘context’
via_accel.c:2623: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2624: error: ‘drm_via_mem_t’ has no member named ‘type’
via_accel.c:2628: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2629: error: ‘drm_via_mem_t’ has no member named ‘size’
via_accel.c:2635: error: ‘drm_via_mem_t’ has no member named ‘offset’
make[3]: *** [via_accel.lo] Error 1
make[3]: leaving directory `/home/juanjavier/openchrome/trunk/src'
make[2]: *** [all] Error 2
make[2]: leaving directory `/home/juanjavier/openchrome/trunk/src'
make[1]: *** [all-recursive] Error 1
make[1]: leaving directory `/home/juanjavier/openchrome/trunk'
make: *** [all] Error 2

What am I missing? Is there any real chance I can get direct rendering enabled?

Code:

~$ glxinfo | grep rendering
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

Any help is appreciated. Regards.

rylan76 · 03-19-2010, 03:39 AM

Quote:

What am I missing? Is there any real chance I can get direct rendering enabled?

No I don't think so. I had exactly the same problem with the same chipset on the same mobo on my dad's old PC. I prodded at the problem for a week, no luck. I too could not get the source to compile, and the driver itself also refused to do acceleration.

This is an on-board display card, right?

Eventually the only solution was to get an old AGP stand-alone display card based on the Nvidia chipset, which IS well supported. Slotted that in, loaded up the Nvidia Linux driver, and all was well. The implementation of this chipset I had on my mobo (I -think- it was the same one you mention here) fortunately was on a motherboard that DID still have an AGP slot. If you motherboard is one of the super-compact ones with limited expansion capabilities, you might not be able to do this (i. e. if it HAS no AGP or even PCIE display card slot!)

It seems the available binary unichrome driver is completely incapable of doing accelerated X windows. This also is an old chipset, and it seems to have "died" - being old and not supported anymore at all. (BTW - the forums were dead too as you say, neither could I get any replies. This was about 2 years ago.)

juanjavier_xxx · 03-21-2010, 02:11 PM

Quote:

Originally Posted by rylan76

No I don't think so. (...) This is an on-board display card, right?

Sure it is.

Quote:

Originally Posted by rylan76

Eventually the only solution was to get an old AGP stand-alone display card based on the Nvidia chipset, which IS well supported.

---Yep, it seems so...

Quote:

Originally Posted by rylan76

It seems the available binary unichrome driver is completely incapable of doing accelerated X windows.

---Correct, I have the binary package for Debian Lenny correctly installed...

Code:

dpkg -s xserver-xorg-video-openchrome
Package: xserver-xorg-video-openchrome
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 536
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Architecture: i386
Version: 1:0.2.902+svn579-4
Replaces: libchromexvmc1, libchromexvmcpro1
Provides: xserver-xorg-video-2
Depends: libc6 (>= 2.7-1), libdrm2 (>= 2.3.1), xserver-xorg-core (>= 2:1.4)
Conflicts: libchromexvmc1, libchromexvmcpro1
Description: X.Org X server -- VIA display driver
 OpenChrome is a project for the development of free and open-source drivers
 for the VIA UniChrome video chipsets.
 .
 Originally called the 'snapshot' release, since it was a snapshot of an
 experimental branch of the unichrome cvs code, this is a continued development
 of the open source unichrome driver (from http://unichrome.sf.net) which
 also incorporates support for the unichrome-pro chipsets.
 .
 Support for hardware acceleration (XvMC) for all chipsets has subsequently
 been ripped out of the unichrome.sf.net driver. Therefore your only option if
 you wish to make use of the acceleration features of your VIA chip with free
 and open-source drivers is to use this version of the driver.
Homepage: http://www.openchrome.org

...and the driver call on startup correctly implemented in xorg.conf:

Code:

Section "Device"
        Identifier      "Configured Video Device"
        Driver          "openchrome"
EndSection

---However the driver itself refuses to accelerate anything...

Quote:

Originally Posted by rylan76

This also is an old chipset, and it seems to have "died" - being old and not supported anymore at all. (BTW - the forums were dead too as you say, neither could I get any replies. This was about 2 years ago.)

---Pity there is no Nvidia AGP card with HDMI built-in output...¿isn't it?