GRUB2 on the MacBook
Hi, Has anyone here tested GRUB 2 on the MacBook(EFI) already? I have been playing with it and here are some things I noticed: Module loading did not work for me. At first I has an image with boot.mod excluded. I loaded boot.mod manually (from an ext2 filesystem) and it crashed after I ran the `boot' command. The module does work when I include it in the image. Is this a known problem? I will look into this and fix it when I have some time again, although I have no clue when that will be because I thought too often I would have time while that turned out not to be true. So if someone else wants to fix this, don't wait for me. Another thing is Linux. This might be a bit off-topic, but it is essential if I want to switch to GRUB 2 completely some day soon. Okuji, you were able to load Linux properly, right? I can't get the framebuffer to work. I am booting with "video=imacfb:macbook", have imacfb and EFI boot support compiled in. When booting the display is messed up. With some kernels+attempts I see the mess scrolling by, but it does not come to a point where I see something or can ssh into this box. Thanks, Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: GRUB2 on the MacBook
Marco Gerards <[EMAIL PROTECTED]> writes: > Another thing is Linux. This might be a bit off-topic, but it is > essential if I want to switch to GRUB 2 completely some day soon. > Okuji, you were able to load Linux properly, right? > > I can't get the framebuffer to work. I am booting with > "video=imacfb:macbook", have imacfb and EFI boot support compiled in. > When booting the display is messed up. With some kernels+attempts I > see the mess scrolling by, but it does not come to a point where I see > something or can ssh into this box. Ignore this part, I got it to work. -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: EFI disk probing problem
On Friday 04 August 2006 07:26, bibo,mao wrote: > My hard disk is MBR partition type, there is FAT partition in my logical > partition, bootloader grub.efi is in this partition. When grub efi > bootloader starts up, it cannot probe my hard disk. It is because that > parent device_path of current logical partition is extended partition, but > not my hard disk's device path. I don't remember precisely, but I think I only added disk devices but not partition devices. On your system, don't disk devices as well as partition devices get enumerated? BTW, can you follow the GNU-style formatting rules? It is very difficult for me to read a different coding style. Thanks, Okuji ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Build environment
On Saturday 05 August 2006 14:16, Jeff Bailey wrote: > I'll start by saying that I have nothing but hate for the build > environment in grub2. That's your freedom. :p > I realise that automake can be equally confusing in many ways, but it > has two main advantages: 1) Everyone knows it already, 2) Other people > are helping solve bugs with it. Automake is unacceptable, since it does not support what GRUB 2 requires. For instance, how do you specify different compilers for different targets? I can enumerate a lot of deficiency in automake, as I was an automake developer, but I don't think it's worth doing here. The only way to fix automake is to redesign it from scratch; then this is much more work than writing our own Makefile generator. Note that our generator is designed for those who know automake to understand very easily. The way of how it works is quite similar to automake. > * No autodetection of Makefile snippet, to auto update them. No > generic rules to handle the updating when testing. I do not understand this. What rules do you need? > * No obvious well to tell how it's getting to any given phase. No > documentation. Because I think it is too trivial for those who know GNU make. > * Dependancy generation is run too early. Initial dependancies are > broken. Yes, I agree. Please feel free to improve it. > * No obvious way to add dependancies to specific files that need them. It is obvious. You just write a dependency as in GNU make. Like automake, every line is verbosely copied. > * Order in .mk files is important even for seemingly unrelated clauses. I haven't notified this. Okuji ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
