EFI-dualbooting OSX and Linux on iMac with T7400-CPU

EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Eeri Kask]

Hello,

After creating 4 partitions with MacOSX installation CD (and installing
OSX) I installed Gentoo 2006.1 x86_64 onto the 4th partition (i.e.
/dev/sda5; in OSX invisible FAT32 partition counts as /dev/sda1).
Now I am kindly looking for help in making linux EFI-bootable using grub2.

In short, what I did so far is (following instructions at
http://grub.enbug.org/TestingOnEFI as closely as I could):

running on CD-booted 64-bit Linux (on /dev/sda5 as root filesystem):

1) cvs -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/grub checkout
grub2
2) cd grub2
3) ./configure --with-platform=efi
4) make
5) ./grub-mkimage -d . -o grub.efi gpt hfsplus fat ext2
6) cp grub.efi *.mod fs.lst command.lst  /boot/grub/
7) cp grub.efi *.mod fs.lst command.lst  /media/usbdisk/
8) I compiled 2.6.18.3 kernel as /boot/vmlinuz

Then I booted MacOS and as root-user:

9) mkdir /Volumes/something/efi/grub
10) Copied  usbstick/*  to  /Volumes/something/efi/grub/
11) bless --folder=/Volumes/something
--file=/Volumes/something/efi/grub/grub.efi --setBoot

12) Then I created  /Volumes/something/efi/grub/grub.cfg  as

set timeout=10
menuentry "GNU/Linux"
{
  search --set /boot/vmlinuz
  set root=(hd0,5)
  linux /boot/vmlinuz root=/dev/sda5
}
menuentry "MacOSX"
{
  set root=(hd0,2)
  chainloader /usr/standalone/i386/boot.efi


In fact 'something' is 'Macintosh HD part2', OSX formatted HFS+
journaled partition /dev/disk0s3.


Now if holding down the 'alt' key while powering on I can choose between
disk0s2 with installed OSX and 'EFI_boot' (disk0s3) which loads and
starts grub if selected.

Grub comes and gives lots of errors:

(line 2-2)
syntax error
Incorrect command
...
(line 12-12)
Press any key to continue...

Then grub shows command line interface:

grub> set root=(hd0,5)
grub> linux /boot/vmlinuz root=/dev/sda5
grub> boot
grub> _

is what I entered and now nothing happens.  However grub reads the
ext3-formatted /dev/sda5 partition as typing TAB completes path- and
filenames.

I am very thankful if someone could point out what is wrong I have done
above.  I have zero experience in using MacOSX but I think the 'bless'
was successful as OSX presents boot device where grub was copied.
Second, I suspect I probably can't boot "MacOSX"-entry above because I
could not figure out if grub can read files in HFS+ journaled partitions
(maybe this is why grub shows syntax errors?); but I can happily live
with pressing 'alt' key while turning power on.

Greetings  (I am sorry for the long post),

    Eeri Kask

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Yoshinori K. Okuji]

On Sunday 03 December 2006 18:05, Eeri Kask wrote:
> After creating 4 partitions with MacOSX installation CD (and installing
> OSX) I installed Gentoo 2006.1 x86_64 onto the 4th partition (i.e.
> /dev/sda5; in OSX invisible FAT32 partition counts as /dev/sda1).
> Now I am kindly looking for help in making linux EFI-bootable using grub2.

Oh, great. :)

> Grub comes and gives lots of errors:
>
> (line 2-2)
> syntax error
> Incorrect command
> ...
> (line 12-12)
> Press any key to continue...

Hmm.. I think you need to put the open braces in the same line as "menuentry" 
commands.

> Then grub shows command line interface:
>
> grub> set root=(hd0,5)
> grub> linux /boot/vmlinuz root=/dev/sda5
> grub> boot
> grub> _
>
> is what I entered and now nothing happens.  However grub reads the
> ext3-formatted /dev/sda5 partition as typing TAB completes path- and
> filenames.

Please check the following:

- Make sure that the linux kernel is compiled with EFI support. I don't know 
how Gentoo defines the default settings, but most distributions do not enable 
it in default kernels, AFAIK.

- Make sure that the linux kernel has an appropriate video driver (or any 
other required drivers). Again, I don't know the current status very much, 
but patches for MacLinux hadn't been integrated with official kernel source 
code when I looked at it. If Gentoo does not get them included, you need to 
apply patches yourself.

- Make sure that you pass correct parameters to the kernel, especially a 
parameter to the video driver. Otherwise, nothing will be displayed.

Another option is to use legacy boot by installing GRUB compiled for PC BIOS 
to the partition for Gentoo. I think recent versions of Intel Mac should 
support legacy boot by default. But, for now, GRUB does not support 
chainloading a legacy boot loader directly, so you will have to boot it up 
from the built-in selector, or use something else, such as refit, or 
implement this feature in GRUB. As I myself haven't played legacy boot well, 
I don't know how to set up this kind of configuration precisely (yet).

BTW, this report seems to be a proof that x86_64 starts up in 32-bit mode even 
on EFI, well, in Intel Mac. So do we really need to implement 64-bit support 
for x86_64?

Thanks,
Okuji

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Eeri Kask]

Yoshinori K. Okuji wrote:
>> (line 2-2)
>> syntax error
>> Incorrect command
>> ...
>> (line 12-12)
>> Press any key to continue...
> 
> Hmm.. I think you need to put the open braces in the same line as "menuentry" 
> commands.

Thank you for the hint!  :-)

So now my grub.cfg looks

menuentry "MacOSX" {
  set root=(hd0,2)
  chainloader /System/Library/CoreServices/boot.efi
}

menuentry "GNU/Linux" {
  set root=(hd0,5)
  linux /boot/vmlinuz root=/dev/sda5
}

and grub shows text-mode menu similar to the old version "0.97".

I think grub is working perfectly well since I can boot MacOSX as one
would expect it to do (my supposition about eventually not reading HFS+
journaled filesystems luckily proved to be false).

Then, selecting 'GNU/Linux' shows

    Booting 'GNU/Linux'

    [Linux-EFI, setup=0x1e00, size=0x231796]


and from now on nothing appears to the screen.  Shortly thereafter I
notice USB-keyboard LEDs blinking on-off (num-lock, caps-lock,
scroll-lock) at some time point, so maybe Linux is in the middle of
booting I simply cannot visually observe.  Assuming booting is in
progress, at some stage it fails though; otherwise I should have remote
ssh-access if it had finished properly, staying in some unusable video
state.
So as you described, graphics drivers need to be investigated and patched.


> BTW, this report seems to be a proof that x86_64 starts up in 32-bit mode even 
> on EFI, well, in Intel Mac. So do we really need to implement 64-bit support 
> for x86_64?

As said, I was able to boot MacOSX 10.4.8 without any trouble on iMac
intel T7400-cpu only using current grub2 from cvs  (i.e. without
bootcamp, without refit, etc. etc.).
Though, after finishing installation, without asking me MacOSX over the
network automatically updated firmware, hopefully to the current latest
version.

Greetings,

    Eeri Kask

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[bibo,mao]

Eeri Kask wrote:
> Yoshinori K. Okuji wrote:
>  >> (line 2-2)
>  >> syntax error
>  >> Incorrect command
>  >> ...
>  >> (line 12-12)
>  >> Press any key to continue...
>  >
>  > Hmm.. I think you need to put the open braces in the same line as "menuentry"
>  > commands.
> 
> Thank you for the hint!  :-)
> 
> So now my grub.cfg looks
> 
> menuentry "MacOSX" {
>   set root=(hd0,2)
>   chainloader /System/Library/CoreServices/boot.efi
> }
> 
> menuentry "GNU/Linux" {
>   set root=(hd0,5)
>   linux /boot/vmlinuz root=/dev/sda5
> }
> 
> and grub shows text-mode menu similar to the old version "0.97".

> 
> I think grub is working perfectly well since I can boot MacOSX as one
> would expect it to do (my supposition about eventually not reading HFS+
> journaled filesystems luckily proved to be false).
> 
> Then, selecting 'GNU/Linux' shows
> 
>     Booting 'GNU/Linux'
> 
>     [Linux-EFI, setup=0x1e00, size=0x231796]
> 
There is no initrd option in your menu, I do not know whether it can
successfully boot up without initrd option with grub2. you can enter
into rescue mode(command-line mode), and enter commands like this:
$linux /boot/vmlinuz root=/dev/sda5
$initrd /boot/xxx
$boot

And what is your linux kernel version?

> 
> and from now on nothing appears to the screen.  Shortly thereafter I
> notice USB-keyboard LEDs blinking on-off (num-lock, caps-lock,
> scroll-lock) at some time point, so maybe Linux is in the middle of
> booting I simply cannot visually observe.  Assuming booting is in
> progress, at some stage it fails though; otherwise I should have remote
> ssh-access if it had finished properly, staying in some unusable video
> state.
> So as you described, graphics drivers need to be investigated and patched.
> 
> 
>  > BTW, this report seems to be a proof that x86_64 starts up in 32-bit mode even
>  > on EFI, well, in Intel Mac. So do we really need to implement 64-bit support
>  > for x86_64?
> 
> As said, I was able to boot MacOSX 10.4.8 without any trouble on iMac
> intel T7400-cpu only using current grub2 from cvs  (i.e. without
> bootcamp, without refit, etc. etc.).
> Though, after finishing installation, without asking me MacOSX over the
> network automatically updated firmware, hopefully to the current latest
> version.
> 
> Greetings,
> 
>     Eeri Kask
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Eeri Kask]

bibo,mao wrote:
>> menuentry "MacOSX" {
>>   set root=(hd0,2)
>>   chainloader /System/Library/CoreServices/boot.efi
>> }
>>
>> menuentry "GNU/Linux" {
>>   set root=(hd0,5)
>>   linux /boot/vmlinuz root=/dev/sda5
>> }
>>
> There is no initrd option in your menu, I do not know whether it can
> successfully boot up without initrd option with grub2. you can enter
> into rescue mode(command-line mode), and enter commands like this:
> $linux /boot/vmlinuz root=/dev/sda5
> $initrd /boot/xxx
> $boot
> 
> And what is your linux kernel version?

2.6.18.5.

initrd is in my case in fact not needed;  I compiled ata_piix and ext3
drivers, and everything inbetween directly into the kernel, so if
correctly loaded, it should be able to access /dev/sda5 and retrieve
/sbin/init from the hard disk; then everything else comes from there as
well.

Currently I am a little puzzled, as grub2 loads and executes MacOS-X
boot.efi correctly, but if trying linux, then linux stops somewhere.
As next, if burning the same kernel image as a bootable syslinux-CD,
linux gets loaded and executed as one would expect.
With the "nv" driver even X11 runs in full 1920x1200 resolution on
iMac-T7400 excellently  (nvidia proprietary driver builds, starts and
runs without complaints, but shows "black pixels" only :-).

Maybe MacOS if booting from CD sets up some faked BIOS environment so
Linux and X11 are in believing it is usual IBM-PC-hardware, but if
booting with grub2 this is not the case and then linux fails?

Momentarily I am not convinced it is a grub2 issue.

Greetings,

    Eeri Kask

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[bibo,mao]

Eeri Kask wrote:
> bibo,mao wrote:
>  >> menuentry "MacOSX" {
>  >>   set root=(hd0,2)
>  >>   chainloader /System/Library/CoreServices/boot.efi
>  >> }
>  >>
>  >> menuentry "GNU/Linux" {
>  >>   set root=(hd0,5)
>  >>   linux /boot/vmlinuz root=/dev/sda5
>  >> }
>  >>
>  > There is no initrd option in your menu, I do not know whether it can
>  > successfully boot up without initrd option with grub2. you can enter
>  > into rescue mode(command-line mode), and enter commands like this:
>  > $linux /boot/vmlinuz root=/dev/sda5
>  > $initrd /boot/xxx
>  > $boot
>  >
>  > And what is your linux kernel version?
> 
> 2.6.18.5.
There exists one bug in Linux kernel only EFI bios relative at
http://marc.theaimsgroup.com/?l=linux-kernel&m=116157536316034&w=2
I do not know whether 2.6.18.5 incorporates this bug.

> 
> initrd is in my case in fact not needed;  I compiled ata_piix and ext3
> drivers, and everything inbetween directly into the kernel, so if
> correctly loaded, it should be able to access /dev/sda5 and retrieve
> /sbin/init from the hard disk; then everything else comes from there as
> well.
> 
> Currently I am a little puzzled, as grub2 loads and executes MacOS-X
> boot.efi correctly, but if trying linux, then linux stops somewhere.
> As next, if burning the same kernel image as a bootable syslinux-CD,
> linux gets loaded and executed as one would expect.
> With the "nv" driver even X11 runs in full 1920x1200 resolution on
> iMac-T7400 excellently  (nvidia proprietary driver builds, starts and
> runs without complaints, but shows "black pixels" only :-).
> 
> Maybe MacOS if booting from CD sets up some faked BIOS environment so
> Linux and X11 are in believing it is usual IBM-PC-hardware, but if
> booting with grub2 this is not the case and then linux fails?
I am not familiar with Mac machine, In general there exists two types of
bios. One is EFI bios, the other is legacy pc bios. I doubt that 
syslinux-CD boots from legacy pc bios but not EFI bios. You can enter 
"dmesg" command to find memory map information to judge which bios kernel
boots from.

thanks
bibo, mao

> 
> Momentarily I am not convinced it is a grub2 issue.
> 
> Greetings,
> 
>     Eeri Kask
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Eeri Kask]

bibo,mao wrote:
>> 2.6.18.5.
> There exists one bug in Linux kernel only EFI bios relative at
> http://marc.theaimsgroup.com/?l=linux-kernel&m=116157536316034&w=2
> I do not know whether 2.6.18.5 incorporates this bug.

Oh, I see.  This bug is not corrected in 2.6.18.5.
As a side note, in contrast, in  "arch/x86_64/kernel/"  there are
seemingly no files having anything to do with efi.  Maybe this is of no
importance though.

>> Maybe MacOS if booting from CD sets up some faked BIOS environment so
>> Linux and X11 are in believing it is usual IBM-PC-hardware, but if
>> booting with grub2 this is not the case and then linux fails?
> I am not familiar with Mac machine, In general there exists two types of
> bios. One is EFI bios, the other is legacy pc bios. I doubt that
> syslinux-CD boots from legacy pc bios but not EFI bios. You can enter
> "dmesg" command to find memory map information to judge which bios kernel
> boots from.

:-)

I sincerely apologise for the long attachment in advance; here I send
you the dmesg output in full, most of it I do not understand.

Greetings,

    Eeri Kask

--------8<--------8<--------

Bootdata ok (command line is root=/dev/sda5 BOOT_IMAGE=bzImage )
Linux version 2.6.18.5 (eeri@sierra) (gcc version 4.1.1 (Gentoo 4.1.1))
#1 SMP PREEMPT Wed Dec 6 16:09:02 CET 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007f103000 (usable)
 BIOS-e820: 000000007f103000 - 000000007f304000 (ACPI NVS)
 BIOS-e820: 000000007f304000 - 000000007febe000 (ACPI data)
 BIOS-e820: 000000007febe000 - 000000007feef000 (ACPI NVS)
 BIOS-e820: 000000007feef000 - 000000007ff00000 (ACPI data)
 BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved)
 BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
DMI 2.4 present.
ACPI: RSDP (v002 APPLE                                 ) @
0x00000000000fe020
ACPI: XSDT (v001 APPLE   Apple00 0x00000093      0x01000013) @
0x000000007fefd1c0
ACPI: FADT (v003 APPLE   Apple00 0x00000093 Loki 0x0000005f) @
0x000000007fefb000
ACPI: HPET (v001 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fefa000
ACPI: MADT (v001 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fef9000
ACPI: MCFG (v001 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fef8000
ACPI: ASF! (v032 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fef7000
ACPI: SBST (v001 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fef5000
ACPI: ECDT (v001 APPLE   Apple00 0x00000001 Loki 0x0000005f) @
0x000000007fef4000
ACPI: SSDT (v001 APPLE   SataPri 0x00001000 INTL 0x20050309) @
0x000000007febb000
ACPI: SSDT (v001 APPLE   SataSec 0x00001000 INTL 0x20050309) @
0x000000007feba000
ACPI: SSDT (v001 APPLE     CpuPm 0x00003000 INTL 0x20050309) @
0x000000007feef000
ACPI: DSDT (v001 APPLE   iMac6,1 0x00010001 INTL 0x20050309) @
0x0000000000000000
No mptable found.
On node 0 totalpages: 511592
  DMA zone: 2296 pages, LIFO batch:0
  DMA32 zone: 509296 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 6:15 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 88000000 (gap: 80000000:70000000)
Built 1 zonelists.  Total pages: 511592
Kernel command line: root=/dev/sda5 BOOT_IMAGE=bzImage
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer.
time.c: Detected 2161.258 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Checking aperture...
Memory: 2043072k/2081804k available (3886k kernel code, 38328k reserved,
1916k data, 232k init)
Calibrating delay using timer specific routine.. 4328.85 BogoMIPS
(lpj=8657703)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
Freeing SMP alternatives: 32k freed
ACPI: Core revision 20060707
Using local APIC timer interrupts.
result 10390656
Detected 10.390 MHz APIC timer.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 4322.54 BogoMIPS
(lpj=8645080)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz stepping 06
Brought up 2 CPUs
testing NMI watchdog ... OK.
migration_cost=27
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at f0000000
ACPI: Found ECDT
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *11 12 14 15)
ACPI: Embedded Controller [EC] (gpe 23) interrupt mode.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 9 devices
intel_rng: FWH not detected
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a
report
PCI-GART: No AMD northbridge found.
PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
  IO window: 2000-2fff
  MEM window: 90000000-91ffffff
  PREFETCH window: 80000000-8fffffff
PCI: Bridge: 0000:00:1c.0
  IO window: 1000-1fff
  MEM window: 92300000-923fffff
  PREFETCH window: 92500000-925fffff
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: 92200000-922fffff
  PREFETCH window: 92000000-920fffff
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: 92100000-921fffff
  PREFETCH window: disabled.
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
GSI 17 sharing vector 0xB1 and IRQ 17
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1166022473.876:1): initialized
Total HugeTLB memory allocated, 0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:01.0:pcie00]
Allocate Port Service[0000:00:01.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
Allocate Port Service[0000:00:1c.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
Allocate Port Service[0000:00:1c.1:pcie03]
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
vga16fb: initializing
vga16fb: mapped to 0xffff8100000a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Using specific hotkey driver
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [APPLE ] OemTableId [
Cpu0Ist] [20060707]
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [APPLE ] OemTableId [
Cpu0Cst] [20060707]
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [APPLE ] OemTableId [
Cpu1Ist] [20060707]
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [APPLE ] OemTableId [
Cpu1Cst] [20060707]
ACPI: CPU1 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU1] (supports 8 throttling states)
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.101 (c) Dave Jones
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
sky2 v1.5 addr 0x92300000 irq 16 Yukon-EC (0xb6) rev 2
sky2 eth0: addr 00:16:cb:a0:0c:4a
PPP generic driver version 2.4.2
bcm43xx driver
Linux video capture interface: v2.00
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot 0000:00:1f.1
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
ICH7: chipset revision 2
ICH7: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x30c0-0x30c7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x30c8-0x30cf, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PIONEER DVD-RW DVR-K06, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache
Uniform CD-ROM driver Revision: 3.20
Loading iSCSI transport class v1.1-646.<7>libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 P2 XX XX ]
Losing some ticks... checking if CPU frequency changed.
ata_piix 0000:00:1f.2: invalid MAP value 0
GSI 19 sharing vector 0xC1 and IRQ 19
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x30D8 ctl 0x30F6 bmdma 0x3020 irq 19
ata2: SATA max UDMA/133 cmd 0x30D0 ctl 0x30F2 bmdma 0x3028 irq 19
scsi0 : ata_piix
ATA: abnormal status 0x7F on port 0x30DF
ATA: abnormal status 0x7F on port 0x30DF
ata1.01: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32)
ata1.01: configured for UDMA/133
scsi1 : ata_piix
ATA: abnormal status 0x7F on port 0x30D7
  Vendor: ATA       Model: ST3500641AS  Q    Rev: 3.BT
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 sda5
sd 0:0:1:0: Attached scsi disk sda
sd 0:0:1:0: Attached scsi generic sg0 type 0
SCSI Media Changer driver v0.25
I2O subsystem v1.325
i2o: max drivers = 8
I2O Configuration OSM v1.323
I2O Bus Adapter OSM v1.317
I2O Block Device OSM v1.325
I2O SCSI Peripheral OSM v1.316
I2O ProcFS OSM v1.316
ieee1394: Initialized config rom entry `ip1394'
ACPI: PCI Interrupt 0000:04:03.0[A] -> GSI 19 (level, low) -> IRQ 19
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]
MMIO=[92104000-921047ff]  Max Packet=[4096]  IR/IT contexts=[4/8]
video1394: Installed video1394 module
ieee1394: raw1394: /dev/raw1394 device initialized
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
ieee1394: sbp2: Try serialize_io=0 for better performance
eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
GSI 20 sharing vector 0xC9 and IRQ 20
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 20, io mem 0x92405400
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
Initializing USB Mass Storage driver...
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
13:55:50 2006 UTC).
no UART detected at 0x1
Motu MidiTimePiece on parallel port irq: 7 ioport: 0x378
GSI 21 sharing vector 0xD1 and IRQ 21
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1b.0 to 64
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0017f2fffe7d08fe]
hda_codec: Unknown model for ALC882, trying auto-probe from BIOS...
ALSA device list:
  #0: Dummy 1
  #1: Virtual MIDI Card 1
  #2: MTPAV on parallel port at 0x378
  #3: HDA Intel at 0x92400000 irq 21
NET: Registered protocol family 1
NET: Registered protocol family 15
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>
ieee80211_crypt: registered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'WEP'
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 232k freed
EXT3 FS on sda5, internal journal

--------8<--------8<--------

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[bibo,mao]

Eeri Kask wrote:
> bibo,mao wrote:
>  >> 2.6.18.5.
>  > There exists one bug in Linux kernel only EFI bios relative at
>  > http://marc.theaimsgroup.com/?l=linux-kernel&m=116157536316034&w=2 
> <http://marc.theaimsgroup.com/?l=linux-kernel&m=116157536316034&w=2>
>  > I do not know whether 2.6.18.5 incorporates this bug.
> 
> Oh, I see.  This bug is not corrected in 2.6.18.5.
> As a side note, in contrast, in  "arch/x86_64/kernel/"  there are
> seemingly no files having anything to do with efi.  Maybe this is of no
> importance though.
x86_64 currently does not support EFI bios, there is no x86_64 efi
booloader and x86_64 kernel does not support EFI bios now. Soon x86_64
kernel patch and grub bootloader patch will be published out.

From your dmesg information, system boots from legacy bios. When machine
is powered on, EFI bios is loaded first and then lagacy bios is loaded if
there is no response.
> 
>  >> Maybe MacOS if booting from CD sets up some faked BIOS environment so
>  >> Linux and X11 are in believing it is usual IBM-PC-hardware, but if
>  >> booting with grub2 this is not the case and then linux fails?
>  > I am not familiar with Mac machine, In general there exists two types of
>  > bios. One is EFI bios, the other is legacy pc bios. I doubt that
>  > syslinux-CD boots from legacy pc bios but not EFI bios. You can enter
>  > "dmesg" command to find memory map information to judge which bios kernel
>  > boots from.
> 
> :-)
> 
> I sincerely apologise for the long attachment in advance; here I send
> you the dmesg output in full, most of it I do not understand.
> 
> Greetings,
> 
>     Eeri Kask
> 
> --------8<--------8<--------
> 
> Bootdata ok (command line is root=/dev/sda5 BOOT_IMAGE=bzImage )
> Linux version 2.6.18.5 (eeri@sierra) (gcc version 4.1.1 (Gentoo 4.1.1))
> #1 SMP PREEMPT Wed Dec 6 16:09:02 CET 2006
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 000000007f103000 (usable)
>  BIOS-e820: 000000007f103000 - 000000007f304000 (ACPI NVS)
>  BIOS-e820: 000000007f304000 - 000000007febe000 (ACPI data)
>  BIOS-e820: 000000007febe000 - 000000007feef000 (ACPI NVS)
>  BIOS-e820: 000000007feef000 - 000000007ff00000 (ACPI data)
>  BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved)
>  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
>  BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
>  BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
>  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>  BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
the memory map information shows that it is e820 map information,
it is legacy bios memory map information. Currently Linux only 
supports EFI bios on IA32 platform.

thanks
bibo,mao
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Marco Gerards]

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> On Sunday 03 December 2006 18:05, Eeri Kask wrote:
>> After creating 4 partitions with MacOSX installation CD (and installing
>> OSX) I installed Gentoo 2006.1 x86_64 onto the 4th partition (i.e.
>> /dev/sda5; in OSX invisible FAT32 partition counts as /dev/sda1).
>> Now I am kindly looking for help in making linux EFI-bootable using grub2.
>
> Oh, great. :)
>
>> Grub comes and gives lots of errors:
>>
>> (line 2-2)
>> syntax error
>> Incorrect command
>> ...
>> (line 12-12)
>> Press any key to continue...
>
> Hmm.. I think you need to put the open braces in the same line as "menuentry" 
> commands.

This is a bug, I will write it down somewhere...  We need a real BTS
soon. :-)

--
Marco

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Thomas Schwinge]

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

On Wed, Dec 13, 2006 at 01:49:10PM +0100, Marco Gerards wrote:
> We need a real BTS soon. :-)

You already have one and people are already using it, only the developers
aren't: <http://savannah.gnu.org/bugs/?group=grub>, 191 bugs reported,
most about GRUB legacy, I guess.


Regards,
 Thomas

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Marco Gerards]

Thomas Schwinge <tschwinge@gnu.org> writes:

> On Wed, Dec 13, 2006 at 01:49:10PM +0100, Marco Gerards wrote:
>> We need a real BTS soon. :-)
>
> You already have one and people are already using it, only the developers
> aren't: <http://savannah.gnu.org/bugs/?group=grub>, 191 bugs reported,
> most about GRUB legacy, I guess.

Right, we are talking about GRUB 2.  We need to decide what to do.  I
don't prefer using savannah, but I prefer it above nothing at all.

--
Marco

Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU

[Yoshinori K. Okuji]

On Wednesday 13 December 2006 14:29, Thomas Schwinge wrote:
> You already have one and people are already using it, only the developers
> aren't: <http://savannah.gnu.org/bugs/?group=grub>, 191 bugs reported,
> most about GRUB legacy, I guess.

Yes, it is a full of garbage. A public BTS into which anybody can post tends 
to be like this, because some people use a BTS only to ask questions or 
support, and some even don't try to see a FAQ page before submitting bugs. So 
I'm now a public BTS hater. If you want to have a BTS, please, please 
restrict who can submit bugs. Otherwise, at a point, you will be very tired 
of closing or cancelling bogus bugs, and it will be the same as the BTS for 
GRUB Legacy.

Okuji