Re: Requirements for Grub2 PPC install
> I'm sorry for posting to the list, but I've had some trouble tracking down > the answers I need.. Don't worry about that. :-) > I've tried following the instructions on the Wiki for installing grub2/ppc > on a clean, basic (working) Gentoo install with yaboot. My partitions > were set up as: Did you use GRUB 2 CVS? > When I tried to boot against it, I saw the initial Grub welcome message, > but it immediately gave an error message. I don't have the error message > to show as I've rebuilt the machine with extra partitions this > time. I can now try dedicating one for /boot and possibly one for grub > itself (running the grub-install seemed to insist on one). Right, the reason for that is that the firmware can't load from ext2 (or whatever you use). So you need a HFS+ partition as /boot (assuming you use an apple). > My question isn't so much why my original try failed, but what are the > requirements for setting up grub2 on ppc's? (req'd partitions, > filesystems, sizes, initrd? etc.) I'd appreciate if someone could work > with me on setting this up offline. Once I understand what is needed and > can get it reliably installed, I will happily update the documentation to > help the next guy (or gal). You need to have a new world apple or a pegasos II. Otherwise it just has to work. If it doesn't, please describe exactly what you did and which errors you encountered. It can certainly be the case that you found a bug; GRUB 2 is still not used that much and it changes and evolves rapidly. > Alternatively, is there a description of the layout of the grub2 code so I > can follow the process myself to figure it out? I'm a developer, but I'm > having some difficulty figuring out the organization as I poke around. > Would the documentation for grub legacy help? Is there some general > information floating around that I haven't found yet? I will write something for the wiki this evening or tomorrow, if nothing is there about the organisation of the code. Otherwise I'll point you to the right documents. -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
serial line - file interface
Hello. I hope that this will be interesting for you... I'm making some experiments with embedde OS, currently with RTEMS on i386. I use some PC (to hand) for my tests and got to the problem with booting. See, it's just to much time for each boot! So I made some changes to grub to be able to boot images from the serial line. I know that there are better sulutions for this problem but maybe this can help on some way to the grub project. There is a new command 'comload' - it's a bit silly but that's Ok for me. That's what I have used first... before the idea for the `(com)' device. The patch to release 1.92 can be found here: http://81.161.251.159/pub/grub/grub-1.92-comio.patch and that's the changelog entry: +2005-02-03 Kiril Paunov <[EMAIL PROTECTED]> + + * util/i386/pc/grub-install.in: Found an syntaxis error. + + * commands/comload: New command for serial data download. + I's a bit ~~~ but can be usefull for people that work with + embedded systems. + + * util/grub-comiosrv.c: Server program for the `(com)' interface + (See bellow include/grub/comio.h io/comio.c). + + * include/grub/comio.h io/comio.c: New file interface. + This allows to download and boot ower the serial line. + I't usefull for people that work with embedded systems. + It's not very good covered by the file interface but i't + works well. There is not a good abstraction for this kind + off filesystem (net/serial/???)!!! + Example: + grub.cfg: + # + # serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 + # terminal serial + # + Host: on /dev/ttyS0 + # + # ./grub-comiosrv -b 115200 /dev/ttyS0 + # + Host: on /dev/ttyS1 + # + # > multiboot (com)/0-115200-n-8-1-my_test_image + # > boot + # + The sintax is: + `(com)/' + `' = - + `' = <0|1> - comm port + `' = - valid baud rate + `' = + `' = <5|6|7|8> + `' = <1|2> + `' = file name on the host relative to `grub-comiosrv' + Protocol: + Request_A: `[my_test_image]' + Respons_A: `[]' + Request_B: `[my_test_image::]' + Request_B: `[]' + + Enjoy yourself! -- With respect & pleasure Kiril Paunov -- http://mail.tu-sofia.bg/ ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
booting grub, loading kernels and unloading kernels question
A question. It may be stupid but I have to ask it. Can we boot grub and boot linux so that linux don't write on grub reserved memory (let's say first 640k) And then make an special halt command that halts linux and boots again grub? (without rebooting) I think this has a lof of possibilities for using OSes as a grub module in live cds but I do not know if it is feasible. Currently I want an easy way of showing an image with a lot of colours in grub without having to code vesa and all of that. (Talking about grub legacy, as always ;) ) If this works... I will need to know how to patch the kernel and how to strip gnu/linux distro to have only the display command or equivalent to show images in framebuffer or equivalent. adrian15 ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
