Contribute
Register
Status
Not open for further replies.
Hey Rehabman, can I install a bootloader on a separate drive to keep my install more vanilla?

For example:

SSD->Mavericks
HDD Partition 1:Bootloader
HDD Partition 2:Data for OSX

Will I lose any boot speed?

I don't see the point. Put the bootloader on the disk that is always present. The bootloader has very little impact on the level of "vanilla."

The boot loader consists of only four components:
- boot0md installed to the MBR
- boot1h installed to the PBR
- /boot in the root
- /Extra for configuration

I don't see how the location of those items is significant at all...
 
Patch your own DSDT using MaciASL. Rehabman have an awesome version with a plenty and useful repository of DSDT patch that can be applied for the U310.

- IRQ FIX
- RTC FIX
- Brightness fix
- 6 Series USB
- SMBus fix
- IGPU Rename
- HD4000 Low Resolution
- Battery Fix Ux10-Z580
- Advanced Audio Layout 12
- Add the USB Multiplexer too, in order to have Sleep and USB 3.0

I have found a Conexant CX 20590 AppleHDA.kext for 10.9. Again i've been trying to build one on my own but i cannot do the bin patch cause bcc9's script doesn't support this codec. But for now with the kext attached and the Multibeast 6 configuration, you can go on your own in Mavericks.
 

Attachments

  • AppleHDA.kext.zip
    1.5 MB · Views: 226
  • U310.mb
    1.3 KB · Views: 182
Patch your own DSDT using MaciASL. Rehabman have an awesome version with a plenty and useful repository of DSDT patch that can be applied for the U310.

- IRQ FIX
- RTC FIX
- Brightness fix
- 6 Series USB
- SMBus fix
- IGPU Rename
- HD4000 Low Resolution
- Battery Fix Ux10-Z580
- Advanced Audio Layout 12
- Add the USB Multiplexer too, in order to have Sleep and USB 3.0

I have found a Conexant CX 20590 AppleHDA.kext for 10.9. Again i've been trying to build one on my own but i cannot do the bin patch cause bcc9's script doesn't support this codec. But for now with the kext attached and the Multibeast 6 configuration, you can go on your own in Mavericks.

I posted this somewhere already, but here are the mods I made to patch-hda-codecs.pl.

Add to %codec_names_to_num:
Code:
    'Nexant 506e', 0x14f1506e, #aka Conexant 20672 (rehabman)

Add to %codecs_map:
Code:
#per http://www.insanelymac.com/forum/topic/268280-guide-thinkpad-t420-with-mountain-lion/page-9#entry1866235
    'Nexant 506e' => 'ADI 1984B',

Then you can binpatch by passing 'Nexant 506e'. And don't get smart and try to change it to 'Conexant 506e' -- it won't work. It must start with a character that is not valid as a hex digit!
 
I posted this somewhere already, but here are the mods I made to patch-hda-codecs.pl.

Add to %codec_names_to_num:
Code:
    'Nexant 506e', 0x14f1506e, #aka Conexant 20672 (rehabman)

Add to %codecs_map:
Code:
#per http://www.insanelymac.com/forum/topic/268280-guide-thinkpad-t420-with-mountain-lion/page-9#entry1866235
    'Nexant 506e' => 'ADI 1984B',

Then you can binpatch by passing 'Nexant 506e'. And don't get smart and try to change it to 'Conexant 506e' -- it won't work. It must start with a character that is not valid as a hex digit!

Also I posted here (post #277) a "guide" relating to the info here (post #80) for patching this codec on Ux10

Furthermore, to get your HDMI audio working see here (post#295)
 
Please try this kext for 10.9.
That "Clean DSDT" is patched.

Get a clean DSDT, use MacIASL.
http://sourceforge.net/projects/maciasl/

Boot without a DSDT and use MacIASL.

Assuming that you're using Chimera:
Code:
DSDT=null IGPEnabler=Yes IGPlatformID=01660003
Bootflags are CaSe sensitive..

If you're using Chameleon the bootflags are different:
Code:
DSDT=null GraphicsEnabler=Yes IntelCapriFB=3

Once you boot with that open MacIASL and it will automatically open your System DSDT.
 
That's what I thought as well at first but I don't see the problem in either of the DSDTs that uploaded.
Can you tell from IOReg?
 
Just upgraded mine.
Only thing missing now is
AppleHDA
and
AppleIntelFramebufferCapri

Can anyone upload working modded for 10.9

I tried messing aroudn with the HDA but causes issues at boot "581 assertion" slows down boot and still no sound.

Everything else is running smooth.
 
That's what I thought as well at first but I don't see the problem in either of the DSDTs that were uploaded..
Can you tell from ioreg?

Yes... I extract the DSDT "in use" from the ioreg. Because a lot of times people are "file management challenged" and are not really able to know which DSDT they actually have loading...

This is how you do it:
- open the ioreg in IORegistryExplorer
- click on AppleACPIPlatformExpert
- expand 'ACPI Tables' on the right
- find the DSDT bits
- click on it (turns blue)
- click at the beginning of the hex byte (character after the '<') to anchor the beginning of the selection
- scroll down to the end of the DSDT bits
- shift+click at the end to select all the hex bytes
- right click Copy (or Command+C)
- go into Terminal and type 'pbpaste|xxd -r -p>dsdt.aml && open dsdt.aml'
- the DSDT should open into MaciASL and you can then examine it

I usually just apply the patch I think is missing and see if there's changes. If there are, then the patch probably was not used.

In this case, there is some sort of IRQ patch used, but it is not the one from my repo. Better to use the actual one than something else then move on to the next possible cause... For example... the overkill in the HDEF _DSM (should be just "Audio Layout 12" not "Audio Layout 12 (advanced")).

Of course, there is lots of other places to make a mistake. Installing the wrong AppleHDA for example...
 
yes... I extract the dsdt "in use" from the ioreg. Because a lot of times people are "file management challenged" and are not really able to know which dsdt they actually have loading...

This is how you do it:
- open the ioreg in ioregistryexplorer
- click on appleacpiplatformexpert
- expand 'acpi tables' on the right
- find the dsdt bits
- click on it (turns blue)
- click at the beginning of the hex byte (character after the '<') to anchor the beginning of the selection
- scroll down to the end of the dsdt bits
- shift+click at the end to select all the hex bytes
- right click copy (or command+c)
- go into terminal and type 'pbpaste|xxd -r -p>dsdt.aml && open dsdt.aml'
- the dsdt should open into maciasl and you can then examine it

i usually just apply the patch i think is missing and see if there's changes. If there are, then the patch probably was not used.

In this case, there is some sort of irq patch used, but it is not the one from my repo. Better to use the actual one than something else then move on to the next possible cause... For example... The overkill in the hdef _dsm (should be just "audio layout 12" not "audio layout 12 (advanced")).

Of course, there is lots of other places to make a mistake. Installing the wrong applehda for example...

+1 awesomeness i looked at the dsdt in the ioreg posted below.
thanks.
 
Hi everyone,
I have an issue whit my ideapad u310. I used Unibeast 3.0.1 install method with its laptop support. I was able to install both, Maverick and Mountain Lion, but I can't boot into os. I tried disabling almost everything in bios but without luck. I have an ideapad with i7-3537u cpu. It always freezes with Missing Bloetooth Controller Transport error. Please help me.
 

Attachments

  • image.jpg
    image.jpg
    921.9 KB · Views: 248
Status
Not open for further replies.
Back
Top