Slice

try FN+F12

 

Keyboard works but in limited range. From dark to twilight. But not to bright. While slides does.

Seems to confirm. After restart I has very low brightness that can't be increased by keyboard. I have to move brightness slider in Display prefPane to make normal brightness. There should be a solution like correcting DSDT. Don't know yet.

Just tried it and I see this strange (-) value

This value should be GPU temperature that you have no. We may set some fixed value by FakeSMC.info.plist: TG0D = 25.

And the window correspond to FAN regulator so don't look in it.

 

I think these several posts are offtopic and must be moved to separate thread like FakeSMC monitoring.

Right now I'm using ACPIMonitor + IntelCPUMonitor cause I get the extra voltage sensor.

It's correct. And I can propose you to use smcK-stat-i application to see also CPU speed.

smcK-Stat-i.app.zip

 

 

I have tried your corrections. Few comments/questions:

- I like what you did with OSID method - nice and simple now. I was impersonating Windows 2006 as Darwin before.

- Can you tell me what is the purpose for moving those three IO's from MB2 to PIC device?

Dunno why Dell create that strange MB2 device. Looks like a mistake. Moreover IRQ0 here is a mistake preventing HPET to works. But HPET is not needed for Windows so Dell is not careful.

I previously did the same move for my Dell Inspiron and got many improvements.

IO port 0x20 is on first IPIC chip, 0xA0 on second, and 0x4d0 is trigger edge/level interrupts. So they are definitely relies to IPIC device.

- I have tried the FSAM device with your ACPIMonitor but this worked for a while (extra cpu heat sink in sensors) and stopped.

- I see Airport Card sensor with no value - strange

I am not clear how you get Airport sensor (TW0P key). It appears in Info.plist? Also strange why ACPIMonitor stopped. First time it happened.

May be better to do

					Method (TCPU,  0, NotSerialized)  // read value
				{ 
                                               Store(\_TZ.THM._TMP, Local0)
					Return (Local0)
				}

 

tried it now i do not have video black screen on boot. i tried injection,Graphics enabler, diffrent bootloaders and modules, only thing that worked was adding video kexts to extra which defeats the need for dsdt. but thanks for at least trying to help me much appreciated.

 

My DSDT has no Video injection. It is for all other purpose. HPET, brightness, correct interrupts...

I edited my previous post before I saw the answer.

I tested that version of FakeSMC once, can't remember why we did use it, but i seem to recall alot of problems, i guess when you get the D420 you can do some experiments with it.

New FakeSMC can't give you any problem. Dunno what you mean. I saw thousand tests.

 

The choice of MBA1,1 was because of several things, first of all to get support for "Remote disc" (since the D4x0 dosent have a build-in drive), second of all because of the "neat'ness" in having it identified as a MBA and latestly because performance for some reason seemed best best - offcourse - i could be mistaken.

Performance issue may relate to the plist I uploaded above. But 430 has a Merom while 420 has a Yonah. It's a difference.

 

Each Latitude "more or less" have their own dsdt.aml in the EDP, you can find them in the dropbox dir as said before.

 

Have a look at the D4x0 one, and let me know if you think something is missing....

My previous post.

FakeSMC latest version is 3.1.0.

New version proposes to you temperature and FAN monitoring.

Full explanation here

New version here

 

And a question about MacModel. Why MacBookAir? It has x3100 graphics and Merom CPU while 4x0 has GMA950 and Yonah CPU.

The MacBook1,1 looks to be the best choice.

And we need to correct IOPlatformPluginFamily for the model

MacBook1_1.plist.zip

 

 

25.02.2011

Some corrections for Yonah and Merom CPU

IntelCPUMonitor.kext-rev480.zip

. here is my dsdt unmodified from linux

 

I can propose my correction. I didn't make correction for USB and Sound b/c I don't know dependencies: your bootloader and drivers.

Check HPET and speedstep if any.

I also made a device for ACPImonitor used with FakeSMC 3.1.

dsdt_from_Slice.zip

that probably why bootloader never finds Hpet.. and yes i can adjust brightness from display menu.. here is my dsdt unmodified from linux

 

Look here

http://www.duxcw.com/faq/irq/irq.htm

HPET must not have IRQ2.

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)

I don't know why you speak about VoodooBattery and battery life in the thread of bootloader. No reason for any relation.

I do not like VoodooBattery, I prefer AppleACPIBatteryManager and iStatPro to look Battery life.

 

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?

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)

I drop new revision RC5m-708 into Dropbox. Did you see it?

Contents of the archive

RC5m-708:
boot			-- put into root of bootable partition, but not EFI!
CHANGES
etc:
	rc.local    -- copy to /private/etc/
	rc.shutdown.local
Extra:
	BootHelp.txt  -- help to you during boot
	com.apple.Boot.plist  -- change to your needs
	Extensions:  -- empty
		10.5:
		10.6:
		Common:
	modules:   -- choose what patches you need
		ACPIPatcher.dylib   -- load patched DSDT 
		ATI5000Enabler.dylib  -- for RadeonHD5000
		GraphicsEnabler.dylib  -- for IntelGMA, nVidia, ATI4000
		GUI.dylib    		-- obligatory
		HPET.dylib			-- if HPET is not worked
		KernelPatcher.dylib -- for Atom CPU
		KextPatcher.dylib   -- for AppleHDA
		klibc.dylib			-- obligatory
		Memory.dylib		-- RAM type and volume cosmetics
		NetbookInstaller.dylib  -- lapic patch. I dont need it.
		Networking.dylib	-- for LAN anf WiFi. Dunno for a why.
		NVRAM.dylib			-- for testing. do nothing
		Resolution.dylib	-- Autoresolution during boot
		Symbols.dylib    	-- obligatory 
		USBFix.dylib		-- preferable
	smbios.plist -- change to your needs
	Themes:
		Default:		-- obligatory
			background.png
			boot.png
			device_cdrom_o.png
			device_cdrom.png
			device_ext3_o.png
			device_ext3.png
			device_fat_o.png
			device_fat.png
			device_fat16.png
			device_fat32.png
			device_generic_o.png
			device_generic.png
			device_hfsplus_o.png
			device_hfsplus.png
			device_hfsraid_o.png
			device_hfsraid.png
			device_ntfs_o.png
			device_ntfs.png
			device_scroll_next.png
			device_scroll_prev.png
			device_selection.png
			font_console.png
			font_small.png
			logo.png
			menu_boot.png
			menu_help.png
			menu_ignore_caches_disabled.png
			menu_ignore_caches.png
			menu_memory_info.png
			menu_selection.png
			menu_single_user_disabled.png
			menu_single_user.png
			menu_verbose_disabled.png
			menu_verbose.png
			menu_video_info.png
			progress_bar_background.png
			progress_bar.png
			text_scroll_next.png
			text_scroll_prev.png
			theme.plist
			thumb.png
		Pinktink:
			logo.png
			theme.plist
		Twilight:
			font_small.png
			logo.png
			theme.plist
nvram.inf		-- for testing NVRAM modules
TODO			-- for developers

 

Some feedback?

If you means Chameleon from trunk than the history is follow:

rev654 - changes in p-states generator by Mozodojo

rev699 - changes in bdmesg by Meklort. Now the utility is i386+x86_64 arch

 

So bootloader had no any changes since rev654.

All revision changes appear due to branches.

Hello, guys!

Please wait for a release. At now it is beta version.