In fact I was using it last year on my 11.1 and possibly 11.2 test system. BTW the user who recommended chrome9 gave you an 11.0 repo for it, and it probably worked ok then. I have used all the drivers at various stages of their development since the time of suse 10.1 (missing out 11.0) up to and including 11.2. I don't have your exact chip, but a Via unichrome pro IGP (K8M800). And I will try the commands that you wrote.Hi Tomorrow I will remove chrome9 and unichrome rpm both and after I will install them separately.

Note the xorg-x11-driver-video-unichrome-20091020-1.1.1.i586, which provides both a 'via' kernel module and a 'unichrome' module while the xorg-x11-driver-chrome9 provides only a 'via' module. When removing, its probably best to remove both chrome9 and unichrome, and then re-install the rpm you want to use. If you want to use the xorg-x11-driver-video-chrome9-5.74.33-2.1.i586 you may need to remove the xorg-x11-driver-video-unichrome. I think you should remove xorg-x11-driver-video-chrome9-5.74.33-2.1.i586 as long as you have the xorg-x11-driver-video-unichrome from OSS repos. Xorg-x11-driver-video-unichrome-20091020-1.1.1.i586Seems that chrome9 and unichrome (from OSS repos) are installed both.Both the xorg-x11-driver-video-chrome9 and the xorg-x11-driver-video-unichrome provide a 'via' graphic kernel module (driver) so its not clear to me at all what driver is being configured when you try to run 'sax2 -r -m 0=via'. (II) VIA(0): H5 3D Engine has been initilized.Ġ: /usr/sbin/xw(xorg_backtrace+0x37) ġ: /usr/sbin/xw(xf86SigHandler+0xa0) ģ: /usr/sbin/xw(miScreenInit+0x4c) Ĥ: /usr/lib/xorg/modules//libfb.so(fbFinishScreenInit+0x14a) ĥ: /usr/lib/xorg/modules//libfb.so(fbScreenInit+0xa2) Ħ: /usr/lib/xorg/modules//drivers/via_drv.so ħ: /usr/sbin/xw(AddScreen+0x1a9) Ĩ: /usr/sbin/xw(InitOutput+0x743) ġ0: /lib/libc.so.6(_libc_start_main+0xfe) (II) VIA(0): into 3D initial.3Dinitial? 0 (WW) VIA(0): Driver will try to find another refresh rate instead. (WW) VIA(0): Refresh rate setting in nf is not supported!! (II) VIA(0): VIASetDisplayPath is DuoView

failed to load kernel module 'via_chrome9'

Code: FATAL: Module via_chrome9 not found.

Via chrome9 driver