Jump to content
theproto

HP Mini 311 Darwin Project Thread (Part II - CURRENT)

900 posts in this topic

Recommended Posts

No news on AppleHDA, I can't get 10.6.3 beta(s) right now, but I know that Apple is planning to hardcode codecs in AppleHDA, I don't know if this has already been done in 10.6.3. We might have to keep 10.6.2 kexts or find a workaround for VoodooHDA (best solution). I was very busy these days, not much time for playing with the Mini, nor HDA...

You did well to add CPUInjector, I was just thinking about it :thumbsup_anim: Thanks for the job.

Share this post


Link to post
Share on other sites
Advertisement

Could anyone run HPB189 and then dump his/her DMI using "L" or HPBQ189 --savetofile? Please send me the ESCD.DAT

I still have some missing values in mine, and BIOS F12 or greater look for them. (F04 wasn't)

 

It would be a good occasion to unleash DX10 by using the "Vista String" : Press "G" then choose Vista OS. Thank's in advance

Share this post


Link to post
Share on other sites
wow, its been awhile since i've been on here. It's good to see the project up to HF4.

 

And have you noticed theproto's facial hair has grown as well? :wacko:

Share this post


Link to post
Share on other sites

Hi guys! Sorry for my english, it's very bad, but I try to describe how my ploblem with Broadcomm BCM4312 (14e4:4315) was solved.

 

I have another laptop - Fujitsu-Siemens V3205. Wi-Fi card is DELL Wireless 1395 MINI with Broadcomm BCM4312 (HP mini have the same). In Leopard 10.5.8 it's works fine, but in Snow Leopard 10.6.2 doesn't recognized. So I put inject in DSDT:

				Device (ARPT)
			{
				......
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x12)
						{
							"AAPL,slot-name", 
							Buffer (0x08)
							{
								"AirPort"
							}, 

							"device-id", 
							Buffer (0x04)
							{
								0x12, 0x43, 0x00, 0x00
							}, 

							"vendor-id", 
							Buffer (0x04)
							{
								0xE4, 0x14, 0x00, 0x00
							}, 

							"subsystem-id", 
							Buffer (0x04)
							{
								0x86, 0x00, 0x00, 0x00
							}, 

							"subsystem-vendor-id", 
							Buffer (0x04)
							{
								0x6B, 0x10, 0x00, 0x00
							}, 

							"name", 
							Buffer (0x0D)
							{
								"pci14e4,4312"
							}, 

							"model", 
							Buffer (0x13)
							{
								"Dell Wireless 1395"  //Can change to another
							}, 

							"device_type", 
							Buffer (0x08)
							{
								"Airport"
							}, 

							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			  .....
			}

 

Reboot and it's works! Now you can try to test it on HP mini 311c.

 

Also who have laptops with BCM943224 can try this inject:

					Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x12)
						{
							"AAPL,slot-name", 
							Buffer (0x08)
							{
								"AirPort"
							}, 

							"device-id", 
							Buffer (0x04)
							{
								0x53, 0x43, 0x00, 0x00
							}, 

							"vendor-id", 
							Buffer (0x04)
							{
								0xE4, 0x14, 0x00, 0x00
							}, 

							"subsystem-id", 
							Buffer (0x04)
							{
								0x93, 0x00, 0x00, 0x00
							}, 

							"subsystem-vendor-id", 
							Buffer (0x04)
							{
								0x6B, 0x10, 0x00, 0x00
							}, 

							"name", 
							Buffer (0x0D)
							{
								"pci14e4,4353"
							}, 

							"model", 
							Buffer ()
							{
								"AirPort Extreme"  //Can change to another
							}, 

							"device_type", 
							Buffer (0x08)
							{
								"Airport"
							}, 

							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}

 

Good luck!

 

P.S. Sorry if this method was tested.

Share this post


Link to post
Share on other sites

So you are saying this will make the native card in the HP Mini 311 functional in Snow Leopard?

Share this post


Link to post
Share on other sites
So you are saying this will make the native card in the HP Mini 311 functional in Snow Leopard?

Yes. This method helped me to solve my problem with the same card on another laptop, maybe it's help to you with your laptop.

Share this post


Link to post
Share on other sites

well i just tried adding this to the end of my dsdt code and now i boot into a kernel panic

 

EDIT* i just got it to boot off the install dvd, were did you inject the code, and is there anything else you have to do to get the BCM4321 to work?

Share this post


Link to post
Share on other sites
I have the BCM94312HMG

anyone know if this works?

also can anyoen psot a guide on how to use the F.04 thingy?

 

What part of the rules in the first post did you not understand?

 

RULE:

 

1.) ALL HELP and support requests belong in the SUPPORT thread

2.) We repeat ALL HELP and support requests belong in the SUPPORT thread

 

Was it rule number 1? Or was it rule number 2?

 

 

Sincerely,

 

The thread police

Share this post


Link to post
Share on other sites
Hi guys! Sorry for my english, it's very bad, but I try to describe how my ploblem with Broadcomm BCM4312 (14e4:4315) was solved.

 

I have another laptop - Fujitsu-Siemens V3205. Wi-Fi card is DELL Wireless 1395 MINI with Broadcomm BCM4312 (HP mini have the same). In Leopard 10.5.8 it's works fine, but in Snow Leopard 10.6.2 doesn't recognized. So I put inject in DSDT:

				Device (ARPT)
			{
				......
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x12)
						{
							"AAPL,slot-name", 
							Buffer (0x08)
							{
								"AirPort"
							}, 

							"device-id", 
							Buffer (0x04)
							{
								0x12, 0x43, 0x00, 0x00
							}, 

							"vendor-id", 
							Buffer (0x04)
							{
								0xE4, 0x14, 0x00, 0x00
							}, 

							"subsystem-id", 
							Buffer (0x04)
							{
								0x86, 0x00, 0x00, 0x00
							}, 

							"subsystem-vendor-id", 
							Buffer (0x04)
							{
								0x6B, 0x10, 0x00, 0x00
							}, 

							"name", 
							Buffer (0x0D)
							{
								"pci14e4,4312"
							}, 

							"model", 
							Buffer (0x13)
							{
								"Dell Wireless 1395"  //Can change to another
							}, 

							"device_type", 
							Buffer (0x08)
							{
								"Airport"
							}, 

							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			  .....
			}

 

Reboot and it's works! Now you can try to test it on HP mini 311c.

 

Also who have laptops with BCM943224 can try this inject:

					Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x12)
						{
							"AAPL,slot-name", 
							Buffer (0x08)
							{
								"AirPort"
							}, 

							"device-id", 
							Buffer (0x04)
							{
								0x53, 0x43, 0x00, 0x00
							}, 

							"vendor-id", 
							Buffer (0x04)
							{
								0xE4, 0x14, 0x00, 0x00
							}, 

							"subsystem-id", 
							Buffer (0x04)
							{
								0x93, 0x00, 0x00, 0x00
							}, 

							"subsystem-vendor-id", 
							Buffer (0x04)
							{
								0x6B, 0x10, 0x00, 0x00
							}, 

							"name", 
							Buffer (0x0D)
							{
								"pci14e4,4353"
							}, 

							"model", 
							Buffer ()
							{
								"AirPort Extreme"  //Can change to another
							}, 

							"device_type", 
							Buffer (0x08)
							{
								"Airport"
							}, 

							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}

 

Good luck!

 

P.S. Sorry if this method was tested.

 

can anyone confirm if this works?

Share this post


Link to post
Share on other sites

a quick question, I noticed on latest Build HF4

"Boot Camp Assistant" Removed

 

Does this mean, we can not use this to make an Dual Boot Boot Camp for Windows 7 too?

 

If not, what other options can I use to make Dual Boot? w/o format the HD prior for 2 partition?

Share this post


Link to post
Share on other sites
Yes. This method helped me to solve my problem with the same card on another laptop, maybe it's help to you with your laptop.

 

@aydar

 

Can you provide step by step instructions to inject that code into the .dstl file? So we can start testing on that?

 

I couldn't believe it when i was reading your post, i had to read it twice. Thank you!!

Share this post


Link to post
Share on other sites
a quick question, I noticed on latest Build HF4

"Boot Camp Assistant" Removed

 

Does this mean, we can not use this to make an Dual Boot Boot Camp for Windows 7 too?

 

If not, what other options can I use to make Dual Boot? w/o format the HD prior for 2 partition?

 

You just need to use "Disk Utility" instead of the fancy but very basic "Boot Camp Assistant".

 

These changes were made to ensure the distribution is completely legit. Whether installing Mac OS X is or is not is not the question, but all the files distributed in the image are legit, thus a Google Code project could be opened.

 

The modified HP firmware is stored on a server elsewhere separate from the project since it is not licensed or open source code. So while it is recommended to be used with the project and a link is provided, it is in no way distributed with the project.

 

@aydar

 

Can you provide step by step instructions to inject that code into the .dstl file? So we can start testing on that?

 

I couldn't believe it when i was reading your post, i had to read it twice. Thank you!!

 

I've got to be honest here... You should browse around a bit and learn about the DSDT from the many topics coverage it since it can be a bit of a learning curve. You might also need to massage the values depending on the actual card you have.

Share this post


Link to post
Share on other sites

 

Here is a big hint (these are your two MiniPCIe slots in our DSDT):

 

			Device (XVR5)
		{
			Name (_ADR, 0x00150000)
			Name (_PRW, Package (0x02)
			{
				0x11, 
				0x05
			})
			Device (XVS5)
			{
				Name (_ADR, Zero)
				Name (_SUN, One)
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x02)
						{
							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			}
		}

		Device (XVR6)
		{
			Name (_ADR, 0x00160000)
			Name (_PRW, Package (0x02)
			{
				0x11, 
				0x05
			})
			Device (XVS6)
			{
				Name (_ADR, Zero)
				Name (_SUN, One)
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x02)
						{
							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			}
		}

 

Replace the following code (and nothing else):

 

					Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x02)
						{
							"built-in", 
							Buffer (One)
							{
								0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}

Share this post


Link to post
Share on other sites

@theproto

 

If i get this correct, all I need to do Dual Boot.

Is to Boot into SnowLeopard Retail Disk, and Use Disk Utility.

Make 2 Partitions, one for SnowLeo and other for Windows

 

Plus I will need to update my F12 Firmware to Icelord Mod Firmware to get this to work?

 

Only question I keep asking my self, How do I choose between the OSX and Windows/Linux?

Do I use Chameleon? or something else? (Which I need to make an Mini Partition for Chameleon?

Like this Installer on http://www.insanelymac.com/forum/index.php?showtopic=201850 by Dr.Hurt?

 

 

thnx in advance for your guides and suggestions. When this all works out, I may end up writing a easy graphical guide.

Share this post


Link to post
Share on other sites

[TUT] How to Flash MOD BIOS

 

What U Need:

-Manufacture Issued BIOS

-MOD BIOS from Google Search (do not ask where to get it, just google it)

Since theproto did not post it no more. I will do the same.

-MINIDOS (something like LiveXP boot disc) (need to to execute EXE file)

 

#1 download a Up to Date Firmware from Manufacture (Current F13)

#2 Unzip the File, unzip Insyde File again (you need to see the Folder itself, with all the files)

#3 Download the MOD Bios from google search. (just search HP 311 Mod Bios)

#4 extract the MOD Bios file, copy the "3651Fxx0.fd" (xx is the current Bios ##)

#5 copy/replace MOD file to the Manufacture existing File.

#6 now all you have to do, is execute the Insyde Flash exe in the Manufacture Folder to FLASH BIOS

 

##Time of Process may take from 30seconds to 5min

 

TUT done by me, after agnoizing unsucceful BIOS update with Boot From USB with Windows+B key, decide to Flash with EXE. Which is a Success!!

Share this post


Link to post
Share on other sites
[TUT] How to Flash MOD BIOS

 

What U Need:

-Manufacture Issued BIOS

-MOD BIOS from Google Search (do not ask where to get it, just google it)

Since theproto did not post it no more. I will do the same.

-MINIDOS (something like LiveXP boot disc) (need to to execute EXE file)

 

#1 download a Up to Date Firmware from Manufacture (Current F13)

#2 Unzip the File, unzip Insyde File again (you need to see the Folder itself, with all the files)

#3 Download the MOD Bios from google search. (just search HP 311 Mod Bios)

#4 extract the MOD Bios file, copy the "3651Fxx0.fd" (xx is the current Bios ##)

#5 copy/replace MOD file to the Manufacture existing File.

#6 now all you have to do, is execute the Insyde Flash exe in the Manufacture Folder to FLASH BIOS

 

##Time of Process may take from 30seconds to 5min

 

TUT done by me, after agnoizing unsucceful BIOS update with Boot From USB with Windows+B key, decide to Flash with EXE. Which is a Success!!

 

The recovery flash method (documented by the project) is very picky about the actual USB memory device, FS and partition table type. Out of the 7 USB sticks I tried only 3 worked however some may have all their sticks work just fine. These methods are much different (one is primarily for emergency recovery use and the other is for a standard update) but give the exact same results.

 

Good post.

Share this post


Link to post
Share on other sites

So, my understanding is that all of the 311 kexts are now in the EFI partition. Does that mean that verbose booting is unnessesary now? Minor thing, but I have to reset it after every hotfix update.

Share this post


Link to post
Share on other sites

Got Everything Installed. SnowLeopard and Windows 7.

Using Disk Utility. Now the only problem left, is I can Boot into Snow, BUT can not boot into Windows 7.

Inaccessible for Windows 7. How do I fix this problem to make both bootable via selection?

NVM, Got Everything Working!! The way I wanted. Now I can boot Windows and Snowy!!

All Left to do is Update!! :)-_-;)B):lol::D:P;)

Share this post


Link to post
Share on other sites

Has anyone recieved a Kernel Panic during the initial installation. I returned my 311, got a new one and still had the same problem. Should I reburn my copy os Snow Leopard and try again or am i doing something wrong. I can provider a screenshot of the kernel panic if that will help.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×