Description of problem: Via module will not load. System:
AMD Duron 800
VIA KM400 integrated chipset
256M DDR RAM
30G MAXTOR HD
I have to load the vesa generic driver to get the GUI to run, but when
I log out or try to restart the computer, the system crashes and seems
to go into suspend mode. I must do a hard reset, and edit out "rhgb
quiet" in GRUB to restart.
Version-Release number of selected component (if applicable):
How reproducible: Attempt to log out of session or restart computer
from graphical mode, monitor goes black and suspend light flashes.
During boot the message "Module via not found" is displyed.
Steps to Reproduce:
1. Log out of graphical session.
2. Press restart button.
3. Edit GRUB, remove "rhgb quiet"
4. Message display during boot "Module via failed to load".
5. VIA driver option not available in display configuration.
VIA chipset detected during installation, and proper module loaded.
VIA provides the driver module for Kernel 2.4 on their website, but I
have not been able to install it on Test 3 with kernel 2.6.
The proper drivers (open source) are on unichrome.sf.net but Im not
sure if they are all merged into FC2test yet
okay, thanks Alan. I was under the impression the driver was included
in the Xorg 6.7 release (does say that on the Xorg website), and it
does show up in the driver list when I run "X -configure" ,but the
module isn't there.
BTW I missed your post on the test-list from 5/1, talking about bug
status and via problems in X. If I had seen that I wouldn't have
opened this bug report, my apologies. MJW
X.org does contain the "via" driver. This is a 2D-only accelerated
driver, which also is part of XFree86 4.4.0, although there are
slight differences between the X.org driver and the XFree86 one
(the X.org one is newer IIRC).
Oops.. Forgot to respond to Alan's comment above...
Alan) The unichrome drivers are not merged into our X.org X11 yet.
We currently are shipping just the stock X.org drivers. Hopefully
the unichrome.sf.net drivers will get merged into X.org CVS head
soon, and into Mesa as well, and we can just pick up the merge from
our next sync to upstream. Alternatively, I will probably merge
the newer driver into Fedora Core 3 development once FC2 is out the
Since updating with yum today, everything is working fine on the
updated kernel. Seems the problem was not the VIA driver, since I am
running the VIA KM400 on the vesa generic driver. Guess you can close
this one out.
Thank you for responding and thanks for all the good work. MJW
Thanks for the update.. Setting status to "CURRENTRELEASE".