Hi,
the coreboot wiki still suggests to use ADLO for booting Windows and does not mention the usability of SeaBIOS with Windows at all. I tried to add a bit of information, but since I don't have access to any coreboot machine right now, the info I can add is pretty limited.
Could someone who uses SeaBIOS please do a wiki search on ADLO and Windows and mention SeaBIOS everywhere as preferred way to get Windows running?
Thanks.
Regards, Carl-Daniel
I am struggled to run windows on my EPIA-ML mainboard. And I have read the wiki about coreboot+ADLO, and still trying.I also read a mail in this maillist that a guy have run windows xp with SeaBIOS+ coreboot on a EPIA mainboard. But Contrast to ADLO, there is very few information about SeaBIOS except source code.
2009/1/21 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Hi,
the coreboot wiki still suggests to use ADLO for booting Windows and does not mention the usability of SeaBIOS with Windows at all. I tried to add a bit of information, but since I don't have access to any coreboot machine right now, the info I can add is pretty limited.
Could someone who uses SeaBIOS please do a wiki search on ADLO and Windows and mention SeaBIOS everywhere as preferred way to get Windows running?
Thanks.
Regards, Carl-Daniel
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Check the mail list from yesterday and look for the thread "Coreboot patches for v2 with SeaBIOS" .
A patch is being worked on and the wiki will be updated soon.
-Baro
Yunchuan Qin wrote:
I am struggled to run windows on my EPIA-ML mainboard. And I have read the wiki about coreboot+ADLO, and still trying. I also read a mail in this maillist that a guy have run windows xp with SeaBIOS+ coreboot on a EPIA mainboard. But Contrast to ADLO, there is very few information about SeaBIOS except source code.
2009/1/21 Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net mailto:c-d.hailfinger.devel.2006@gmx.net>
Hi, the coreboot wiki still suggests to use ADLO for booting Windows and does not mention the usability of SeaBIOS with Windows at all. I tried to add a bit of information, but since I don't have access to any coreboot machine right now, the info I can add is pretty limited. Could someone who uses SeaBIOS please do a wiki search on ADLO and Windows and mention SeaBIOS everywhere as preferred way to get Windows running? Thanks. Regards, Carl-Daniel -- http://www.hailfinger.org/ -- coreboot mailing list: coreboot@coreboot.org <mailto:coreboot@coreboot.org> http://www.coreboot.org/mailman/listinfo/coreboot
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Hello,
Yunchuan Qin wrote:
But Contrast to ADLO, there is very few information about SeaBIOS except source code.
http://www.coreboot.org/SeaBIOS has some limited information.
http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108 can be downloaded and used as payload in coreboot, and it will make the system work very similar (in theory) to when using a factory BIOS.
If coreboot has ACPI tables for the board some changes to coreboot source code may still be required, but as Bari pointed out work is being done to make using SeaBIOS even easier to use.
//Peter
Yes, I have downloadded bios.bin.elf-20081108-viavgahttp://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108-viavga directly from .http://linuxtogo.org/~kevin/SeaBIOS.http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108 But I downloaded the source code from git tree but compiled with errors!
Compiling whole program out/ccode.16.s In file included from src/util.c:8: src/bregs.h:98: error: conflicting types for '__set_fail' src/output.c:301: error: previous definition of '__set_fail' was here src/bregs.h:99: error: conflicting types for '__set_code_fail' src/output.c:313: error: previous definition of '__set_code_fail' was here src/util.c:16: error: conflicting types for 'call16' src/util.h:78: error: previous declaration of 'call16' was here src/util.c:30: error: conflicting types for 'call16big' src/util.h:79: error: previous declaration of 'call16big' was here src/util.c:44: error: conflicting types for '__call16_int' src/util.h:80: error: previous declaration of '__call16_int' was here In file included from src/floppy.c:15: src/bregs.h:98: error: conflicting types for '__set_fail' src/bregs.h:98: error: previous declaration of '__set_fail' was here src/bregs.h:99: error: conflicting types for '__set_code_fail' src/bregs.h:99: error: previous declaration of '__set_code_fail' was here In file included from src/misc.c:8: src/bregs.h:98: error: conflicting types for '__set_fail' src/bregs.h:98: error: previous declaration of '__set_fail' was here src/bregs.h:99: error: conflicting types for '__set_code_fail' src/bregs.h:99: error: previous declaration of '__set_code_fail' was here In file included from src/misc.c:10:
2009/1/23 Peter Stuge peter@stuge.se
Hello,
Yunchuan Qin wrote:
But Contrast to ADLO, there is very few information about SeaBIOS except source code.
http://www.coreboot.org/SeaBIOS has some limited information.
http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108 can be downloaded and used as payload in coreboot, and it will make the system work very similar (in theory) to when using a factory BIOS.
If coreboot has ACPI tables for the board some changes to coreboot source code may still be required, but as Bari pointed out work is being done to make using SeaBIOS even easier to use.
//Peter
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Fri, Jan 23, 2009 at 02:33:50PM +0800, Yunchuan Qin wrote:
Yes, I have downloadded bios.bin.elf-20081108-viavgahttp://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108-viavga directly from .http://linuxtogo.org/~kevin/SeaBIOS.http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-20081108 But I downloaded the source code from git tree but compiled with errors!
Compiling whole program out/ccode.16.s In file included from src/util.c:8: src/bregs.h:98: error: conflicting types for '__set_fail' src/output.c:301: error: previous definition of '__set_fail' was here
You have an older version of gcc. You need to build with:
make AVOIDCOMBINE=1
-Kevin
On Sat, Jan 24, 2009 at 11:26:59PM -0500, Kevin O'Connor wrote:
On Fri, Jan 23, 2009 at 02:33:50PM +0800, Yunchuan Qin wrote:
Compiling whole program out/ccode.16.s In file included from src/util.c:8: src/bregs.h:98: error: conflicting types for '__set_fail' src/output.c:301: error: previous definition of '__set_fail' was here
You have an older version of gcc. You need to build with:
make AVOIDCOMBINE=1
Since this is so common, I enhanced the build to autodetect the need for AVOIDCOMBINE. With the latest git, everyone should be able to just run "make".
-Kevin
-
bari -
Carl-Daniel Hailfinger -
Kevin O'Connor -
Peter Stuge -
Yunchuan Qin