SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been following this thread for quite awhile now. I run Ubuntu Feisty on my MacBook Core Duo (not C2D or MB Pro). My system is fully working --wireless/isight/adv. keyboard/adv. touchpad/backlight/suspend-to-ram/hibernate(sorta) etc etc.
I have been running ubuntu as the sole OS for about 2 months, just using GRUB installed on the MBR block of the GPT. It boots fine after about 5 secs of EFI looking for a bootable disk. I really want to get Ubuntu to boot in a pure EFI/GPT environment. That is, without using GRUB on the protected MBR block and without any BIOS emulation business. My understanding is that I need an EFI bootloader, either GRUB2 or ELILO, as well as having an EFI-aware kernel to properly accept control and boot.
I have been reading on the Debian lists and it *seems* that the ia64 and even ia32 kernels have supported EFI for awhile. But, when I apt-get install elilo it pulls down a little utility called efibootmgr which is supposed to allow access to the EFI boot parameters. But, efibootmgr requires module efivars to be loaded. My kernel doesn't include efivars and nowhere have I been able to find it.
Am I understanding this right?? Should my ubuntu be able to boot directly from EFI via ELILO? I'm running the stock 2.6.20-15-generic that Ubuntu installed. I think there is a big conception that ELILO is for ia64 kernels only, since they apparently contain the necessary EFI code.
Sorry I can't be of more help. The thread that's still on the first page has some good info... 'explanation of elilo' or something to that effect. Their server is being screwy lately so I'll post it from my inbox:
Quote:
Originally Posted by mactel-users
hi guys. i spent a bit of time looking into what elilo is, and have a
couple of questions.
1) why is rEFIt + lilo recommended in most how-to guides rather than
just using elilo?
2) what problems exist for using elilo on a MBP C2D?
3) are there any reasons to stick with rEFIt + lilo/grub rather than
switch to elilo?
thanks!
Nick
-----------------
Hello,
more precisely,
we can boot with EFI kernel,
but video needs BIOS data to works properly:
If I remember well, some information about it
can be fount at the rEFIt site.
hth,
Jerome
----------------------------------
> but video needs BIOS data to works properly:
Only if you want to use the proprietary ATI driver or the free VESA
driver. The framebuffer was working correctly for me (even if it was
slow and limited).
Bye,
Rousseau
------------------------------------
> Only if you want to use the proprietary ATI driver or the free VESA
> driver. The framebuffer was working correctly for me (even if it was
> slow and limited).
The Intel graphics driver requires a VESA BIOS, too. So, every Intel
Mac has only limited use without it (no hardware 3D, no smooth
fullscreen video etc.)
Regards,
Tino
-----------------------------------
> Only if you want to use the proprietary ATI driver or the free VESA
> driver. The framebuffer was working correctly for me (even if it was
> slow and limited).
>
On my macmini with a non efi kernel X stuff work fine,
with an efi kernel it no more true (I dot not care as I used it
as a number cruncher)
Jerome
Also, some more info concerning wireless.. madwifi is making more progress. wep and wpa should be working now..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.