coreboot

coreboot@coreboot.org

39717 discussions

[LinuxBIOS] Public request for a LinuxBIOS for VMware
by Borg No. One 08 Jan '06

08 Jan '06

Hi. 1.) Is there someone who + already built a LinuxBIOS/OpenBIOS for VMware? + is interested in building a LinuxBIOS/OpenBIOS for VMware? then please let the LinuxBIOS/OpenBIOS community and me know about your work. 2.) If you think: "How to use 3rd party / modified BIOS in VMware" after reading the question(s) above, then you should check following links: http://www.vmware.com/community/message.jspa?messageID=103265#103265 http://www.vmware.com/community/thread.jspa?threadID=28149&tstart=0 http://www.wimsbios.com/phpBB2/viewtopic.php?p=33730& http://vmware.itst.org/viewtopic.php?p=10881 http://www.google.de/search?q=bios440 -- DSL-Aktion wegen gro�er Nachfrage bis 28.2.2006 verl�ngert: GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl

3 2

Re: [LinuxBIOS] Inclusion of x86_64 memorize ioapic at bootup patch
by yhlu 08 Jan '06

08 Jan '06

does stefan put the mptable in first 1K? good way is put mptable 0xf0000:0x100000. YH On 1/7/06, Eric W. Biederman <ebiederm(a)xmission.com> wrote: > yhlu <yhlu.kernel(a)gmail.com> writes: > > > MPTABLE in LinuxBIOS is put from 0x20, if the system has too many cpu > > and devices (slots) the mptable will get bigger than 0x464, so it > > will use 0x40:67.... > > Then you or someone moved it. The base in low memory was originally > at 0x500, to avoid just these kinds of problems. > > > We need to put mptable to [0xf0000:0x100000] together with acpi > > tables. > > Or move it up a few bytes. > > > and if it is bigger than 64k, then we have to put it on special > > postion ...from 1K, and pass the posstion of mptable to the kernel via > > command line. > > > > I will update the code in LinuxBIOS. > > Thanks. It is always a good idea not to assign legacy regions of the > address space new meanings. > > Eric > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >

2 1

Re: [LinuxBIOS] tyan s2881 - partial success (update)
by Lu, Yinghai 06 Jan '06

06 Jan '06

Where is the driver module for MD, is it in initrd.img? YH -----Original Message----- From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Ward Vandewege Sent: Friday, January 06, 2006 12:46 PM To: LinuxBIOS Subject: Re: [LinuxBIOS] tyan s2881 - partial success (update) On Fri, Jan 06, 2006 at 10:24:26AM -0800, Lu, Yinghai wrote: > I'm thinking the way that you can use > 1. use LinuxBIOS to boot tiny kernel > 2. use RAID5 support in Tiny Kernel and kexec to boot the final kernel. > > I wonder if the SW RAID access in FILO is a problem.... I'm not sure why FILO would care. I now boot off (a drive of) a RAID1 partition, which is a perfectly normal drive partition as far as FILO is concerned. When the kernel is loaded, it has the sw-raid drivers and hence it can deal with the RAID5 array. Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator -- LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

Re: [LinuxBIOS] tyan s2881 - partial success (update)
by Lu, Yinghai 06 Jan '06

06 Jan '06

I'm thinking the way that you can use 1. use LinuxBIOS to boot tiny kernel 2. use RAID5 support in Tiny Kernel and kexec to boot the final kernel. I wonder if the SW RAID access in FILO is a problem.... YH -----Original Message----- From: linuxbios-bounces(a)openbios.org [mailto:linuxbios-bounces@openbios.org] On Behalf Of Ward Vandewege Sent: Friday, January 06, 2006 7:50 AM To: LinuxBIOS Subject: Re: [LinuxBIOS] tyan s2881 - partial success (update) On Tue, Jan 03, 2006 at 04:50:39PM -0800, Lu, Yinghai wrote: > Can you try with single HD instead of RAID5? I haven't tried that yet, but I just tried after having the raid array rebuilt running the proprietary BIOS. The serial log is attached. It took longer now to crash, just as I observed the first time I succesfully booted LinuxBIOS. I got a login prompt and things worked fine for a few minutes. After that, the same thing: serial log shows that the fallback image is being restarted, and the machine just hangs. In other words, heavy disk activity (sw-raid5 rebuilding) seems to trigger the crashes more quickly than otherwise. Thanks, Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

2 1

Re: [LinuxBIOS] Inclusion of x86_64 memorize ioapic at bootup patch
by Yinghai Lu 06 Jan '06

06 Jan '06

the patch is good. I tried LinuxBIOS with kexec. without this patch: I need to disable acpi in kernel. otherwise the kernel with acpi support can boot the second kernel, but the second kernel will hang after time.c: Using 14.318180 MHz HPET timer. time.c: Detected 2197.663 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Memory: 1009152k/1048576k available (2967k kernel code, 39036k reserved, 1186k ) YH On 1/2/06, Vivek Goyal <vgoyal(a)in.ibm.com> wrote: > Hi Andi, > > Can you please include the following patch. This patch has already been pushed > by Andrew. > > http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.1… > > This patch is regarding remembering at boot up time where i8259 is connected > and restore the APIC settings back during kexec boot or kdump boot. This > enables getting timer interrupts in new kernel in legacy mode. > > This patch is needed to make kexec and kdump work on some systems, > especially opteron boxes. Otherwise the second kernel does not receive > timer interrupts during early boot hence hangs. > > I understand, that you are inclined towards remembering all the APIC states > and simply restore it back instead of putting hooks. This will work > well for kexec but not for kdump because in kdump system can crash on > non-boot cpu. > > Restoring BIOS APIC state can make sure that BIOS designated boot cpu will > always be able to see timer interrupts in legacy mode but same does not > hold good if new kernel boots on some other cpu as is the case with kdump. > > In case of kexec boot, we relocate to boot cpu but in case of kdump we > don't because it was suggested that in some extreme cases of crash, boot cpu > might not respond even to NMI and relocation to boot cpu will not be > possible. > > Can you please re-consider this patch for inclusion. > > Thanks > Vivek > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >

5 8

Re: [LinuxBIOS] tyan s2881 - partial success (update)
by Lu, Yinghai 06 Jan '06

06 Jan '06

Can you try with single HD instead of RAID5? YH

2 1

[LinuxBIOS] x86_64: calibrate_delay_direct and apic id lift for BSP
by Yinghai Lu 06 Jan '06

06 Jan '06

andi, I tried to lift apic id in LinuxBIOS for all cpus after 0x10. When using MB with AMD8111, the jiffies was not moving. So it is locked at calibrate_delay_direct... but MB with Nvidia ck804, jiffies is moving. If I don't change BSP apic id ( keep it to 0), It changes.... I have no idea how the jiffies changes, there is another thread change it....? YH Memory: 508000k/524288k available (3146k kernel code, 15900k reserved, 1160k data, 296k init) calibrate_delay_direct i=0 calibrate_delay_direct start_jiffies=fffedb08 calibrate_delay_direct 1 jiffies=fffedb08 calibrate_delay_direct 1 jiffies=fffedb08 calibrate_delay_direct 1 jiffies=fffedb08 calibrate_delay_direct 1 jiffies=fffedb08

3 2

[LinuxBIOS] Support for the EBC3610-f
by Adam Talbot 05 Jan '06

05 Jan '06

Is there any support for the EBC3610-f http://www.bcmcom.com/bcm_product_ebc3610f.htm I see that linuxbos supports the VT8601North bridge. How close it that to the VT8606? -Adam Talbot

1 0

Re: [LinuxBIOS] Tyan Tiger 100 S1832
by Richard Smith 05 Jan '06

05 Jan '06

> Thanks for the datasheet. On my Tyan S1832 board I can report that > the chip says > "PC87309-IBW/VLJ" > On my system: > dmesg -s 1000000 | grep PC87 > gives > FDC 0 is a National Semiconductor PC87306 > > I'm assuming that Linux is incorrectly detecting the chipset > but it's close enough to the 309 that it still works. A lot of the NS superIO's are very similar. The cases I've seen so far are just addition/subtraction of all the "special" features. Like fan control, power control stuff, special purpose gpio. The FDC between the 2 may be identical. > > sides, pins will be pretty close together. Willlook similar to this: > > http://www.topline.tv/qfp.html > > Found it... looked exactly as you described. > > > I can't go past 40 or it locks and there aren't any newer updates for my > > MB. > > I assume it's a different one and not a S1832? Yeah. It just has a 440bx chipset on it. > > An additional board would be pretty much a requirement for doing thedev > > work. You will need some method of programming the flash chips aswell. > > Either a programmer/ bios savior or ZIF socket so you can dohotswap > > programming. --Richard A. Smith > > A BIOS savior sounds like a good insurance in any case! I'll try to find > a duplicate MB. Good choice. The only thing better than a bios savior is a ROM emulator but it's lots more expensive. Make sure when you order your replacement flash that its supported by flashrom. Most are but check to make sure. You don't have to get the exact brand of flash thats in the board since the factory part may be hard to find. Only the size and speed (and supply voltage of course) needs to match. If you have any doubts about what chips will work just post up the part number (The one _under_ the sticker) on your bios chip and we should be able to cross it for you. -- Richard A. Smith

1 0

[LinuxBIOS] Tyan Tiger 100 S1832
by Mark Longridge 04 Jan '06

04 Jan '06

Hi folks, I've heard interesting things about linux bios so I figured I'd ask about my motherboard. I have a Tyan Tiger 100 S1832 board with two P3 550 cpus. Some specs: ·Intel 440BX AGPset. ·Intel PIIX4e controller. ·National 309 Super I/O chipset. Guess it's pretty old but I'd still like to try to put a linux bios on it. I have a pdf of the manual so if there's any other info needed please let me know. Thanks, Mark

2 2

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