-Leon My board is close to the MII, but not exact. I have a different south bridge. http://www.bcmcom.com/bcm_product_ebc3266.htm
So thinking that I can get the north bridge up, I am hoping that I can get my board to at least give me something out of the console, from there I can start debugging. I dont think the dd if=/dev/mem.... to grab the video bios will work for me, different address range's. Currently I have linuxbios 2177, same as you, but I dont have a computable flash chip (SST39SF040) currently not supported, so I am using an external burner. The biggest bug I am currently stuck on is the linuxbios.rom keeps coming out at 192k and not 256k... No clue what I have wrong. If i can get 256k then just `cat linuxbios.rom >> linuxbios.rom.512` do that twice and I should have a 512 rom. Can I snag a copy of your Config.lb? My current payload is /etc/hosts, I will switch to filo when I can get console running. For now I would just like to see ANY signs of life out of the console. Console is tested and fully running, I currently dont even use a screen, just serial console. -Adam
Leon Woestenberg wrote:
Hello Adam,
found your question on the LinuxBIOS list (see below).
I just retried the EPIA-M LinuxBIOS code again and it worked for my EPIA-M 10000 board. Actually, this is the first time I got it working. SVN HEAD tree (rev 2177) with filo 4.2.0 with Linux 2.6.11 (or so).
Note that I did *not* get VGA to work under the early LinuxBIOS boot and FILO boot, it came up when Linux booted. I controlled FILO through a null-modem serial connection.
I have attached my notes below.
Please if you proceed with your EPIA board, keep me in the loop with your experiences. It's hard to find experiences from stuff that worked.
note: Seaching for the VGA issue, it seems I should take the VGA BIOS from some specific version of VIA's BIOS...
Regards,
Leon Woestenberg.
[LinuxBIOS] Status of the epia-m
*Adam Talbot* talbotx at comcast.net mailto:linuxbios%40linuxbios.org?Subject=%5BLinuxBIOS%5D%20Status%20of%20the%20epia-m&In-Reply-To= /Tue Feb 21 23:13:44 CET 2006/
* Previous message: [LinuxBIOS] This should be an easy error... <http://www.openbios.org/pipermail/linuxbios/2006-February/013515.html> * Next message: [LinuxBIOS] EPIA M COM2 problem + possible solution? <http://www.openbios.org/pipermail/linuxbios/2006-February/013526.html> * *Messages sorted by:* [ date ] <http://www.openbios.org/pipermail/linuxbios/2006-February/date.html#13517> [ thread ] <http://www.openbios.org/pipermail/linuxbios/2006-February/thread.html#13517> [ subject ] <http://www.openbios.org/pipermail/linuxbios/2006-February/subject.html#13517> [ author ] <http://www.openbios.org/pipermail/linuxbios/2006-February/author.html#13517>
Is the current epia-m code running? -Adam
http://www.viaarena.com/default.aspx?PageID=22&DSCat=155&DCatType=3
i010t117.bin
rev 2177 of linuxbiosv2
Debugging output from the EPIA:
115200,8n1,first serial port
Extract VGA BIOS:
dd if=/dev/mem of=/video.bios.bin \ bs=1 count=65536 skip=790528
Linux sits on:
/dev/hdc2 on / type ext3 (rw,errors=remount-ro)
In the 'util/flash_and_burn' directory is the source for the 'flash_rom' utility, which is great for re-programming the flash chips on the EPIA-M / MII.
Correction: should be in 'util/flashrom' directory since 2101 or so.
apt-get install pciutils apt-get install pciutils-dev
leon@nehemiah:~/sandbox/linuxbios/util/flashrom$ sudo -s root@nehemiah:~/sandbox/linuxbios/util/flashrom# ./flashrom Calibrating delay loop... ok No LinuxBIOS table found. Enabling flash write on VT8235...tried to set 0x45 to 0x55 on VT8235 failed (WARNING ONLY) SST39SF020A found at physical address: 0xfffc0000 Flash part is SST39SF020A OK, only ENABLING flash write, but NOT FLASHING.
SST39SF020A is a 256k words of 8 bit = 2 Mbit
ST29SF040A is a 512k words of 8 bit = 4 Mbit
Note that the EPIA will address the second half of the 4 Mbit Flash! To be sure, copy the bin to both halves of the flash.
wget http://felixx.tsn.or.jp/~ts1/filo/filo-0.4.2.tar.bz2
[...]
The main configuration file for the epia-m is in 'targets/via/epia-m/Config.lb' If you need to make any changes to the configuration, for example you wish to locate filo.elf in a place other than '/filo.elf', or during the more advanced steps of this HOWTO, then these changes are made to this file. You need to re-run the './buildtarget via/epia-m' after any such change. Change the configuration file to match the full path of the filo.elf file. payload /home/leon/sandbox/linuxbios/filo.elf Regenerate the build: ./buildtarget via/epia-m
cd targets/via/epia-m/epia-m
make
cd filo edit Config make
cp filo.elf ../linuxbios cd ../linuxbios/targets ./buildtarget via/epia-m cd via/epia-m/epia-m edit Makefile
serial.c:54.34: serial.c:66.29: console.c:6.21: console.c:16.26: console.c:51.36: console.c:72.71: bist.h:11.34: auto.c:133.28: 0x81a44e0 noop Internal compiler warning: awakening noop?