coreboot March 2007

coreboot@coreboot.org

118 participants
226 discussions

[LinuxBIOS] Distros
by joe＠smittys.pointclark.net 16 Mar '07

16 Mar '07

Hello, What Linux Distro is everyone using to build LinuxBIOS? I only ask because the one I am using is having an issue right now. Thanks - Joe

8 13

[LinuxBIOS] google support: automatic build reports: HOWTO ?
by Quux 16 Mar '07

16 Mar '07

can someone knowledgable tell us about those automated build reports on mainboards ? how does it work ? greetinx: --Q

7 14

[LinuxBIOS] HOW ABOUT THE SUPPORT FOR USB BOOT IN FIL O-0.5?
by 徐家德 15 Mar '07

15 Mar '07

Hi My MB is dbe61,It can boot from IDE normally.But when I try to get it boot from usb disk,I got the serial output as below. How can I fix it?Any suggestions? thanks :) FILO version 0.5 (root(a)localhost.localdomain) Tue Feb 27 10:48:56 CST 2007 collect_sys_info: boot eax = 0xe1fb007 collect_sys_info: boot ebx = 0x77b65e0 collect_sys_info: boot arg = 0x77b65e0 malloc_diag: alloc: 0 bytes (0 blocks), free: 65528 bytes (1 blocks) malloc_diag: alloc: 24 bytes (1 blocks), free: … [View More]65504 bytes (1 blocks) malloc_diag: alloc: 40 bytes (2 blocks), free: 65488 bytes (1 blocks) collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 00000530 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 00000530 malloc_diag: alloc: 112 bytes (3 blocks), free: 65416 bytes (1 blocks) convert_memmap: 0x00000000000000 0x00000000000728 16 convert_memmap: 0x00000000000728 0x0000000009f8d8 1 convert_memmap: 0x000000000f0000 0x00000000010000 16 convert_memmap: 0x00000000100000 0x000000076c0000 1 collect_sys_info: 0000000000000728-00000000000a0000 collect_sys_info: 0000000000100000-00000000077c0000 collect_sys_info: RAM 119 MB pci_init: Scanning PCI: found 14 devices malloc_diag: alloc: 288 bytes (4 blocks), free: 65240 bytes (1 blocks) pci_init: 00:01.0 1022:2080 0600 00 pci_init: 00:01.1 1022:2081 0300 00 pci_init: 00:01.2 1022:2082 1010 00 pci_init: 00:0b.0 1106:3044 0c00 10 pci_init: 00:0c.0 1106:3106 0200 00 pci_init: 00:0d.0 1106:3106 0200 00 pci_init: 00:0e.0 168c:0013 0200 00 pci_init: 00:0f.0 1022:2090 0601 00 pci_init: 00:0f.2 1022:209a 0101 80 pci_init: 00:0f.3 1022:2093 0401 00 pci_init: 00:0f.4 1022:2094 0c03 10 pci_init: 00:0f.5 1022:2095 0c03 20 pci_init: 00:0f.6 1022:2096 0c03 fe pci_init: 00:0f.7 1022:2097 0c03 80 Press <Enter> for default boot, or <Esc> for boot prompt... 2 1 timed out boot: uda1:/boot/vmlinuz-2.6.15-1.2054_FC5 initrd=uda1:/boot/initrd-2.6.15-1.2054_FC5.img root=/dev/sda1 console=tty0 console=ttyS0,115200 malloc_diag: alloc: 432 bytes (5 blocks), free: 65096 bytes (1 blocks) malloc_diag: alloc: 448 bytes (6 blocks), free: 65080 bytes (1 blocks) LinuxLabs USB bootloader ohc_init: ohc_init num_controllers=0 ohci=121300 malloc_diag: alloc: 968 bytes (7 blocks), free: 64560 bytes (1 blocks) malloc_diag: alloc: 4048 bytes (8 blocks), free: 61480 bytes (1 blocks) malloc_diag: alloc: 4208 bytes (9 blocks), free: 61320 bytes (1 blocks) malloc_diag: alloc: 4272 bytes (10 blocks), free: 61256 bytes (1 blocks) ohc_init: Found OHCI at f69a3670 ohc_reset: Resetting OHCI ohc_reset: USB HC reset_hc usb-f69a3670: ctrl = 0x0 ohc_start: Starting OHCI malloc_diag: alloc: 7352 bytes (11 blocks), free: 58176 bytes (1 blocks) poll_usb: poll_usb1 i=0 poll_o_root_hub1 v=00010101 port = f69a36c4, controller = 0 poll_o_root_hub: poll_o_root_hub2 v=00010101 poll_o_root_hub21 v=00010101 Connection on port f69a36c4 New USB device, setting address 2 dma_to_td: can not find td dma_to_td: can not find td .RET URB:[ 0] dev: 0,ep: 0-O,type:CTRL,flags: 0,len:0/0,stat:-115(ffffff8d) ohci.c: cmd(8): 00 00 00 f2 90 e9 67 07 configure_device: Fetching device descriptor length dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/8,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 01 00 00 08 00 ohci.c: data(0/8): stat:-115 configure_device: Fetching device descriptor dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/0,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 01 00 00 00 00 configure_device: Fetching config descriptor length dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/8,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 02 00 00 08 00 ohci.c: data(0/8): stat:-115 configure_device: Fetching config descriptor dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/0,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 02 00 00 00 00 configure_device: device: dump_device_descriptor: bLength: 00 dump_device_descriptor: type: 00 dump_device_descriptor: bcdVersion: 00 dump_device_descriptor: Class: 00 dump_device_descriptor: SubClass: 00 dump_device_descriptor: protocol: 00 dump_device_descriptor: max_packet: 0 dump_device_descriptor: idVendor: 0000 dump_device_descriptor: idProduct: 0000 dump_device_descriptor: bcdDeviceVersion: 00 dump_device_descriptor: iManufacturor: 00 dump_device_descriptor: iProduct: 00 dump_device_descriptor: iSerial: 00 dump_device_descriptor: bNumConfig: 00 configure_device: config: dump_config_descriptor: bLength: 00 dump_config_descriptor: type: 00 dump_config_descriptor: wTotalLength: 0000 dump_config_descriptor: bNumInterfaces: 00 dump_config_descriptor: bConfigurationValue: 00 dump_config_descriptor: iConfiguration: 00 dump_config_descriptor: bmAttributes: 00 dump_config_descriptor: bMaxPower: 00 dump_config_descriptor: Interface(140ee7): dump_interface_descriptor: bLength: 00 dump_interface_descriptor: type: 00 dump_interface_descriptor: bInterfaceNumber: 00 dump_interface_descriptor: bAlternateSetting: 00 dump_interface_descriptor: bNumEndpoints: 00 dump_interface_descriptor: bInterfaceClass: 00 dump_interface_descriptor: bInterfaceSubClass: 00 dump_interface_descriptor: bInterfaceProtocol: 00 dump_interface_descriptor: iInterface: 00 configure_device: Selecting Configuration number 0: dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-O,type:CTRL,flags: 0,len:0/0,stat:-115(ffffff8d) ohci.c: cmd(8): 00 09 00 00 00 00 00 00 00:00:00 dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/4,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 03 00 00 04 00 ohci.c: data(0/4): stat:-115 dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/255,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 03 00 0f ff 00 ohci.c: data(0/255): stat:-115 Manufacturor: USB dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/255,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 03 00 0f ff 00 ohci.c: data(0/255): stat:-115 Product: B dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/255,stat:-115(ffffff8d) ohci.c: cmd(8): 80 06 00 03 00 0f ff 00 ohci.c: data(0/255): stat:-115 Serial: configure_device: DEVICE CONFIGURED OHCI controller usb-f69a3670 state control: 0x00000093 HCFS=operational CLE CBSR=3 cmdstatus: 0x00000000 SOC=0 intrstatus: 0x00000044 RHSC SF intrenable: 0x80000013 MIE UE WDH SO ed_controlhead 077ac390 hcca frame #0000 roothub.a: 10000a04 POTPGT=16 OCPM NPS NDP=4 roothub.b: 00000000 PPCM=0000 DR=0000 roothub.status: 00000000 roothub.portstatus [0] = 0x00000103 PPS PES CCS roothub.portstatus [1] = 0x00000100 PPS roothub.portstatus [2] = 0x00000100 PPS roothub.portstatus [3] = 0x00000100 PPS dma_to_td: can not find td .RET URB:[ 0] dev: 2,ep: 0-I,type:CTRL,flags: 0,len:0/1,stat:-115(ffffff8d) ohci.c: cmd(8): a1 fe 00 00 00 00 01 00 ohci.c: data(0/1): stat:-115 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36c8, controller = 0 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36cc, controller = 0 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36d0, controller = 0 poll_usb: poll_usb1 i=0 poll_o_root_hub1 v=00000103 port = f69a36c4, controller = 0 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36c8, controller = 0 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36cc, controller = 0 poll_o_root_hub: poll_o_root_hub1 v=00000100 port = f69a36d0, controller = 0 malloc_diag: alloc: 7336 bytes (10 blocks), free: 58192 bytes (2 blocks) malloc_diag: alloc: 7192 bytes (9 blocks), free: 58336 bytes (2 blocks) boot: uda1:/boot/vmlinuz-2.6.15-1.2054_FC5 initrd=uda1:/boot/initrd-2.6.15-1.2054_FC5.img root=/dev/sda1 console=tty0 console=ttyS0,115200 [View Less]

2 1

[LinuxBIOS] help
by Narfight 15 Mar '07

15 Mar '07

linuxbios-request(a)linuxbios.org a écrit : > Send linuxbios mailing list submissions to > linuxbios(a)linuxbios.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.openbios.org/mailman/listinfo/linuxbios > or, via email, send a message with subject or body 'help' to > linuxbios-request(a)linuxbios.org > > You can reach the person managing the list at > linuxbios-owner(a)linuxbios.org > > When replying, please edit your Subject … [View More]line so it is more specific > than "Re: Contents of linuxbios digest..." > > > Today's Topics: > > 1. Re: google support: automatic build reports: HOWTO ? (todthgie) > 2. Re: Store cmos on flash (Russ Whitaker) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 Mar 2007 20:37:52 +0100 > From: "todthgie" <todthgie(a)hotmail.com> > Subject: Re: [LinuxBIOS] google support: automatic build reports: > HOWTO ? > To: <linuxbios(a)linuxbios.org> > Message-ID: <BAY132-DAV79F8CFE53F41FD14B366BC7730(a)phx.gbl> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > hello all, > > sorry about the bad language in this mail, i dont have much time atm. > I'm quite new to linuxbios(this is my first post to te list), but i find it > realy interresting. > in some time i will start to install it in some machines here starting whit > the to be carpc. > I'm more a hardware engineer that a software one (but i concider firmware > almost hardware;-) ) > and i think i can and maybe will design a (new) device for automated testing > > This because i dont realy like to (hot) swap chips. and i think adding > support for new board (i have not found one of my boards on the list) > will not be done i a few builds. So the device for automated building can > help greatly with the 'normal' devolopment. > > but before i start designing i would like to have some input about what > functions the device should have. > > at this moment im thinking about the folowing: > > - as a minimum savior like way to update the bios, but much better is this > can be done remote > im thinking about using the flash chip as a shared memory between a > microcontroler and the motherboard (using tristable drivers for arbitrage) > - have a usb to serial convertor so the test server can talk to the > microcontroler. > - maybe include a way to switch the mains voltage to the target computer > - OR / AND inculde a way to switch off the remaining voltage (+5Vsb) of the > atx power supply (this is easy) > and prevent the mother board from switching on the atx PSU. > - monitor at least some core functions of the target device (power supply > voltage ect) to report state to the host. > - maybe relay the serial debug console of the target to the host. > > - of cource als schematics/layouts/Ucfirmware will be public. > - i have no idea of i price yet. but i hope to come up with something that > can do a lost for not too much money. > > furthermore i would like to know what kind of bios chips are around on > motherboards.. i know of the following: > > Prom like flash devices in DIP or PLCC or SOIC packages that have Address, > Data and Control (CE/RD/WR) busses > Disk on Chip Millenium combo devices that combine a flash 'disk' with a > 'bios' > > Greetings > Reinder de Haan > The Netherlands > > > > ----- Original Message ----- > From: "Peter Stuge" <stuge-linuxbios(a)cdy.org> > To: <linuxbios(a)linuxbios.org> > Sent: Wednesday, March 14, 2007 19:14 > Subject: Re: [LinuxBIOS] google support: automatic build reports: HOWTO ? > > > >> On Wed, Mar 14, 2007 at 05:44:12PM +0100, Stefan Reinauer wrote: >> >>> It might be an interesting idea to integrate the bios savior into >>> the circuit as well, as IOSS does not produce the bios savior >>> anymore. >>> >> No doubt the way to go. >> >> >> //Peter >> >> -- >> linuxbios mailing list >> linuxbios(a)linuxbios.org >> http://www.openbios.org/mailman/listinfo/linuxbios >> >> > > > > > ------------------------------ > > Message: 2 > Date: Wed, 14 Mar 2007 17:39:12 -0700 (PDT) > From: Russ Whitaker <russ(a)ashlandhome.net> > Subject: Re: [LinuxBIOS] Store cmos on flash > To: Peter Stuge <stuge-linuxbios(a)cdy.org> > Cc: linuxbios(a)linuxbios.org > Message-ID: <Pine.LNX.4.64.0703141734070.6525(a)bigred.russwhit.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > > On Wed, 14 Mar 2007, Peter Stuge wrote: > > >> Hi Thomas, >> >> On Wed, Mar 14, 2007 at 12:53:09PM +0100, Thomas Ekstrand (AL/EAB) wrote: >> >>>> Is there a way to store cmos settings in the BIOS flash chip? >>>> >> Nothing prepared, no. Of course you could put defaults into code for >> your particular target. >> >> >> >>>> Or is there another way of resolving the issue of an unpowered >>>> cmos? (no battery) >>>> > Another issue: the cmos is the hardware clock. With a battery, it keeps > running while the box is powered down. > > russ > > > > ------------------------------ > > _______________________________________________ > linuxbios mailing list > linuxbios(a)linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > End of linuxbios Digest, Vol 25, Issue 61 > ***************************************** > > [View Less]

1 0

Re: [LinuxBIOS] Store cmos on flash
by Peter Stuge 15 Mar '07

15 Mar '07

Hi Thomas, On Wed, Mar 14, 2007 at 12:53:09PM +0100, Thomas Ekstrand (AL/EAB) wrote: > > Is there a way to store cmos settings in the BIOS flash chip? Nothing prepared, no. Of course you could put defaults into code for your particular target. > > Or is there another way of resolving the issue of an unpowered > > cmos? (no battery) So far the settings in CMOS have not really been critical to the boot process. At most there's the fallback vs. normal setting which indicates … [View More]

2 1

[LinuxBIOS] Smart card
by Fred . 14 Mar '07

14 Mar '07

I think it would be cool if the computer would refuse to boot without a smart card.

3 2

[LinuxBIOS] Accessing MCP55 internal serial UART, GPIOs
by Ed Swierk 14 Mar '07

14 Mar '07

I'm trying to get LinuxBIOS booting on a custom board with a Socket AM2 Athlon and an MCP55. There is no SuperIO; instead, we're using the MCP55's internal serial UART. A couple of the MCP55's GPIO pins are hooked up to LEDs. I have had no luck getting either the serial port or the LEDs to work, though. My cache_as_ram_main() sets up the serial port by: - enabling the serial port and configuring the IO address and IRQ in register 0x78 on PCI device 1:0 - NOT redirecting IO address 0x3f8 to … [View More]

5 7

[LinuxBIOS] Problem on compilation
by ccases＠navista.fr 14 Mar '07

14 Mar '07

Hi, For recapitulate a little, I have un embeded motherboard advantech PCM-5823 and I am interrest to put LinuxBios in. I have use the configuration file of iei nova4899r for create my config file (because the nova4899r is an embeded motherboard seems to have the same architectur, something has near ). I have create this config file (Config.lb) in LinuxBiosV2/targets/advantech/pcm-5823/ like this : >target pcm-5823 >mainboard advantech/pcm-5823 > >option DEFAULT_CONSOLE_LOGLEVEL=… [View More]8 >option MAXIMUM_CONSOLE_LOGLEVEL=8 >option CONFIG_COMPRESSED_PAYLOAD_NRV2B=1 > >option ROM_SIZE=(256*1024)-(64*1024)-(32*1024) >#option FALLBACK_SIZE = ROM_SIZE > >romimage "normal" > option USE_FALLBACK_IMAGE=0 > option LINUXBIOS_EXTRA_VERSION=".0Normal" > option ROM_IMAGE_SIZE=64*1024 > payload /home/ccases/etherboot-5.2.6/src/bin/rtl8139.elf >end > >romimage "fallback" > option USE_FALLBACK_IMAGE=1 > option LINUXBIOS_EXTRA_VERSION=".0Fallback" > option ROM_IMAGE_SIZE=64*1024 > payload /home/ccases/etherboot-5.2.6/src/bin/rtl8139.elf >end > >buildrom ./linuxbios.rom ROM_SIZE "fallback" "normal" I build the makefile with ./buildtarget and if I do an make, I have this message : 6' -DCONFIG_PCI_ROM_RUN='1' -DCONFIG_PCI_64BIT_PREF_MEM='0' -DHAVE_MP_TABLE='0' -DHAVE_PIRQ_TABLE='1' -DUSE_FALLBACK_IMAGE='1' -DHAVE_HARD_RESET='0' -DIRQ_SLOT_COUNT='7' -DLINUXBIOS_EXTRA_VERSION='".0Fallback"' -DFALLBACK_SIZE='0x20000' -DROM_SIZE='0x28000' -DROM_SECTION_SIZE='0x20000' -DROM_SECTION_OFFSET='0x8000' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xffff0000' -DCONFIG_UDELAY_TSC='1' -DCONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2='0' -DCONFIG_UDELAY_IO='0' -DUSE_FAILOVER_IMAGE='0' -Os -nostdinc -nostdlib -fno-builtin -Wall -o static.o static.c rm -f linuxbios.a ar cr linuxbios.a malloc.o lapic_cpu_init.o pci_ops.o lapic.o smbus_ops.o memset.o pci_ops_auto.o superio.o linuxbios_table.o fallback_boot.o pciexp_device.o tables.o keyboard.o pnp_device.o printk.o irq_tables.o pcix_device.o decode.o pci_device.o console.o delay_tsc.o elfboot.o hardwaremain.o boot.o i8259.o delay.o version.o pci_ops_mmconf.o memcmp.o exception.o secondary.o isa-dma.o pcibios.o hypertransport.o vtxprintf.o ops.o prim_ops.o root_device.o cardbus_device.o uart8250.o sys.o device_util.o ./option_table.o compute_ip_checksum.o device.o onboard.o northbridge.o memcpy.o agp_device.o clog2.o pirq_routing.o memmove.o pci_rom.o pci_ops_conf2.o pci_ops_conf1.o mc146818rtc.o cache.o fpu.o rom_stream.o debug.o c_start.o ops2.o biosemu.o vsprintf.o cpu.o static.o gcc -m32 -nostdlib -r -o linuxbios_ram.o c_start.o uart8250_console.o model_gx1_init.o mainboard.o cs5530.o vga_console.o cs5530_ide.o linuxbios.a /usr/lib/gcc-lib/i486-linux/3.3.5/libgcc.a gcc -m32 -nostdlib -nostartfiles -static -o linuxbios_ram -T /home/ccases/LinuxBIOSv2/src/config/linuxbios_ram.ld linuxbios_ram.o linuxbios_ram.o(.text+0x4b6b): In function `write_tables': : undefined reference to `write_pirq_routing_table' collect2: ld returned 1 exit status make[1]: *** [linuxbios_ram] Error 1 make[1]: Leaving directory `/home/ccases/LinuxBIOSv2/targets/advantech/pcm-5823/pcm-5823/fallback' make: *** [fallback/linuxbios.rom] Error 1 I don't know why, if anyone has a solution, Thank's by advance for your help regards Ccases [View Less]

4 10

[LinuxBIOS] Store cmos on flash
by Thomas Ekstrand (AL/EAB) 14 Mar '07

14 Mar '07

> Hi! > > I'm quite new to this and i'm doing some research to learn more but > i'm having trouble finding some answers. > > Is there a way to store cmos settings in the BIOS flash chip? > Or is there another way of resolving the issue of an unpowered cmos? > (no battery) > > Does it matters what flash chip you use? Is linuxbios compatible with > all? I'm talking about sizes at about 1Mbyte. > > I'm also curious of how you apply settings during run-… [View More]

1 0

[LinuxBIOS] cmos.layout
by joe＠smittys.pointclark.net 14 Mar '07

14 Mar '07

Hello everyone, I do have a question. What is the purpose of the cmos.layout file. Does this come from the DMI of the original bios? What other source files use this file? Thanks - Joe

2 3

← Newer
1
...
10
11
12
13
14
15
16
...
23
Older →

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 March 2007