coreboot April 2004

coreboot@coreboot.org

47 participants
130 discussions

EPIA-M build problem
by Dave Ashley 19 Apr '04

19 Apr '04

I didn't get far: 1) CVS checkout latest 2) Take /freebios/src/mainboard/via/epia-m/example.config, A) comment out #payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi towards bottom B) Note: There are 2 conflicting target lines, and 2 conflicting payload lines. 3) Run python config script: python /ram/freebios/util/config/NLBConfig.py example.config /ram/freebios/ (Worked ok, no errors) 4) Go into /ram/freebios/obj and do "make" 5) Fails with this: make: *** No rule to make target `/ram/freebios/src/mainboard/via/epia-m/earlysetup.inc', needed by `crt0.s'. Stop. Could it be a missing cvs commit? -Dave

2 2

etherboot-5.2.4 linuxbios error!
by 王金健 19 Apr '04

19 Apr '04

Dear sir: I want to use etherboot-5.2.4 under linuxbios, but when I comment -DPCBIOS and uncomment -DLINUX line in arch/i386/Config, I can not compile the source rightly!! the message as follow: ld -N -Ttext 0x20000 -T arch/i386/core/etherboot.lds -o bin/undi.tmp bin/start32.o bin/pcbios.o bin/memsizes.o bin/basemem.o bin/linuxbios.o bin/config.o bin/undi.o bin/bootlib.a bin/undi.o(.text+0x8b): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0x90): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x96): In function `allocate_base_mem_data': : undefined reference to `allot_base_memory' bin/undi.o(.text+0xe9): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0xee): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x11d): In function `free_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0x122): In function `free_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x129): In function `free_base_mem_data': : undefined reference to `forget_base_memory' bin/undi.o(.text+0x238): In function `shoot_targets': : undefined reference to `forget_base_memory' bin/undi.o(.text+0x376): In function `hunt_pixie': : undefined reference to `get_free_base_memory' bin/undi.o(.text+0x642): In function `undi_call_loader': : undefined reference to `__undi_call' bin/undi.o(.text+0x6c0): In function `undi_call_silent': : undefined reference to `__undi_call' bin/undi.o(.text+0x76e): In function `undi_loader': : undefined reference to `allot_base_memory' bin/undi.o(.text+0x7ba): In function `undi_loader': : undefined reference to `allot_base_memory' bin/undi.o(.text+0xdde): In function `undi_full_shutdown': : undefined reference to `forget_base_memory' bin/undi.o(.text+0xe12): In function `undi_full_shutdown': : undefined reference to `forget_base_memory' bin/bootlib.a(pic8259.o)(.text+0x251): In function `install_trivial_irq_handler': : undefined reference to `fake_irq' bin/bootlib.a(pic8259.o)(.text+0x35e): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x367): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_end' bin/bootlib.a(pic8259.o)(.text+0x36c): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x392): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x397): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_end' bin/bootlib.a(pic8259.o)(.text+0x3b2): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler' bin/bootlib.a(pic8259.o)(.text+0x3bd): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_trigger_count' bin/bootlib.a(pic8259.o)(.text+0x3c8): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_chain_to' bin/bootlib.a(pic8259.o)(.text+0x3d6): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_chain' bin/bootlib.a(pic8259.o)(.data+0x0): undefined reference to `_trivial_irq_handler' bin/bootlib.a(pic8259.o)(.data+0x4): undefined reference to `_trivial_irq_trigger_count' bin/bootlib.a(pic8259.o)(.data+0x8): undefined reference to `_trivial_irq_chain_to' bin/bootlib.a(pic8259.o)(.data+0xc): undefined reference to `_trivial_irq_chain' make: *** [bin/undi.tmp] Error 1 Can somebody help me! Thank you! wjjsun e-mail:wjjsun@eyou.com

1 0

FILO features request
by YhLu 18 Apr '04

18 Apr '04

Eric, Are you adding features to filo? I hope it can 1. understand grub.conf in HD --- and append console=tty0 console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically 3. editor to boot command line 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem@0xfff80000 mem@0xfff90000 mem@0xfffa0000 mem@0xfffb0000 .... Regards YH

5 6

flash_rom Problem
by Thomas Spear 16 Apr '04

16 Apr '04

This is what happens when I try to build flash_rom: root@(none):/home/freebios2/util/flash_and_burn# make gcc -O2 -g -Wall -Werror -c -o flash_rom.o flash_rom.c gcc -O2 -g -Wall -Werror -c -o flash_enable.o flash_enable.c flash_enable.c:3: pci/pci.h: No such file or directory make: *** [flash_enable.o] Error 1 Someone please tell what I've done wrong. Where does "pci/pci.h" come from? The romimage seems to build ok (I don't really know since I can't flash the rom and try it). Thanks. _________________________________________________________________ >From must-see cities to the best beaches, plan a getaway with the Spring Travel Guide! http://special.msn.com/local/springtravel.armx

4 3

epia-m IRQ routing
by ron minnich 16 Apr '04

16 Apr '04

kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron

2 2

答复: 答复: Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#]
by YhLu 16 Apr '04

16 Apr '04

The arima's PCI-X ioapic is poorly connected. -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月16日 14:42 收件人: YhLu 抄送: Eric Biederman; LinuxBIOS 主题: Re: 答复: Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#] On Fri, 2004-04-16 at 11:21, YhLu wrote: > That's decided by HW. > Do you mean even the device is behind the PCIX bridge, it's IRQ is not routed by the APIC on the bridge ? Ollie > YH > > -----邮件原件----- > 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] > 发送时间: 2004年4月16日 10:07 > 收件人: Eric Biederman; LinuxBIOS > 主题: Broadcom NIC, MPTable and APIC ID for HDAMA > > Eric, > > The broadcom nic on hdama is connected behind the 8131. > So the IRQ should be routed by the APIC on 8131, right ? > But in the current mptable.c it is > > /* PCI Ints: Type Polarity > Trigger > Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ > /* On board nics */ > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, (0x03<<2)|0, 0x02, 0x13); > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, > (0x04<<2)|0, 0x02, 0x13); > > The IRQ is routed by APIC #2 which is in 8111. Is it correct ? > Why is it still working ? > > Ollie > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

答复: Broadcom NIC, MPTable and APIC ID for HDAMA
by YhLu 16 Apr '04

16 Apr '04

That's decided by HW. YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月16日 10:07 收件人: Eric Biederman; LinuxBIOS 主题: Broadcom NIC, MPTable and APIC ID for HDAMA Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

答复: 答复: epia-m IRQ routing
by YhLu 16 Apr '04

16 Apr '04

2.4.22 is the most stabe one. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月16日 13:56 收件人: YhLu 抄送: linuxbios(a)clustermatic.org 主题: Re: 答复: epia-m IRQ routing On Fri, 16 Apr 2004, YhLu wrote: > Why just try 2.4.26? I'm stuck to this version for now. I can't try .26 ron

1 0

答复: epia-m IRQ routing
by YhLu 16 Apr '04

16 Apr '04

Why just try 2.4.26? Only tg3.c has problem in opteron MB. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月16日 12:22 收件人: linuxbios(a)clustermatic.org 主题: epia-m IRQ routing kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

Broadcom NIC, MPTable and APIC ID for HDAMA
by Li-Ta Lo 16 Apr '04

16 Apr '04

Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
13
Older →

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 2004