coreboot

coreboot@coreboot.org

39717 discussions

Re: [LinuxBIOS] ADLO with EPIA-M LX2
by Richard Smith 09 Nov '05

09 Nov '05

I'm sticking this back on the list so others can suggest things as well. On 11/9/05, Anton Borisov <a.borisov(a)tesv.tmb.ru> wrote: > On Tue, 8 Nov 2005 23:56:53 -0600 > Richard Smith <smithbone(a)gmail.com> wrote: > > > > > See if you can load any payload at all or if its just the ADLO payload > > > > thats causing you trouble. Try memtest without the video bios so you > > > > don't have to change any settings. > > > > > > You're quite right - ADLO payload causing this problem. FILO just works perfectly. I'm ready to blame the size of my ADLO payload ;-) - more then 120 kb. But I wasn't able to start ADLO without VIDEO as well. > > > > > > > So ADLO with no video bios won't load either? Do you still get an elf > > load error? > > I probed 2 versions of ADLO: with integrated VIDEO ROM and without it. Sizes accordingly are 58Kb and 124Kb. Tracing with minicom revealed the same effect - > == > Found ELF candiate at offset 0 > Cannot Load ELF Image > == > Maybe I've run into improper understanding of XIP_ROM_SIZE and ROM_SIZE params inside Config.lb, but I doubt this ;-) I don't think your problem is related to size. The elf image is found but failed to load properly. I believe the size is embedded in the elf segment. If your sizes were all wrong I would expect that it either wouldn't boot or it would not find the payload. Are you using XIP? If so you might try turning it off. You will probally have to go look in the elf load code and see what causes that message I've not looked at the elf load code so I don't have many suggestions. Is you adlo.elf really a valid elf image? What do you get for a 'readelf -a adlo.elf' -- Richard A. Smith

1 0

[LinuxBIOS] ADLO with EPIA-M LX2
by Anton Borisov 09 Nov '05

09 Nov '05

Hi. I have compiled ADLO from LX1 (freebios--devel--1.0--base-0.tar.bz2). Pure BOCHS BIOS ~58k. Payload with VGABIOS - 124k. My Config.lb is below: = target epia-m mainboard via/epia-m option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 option FALLBACK_SIZE=0x30000 option _RAMBASE=0x00004000 romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x30000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" payload /home/anthony/src/payloads/adlo.elf end buildrom ./linuxbios.rom ROM_SIZE "fallback" = Some comments regarding FALLBACK_SIZE. This is done intentionally to include VIA's VGABIOS into fallback portion. linuxbios.rom being composed this way is written into flash chip. Unfortunately I wasn't able to load ADLO payload (see messages below). = Moving GDT to 0x500...ok Wrote linuxbios table at: 00000530 - 00000b28 checksum 97d3 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 33:stream_init() - rom_stream: 0xfffd0000 - 0xfffeffff Found ELF candiate at offset 0 Cannot Load ELF Image = I assume this is a problem with improper configuring ROM_IMAGE_SIZE, ROM_SECTION_OFFSET in my example. I did increase it to 0x20000 value. And I've got this error while compiling with ROMCC: = ./romcc -mcpu=c3 -O -I/home/lx/src/LinuxBIOSv2-2080/src -I. -I/home/lx/src/LinuxBIOSv2-earlymtrr.c:21.45: Integer constant to large = Where I've done wrong? Does anybody experienced with ADLO applying to LX2 recently? Thanks. -- Sincerely, Anton Borisov

2 1

Re: [LinuxBIOS] dual core disable?
by Lu, Yinghai 08 Nov '05

08 Nov '05

Northbridge.c cpu_bus_scan need to be modified too, you need to assume the CONFIG_LOGICAL_CPU==1 there.. YH -----Original Message----- From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Lu, Yinghai Sent: Monday, November 07, 2005 3:55 PM To: Greg Johnson Cc: linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] dual core disable? OK, We may need to set the nbcfg 54 bit even disable the dual core. Please several lines 1. src/cpu/dualcore/dualcore.c //If(read_option(CMOS_VSTART_dual_core..... 2. in you cache_as_ram_auto.c //#if CONFIG_LOGICAL_CPUS == 1 Set_apicid_cpuid_lo(); //#endif YH -----Original Message----- From: Greg Johnson [mailto:gjohnson@lanl.gov] Sent: Monday, November 07, 2005 3:37 PM To: Lu, Yinghai Cc: Ronald G Minnich; Greg Johnson; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] dual core disable? On Mon, Nov 07, 2005 at 03:00:09PM -0800, Lu, Yinghai wrote: > ? > > In Normal BIOS, is there option to disable dual core? > No. I'm pretty sure that I'm really getting two cores on one socket. Memory bandwidth is affected when running on both cores. In any case, Linux K8 NUMA is confused: p5:~# numactl --show policy: default preferred node: current cpubind: 0 membind: 0 1 Greg -- LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

[LinuxBIOS] EPIA-M VGA
by Jun OKAJIMA 08 Nov '05

08 Nov '05

I also have another problem: VGA does not work *USUALLY*. I mean, I have seen several times that VGA works, but in most cases, does not. And, I can not understand what is the difference. I did some experiment, like turning off power, not pushing reset button, or once you boot it with normal bios, and then switch to LX, or.... But, I have not found any rule so far. Why it sometimes works? Umm.. --- Okajima, Jun. Tokyo, Japan.

4 6

Re: [LinuxBIOS] dual core disable?
by Lu, Yinghai 08 Nov '05

08 Nov '05

That bit is cleared default, and if you don't want to dual core, you don't need to set it.... YH -----Original Message----- From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Greg Johnson Sent: Monday, November 07, 2005 4:03 PM To: Lu, Yinghai Cc: Greg Johnson; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] dual core disable? BTW, How come you don't use the CPU1 Enable (Cpu1En) bit to disable the second core? Greg On Mon, Nov 07, 2005 at 03:55:01PM -0800, Lu, Yinghai wrote: > OK, > > We may need to set the nbcfg 54 bit even disable the dual core. > > Please several lines > 1. src/cpu/dualcore/dualcore.c > //If(read_option(CMOS_VSTART_dual_core..... > 2. in you cache_as_ram_auto.c > //#if CONFIG_LOGICAL_CPUS == 1 > Set_apicid_cpuid_lo(); > //#endif > > YH > > > -----Original Message----- > From: Greg Johnson [mailto:gjohnson@lanl.gov] > Sent: Monday, November 07, 2005 3:37 PM > To: Lu, Yinghai > Cc: Ronald G Minnich; Greg Johnson; linuxbios(a)openbios.org > Subject: Re: [LinuxBIOS] dual core disable? > > On Mon, Nov 07, 2005 at 03:00:09PM -0800, Lu, Yinghai wrote: > > ? > > > > In Normal BIOS, is there option to disable dual core? > > > > No. I'm pretty sure that I'm really getting two cores on one socket. > Memory bandwidth is affected when running on both cores. In any case, > Linux K8 NUMA is confused: > > p5:~# numactl --show > policy: default > preferred node: current > cpubind: 0 > membind: 0 1 > > Greg > -- LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

1 0

Re: [LinuxBIOS] dual core disable?
by Lu, Yinghai 08 Nov '05

08 Nov '05

OK, We may need to set the nbcfg 54 bit even disable the dual core. Please several lines 1. src/cpu/dualcore/dualcore.c //If(read_option(CMOS_VSTART_dual_core..... 2. in you cache_as_ram_auto.c //#if CONFIG_LOGICAL_CPUS == 1 Set_apicid_cpuid_lo(); //#endif YH -----Original Message----- From: Greg Johnson [mailto:gjohnson@lanl.gov] Sent: Monday, November 07, 2005 3:37 PM To: Lu, Yinghai Cc: Ronald G Minnich; Greg Johnson; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] dual core disable? On Mon, Nov 07, 2005 at 03:00:09PM -0800, Lu, Yinghai wrote: > ? > > In Normal BIOS, is there option to disable dual core? > No. I'm pretty sure that I'm really getting two cores on one socket. Memory bandwidth is affected when running on both cores. In any case, Linux K8 NUMA is confused: p5:~# numactl --show policy: default preferred node: current cpubind: 0 membind: 0 1 Greg

2 1

Re: [LinuxBIOS] dual core disable?
by Lu, Yinghai 08 Nov '05

08 Nov '05

That's OK, the kernel problem.... It assumes all nbcfg 54 bit is set.....with out check it. So it could treat Node1/core0 as Node0/Core1.... YH -----Original Message----- From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Greg Johnson Sent: Monday, November 07, 2005 12:22 PM To: linuxbios(a)openbios.org Subject: [LinuxBIOS] dual core disable? Disabling dual core on our s2891 boards with Opteron 270's doesn't seem to work properly. When I boot with dual core disabled, I am getting two cores on one socket enabled and none on the other socket. Here's /proc/cpuinfo with dual core disabled: p5:~# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : unknown stepping : 2 cpu MHz : 2010.318 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 4029.78 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : unknown stepping : 2 cpu MHz : 2010.318 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 4020.90 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp It also performs like it's using both cores on one socket. Any thoughts? Thanks, Greg -- LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

Re: [LinuxBIOS] dual core disable?
by Lu, Yinghai 08 Nov '05

08 Nov '05

? In Normal BIOS, is there option to disable dual core? YH -----Original Message----- From: Ronald G Minnich [mailto:rminnich@lanl.gov] Sent: Monday, November 07, 2005 3:40 PM To: Lu, Yinghai Cc: Greg Johnson; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] dual core disable? Lu, Yinghai wrote: > That's OK, the kernel problem.... how is that ok? > > It assumes all nbcfg 54 bit is set.....with out check it. so how do we fix it? ron

2 1

[LinuxBIOS] S2882 - Fallback Only?
by Matthew Simmons 08 Nov '05

08 Nov '05

First off thanks for your help with the APIC problems on my system. Now I am trying to straighten out the boot sequence. I have noticed that I am booting off the fallback image. Both images are build using the payload and the same configuration. However, I would like to use Filo with USB disk support, and that increased Filo's size by 50% from 24K to 34K. This makes filo large to fit inside of the 131K room for the fallback rom image. Is there any help you guys could give me as to why I am not booting off the primary image? Thanks, Matt

2 1

Re: [LinuxBIOS] S2882 - Fallback Only?
by Lu, Yinghai 07 Nov '05

07 Nov '05

Don't need. You can put the payload as follow FULL_FILO_WITH_USB+NORMAL_IMAGE+FALLBACK_IMAGE Then you make filo to be very simple one with command line to boot the FULL_FILO_WITH_USB in FLASH. Or you can use tiny kernel as payload for normal back, then fallback can jump that kernel. Please check README.filo_in_etherboot for more command lines about mem@0xfffe0000 you may need to subtract the size for VGA Option rom on flash if you are using it. YH ________________________________ From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Matthew Simmons Sent: Monday, November 07, 2005 12:53 PM To: linuxbios(a)openbios.org Subject: [LinuxBIOS] S2882 - Fallback Only? First off thanks for your help with the APIC problems on my system. Now I am trying to straighten out the boot sequence. I have noticed that I am booting off the fallback image. Both images are build using the payload and the same configuration. However, I would like to use Filo with USB disk support, and that increased Filo's size by 50% from 24K to 34K. This makes filo large to fit inside of the 131K room for the fallback rom image. Is there any help you guys could give me as to why I am not booting off the primary image? Thanks, Matt

1 0

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