Hi All, 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[1]: *** [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 protected] [[email protected]] On Behalf Of [email protected] [[email protected]] Sent: Thursday, July 09, 2009 2:18 AM To: [email protected] Subject: coreboot Digest, Vol 53, Issue 44 Send coreboot mailing list submissions to [email protected] 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 protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of coreboot digest..." Today's Topics: 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 protected]> To: [email protected] Subject: Re: [coreboot] excessive whitespace; was: fam10 resource can not allocated. Message-ID: <[email protected]> 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? //Peter ------------------------------ Message: 2 Date: Wed, 8 Jul 2009 07:52:09 -0600 From: Myles Watson <[email protected]> To: Rudolf Marek <[email protected]> Cc: [email protected] Subject: Re: [coreboot] Holding the s2895 in reset powers off the machine Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" On Wed, Jul 8, 2009 at 1:13 AM, Rudolf Marek <[email protected]> wrote: > Hi, > > Please tell what superios are there. The pwrgood is sometimes involved. It > looks like a SIO thingie. smsc lpc47b397. On Tue, Jul 7, 2009 at 6:17 PM, Carl-Daniel Hailfinger < [email protected]> 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: > 1. 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. > 2. Which part of the board reacts to the held reset line and triggers > the poweroff? > I don't know. > 3. 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. Thanks, Myles -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20090708/3fc68c63/attachment-0001.htm> ------------------------------ Message: 3 Date: Wed, 8 Jul 2009 08:03:03 -0600 From: "Myles Watson" <[email protected]> To: "'Anurag_Vashisth'" <[email protected]>, <[email protected]> Subject: Re: [coreboot] error in Building coreboot: Corrupt rom -- found no header at 2031584 Message-ID: <e685b03a296b44b59ec6d446e0149...@chimp> Content-Type: text/plain; charset="us-ascii" > I used the following command to build the coreboot payload: > mkelfImage --append="console=ttyS0" --initrd=/boot/initrd.img-2.6.27-7- > generic /boot/vmlinuz-2.6.27-7-generic linux.elf > > and when i executed the 'make' command from the targets/emulation/qemu- > x86/qemu-x86 directory i got the error message as: > Corrupt rom -- found no header at 2031584 How big is your payload. It looks like it is too big to fit in the space that's left. Thanks, Myles ------------------------------ Message: 4 Date: Wed, 8 Jul 2009 08:02:35 -0700 From: ron minnich <[email protected]> To: Anurag_Vashisth <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [coreboot] error in Building coreboot: Corrupt rom -- found no header at 2031584 Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 2097152 any reason for that size? I have had this problem but I think only when I somehow misconfigured the ROM sizes. What parts of coreboot have you changed? ron ------------------------------ Message: 5 Date: Wed, 8 Jul 2009 08:26:35 -0700 From: ron minnich <[email protected]> To: Anurag_Vashisth <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [coreboot] error in Building coreboot: Corrupt rom -- found no header at 2031584 Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 8, 2009 at 8:02 AM, ron minnich<[email protected]> wrote: > 2097152 > > any reason for that size? it's early morning and my brain is turned off, sorry, a nice person reminded me that was 2M. ron ------------------------------ Message: 6 Date: Wed, 8 Jul 2009 10:00:53 -0600 From: Myles Watson <[email protected]> To: Anurag_Vashisth <[email protected]>, [email protected] Subject: Re: [coreboot] error in Building coreboot: Corrupt rom -- found no header at 2031584 Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" On Wed, Jul 8, 2009 at 8:03 AM, Myles Watson <[email protected]> wrote: > > > I used the following command to build the coreboot payload: > > mkelfImage --append="console=ttyS0" --initrd=/boot/initrd.img-2.6.27-7- > > generic /boot/vmlinuz-2.6.27-7-generic linux.elf > > > > and when i executed the 'make' command from the targets/emulation/qemu- > > x86/qemu-x86 directory i got the error message as: > > Corrupt rom -- found no header at 2031584 > How big is your payload. It looks like it is too big to fit in the space > that's left. > make[1]: Entering directory `/home/anurag/Desktop/coreboot-v2-4304/util/cbfstool' If you check out the latest coreboot version the error message is more understandable. I'd recommend always trying svn head if you can't get an older version to work. Thanks, Myles -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20090708/5b347d0a/attachment-0001.htm> ------------------------------ Message: 7 Date: Wed, 08 Jul 2009 14:46:42 -0400 From: Joseph Smith <[email protected]> To: coreboot <[email protected]> Subject: [coreboot] GPLv2 vs GPLv3 Message-ID: <[email protected]> Content-Type: text/plain; charset="UTF-8" Hello, This has probably been discussed before but what are the pros and cons of GPLv2 and GPLv3? -- Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org ------------------------------ Message: 8 Date: Wed, 8 Jul 2009 11:54:58 -0700 From: ron minnich <[email protected]> To: Joseph Smith <[email protected]> Cc: coreboot <[email protected]> Subject: Re: [coreboot] GPLv2 vs GPLv3 Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 8, 2009 at 11:46 AM, Joseph Smith<[email protected]> wrote: > > Hello, > This has probably been discussed before but what are the pros and cons of > GPLv2 and GPLv3? let's not do that here. Just google the flame wars. :-) ron ------------------------------ Message: 9 Date: Wed, 08 Jul 2009 15:47:36 -0400 From: Joseph Smith <[email protected]> To: ron minnich <[email protected]> Cc: coreboot <[email protected]> Subject: Re: [coreboot] GPLv2 vs GPLv3 Message-ID: <[email protected]> Content-Type: text/plain; charset="UTF-8" On Wed, 8 Jul 2009 11:54:58 -0700, ron minnich <[email protected]> wrote: > On Wed, Jul 8, 2009 at 11:46 AM, Joseph Smith<[email protected]> wrote: >> >> Hello, >> This has probably been discussed before but what are the pros and cons > of >> GPLv2 and GPLv3? > > > let's not do that here. Just google the flame wars. :-) > Sorry I didn't know it was a sensitive subject. I'm going to release some code soon, and I was just wondering which one to use. -- Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org ------------------------------ Message: 10 Date: Wed, 8 Jul 2009 16:48:19 -0400 From: Robinson Tryon <[email protected]> To: Co-Reboot <[email protected]> Subject: Re: [coreboot] GPLv2 vs GPLv3 Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 8, 2009 at 3:47 PM, Joseph Smith<[email protected]> wrote: > > > > On Wed, 8 Jul 2009 11:54:58 -0700, ron minnich <[email protected]> wrote: >> On Wed, Jul 8, 2009 at 11:46 AM, Joseph Smith<[email protected]> wrote: >>> >>> Hello, >>> This has probably been discussed before but what are the pros and cons >> of >>> GPLv2 and GPLv3? >> >> >> let's not do that here. Just google the flame wars. ?:-) >> > Sorry I didn't know it was a sensitive subject. I'm going to release some > code soon, and I was just wondering which one to use. If you have the time, I'd suggest that the best thing to do is to carefully read the two, compare them, and then choose one yourself: http://www.gnu.org/licenses/gpl-2.0.html http://www.gnu.org/licenses/gpl-3.0.html If you'd like to hear from the architect of the licenses, RMS wrote a letter encouraging projects to upgrade from v2 -> v3. You might find it relevant: http://www.gnu.org/licenses/rms-why-gplv3.html If you have special licensing needs or specific license questions, remember that you can always drop a line to the friendly SFLC folks. Their lawyers are very helpful at answering legal inquiries about Free Software licensing and other related questions: http://www.softwarefreedom.org/ Good luck! --Robinson ------------------------------ _______________________________________________ coreboot mailing list [email protected] http://www.coreboot.org/mailman/listinfo/coreboot End of coreboot Digest, Vol 53, Issue 44 **************************************** DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
Config.lb
Description: Config.lb
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
