coreboot

coreboot@coreboot.org

1 participants
39700 discussions

[ANNOUNCE] mkelfImage-1.18
by ebiederman＠lnxi.com 10 Nov '02

10 Nov '02

Available at: ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-1.18.tar.gz rpm -tb mkelfImage-1.18.tar.gz to build an rpm. binutils continues to give mkelfImage a hard time. And this fixes the latest batch of problems. Appearently 2.13 has a larger set of symbols in different sections that it will not subtract so I have moved a litte more the math into the linker script. Eric

1 0

[ANNOUNCE] Second paper on BIOS Interrupts as used by Windows XP.
by Adam Sulmicki 10 Nov '02

10 Nov '02

Hello, I am pleased to announce release of the second paper which study interrupts usage by Windows XP. It should help us in our efforts to add support for legacy applications, such as Windows XP, under LinuxBIOS. You can find the paper here: http://www.missl.cs.umd.edu/Projects/sebos/winint/index2.html Some of the people from the list should find their names in the Acknowledgments section. If you don't see your name there (and you contributed to the paper) drop me an email. We have fairly advanced prototype system running house and we exepect release fairly soon. Adam Sulmicki -- Adam http://www.eax.com The Supreme Headquarters of the 32 bit registers

1 2

who can solve 100MHz FSB problem of winfast6300
by zhu shi song 10 Nov '02

10 Nov '02

linuxbios now can't support 100MHz FSB of winfast6300. Who can solve the problem or give clear clues to solve it? So linuxbios can support 850MHz celeron. thanks zhu __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2

1 0

Re: VIA EPIA - Trying to get it built
by BIOS Support 10 Nov '02

10 Nov '02

>> I found that in my Makefile, which was generated without error by >> /NLBConfig.py, the path for two files is just /../freebios/mainboard.c and >> /../freebios/irq_tables.c >> Aren't they supposed to be at >> /../freebios/src/mainboard/via/epia/mainboard.c and >> /../freebios/src/mainboard/via/epia/irq_tables.c? Andrew Ip wrote: >That's right. irq_tables.c and mainboard.c should be at >freebios/src/mainboard/via/epia. OK, I didn't think anything had to be moved but that was just one way for me to get the make all the way through. >What about your linuxbios config file? Are you using the example.config in >epia's dir? My config file, at the time of the error, was /../freebios/src/mainboard/via/epia/Config. What's the deal with the one with the name Config? Now, I have successfully gotten past the make of object files by switching to the example.config you're talking about. There are other problems though.... When doing just a make this is the error: objcopy -O binary -R .note -R .comment -S linux.bin objcopy: linux.bin: No such file or directory make: *** [linux.bin] Error 1 So, I decide to see if this happens for another mainboard. So I created another environment to build another mainboard and chose PC-Chips M810LR since Antony Stone has written one of the most recent documents about building. I follow the document and get the exact same error! It must be my environment since I doubt another mainboard's make has the same problem. Is it because I need to have the environment variable LINUX pointing somewhere? It's blank when I "echo $LINUX". I built linux 2.4.19 but didn't patch since there are no patches in the /mainboard/via/epia directory. Also I never saw instructions that say to set the env var for LINUX. Yes, I'm probably showing some of my ignorance but I'm trying to follow instructions as provided. I did notice in the M810LR writeup that this kernel is the one to boot to, not the one to use for LinuxBIOS. So, how where's the Linux "kernel" for LinuxBIOS kept? Have I missed something in the documentation? Andrew Ip, which kernel went into your LinuxBIOS? I'm just trying to get caught up with where you were at with epia booting and your last listed issue with irq_tables. My build environment is 2.4.18-17.7.x (A patched RedHat 7.3 distro). Any bearing on my problems? I got the kernel source from kernel.org and it is 2.4.19 which is the version I will want to have on my IDE device (either HD or CompactFlash). If I have to change build environments I'll deal with it. Also, just so that whoever is helping me through knows where I'm trying to get to... I want to create just a boot ROM to boot Linux from IDE. I'm not looking to do any DOC stuff, ATPT. What is the file that I should be looking for to flashing my BIOS? Probably romimage? I suspect I can do the Award BIOS Flash PLCC pull and put in a brand new ST M29F002BT. Any special recommendations for getting this operation to work? Changes to which config file, etc.? Do I have to do "make floppy"? - It looks like it only puts the romimage on floppy, so where's the flashing program? The floppy should be M$-DO$ formatted as bootable before putting the romimage to it, right? I feel pretty ignorant. Not stupid, just ignorant. A long list of questions and observations but the answers will go a long way to bringing me into the LinuxBIOS fold, I hope! Andy

2 1

ide kernel loading
by John Allen 08 Nov '02

08 Nov '02

I found a parameter, BOOT_IDE, which I have enabled instead of USE_GENERIC_ROM. It appears that when I use this parameter, linuxbios tries to load the kernel from my hard ide hard drive. Is this what the parameter is meant to do? If this is the case, then I should be able to place the kernel on the hard drive instead of within the flash memory. This would solve my 256K flash size limit problem. It also seems to be easier to load the kernel from the hard drive, instead of loading a kernel from the flash, then having that kernel load the kernel from the hard drive. If I can load the kernel from the hard drive, then how do I get the kernel to the hard drive. Does it need its own partition. Maybe I could make a small raw partition at the beginning of the drive, and the rest of the root file system on another partition behind the raw one. Any thoughts? John

2 1

DOC & CWlinux SDK
by Bob Drzyzgula 08 Nov '02

08 Nov '02

I'm just now finally able to get back to a project that I started a few months ago, and I have a couple of questions. First, though, I want to offer great thanks to Andrew and CWlinux for their SDK. That stuff really is a tremendous help. First, DOC problems. I've spent about a day and a half getting an M810LMR up and running off a DOC, using one of CWlinux's images. Part of my problem turned out to be some flaky DOCs. Of four units I took out of a tube, two of them have turned out to have faulty sectors, from what I can tell. After futzing around, I finally came to the realization that I could not even get eraseall to work -- it would repeatedly give an MTD erase failure [1] error. It would fail at the same address every time, but that address was different for the two DOCs. The other two DOCs had no such problem. I guess that my main questions here are (a) are these DOCs toast, and (b) is this common with DOCs? These are labeled "MD-2800-D08/JAPAN0028HAK 1". The other issue I had was with regard to the CWlinux DOC images; I don't think this is a question so much as an FYI for Andrew and maybe other newbies, I was able to work around things and I'll be moving beyond his examples soon anyway. In cwlinux_810lmr_lite.lb, the size of the minix filesystem appears to be larger than the size of the nftl partition on the DOC [2]. This is confirmed with a error when I run the dd to write the filesystem to flash. The filesystem in the cwlinux_810lmr_mb-mii.lb image is small enough to fit, however [3]. Finally, when I use the docipl, linux.bin.gz.block, and linuxbios.block from cwlinux_810lmr_mb-mii.lb, the linux commandline gives me consoles on /dev/ttyS0 and /dev/tty0. The one on ttyS0 works fine, but the one on tty0 has carriage return issues; the virtual console on tty1 also works OK. If I use the docipl, linux.bin.gz.block, and linuxbios.block from cwlinux_810lmr_lite.lb but the minix filesystem from cwlinux_810lmr_mb-mii.lb, the command line gives me a console only on /dev/tty5 and there's a GUI splash screen. In this case, the virtual consoles, including the one on tty0, work just fine. This has worked out to be the best combination. Thanks, --Bob [1] (with defective DOC in socket) [root@linuxbios cwlinux_810lmr_lite.lb]# lsmod Module Size Used by Tainted: P binfmt_misc 6980 1 autofs 11396 0 (autoclean) (unused) sis900 15012 1 ipchains 37992 10 ide-cd 30368 0 (autoclean) cdrom 31168 0 (autoclean) [ide-cd] ext3 66464 4 (autoclean) jbd 52672 4 (autoclean) [ext3] md 62976 0 (unused) usb-ohci 22016 0 (unused) usbcore 69056 1 [usb-ohci] [root@linuxbios cwlinux_810lmr_lite.lb]# flash_on [root@linuxbios cwlinux_810lmr_lite.lb]# modprobe doc2000 [root@linuxbios cwlinux_810lmr_lite.lb]# modprobe docprobe [root@linuxbios cwlinux_810lmr_lite.lb]# eraseall /dev/mtd0 Erasing 8 Kibyte @ 2c000 -- 2 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erased 8192 Kibyte @ 0 -- 100% complete. [root@linuxbios cwlinux_810lmr_lite.lb]# dmesg | tail -2 Ignoring DiskOnChip 2000 at 0xFFFEE000 - already configured Error erasing at 0x2c000 [2] (with good DOC in socket) [root@linuxbios cwlinux_810lmr_lite.lb]# sfdisk -l -uS /dev/nftla Disk /dev/nftla: 1019 cylinders, 14 heads, 1 sectors/track Units = sectors of 512 bytes, counting from 0 Device Boot Start End #sectors Id System /dev/nftla1 1 14265 14265 83 Linux /dev/nftla2 0 - 0 0 Empty /dev/nftla3 0 - 0 0 Empty /dev/nftla4 0 - 0 0 Empty [root@linuxbios cwlinux_810lmr_lite.lb]# expr 14265 \* 512 7303680 [root@linuxbios cwlinux_810lmr_lite.lb]# ls -l data/*minix -rw-r--r-- 1 root root 7307264 May 3 13:21 data/rootfs.minix [root@linuxbios cwlinux_810lmr_lite.lb]# cat config/* # partition table of /dev/nftla unit: sectors /dev/nftla1 : start= 1, size= 14265, Id=83 /dev/nftla2 : start= 0, size= 0, Id= 0 /dev/nftla3 : start= 0, size= 0, Id= 0 /dev/nftla4 : start= 0, size= 0, Id= 0 [3] [root@linuxbios cwlinux_810lmr_lite.lb]# ls -l ../cwlinux_810lmr_mb-mii.lb/data/*minix -rw-r--r-- 1 root root 7303168 Sep 6 07:53 ../cwlinux_810lmr_mb-mii.lb/data/rootfs.minix

1 1

Re: kernel image size
by ollie lho 08 Nov '02

08 Nov '02

1 0

Re: VIA EPIA - Trying to get it built
by BIOS Support Personnel 08 Nov '02

08 Nov '02

> > Again, I run make and get "make: *** No rule to make target > > '.../freebios/mainboard.c', needed by 'mainboard.o'. Stop. > that's weird. But there have been several changes lately so we'll have to > do some looking around. Andrew, are you seeing this? I don't see this problem. -Andrew ------------------------- I found that in my Makefile, which was generated without error by /NLBConfig.py, the path for two files is just /../freebios/mainboard.c and /../freebios/irq_tables.c Aren't they supposed to be at /../freebios/src/mainboard/via/epia/mainboard.c and /../freebios/src/mainboard/via/epia/irq_tables.c? Is my config file the cause? Here it is (it's just the latest that was checked in by Ron, just yesterday): -------------------------------- arch i386 mainboardinit cpu/i386/entry16.inc mainboardinit cpu/i386/entry32.inc ldscript cpu/i386/entry16.lds ldscript cpu/i386/entry32.lds mainboardinit cpu/i386/reset16.inc ldscript cpu/i386/reset16.lds mainboardinit superio/via/vt8231/setup_serial.inc mainboardinit pc80/serial.inc mainboardinit arch/i386/lib/console.inc mainboardinit northbridge/via/vt8601/raminit.inc # mainboardinit ram/dump_northbridge.inc # mainboardinit ram/ramtest.inc # mainboardinit mainboard/via/epia/do_ramtest.inc # option RAM_TEST=1 northbridge via/vt8601 southbridge via/vt8231 superio via/vt8231 mainboardinit cpu/p6/earlymtrr.inc option ENABLE_FIXED_AND_VARIABLE_MTRRS=1 option FINAL_MAINBOARD_FIXUP=1 option HAVE_PIRQ_TABLE=1 option SUPERIO_DEVFN=0x88 object mainboard.o object irq_tables.o keyboard pc80 cpu p5 cpu p6 option MAINBOARD_PART_NUMBER=EPIA option MAINBOARD_VENDOR=VIA -------------- Andy

3 2

linux bios kernel for m758lmr+
by James Alton 07 Nov '02

07 Nov '02

Hi, I'm trying to get *any* linux kernel to compile for the m758lmr+ motherboard and disk on chip millenium. I tried 2.4.7, 2.4.17, and 2.4.19, but none of them compiled. I even tried messing with the code and fixing it up, but still am unable to compile. Does anyone know of the best kernel to use for sis630 chipset, and do you have to patch it? (I have been patching the kernel every time I have tried to compile, but am not sure this is even necessary.) -James Alton -jalton(a)olsh.cx

9 19

Re: Geode sc1200
by David Aparicio Campos 07 Nov '02

07 Nov '02

>> we can help you but there's a price :-) >> >> would you be willing to send me a writeup on "How I built for the Geode >> sc1200" if I tell you :-) I'm also looking at the code, and I would have found useful this guide too. It would be ok to pay the price for me! :-) At this moment I still don't have the hardware (a reference board from National) but I have been able to build a LinuxBIOS image, still some questions about what to flash on it. I would prefer to post all my doubts to a single person, the resume them and write the guide once, then post it in the list or whatever. Makes this sense? Best regards David

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot