new GFX driver for Ubuntu v8.10 - December 2nd, 2008

[luvit]

get it here: http://linux.via.com.tw

then install compiz: link

[luvit]

get it here: http://linux.via.com.tw

then install compiz: link

[JeeBee]

No luck with the driver here, tried both the install script and the manual configuration as per the instructions, but keeps dropping back to failsafe graphics.

Does anyone have a working xorg.conf for Ubuntu 8.10 for this driver version?

[JeeBee]

No luck with the driver here, tried both the install script and the manual configuration as per the instructions, but keeps dropping back to failsafe graphics.

Does anyone have a working xorg.conf for Ubuntu 8.10 for this driver version?

[JeeBee]

Right, got the xorg.conf in the other thread working, although it surely needs a lot of tidying up?

I don't know if the graphics are hardware accelerated - if I try to enable compiz effects it says it can't enable them (I added 'via' to the WHITELIST in /usr/bin/compiz).

The Xorg log file (in /var/log/) does say:

(II) LoadModule: "via"

(II) Loading /usr/lib/xorg/modules/drivers//via_drv.so
(II) Module via: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 5.74.255
Module class: X.Org Video Driver

which looks good. The DPI is wrong again (it should be 168)

(**) via(0): Virtual size is 1280x768 (pitch 1280)
(**) via(0): *Default mode "1280x768": 80.1 MHz, 47.7 kHz, 60.0 Hz
(II) via(0): Modeline "1280x768"x60.0 80.10 1280 1344 1480 1680 768 769 772 795 -hsync +vsync (47.7 kHz)
(==) via(0): DPI set to (96, 96)
(**) via(0): disable DVI Display SW scaling, It isn't HDMI
(II) via(0): VIASetDisplayPath is DuoView

then it starts to look bad:

(II) via(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(EE) via(0): Couldn't open "/dev/video2"
(II) via(0): VIAScreenInit : V4L Disabled : fd2 = -1
(II) via(0): [drm] Detect H5s1 chipset: 0005 chipid: 3371
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "via_chrome9"
(EE) via(0): DRM open error

but I think I still have accelerated 2D at least right now.

[JeeBee]

Right, got the xorg.conf in the other thread working, although it surely needs a lot of tidying up?

I don't know if the graphics are hardware accelerated - if I try to enable compiz effects it says it can't enable them (I added 'via' to the WHITELIST in /usr/bin/compiz).

The Xorg log file (in /var/log/) does say:

(II) LoadModule: "via"

(II) Loading /usr/lib/xorg/modules/drivers//via_drv.so
(II) Module via: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 5.74.255
Module class: X.Org Video Driver

which looks good. The DPI is wrong again (it should be 168)

(**) via(0): Virtual size is 1280x768 (pitch 1280)
(**) via(0): *Default mode "1280x768": 80.1 MHz, 47.7 kHz, 60.0 Hz
(II) via(0): Modeline "1280x768"x60.0 80.10 1280 1344 1480 1680 768 769 772 795 -hsync +vsync (47.7 kHz)
(==) via(0): DPI set to (96, 96)
(**) via(0): disable DVI Display SW scaling, It isn't HDMI
(II) via(0): VIASetDisplayPath is DuoView

then it starts to look bad:

(II) via(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(EE) via(0): Couldn't open "/dev/video2"
(II) via(0): VIAScreenInit : V4L Disabled : fd2 = -1
(II) via(0): [drm] Detect H5s1 chipset: 0005 chipid: 3371
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "via_chrome9"
(EE) via(0): DRM open error

but I think I still have accelerated 2D at least right now.

[JeeBee]

Okay, I enabled compiz.

I had tried running the vinstall script. DO NOT RUN THIS IF YOU DON'T WANT HASSLE.

If you have run it, you need to switch your via_chrome9.ko file back to the one that the VIA install replaced - luckily it created a backup of the old file, so you just rename the new one to via_chrome9.ko.failed, and the old one to via_chrome9.ko.

113 locate via_chrome9
114 cd /lib/modules/2.6.27-9-generic/kernel/ubuntu/via_chrome9/
117 ls -l
118 sudo mv via_chrome9.ko via_chrome9.ko.fails
119 sudo mv via_chrome9.ko.viabak via_chrome9.ko
120 ls -l

Reboot. Enable Compiz. Works!

Oddly enough, the 2D seems slower now however...

Now to find the configuration for Compiz to enable some of the effects... apart from drop shadows on windows.

[JeeBee]

Okay, I enabled compiz.

I had tried running the vinstall script. DO NOT RUN THIS IF YOU DON'T WANT HASSLE.

If you have run it, you need to switch your via_chrome9.ko file back to the one that the VIA install replaced - luckily it created a backup of the old file, so you just rename the new one to via_chrome9.ko.failed, and the old one to via_chrome9.ko.

113 locate via_chrome9
114 cd /lib/modules/2.6.27-9-generic/kernel/ubuntu/via_chrome9/
117 ls -l
118 sudo mv via_chrome9.ko via_chrome9.ko.fails
119 sudo mv via_chrome9.ko.viabak via_chrome9.ko
120 ls -l

Reboot. Enable Compiz. Works!

Oddly enough, the 2D seems slower now however...

Now to find the configuration for Compiz to enable some of the effects... apart from drop shadows on windows.

[mikez]

What is the version of the running kernel? (uname -a)
What is the version string of the modules you are trying to load?
(use: /sbin/modinfo /full/path/to/module/<whatever>.ko - to read a non-loaded module)
Are you using the 'force' (-f) option to load the modules?

[mikez]

What is the version of the running kernel? (uname -a)
What is the version string of the modules you are trying to load?
(use: /sbin/modinfo /full/path/to/module/<whatever>.ko - to read a non-loaded module)
Are you using the 'force' (-f) option to load the modules?