coreboot

coreboot@coreboot.org

10 participants
39710 discussions

pirq table consistency
by Stefan Reinauer 28 Oct '03

28 Oct '03

Hi, If Linux detects an inconsistent pirq table, it will refuse to use it. The attached patch fixes the pirq table in case LinuxBIOS finds a problem. Since there was kind of a common sense that pirq tables et al should be generated by LinuxBIOS instead of coping with hard codes, this might be a first but very small step. If I get no objections, I'd like to check it into the freebios2 cvs soon. Stefan -- Stefan Reinauer, SUSE LINUX AG Teamleader Architecture Development

2 2

epia 800
by Erdem Guven 28 Oct '03

28 Oct '03

Hi, I have a epia 800. I have build via/epia/Config.filo.lb, compiled & flashed succesfully. But it stops after : ... vt8601 done Copying LinuxBIOS to ram. Jumping to LinuxBIOS. Post code : FE It's in c_start.S before 'call hardwaremain'. Can someone help me? Thanks. __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/

3 8

HDAMA errors during PCI scan
by Craig C Forney 28 Oct '03

28 Oct '03

I wanted get up to date with the latest code developments with Linuxbios on the HDAMA board. I downloaded the current source tree from sourceforge this morning. The build went just fine. However, it gets stuck during initialization. The only code change I made to the latest version was to change the PAYLOAD to FILO 0.4. (The version from a few weeks ago makes, compiles, and boots Linux using FILO 0.3.) I'm guessing that there is some configuration change needed for HDAMA. Any thoughts? -- Craig Forney, Opus Innovations LLC Latest version (not working): Copying LinuxBIOS to ram. 003 booting... Finding PCI configuration type. PCI: Using configuration type 1 Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Enumerating: AMD K8 Enumerating: AMD 8111 Enumerating: NSC 87360 Enumerating buses...PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [ffff/ffff] enabled PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.1 No device operations PCI: 00:19.2 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.2 No device operations PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring. PCI: 00:19.3 No device operations amdk8_scan_chains max: 0 starting... Earlier version (working): LinuxBIOS-1.1.4.0Fallback Thu Oct 9 03:02:57 PDT 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.4.0Fallback Thu Oct 9 03:02:57 PDT 2003 booting... Finding PCI configuration type. PCI: Using configuration type 1 Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Enumerating: AMD K8 Enumerating: NSC 87360 Enumerating buses...PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [1022/1100] enabled PCI: 00:19.1 [1022/1101] enabled PCI: 00:19.2 [1022/1102] enabled PCI: 00:19.3 [1022/1103] ops PCI: 00:19.3 [1022/1103] enabled amdk8_scan_chains max: 0 starting... Hyper transport scan link: 0 max: 1 PCI: 01:01.0 [1022/7450] enabled next_unitid: 0003 PCI: 01:03.0 [1022/7460] enabled next_unitid: 0007 HyperT reset needed

2 1

Support for Boser crusoe board?
by Hubert Denkmair 25 Oct '03

25 Oct '03

Hello list, I have a very, VERY nice mini PC with Crusoe TM5400 / VIA VT82C686A chipset here: http://www.boser.com.tw/products/sbc/hs1600.htm Linux works fine on it, now it would be cool if it was supported by linuxbios. There seems to be support for the vt82c686 (without 'A') in the v1 source tree, but of course there is no direct support for the Boser board. lspci says: --- 00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge 00:00.1 RAM memory: Transmeta Corporation SDRAM controller 00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 10) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10) 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:09.0 VGA compatible controller: Chips and Technologies F69000 HiQVideo (rev 64) 00:0b.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive (rev 02) --- Are there chances that this board will work with linuxbios? If yes, what do I have to do to get it working? Hubert --- PS: lspci -v, don't know if it helps: ---------------------------------------- 00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge Subsystem: Transmeta Corporation: Unknown device 0295 Flags: bus master, medium devsel, latency 0 Memory at e2000000 (32-bit, non-prefetchable) [size=1M] 00:00.1 RAM memory: Transmeta Corporation SDRAM controller Subsystem: Transmeta Corporation: Unknown device 0295 Flags: fast devsel 00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad Subsystem: Transmeta Corporation: Unknown device 0295 Flags: fast devsel 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 32 I/O ports at c000 [size=16] Capabilities: [c0] Power Management version 2 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 9 I/O ports at c400 [size=32] Capabilities: [80] Power Management version 2 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) Flags: medium devsel Capabilities: [68] Power Management version 2 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 32, IRQ 15 I/O ports at cc00 [size=256] Memory at e2100000 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 00:09.0 VGA compatible controller: Chips and Technologies F69000 HiQVideo (rev 64) (prog-if 00 [VGA]) Subsystem: Chips and Technologies F69000 HiQVideo Flags: stepping, medium devsel, IRQ 12 Memory at e0000000 (32-bit, non-prefetchable) [size=16M] Expansion ROM at <unassigned> [disabled] [size=256K] 00:0b.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive (rev 02) Subsystem: ESS Technology: Unknown device 8898 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at d000 [size=64] I/O ports at d400 [size=16] I/O ports at d800 [size=16] I/O ports at dc00 [size=4] I/O ports at e000 [size=4] Capabilities: [c0] Power Management version 1

3 3

awakening noop
by Stefan Reinauer 25 Oct '03

25 Oct '03

Haven't seen these in a while, but they are back with the latest romcc release: apic.h:100.1: auto.c:123.19: auto.c:197.30: 0x735c00 noop Internal compiler warning: awakening noop? apic.h:100.1: auto.c:129.19: auto.c:197.30: 0x736b90 noop Internal compiler warning: awakening noop? Don't think they're saying anything else but that a dead subtree was detected in the code? Stefan -- Stefan Reinauer, SUSE LINUX AG Teamleader Architecture Development

2 2

Re: Totally mystified w/ V2
by Dave Ashley 25 Oct '03

25 Oct '03

Found earlier post which suggests doing this: buildtarget via/epia Guessed that this had to be done within targets directory. Got this error: ... lots cut, hashed over before TypeError: long requires exactly 1 argument; 2 given Ended up modifying util/newconfig/config.g> rule term: NUM {{ return long(NUM, 10) }} | HEX_PREFIX HEX_NUM {{ return long(HEX_NUM, 16) }} becomes rule term: NUM {{ return long(NUM) }} | HEX_PREFIX HEX_NUM {{ return long(eval("0x" + HEX_NUM)) }} Hopefully this is compatible with newer versions of python and that the long() can take 1 or 2 arguments... Then it dies on this: gcc ... -o crt0.o crt0.s crt0.s: Assembler messages: crt0.s:16821: Error: missing ')' crt0.s:16821: Error: junk `L+0x03)' after expression crt0.s:16822: Error: missing ')' crt0.s:16822: Error: junk `L|0x80)' after expression crt0.s:16835: Error: missing ')' crt0.s:16835: Error: junk `L+0x00)' after expression etc, etc. This is after I go into targets/via/epia/epia and do 'make'. -Dave

3 2

[Freebios-cvs] freebios2/src/northbridge/via/vt8601 raminit.c,1.11,1.12 (fwd)
by ron minnich 25 Oct '03

25 Oct '03

well, this is interesting. I just got the commit email for something I did several days ago. Does anyone have contacts at sourceforge? I'd like to see if this is temporary delays or a death spasm. ron ---------- Forwarded message ---------- Date: Wed, 22 Oct 2003 14:54:21 -0700 From: rminnich(a)users.sourceforge.net To: freebios-cvs(a)lists.sourceforge.net Subject: [Freebios-cvs] freebios2/src/northbridge/via/vt8601 raminit.c,1.11, 1.12

1 0

the new pcchips m810 with DDR
by Andre Dias 24 Oct '03

24 Oct '03

SDRAM memories are becoming scarce. DDR memories are more common. Linuxbios already supports DDR, and the cheapest pcchips board that uses DDR and will substitute the m810 will be M810dlu 7.5A (http://www.pcchips.com.tw/product/M810DLUv75a.html). Does linuxbios support it? I have a very small company that uses linuxbios on M810 and K7SEM boards (sis730/sis730s), despite a small problem with keyboard idle, its pretty stable. I am willing to pay to have linuxbios working on M810dlu 7.5A (though I am very short on money). I don't need X, just the framebuffer, but I need the keyboard bug solved. Can someone help me? I can donate the boards and material. Thanks fellows

1 0

v2 -- status of epia-m (m!!!)
by Niki Waibel 24 Oct '03

24 Oct '03

what is the current dev status of epia-m in v2? niki

2 1

Totally mystified w/ V2
by Dave Ashley 24 Oct '03

24 Oct '03

Well I'm having no luck trying to figure out how to build V2. No doc files, just some ".tex" files which tex doesn't like. Some files that the old configure method doesn't work on: dash% python ../util/config/NLBConfig.py ../targets/via/epia/Config.lb /ram/freebios2 /ram/freebios2/targets/via/epia/Config.lb:5: arch, target, or mainboard must be the first commands, not loadoptions Can someone tell me how to build the epia target in the freebios2 tree? Here's some stuff that should make this thread easier to find building with v2 building with linuxbios version2 building with linuxbios v2 how-to build version2 Thanks-- Dave

2 1

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