I made two changes in the Config.lb file first one is ROM_SIZE i made as 2048*1024 and second i specified the location of my payload.
yea I also think i misconfigured the Config.lb file. I modified the ROM_SIZE but forgot to change the ROM_IMAGE_SIZE in the Config.lb file according to it.
The modified version of this file i've attached. and then again tried to rebuild the coreboot but this time after executing the make command i got the error message as:
/usr/bin/ld: _start too low. Please decrease ROM_IMAGE_SIZE collect2: ld returned 1 exit status make: *** [coreboot] Error 1
So i think the problm is with my paylod linux.elf. Its description is as follows
Actually i am going to build qemu without using FILO, for that i took the vmlinuz and initrd image from my system(development machine) whose size is 2.1 MB and 7.8 MB respectively when i used the mkelfImage utilty to generate the elf image using the command:
mkelfImage --append="console=ttyS0" --initrd=/boot/initrd.img-2.6.27-7-generic /boot/vmlinuz-2.6.27-7-generic linux.elf the size of the linux.elf image was 10 MB. So this may be problem also.
So I dont know how to decrease the size of linux.elf, Any help would be greatly appreciated.
Thanks Anurag Vashisth 9739278384
________________________________________ From: email@example.com [firstname.lastname@example.org] On Behalf Of email@example.com [firstname.lastname@example.org] Sent: Thursday, July 09, 2009 2:18 AM To: email@example.com Subject: coreboot Digest, Vol 53, Issue 44
Send coreboot mailing list submissions to firstname.lastname@example.org
To subscribe or unsubscribe via the World Wide Web, visit http://www.coreboot.org/mailman/listinfo/coreboot or, via email, send a message with subject or body 'help' to email@example.com
You can reach the person managing the list at firstname.lastname@example.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of coreboot digest..."
1. Re: excessive whitespace; was: fam10 resource can not allocated. (Peter Stuge) 2. Re: Holding the s2895 in reset powers off the machine (Myles Watson) 3. Re: error in Building coreboot: Corrupt rom -- found no header at 2031584 (Myles Watson) 4. Re: error in Building coreboot: Corrupt rom -- found no header at 2031584 (ron minnich) 5. Re: error in Building coreboot: Corrupt rom -- found no header at 2031584 (ron minnich) 6. Re: error in Building coreboot: Corrupt rom -- found no header at 2031584 (Myles Watson) 7. GPLv2 vs GPLv3 (Joseph Smith) 8. Re: GPLv2 vs GPLv3 (ron minnich) 9. Re: GPLv2 vs GPLv3 (Joseph Smith) 10. Re: GPLv2 vs GPLv3 (Robinson Tryon)
Message: 1 Date: Wed, 8 Jul 2009 14:03:27 +0200 From: Peter Stuge email@example.com To: firstname.lastname@example.org Subject: Re: [coreboot] excessive whitespace; was: fam10 resource can not allocated. Message-ID: email@example.com Content-Type: text/plain; charset=us-ascii
Russell Whitaker wrote:
If the program writing the display does not word-wrap at the edge of the screen then some data just disappears.
Doesn't that depend on the console driver?
Message: 2 Date: Wed, 8 Jul 2009 07:52:09 -0600 From: Myles Watson firstname.lastname@example.org To: Rudolf Marek email@example.com Cc: firstname.lastname@example.org Subject: Re: [coreboot] Holding the s2895 in reset powers off the machine Message-ID: email@example.com Content-Type: text/plain; charset="iso-8859-1"
On Wed, Jul 8, 2009 at 1:13 AM, Rudolf Marek firstname.lastname@example.org wrote:
Please tell what superios are there. The pwrgood is sometimes involved. It looks like a SIO thingie.
On Tue, Jul 7, 2009 at 6:17 PM, Carl-Daniel Hailfinger < email@example.com> wrote:
I have no idea if the reset button directly triggers a reset line or something similar on the processor, but it would be interesting to know:
- Does the power off also happen if you hold reset after the machine
has already been booted? (Do n seconds of reset always trigger a poweroff?)
No. After a few seconds of booting you can hold it in reset as long as you want. Since there is no output (no post codes either), I haven't been able to narrow it down.
What I'm hoping is that it is some setting that can be saved by the device for the next boot. Otherwise I have to figure out a workaround, since I can't access the SuperIO before HT is initialized, and I need to hold the board in reset before HT is initialized.
- Which part of the board reacts to the held reset line and triggers
I don't know.
- Is reset maybe somehow coupled to PWRGOOD and holding down reset is
perceived as electrical problem of the power supply?
Since #1 is no, I don't think so.