Hi,
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
The changes to seabios have been committed to the git repo. One can download it with:
git clone git://git.linuxtogo.org/home/kevin/seabios.git
The reason the install and boot failed before was due to the pcibios functions. The VIA vga card shows up on bus 1 on the epia-m. However, the pcibios functions only supported bus 0. The latest seabios git now supports pcibios calls on machines with more than 1 bus.
I still need to disable ACPI support in order to install winxp (hit the F7 key when asked about additional driver). This appears to be due to incomplete ACPI support in coreboot-v2 for the epia-m.
To enable coreboot support in seabios, modify the file src/config.h and change CONFIG_COREBOOT to 1. You'll also likely want to change CONFIG_DEBUG_LEVEL and CONFIG_DEBUG_SERIAL. Finally, make sure CONFIG_PCI_BUS_COUNT is correct for your machine.
There is still plenty of stuff to do, but I think this is an important step forward.
-Kevin
Hi Kevin,
On 17.08.2008 18:24, Kevin O'Connor wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
This is absolutely awesome! I hope others with an Epia-M can reproduce the success.
Regards, Carl-Daniel
On Sun, Aug 17, 2008 at 07:13:54PM +0200, Carl-Daniel Hailfinger wrote:
Hi Kevin,
On 17.08.2008 18:24, Kevin O'Connor wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
This is absolutely awesome! I hope others with an Epia-M can reproduce the success.
Seabios isn't epia specific, so I'm hoping others will be able to replicate on other platforms. :-)
-Kevin
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
YAHOO!!! Great work Kevin:-)
On Sun, Aug 17, 2008 at 11:25 AM, Joseph Smith joe@settoplinux.org wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
YAHOO!!! Great work Kevin:-)
screenshot on wiki?
This is kind of a big deal :-)
ron
Get ready for the slashdot effect.
ron minnich wrote:
On Sun, Aug 17, 2008 at 11:25 AM, Joseph Smith joe@settoplinux.org wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
YAHOO!!! Great work Kevin:-)
screenshot on wiki?
This is kind of a big deal :-)
ron
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Sun, Aug 17, 2008 at 12:22 PM, bari bari@onelabs.com wrote:
Get ready for the slashdot effect.
Then we for sure want that nice wiki page ready. And, stepan can sit next to coreboot.org for 72 hours managing the problems.
ron
Hi,
On Sun, Aug 17, 2008 at 12:09:13PM -0700, ron minnich wrote:
On Sun, Aug 17, 2008 at 11:25 AM, Joseph Smith joe@settoplinux.org wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
YAHOO!!! Great work Kevin:-)
screenshot on wiki?
I was thinking of that too, but there isn't much to screenshot. It looks just like regular windows.
If anyone has any suggestions, let me know.
-Kevin
On Sun, Aug 17, 2008 at 12:24:43PM -0400, Kevin O'Connor wrote:
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
The changes to seabios have been committed to the git repo. One can download it with:
git clone git://git.linuxtogo.org/home/kevin/seabios.git
I've also uploaded the source code in tar format to:
http://linuxtogo.org/~kevin/SeaBIOS/seabios-0.3.0.tar.gz
and I've placed a precompiled elf file suitable for coreboot at:
http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-0.3.0
-Kevin
Hi,
Well done!
I still need to disable ACPI support in order to install winxp (hit the F7 key when asked about additional driver). This appears to be due to incomplete ACPI support in coreboot-v2 for the epia-m.
Please check the Asus A8V-E SE DSDT table in coreboot. Windows Installer may need ACPI routing and also floppy/keyboard/mouse objects. Check DSDT from Qemu.
Check this:
http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx http://www.microsoft.com/whdc/archive/pcguides.mspx
Handy BSOD STOP decoder for ACPI:
http://support.microsoft.com/?scid=kb%3Ben-us%3B314830&x=4&y=7
Compatibility:
http://support.microsoft.com/kb/314088/en-us
Thanks, Rudolf
Kevin,
It changed the behavior for me for XP installation. Now I get "Hardware Malfunction Contact your hardware vendor for support."
I used 6 for the number of PCI buses.
It still hangs in the same place for ReactOS. It wants me to press enter to continue, but it's frozen.
Thanks, Myles
On Sun, Aug 17, 2008 at 10:24 AM, Kevin O'Connor kevin@koconnor.net wrote:
Hi,
I've now successfully installed and booted Windows XP professional on my epia-m with coreboot-v2 and seabios.
The changes to seabios have been committed to the git repo. One can download it with:
git clone git://git.linuxtogo.org/home/kevin/seabios.git
The reason the install and boot failed before was due to the pcibios functions. The VIA vga card shows up on bus 1 on the epia-m. However, the pcibios functions only supported bus 0. The latest seabios git now supports pcibios calls on machines with more than 1 bus.
I still need to disable ACPI support in order to install winxp (hit the F7 key when asked about additional driver). This appears to be due to incomplete ACPI support in coreboot-v2 for the epia-m.
To enable coreboot support in seabios, modify the file src/config.h and change CONFIG_COREBOOT to 1. You'll also likely want to change CONFIG_DEBUG_LEVEL and CONFIG_DEBUG_SERIAL. Finally, make sure CONFIG_PCI_BUS_COUNT is correct for your machine.
There is still plenty of stuff to do, but I think this is an important step forward.
-Kevin
Hi Myles,
On Tue, Aug 19, 2008 at 04:54:55PM -0600, Myles Watson wrote:
It changed the behavior for me for XP installation. Now I get "Hardware Malfunction Contact your hardware vendor for support."
Well, I guess that's progress. :-/ Does it fail after a while, or right at the start? You got through the install with bochs bios, right?
I used 6 for the number of PCI buses.
[...]
PCI: 07:09.1 [14e4/1648] enabled
I think you want to set CONFIG_PCI_BUS_COUNT to 8 - it should be one more than your largest bus number.
It still hangs in the same place for ReactOS. It wants me to press enter to continue, but it's frozen.
Hrmm. Does the bios keyboard support work at all? If you use a freedos CD, can you type in dos commands?
Have you been able to confirm that reactos works on your machine with a different bios?
-Kevin
Kevin,
On Tue, Aug 19, 2008 at 04:54:55PM -0600, Myles Watson wrote:
It changed the behavior for me for XP installation. Now I get "Hardware Malfunction Contact your hardware vendor for support."
Well, I guess that's progress. :-/ Does it fail after a while, or right at the start? You got through the install with bochs bios, right?
It fails at the "Setup is Starting Windows" screen. It flashes the screen, then gives the failure message.
That's right, I got through the install with the original Bochs BIOS, but without any of the 32-bit or PCI functions.
I used 6 for the number of PCI buses.
[...]
PCI: 07:09.1 [14e4/1648] enabled
I think you want to set CONFIG_PCI_BUS_COUNT to 8 - it should be one more than your largest bus number.
I didn't look closely enough. Thanks for pointing that out. The largest I saw was 5.
It still hangs in the same place for ReactOS. It wants me to press
enter to
continue, but it's frozen.
Hrmm. Does the bios keyboard support work at all? If you use a freedos CD, can you type in dos commands?
It works enough for me to select items from the boot menu. I'll try freedos.
Have you been able to confirm that reactos works on your machine with a different bios?
I don't have a different BIOS, but ReactOS works in QEMU fine.
It's possible that the freeze is not related to the keyboard, it just happens to be what's on the screen.
Thanks, Myles