LinuxQuestions.org - VIA/S3G video drivers for Asus A7V8X-MX-UAY

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - VIA/S3G video drivers for Asus A7V8X-MX-UAY (https://www.linuxquestions.org/questions/linux-hardware-18/via-s3g-video-drivers-for-asus-a7v8x-mx-uay-131676/)

VIA/S3G video drivers for Asus A7V8X-MX-UAY

I know it's naughty - I've posted this at another forum as well but I'm not getting any replies.

I am trying to install the VIA/S3G video drivers on my new computer, which has an Asus A7V8X-MX-UAY main board with onboard sound and graphics. It's equipped with a VIA VT8235 CA Southbridge Conroller. The CPU is an Athlon XP 2600.

At present the display is ok but not very good. The monitor is flickering slightly and there are no GL drivers to smooth things out.

The motherboard came with display drivers on the CD and "VIA/S3G CLE266 Installation Notes for Linux XFree86".

I followed these accurately. Given the choice between CPUs
1. VIA C3-2(Nehemiah) or INTEL Pentium 2/3/4
2. VIA C3
3. AMD K 7/8
I chose the AMD option and proceded to install. The following is the output:

Code:

cp: cannot stat `//k7/via_v4l_drv.o': No such file or directory

cp: cannot stat `//k7/videodev.o': No such file or directory

cp: cannot stat `//k7/via_drv.o': No such file or directory

cp: cannot stat `//k7/via.o': No such file or directory

cp: cannot stat `//k7/via_dri.so': No such file or directory

cp: cannot stat `//k7/libddmpeg.so': No such file or directory

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/miropcm20.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-aimslab.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-aztech.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-cadet.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-gemtek-pci.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-gemtek.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-maestro.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-maxiradio.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-rtrack2.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-sf16fmi.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-sf16fmr2.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-terratec.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-trust.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-typhoon.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/radio/radio-zoltrix.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/bttv.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/bw-qcam.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/c-qcam.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/cpia.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/meye.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/pms.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/saa5249.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/stradis.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/via_v4l_drv.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/videodev.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/videodev.o.bak

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/w9966.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/zoran.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/media/video/zr36067.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/dsbr100.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/ov511.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/pwc.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/se401.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/stv680.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/usbvideo.o

depmod: *** Unresolved symbols in /lib/modules/2.4.20-20.9/kernel/drivers/usb/vicam.o

/lib/modules/2.4.20-20.9/kernel/drivers/char/agp/agpgart.o: init_module: Invalid argument

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

    You may find more information in syslog or the output from dmesg

/lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o: kernel-module version mismatch

      /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o was compiled for kernel version 2.4.18-14

      while this kernel is version 2.4.20-20.9.

/lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o: insmod /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o failed

/lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o: insmod via_v4l_drv failed

/lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o: kernel-module version mismatch

      /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o was compiled for kernel version 2.4.18-14

      while this kernel is version 2.4.20-20.9.

Now start to install VIA(S3) display utility...

Put the main program(s3utility) into the bin directory: /usr/local/bin

Utility installation is finished!

-------- vinstall end --------

I don't know much about it, but appears that the install is not recognizing my kernel version.

Could someone please help me solve this problem.

Thanks folks.

Abra-kadaba Bump :confused:

I'm desperate. Could someone help me please, or at least suggest where I could find answers to this problem.

Which linux are you using?

I'm using Redhat 9 kernel 2.4.20-20.9

I had the same kind of problem for a VIA chipset on my laptop. The drivers provided by VIA only work with the stock kernel of the target distro; the shell script is poorly written and fails miserably with these kind of error messages in most cases.

For instance, if you downloaded a "RedHat 9" driver, it will only work with kernel 2.4.9-8 or whatever comes with RedHat 9. Of course, VIA supports only a very limited set of distros...

I personnaly gave up installing the driver for my chipset, and I have to run X in vesa mode...

Nevertheless, if the following command:

Code:

insmod -f /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o

(run as root) does not produce any error, there may be a work-around.

Thanks for your help FRACA7 !

Quote:

Nevertheless, if the following command:

code:insmod -f /lib/modules/2.4.20-20.9/kernel/drivers/char/drm/via.o

(run as root) does not produce any error, there may be a work-around.

Yes, produces lots of errors and basically says that the driver is compiled for a different kernel - just like you said. Bummer !

The more I read about the problem, the more it seems that it's a lost cause trying to fix it. Next time I'll make sure that my motherboard and all the processors on it are Linux compatible.

Now, if I still wanted to fix the problem, would it be possible to install a good graphics card on the motherboard and work around the problem that way ? Bypassing the VIA Southbridge controller. Is this a solution or will it still not work? If not, why not? Which graphics cards are 100% Linux compatible ?

I just took a look at www.viaarena.com and it seems they provide kernel-independent binaries and even source for this particular chipset. Their layout is confusing though, and I don't know if it's really the source for the full driver or just the framebuffer...

Try here: http://www.viaarena.com/?PageID=325

Quote:

The more I read about the problem, the more it seems that it's a lost cause trying to fix it. Next time I'll make sure that my motherboard and all the processors on it are Linux compatible.

Now, if I still wanted to fix the problem, would it be possible to install a good graphics card on the motherboard and work around the problem that way ? Bypassing the VIA Southbridge controller. Is this a solution or will it still not work? If not, why not? Which graphics cards are 100% Linux compatible ?

That would work; see the HCL for compatible cards (http://www.linuxquestions.org/hcl/).

Quote:

Try here: http://www.viaarena.com/?PageID=325

I have downloaded the Lite Binary (clexf40038-lite-bin) file from that page and tried to install it, but to no avail. I'm getting the same error messages. Also, when it gives me the options of processors (during installation), there is no Athlon or K400 listed. Either of the other 2 options result in the same error messages again.

I'm currently downloading the Full Binary to see how it goes, but 51Mb over a dial-up modem will take some time. I'm not holding my breath for it to work ......

Thanks again. I'll post to tell what happened.

Let it be, I took a look at it and it's absolutely not 'kernel independent', it's just all the kernel-dependent ones packaged together... Useless... And you can't get the source :(

Yup, you're right !

I saw your latest post after I downloaded and tried. Useless as you said. Same problems.

Well, I guess my only fix will be a nice graphics card. From what I read on the link you provided the Nvidia FX 5200 128Mb is the go.

Thanks so much for looking into it for me and helping me with my problem,. Now I know exactly where I'm at and what I've suspected has been confirmed by you. It's nice to know I'd waste my time if I tried any more.

See you around. ;)