coreboot November 2002

coreboot@coreboot.org

65 participants
108 discussions

Re: RLX 800i: registered DRAM doesn't work
by Ronald G. Minnich 26 Nov '02

26 Nov '02

On Mon, 25 Nov 2002, Aditya wrote: > Any chance that Linuxbios might support the older RLX Transmeta-based blades? We have not seen enough transmeta platforms to make the effort worthwhile. Back when it did look worthwhile we were unable to get docs we needed. Transmeta did release the docs last summer (good!), but they do make it kind of hard to get a development system (try it, the process is lengthy and involves lots of click-wrap forms and IDs) so I have not gotten around to getting one and doing the work. ron

1 0

elf booting
by Andrew Kohlsmith 26 Nov '02

26 Nov '02

I seem to have gotten myself stuck. I can load an elf image out of ROM but can't jump to it. I _can't_ load an elf image off of the drive at all. The output of a boot using BOOT_ROM=1 and having the natsemi.elf at 0xc000 is attached. If I try BOOT_IDE=1 the only difference is that it doesn't find an elf candidate (it never tries to access the HDD). The end goal is to load the kernel off of CompactFlash on IDE0 master. I (think I) know how to place the kernel on the HDD and adjust the IDE_OFFSET in the config but I'm not even getting that far. >From the attached serial output you can see that it finds the natsemi.elf and that it is declared valid. If I examine code at 0x400000 it seems to be correct, meaning that it did copy the code over there. The processor never gets up there though. From tracing through the image it seems that the adjustment for Linuxbios' image in high memory is all messed up. After editing loglevel.h to allow "spew" level printks, the following is visible (I could see it throught the bochs debugger, but this just verifies that I'm not totally crazy. :-) Loaded segments verified segments closed down stream Jumping to boot code at 0x400000 entry = 0x00400000 lb_start = 0x00004000 lb_size = 0x0004e2d0 adjust = 0x3fbadd30 buffer = 0x3fb63a60 elf_boot_notes = 0x0000bc40 adjusted_boot_notes = 0x3fbb9970 now adjust and buffer are both waaaaaaaaaaaaaay beyond normal memory space... Is this normal or did I just fail to initialize something correctly? the objdump output for the natsemi.elf is also attached. From what I can tell it's nothing unusual. Regards, Andrew

4 5

for the archvies/faq: how to get BOOT_IDE to work
by Andrew Kohlsmith 26 Nov '02

26 Nov '02

This may be obvious to the software authors, but to mere peons like myself this will save aggravation. :-) In order to get BOOT_IDE to work, you must (obviously) "option BOOT_IDE=1" in the little-c config file. However, from what I can gather, there can only be one stream configured. Streams are places to get elf images from: rom, tftp, ide, floppy and so on. So "option BOOT_ROM=0" must be present, and further, "option USE_GENERIC_ROM=0" must also be present, or the rom stream is enabled, effectively removing the IDE stream. I think. Perhaps Eric can elaborate a little bit, but with what I've written here I am able to have the IDE system initialized and used to get the ELF image to run. No actual kernel loading yet, but at least I am on the right track now. :-) Regards, Andrew

2 1

rom_stream: The use of stream tags?
by Andrew Kohlsmith 26 Nov '02

26 Nov '02

Can someone explain why the rom stream init function looks for "$TAG$" in memory? It appears nowhere in a "regular" romimage (i.e. one with only an elfboot and the linuxbios image), other in the code that looks for the tag. Regards, Andrew

2 1

Does it some differences between K7SEM V1.0c & V3.0?
by bendany 25 Nov '02

25 Nov '02

I have bought a mainboard K7SEM, and The mainboard also have a CPU in it, duron 1000+, and I follow the m810 HOWTO to burn a DOC chip, and reset, nothing happen. and I also download the LinuxBIOS SDK from the cwlinux.com , burn the k7sem into the DOC, i seem the LinuxBIOS has write into the DOC, i can mount the fs in the DOC, and when I turn reset key, nothing happen too finally, I download the m810-etherboot.rom from cwlinux.com ,using a external chip burnner ,burn it into the original BIOS chip, and it works, I can take some boot message from the serial console, but still does not work, the log like this: <abort> Boot from (N)etwork or from (L)ocal? N Probing...[SIS900]Found SIS900 ROM address 0x0000 Found SIS 85C503/5513 PCI to ISA bridge ROM address 0x0000 sis900_probe: MAC addr 00:07:95:2B:50:CE at ioaddr 0X2000 sis900_probe: Vendor:0X1039 Device:0X0900 sis900_probe: No MII transceivers found! No adapter found <sleep> How can I make my mainboard work? Need help!

1 0

Does it some differences between K7SEM V1.0c & V3.0?
by bendany 25 Nov '02

25 Nov '02

2 1

ANNOUNCE: LinuxBIOS booting Windows 2000 (free software BIOS)
by Adam Sulmicki 25 Nov '02

25 Nov '02

We're happy to announce that we've successfully booted Windows 2000 without a legacy proprietary BIOS. We accomplished this by developing software that combined elements from two very successful projects: LinuxBIOS and BOCHS. The Etherboot project also helped in various ways. As a result, we now have a completely free software replacement for the BIOS that supports (without modification) either LILO or GRUB as bootloaders, and Linux, OpenBSD, and Windows 2000 as operating systems (NOTE: We're still working on supporting FreeBSD and Windows XP. We expect that improving ATA support will permit Win98 and WinXP to boot, and finishing PIRQ support will permit FreeBSD to boot.) Motherboard support is limited at this time, but we hope to expand that along with LinuxBIOS. More details can be found at: http://www.missl.cs.umd.edu/Projects/sebos/main.shtml and http://www.missl.cs.umd.edu/Projects/sebos/phase2.shtml The GPL'd source for our contribution, ADLO, will be included in the LinuxBIOS CVS tree shortly. ADLO is the "glue" that combines the initialization code from LinuxBIOS with the BOCHS BIOS code-- creating a true free software BIOS. Ironically, twenty years ago this month Compaq introduced their Compaq portable computer with the first BIOS outside of IBM, see http://www.old-computers.com/museum/computer.asp?st=1&c=547. Adam Sulmicki Adam Agnew William Arbaugh This work has been funded by a grant from DARPA under the CHATS program. -- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit registers

3 2

Re: ADLO committed
by Bari Ari 25 Nov '02

25 Nov '02

Adam Sulmicki wrote: >>LinuxBIOS + BOCHS BIOS + Video BIOS =? >> > >Doesn't it seem like much of problem: > 64+64+48 = 176KB > 176 < 512KB > >and you probably could gzip it for even more space saving. >(though I'm not sure of exact sizes of LinuxBIOS as bulk of my >time was spent on BOCHS bios part.) > Linux Kernel 448KB + BOCHS 64 KB + Video BIOS 48 KB = 560KB ouch! Bari

2 1

Re: occurs segmentation fault, when I make a file system(ext3 or reiserfs)
by Munjun Kang 25 Nov '02

25 Nov '02

Dear Eric. Thanks for your reply. Follows are "ksymoops" decoding message. Regards, malas ----------------- ksymoops decoding message ----------------- c022ade5 *pde = 00017063 Oops: 0002 CPU: 0 EIP: 0010:[<c022ade5>] Not tainted EFLAGS: 00010246 eax: 00000000 ebx: c58bc000 ecx: 00001000 edx: 00000000 esi: 0806acb8 edi: c58bc000 ebp: c109f2c8 esp: c1089f34 ds: 0018 es: 0018 ss: 0018 Process mkreiserfs (pid: 127, stackpage=c1089000) Stack: 00000000 00001000 00001000 c124f054 00000000 00001000 00000000 00000000 011de000 00000000 c109f220 00000000 00000001 0806acb8 c109f28c c109f220 c13bbaa0 c01290df c13bbaa0 0806acb8 00001000 c13bbac0 0806acb8 c13bbaa0 Call Trace: [<c01290df>] [<c0133c65>] [<c0108d43>] Code: f3 aa 58 59 e9 9f df ef ff b8 f2 ff ff ff 30 d2 e9 b7 14 f0 >>EIP; c022ade5 <rwsem_down_failed_common+1175/2d00> <===== Trace; c01290df <generic_file_write+6f/b0> Trace; c0133c65 <sys_write+85/100> Trace; c0108d43 <system_call+33/40> Code; c022ade5 <rwsem_down_failed_common+1175/2d00> 00000000 <_EIP>: Code; c022ade5 <rwsem_down_failed_common+1175/2d00> <===== 0: f3 aa repz stos %al,%es:(%edi) <===== Code; c022ade7 <rwsem_down_failed_common+1177/2d00> 2: 58 pop %eax Code; c022ade8 <rwsem_down_failed_common+1178/2d00> 3: 59 pop %ecx Code; c022ade9 <rwsem_down_failed_common+1179/2d00> 4: e9 9f df ef ff jmp ffefdfa8 <_EIP+0xffefdfa8> c0128d8d <do_generic_file_write+3fd /6e0> Code; c022adee <rwsem_down_failed_common+117e/2d00> 9: b8 f2 ff ff ff mov $0xfffffff2,%eax Code; c022adf3 <rwsem_down_failed_common+1183/2d00> e: 30 d2 xor %dl,%dl Code; c022adf5 <rwsem_down_failed_common+1185/2d00> 10: e9 b7 14 f0 00 jmp f014cc <_EIP+0xf014cc> c112c2b1 <END_OF_CODE+e4ce6d/???? 1 warning issued. Results may not be reliable. ----- Original Message ----- From: "Eric W. Biederman" <ebiederman(a)lnxi.com> To: "Munjun Kang" <malas(a)pinetron.com> Cc: <linuxbios(a)clustermatic.org> Sent: Saturday, November 23, 2002 4:02 PM Subject: Re: occurs segmentation fault, when I make a file system(ext3 or reiserfs) > "Munjun Kang" <malas(a)pinetron.com> writes: > > > Dear linuxbios. > > > > Hello. > > > > I've worked for development of Embedded linux project in my corp. > > Following is decription of my projcet. > > CPU : VIA C3 800Mhz (EBGA) > > Reference Board : VT6015 > > Northbridge : VT8606 (include S3 twister video core) > > Southbridge : VT8231 (include VIA rhine II LAN core) > > Bootbios : Linuxbios > > OS : linux 2.4.19 ( ramdisk include glibc 2.3.1, busybox 0.60.5 and tinylogin > > 1.2 ) > > > > > > Now, It works well except hard disk. > > I try to boot the kernel in two way. > > First, it loads compressed kernel and ramdisk image via network using tftp > > protocol. > > > > Second, it loads elfImage, generated by 'mkelfImage' via network. > > All of them work great. (It means that I can see the prompt '\ '.) > > > > But, when I try to make a file system the harddisk, 'segmentation fault' occurs. > > > > mke2fs and mkreiserfs have same problem. > > > > For find out the cause, I try to make a file system in various method. > > > > 1. Buildin Bios + Redhat 8.0 installed harddisk + test harddisk > > 2. Linuxbios + Redhat 8.0 installed harddisk + test harddisk > > 3. Linuxbios + Kernel(newly compiled), own ramdisk + test harddisk > > > > After boot, I try to make a file system on test harddisk. > > > > In case 1, It works well. Of course, it must be. > > In case 2 and 3, I meet the segmentation fault. > > So, I think that this problem caused in Linuxbios. > > > > Maybe, this problem caused by harddisk initialization in linuxbios. > > But, there are no harddisk initialization code in linuxbios. > > > > Cound you help me? > > > > Thanks for reading. > > Regards, > > malas > > > > PS. In addition, memtest86 v3.0 works well without error. > > > My hunch is that it is a DMA problem, or a similar hardware timing > problem. But you missed the most important part of the kernel crash. > The symbolic output of ksymoops. > > Without knowing where the code crashed it is hard to guess where the > code crashed in the kernel, and thus have a good idea what the real > problem is. > > Eric > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

Bochs and LinuxBIOS and kexec functions
by Gregg C Levine 24 Nov '02

24 Nov '02

Hello from Gregg C Levine Just for the record, has anyone gotten the 1.4.1 version of Bochs to boot the 2.5.48 version enabled of Linux, to boot inside it? And then to launch a kexec function from it? My normal Linux box is on down time, as I track down spare parts for it, so I am resorting to this rather unconventional method. ------------------- Gregg C Levine hansolofalcon(a)worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )

1 0

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 2002