Possible fix for ALL non booting linux kernels

[Guest]

Solution: Dont boot em.
QEMU has a option called -kernel that lets you load a kernel into memory and boot it. If we give PearPC a option like that
(ppc_kernel_enabled = 1
ppc_kernel_path = vmlinuz)
And add a option to the boot screen

Choose a option

0 Show all (even unbootable)
1. Partition 2 of hd1 (apple/apple_bootstrap)
2. Linux kernel in memory (vmlinuz)

Your choice? _

We might be able to boot the kernel. Or we might have to make a kind of easy to edit Yaboot or even
ppc_kernel_options = -------- (cant renember options)
It might be something worth looking into.

[Alex]

OpenBIOS is being implemented right now, so once it is complete, Yaboot will run fine, and there would be no need for this

[jchowland]

How is open bios support coming along? Next week, month... year?

[Guru3]

[quote="jchowland":c12d0f9ae6]
How is open bios support coming along? Next week, month... year?
[/quote:c12d0f9ae6]We don't really know, but, as it's something that's already on the way, it will probably be done a lot quicker than this could be...

[Guest]

Is it avalible on CVS yet?

[Alex]

no

[dfoesch]

[quote="jchowland":6db2ef0b98]
How is open bios support coming along? Next week, month... year?
[/quote:6db2ef0b98]

I'm waiting on the OpenBIOS people right now. The device discovery of OpenBIOS is non-existant, so we really wouldn't be gaining all that much from using OpenBIOS right now at all.

Honestly, the only thing that OpenBIOS would get us is passing off the work of implementing a compliant OpenFirmware implementation to someone else.

*Shrug* oh well, it will work eventually, and PearPC is pretty much the best platform for them to be working on it.

[Guest]

Can someone just answer?
Will my method get 2.6 working
Or will OpenBIOS

[dfoesch]

[quote="Anonymous":8759e3bcc8]
Can someone just answer?
Will my method get 2.6 working
Or will OpenBIOS
[/quote:8759e3bcc8]

The problem with booting 2.6 is manyfold.

First, the console doesn't work.

Second, the load-address defined by the standard CHRP doesn't hack it. Likely, the linux kernel has a different address that it asks for in the ELF file. (the promboot fixes this, but my promboot patch won't boot a linux 2.6 kernel either, as it has problems allocating stack space)

Third, there's still some problem somewhere that's causing it to lock up.

[Guest]

The promboot doesnt even get past the select boot device screen :shock:. Well lets hope for the best. Something for far future. Cherryos like GUI. I am already working on one.