Jump to content
Thund3rbolt

Slice's newest bootloader

Recommended Posts

Some feedback?

I'm testing it on D630 X3100 without dsdt in /Extra

 

a. user interaction is needed during boot (flashing "\") stops

- at this point pressing any key continues booting | deleting ATI5000Enabler.dylib fixes it

 

b. Auto resolution is not working during boot (standard 1024x768)

- adding Graphic Mode = 1280x800x32 has no result

 

c. black screen in graphic mode (with and without GraphicsEnabler=Yes)

Share this post


Link to post
Share on other sites

Without my own test on the same hardware I can't say anything. The bootloader rev708 works fine on Dell Inspiron 1525. (Yes, exclude ATI5000)

Share this post


Link to post
Share on other sites

Without my own test on the same hardware I can't say anything. The bootloader rev708 works fine on Dell Inspiron 1525. (Yes, exclude ATI5000)

It seems like the boot loader is expecting higher resolution display (mine is 1280x800). Cause I know this effect from faulty AAPL01,DualLink injection.

Resolution up to 1280x800:

"AAPL01,DualLink", 
Buffer (0x04)
{ 0x00, 0x00, 0x00, 0x00 },

For higher resolution

"AAPL01,DualLink", 
Buffer (0x04)
{ 0x01, 0x00, 0x00, 0x00 },

Share this post


Link to post
Share on other sites

Well Slice I seem to have all of the problems that Mariusz has plus when i put the machine to sleep it wakes back up instantly like if something was being called on the bus.. I'm using a dsdt mariusz compiled which worked for me previously...

 

also if this module loaded does it interfere with applehdadisabler or voodoohda

KextPatcher.dylib -- for AppleHDA

dsdt.aml.zip

Share this post


Link to post
Share on other sites

It seems like the boot loader is expecting higher resolution display (mine is 1280x800). Cause I know this effect from faulty AAPL01,DualLink injection.

Resolution up to 1280x800:

"AAPL01,DualLink", 
Buffer (0x04)
{ 0x00, 0x00, 0x00, 0x00 },

For higher resolution

"AAPL01,DualLink", 
Buffer (0x04)
{ 0x01, 0x00, 0x00, 0x00 },

 

I did it already.

[color=#D7000F][font=Menlo][size=2]	if(is_module_loaded("Resolution.dylib"))[/size][/font][/color]	{

	getResolution(&screen_params[0], &screen_params[1], &screen_params[2]);

	gDualLink =((screen_params[0] * screen_params[1]) > (1<<20))?1:0;

	msglog("GUI module screen width=%d height=%d\n",(int)screen_params[0], (int)screen_params[1]);


[font=Menlo][size=2]	}[/size][/font]

 

May be some mistake here?

Share this post


Link to post
Share on other sites

I did it already.

[color=#D7000F][font=Menlo][size=2]	if(is_module_loaded("Resolution.dylib"))[/size][/font][/color]	{

	getResolution(&screen_params[0], &screen_params[1], &screen_params[2]);

	gDualLink =((screen_params[0] * screen_params[1]) > (1<<20))?1:0;

	msglog("GUI module screen width=%d height=%d\n",(int)screen_params[0], (int)screen_params[1]);


[font=Menlo][size=2]	}[/size][/font]

 

May be some mistake here?

For my quick look logic the code looks good...

But maybe this will help tracking this case. Just tried the revision 691 and with GraphicEnabler=Yes and Graphic Mode set to 1280x800x32 I have a proper resolution when I do this simple steps:

I enter the text mode during boot (pressing TAB) and go back to correct (1280x800) graphic mode. This is the same case with my D430 on GMA950 and D630 with X3100. Maybe you can track it down by checking the old GraphicsEnabler.dylib and Resolution.dylib code. Just a thought.

PS. Attached bdmesg log

bdmesg-D630-Mariusz.txt

Share this post


Link to post
Share on other sites

Well Slice I seem to have all of the problems that Mariusz has plus when i put the machine to sleep it wakes back up instantly like if something was being called on the bus.. I'm using a dsdt mariusz compiled which worked for me previously...

 

also if this module loaded does it interfere with applehdadisabler or voodoohda

KextPatcher.dylib -- for AppleHDA

 

I made a quick look into your DSDT. It is a subject to further work.

    Name (W98S, "Microsoft Windows")
   Name (NT5S, "Microsoft Windows NT")
   Name (WINM, "Microsoft WindowsME: Millennium Edition")
   Name (WXP, "Windows 2001")
   Name (WLG, "Windows 2006")

 

Where is a "Darwin"? Because of next operation

                If (LGreaterEqual (OSID (), 0x10))
               {
                   Notify (\_SB.PCI0, Zero)
                   Sleep (0x03E8)
               }
               Else
               {

 

Is OSID greater then 10? (OS identification). Your ACPI doesn't know "Darwin" and set "Unknown".

 

Device (PNLF) inside LID? It's new for me. Does brightness works with slider in Display.prefPane?

 

Strange Device (MB2) with IRQ0. So why HPET has IRQ2 that must be @IPIC.

 

Useless devices SPK and ECP. (speaker and Parallel Port)

Share this post


Link to post
Share on other sites

×
×
  • Create New...