This one took me some time to find out.
LinuxBIOS v2 contains a flash utility called "flash_rom". It can be found under LinuxBIOS - in the package under freebios2/util/flash_and_burn.
This utility can be used to flash the bios instead of awdflash.

# ./flash_rom --help
The arguments are:
usage: ./flash_rom [-rwv] [-c chipname] [-s exclude_start] [-e exclude_end] [file]
-r: read flash and save into file
-w: write file into flash (default when file is specified)
-v: verify flash against file
-c: probe only for specified flash chip
-s: exclude start position
-e: exclude end postion
 If no file is specified, then all that happens
 is that flash info is dumped

A tipical flash-session would be:

./flash_rom -r test.bin
The arguments are:
-r
test.bin
Calibrating timer since microsleep sucks ... takes a second
Setting up microsecond timing loop
260M loops per second
OK, calibrated, now do the deed
Enabling flash write on VT8235...OK
Trying Am29F040B, 512 KB
probe_29f040b: id1 0x24, id2 0xa6
Trying At29C040A, 512 KB
probe_jedec: id1 0xbf, id2 0xb6
Trying Mx29f002, 256 KB
probe_29f002: id1 0xbf, id2 0xb6
Trying SST29EE020A, 256 KB
probe_jedec: id1 0xbf, id2 0xb6
Trying SST28SF040A, 512 KB
probe_28sf040: id1 0x24, id2 0xa6
Trying SST39SF020A, 256 KB
probe_jedec: id1 0xbf, id2 0xb6
SST39SF020A found at physical address: 0xfffc0000
Part is SST39SF020A
Reading Flash...done

Get the new Bios - and burn it with:

# ./flash_rom -w epiam_116_fixed.bin
The arguments are:
-w
epiam_116_fixed.bin
Calibrating timer since microsleep sucks ... takes a second
Setting up microsecond timing loop
252M loops per second
OK, calibrated, now do the deed
Enabling flash write on VT8235...OK
Trying Am29F040B, 512 KB
probe_29f040b: id1 0x24, id2 0xa6
Trying At29C040A, 512 KB
probe_jedec: id1 0xbf, id2 0xb6
Trying Mx29f002, 256 KB
probe_29f002: id1 0xbf, id2 0xb6
Trying SST29EE020A, 256 KB
probe_jedec: id1 0xbf, id2 0xb6
Trying SST28SF040A, 512 KB
probe_28sf040: id1 0x24, id2 0xa6
Trying SST39SF020A, 256 KB
probe_jedec: id1 0xbf, id2 0xb6
SST39SF020A found at physical address: 0xfffc0000
Part is SST39SF020A
Programming Page: 0063 at address: 0x0003f000

You should then reread the installed bios from Flash - and compare it against the one you have just uploaded using:

 diff <newfile> <oldfile>

There should be no difference between the files ! 

 Usually, you would use the Flitedeck utility from VIA. However - this one is deprecated, and won't work on the new plattform.
The problem with the Hush-PC is that it has no Floppy drive connected to it. If you try a USB-Floppy drive, it won't work either - the awdflash utility will deactivate all USB stuff _before_ reading the new BIOS in - thus cutting the tree it's sitting on.

Solution: Burn a Bootable CD-rom. for this -you need a Floppy-bootdisk image. With a Cd-Writing utility - copy all DOS-Files onto the CD, add the awdflash.exe utility and the new BIOS.bin file on it. Then go to the next step to add the bootable Image (Use the Floppy-Image) and you're done.
Boot from the CD - and once done - type in the following command:

awdflash.exe BIOS.bin /py/sn/cd/cp/tiny

and you should be done. Note that this should work with future and old versions of BIOS's.  

 This results from the Fact that TV-Out has a maximum resolution of 1024x768 using the CLE266 Overlay Capabilities. So - in case you're using the Frame-Buffer device to run X-Windows, make sure in the BIOS you deactivate the TV Out in the CMOS-Setup, Advanced Chipset Features/Select Display Device - just use CRT. 

 Actually - what you see is the noise of many things going on on your system - it mostly happens on Harddisk Accesses, Sound-card playing music, Strong Network-Transfers etc.

• It has something to do with the Powerunit/Mass connection and the connection between the Screen and the Onboard graphic card
• Once you make sure the Case and the Mass of your Board is connected to the Generall Mass (in Germany it's called "Erdung"), this noise apparitions go away on your Screen
• It can also have something to do with the Powerunit not beeing strong enough - so you can try out a stronger Powerunit to see if it solves the problem

 This is most probably due to the fact that you're using the wrong Sampling speed. It avered to work correctly when using the alsa-Drivers 0.9.x with x > 4 and 1.0.x with x < 2- but you'll have to recompile these. Under Mandrake however - these will only compile if you deactivate the verbose-printk stuff. In the Alsa-Driver directory, compile it using:

./configure --disable-verbose-printk && make && make install

or you'll get unresolved dependencies. Once this is done, make sure the alsa drivers are loaded using dxs_support=3. In the /etc/modules.conf - this will look like:

# Sound Stuff
above snd-via82xx snd-pcm-oss
alias sound-slot-0 snd-via82xx
options snd-via82xx dxs_support=3

And it should work :) 

 Mandrake has the correct lm_sensors version in - however - the sensors_detect perl-script needs to be updated to find the correct chip. You can get that script here:
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/prog/detect/sensors-detect
A local copy is attached to this FAQ entry.
Once run - you need to make sure that the following modules are loaded through /etc/sysconfig/lm_sensors

MODULE_0=i2c-viapro
MODULE_1=i2c-isa
MODULE_2=eeprom
MODULE_3=vt1211

After that - adapt the /etc/sensors.conf file - Check mine in the related files section of this FAQ. Note that the Mini-ITC Nemiah M10000 seem to have only one temperature sensor. All others give back Junk.
Check the entire setup by starting it through /etc/rc.d/init.d/lm_sensors start After that - a sensors output should provide something like this:

eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0500
Algorithm: Non-I2C SMBus adapter
Memory type:            DDR SDRAM DIMM SPD
Memory size (MB):       512

vt1211-isa-6000
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore1:    +2.31 V  (min =  +2.24 V, max =  +2.74 V)
+5V:       +4.71 V  (min =  +4.48 V, max =  +5.49 V)
+12V:     +11.78 V  (min = +10.77 V, max = +13.15 V)
+3.3V:     +3.28 V  (min =  +3.13 V, max =  +3.45 V)
Proc Temp: +56.5C  (limit =  +65C, hysteresis =  +60C)

 The 2.6.2 kernel works well on the EPIA boards, but the patch is not as well developed as the 2.4 patch. First, start with a recent distribution - I used Fedora core 1. Download the 2.6.2 kernel from kernel.org. Next, download the 2.6.1 kernel patch. Don't worry - the 2.6.1 patch works with the 2.6.2 kernel source but we will have to create a symlink so that the patch finds the source tree. Next, extract and patch the kernel:

bash$ tar -xjf linux-2.6.2.tar.bz2
bash$ cd linux-2.6.2
bash$ gunzip -c ../via-v4l-1.4a-drm.patch.gz | patch -p1

If you have a more recent kernel - as the 2.6.11.5 - you don' t need to patch it - as all required patches are in the main kernel stream.
Next we have to configure the kernel. If you want, you can download this stripped down config file. Copy it to linux-2.6.2/.config and execute the make xconfig. The example config file is designed for a Nehemiah processor. If you are using an earlier processor then you must change the CPU type to C3. Then save and build.

bash$ make xconfig
bash$ make bzImage
bash$ make modules
bash$ su
Password:
bash# make modules_install
bash# make install

You should know how to modify your boot configuration to boot from the new kernel. Note that I have not been able to use the VESA framebuffer with the 2.6.2 kernel - the virtual terminals are blank. So boot in normal 80x25 mode. You will load the drivers manually (or edit your init scripts):

bash# /sbin/modprobe uhci-hcd
bash# /sbin/modprobe via82cxxx_audio
bash# /sbin/modprobe hid
bash# /sbin/modprobe agpgart
bash# /sbin/modprobe via_agp
bash# /sbin/modprobe via_v4l_drv
bash# /sbin/modprobe via

Also, you may need to edit your /etc/modules.conf file. The usb module has changed names, so you should have something like this:

alias usb-controller uhci-hcd
alias usb-controller1 uhci-hcd

 Check out complete details on the VIA webpage

In the download section you can also find:
* Epia M10000 Operating Guidelines
* Epia M10000 User's Manual
 

 For the X-Windows System xorg-6.8.2 - check out the following files. Plesae note - that I also have a MGA 450 PCI board in my system - for Dual-Screen - and sometimes I use the DVI-Port - as the signals the Onboard-chip provides are quite bad. This is why I also provide some xorg.configs for that board - or comabination of both.

• Gentoo 2005.0
• xorg.conf_cle266 - Plain cle266 - using one screen
• xorg.conf_cle266_mga - M10000 Board using cle266 and MGA G450 PCI Board for Dual-Screen, xinerama mode
• xorg.conf_mga450 - Plain MGA450 PCI only - using one screen
• xorg.conf_cle266_mga - M10000 Board using a MGA G450 PCI Board only for Dual-Screen, xinerama mode




• SUSE 9.3
  • xorg.conf_cle266 - As configured by the System

Please adapt your Kezboard configurations and eventually also the mouse configs. Using a US-Keyboard here, and a Logitech MX700 Wiireless mouse 

 This is a known problem of the longhaul module on the SUSE system kernel. Make SUSE can not load the longhaul module - and you're safe.

For this - boot into the single-user mode - at the lilo-prompt - add the option:

init 1

Edit the file /etc/modules.conf or /etc/modprobe.conf and make sure the following line is in there:

 alias longhaul off 

If you want to remove the module completely - go to the /lib/modules directory - and issue the following command:

find . -name "longhaul*"

This will tell you where the longhaul module is located. Move it to a different location outside the kernel-version tree, or delete it - then you should be done. Reboot and enjoy...  

 it looks really cool. Check out details at Hush Technologies. Please note that the version with M10000 Epia Board is not manufactured any more.  

 These drivers are for different use

• via_agp is needed to get agp working
• via is needed to get drm working.

If only via is loaded, drm will work, but will fail to acquire AGP, and instead use only the PCI path which for the driver you are trying to use is available only for root since it tries to access registers not even available for an insecure dri client.