coreboot September 2006

coreboot@coreboot.org

52 participants
173 discussions

Re: [LinuxBIOS] (fwd) Re: USB bootloader
by yhlu 09 Sep '06

09 Sep '06

you need to use filo.zelf YH On 9/8/06, Al Boldi <a1426z(a)gawab.com> wrote: > yhlu wrote: > > did you try filo on Etherboot? > > > > I remember I first tried out on UHCI, and then added OHCI support. > > Yes, but filo.zlilo on etherboot5.4.2 just reboots on initial loading. > > Filo 0.5 from openbios.org works fine with ide but not usb. > > Also, the i440bx board has a UHCI controller. > > > Thanks for looking into this! > > -- > Al > > > > > YH > > > > On 9/7/06, Stefan Reinauer <stepan(a)coresystems.de> wrote: > > > Hi, > > > > > > anyone has an idea on this one? > > > > > > ----- Forwarded message from Al Boldi ----- > > > > > > Date: Thu, 7 Sep 2006 13:52:28 +0300 > > > From: Al Boldi <a1426z(a)gawab.com> > > > To: Stefan Reinauer <stepan(a)coresystems.de> > > > Cc: openbios(a)lists.openbios.org, etherboot-discuss(a)lists.sourceforge.net > > > Subject: Re: USB bootloader > > > > > > > > > Thanks for your response! > > > > > > Stefan Reinauer wrote: > > > > * Al Boldi <a1426z(a)gawab.com> [060904 20:58]: > > > > > FILO version 0.5 .... > > > > > Can't get memory map from firmware. Using hardcoded default. > > > > > Press ... > > > > > boot: uda1:/vmlinuz > > > > > LinuxLabs USB bootloader > > > > > New USB device, setting address 2 (repeats 1-4 times) > > > > > boot: uda1:/vmlinuz > > > > > LinuxLabs USB bootloader > > > > > Out of heap space > > > > > > > > Please try increasing the heap space in i386/ldscript by changing the > > > > following lines: > > > > /* 16KB heap and stack */ > > > > HEAP_SIZE = 16384; > > > > to > > > > /* 32KB heap and 16K stack */ > > > > HEAP_SIZE = 32768; > > > > > > > > > And, how can filo 0.5 be fixed to boot USB? > > > > > > > > If the message stays, try all the way up to 262144. > > > > > > Ok, the message is gone, but it still does not boot. > > > > > > Turning on debug repeats this: > > > > > > FILO version 0.5 (root@localhost) Thu Sep 7 13:40:13 AST 2006 > > > collect_sys_info: boot eax = 0x0 > > > collect_sys_info: boot ebx = 0x0 > > > collect_sys_info: boot arg = 0xfeee330 > > > collect_elfboot_info: Bootloader: Etherboot > > > collect_elfboot_info: Version: 5.4.1 > > > malloc_diag: alloc: 0 bytes (0 blocks), free: 262136 bytes (1 blocks) > > > malloc_diag: alloc: 16 bytes (1 blocks), free: 262120 bytes (1 blocks) > > > collect_elfboot_info: Image name: /tftpboot/boot/pxelinux.0 > > > malloc_diag: alloc: 32 bytes (2 blocks), free: 262104 bytes (1 blocks) > > > collect_linuxbios_info: Searching for LinuxBIOS tables... > > > Can't get memory map from firmware. Using hardcoded default. > > > malloc_diag: alloc: 72 bytes (3 blocks), free: 262064 bytes (1 blocks) > > > collect_sys_info: 0000000000000000-00000000000a0000 > > > collect_sys_info: 0000000000100000-0000000002000000 > > > collect_sys_info: RAM 32 MB > > > relocate: Current location: 0x100000-0x16d827 > > > relocate: Relocating to 0x1f927d0-0x1fffff7... ok > > > setup_timers: CPU 413 MHz > > > pci_init: Scanning PCI: found 9 devices > > > malloc_diag: alloc: 192 bytes (4 blocks), free: 261944 bytes (1 blocks) > > > pci_init: 00:00.0 8086:7120 0600 00 > > > pci_init: 00:01.0 8086:7121 0300 00 > > > pci_init: 00:1e.0 8086:2418 0604 00 > > > pci_init: 01:04.0 1282:9102 0200 00 > > > pci_init: 01:05.0 10ec:8139 0200 00 > > > pci_init: 01:0a.0 1191:8040 0100 00 > > > pci_init: 00:1f.0 8086:2410 0601 00 > > > pci_init: 00:1f.1 8086:2411 0101 80 > > > pci_init: 00:1f.2 8086:2412 0c03 00 > > > > > > boot: uda1:/vmlinuz > > > malloc_diag: alloc: 216 bytes (5 blocks), free: 261920 bytes (1 blocks) > > > malloc_diag: alloc: 232 bytes (6 blocks), free: 261904 bytes (1 blocks) > > > file_open: dev=uda1, path=/vmlinuz > > > LinuxLabs USB bootloader > > > uhc_init: Found UHCI at ffffd000 > > > uhc_reset: Resetting UHCI > > > uhc_init: uhc_init setting framelist to: 01e927d0 > > > uhc_start: Starting UHCI > > > dump_uhci: HCI at ffffd000 > > > malloc_diag: alloc: 8432 bytes (7 blocks), free: 253704 bytes (1 blocks) > > > init_framelist: frame_list is at 12a000 > > > dump_link: frame_list_link: addr: 00125850 > > > dump_link: frame_list_link: raw addr: 1fb8020 > > > dump_link: frame_list_link: terminate: 0 > > > dump_link: frame_list_link: queue: 1 > > > dump_link: frame_list_link: depth: 0 > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 > > > blocks) poll_usb: poll_usb1 i=0 poll_u_root_hub1 v=00001083 > > > poll_u_root_hub2 v=00001083 poll_u_root_hub21 v=00001083 > > > Connection on port d010 New USB device, setting address 2 > > > uhci_control_msg: uhci_control_msg: request_type = 0 request = 5 > > > wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free: 246520 bytes > > > (1 blocks) dump_uhci: HCI at ffffd000 > > > dump_td: failed_transaction: TD(0011d860): > > > dump_td: failed_transaction: type: SETUP > > > dump_td: failed_transaction: retries: 3 > > > dump_td: failed_transaction: IOC > > > dump_td: failed_transaction: active: 0001 > > > dump_td: failed_transaction: device_addr: 00 > > > dump_td: failed_transaction: endpoint: 0 > > > dump_td: failed_transaction: data_toggle: 0 > > > dump_td: failed_transaction: max_transfer: 7 > > > dump_td: failed_transaction: actual: 0 > > > dump_td: failed_transaction: link: > > > dump_link: failed_transaction: addr: 0011d880 > > > dump_link: failed_transaction: raw addr: 1fb0050 > > > dump_link: failed_transaction: terminate: 0 > > > dump_link: failed_transaction: queue: 0 > > > dump_link: failed_transaction: depth: 0 > > > dump_td: failed_transaction: TD(0011d880): > > > dump_td: failed_transaction: type: IN > > > dump_td: failed_transaction: retries: 0 > > > dump_td: failed_transaction: active: 0001 > > > dump_td: failed_transaction: device_addr: 00 > > > dump_td: failed_transaction: endpoint: 0 > > > dump_td: failed_transaction: data_toggle: 1 > > > dump_td: failed_transaction: max_transfer: 7ff > > > dump_td: failed_transaction: actual: 0 > > > dump_td: failed_transaction: link: > > > dump_link: failed_transaction: addr: fe16d830 > > > dump_link: failed_transaction: raw addr: 0000 > > > dump_link: failed_transaction: terminate: 1 > > > dump_link: failed_transaction: queue: 0 > > > dump_link: failed_transaction: depth: 0 > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 > > > blocks) configure_device: configure_device: set_address failed! > > > > > > poll_u_root_hub: poll_u_root_hub1 v=00001080 poll_usb1 i=0 > > > poll_u_root_hub1 v=00001083 poll_u_root_hub2 v=00001083 > > > poll_u_root_hub21 v=00001083 Connection on port d010 > > > New USB device, setting address 2 > > > uhci_control_msg: uhci_control_msg: request_type = 0 request = 5 > > > wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free: 246520 bytes > > > (1 blocks) dump_uhci: HCI at ffffd000 > > > dump_td: failed_transaction: TD(0011d860): > > > dump_td: failed_transaction: type: SETUP > > > dump_td: failed_transaction: retries: 3 > > > dump_td: failed_transaction: IOC > > > dump_td: failed_transaction: active: 0001 > > > dump_td: failed_transaction: device_addr: 00 > > > dump_td: failed_transaction: endpoint: 0 > > > dump_td: failed_transaction: data_toggle: 0 > > > dump_td: failed_transaction: max_transfer: 7 > > > dump_td: failed_transaction: actual: 0 > > > dump_td: failed_transaction: link: > > > dump_link: failed_transaction: addr: 0011d880 > > > dump_link: failed_transaction: raw addr: 1fb0050 > > > dump_link: failed_transaction: terminate: 0 > > > dump_link: failed_transaction: queue: 0 > > > dump_link: failed_transaction: depth: 0 > > > dump_td: failed_transaction: TD(0011d880): > > > dump_td: failed_transaction: type: IN > > > dump_td: failed_transaction: retries: 0 > > > dump_td: failed_transaction: active: 0001 > > > dump_td: failed_transaction: device_addr: 00 > > > dump_td: failed_transaction: endpoint: 0 > > > dump_td: failed_transaction: data_toggle: 1 > > > dump_td: failed_transaction: max_transfer: 7ff > > > dump_td: failed_transaction: actual: 0 > > > dump_td: failed_transaction: link: > > > dump_link: failed_transaction: addr: fe16d830 > > > dump_link: failed_transaction: raw addr: 0000 > > > dump_link: failed_transaction: terminate: 1 > > > dump_link: failed_transaction: queue: 0 > > > dump_link: failed_transaction: depth: 0 > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 > > > blocks) configure_device: configure_device: set_address failed! > > > > > > (...repeats...) > > > > > > > > > Thanks again! > > > > > > -- > > > Al > > > > > > > > > > > > ----- End forwarded message ----- > > > > > > -- > > > 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/ > > > > > > -- > > > linuxbios mailing list > > > linuxbios(a)linuxbios.org > > > http://www.openbios.org/mailman/listinfo/linuxbios > >

1 0

Re: [LinuxBIOS] FILO link errors on AMD64
by Stefan Reinauer 08 Sep '06

08 Sep '06

* Chris Stillo <Chris.Stillo(a)celoxica.com> [060908 23:02]: > Hello, > > I am attempting to compile FILO on a AMD64 (dk8htx) platform. Which version? svn? > I'm getting link errors(shown below), due to the 64-bit math > operations not being implemented in i386_x64 libgcc. Has anyone run > into this previously? not me. > ld -m elf_i386 -N -T i386/ldscript -o filo main/builtin.o main/grub/builtin.o > fs/builtin.o drivers/builtin.o drivers/usb/builtin.o i386/builtin.o /usr/lib/ > gcc-lib/x86_64-linux/3.3.5/./libgcc.a Is this with a clean checkout? If so, your gcc is broken as it points to the wrong libgcc. What does the following command tell you? $ gcc -m32 -print-libgcc-file-name on my system it says: /usr/lib64/gcc/x86_64-suse-linux/4.1.2/32/libgcc.a ^^^^ Try updating your gcc. 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

[LinuxBIOS] FILO link errors on AMD64
by Chris Stillo 08 Sep '06

08 Sep '06

Hello, I am attempting to compile FILO on a AMD64 (dk8htx) platform. I'm getting link errors(shown below), due to the 64-bit math operations not being implemented in i386_x64 libgcc. Has anyone run into this previously? Thanks, Chris chris.stillo(a)celoxica.com <BLOCKED::mailto:chris.stillo@celoxica.com> ld -m elf_i386 -N -T i386/ldscript -o filo main/builtin.o main/grub/builtin.o fs/builtin.o drivers/builtin.o drivers/usb/builtin.o i386/builtin.o /usr/lib/gcc-lib/x86_64-linux/3.3.5/./libgcc.a main/builtin.o(.text+0xa17): In function `number': : undefined reference to `__umoddi3' main/builtin.o(.text+0xa2f): In function `number': : undefined reference to `__udivdi3' drivers/builtin.o(.text+0xcad): In function `init_drive': : undefined reference to `__udivdi3' drivers/builtin.o(.text+0xcd2): In function `init_drive': : undefined reference to `__udivdi3' i386/builtin.o(.text+0x3b2): In function `calibrate_tsc': : undefined reference to `__udivdi3' i386/builtin.o(.text+0x3f0): In function `currticks': : undefined reference to `__udivdi3' i386/builtin.o(.text+0x443): more undefined references to `__udivdi3' follow make: *** [filo] Error 1 _____________________________________________________________________ This message has been checked for all known viruses by the MessageLabs Virus Scanning Service, on behalf of Celoxica Ltd. This email and any files transmitted with it are confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed. If you have received this in error, please contact the sender and delete the material immediately. Whilst this email has been swept for viruses, you should carry out your own virus check before opening any attachment. Celoxica Ltd accepts no liability for any loss or damage which may be caused by software viruses or interception or interruption of this email.

1 0

[LinuxBIOS] PATCH: Show flash chip size (flashrom).
by Uwe Hermann 08 Sep '06

08 Sep '06

Tiny patch to show the size of the detected flash part. Uwe. -- Uwe Hermann http://www.hermann-uwe.de http://www.it-services-uh.de | http://www.crazy-hacks.org http://www.holsham-traders.de | http://www.unmaintained-free-software.org

1 0

[LinuxBIOS] r2401 - trunk/LinuxBIOSv2/util/romcc
by svn＠openbios.org 08 Sep '06

08 Sep '06

Author: stepan Date: 2006-09-08 19:44:42 +0200 (Fri, 08 Sep 2006) New Revision: 2401 Added: trunk/LinuxBIOSv2/util/romcc/romcc.1 Log: add romcc manpage from Uwe Hermann Added: trunk/LinuxBIOSv2/util/romcc/romcc.1 =================================================================== --- trunk/LinuxBIOSv2/util/romcc/romcc.1 (rev 0) +++ trunk/LinuxBIOSv2/util/romcc/romcc.1 2006-09-08 17:44:42 UTC (rev 2401) @@ -0,0 +1,243 @@ +.\" Copyright (C) 2006 Uwe Hermann <uwe(a)hermann-uwe.de>. +.\" This manpage is licensed under the terms of the GNU GPL. +.TH ROMCC 1 "September 7, 2006" +.SH NAME +romcc \- compile C programs into binaries that don't use any RAM +.SH SYNOPSIS +.B romcc +.BR [ OPTIONS ] +.IR "<source>" ".c" +.SH DESCRIPTION +.B romcc +is a C compiler which produces binaries which do not rely on RAM, but +instead only use CPU registers. +.br +It is prominently used in the LinuxBIOS project to compile C code which +needs to run before the (Linux)BIOS has initialized the RAM, but can be +used for other purposes, too. +.SH OPTIONS +.B "\-o" <filename> +Output file name. +.PP +.B "\-f<option>" +Specify a generic compiler option. +.PP +.B "\-m<option>" +Specify an architecture-dependent compiler option. +.PP +.B "\-\-" +Specify that this is the last option. +.PP +.SH "GENERIC COMPILER OPTIONS" +.B "\-O" +.PP +.B "\-O2" +.PP +.B "\-E" +.PP +.B "\-ftrigraphs" +.PP +.B "\-fno-trigraphs" +.PP +.B "\-fpp-only" +.PP +.B "\-fno-pp-only" +.PP +.B "\-feliminate-inefectual-code" +.PP +.B "\-fno-eliminate-inefectual-code" +.PP +.B "\-fsimplify" +.PP +.B "\-fno-simplify" +.PP +.B "\-fscc-transform" +.PP +.B "\-fno-scc-transform" +.PP +.B "\-fsimplify-op" +.PP +.B "\-fno-simplify-op" +.PP +.B "\-fsimplify-phi" +.PP +.B "\-fno-simplify-phi" +.PP +.B "\-fsimplify-label" +.PP +.B "\-fno-simplify-label" +.PP +.B "\-fsimplify-branch" +.PP +.B "\-fno-simplify-branch" +.PP +.B "\-fsimplify-copy" +.PP +.B "\-fno-simplify-copy" +.PP +.B "\-fsimplify-arith" +.PP +.B "\-fno-simplify-arith" +.PP +.B "\-fsimplify-shift" +.PP +.B "\-fno-simplify-shift" +.PP +.B "\-fsimplify-bitwise" +.PP +.B "\-fno-simplify-bitwise" +.PP +.B "\-fsimplify-logical" +.PP +.B "\-fno-simplify-logical" +.PP +.B "\-fsimplify-bitfield" +.PP +.B "\-fno-simplify-bitfield" +.PP +.B "\-finline-policy=always" +.PP +.B "\-finline-policy=never" +.PP +.B "\-finline-policy=defaulton" +.PP +.B "\-finline-policy=defaultoff" +.PP +.B "\-finline-policy=nopenalty" +.PP +.B "\-fdebug-all" +.PP +.B "\-fno-debug-all" +.PP +.B "\-fdebug-abort-on-error" +.PP +.B "\-fno-debug-abort-on-error" +.PP +.B "\-fdebug-basic-blocks" +.PP +.B "\-fno-debug-basic-blocks" +.PP +.B "\-fdebug-fdominators" +.PP +.B "\-fno-debug-fdominators" +.PP +.B "\-fdebug-rdominators" +.PP +.B "\-fno-debug-rdominators" +.PP +.B "\-fdebug-triples" +.PP +.B "\-fno-debug-triples" +.PP +.B "\-fdebug-interference" +.PP +.B "\-fno-debug-interference" +.PP +.B "\-fdebug-scc-transform" +.PP +.B "\-fno-debug-scc-transform" +.PP +.B "\-fdebug-scc-transform2" +.PP +.B "\-fno-debug-scc-transform2" +.PP +.B "\-fdebug-rebuild-ssa-form" +.PP +.B "\-fno-debug-rebuild-ssa-form" +.PP +.B "\-fdebug-inline" +.PP +.B "\-fno-debug-inline" +.PP +.B "\-fdebug-live-range-conflicts" +.PP +.B "\-fno-debug-live-range-conflicts" +.PP +.B "\-fdebug-live-range-conflicts2" +.PP +.B "\-fno-debug-live-range-conflicts2" +.PP +.B "\-fdebug-color-graph" +.PP +.B "\-fno-debug-color-graph" +.PP +.B "\-fdebug-color-graph2" +.PP +.B "\-fno-debug-color-graph2" +.PP +.B "\-fdebug-coalescing" +.PP +.B "\-fno-debug-coalescing" +.PP +.B "\-fdebug-coalescing2" +.PP +.B "\-fno-debug-coalescing2" +.PP +.B "\-fdebug-verification" +.PP +.B "\-fno-debug-verification" +.PP +.B "\-fdebug-calls" +.PP +.B "\-fno-debug-calls" +.PP +.B "\-fdebug-calls2" +.PP +.B "\-fno-debug-calls2" +.PP +.B "\-fdebug-tokens" +.PP +.B "\-fno-debug-tokens" +.PP +.B "\-flabel-prefix=<prefix for assembly language labels>" +.PP +.B "\-\-label-prefix=<prefix for assembly language labels>" +.PP +.B "\-I<include path>" +.PP +.B "\-D<macro>[=defn]" +.PP +.B "\-U<macro>" +.SH "ARCHITECTURE-SPECIFIC COMPILER OPTIONS" +.B "\-mmmx" +.PP +.B "\-mno-mmx" +.PP +.B "\-msse" +.PP +.B "\-mno-sse" +.PP +.B "\-mnoop-copy" +.PP +.B "\-mno-noop-copy" +.PP +.B "\-mcpu=i386" +.PP +.B "\-mcpu=p2" +.PP +.B "\-mcpu=p3" +.PP +.B "\-mcpu=p4" +.PP +.B "\-mcpu=k7" +.PP +.B "\-mcpu=k8" +.PP +.B "\-mcpu=c3" +.PP +.B "\-mcpu=c3-2" +.SH BUGS +Please report any bugs to Eric W. Biederman <ebiederman(a)lnxi.com>. +.SH LICENCE +.B romcc +is covered by the GNU General Public License (GPL), version 2. +.SH SEE ALSO +.BR flashrom (1). +.SH COPYRIGHT +2003-2006 Eric W. Biederman +.SH AUTHORS +Eric W. Biederman <ebiederman(a)lnxi.com> +.br +Some contributions by others. +.PP +This manual page was written by Uwe Hermann <uwe(a)hermann-uwe.de>.

1 0

[LinuxBIOS] r2400 - in trunk/LinuxBIOSv2: . src/config
by svn＠openbios.org 08 Sep '06

08 Sep '06

Author: stepan Date: 2006-09-08 18:34:51 +0200 (Fri, 08 Sep 2006) New Revision: 2400 Removed: trunk/LinuxBIOSv2/ChangeLog Modified: trunk/LinuxBIOSv2/NEWS trunk/LinuxBIOSv2/src/config/Options.lb Log: hurry hurry before we might start 3.0 ;-) Deleted: trunk/LinuxBIOSv2/ChangeLog =================================================================== Modified: trunk/LinuxBIOSv2/NEWS =================================================================== --- trunk/LinuxBIOSv2/NEWS 2006-09-07 15:31:27 UTC (rev 2399) +++ trunk/LinuxBIOSv2/NEWS 2006-09-08 16:34:51 UTC (rev 2400) @@ -1,3 +1,6 @@ +- 2.0.0 + - this NEWS file is neglected in favor of the svn commit logs. + See http://snapshots.linuxbios.org/ - 1.1.8 - Store everything in arch - 1.1.7 Modified: trunk/LinuxBIOSv2/src/config/Options.lb =================================================================== --- trunk/LinuxBIOSv2/src/config/Options.lb 2006-09-07 15:31:27 UTC (rev 2399) +++ trunk/LinuxBIOSv2/src/config/Options.lb 2006-09-08 16:34:51 UTC (rev 2400) @@ -97,7 +97,7 @@ comment "Objcopy command" end define LINUXBIOS_VERSION - default "1.1.8" + default "2.0.0" export always format "\"%s\"" comment "LinuxBIOS version"

1 0

[LinuxBIOS] Tyan s2895 clarification
by Lionel Elie Mamane 08 Sep '06

08 Sep '06

Hi, I'm confused. My Tyan s2895 has a 8Mbit LPC Flash ROM, so I thought I could not use a RD1 Bios Savior, as no 8Mbit model was available; this kept me from trying out LinuxBIOS by fear of turning my computer into an expensive paper weight. But now I see posts to this ML's archive (such as http://www.linuxbios.org/pipermail/linuxbios/2006-January/013420.html) that talk about using 4Mbit savior with the Tyan s2895. Quid? -- Lionel

2 2

[LinuxBIOS] (fwd) Re: USB bootloader
by Stefan Reinauer 07 Sep '06

07 Sep '06

Hi, anyone has an idea on this one? ----- Forwarded message from Al Boldi ----- Date: Thu, 7 Sep 2006 13:52:28 +0300 From: Al Boldi <a1426z(a)gawab.com> To: Stefan Reinauer <stepan(a)coresystems.de> Cc: openbios(a)lists.openbios.org, etherboot-discuss(a)lists.sourceforge.net Subject: Re: USB bootloader Thanks for your response! Stefan Reinauer wrote: > * Al Boldi <a1426z(a)gawab.com> [060904 20:58]: > > FILO version 0.5 .... > > Can't get memory map from firmware. Using hardcoded default. > > Press ... > > boot: uda1:/vmlinuz > > LinuxLabs USB bootloader > > New USB device, setting address 2 (repeats 1-4 times) > > boot: uda1:/vmlinuz > > LinuxLabs USB bootloader > > Out of heap space > > Please try increasing the heap space in i386/ldscript by changing the > following lines: > /* 16KB heap and stack */ > HEAP_SIZE = 16384; > to > /* 32KB heap and 16K stack */ > HEAP_SIZE = 32768; > > > And, how can filo 0.5 be fixed to boot USB? > > If the message stays, try all the way up to 262144. Ok, the message is gone, but it still does not boot. Turning on debug repeats this: FILO version 0.5 (root@localhost) Thu Sep 7 13:40:13 AST 2006 collect_sys_info: boot eax = 0x0 collect_sys_info: boot ebx = 0x0 collect_sys_info: boot arg = 0xfeee330 collect_elfboot_info: Bootloader: Etherboot collect_elfboot_info: Version: 5.4.1 malloc_diag: alloc: 0 bytes (0 blocks), free: 262136 bytes (1 blocks) malloc_diag: alloc: 16 bytes (1 blocks), free: 262120 bytes (1 blocks) collect_elfboot_info: Image name: /tftpboot/boot/pxelinux.0 malloc_diag: alloc: 32 bytes (2 blocks), free: 262104 bytes (1 blocks) collect_linuxbios_info: Searching for LinuxBIOS tables... Can't get memory map from firmware. Using hardcoded default. malloc_diag: alloc: 72 bytes (3 blocks), free: 262064 bytes (1 blocks) collect_sys_info: 0000000000000000-00000000000a0000 collect_sys_info: 0000000000100000-0000000002000000 collect_sys_info: RAM 32 MB relocate: Current location: 0x100000-0x16d827 relocate: Relocating to 0x1f927d0-0x1fffff7... ok setup_timers: CPU 413 MHz pci_init: Scanning PCI: found 9 devices malloc_diag: alloc: 192 bytes (4 blocks), free: 261944 bytes (1 blocks) pci_init: 00:00.0 8086:7120 0600 00 pci_init: 00:01.0 8086:7121 0300 00 pci_init: 00:1e.0 8086:2418 0604 00 pci_init: 01:04.0 1282:9102 0200 00 pci_init: 01:05.0 10ec:8139 0200 00 pci_init: 01:0a.0 1191:8040 0100 00 pci_init: 00:1f.0 8086:2410 0601 00 pci_init: 00:1f.1 8086:2411 0101 80 pci_init: 00:1f.2 8086:2412 0c03 00 boot: uda1:/vmlinuz malloc_diag: alloc: 216 bytes (5 blocks), free: 261920 bytes (1 blocks) malloc_diag: alloc: 232 bytes (6 blocks), free: 261904 bytes (1 blocks) file_open: dev=uda1, path=/vmlinuz LinuxLabs USB bootloader uhc_init: Found UHCI at ffffd000 uhc_reset: Resetting UHCI uhc_init: uhc_init setting framelist to: 01e927d0 uhc_start: Starting UHCI dump_uhci: HCI at ffffd000 malloc_diag: alloc: 8432 bytes (7 blocks), free: 253704 bytes (1 blocks) init_framelist: frame_list is at 12a000 dump_link: frame_list_link: addr: 00125850 dump_link: frame_list_link: raw addr: 1fb8020 dump_link: frame_list_link: terminate: 0 dump_link: frame_list_link: queue: 1 dump_link: frame_list_link: depth: 0 malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 blocks) poll_usb: poll_usb1 i=0 poll_u_root_hub1 v=00001083 poll_u_root_hub2 v=00001083 poll_u_root_hub21 v=00001083 Connection on port d010 New USB device, setting address 2 uhci_control_msg: uhci_control_msg: request_type = 0 request = 5 wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free: 246520 bytes (1 blocks) dump_uhci: HCI at ffffd000 dump_td: failed_transaction: TD(0011d860): dump_td: failed_transaction: type: SETUP dump_td: failed_transaction: retries: 3 dump_td: failed_transaction: IOC dump_td: failed_transaction: active: 0001 dump_td: failed_transaction: device_addr: 00 dump_td: failed_transaction: endpoint: 0 dump_td: failed_transaction: data_toggle: 0 dump_td: failed_transaction: max_transfer: 7 dump_td: failed_transaction: actual: 0 dump_td: failed_transaction: link: dump_link: failed_transaction: addr: 0011d880 dump_link: failed_transaction: raw addr: 1fb0050 dump_link: failed_transaction: terminate: 0 dump_link: failed_transaction: queue: 0 dump_link: failed_transaction: depth: 0 dump_td: failed_transaction: TD(0011d880): dump_td: failed_transaction: type: IN dump_td: failed_transaction: retries: 0 dump_td: failed_transaction: active: 0001 dump_td: failed_transaction: device_addr: 00 dump_td: failed_transaction: endpoint: 0 dump_td: failed_transaction: data_toggle: 1 dump_td: failed_transaction: max_transfer: 7ff dump_td: failed_transaction: actual: 0 dump_td: failed_transaction: link: dump_link: failed_transaction: addr: fe16d830 dump_link: failed_transaction: raw addr: 0000 dump_link: failed_transaction: terminate: 1 dump_link: failed_transaction: queue: 0 dump_link: failed_transaction: depth: 0 malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 blocks) configure_device: configure_device: set_address failed! poll_u_root_hub: poll_u_root_hub1 v=00001080 poll_usb1 i=0 poll_u_root_hub1 v=00001083 poll_u_root_hub2 v=00001083 poll_u_root_hub21 v=00001083 Connection on port d010 New USB device, setting address 2 uhci_control_msg: uhci_control_msg: request_type = 0 request = 5 wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free: 246520 bytes (1 blocks) dump_uhci: HCI at ffffd000 dump_td: failed_transaction: TD(0011d860): dump_td: failed_transaction: type: SETUP dump_td: failed_transaction: retries: 3 dump_td: failed_transaction: IOC dump_td: failed_transaction: active: 0001 dump_td: failed_transaction: device_addr: 00 dump_td: failed_transaction: endpoint: 0 dump_td: failed_transaction: data_toggle: 0 dump_td: failed_transaction: max_transfer: 7 dump_td: failed_transaction: actual: 0 dump_td: failed_transaction: link: dump_link: failed_transaction: addr: 0011d880 dump_link: failed_transaction: raw addr: 1fb0050 dump_link: failed_transaction: terminate: 0 dump_link: failed_transaction: queue: 0 dump_link: failed_transaction: depth: 0 dump_td: failed_transaction: TD(0011d880): dump_td: failed_transaction: type: IN dump_td: failed_transaction: retries: 0 dump_td: failed_transaction: active: 0001 dump_td: failed_transaction: device_addr: 00 dump_td: failed_transaction: endpoint: 0 dump_td: failed_transaction: data_toggle: 1 dump_td: failed_transaction: max_transfer: 7ff dump_td: failed_transaction: actual: 0 dump_td: failed_transaction: link: dump_link: failed_transaction: addr: fe16d830 dump_link: failed_transaction: raw addr: 0000 dump_link: failed_transaction: terminate: 1 dump_link: failed_transaction: queue: 0 dump_link: failed_transaction: depth: 0 malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes (1 blocks) configure_device: configure_device: set_address failed! (...repeats...) Thanks again! -- Al ----- End forwarded message ----- -- 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/

2 1

[LinuxBIOS] EPIA-MII RL5C476 CF and Linux
by Peter Stuge 07 Sep '06

07 Sep '06

southbridge/ricoh/rl5c476/rl5c476.c configures the CF slot to use io ports 0x1e0 through 0x1ef. There are some comments in the file explaining that this is done because "the pcmcia package within Linux then could not re-initialise the device as it tried to take control of it." but maybe this has changed now? When forcing the ide driver to look in the right place (ide2=0x1e0,0x1ec,5) it does indeed find the CF but it seems that the pccard code takes over later on since it notices that a card is inserted in slot 1. Trying to open /dev/hde once the system has booted also fails. (I'm running off NFS root for now.) Where do we want to go with this? The common case is likely a CF memory card, but on the other hand we want to support any CF device that Linux can handle in the slot. Treating the CF slot as a PCMCIA slot appears to require an initrd, which I'd like to avoid if possible. (My kernel has ide-cs, but it doesn't pick up the CF card even though pccard reports it is inserted.) Treating the CF slot as an IDE drive will work for LB, FILO and kernel when booting off of a CF card, but is useless for people wanting to use some other CF device. Is the problem really that I haven't set up PCMCIA properly in my kernel? (I would expect ide-cs to attach to the card when pccard says there's something in the slot?) Shouldn't this happen by way of the pccardd kernel thread? I really don't want an initrd with pcmcia-cs just for this.. //Peter

1 0

[LinuxBIOS] RE : Re: VGA bios and i/o access for powerpc
by jean-francois simon 07 Sep '06

07 Sep '06

Hi, Maybe there is a way to do without the emulation layer altogether: Since in our case we use PCI graphics, I can record all the PCI cycles made by the VGA BIOS to the graphic card on a BIOS based system (using a PCI analyser), put them into a listing, run a perl script on it and include them in the firmware of the non BIOS system....an redo the process whenever we need to use a different graphic which doesn't happen very often -jf simon I think a sure way is to record all the PCI cycles generated by the VGA BIOS jean-francois simon <jfaslist(a)yahoo.fr> a écrit : Those legacy IO ports are NOT necessary mapped to the PCI IO address. Some VGA card does and some others come with some kind of remapping or offset. Your system chipset should have a way to map legacy VGA IO ports to memory address. You have to read the doc to the PPC chipset carefully to find it out. I have read the chipset doc and there is no such VGA support. But could you plse explain more on the different ways for VGA cards to map the VGA registers? Since the registers are located on a PCI agent (the graphic card), there must be a way to access them by generating PCI cycles? Thanks -jf simon --------------------------------- Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.

4 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot September 2006