coreboot April 2006

coreboot@coreboot.org

50 participants
115 discussions

[LinuxBIOS] Spradic linking errors
by Eric Poulsen 28 Apr '06

28 Apr '06

I'm getting these errors sporadically when compiling. I am doing 'make clean,' but it doesn't help. At one point, I changed the config and re-ran buildtarget, then changed the config back and re-built, and it seem to clear it up. Anyone have any idea on what's causing this? 86/16bit/entry16.lds /usr/src/LinuxBIOSv2.ml/src//cpu/x86/32bit/entry32.lds /usr/src/LinuxBIOSv2.ml/src//cpu/x86/16bit/reset16.lds /usr/src/LinuxBIOSv2.ml/src//arch/i386/lib/id.lds /usr/src/LinuxBIOSv2.ml/src//arch/i386/lib/failover.lds ; do echo /\* $file \*/ >> ldscript.ld; cat $file >> ldscript.ld ; done gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o /usr/bin/ld: section .reset [00000000fffffff0 -> 00000000ffffffff] overlaps section .rom [00000000ffffb646 -> 0000000100001b1f] /usr/bin/ld: section .id [00000000ffffffd8 -> 00000000ffffffef] overlaps section .rom [00000000ffffb646 -> 0000000100001b1f] /usr/bin/ld: linuxbios: section .data lma 0xffffb648 overlaps previous sections crt0.o: In function `L1058': crt0.S:(.rom.text+0xef): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1072': crt0.S:(.rom.text+0x2b1): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1080': crt0.S:(.rom.text+0x2f7): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1087': crt0.S:(.rom.text+0x353): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1093': crt0.S:(.rom.text+0x39f): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1099': crt0.S:(.rom.text+0x3eb): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1105': crt0.S:(.rom.text+0x437): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1111': crt0.S:(.rom.text+0x483): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1117': crt0.S:(.rom.text+0x4cf): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1123': crt0.S:(.rom.text+0x51b): relocation truncated to fit: R_386_32 against `.rom.data' crt0.o: In function `L1129': crt0.S:(.rom.text+0x562): additional relocation overflows omitted from the output collect2: ld returned 1 exit status

2 2

Re: [LinuxBIOS] New Target for LinuxBios MB1030 / 3036 Success!!!???
by Richard Smith 28 Apr '06

28 Apr '06

On 4/23/06, Christian Sühs <chris(a)suehsi.de> wrote: > > > > > I've added some debug output to the VGA area that determines which > > device to use as primary. Apply the attached patch and post the > > output. > > > > Thanks, but there is no attachement :( > I will have a look to the svn Sorry. Forgot to attach. Try this. -- Richard A. Smith

7 134

Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D
by Goodrich,Steven 28 Apr '06

28 Apr '06

No... Just trying to figure out what you've got on the system. -- Steve G. Steve Goodrich (Steven.Goodrich(a)amd.com) Advanced Micro Devices, Inc. -----Original Message----- From: Stefan Reinauer [mailto:stepan@coresystems.de] Sent: Thursday, April 27, 2006 4:07 PM To: Goodrich,Steven Cc: LinuxBIOS Subject: Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D * Goodrich,Steven <steven.goodrich(a)amd.com> [060427 23:47]: > Are you loading an SMM handler on this platform? We don't do any SMM stuff (yet). Is there any good reason to do so? Except the very nice Debugger available as SMI code from AMD's website? Stefan -- coresystems GmbH * Brahmsstr. 16 * D-79104 Freiburg i. Br. Tel.: +49 761 7668825 * Fax: +49 761 7664613 Email: info(a)coresystems.de * http://www.coresystems.de/

1 0

Re: [LinuxBIOS] Kernel crash output: Memtest86+ output
by Richard Smith 28 Apr '06

28 Apr '06

> LinuxBIOS + filo > Errors from C0000 to EFEFC > Walltime Cached RsvdMem MemMap Cache ECC Test > 224M 0 LinuxBIOS on off std > > Obviously, memtest86 isn't skipping the cmos -- I managed to pause it just > as it hit C000, and looked at the error result -- AA 55 was in there. It's > reading the cmos, and failing to test it, as it should. That range is not CMOS. CMOS is 128 bytes and you access it via portIO. Memtest86 never hits CMOS. Those are your legacy video bios and other shadow area ranges. Depending on how they are enabled by your setup code they may not be writeable. Doubtfull its a problem though as Linux won't use those area for RAM. -- Richard A. Smith

4 11

Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D
by Goodrich,Steven 28 Apr '06

28 Apr '06

We have an older board (from before I came to be with AMD) which was built with a GXm, CS5530, and NSC 97317 SIO. I can pull preferred register settings from a document if that would help. Our preferred settings for this platform were: BC_XMAP_1 = 0x1300C060 BC_XMAP_2 = 0x09999999 BC_XMAP_3 = 0x99****99 (* = don't care) Are you loading an SMM handler on this platform? -- Steve G. Steve Goodrich (Steven.Goodrich(a)amd.com) Advanced Micro Devices, Inc. -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Richard Smith Sent: Thursday, April 27, 2006 3:00 PM To: Christian Sühs Cc: Stefan Reinauer; LinuxBIOS Subject: Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D On 4/27/06, Christian Sühs <chris(a)suehsi.de> wrote: > > > > > Run memtest as a payload and see where it errors. > > > > Also you need to rip the BC_XMAP_* settings while booted under the factory bios. > > > > Fine ;) How can I get them. Do you have an account here? http://wwwd.amd.com/AMD/developer.nsf/ There are tools there for DOS and linux that can read various things. Its not obvious to me if the XMAP registers are in the list of thingsn they can read. If not then you will have to study the LinuxBIOS source and the gx1 datasheet to figure out how to write a small program that can read them. -- Richard A. Smith -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

3 2

Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D
by Goodrich,Steven 27 Apr '06

27 Apr '06

Sorry, I've not been following this thread. It's a Geode? Could I get some info, like what CPU and what Southbridge? -- Steve G. Steve Goodrich (Steven.Goodrich(a)amd.com) Advanced Micro Devices, Inc. -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Christian Sühs Sent: Thursday, April 27, 2006 1:11 PM To: Peter Stuge Cc: LinuxBIOS Subject: Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D > > You could try enabling caching in the Geode control register. > > Instead of 0x33333333 try 0x77777777 for BC_XMAP_2. > I have set it to 0xFFFFFFFF but I can give it a chance :D > The right solution is clearly to make x86emu use other RAM though. > > > //Peter > -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

3 3

[LinuxBIOS] Loading "other" OS's?
by Goodrich,Steven 27 Apr '06

27 Apr '06

I work on AMD's Geode processors -- in the BIOS group -- and I'd like to know if LinuxBIOS can meet our needs for loading other Operating Systems (Windows CE) in addition to Linux. Can anyone tell me how I'd load a WinCE image using LinuxBIOS as the loader? Thanks! -- Steve G. Steve Goodrich (Steven.Goodrich(a)amd.com <mailto:Steven.Goodrich@amd.com> ) Advanced Micro Devices, Inc. 1351 S. Sunset Street Mail Stop 83-36 Longmont, CO 80501 303-774-5129 (fax: 303-774-5801) http://www.amd.com/embeddedprocessors

4 3

[LinuxBIOS] Is there sched_clock equivalent in LB?
by Eric Poulsen 27 Apr '06

27 Apr '06

I was going to hack LB a bit, and add a timestamp, just like you see in the newer Linux kernels, to look for potential bottlenecks specific to my MLB. The kernel printk uses sched_clock() to get the current time. Is there an equivalent call in LB? I've looked through the code base for files / code that has *clock* or *time* or something similar, but without much luck.

5 5

[LinuxBIOS] What's stored in the CMOS by LB?
by Eric Poulsen 27 Apr '06

27 Apr '06

The LinuxBIOS boot doesn't always work for me 100%. Sometimes I get Exception 6 in LB itself (causing a halt), other times, the Kernel has an Exception 6, or it can't find the hard drive. Here's the weird part: I flip back to the factory BIOS, it says "CMOS checksum invalid, using defaults". I hit DEL, save the settings to CMOS, and power down. I flip back to LB, and all of a sudden, it's working fine for a while. The kernel is a stock Ubuntu kernel with initrd that always works with the stock BIOS + grub loading. 1) Does LB store anything in the CMOS? 2) If yes, is there anything in there that could become corrupted and cause "weird issues" as described above? 3) If no, any other guesses? -- Eric P.S>> I haven't had any issues since I got VGA working, but I've only powered up the machine twice since that flashing.

6 12

[LinuxBIOS] Epia ML 5000 success
by Eric Poulsen 27 Apr '06

27 Apr '06

Last night, I got LinuxBios + VGA working on an Epia ML 5000. If I'm feeling ambitious, I'll figure out how to get a splash logo. I'll write up my efforts as a HOWTO in the near future. I'd like to thank everyone here for their help -- This is one of the most helpful technical mailing lists that I've been on. -- Eric

5 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot April 2006