coreboot

coreboot@coreboot.org

11 participants
39712 discussions

RE: elf for USB boot in FILO in Etherboot
by Dave Aubin 02 Sep '04

02 Sep '04

Here's is what I've found and made filo & elf work. I build with AMD64, 2.6.6 compiled under Suse 9.0, gcc 3.3.1. I build with mkelfImage also on Suse 9.0, Amd 64. There is a problem loading any mkelf image with an initrd. I don't think it has anything to do with the tools as I've tried An elf made with all 32 bit tools and an older compiler got the Same failure with the initrd portion. I suspect it is the elf Decompression in filo with a multipart built elf. I know mkelfImage with multipart works in etherboot, so I further think It is filo's elf reader. That said here's what I did to get around The problem. Don't use a kernel & initrd approach. Use a different early file system Approach. I use initramfs. It is one Big Fat Kernel (BFK). When I use this Approach it works for me. I hope this helps those who wish to use filo & etherboot. Thanks, Dave -----Original Message----- From: linuxbios-admin(a)clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of Yinghai Lu Sent: Thursday, September 02, 2004 12:37 PM To: 'ron minnich' Cc: 'LinuxBIOS' Subject: elf for USB boot in FILO in Etherboot I remember that some time ago, Miller met the problem with the use FILO and FILO in Etherboot to boot elf made by mkelfImage 2.5....from Kernel and Init. The kernel said that can not find the init. Yesterday I met the same problem under following configuration: Kernel: 2.6.8.1 compiled under Suse 9.1 AMD64 ( gcc 3.3.3). Used mkelfImage under Redhat 9 to produce the final elf. When I use 2.6.5, 2.6.6, 2.6.7 with Suse 9 compiler gcc 3.3.1, all work well. Miller seems have problem with 2.6.6 and Suse 9.1. So I guess there is some problem with gcc 3.3.3 in Suse 9. or there is some optimization for (EM86T) cause problem. Miller, Can you try to compile your kernel under Suse 9.? Regards YH _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

reset16.inc and 32bit reset vector
by Jeremy Jackson 02 Sep '04

02 Sep '04

. = 0x8; .code32 jmp protected_start .previous What in the world would use this? Is there am i386 CPU that starts in protected mode? -- Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net

3 4

testbios halt
by zhu shi song 02 Sep '04

02 Sep '04

I have made my ADIA6T MB (vt8601/vt82c686B) booting from linuxbios(freebios V1). I can't make vgabios work in linuxbios. So I try to use testbios to make VGA work. But testbios halt the MB. The output log is as following: [root@localhost /sbin]# ./testbios -s 65536 ./a6tvga.bios.bin running file ./a6tvga.bios.bin No base specified. defaulting to 0xc0000 No initial code segment specified. defaulting to 0xc000 No initial instruction pointer specified. defaulting to 0x0003 eax=0x9 ecx=0x8500 eflags=0x90 [halt linux] _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush

1 0

Re: VGA Problem about 440bx chipset
by Chiu Gerald 02 Sep '04

02 Sep '04

thanks,Richard! >Yes some PCI cards work. I've made several Assiliant 65550 and >69000 >based PCI cards work and some S3 based cards work. There are >reports of >some ATI cards working but I am still having problems getting my ATI >M1 >based card to work. My card is ATI,too.:( Maybe I need to look for another PCI card to try. > >Are you setting up the shadowing correctly? You have to setup the >shadowing in loader.s or bochs and the video bios never make it into >ram. The stock ADLO setup won't work on the 440bx. > >I've attached my loader.s which sets up the shadowing correctly. > Thanks,the shadow setting is correct ,and I debugged into rombios.c ,found that it halts when it run into vga bios and never return back. _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn

1 0

Firmware hub/ICH top block swap
by Jeremy Jackson 02 Sep '04

02 Sep '04

Has anyone pursued this feature of the i8xx series chipsets? Seems it could do what the Bios saviour does, even for boards with a soldered on flash chip. At least for the 810e, there is a "top block swap" feature: The FWH flash part is a 512kB (or more) part, of 8x (or more) 64kB blocks. The top block can be write protected separately via a jumper. The other blocks can also be collectively write protected by a jumper. The ICH (like a southbridge I guess) contains the CMOS batter-backed ram. One extra bit in CMOS can be set in the PCI config space of the ICH. The "top block swap" can be used for failsafe top or "boot" block updates to the FWH flash. The update utility first copies the top block to the block just below it, and verifies the flash operation. It then sets the top block swap bit. From this point on, if a flash operation to the top block fails, the power is lost, etc, the system will boot to the 2nd from top block, which presumably contains enough code to load the flash utility from some device (floppy/cdrom?) Once the update has completed successfully, the top block swap is disabled. I have verified this using setpci. On an IBM NetVista 6341-23U, it works in that the system fails to boot upon setting the bit, and clearing the CMOS restores the system to normal. The chipset docs also advertise a power-on strapping option for the ICH, but the system I tested had neither that or the write protect jumpers. ( It did have a recovery jumper, but that seems to just activate recovery mode in the top block's boot block code, not force a top block swap) I'm going to try using this as a way of trying out Linuxbios with a way to get back the vendor bios (the FWH is soldered on); flash linuxbios to the 2nd from top block, set the swap bit. If it breaks, clear CMOS, recover the vendor bios. BTW - does anyone have any working code to flash an ST M50FW0404 or an Intel 82802? Uniflash/devbios don't support the ST at least. -- Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net

2 2

DK8S2?
by Peter Buckingham 01 Sep '04

01 Sep '04

Hi, I've built my linuxbios.rom for Iwill's dk8s2. the only change i made was to the ROM_SIZE (i needed it to be 512k, not 1mb). i've plugged in the prom and a serial console set to 115200 bps. i don't actually see anything. what sort of output should i be seeing? i've tried turning up the debug level, but still see no output. does anyone have any experience with this board? thanks, peter

3 6

RE: Redirect your console to the network
by ron minnich 01 Sep '04

01 Sep '04

I'll try to find it. The other change I made was to turn it into a real device (which they may also have done) and have it not start sending output until the first open. This change was needed to ensure it would not try to use the network stack until it was actually there ... ron

2 1

RE: Redirect your console to the network
by Dave Aubin 01 Sep '04

01 Sep '04

How to get netconsole to work: 1. Build your 2.6 kernel with tg3 support AND netconsole as part of the kernel A. This is the easiest way, I couldn't do it via modules as I couldn't get the polling to work. 2. Pass in to the kernel as a parameter the netconsole information A. This will automatically send the console information to the destination address when eth0 is up. Doing this worked for me, but a little bit of a pain was involved. Hope this helped. Dave -----Original Message----- From: linuxbios-admin(a)clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of Dave Aubin Sent: Wednesday, September 01, 2004 3:12 PM To: ron minnich Cc: linuxbios(a)clustermatic.org Subject: RE: Redirect your console to the network Hey Ron, If your tool doesn't have to support polling can you please pass that on to me? That's one side effect of the netconsole tool. You need to have polling enabled in the Network driver. I've been having trouble getting that to fly actually. Thanks, Dave -----Original Message----- From: ron minnich [mailto:rminnich@lanl.gov] Sent: Wednesday, September 01, 2004 11:08 AM To: Dave Aubin Cc: linuxbios(a)clustermatic.org Subject: Re: Redirect your console to the network yes, we have used that off and on for a while. I hope they improved it to be a real module, but if not I have an iproved version here ... thanks for the pointer. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

epia-m vga cromwell bios
by Trellix78＠aol.com 01 Sep '04

01 Sep '04

This is actually 2 questions in one. I've been having some problems getting VGA to work on my epia-m board. I was able to get etherboot to load the kernel, etc, but when I made the recent changes for VGA, elfboot doesn't like what I did. I've included a capture of the serial output and my configuration file. I also was interested in doing something like the cromwell open-source bios for the Xbox, where vga is fully initialized from the start and a nice graphical screen can be set up to enable booting from etherboot, cd-rom or the hard disk via grub. My Xbox mod-chip is also 256kb, so I'm guessing it should work. Here's the serial port capture: LinuxBIOS-1.0.0 Thu Aug 26 13:21:59 EDT 2004 starting... 80 08 07 0d 0a 01 40 00 04 75 75 00 82 08 00 01 0e 04 0c 01 02 20 c0 a0 75 00 00 50 3c 50 2d 40 a0 a0 50 50 00 00 00 00 00 41 4b 34 32 75 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.0.0 Thu Aug 26 13:21:59 EDT 2004 booting... Finding PCI configuration type. PCI: Using configuration type 1 Scanning PCI bus...PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [1106/3123] PCI: 00:01.0 [1106/b091] PCI: 00:0d.0 [1106/3044] PCI: 00:10.0 [1106/3038] PCI: 00:10.1 [1106/3038] PCI: 00:10.2 [1106/3038] PCI: 00:10.3 [1106/3104] PCI: 00:11.0 [1106/3177] PCI: 00:11.1 [1106/0571] PCI: 00:11.5 [1106/3059] PCI: 00:12.0 [1106/3065] PCI: pci_scan_bus for bus 1 PCI: 01:00.0 [1106/3122] PCI: pci_scan_bus returning with max=01 PCI: pci_scan_bus returning with max=01 done Allocating PCI resources... PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it ASSIGN RESOURCES, bus 0 PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io PCI: 00:01.0 24 <- [0xf8000000 - 0xfbffffff] bus 1 prefmem PCI: 00:01.0 20 <- [0xfc000000 - 0xfcffffff] bus 1 mem ASSIGN RESOURCES, bus 1 PCI: 01:00.0 10 <- [0xf8000000 - 0xfbffffff] prefmem PCI: 01:00.0 14 <- [0xfc000000 - 0xfcffffff] mem ASSIGNED RESOURCES, bus 1 PCI: 00:0d.0 10 <- [0xfd000000 - 0xfd0007ff] mem PCI: 00:0d.0 14 <- [0x00001800 - 0x0000187f] io PCI: 00:10.0 20 <- [0x00001880 - 0x0000189f] io PCI: 00:10.1 20 <- [0x000018a0 - 0x000018bf] io PCI: 00:10.2 20 <- [0x000018c0 - 0x000018df] io PCI: 00:10.3 10 <- [0xfd001000 - 0xfd0010ff] mem PCI: 00:11.1 20 <- [0x000018e0 - 0x000018ef] io PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io PCI: 00:12.0 10 <- [0x00001400 - 0x000014ff] io PCI: 00:12.0 14 <- [0xfd002000 - 0xfd0020ff] mem ASSIGNED RESOURCES, bus 0 Allocating VGA resource done. Enabling PCI resourcess...PCI: 00:00.0 cmd <- 06 PCI: 00:01.0 cmd <- 07 PCI: 00:0d.0 cmd <- 83 PCI: 00:10.0 cmd <- 01 PCI: 00:10.1 cmd <- 01 PCI: 00:10.2 cmd <- 01 PCI: 00:10.3 cmd <- 02 PCI: 00:11.0 cmd <- 07 PCI: 00:11.1 cmd <- 07 PCI: 00:11.5 cmd <- 01 PCI: 00:12.0 cmd <- 83 PCI: 01:00.0 cmd <- 03 done. Initializing PCI devices... PCI devices initialized totalram: 96M Initializing CPU #0 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 64MB, type WB Setting variable MTRR 1, base: 64MB, range: 32MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs done. Max cpuid index : 1 Vendor ID : CentaurHauls Processor Type : 0x00 Processor Family : 0x06 Processor Model : 0x09 Processor Mask : 0x00 Processor Stepping : 0x01 Feature flags : 0x0380b135 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled Disabling local apic...done. CPU #0 Initialized Mainboard fixup Final mainboard fixup Southbridge fixup setting firewire Assigning IRQ 10 to 0:d.0 Readback = 10 setting usb Assigning IRQ 11 to 0:10.0 Readback = 11 Assigning IRQ 10 to 0:10.1 Readback = 10 Assigning IRQ 12 to 0:10.2 Readback = 12 Assigning IRQ 5 to 0:10.3 Readback = 5 setting vt8235 Assigning IRQ 5 to 0:11.1 Readback = 5 Assigning IRQ 12 to 0:11.5 Readback = 12 setting ethernet Assigning IRQ 11 to 0:12.0 Readback = 11 setting vga Assigning IRQ 11 to 1:0.0 Readback = 11 setting pci slot setting vt8235 slot Assigning IRQ 5 to 0:11.1 Readback = 5 Assigning IRQ 12 to 0:11.5 Readback = 12 Checking IRQ routing tables... /home/dhillman/freebios/src/arch/i386/lib/pirq_routing.c: 30:check_pirq_routing_table() - irq_routing_table located at: 0x00008c60 done. Copying IRQ routing tables to 0xf0000...done. Verifing priq routing tables copy at 0xf0000...failed Wrote linuxbios table at: 00000500 - 00000654 checksum d443 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 37:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Cannot Load ELF Image What should I be looking for if it's successful, besides the output on the monitor? Here's my config file: # # LinuxBIOS config file for: VIA epia-m mini-itx # target /home/dhillman/epia # via epia mainboard via/epia-m # Enable Serial Console for debugging option SERIAL_CONSOLE=1 option TTYS0_BAUD=115200 option DEFAULT_CONSOLE_LOGLEVEL=9 option DEBUG=1 # Use 256KB Standard Flash as Normal BIOS option RAMTEST=1 option USE_GENERIC_ROM=1 option STD_FLASH=1 option ROM_SIZE=262144 option ZKERNEL_START=0xfffd0000 # payload size = 192KB option PAYLOAD_SIZE=196608 # use ELF Loader to load Etherboot option USE_ELF_BOOT=1 # Use Etherboot as our payload #payload /home/dhillman/etherboot-5.0.8/src/bin32/via-rhine.ebi #payload /home/dhillman/epia/payload.adlo #payload /home/dhillman/epia/vga+eb.bin payload /home/dhillman/epia/vgabios.bin # for VGA support (optional) option HAVE_FRAMEBUFFER=1 option SMA_SIZE=8 option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1 option VGABIOS_START=0xfffe0000 #option VGABIOS_START=0xfff00000 addaction romimage dd if=vgabios.bin of=romimage bs=65536 seek=2 conv=sync conv=notrunc dir src/bioscall # end VGA support

1 0

RE: Redirect your console to the network
by Dave Aubin 01 Sep '04

01 Sep '04

Hey Ron, If your tool doesn't have to support polling can you please pass that on to me? That's one side effect of the netconsole tool. You need to have polling enabled in the Network driver. I've been having trouble getting that to fly actually. Thanks, Dave -----Original Message----- From: ron minnich [mailto:rminnich@lanl.gov] Sent: Wednesday, September 01, 2004 11:08 AM To: Dave Aubin Cc: linuxbios(a)clustermatic.org Subject: Re: Redirect your console to the network yes, we have used that off and on for a while. I hope they improved it to be a real module, but if not I have an iproved version here ... thanks for the pointer. ron

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