coreboot September 2004

coreboot@coreboot.org

41 participants
123 discussions

epia-m VGA bios update
by Trellix78＠aol.com 03 Sep '04

03 Sep '04

I am still trying to get VGA output on an epia-M10000. I've tried many configurations and none actually work. Here's a part of the BIOS output log: Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.0.0 Thu Sep 2 21:09:55 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 INSTALL REAL-MODE IDT DO THE VGA BIOS found VGA: vid=1106, did=3122 write_protect_vgabios 0x55 0xaa 0x7d 0xe9 0x26 0x7f 0x5e 0x1b 0xfa 0xf9 0xf4 0x82 0x0 0x0 0x0 0x0 bus/devfn = 0x100 biosint: # 0x15, eax 0x5f00 ebx 0x100 ecx 0x100 edx 0x12 biosint: ebp 0x1191c esp 0xff2 edi 0xd96c esi 0x12230 biosint: ip 0x637f cs 0xc000 flags 0x46 biosint: # 0x1a, eax 0xb108 ebx 0x0 ecx 0x0 edx 0x3d5 biosint: ebp 0x1191c esp 0xfcc edi 0xf6 esi 0x155eb biosint: ip 0x40da cs 0xc000 flags 0x46 0xb108: bus 0 devfn 0x0 reg 0xf6 val 0x3 biosint: # 0x15, eax 0x5f02 ebx 0x100 ecx 0x101 edx 0x3d5 biosint: ebp 0x1191c esp 0xfb8 edi 0x44 esi 0x155eb biosint: ip 0x63cb cs 0xc000 flags 0x46 biosint: # 0x15, eax 0x5f02 ebx 0x100 ecx 0x101 edx 0x3d5 biosint: ebp 0x1191c esp 0xfb8 edi 0x44 esi 0x155eb biosint: ip 0x63cb cs 0xc000 flags 0x46 biosint: # 0x15, eax 0x5f02 ebx 0x100 ecx 0x101 edx 0x3d5 biosint: ebp 0x1191c esp 0xfb8 edi 0x44 esi 0x155eb biosint: ip 0x63cb cs 0xc000 flags 0x46 biosint: # 0x15, eax 0x5f0f ebx 0x100 ecx 0x100 edx 0x3d5 biosint: ebp 0x1191c esp 0xfee edi 0x44 esi 0x12230 biosint: ip 0x647e cs 0xc000 flags 0x2 biosint: # 0x15, eax 0x5f02 ebx 0x0 ecx 0x1 edx 0x0 biosint: ebp 0x1191c esp 0xfdc edi 0x44 esi 0x12230 biosint: ip 0x63cb cs 0xc000 flags 0x46 biosint: # 0xff, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0 biosint: ebp 0x10fca esp 0xfbe edi 0xb9f0 esi 0x1010a biosint: ip 0x3333 cs 0xc000 flags 0x246 biosint: Unsupport int #0xff Checking IRQ routing tables... /home/dhillman/freebios-modified/src/arch/i386/lib/pirq_routing.c: 30:check_pirq_routing_table() - irq_routing_table located at: 0x00009360 done. Copying IRQ routing tables to 0xf0000...done. Verifing priq routing tables copy at 0xf0000...failed Wrote linuxbios table at: 00000500 - 0000066c checksum e855 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 ------------------------------------------- What is that unsupport int 0xff? That's the only unusual thing that I see. It boots all the way to a login prompt on the serial port but nothing shows up on the monitor. It feels like I'm almost there.

1 0

RE: use ramdisk as root file system
by Trellix78＠aol.com 03 Sep '04

03 Sep '04

Here's a step-by-step way to do an initial ramdisk: Much of this is from memory an bits of notes. I'm assuming that the elfboot system is being used, along with kernel 2.4 or greater. The way I did it is to have the boot system interrupted in the ramdisk without ever getting to init, but it's simple to go all the way using the full init or the busybox version. Ok, here's how to build the ramdisk: 1. enable ramdisk and initial ramdisk support in the kernel 2. at the prompt, type (without quotes) "#>dd if=/dev/zero of=initrd bs=1k count=8000" that'll build an 8 megabyte ramdisk so substitute 8000 for the needed size 3. build the filesystem using: "#>/sbin/mke2fs -F -m0 initrd" 4. the file can then be mounted by typing "#>mount -t ext2 -o loop initrd /mnt/initrd" Make sure /mnt/initrd exists. 5. copy all needed files to /mnt/initrd The next part can be done a couple of different ways. One way is to have a script called linuxrc (or some other) in the root filesystem of initrd that sets everything up and then drops to a shell. Another way is to have init in the usual place, with /etc/inittab set to run a setup script, along with agetty to monitor the serial port. One other way is to use busybox's init. You can get an automatic login that way by just starting a shell on the console by having this in inittab: "ttyS0::respawn:/bin/sh". Busybox init can also run without an /etc/inittab file. It'll automatically detect that the console is on the serial port and put a shell there. Now, to booting with etherboot. Serial console support needs to be compiled into the kernel. I used mkelfImage from the freebios util directory to make a combined kernel and initrd elf image. Here's the actual command: #> mkelfImage --kernel=<path-to-kernel> --ramdisk=<path-to-initrd> --output=<output-file-name> --command-line="root=0100 rw init=/linuxrc console=ttyS0,115200n8" The rw is there to enable initrd to be read/write. The init=/linuxrc should be taken out if /sbin/init is to be used. I used the major and minor numbers but root=/dev/ram0 can be used. Make sure ACPI is turned off the first time around. That should work.

1 0

RE: use ramdisk as root file system
by zhu shi song 03 Sep '04

03 Sep '04

I've made one initrd to try. But when executing at /sbin/init, linux halts. Output log is as following: RAMDISK: Compressed image found at block 0 Freeing initrd memory: 3687k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 64k freed Warning: unable to open an initial console. [end] By the way, using initramfs, can I have rw root fs on ramdisk? tks zhu --- Dave Aubin <daubin(a)actuality-systems.com> wrote: > Here is a good way to do initramfs. Initramfs > becomes part of the > kernel and > Then executes it's programs in user space which > makes things nice. But > there > Are other advantages as well. Feel free to read > these while on the > thrown;) > > http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html > http://seclists.org/lists/linux-kernel/2004/Jul/0154.html > http://lwn.net/Articles/14776/ > > For my needs initramfs is a life saver, but initrd > is good too. Heck > you could > Go NFS if you wish. > > Enjoy, > Dave:) > > > > -----Original Message----- > From: linuxbios-admin(a)clustermatic.org > [mailto:linuxbios-admin@clustermatic.org] On Behalf > Of zhu shi song > Sent: Friday, September 03, 2004 6:53 AM > To: linuxbios(a)clustermatic.org > Subject: use ramdisk as root file system > > I now can boot my QDIA6T(vt8601/vt82c686b) MB using > hard disk as root > file system though there is no vga turned on. But I > don't need HD. I > hope I can mount RAMDisk as my root filesystem which > can be read and > written. How should I do to start such work? I > have read some material > about initrd but I don't understand it very clearly. > > tks > zhu > > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - 100MB free storage! > http://promotions.yahoo.com/new_mail > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

3 3

RE: use ramdisk as root file system
by Dave Aubin 03 Sep '04

03 Sep '04

Pass the following in to your kernel parameter list console=tty0, console=ttyS0,115200 Then connect a serial line to your serial port and to another machine and Look at the serial output with hyperterm or something. I didn't want to Do this at first, but it has made my life sooooo much easier. If you can't Do this, consider also that 2.6 kernel has netconsole. Netconsole can Send the same serial information over the network so you can see what is Failing. -----Original Message----- From: zhu shi song [mailto:zhushisongzhu@yahoo.com] Sent: Friday, September 03, 2004 9:25 AM To: Dave Aubin; linuxbios(a)clustermatic.org Subject: RE: use ramdisk as root file system I've made one initrd to try. But when executing at /sbin/init, linux halts. Output log is as following: RAMDISK: Compressed image found at block 0 Freeing initrd memory: 3687k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 64k freed Warning: unable to open an initial console. [end] By the way, using initramfs, can I have rw root fs on ramdisk? tks zhu --- Dave Aubin <daubin(a)actuality-systems.com> wrote: > Here is a good way to do initramfs. Initramfs becomes part of the > kernel and Then executes it's programs in user space which makes > things nice. But there Are other advantages as well. Feel free to > read these while on the > thrown;) > > http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html > http://seclists.org/lists/linux-kernel/2004/Jul/0154.html > http://lwn.net/Articles/14776/ > > For my needs initramfs is a life saver, but initrd is good too. Heck > you could Go NFS if you wish. > > Enjoy, > Dave:) > > > > -----Original Message----- > From: linuxbios-admin(a)clustermatic.org > [mailto:linuxbios-admin@clustermatic.org] On Behalf Of zhu shi song > Sent: Friday, September 03, 2004 6:53 AM > To: linuxbios(a)clustermatic.org > Subject: use ramdisk as root file system > > I now can boot my QDIA6T(vt8601/vt82c686b) MB using hard disk as root > file system though there is no vga turned on. But I don't need HD. I > hope I can mount RAMDisk as my root filesystem which can be read and > written. How should I do to start such work? I have read some > material about initrd but I don't understand it very clearly. > > tks > zhu > > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - 100MB free storage! > http://promotions.yahoo.com/new_mail > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

1 0

RE: use ramdisk as root file system
by zhu shi song 03 Sep '04

03 Sep '04

initramfs can only be supported under 2.6 kernel. I'm using kernel 2.4. --- Dave Aubin <daubin(a)actuality-systems.com> wrote: > Here is a good way to do initramfs. Initramfs > becomes part of the > kernel and > Then executes it's programs in user space which > makes things nice. But > there > Are other advantages as well. Feel free to read > these while on the > thrown;) > > http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html > http://seclists.org/lists/linux-kernel/2004/Jul/0154.html > http://lwn.net/Articles/14776/ > > For my needs initramfs is a life saver, but initrd > is good too. Heck > you could > Go NFS if you wish. > > Enjoy, > Dave:) > > > > -----Original Message----- > From: linuxbios-admin(a)clustermatic.org > [mailto:linuxbios-admin@clustermatic.org] On Behalf > Of zhu shi song > Sent: Friday, September 03, 2004 6:53 AM > To: linuxbios(a)clustermatic.org > Subject: use ramdisk as root file system > > I now can boot my QDIA6T(vt8601/vt82c686b) MB using > hard disk as root > file system though there is no vga turned on. But I > don't need HD. I > hope I can mount RAMDisk as my root filesystem which > can be read and > written. How should I do to start such work? I > have read some material > about initrd but I don't understand it very clearly. > > tks > zhu > > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - 100MB free storage! > http://promotions.yahoo.com/new_mail > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

1 0

RE: use ramdisk as root file system
by Dave Aubin 03 Sep '04

03 Sep '04

Here is a good way to do initramfs. Initramfs becomes part of the kernel and Then executes it's programs in user space which makes things nice. But there Are other advantages as well. Feel free to read these while on the thrown;) http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html http://seclists.org/lists/linux-kernel/2004/Jul/0154.html http://lwn.net/Articles/14776/ For my needs initramfs is a life saver, but initrd is good too. Heck you could Go NFS if you wish. Enjoy, Dave:) -----Original Message----- From: linuxbios-admin(a)clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of zhu shi song Sent: Friday, September 03, 2004 6:53 AM To: linuxbios(a)clustermatic.org Subject: use ramdisk as root file system I now can boot my QDIA6T(vt8601/vt82c686b) MB using hard disk as root file system though there is no vga turned on. But I don't need HD. I hope I can mount RAMDisk as my root filesystem which can be read and written. How should I do to start such work? I have read some material about initrd but I don't understand it very clearly. tks zhu __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

use ramdisk as root file system
by zhu shi song 03 Sep '04

03 Sep '04

I now can boot my QDIA6T(vt8601/vt82c686b) MB using hard disk as root file system though there is no vga turned on. But I don't need HD. I hope I can mount RAMDisk as my root filesystem which can be read and written. How should I do to start such work? I have read some material about initrd but I don't understand it very clearly. tks zhu __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail

2 1

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

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 2004