coreboot November 2003

coreboot@coreboot.org

44 participants
133 discussions

Re: LinuxBios in epia m-10000 (freebios2)
by Dave Ashley 04 Nov '03

04 Nov '03

>is the M-10000 different in some way important from the standard EPIA-M? My take is the 10000 is different only in that it has a bigger heat sink that covers the southbridge chip, and there is a cpu fan, and it runs at 1 ghz. Otherwise it is identical. My lspci -n matched exactly. Regarding epia-m, I'm not sure if the changes I posted were incorporated into the freebios tree. These consisted of 1) VGA working fully at least for going into linux/XFree86 2) Fixed vga bug where it would get in an endless loop and not exit in the init (actually came up with a workaround). 3) Improved the reboot procedure so it does a pci reset to reset the pci bus. This is for a clean soft reset. Other people don't seem to experience the epia-m problems we have. We are using them without any cooling fans, just the 600 mhz version. With the stock bios some percentage of boards are really touchy as regards overheating. They can be running fine, then you power it off and power it on again, and it will just sit there beeping forever. If I blow a fan on the motherboard that fixes it. I also don't understand the interest in the epia (Not M). We tried these first and found them unsatisfactory because the composite/svideo output had awful color banding. VIA upscaled us to the epia-m. Our current epia-m status: as far as I know everything is working 100% except the serial port is 1/2 the baud rate it should be (57600 max instead of 115200). We even have a watchdog timer that reboots the epia-m in case of lockup. Oh, and we don't have the auto SPD ddr configuration. We're running the original freebios, not freebios2. A lot of people seem to have epia-m spd configuration on their roadmap but no one has jumped into it. I recently tried building freebios2 now that the linuxbios cvs server appears working again. My system was redhat 7.1 and so wouldn't build. I've upgraded to slackware 9.1 now and am ready to try again. What I'm hoping to find is that the SPD configuration is similiar/identical across the 2 VIA chipsets. Also that there is little difference between SDRAM + DDR configuration. So that hopefully just changing a few constants will get SPD auto configuration working for the epia-m...I got as far as being able to read out the SPD contents on the epia-m (freebios) but didn't take it any further. It sounds like freebios2 is what everyone wants to work on and freebios is going to get left behind, so I'd better go along... -Dave

3 2

arima/hdama fails from current cvs
by ron minnich 04 Nov '03

04 Nov '03

I am finally getting time to do K8s again. I just did a cvs update, built linuxbios for the arima/hdama, and tested it out. It failed. Looks like the ethernet is now back on bus 2, and linux does not see the ethernets at all. Anyone else tried this lately? The K8 platforms seem, overall, to be not quite working at present. ron

2 2

proces to flash on epia m10000
by Xavier Pegenaute 04 Nov '03

04 Nov '03

Hi, may be i'm wrong in the process and this is the reason for don't work. I'll show you the exact process to do it: (first I want filo, at least i have to see something in serial line) #### freebios2 - cp targets/via/epia/Config.filo.lb to targets/via/epia/Config.lb - edit targets/via/epia/Config.lb and add: uses TTYS0_BAUD option TTYS0_BAUD=115200 - ./buildtarget via/epia/ - make in targets/via/epia/epia (yes filo.elf is where he thought), linuxbios.rom is generated - util/flash_and_burn/flash_rom ../../targets/via/epia/epia/linuxbios.rom - reboot Is it right ? Xavi.

1 0

Re: EPIA-M10000 can't work properly with VGA from HD [PMX:##]
by mirenna＠mi.ingv.it 04 Nov '03

04 Nov '03

Hi, can you tell me if the ammount of RAM DDR have you and if this ammount is hardcoded on linuxbios ... and where. Best Regards Santi Mirenna

1 0

EPIA-M10000 can't work properly with VGA from HD [PMX:##]
by eddyfu＠pchome.com.tw 04 Nov '03

04 Nov '03

>Hi, >i had problem to compile linuxbios for EPIA-M 10000. >Can you tell me please which version of linuxbios are you using, >and the way you obtain VGA+filo image. >Can you sen me tree to compile, or the bios image you obtail. >Thanks. >Santi >Mirenna The LinuxBIOS is CVS version. The following steps are getting VGA image(vga+filo.bin). #setpci -s 0:11.0 40.b=54 (accessing bios rom on EPIA-M) #dd if=/proc/kcore of=vgabios.bin bs=1 count=65536 skip=790528 #cp vgabios.bin vga+filo.bin #dd if=/filo.elf of=/vga+filo.bin bs=1 seek=65536 My romimage file used partition /dev/hda2 and kernel image named /vmlinuz.epia Regards, Eddy ========================================================== 沒錢換照相手機？快上 eBay 撿便宜 http://edm-prg.epaper.com.tw/click.php?ad_code=31602 ========================================================== PChome交友~~幸福天天有 \*^o^*// http://love.pchome.com.tw/ ==========================================================

1 0

EPIA-M10000 can't work properly with VGA from HD
by mirenna＠mi.ingv.it 04 Nov '03

04 Nov '03

Hi, i had problem to compile linuxbios for EPIA-M 10000. Can you tell me please which version of linuxbios are you using, and the way you obtain VGA+filo image. Can you sen me tree to compile, or the bios image you obtail. Thanks. Santi Mirenna

1 0

Re: EPIA-M10000 can't work properly with VGA from HD [PMX:##]
by eddyfu＠pchome.com.tw 04 Nov '03

04 Nov '03

── 以下為原始信件 ── From: ron minnich <rminnich(a)lanl.gov> To: eddyfu(a)pchome.com.tw Cc: linuxbios(a)clustermatic.org Subject: Re: EPIA-M10000 can't work properly with VGA from HD [PMX:##] can you send serial port output? ron Hi Ron Sorry!! They are some large mess codes. Best regards, Eddy ========================================================== 沒錢換照相手機？快上 eBay 撿便宜 http://edm-prg.epaper.com.tw/click.php?ad_code=31602 ========================================================== PChome交友~~幸福天天有 \*^o^*// http://love.pchome.com.tw/ ==========================================================

1 0

LAB (LinuxBIOS-like thing for embedded ARM-based devices)
by Joshua Wise 04 Nov '03

04 Nov '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, Some of you may remember me as the LAB guy (Linux As Bootldr). Just wanted to let you all know that LAB is booting on the iPAQ h3900. It's currently 512kbytes, and I don't expect it to go over that, although I'm aiming for 256kbytes. Code is in handhelds.org CVS. Does anyone have any suggestions for fitting a kernel 2.6 in sub-256k? /joshua (Also, I've got me an ABIT KG7-RAID here. I've been sick and tired of the crap BIOS that comes with it. What information do I need to collect so I can start working on this board, and what hardware do you all think I should use? Does a DOC work through a bios savior?) - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 Quote | <lilo> I akilled *@* by mistake -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/pzJpPn9tWOqA4LMRAoD1AJ44XfwpaPgOdsko+EsD7+53A2dVMwCgtO2A VlBPvGui1Hm5+Xu5SE4AjkI= =GquT -----END PGP SIGNATURE-----

1 0

EPIA-M10000 can't work properly with VGA from HD
by eddyfu＠pchome.com.tw 04 Nov '03

04 Nov '03

Hi , Have any one can help me? I used EPIA-M10000 + LinuxBIOS+ Filo 0.4.1 + mkelfImage 1.6 on Red Hat 8.0. I needed VGABIOS to use. But it can't work properly. Serial port msgs show some unknow codes. The POST number is 96. epia config file: # # LinuxBIOS config file for: VIA epia-m mini-itx # target /epia-m # via epia mainboard via/epia-m # Enable Serial Console for debugging option SERIAL_CONSOLE=1 #option SERIAL_POST=1 #option TTYS0_BAUD=115200 option TTYS0_BAUD=57600 option DEFAULT_CONSOLE_LOGLEVEL=9 option DEBUG=1 # Use 256KB Standard Flash as Normal BIOS option RAMTEST=1 option USE_GENERIC_ROM=1 option STD_FLASH=1 option VGABIOS_START=0xfffc0000 option ZKERNEL_START=0xfffd0000 option ROM_SIZE=262144 # FrameBuffer option HAVE_FRAMEBUFFER=1 option SMA_SIZE=16 option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1 option CONFIG_PCIPIOS_IRQ=1 dir src/bioscall # payload size = 192KB option PAYLOAD_SIZE=196608 # use ELF Loader to load Etherboot option USE_ELF_BOOT=1 # Use Filo as our payload payload /vga+filo.bin filo config: # !!! NOTE !!! # Do NOT add spaces or comments at the end of option lines. # It confuses some versions of make. # Image filename for automatic boot and optional command line parameter AUTOBOOT_FILE = "hda2:/vmlinuz.epia root=/dev/hda2 console=tty0 console=ttyS0,57600" # Time in second before booting AUTOBOOT_FILE AUTOBOOT_DELAY = 2 # Driver for hard disk, CompactFlash, and CD-ROM on IDE bus IDE_DISK = 1 # VGA text console VGA_CONSOLE = 1 PC_KEYBOARD = 1 # Serial console SERIAL_CONSOLE = 1 SERIAL_IOBASE = 0x3f8 SERIAL_SPEED = 57600 # Filesystems FSYS_EXT2FS = 1 FSYS_FAT = 1 FSYS_JFS = 1 FSYS_MINIX = 1 FSYS_REISERFS = 1 FSYS_XFS = 1 FSYS_ISO9660 = 1 # Support for boot disk image in bootable CD-ROM (El Torito) ELTORITO = 1 # PCI support SUPPORT_PCI = 1 # Sound support (needs SUPPORT_PCI) SUPPORT_SOUND = 1 # Sound drivers VIA_SOUND = 1 # Debugging DEBUG_ALL = 1 DEBUG_ELFBOOT = 1 DEBUG_ELFNOTE = 1 DEBUG_LINUXBIOS = 1 #DEBUG_MALLOC = 1 DEBUG_MULTIBOOT = 1 #DEBUG_SEGMENT = 1 #DEBUG_SYS_INFO = 1 #DEBUG_TIMER = 1 #DEBUG_BLOCKDEV = 1 DEBUG_PCI = 1 #DEBUG_VIA_SOUND = 1 DEBUG_LINUXLOAD = 1 DEBUG_IDE = 1 #DEBUG_ELTORITO = 1 # i386 options # Loader for standard Linux kernel image, a.k.a. /vmlinuz LINUX_LOADER = 1 # Boot FILO from Multiboot loader (eg. GRUB) MULTIBOOT_IMAGE = 1 # Use PCI Configuration Mechanism #1 (most boards) PCI_CONFIG_1 = 1 ************************************************************ Any suggestion, please tell me. Best regards, Eddy ========================================================== 沒錢換照相手機？快上 eBay 撿便宜 http://edm-prg.epaper.com.tw/click.php?ad_code=31602 ========================================================== PChome交友~~幸福天天有 \*^o^*// http://love.pchome.com.tw/ ==========================================================

2 1

device configuration
by Greg Watson 03 Nov '03

03 Nov '03

Hi, Can someone please provide some assistance on the new device configuration setup? For example, how do I configure the IDE controller on a Winbond chip? I used to do this through the enable routine in the chip_control structure but this is no longer used. I've tried using the enable_dev routine, but it never seems to get called. Do I need to do something with the 'pci' configuration statement? What is the purpose of these? I've tried defining 'pci 0:9.0 on' and 'pci 0:9.1 on' but it doesn't make any difference. Thanks, Greg

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot November 2003