After posting about the Spanish version of this tutorial here, I decided I should give back (a little) to those who so many times saved me, and did so in English.
I wont translate the whole history on how I ended buying this motherboard, but this is what i got: I was expecting my post-install to be a flawless one, when i found out that windows moved extremely slow, not to name Firefox scrolling of webpages crawling like if I were playing Quake 4. This last issue didn’t precisely help in the search for this driver.
Click the following link to continue reading.
The only thing I’m going to say about it is that I hope Via, Xorg and the whole distro-world start doing something with this kind of things. VIA and SiS are very popular chipsets around Latin America (they are cheaper, and when you don’t need that extra performance from Intel or nVidia, the budget rules) and they should, better yet, MUST be easy as hell to install, as they have (Via ones, for 2D at least) open source drivers. Of course this is not the case and here we are, writing a tutorial for it. I don’t know or understand the reasons behind this, if there are any that you know of, and I’m obviously missing, please post a comment and tell me about it.
This tutorial will install the official open source Via drivers for the K8M890 chipset, but will work for all and any of the next:
- CLE266 UniChrome integrated graphics ( VT8622/3 )
- CN700 UniChrome Pro integrated graphics ( CN700 )
- CN800 UniChrome Proâ„¢ integrated graphics ( CN800 )
- CX700 UniChrome Pro integrated graphics ( CX700 CX700 )
- CX700M UniChome Pro integrated graphics ( )
- K8M800/K8N800 UniChrome Pro integrated graphics ( K8M800 K8N800 )
- K8M890CE/K8N890CE Chrome9â„¢ integrated graphics ( K8M890 )
- KN400 & KM400 UniChrome integrated graphics ( KN400 VT8378 )
- P4M800/CE/Pro UniChrome Pro integrated graphics ( P4M800 P4M800Pro )
- P4M890 UniChrome Pro integrated graphics ( P4M890 )
- P4M900 VIA Chrome9â„¢ HC integrated graphics ( P4M900 )
- PM880, PM800, CN400 UniChrome integrated graphics ( PM880 CN400 PM800 )
- VN800 UniChrome Pro integrated graphics ( VN800 )
- VX700 Single chip solution ( )
Here is the drivers page for more info and the download of the source.
Now, lets get hands on the dirty task of making video work as it should, you can copy and paste each instruction if you follow the order and everything should work, of course, take a look at the comments in case you have to make some modification:
First we are going to remove any traces of other may-be-conflicting drivers:
sudo apt-get remove xserver-xorg-video-via xserver-xorg-video-unichromeWe should confirm the removal and move on to installing all the dependencies that we will need to compile the driver:
sudo apt-get install build-essential libxinerama-dev x11proto-xinerama-dev libxvmc-dev sysutils tofrodossudo apt-get build-dep xserver-xorg-video-viasudo apt-get build-dep xorgAgain, confirm the installation for each step and move on to decompressing the drivers source.
# tar zxvf CN_CX700-CN800XORG40071-kernel-src_[date].tgz
Once decompressed get inside the src directory:
# cd CN_CX700-CN800XORG40071-kernel-src_[fecha]/src
And we try to compile (and i say try, because you never know when something can go wrong!):
Update: 2007/06/01
As I sayd before, you never know when something can go wrong!
Several people comment problems compiling the driver. This issue is caused by a problem with kernel versions in the drivers.
If you are using Ubuntu Edgy, you should check for this, before compiling (this might work for other distributions if you are having the same problem, try it):
uname -rThats your kernel version. Now check what version the drivers are for, inside the driver folder run:
grep "2.6." makedriverCheck the version is the same, if its not, then, edit it with vim (or your prefered editor) and replace the wrong version entries with the one of the command: “uname -r“.
Now check again the version of the kernel, but this time in another file:
grep "2.6." vinstall_2DCheck the version is the same, if its not, then, edit it with vim (or your prefered editor) and replace the wrong version entries with the one of the command: “uname -r“.
# ./makedriver
Once we run makedriver we have to answer a couple of questions:
1) The driver version. In this case is 71. You can find this at the end of the first block of numbers in the filename before the ‘kernel’ word.
2) Our CPU architecture. You should know what type of processor you have. If in doubt, type cat /proc/cpu in another console, and enter the correct option.
After this, we re-index our libraries:
# ldconfig
That shouldnt take long on a fresh install, then, we should find our driver compiled right in /CN_CX700-CN800XORG40071, so we get inside to finish the task:
# cd /CN_CX700-CN800XORG40071
And finally, enter the last command to finish the installation:
# ./vinstall_2D
We should get some output indicating everything went right.
This should have changed ‘vesa’ for ‘via’ in /etc/X11/xorg.conf automatically.
Now, you should reboot and watch our firefox scroll go as fast as it can ;)
Some references used to build this how-to and accomplish the task:
Help Ubuntu – OpenChrome
OpenChrome Mailing List
Via Arena Forums
[...] Entonces me puse manos a la obra, y orandole a San Google ™, empece a recaudar información de todas partes. Finalmente, logre tener un driver de video que funciona y a una velocidad mas q aceptable, exceptuando que no tiene ninguna cualidad 3D. Esta es una guía de como configurar el video de una placa integrada chipset K8M890 en Xorg y Ubuntu, sin morir en el intento. English: You can find the English version of this article here [...]
Hi. I am using ubuntu with a kernel core of 2.6.17-10. The make files provided with the VIA driver for the k8m80069 chip did not work in spite of some persistent modification on my part.
I followed your link to the openchrome pages and was able to successfully install and configure my graphics! YAH!
Thanks for all your info, much appreciated!
thanks, it worked out well for me – to a certain point – the chip is running fast now, but i’m stuck to 800×600 resolution, because the x-server is not recognising the mode-lines correctly… i’ll post my xorg.conf and my xorg.0.log here, if anybody has an idea, just post a comment, i’ll return here frequently until i got the right 1280×800 resolution running on my Fujistu-Siemens Amilo Pro V 2035 VIA VN800.
From the How-To makedriver-step, i chose as answers to the questions:
driver ? 71
chip ? 1
Here my xorg.conf:
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type “man /etc/X11/xorg.conf” at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section “Files”
FontPath “/usr/share/X11/fonts/misc”
FontPath “/usr/share/X11/fonts/cyrillic”
FontPath “/usr/share/X11/fonts/100dpi/:unscaled”
FontPath “/usr/share/X11/fonts/75dpi/:unscaled”
FontPath “/usr/share/X11/fonts/Type1″
FontPath “/usr/share/X11/fonts/100dpi”
FontPath “/usr/share/X11/fonts/75dpi”
FontPath “/usr/share/fonts/X11/misc”
# path to defoma fonts
FontPath “/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType”
EndSection
Section “Module”
Load “glx”
Load “i2c”
Load “bitmap”
Load “ddc”
Load “dri”
Load “extmod”
Load “freetype”
Load “int10″
Load “type1″
Load “vbe”
Load “synaptics”
EndSection
Section “InputDevice”
Identifier “Generic Keyboard”
Driver “kbd”
Option “CoreKeyboard”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105″
Option “XkbLayout” “de”
Option “XkbOptions” “lv3:ralt_switch”
EndSection
Section “Device”
Driver “via”
VendorName “VIA Tech”
BoardName “via”
Identifier “Generic Video Card”
BusID “PCI:1:0:0″
EndSection
Section “Monitor”
ModeLine “720×480″ 26.7 720 736 808 896 480 481 484 497
ModeLine “720×576″ 32.7 720 744 816 912 576 577 580 597
ModeLine “800×480″ 29.58 800 816 896 992 480 481 484 497
ModeLine “848×480″ 31.5 848 864 952 1056 480 481 484 497
ModeLine “856×480″ 31.7 856 872 960 1064 480 481 484 497
ModeLine “1024×512″ 41.3 1024 1056 1160 1296 512 513 516 531
ModeLine “1280×720″ 74.6 1280 1341 1474 1688 720 721 724 746
ModeLine “1280×768″ 80.1 1280 1344 1480 1680 768 769 772 795
ModeLine “1360×768″ 85.50 1360 1392 1712 1744 768 783 791 807 +HSync +Vsync
ModeLine “1366×768″ 85.86 1366 1440 1584 1800 768 769 772 795 -HSync +Vsync
ModeLine “1440×1050″ 126.2 1440 1536 1688 1936 1050 1051 1054 1087
ModeLine “1920×1080″ 172.9 1920 2043 2249 2578 1080 1081 1084 1118
ModeLine “720×480″ 34.9 720 752 824 928 480 481 484 502
ModeLine “720×576″ 42.6 720 760 832 944 576 577 580 602
ModeLine “848×480″ 41.0 848 880 968 1088 480 481 484 502
ModeLine “856×480″ 41.3 856 888 976 1096 480 481 484 502
ModeLine “1024×512″ 53.3 1024 1072 1176 1328 512 513 516 535
ModeLine “1280×768″ 103.0 1280 1360 1496 1712 768 769 772 802
ModeLine “1440×1050″ 160.0 1440 1536 1696 1952 1050 1051 1054 1096
ModeLine “1280×768″ 118.5 1280 1368 1504 1728 768 769 772 807
# The following are my trial and error Modelines. which didn’t work until now:
ModeLine “1280×800″ 118.5 1280 1368 1505 1728 800 801 804 839 -hsync -vsync
Modeline “640×480″ 25.20 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline “1280×800″ 25.20 1280 1312 1504 1600 800 820 824 890 -hsync -vsync
Identifier “Generic Monitor”
Option “DPMS”
EndSection
Section “Screen”
Identifier “Default Screen”
Device “Generic Video Card”
Monitor “Generic Monitor”
DefaultDepth 24
SubSection “Display”
Depth 1
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 4
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 8
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 15
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 16
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 24
Modes “1280×800″ “1024×768″ “800×600″ “640×480″
EndSubSection
EndSection
Section “ServerLayout”
Identifier “Default Layout”
Screen “Default Screen”
InputDevice “Generic Keyboard”
InputDevice “Configured Mouse”
InputDevice “stylus” “SendCoreEvents”
InputDevice “cursor” “SendCoreEvents”
InputDevice “eraser” “SendCoreEvents”
InputDevice “Synaptics Touchpad”
EndSection
Section “DRI”
Mode 0666
EndSection
#####
Here my xorg.0.log
(II) Reloading /usr/lib/xorg/modules/libddc.so
(II) VIA(0): VESA VBE DDC supported
(II) VIA(0): VESA VBE DDC Level 2
(II) VIA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VIA(0): VESA VBE DDC read failed
(II) VIA(0): I2C device “I2C bus 1:ddc2″ registered at address 0xA0.
(II) VIA(0): I2C device “I2C bus 1:ddc2″ removed.
(–) VIA(0): unexpected EDID version 0 revision 0
(II) VIA(0): Generic Monitor: Using default hsync range of 31.50-37.90 kHz
(II) VIA(0): Generic Monitor: Using default vrefresh range of 50.00-70.00 Hz
(II) VIA(0): Clock range: 20.00 to 270.00 MHz
(II) VIA(0): Not using mode “720×480″ (hsync out of range)
(II) VIA(0): Not using mode “800×480″ (hsync out of range)
(II) VIA(0): Not using mode “1440×1050″ (hsync out of range)
(II) VIA(0): Not using mode “1280×768″ (hsync out of range)
(II) VIA(0): Not using mode “1280×800″ (hsync out of range)
(II) VIA(0): Not using mode “1280×800″ (hsync out of range)
(II) VIA(0): Not using default mode “640×350″ (vertical timing out of range)
(II) VIA(0): Not using default mode “2048×1536″ (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode “1024×768″ (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using mode “1280×800″ (no mode of this name)
(II) VIA(0): Not using mode “1024×768″ (no mode of this name)
(II) VIA(0): Not using mode “1024×512″ (width too large for virtual size)
(–) VIA(0): Virtual size is 800×600 (pitch 800)
(**) VIA(0): *Default mode “800×600″: 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) VIA(0): Modeline “800×600″ 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(**) VIA(0): *Mode “640×480″: 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) VIA(0): Modeline “640×480″ 25.20 640 656 752 800 480 490 492 525 -hsync -vsync
(**) VIA(0): Default mode “800×600″: 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) VIA(0): Modeline “800×600″ 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync
(**) VIA(0): Mode “720×576″: 32.7 MHz, 35.9 kHz, 60.1 Hz
(II) VIA(0): Modeline “720×576″ 32.70 720 744 816 912 576 577 580 597
(==) VIA(0): DPI set to (75, 75)
(II) Loading sub module “fb”
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID PCI:1:0:0
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
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) VIA(0): [drm] drmOpen failed
(EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) VIA(0): VIAInternalScreenInit
(II) VIA(0): Frame Buffer From (0,0) To (800,2047)
(II) VIA(0): Using 2047 lines for offscreen memory.
(**) Option “Device” “/dev/wacom”
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : Invalid argument
Synaptics DeviceInit called
SynapticsCtrl called.
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
(–) Synaptics Touchpad auto-dev sets device to /dev/input/event3
(**) Option “Device” “/dev/input/event3″
(–) Synaptics Touchpad touchpad found
Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
ProcXCloseDevice to close or not ?
#####
So long, and thanks for the fish ;)
Well, as you didnt left an email to contact you, I will post some comments regarding the errors you show in you post, but leave me an email so i can explain it better if you need assistance.
First of all, you should look at this error:
(II) VIA(0): Generic Monitor: Using default hsync range of 31.50-37.90 kHz
(II) VIA(0): Generic Monitor: Using default vrefresh range of 50.00-70.00 Hz
(II) VIA(0): Not using mode “1280×800″ (hsync out of range)
Your monitor is being detected as default, thats the cause of your problems, not the video card.
You should set the max. vertical range and horizontal range so Xorg can autoadjust the refresh rate to the resolution.
I will post my Monitor xorg.conf section so you can have a look at it.
Also, there are other problems and errors. You should comment the DRI entries, and the wacom one too.
Regards
@leonardo: ;)
thanks a lot for trying to help me…
…actually i tried a lot of things since yesterday… i installed the openchrome-driver over this one, then again this one, then again openchrome, then played around a lot in my xorg.conf and read man xorg, man xorg.conf, restarted the server and my machine about 100 times (at least) and did not sleep much. actually i am without a running xserver and am writing this in the lynx-text-browser. but i learned somethings… the very moment i try to reinstall this official via unichrome driver for VN800, i’ll let you know what’s going on.
unfortunately i can not easily access my e-mail right now and do not really how-to copy and paste my xorg.conf and xorg.0.log into this text-window.
i’ll definitely keep you informed about my progress and definitely apípreciate your help ;)
2 minutes later: yes ! i got my xserver back ;!
but on a really weird resolution – i guess i did something wrong in driver-compiling, as the xorg.0.log states:
(II) via: driver for VIA chipsets: CLE266, KM400/KN400, K8M800/K8N800, PM800/PM880/CN400, P4M800PRO, CX700, K8M890, P4M890, CN750, P4M900
(–) Chipset P4M800PRO found
i guess instead a VN800 Chipset should be found.
i’m gonna repeat the process AND/OR dig deeper…
DRI-support is commented out by now. My Monitor is a Laptop-TFT, are there any hsync-vsync-rates for that ?
i’ll report more later… thanks for the tutorial and help.
okay – i did it again :]
i followed all steps from this manual, got my xserver running again and put my xorg.conf and Xorg.0.log on my webspace, so you can have a look at it.
http://ooommm.org/lab/linux/Xorg.0.log
http://ooommm.org/lab/linux/xorg.conf
i don’t understand why the Xorg.0.log still detects the wrong driver, and not my VN800:
(II) via: driver for VIA chipsets: CLE266, KM400/KN400, K8M800/K8N800, PM800/PM880/CN400, P4M800PRO, CX700, K8M890, P4M890, CN750, P4M900
(–) Chipset P4M800PRO found
and – yes – now i am to 640×480, not even 800×600 anymore… …any ideas are appreciated.
i can read e-mail now: [email protected]
;j
Are you trying the updated drivers?
Via Linux Drivers
More specifically, the second entry is related to your chipset. You should download that version, and try the same steps as the ones above, they shouldn’t differ much in that aspect, except for the driver version part. Also, what’s your motherboard model and processor type?
Here is the direct link the drivers, just in case.
Greetings Leonardo, glad to read you :]
My System is like this:
6.10 Edgy Eft on Fujitsu-Siemens Amilo Pro V 2035, Intel Celeron M 370 1.5GHz, 768MB RAM, Graphic: VIA VN800 Mobile, Sound Via AC97, ALPS Touchpad, USB-Mouse.
More Data in this pdf:
http://vilpart.fujitsu-siemens.de/vil/pc/region_d/datenblaetter/amilo/db_amilo_pro_v2035_ed3.pdf
I did not see the new drivers – looks like hope on the horizon – i’m gonna try that immediately (although i’m already getting used to 640×480, gives somekind of oldschool-videogame-feeling).
Gonna be back to report soon (crashing xservers don’t scare me anymore – i live in xorg.conf now…).
Yipppieeeeeeee-ka-yoooooo-wooooooooo-haaaaaaa ;!
http://ooommm.org/lab/linux-01/xorg.conf
http://ooommm.org/lab/linux-01/Xorg.0.log
With the new driver it’s running well. After Adding the “1280×800″ Modes in the Screen Section of xorg.conf i finally have my desired resolution.
Strangely the Xorg.0.log is still recognizing the wrong driver identification:
glxinfo is not really satisfying:
and glxgears -printfps isn’t making me happy neither:
… but at least i can see again ;)
Thanks again for the good tutorial and the friendly help :)
I still welcome any tips how to get these graphics running faster…
Im glad its working and the tutorial was of some help :)
Regarding the performance… you should note that the VIA drivers are only for 2D, and that they dont have almost any 3D optimization, so you wont get much out of them.
The haven’t open sourced the 3D part yet, we just have to hope they will someday.
If i find anything relating 3D performance on VIA chipsets I will be posting about it!
Regards!
https://help.ubuntu.com/community/OpenChrome
That is the other Tutorial i tried, and i’m gonna try again in some days, but first i have to do some work that definitely needs 1280×800 – after that i’ll get back to experimental mode ;)
Valeo Galera -_-
I am having issues running the ./makedriver, I already had to edit the makedriver makefile because it wasn’t recognizing my customized kernel of edgy. After that I am still erroring out running the makedriver.
I am getting this error.
cp: cannot stat `via_drv.o’: No such file or direct
its like its looking for the source for the Xserver. Any advice will be appreciated.
Hey guys, to respond to emachine’s problem first, I had this issue also. You are getting this error when you run ./vinstall_2D, right? if so, you need to move this script to the /CN_CX700-CN800XORG40071 directory and execute it there. This solved my problem.
Now onto my problem. I’ve installed the newest drivers, and I can choose any resolution I want for a computer monitor, and it all works fine when I have my monitor plugged in and my tv plugged in at the same time. But I want this box to be only hooked up to the TV. When I do this, my resolution goes to 640×480 and I can’t change it. My xorg.conf is below. The only line i’ve added is Option “ActiveDevice” “TV”.
I’m thinking that I could use a screen section for my TV-out, but I’m not really sure what to put for that.
Thanks. (i’ll check back frequently)
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type “man /etc/X11/xorg.conf” at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section “Files”
FontPath “/usr/share/X11/fonts/misc”
FontPath “/usr/share/X11/fonts/cyrillic”
FontPath “/usr/share/X11/fonts/100dpi/:unscaled”
FontPath “/usr/share/X11/fonts/75dpi/:unscaled”
FontPath “/usr/share/X11/fonts/Type1″
FontPath “/usr/share/X11/fonts/100dpi”
FontPath “/usr/share/X11/fonts/75dpi”
FontPath “/usr/share/fonts/X11/misc”
# path to defoma fonts
FontPath “/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType”
EndSection
Section “Module”
Load “glx”
Load “i2c”
Load “bitmap”
Load “ddc”
Load “dri”
Load “extmod”
Load “freetype”
Load “int10″
Load “type1″
Load “vbe”
EndSection
Section “InputDevice”
Identifier “Generic Keyboard”
Driver “kbd”
Option “CoreKeyboard”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105″
Option “XkbLayout” “us”
Option “XkbOptions” “lv3:ralt_switch”
EndSection
Section “InputDevice”
Identifier “Configured Mouse”
Driver “mouse”
Option “CorePointer”
Option “Device” “/dev/input/mice”
Option “Protocol” “ExplorerPS/2″
Option “ZAxisMapping” “4 5″
Option “Emulate3Buttons” “true”
EndSection
Section “InputDevice”
Driver “wacom”
Identifier “stylus”
Option “Device” “/dev/wacom” # Change to
# /dev/input/event
# for USB
Option “Type” “stylus”
Option “ForceDevice” “ISDV4″ # Tablet PC ONLY
EndSection
Section “InputDevice”
Driver “wacom”
Identifier “eraser”
Option “Device” “/dev/wacom” # Change to
# /dev/input/event
# for USB
Option “Type” “eraser”
Option “ForceDevice” “ISDV4″ # Tablet PC ONLY
EndSection
Section “InputDevice”
Driver “wacom”
Identifier “cursor”
Option “Device” “/dev/wacom” # Change to
# /dev/input/event
# for USB
Option “Type” “cursor”
Option “ForceDevice” “ISDV4″ # Tablet PC ONLY
EndSection
Section “Device”
Driver “via”
VendorName “VIA Tech”
BoardName “via”
Identifier “Generic Video Card”
BusID “PCI:1:0:0″
Option “ActiveDevice” “TV”
Option “Simulateous”
EndSection
Section “Monitor”
ModeLine “720×480″ 26.7 720 736 808 896 480 481 484 497
ModeLine “720×576″ 32.7 720 744 816 912 576 577 580 597
ModeLine “800×480″ 29.58 800 816 896 992 480 481 484 497
ModeLine “848×480″ 31.5 848 864 952 1056 480 481 484 497
ModeLine “856×480″ 31.7 856 872 960 1064 480 481 484 497
ModeLine “1024×512″ 41.3 1024 1056 1160 1296 512 513 516 531
ModeLine “1280×720″ 74.6 1280 1341 1474 1688 720 721 724 746
ModeLine “1280×768″ 80.1 1280 1344 1480 1680 768 769 772 795
ModeLine “1360×768″ 85.50 1360 1392 1712 1744 768 783 791 807 +HSync +Vsync
ModeLine “1366×768″ 85.86 1366 1440 1584 1800 768 769 772 795 -HSync +Vsync
ModeLine “1440×1050″ 126.2 1440 1536 1688 1936 1050 1051 1054 1087
ModeLine “1920×1080″ 172.9 1920 2043 2249 2578 1080 1081 1084 1118
ModeLine “720×480″ 34.9 720 752 824 928 480 481 484 502
ModeLine “720×576″ 42.6 720 760 832 944 576 577 580 602
ModeLine “848×480″ 41.0 848 880 968 1088 480 481 484 502
ModeLine “856×480″ 41.3 856 888 976 1096 480 481 484 502
ModeLine “1024×512″ 53.3 1024 1072 1176 1328 512 513 516 535
ModeLine “1280×768″ 103.0 1280 1360 1496 1712 768 769 772 802
ModeLine “1440×1050″ 160.0 1440 1536 1696 1952 1050 1051 1054 1096
ModeLine “1280×768″ 118.5 1280 1368 1504 1728 768 769 772 807
ModeLine “1440×1050″ 184.5 1440 1544 1704 1968 1050 1051 1054 1103
ModeLine “848×480″ 47.4 848 888 976 1104 480 481 484 505
Identifier “Gateway EV91″
Option “DPMS”
EndSection
Section “Screen”
Identifier “Default Screen”
Device “Generic Video Card”
Monitor “Gateway EV91″
DefaultDepth 24
SubSection “Display”
Modes “1024×768″
Depth 1
EndSubSection
SubSection “Display”
Modes “1024×768″
Depth 4
EndSubSection
SubSection “Display”
Modes “1024×768″
Depth 8
EndSubSection
SubSection “Display”
Modes “1024×768″
Depth 15
EndSubSection
SubSection “Display”
Modes “1024×768″
Depth 16
EndSubSection
SubSection “Display”
Modes “1024×768″
Depth 24
EndSubSection
EndSection
Section “ServerLayout”
Identifier “Default Layout”
Screen “Default Screen”
InputDevice “Generic Keyboard”
InputDevice “Configured Mouse”
InputDevice “stylus” “SendCoreEvents”
InputDevice “cursor” “SendCoreEvents”
InputDevice “eraser” “SendCoreEvents”
EndSection
Section “DRI”
Mode 0666
EndSection
@emachine: did the solution from shemonskizzle work for you ?
@shemonskizzle:
Did you read this .pdf provided by VIA ?
http://www.viaarena.com/Driver/via_fc5_cle266&cn400&cncx700m&&cn800&vx700m_display_appnote_ver0.8a.tar.gz
I’m not sure if it helps, but there are chapters about TV-Out ;)
@me:
I only found out now, that since i installed the VIA-Driver all videos i play have a “green-overlay-graphic-error” – any suggestions ?
Actually returning to “vesa”-driver for the moment gave me back my video-playback and even more fps in glxgears:
jobo@zbox:~$ glxgears -printfps
1477 frames in 5.0 seconds = 292.552 FPS
1482 frames in 5.1 seconds = 290.755 FPS
1482 frames in 5.0 seconds = 294.792 FPS
mmh…
@jonobo: Thank you for the reply. I did read through that information. It’s the only stuff I’ve been able to find…and all it has told me is that my TV encoder (the VT1623) is capable of higher resolutions. Too bad it doesn’t say anything about how to set those resolutions.
But wow…a green-overlay-graphic-error…never heard of it (and I assume that you have seen that google hasn’t either). I probably won’t be able to help you with that, but just for the hell of it…what video player are you using? totem works fine for me (audio is great also).
Guys, I am getting that error when I run the ./makedriver. I got the openChrome to work, but I am hearing these drivers are better.
@emachine: awesome. I’ve never heard of openchrome, but I decided to give it a try anyway. Installation was easy, and everything works perfectly now. I have my TV and computer monitor at 1024×768 (and i can probably change these if i feel like it) thank you so much guys.
-shemonskizzle
After updating system Ubuntu 6.10 I can´t run ./makedriver . Can you help mee ?
Fixed by entering to makedriver file and change version on kernel.
I just received my VIA EX (CX700M2) motherboard and try to enable the MPEG2/4 decoding by using VIA’s driver http://www.viaarena.com/Driver/cle266cn400cn-cx700cn800xorg40072-kernel-src_20061226a(20070212111755).zip and this tutorial. However after running
sudo ./makedriver drm
it complained about not finding 3D/DRI-Xorg_bin/via_dri.so which I solved by linking to 3D/DRI-Xorg_bin/Ubuntu/6.10/via_dri.so.
Then after running makedriver again it complained about not finding directory /usr/src/xc/programs/Xserver/hw/xfree86/drivers/via. Although I followed the tutorial above, including the apt-get stuff, I don’t have these directory, I don’t even have /usr/src/xc.
Any help would be appreciated.
The makedriver script checks your current kernel (for Ubuntu that is 2.6.17-10-generic). Meanwhile the Ubuntu kernel has been updated to 2.6.17-11. Changing this in the makedriver script (2 times) fixed the problem.
Thanks to emachine (http://www.ubuntuforums.org/showthread.php?t=351324) for pointing this out.
Great Taeke, thanks for posting the solution.
Regards!
Like Taeke says, if your kernel (‘uname -r’) does not match the listing in the ‘makedriver’ script you can just manualy edit it. The same goes for the ‘vinstall_2D’ script. Search for the phrase ‘ubuntu’, and you’ll find 3 or 4 places to edit in each script. This should work fine for Debian Etch as well, using Debian/4.0 as DIR1/DIR2 and OS/VER (actually I think you can use any value here).
Oh, so close!
My Ubuntu version is 2.6.17-11, so I changed the two references to 2.6.17-10 in makefile. It appeared to work and make the driver.
Then I moved to CN_CX700-CN800XORG40071 and changed the same reference (only one) in install_2D.
Now, when I try to run install_2D I get:
cp: cannot create regular file `/usr/X11R6/lib/modules/drivers’: No such file or directory
Now start to install VIA/S3G display utility…
Warning, system cannot find the /usr/X11R6/lib/libXv.so.1.0 file.
You can find the package in the installation CD
There isn’t much in my /usr/X11R6/lib/ directory. Just a subdirectory, X11 and a file, libddmpeg.so
I carefully performed each step above, and checked to make sure all the packages listed are installed.
My goal is to get dual monitors working on my Acer Aspire 1522 with its VIA K8N800.
Can anybody help me? Am I missing something? Did I do something wrong? I’ve been banging my head against this wall for a very very very long time.
Thanks!
updating my previous message…
I got past the first error by creating the modules directory it was looking for, and it put file called “drivers” in it when I tried again to install. Still getting the second message.
I may get past the next by copying libXv.so.1.0 from /usr/lib/libXv.so.1.0, but it seems something isn’t right, or these things would have been in place already.
@Julia,
Did you uninstall all -via and -unichrome, and installed all the dependencies listed above in the howto? Im asking because, as you say, something isn’t right.
If it cant build or is listing missing files, that’s because something didn’t compile right or a dependency wasn’t satisfied.
Maybe i should update the guide using the new drivers, but I don’t think the differences are so big to get so many problems… the “makedriver” and “ldconfig” commands, give you an error-free output?
Leonardo, thanks for your reply!
Yes, I went though all the steps meticulously. Since I last wrote, I tried again with a fresh Kubuntu installation. I messed around with ndiswrapper some trying to get my wireless back up, and installed Firefox, synaptic, and krusader, but otherwise didn’t make any changes to the system.
I got very similar results to the other (many) times I’ve tried it. I didn’t see errors, but I think makefile didn’t complete. It ended the same way it usually does with:
rm -f *.o
rm -f *.lo
——– Complete to make & copy driver ——–
I kept a fairly thorough log this time, with more than you probably want to know, but I’d be happy to send it to you somehow, if you’d like to have a look. (I don’t see an email link or form.)
Thanks again.
I shut down after that attempt last night. When I rebooted this morning, I couldn’t get past the command prompt. Following is some of the info it displayed before the prompt (roughly from notes):
X Window System Version 7.1.1
Build Operating System: Linux 2.6.15.7 i686
Current Operating System: Linux Julia 2.6.17-11-generic #2 SMP Thurs Feb 1 19:52:28 UTC 2007 i686
Fatal Server error: no screens found
X10: fatal IO error 104 (connection reset by peer) on X Server “:0.0″ after requests (01 entry processed) with 0 events remaining
(==) Log file: “/var/log/xorg.0.log”
(==) Using config file “/etc/X11/xorg.conf”
(EE) Failed to load “via” /module does not exist.”
(EE) No drivers available
…and I forgot to back up my xorg.conf file this time, so I edited it by hand with Joe, and changed “via” to “vesa”, but I guess it’s serious about no drivers available because I got the following command prompt login:
Ubuntu 6.10 Julia tty1
Julia login:
I saved the log I made to my fat32 drive. This is a dual boot machine, so I have access to it here in Windows if you want to see it. I could also copy the xorg.0.log over here too.
@Julia,
According to the error you post, it cant find the module, and it seems there is no ‘/module’ directory… which is weird but I’m sure there shouldn’t be one, at least not if thats the full path for it.
Send me your logs to “hombrepac (o) gmail”
I will have a look at them and see if i can find anything of use.
Regards!
Leonardo, knowing somebody was willing to help has been a real boon. I went back and looked at my logs more closely before I sent them, and found some clues myself. When I ran the very first step, it did nothing, because xserver-xorg-video-unichrome was not installed.
So, I cut it out of the command and just ran sudo apt-get remove xserver-xorg-video-via. Doing that uninstalls xorg, and xserver-org, and nothing else we did put it back. It also uninstalled kubuntu-desktop, and I thought that was the real problem, however, I since have found out it wasn’t.
Another problem was that sysutils wasn’t installing, and I hadn’t noticed. I had to enable universe to get it to show up. Eventually I got the driver to compile, and install, but the result was a black screen.
I tried a fresh install, and compiled and installed before I let it update, but got the same black screen with no login prompt. Something along the way made me suspect kde, so I then tried the same thing – a fresh install before updating with Ubuntu instead of Kubuntu with the same result.
I let it update, and installed again, and the driver compiled without any errors, but still took me to the black screen.
I found a command somewhere for verbose output to the log file, and discovered there’s a problem with the VGA BIOS. The errors were:
Bad V_Bios checksum
Vesa BIOS detected
VESA VBE version 3.0
I don’t know what to make of this. I’ve been all over the place trying to find information about possibly updating the VGA BIOS on and Acer 1522lmi, but have come up empty. I checked in my BIOS settings, and the only thing I can do there is adjust the memory allocation. It’s set at 64, and the other choices are 32 and 16. I haven’t messed with those yet. It also tells me in setup, that I it’s using VGA BIOS version 90.F8.00.40
That’s probably all beyond the scope of your “How to”, but I wanted to let you know where it stands.
Thanks, again.
Leonardo, I’m starting from the beginning yet again. This time, maybe you can confirm something for me.
I’m now trying this on Ubuntu instead of Kubuntu, but I get the same results every time either way on a clean install of Ubuntu 6.11.
After the first step:
sudo apt-get remove xserver-sorg-video via xserver-xorg-video-unichrome
I get:
xserver xserver-xorg-video-unichrome is not installed.
The following packages were autoinstalled and are no longer needed:
xserver-xorg
xserver-xorg-video-all
ubuntu-desktop
xserver-xorg-video-via
xorg
Use ‘apt-get autoremove’ to remove them
The following packages will be REMOVED!
ubuntu-desktop
xorg
xserver-xorg
xserver-xorg-video-all
xserver-xorg-video-via
It seems odd that it tells me to use autoremove to remove them, then turns around and does it itself.
If I let it uninstall all that and go through the rest of the steps, I can’t compile the driver. If I don’t let it remove it, the driver seems to compile, but doesn’t work – black screen, and the errors I mentioned above.
So, my question is, do my results from that first step look okay to you? Or do you think something is different in 6.11? If so, any suggestions for how to get past it?
Thanks once again.
Hi Julia,
I think here is the problem: you are removing the packages with one being mistyped. Check that you remove exactly this two packages:
1) xserver-xorg-video-via
2) xserver-xorg-video-unichrome
From your post i see you get to remove ‘xserver-xorg’ that shouldnt happen.
Try this:
sudo apt-get remove xserver-xorg-video-via
sudo apt-get remove xserver-xorg-video-unichrome
If it says its not installed. Its ok.
It shouldn’t remove anything other than those two packages, so if something else is being done, then something went wrong somewhere. Post as soon as you have any news!
Regards
Hello leonardo,
I try to install Fedora6 on my Asus M2V-MX with K8M890. I try to download files from the driverspage as you write above, but I get no linux-drivers, only promotionsheets.
I do have another problem, after installing I only see: 90K/60HZ frequency out of range.
So to folow your instructions this problem has to be fixed first, but I dont know how. If you could help,best regards.
Sorry, the typo was just in my post here. Here are copy and pasted results of the first command:
julia@Julia:~$ sudo apt-get remove xserver-xorg-video-via
Password:
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
xserver-xorg xserver-xorg-video-all ubuntu-desktop xserver-xorg-video-via
xorg
Use ‘apt-get autoremove’ to remove them.
The following packages will be REMOVED:
ubuntu-desktop xorg xserver-xorg xserver-xorg-video-all
xserver-xorg-video-via
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 1159kB disk space will be freed.
Do you want to continue [Y/n]?
I get the same results no matter what I do. I’ve reinstalled Ubuntu and tried Kubuntu completely from scratch several times. The results are always the same, whether I’m logged in as my user, and using sudo, or whether I’m logged in as root. It happens whether I’m logged into a console window, logged out of xserver using ctrl-alt-backspace, or logged in as root directly from grub to recovery mode.
No matter what I do, it wants to take all those packages out. When I let it, I end up in a mess, and wind up reinstalling. If I don’t let it, I can’t make the driver work.
This is happening on Ubuntu and Kubuntu completely updated. I tried going through the process on a few installations before updating. It’s been a while since I tried that, so I don’t remember the exact results, but it didn’t work either.
I tried earlier with the 72 package, but lost it in a reformat and can’t find it anywhere anymore. I can find instructions, but no package. So, I’ve used 71 the last few times. I’m not 100% sure either is the right package for me with my K8N800.
I took a little detour through Openchrome this week, which is what’s installed at the moment, but still haven’t managed to get dual monitors set up. There are many xorg.com examples out there, and various methods for achieving dual monitors, but none have worked yet, so I’m inclined to think it’s still the driver. (Dual monitors work fine in Windows on this machine).
I’m going to give it a try again now with Via’s package specifically for the K8N800. Their instructions are clunky, but I’m going to give that a try. I’ll be back to let you know how it goes!
Julia
I tried installing K8M64XF41061-kernel-src_20050926, but its makefile lacks any reference to Ubuntu. Changing an existing reference for 6.11 is one thing, adding it in from scratch looks too messy for me.
I found the 72 version, and tried it even though it doesn’t say it supports K8N800. Tried installing on top my old driver, and it gives me a black screen.
Tried uninstalling xserver-xorg-video-via using Synaptic. it wants to uninstall the all same packages I mentioned above. I asked a friend, and he checked his system – the same thing happens for him.
Hi, This link looks interesting, but the via source indicates FC4? Will this work on FC6 before I even try to start messing around. I am a Linux/FC newbie by the way, so have been trying to investigate all this with lot of frustration ….
I can not even get X windows to run on FC6, so have not been able to even set up my DSL link! I’m still using grub to run XP to get on the internet!!!
Here’s my info so far
Motherboard: VIA Technologies – K8M890M2MA
Video: K8M890CE
OS: Linux 2.6.18-1.2798.fc6
Video part of kudzu probe:
…
class: VIDEO
bus: PCI
detached: 0
desc: “VIA Technologies, Inc. Unknown device 3230″
vendorId: 1106
deviceId: 3230
subVendorId: 105b
subDeviceId: 0c84
….
Regards,
Kevin (South Africa)
Hi!
I’ve the Edgy with the new -11 Kernel. I edited the makedriver an the vinstall_2D – successfully. Both of them were succsessfully installed for my k8m890 . But aufter the restart I only have an error Message “no screens found”. In the Xorg.0.log there’s a line “(EE) No devices detected.”
Can anybody help me??!
Jonas
You can see if this link works better for you.
https://help.ubuntu.com/community/OpenChrome
Jonas, I keep running into like that too with the new kernel. I have tried everything I could think of and looked all over for solutions, but still no answer. If you find a solution, please post back here!
Hi I have the same problem than Julia. I have an Amilo Li 1705 with IGP Via Chrome9 HC (P4M900), and running on kubuntu edgy 6.1, there’s no way I can get to uninstall xserver-…-via without uninstalling xserver-xorg and the rest of the packages julia wrote before. If I try installing xserver-xorg, then it auto-installs the xserver-..-via package. Anyway, I tried to install the driver and everything worked (all dependencies installed and reinstalled). it worked flawessly but when I do a reboot the screen starts doing weird things, it starts with a black screen and slowly changes to white. Tried also Openchrome and same result. Any ideas?
Hi !
I have Ubuntu 7.04 beta in my computer with chip K8M890 and from now on the driver vesa is better working then via.
jep, do you know a way to get an extended desktop on an external monitor using vesa or any other drivers?
No Julia, I don’t know how to do.
Here is what I get right at the end…
./vinstall_2D
——– install start ——–
cp: cannot stat `XServer/via_drv.o’: No such file or directory
Now start to install VIA/S3G display utility…
Warning, system cannot find the /usr/X11R6/lib/libXv.so.1.0 file.
You can find the package in the installation CD.
Abort, the utility is not installed.
I can find via_drv.o it’s installed, but libXv.so.1.0 is missing. I can not even find one to download. I’m guessing something has gone wrong but don’t know what. Any ideas?
Well it looks like no one comes here anymore…
It seems like some people with older model video can get this to work. Has anyone with P4M900 managed to get drivers installed? I’m running Debian Etch, 2.6.18-4-686. I was hoping to at least be able to play classic quake on my laptop…AAARRGGG!!!
Alan, I check back once in a while to see if anybody has any news. I’m still hoping to get it working.
Hi people.
I guess I should post an updated version, but i dont have the time right now (thats why there are no new posts either).
I have a K8M900/CE working with the OpenChrome drivers, those work with the same code base of the P4M900, if that is of some help, you should try those. Here is a link:
https://help.ubuntu.com/community/OpenChrome
Regards
Awesome!
I followed the link to a wiki page with more link for different flavors of Linux. However the one that shows, Debian/Ubuntu has
http://www.csd.uwo.ca/~mfgalizi/debian when I click on it I get a forbidden warning comes up. I guess I’ll check back there later.
I ended up making a windoze partition to play quake on, which sucks, oh well. I’ll probably end up giving this to some one in the family.
Thanks Alan :)
[...] * How-to: VIA K8M890 Chrome 9 IGP and Linux’s Xorg – Ubuntu Edgy 6.10 * HOW TO: Compiling and Installing the OpenChrome Graphical VIA [...]
[...] I’m following these slightly outdated instructions… here’s the rough set of steps I’m taking: 1. cd src 2. vim [...]
Can I use the 3d effect by this process??
Please help me to get 3d effect.
I am using P4M900.
Ok! los Amigos de la caminhada em Vida livre (linux) solo Compania delo Chipset VIA que nos faz esta Vida male Ruim !!
[...] [...]
[...] tutorial is an updated version of the one made two years ago. After two years of development, the OpenChrome drivers are looking much better than the Via ones, [...]
You wouldn’t believe it but I’ve wasted all day digging for some content articles about this. You might be a lifesaver, it was an very good read and has helped me out to no end. Cheers!