grub2 EFI boot loader internal/external booting

[tschuliaen]

They are the first thing printed when grub runs (after rEFIt).
You can add a line in the beginning of the grub.cfg
"echo startup" and this debug should appear just afterwards.

metatech

Ok i get:

video/efi_uga.c:102: Display controller: 1:0.0
Device id: 40710de
video/efi_uga.c:131:MMIO(0):0xd2000000
video/efi_uga.c:131:VMEM(1):0xc0000000
video/efi_uga.c:131:MMIO(3):0xd0000000

Thanks for your help metatech!

[metatechbe]

Ok i get:

video/efi_uga.c:102: Display controller: 1:0.0
Device id: 40710de
video/efi_uga.c:131:MMIO(0):0xd2000000
video/efi_uga.c:131:VMEM(1):0xc0000000
video/efi_uga.c:131:MMIO(3):0xd0000000

Thanks for your help metatech!

OK it looks normal.

Can you add "initcall_debug" to your kernel parameters and look for "efifb" in the files
/var/log/kern.log.[0-n].

metatech

[tschuliaen]

OK it looks normal.

Can you add "initcall_debug" to your kernel parameters and look for "efifb" in the files
/var/log/kern.log.[0-n].

metatech

Here comes the kern log:

Nov 19 21:09:51 joesmbp kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz root=/dev/sda3 video=efifb initcall_debug
Nov 19 21:09:51 joesmbp kernel: [    0.424884] calling  efifb_init+0x0/0x1de @ 1
Nov 19 21:09:51 joesmbp kernel: [    0.424893] efifb: dmi detected MacBookPro4,1 - framebuffer at 00000000c0060000 (1920x1200, stride 8192)
Nov 19 21:09:51 joesmbp kernel: [    0.424912] efifb: probing for efifb
Nov 19 21:09:51 joesmbp kernel: [    0.425873] efifb: framebuffer at 0xc0060000, mapped to 0xffffc90005100000, using 7232k, total 7232k
Nov 19 21:09:51 joesmbp kernel: [    0.425878] efifb: mode is 1440x900x32, linelength=8192, pages=1
Nov 19 21:09:51 joesmbp kernel: [    0.425880] efifb: scrolling: redraw
Nov 19 21:09:51 joesmbp kernel: [    0.425883] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 19 21:09:51 joesmbp kernel: [    0.583282] initcall efifb_init+0x0/0x1de returned 0 after 154684 usecs

[metatechbe]

Here comes the kern log:

It seems that the hard-coded resolution for your model in the kernel is not correct. But the other parameters might be wrong as well.
Can you please run the following command under MacOS X :

sudo ioreg -lw0 |grep manufacturer|cut  -b25-80;sudo ioreg -lw0|grep "product-name"|cut -b 25-80;sudo dtrace -qn  'BEGIN{boot_args=((struct  boot_args*)(`PE_state).bootArgs);printf("FrameBufferBase:  0x%08x\nPixelsPerScanLine: %d\nHorizontalResolution:  %d\nVerticalResolution: %d", boot_args->Video.v_baseAddr,  boot_args->Video.v_rowBytes/4, boot_args->Video.v_width,  boot_args->Video.v_height);exit(0)} '

+ how much RAM do you have ?
metatech

[tschuliaen]

It seems that the hard-coded resolution for your model in the kernel is not correct. But the other parameters might be wrong as well.
Can you please run the following command under MacOS X :

sudo ioreg -lw0 |grep manufacturer|cut  -b25-80;sudo ioreg -lw0|grep "product-name"|cut -b 25-80;sudo dtrace -qn  'BEGIN{boot_args=((struct  boot_args*)(`PE_state).bootArgs);printf("FrameBufferBase:  0x%08x\nPixelsPerScanLine: %d\nHorizontalResolution:  %d\nVerticalResolution: %d", boot_args->Video.v_baseAddr,  boot_args->Video.v_rowBytes/4, boot_args->Video.v_width,  boot_args->Video.v_height);exit(0)} '

+ how much RAM do you have ?
metatech

Here the output:

 <"Apple Inc.">
 <"MacBookPro4,1">
FrameBufferBase:  0xc0060000
PixelsPerScanLine: 2048
HorizontalResolution:  1440
VerticalResolution: 900

RAM: 4GB

[metatechbe]

Here the output:

 <"Apple Inc.">
 <"MacBookPro4,1">
FrameBufferBase:  0xc0060000
PixelsPerScanLine: 2048
HorizontalResolution:  1440
VerticalResolution: 900

RAM: 4GB

FrameBufferBase and PixelsPerScanLine are correct for your model, only the resolution is not correct. I am not sure it is the cause of the problem.

Maybe in kern.log, another driver takes over the framebuffer/console after efifb, do you see something like this ? Maybe some driver needs to be blacklisted ?

I am running out of ideas... I hope you will find the problem...

metatech

[tschuliaen]

FrameBufferBase and PixelsPerScanLine are correct for your model, only the resolution is not correct. I am not sure it is the cause of the problem.

Maybe in kern.log, another driver takes over the framebuffer/console after efifb, do you see something like this ? Maybe some driver needs to be blacklisted ?

I am running out of ideas... I hope you will find the problem...

metatech

Ok thank you... I'm not quite getting a clue of the log file, it's attached.

Maybe there needs to be done some patching?

Here http://grub.enbug.org/TestingOnMacbook someone that has tested the MBP4,1 writes: Model details of "drivers/video/efifb.c" were wrong and needed patching/recompiling

I also found that this patch is needed: https://help.ubuntu.com/community/Ma...get=e820.patch

Are they really needed? And do I really have to install the latest nvidia drivers (which I did by the way but I'm not sure whether they are "active"

[metatechbe]

Ok thank you... I'm not quite getting a clue of the log file, it's attached.

Maybe there needs to be done some patching?

You forgot the attachment.

You can also try the "agp=off"
then
Option "NvAgp" "1"
in xorg.conf
then try to blacklist the agp modules
then the other patches you mentioned.

Good luck, keep us posted once you find the solution...
Regards,

metatech

[tschuliaen]

You forgot the attachment.

You can also try the "agp=off"
then
Option "NvAgp" "1"
in xorg.conf
then try to blacklist the agp modules
then the other patches you mentioned.

Good luck, keep us posted once you find the solution...
Regards,

metatech

I have found that in the linux-source/drivers/video/efifb.c the line for my MacBookPro 4,1 is wrong:

        [M_MBP_4] = { "mbp4", 0xc0060000, 2048 * 4, 1920, 1200 },

instead of

        [M_MBP_4] = { "mbp4", 0xc0060000, 2048 * 4, 1440, 900 },

I reckon the config before was for the 17inch modell or just wrong...
I'm now recompiling a kernel, it's the first time I'm doing this, it takes ages and well I'll see whether it was successful later :S

[metatechbe]

tschuliaen,

Is your int10.bin file correct ?
You could also try adding "RenderAccel 0" in xorg.conf…

metatech