Page 26 of 89 FirstFirst ... 1624252627283676 ... LastLast
Results 251 to 260 of 883

Thread: Macbook Pro 8,1 + Maverick

  1. #251
    Join Date
    Nov 2005
    Beans
    60

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by axflash View Post
    The Intel graphics alone would make it totally worth it in my book. While it is extremely nice to not have to rely on the closed nvidia driver on the laptop, the power management on radeon is pretty pathetic. Even in the low power mode, I still end up with a laptop that eats ~18W or power. And in the low power mode, scrolling is painfully slow, choppy, and almost unbearable. Higher power modes work great, but consume way too much power to be useful (adds about 10W even for the next mode, "mid"). Dynamic modes are useless, as the screen flickers when switching clocks. At least the nvidia chip had good power management.

    Using the Intel chip would cut 2-3W off the power. That's essentially an extra hour of computer time when traveling.

    So I'd say that being able to use the Intel graphics would be immensely useful. I spent a few hours playing with EFI boot, and the results weren't too great. It boots, but graphics output was garbled (dual link issue, I believe, there's a patch). It would not come out of suspend either.
    I'm good with radeon performance on low, and really, battery life is not my big issue here.

    That said, I'd be thrilled to have EFI boot, just for Intel graphics.

    No luck (and I did try the outb solution posted, no good.)

  2. #252
    Join Date
    Apr 2011
    Beans
    9

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by paul.lovvik View Post
    I had exactly the same problem and struggled with every combination I could think of. Finally I tried using the bootable CD and the bootable USB stick together. I booted from the CD, and during the install it mounted the USB stick and continued installing.

    Certainly not elegant, but it did install.
    Does your DVD/CD drive work after install?

    I got the same problem on MBP 8,2 - I can not boot from 11.04 beta 2 Live CD alone.

    After booting with 11.04 beta2 Live CD and USB, MBP did boot, but I could not see CD device in /dev directory.

    Here is what I get in dmesg. Can someone explain what does "[ 24.337060] ata2.00: disabled" means in this case. Does it mean that CD drive was disabled?


    Code:
    dmesg |grep ata2.00
    [    6.002792] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [    6.022976] ata2.00: ATAPI: MATSHITADVD-R   UJ-898, HE13, max UDMA/100
    [    6.062814] ata2.00: configured for UDMA/100
    [   11.061151] ata2.00: qc timeout (cmd 0xa0)
    [   11.061222] ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
    [   12.640678] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [   12.700718] ata2.00: configured for UDMA/100
    [   17.698968] ata2.00: qc timeout (cmd 0xa0)
    [   17.699049] ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
    [   17.699107] ata2.00: limiting SATA link speed to 1.5 Gbps
    [   17.699161] ata2.00: limiting speed to UDMA/100:PIO3
    [   19.278565] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [   19.338614] ata2.00: configured for UDMA/100
    [   24.336930] ata2.00: qc timeout (cmd 0xa0)
    [   24.337005] ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
    [   24.337060] ata2.00: disabled
    [   24.337130] ata2.00: hard resetting link
    [   25.916461] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

  3. #253
    Join Date
    Feb 2011
    Location
    USA
    Beans
    46

    Re: Macbook Pro 8,1 + Maverick

    Anyone know how to get the keyboard backlight off in classic-noeffects?
    "Like computer viruses, successful mind viruses will tend to be hard for their victims to detect. If you are the victim of one, the chances are that you won't know it, and may even vigorously deny it." -- Richard Dawkins

  4. #254
    Join Date
    Jun 2005
    Beans
    100

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by Anon7-2521 View Post
    Anyone know how to get the keyboard backlight off in classic-noeffects?
    Yes, just pressing the F5 key to lower it until its off. This works for me (I have mactel ppa stuff installed)

  5. #255
    Join Date
    Nov 2005
    Beans
    60

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by Sloth View Post
    I'm good with radeon performance on low, and really, battery life is not my big issue here.

    That said, I'd be thrilled to have EFI boot, just for Intel graphics.

    No luck (and I did try the outb solution posted, no good.)
    I finally managed to get this to work, and work perfectly, including resume.

    And it was totally, totally worth doing. First time I saw <12W of power usage, I was sold. 7 hours on battery, and I just pulled the equivalent of a 10W lightbulb out of my lap.

    I'll do a write up. Basically, I'm within spitting distance of having a MBP 8,3 working perfectly except for wireless, using the integrated graphics. The only outstanding issue is the backlight, which I know how to fix, just need to wrangle it a bit.

    This is awesome.

  6. #256
    Join Date
    Oct 2005
    Location
    Earth, Europe, The Nether
    Beans
    10

    Re: Macbook Pro 8,1 + Maverick

    Would be great to read your writeup! Have you already contact the Mactel mailinglist to inform them of this? Would be grand if your changes could become part of Natty

  7. #257
    Join Date
    Sep 2010
    Beans
    50

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by Sloth View Post
    I finally managed to get this to work, and work perfectly, including resume.

    And it was totally, totally worth doing. First time I saw <12W of power usage, I was sold. 7 hours on battery, and I just pulled the equivalent of a 10W lightbulb out of my lap.

    I'll do a write up. Basically, I'm within spitting distance of having a MBP 8,3 working perfectly except for wireless, using the integrated graphics. The only outstanding issue is the backlight, which I know how to fix, just need to wrangle it a bit.

    This is awesome.
    Awesome is indeed the word! Would be great if you could do a writeup, would save the rest of us a lot of time. Intel graphics is the only missing piece here, I'm pretty sick of 18-19W idle power and warmish laptop (and the battery life that follows).

  8. #258
    Join Date
    Feb 2011
    Location
    USA
    Beans
    46

    Re: Macbook Pro 8,1 + Maverick

    Quote Originally Posted by dmb View Post
    Yes, just pressing the F5 key to lower it until its off. This works for me (I have mactel ppa stuff installed)
    Doesn't work in classic-no effects. Only with effects.
    "Like computer viruses, successful mind viruses will tend to be hard for their victims to detect. If you are the victim of one, the chances are that you won't know it, and may even vigorously deny it." -- Richard Dawkins

  9. #259
    Join Date
    Nov 2005
    Beans
    60

    Re: Macbook Pro 8,1 + Maverick

    Home sick, but here's a quick write up.

    Overview

    This document details how to setup a MacBook Pro 8,3 running Ubuntu Linux, booting in EFI (i.e., native, not BIOS) mode. While designed for the MBP 8,3, similar steps should work with other Macs using Intel integrated graphics, and - with modification - other Macbooks with two GPUs.

    This is not a simple process, so the first question that needs to be answered is why you might want to do this. There are two primary reasons:

    * In EFI mode, you can enable the integrated graphics controller amd turn off the discrete controller. This results in quite a bit of power saving and, if you do not need the power of the discrete GPU, is greatly superior. You will get better battery life and less heat. If you just want desktop effects, the discrete GPU is overkill.

    * AHCI mode is enabled in EFI. You can enable AHCI if you are booting using BIOS mode, but it's a pain.

    There are downsides of doing this as well. Frankly, it's a pain to set this up and you really need to know what you are doing. Not for the faint of heart.

    But it is *very* worth it, for battery/heat reasons alone. Using the discrete GPU, I was never able to get below 21W of power usage. I've seen <12W using the integrated GPU.

    You do this at your own risk. If it eats your MBP, not my problem.

    Getting started

    First, get everything working as best you can using the traditional (BIOS) install. That's your base system, and will be used for most everything else.

    Next, you need to install grub2 efi. A guide can be found here: http://grub.enbug.org/TestingOnUEFI?...stingOnMacbook

    You will need to dump the BIOS and int 10 to get everything working, so don't skip this step:

    Code:
    dd if=/dev/mem of=/boot/vbios.bin bs=65536 skip=12 count=1
    dd if=/dev/mem of=/boot/int10.bin bs=4 skip=16 count=1
    The grub menu entry you want to setup looks like this. I've added comments to make it clear:

    Code:
    menuentry 'Ubuntu, with Linux 2.6.39-rc4+' --class ubuntu --class gnu-linux --class gnu --class os {
            recordfail
            set gfxpayload=$linux_gfx_mode
            insmod part_gpt
            insmod ext2
            set root='(/dev/sda,gpt3)'
            search --no-floppy --fs-uuid --set=root e945d848-dc1e-4804-9474-1d1e1c5ad918
            loadbios /boot/vbios.bin /boot/int10.bin
    # Switch gmux to IGD
            outb 0x728 1
            outb 0x710 2
            outb 0x740 2
    # Powers down ATI
            outb 0x750 0
            linux   /boot/vmlinuz-2.6.39-rc4+ root=UUID=e945d848-dc1e-4804-9474-1d1e1c5ad918 ro nosplash noefi i915.lvds_channels=2 reboot=pci acpi_backlight=vendor
            initrd  /boot/initrd.img-2.6.39-rc4+
    }
    Note the outb commands. These are disabling the ATI discrete GPU and switching to the IGD (integrated device.)

    The other kernel parameters are needed to force LVDS detection to work (depends on the patch mentioned below) and warns the acpi driver off of claiming that it controls the backlight (it doesn't.)

    *You will need the LVDS dual channel patch mentioned on the grub2 page* The link is dead; fortunately the patch was recently resubmitted. It can be found here: http://permalink.gmane.org/gmane.com...ers.intel/3826

    You will also need to add/modify your /etc/X11/xorg.conf to look like this:
    Code:
    Section "Device"
            Identifier      "Device0"
            Driver          "intel"
            BusID           "0:2:0"
    EndSection
    Once you've done all of this, you should be able to boot into X. You will not have fans or backlight.

    Fans and Sensors

    Fans and sensors are controlled by the apple SMC chip. This driver is looking for a DMI decode to continue; there is none, so it will not load. In order to patch it to always load, go into your kernel source and make this mod:

    In drivers/hwmon/applesmc.c, disable the dms_check_system by adding "0 && " to the following statement (this is a dirty hack; I'll fix it later.)

    Code:
    static int __init applesmc_init(void)
    {
            int ret;
    
            if (0 && !dmi_check_system(applesmc_whitelist)) {
                    pr_warn("supported laptop not found!\n");
                    ret = -ENODEV;
                    goto out;
            }
    Once you've rebooted with this new kernel, you should have sensors and fan control.

    Backlight
    Now for the backlight. Here are my diffs against drivers/video/backlight/apple_bl.c (in 2.6.39-rc4). You need to add the use_gmux=1 option to the driver load and, for the 8,3, max_brightness=132000

    Code:
    --- a/drivers/video/backlight/apple_bl.c
    +++ b/drivers/video/backlight/apple_bl.c
    @@ -31,6 +31,8 @@ struct hw_data {
     	/* I/O resource to allocate. */
     	unsigned long iostart;
     	unsigned long iolen;
    +	unsigned long io_1_start;
    +	unsigned long io_1_len;
     	/* Backlight operations structure. */
     	const struct backlight_ops backlight_ops;
     	void (*set_brightness)(int);
    @@ -44,6 +46,12 @@ static const struct hw_data *hw_data;
     static int debug;
     module_param_named(debug, debug, int, 0644);
     MODULE_PARM_DESC(debug, "Set to one to enable debugging messages.");
    +static int use_gmux;
    +module_param_named(use_gmux, use_gmux, int, 0644);
    +MODULE_PARM_DESC(use_gmux, "Set to one to use gmux backlight method");
    +static int max_brightness = 132000;
    +module_param_named(max_brightness, max_brightness, int, 0644);
    +MODULE_PARM_DESC(max_brightness, "Set to max allowable brightness");
     
     /*
      * Implementation for machines with Intel chipset.
    @@ -139,6 +147,53 @@ static const struct hw_data nvidia_chipset_data = {
     	.set_brightness = nvidia_chipset_set_brightness,
     };
     
    +#define PORT_BACKLIGHT_1 0x774
    +#define PORT_BACKLIGHT_2 0x10724
    +
    +static void gmux_set_brightness(int intensity)
    +{
    +	outw(0x2f, PORT_BACKLIGHT_2);
    +	outl(intensity, PORT_BACKLIGHT_1);
    +}
    +
    +static int gmux_send_intensity(struct backlight_device *bd)
    +{
    +	int intensity = bd->props.brightness;
    +
    +	if (debug)
    +		printk(KERN_DEBUG DRIVER "setting brightness to %d\n",
    +		       intensity);
    +
    +	gmux_set_brightness(intensity);
    +	return 0;
    +}
    +
    +static int gmux_get_intensity(struct backlight_device *bd)
    +{
    +	int intensity;
    +	intensity = inl(PORT_BACKLIGHT_1);
    +
    +	if (debug)
    +		printk(KERN_DEBUG DRIVER "read brightness of %d\n",
    +		       intensity);
    +
    +	return intensity;
    +}
    +
    +static const struct hw_data gmux_data = {
    +	.iostart = PORT_BACKLIGHT_1,
    +	.iolen = 4,
    +	.io_1_start = PORT_BACKLIGHT_2,
    +	.io_1_len = 2,
    +	.backlight_ops		= {
    +		.options	= BL_CORE_SUSPENDRESUME,
    +		.get_brightness	= gmux_get_intensity,
    +		.update_status	= gmux_send_intensity
    +	},
    +	.set_brightness = gmux_set_brightness,
    +};
    +
    +
     static int __devinit apple_bl_add(struct acpi_device *dev)
     {
     	struct backlight_properties props;
    @@ -152,10 +207,16 @@ static int __devinit apple_bl_add(struct acpi_device *dev)
     		return -ENODEV;
     	}
     
    -	if (host->vendor == PCI_VENDOR_ID_INTEL)
    -		hw_data = &intel_chipset_data;
    -	else if (host->vendor == PCI_VENDOR_ID_NVIDIA)
    -		hw_data = &nvidia_chipset_data;
    +	if(use_gmux == 0) {
    +		if (host->vendor == PCI_VENDOR_ID_INTEL)
    +			hw_data = &intel_chipset_data;
    +		else if (host->vendor == PCI_VENDOR_ID_NVIDIA)
    +			hw_data = &nvidia_chipset_data;
    +	}
    +	else 
    +		hw_data = &gmux_data;
    +	
    +	printk(KERN_ERR DRIVER "host->vendor == %x gmux = %d", host->vendor, use_gmux);
     
     	pci_dev_put(host);
     
    @@ -170,24 +231,38 @@ static int __devinit apple_bl_add(struct acpi_device *dev)
     
     	if (!intensity) {
     		hw_data->set_brightness(1);
    -		if (!hw_data->backlight_ops.get_brightness(NULL))
    +		if (!hw_data->backlight_ops.get_brightness(NULL)) {
    +			printk(KERN_ERR DRIVER "cannot set brightness - no device found\n");
     			return -ENODEV;
    +		}
    +		
     
     		hw_data->set_brightness(0);
     	}
    -
    +	
     	if (!request_region(hw_data->iostart, hw_data->iolen,
    -			    "Apple backlight"))
    -		return -ENXIO;
    +						"Apple backlight")) {
    +		printk(KERN_ERR DRIVER "cannot request backlight region\n");
    +		//		return -ENXIO;
    +	}
    +	if (hw_data->io_1_start != 0 && !request_region(hw_data->io_1_start, hw_data->io_1_len,
    +						"Apple backlight1")) {
    +		printk(KERN_ERR DRIVER "cannot request backlight region 1\n");
    +		//		return -ENXIO;
    +	}
    +	
     
     	memset(&props, 0, sizeof(struct backlight_properties));
     	props.type = BACKLIGHT_PLATFORM;
    -	props.max_brightness = 15;
    -	apple_backlight_device = backlight_device_register("apple_backlight",
    +	props.max_brightness = use_gmux ? max_brightness : 15;
    +	apple_backlight_device = backlight_device_register("acpi_video0",
     				  NULL, NULL, &hw_data->backlight_ops, &props);
     
     	if (IS_ERR(apple_backlight_device)) {
     		release_region(hw_data->iostart, hw_data->iolen);
    +		if(hw_data->io_1_start)
    +			release_region(hw_data->io_1_start, hw_data->io_1_len);
    +		printk(KERN_ERR DRIVER "cannot register device\n");
     		return PTR_ERR(apple_backlight_device);
     	}
     
    @@ -203,6 +278,8 @@ static int __devexit apple_bl_remove(struct acpi_device *dev, int type)
     	backlight_device_unregister(apple_backlight_device);
     
     	release_region(hw_data->iostart, hw_data->iolen);
    +	if(hw_data->io_1_start)
    +		release_region(hw_data->io_1_start, hw_data->io_1_len);
     	hw_data = NULL;
     	return 0;
     }

  10. #260
    Join Date
    Nov 2005
    Beans
    60

    Re: Macbook Pro 8,1 + Maverick

    Got to lie down for a few.

    Next up: fixing video on resume.

Page 26 of 89 FirstFirst ... 1624252627283676 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •