[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] New x86_64 EFI patch

From: Bean
Subject: Re: [PATCH] New x86_64 EFI patch
Date: Sat, 28 Jun 2008 19:55:59 +0800

On Sat, Jun 28, 2008 at 6:51 PM, Isaac Dupree
<address@hidden> wrote:
> Bean wrote:
>> Perhaps command line is not passed to loader correctly, you can verify
>> it with the OSX loader:
>> set root=(hd0,2)
>> chainloader /System/Library/CoreServices/boot.efi -- -v
>> boot
>> Please try this out, if parameter -v is passed to the loader, you will
>> see console screen before switching to GUI.
> That 'chainloader' didn't work at all: It seems GRUB2 here isn't
> understanding the HFS+(journaled) filesystem at all.  Neither in EFI nor
> BIOS grub2 can I see anything on that partition, even though I have module
> hfsplus loaded (I think - but lsmod in grub takes up more than the whole
> screen, so I can't see them all - is there any way to get around that?).
> Also I decided to play around and try a few other commands in grub2.
> cpuid (efi or pc) -- finishes instantly without outputting anything
> lspci (efi) -- hangs (but it works properly in pc)
> reboot (efi) -- hangs (but it works properly in pc)

I wonder if there is bug in the hfsplus module. You can check it out
with grub-fstest command:

sudo ./grub-fstest /dev/sda3 ls /

This would list the content of root directory.

You can also create a small hfs+ image and test it with grub-fstest,
if it does have problem, you can upload the image for me to test.

cpuid would check if cpuid exists and set return code, there is no output.

The result is lspci is a little strange. Is there any output before
hanging ? When you use video=efifb or video=vesafb. It enum pci to get
the frame buffer address, if it doesn't hang there, it shouldn't hang
here as well.

reboot could be a firmware related issue, I can check it out.

Oh btw, do you compile from source or use the binary version ?

>>> every time I've tried Ubuntu with a different kernel... it has problems.
>>>  Ubuntu has a fancy initrd, modules, lots of patches, Upstart as init, >and
>>> who knows what assumptions about the boot process... but maybe.  I could use
>>> the kernel from the Ubuntu development branch, if I >had any idea how to use
>>> APT to upgrade just a few specific things from an unstable package-source
>>> and not my whole system (the kernel >binary obviously doesn't depend on
>>> system libraries, so it should be uniquely easy to do this...).  Do you know
>>> about debians -- if that's >possible?
>> In debian, all I have to do is to add the sid line to
>> /etc/apt/source.list, apt-get update, then apt-get install
>> linux-image-xxx. Ubuntu is based on debian, the process should be
>> similar.
> yes it is similar (and I'd probably try and use the Ubuntu development
> branch for the next release, "intrepid") : however, what bothers me is that
> this seems to make the whole apt repo, not just the part I want, be a
> first-class citizen; so that if it contains a newer version number of any
> package on my system, it will install that if I ask to install the package,
> or it will offer to upgrade to that version if it's already installed (so I
> can't even begin to pick out which are the Ubuntu-stable updates).  I hope
> I'm missing some option that lets me avoid this risky nuisance, while still
> keeping tabs on the unstable linux-image packages?

Perhaps the most simple way is to download the deb package from
intrpid, then install it with dpkg.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]