coreboot

coreboot@coreboot.org

3 participants
39562 discussions

EPIA-800 and VGA post LinuxBIOS init
by David Hendricks 17 Sep '03

17 Sep '03

I have successfully managed to boot an EPIA-800 board to a usable state using Steve Gehlback's VGA configuration, Etherboot, and a vanilla FreeBIOS tree. VGA comes up reliably every time I boot. However VGA output only appears until Etherboot jumps to my phase 1 beoboot image. What must be done to have VGA output after Etherboot loads my image?

2 1

LinuxBios + EPIA5000 + Win2k Bootloader + HD + VGA
by Sven Lübke 17 Sep '03

17 Sep '03

Hi! I want to install LinuxBIOS on my EPIA5000 in combination with an IDE-Harddisk. The harddisk contains a Win2k bootloader which boots LiLo or Win2k. The VGA port on the EPIA board should be enabled! Is that combination possible/up-to-date at all? Which setup has the fastest boottime? I tried to compile LinuxBIOS with ADLO and Bochs, cause I don't want to use etherboot, but for some reason the computer didn't boot. I read all the FAQs and the "How to" for EPIA mainboards but it's not working anyway! Is ADLO able to boot the Win2k loader? Is someone using the same setup and has a config-file for me? Can someone help me? My goal is to boot Linux as fast as possible and sometimes (if I need it) switch to Win2k. Thank you for your help! Best regards, Sven

2 1

CVS not working, link to daily snapshot broken
by Dave Ashley 16 Sep '03

16 Sep '03

http://www.linuxbios.org/developer/download/index.html cvs [checkout aborted]: recv() from server cvs.freebios.sourceforge.net: EOF cvs [checkout aborted]: recv() from server cvs.freebios.sourceforge.net: Connection reset by peer http://cvs.sourceforge.net/cvstarballs/freebios-cvsroot.tar.gz Object not found! The requested URL was not found on this server. The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error. If you think this is a server error, please contact the webmaster Error 404

2 1

romcc fixes for AMD64
by Stefan Reinauer 16 Sep '03

16 Sep '03

Hi, with the attached fix romcc is able to compile all of auto.c for the freebios2 amd64 targets. To keep all changes clean and visible, they're encapsulated in ifdefs. Note: This fix alone does not make LinuxBIOS compile on AMD64 completely yet. GCC and ld need the -m32 in some places at least to compile everything. Is there any need in going 64bit for the LinuxBIOS C payload on Opteron? Since the kernel does long mode switching itself this should not be the case, but maybe there are different opinions. Next fail I saw after romcc passed auto.c was the following: /home/stepan/freebios2/src/superio/NSC/pc87360/superio.c:61: warning: `pnp_read_enable' defined but not used /tmp/ccLriZXb.s: Assembler messages: /tmp/ccLriZXb.s:243: Error: Incorrect register `%rdx' used with `l' suffix /tmp/ccLriZXb.s:245: Error: Incorrect register `%rdx' used with `l' suffix make: *** [superio.o] Error 1 Greetings, Stefan -- Architecture Team SuSE Linux AG

3 5

Re: extending "buildrom"
by YhLu 16 Sep '03

16 Sep '03

Optional offset is a good idea. But seem when We build normal or fallback image the offset are fixed at the time. For example: The LsiSCSIFW is 48k. and its final offset in ROM is 0. When building fallback image, I set ROM_SIZE is 512K, and fallback section size if 96K ( 32k+64k) so the offset is 512K-96K.The final offset in ROM should be 512K-96K. When building normal image, I set ROM_SIZE is 512K-48K. and normal section size is 512k-48k-96k, and the offset is 48K. The final offset in ROM should be 48K. So We only need to cat them all together, except We don't want normal you may need the optional offset. Regards YH. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年9月16日 7:25 收件人: Stefan Reinauer 抄送: YhLu; LinuxBIOS 主题: Re: extending "buildrom" On Tue, 16 Sep 2003, ron minnich wrote: > On Tue, 16 Sep 2003, Stefan Reinauer wrote: > > > * ron minnich <rminnich(a)lanl.gov> [030915 16:51]: > > > On Mon, 15 Sep 2003, Stefan Reinauer wrote: > > > > > > > buildrom <imagename.rom> > > > > size ROM_SIZE > > > > data ./lsiscsifw 65536 So the one change I'd make is to have an optional offset. data ./lsiscsifs 65536 image normal NORMAL_SIZE 0x20000 etc. This would be so that you could have non-contiguous data areas. ron

1 0

Re: extending "buildrom"
by YhLu 16 Sep '03

16 Sep '03

For s2880 that with LSI scsi FW and some other ATI onboad Server Mainboard may need us to put the FW or VGA ROM in the linuxbios.rom too. For s2880 I cat lsiscsifw, normal, and fallback together. -----邮件原件----- 发件人: Stefan Reinauer [mailto:stepan@suse.de] 发送时间: 2003年9月12日 10:05 收件人: LinuxBIOS 主题: extending "buildrom" Hi, to get used to the config tool, I wrote the attached little patch to change the buildrom command to allow specifying a filename of a rom file that is produced when building LinuxBIOS i.e. buildrom ROM_SIZE "normal" "fallback" changed to: buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" creating a linuxbios.rom file in the build target directory that consists of the 2 concatenated romimages "normal" and "fallback" This way it's now possible to build several roms with "buildrom" that take the specified "romimage"s that were built. This could i.e. be used to build several roms at once i.e. with different payloads in them. Is this ok to check in? -- Architecture Team SuSE Linux AG

3 5

[OT] Phoenix Developing DRM-Equipped BIOS
by Dale Harris 16 Sep '03

16 Sep '03

This isn't exactly on topic, but I thought it was interesting nonetheless. So with a mobo that would support this BIOS, could we still pop out the Phoenix BIOS and pop in a LinuxBIOS or FreeBIOS? http://www.extremetech.com/article2/0,3973,1237519,00.asp BIOS maker Phoenix Technologies said it is currently shopping a digital-rights-enabled BIOS system to top PC OEMs, the most aggressive use of DRM technology to date. Phoenix executives said Wednesday that they've developed a prototype version of its Core Management Environment (cME) using DRM technology in conjunction with Orbid Corp., a DRM technology provider. The software was designed to assist content providers to authenticate and track software moving from PC to PC. -- Dale Harris rodmur(a)maybe.org /.-)

9 20

Intel 865G
by dale_anderson＠paradise.net.nz 15 Sep '03

15 Sep '03

Hi All Have been watching for a while and hadnt seen any discussion on this one so I thought I'd ask :) Anyone working on the Intel 865G equiped boards atm ? I currently have a Gigabyte GA-8IG1000 in my possession and was wondering if anything in cvs atm , would have peliminary support ? Im assuming stuff like enabling hyperthreading etc is a wee way off , but as im running a celery it doesnt really worry me :) what are the chances like in getting something to work ? TIA Dale Anderson.

1 0

[Fwd: Re: 2.7 block ramblings (was Re: DMA for ide-scsi?)]
by Justin Cormack 15 Sep '03

15 Sep '03

This is from lkml. Can someone reply (and persuade Dell how broken their thought process is). Actually the whole thread about boot disk is odd. My usual problem with lilo and grub was trying to persuade them to install on something that wasnt the boot disk but was going to be. -----Forwarded Message----- From: Matt Domsch <Matt_Domsch(a)dell.com> To: Jeff Garzik <jgarzik(a)pobox.com> Cc: linux-kernel(a)vger.kernel.org Subject: Re: 2.7 block ramblings (was Re: DMA for ide-scsi?) Date: 13 Sep 2003 16:11:17 +1400 > Further, some sites may prefer block-level GUIDs to fs-level ones. > Sites using raw partitions instead of filesystems, for one. The EFI GUID Partition scheme (aka GPT aka CONFIG_EFI_PARTITION) stores a GUID in the disk label to define the whole disk, plus another per-partition GUID and per-partition label. So even if the file system doesn't have one, if you're using GPT, one *could* use those. I haven't hacked up mount to search for those though. If there's enough interest, I'll do so. Recall GPT is currently only used on ia64, though the code works fine on other arches including x86, and it's been decided (on l-k at least) that GPT will be the default disk label format for systems running 2.6.x kernels with disks >2TB, as the msdos label can't hold it. > The boot disk, OTOH, is tough. Right now, we just assume the > sysadmin knows what's he's doing, when he installs lilo or grub on a > disk. You care about the boot disk when installing lilo... maybe > there are similar situations too which I do not recall. As Alan > said, besides EDD (only on newer boxes) there's really nothing. EDD BIOSs are coming, slowly... 2 work today correctly, several more are "close but no cigar", it's all the rest that worry me. There's one more trick that's being used successfully, which I would like to add to the EDD code. That's "let BIOS help you out before installing". i.e. you boot into a FreeDOS environment, write a system-unique disk signature to the boot disk (int13 device 80h) "BOOT" or something - we've got 4 bytes available in the msdos label for it, then reboot and let Linux go grab the signature, store it, and like edd.o does, export it to userspace. Now from userspace one can see what Linux-named-disk has the signature you're looking for, and voila, you now solved it w/o needing EDD BIOSs. But it requires a non-Linux boot step somewhere in the install process. Thanks, Matt -- Matt Domsch Sr. Software Engineer, Lead Engineer Dell Linux Solutions www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com - 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

support for Epia or other Mini-ITX boards
by Michael Fenner 13 Sep '03

13 Sep '03

Hallo, want to set up a machine with LinuxBios - do not know which board to choose - I want to buy a new one and it has to be small. At the moment I have a FV24 with a VIA 1GHz processor. I'm looking into buying an Eipa, Epia-M or Epia-V board. The status page says that only the Eipa is fully supported - but I would prefer an Eipa-M or Eipa-V. Which one would you recommend if I want to install LinuxBios? Or do you have any other sugestions for a Mini-ITX board? Do you have something like a documentation for installing LinuxBios? Thanks for your help, Michael

2 1

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