Jump to content

TP-Link TL-WN851N - connection dropping


  • Please log in to reply
45 replies to this topic

#21
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida

Thank you very much! I just loaded the new DSDT and I'll see if the problem's fixed. :)

So, what was the thing you mentioned about SLI? I don't use SLI but I'm curious...also, what were you talking about with the SBUS? :)

Funny thing about the RTC, because I had fixed that last one so it wouldn't reset CMOS...guess I was still wrong. :P


isli
		Method (ISLI, 0, NotSerialized)
		{
			If (CondRefOf (_OSI, Local0))
			{
				If (_OSI ("Linux")) // Darwin ?
				{
					Return (One)
				}
				Else
				{
					Return (Zero)
				}
			}
			Else
			{
				Return (Zero)
			}
		}
and this reacts to it
Method (GUSB, 0, NotSerialized)
	{
		If (ISLI ()) //  1 or zero? Else SMI2 (0xBA)
		{
			Return (Zero)
		}
		Else
		{
			Return (SMI2 (0xBA))
		}
	}
amd this in wak also
Method (_WAK, 1, NotSerialized)
	{
		If (LEqual (Arg0, 0x04)) // sleep state S4
		{
			GUSB () // Zero or SMI (0xBA) ?
		}

i think ISLI isnt SLi but a wake parameter for GUSB ?? as in usb wake from s4 ?
SMI (0xBA) is the parameter that matters on wake.

Intel Sleep LInux ?

SBUS
Device (SBUS)
		{
			Name (_ADR, 0x001F0003)
search for 001F0003 in any dsdt to find sbus

is missing on dells a lot
so i added this basic SBUS of ich8= 283E
Device (SBUS)
		{
			Name (_ADR, 0x001F0003)
			Device (BUS0)
			{
				Name (_CID, "smbus")
				Name (_ADR, Zero)
				Device (DVL0)
				{
					Name (_ADR, 0x57)
					Name (_CID, "diagsvault")
				}
			}

			Method (_DSM, 4, NotSerialized)
			{
				Store (Package (0x0A)
					{
						"built-in",
						Buffer (One)
						{
							0x00
						},

						"name",
						"pci8086,283e",
						"device-id",
						Buffer (0x04)
						{
							0x3E, 0x28, 0x00, 0x00
						},

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

						"subsystem-vendor-id",
						Buffer (0x04)
						{
							0x6B, 0x10, 0x00, 0x00
						}
					}, Local0)
				DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
				Return (Local0)
			}
		}

last thing missing is IRQ removals. i have to check it in detail.
with your testing =
DSDT=hd(0,2)/Extra/testdsdt.aml

#22
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
Thanks for all the patches. Wireless works like a charm. :)

However, 10.6.8 still bombs...hope I can get it worked out. :(

#23
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
try macpro3,1 smbios

whats the error log ? try -v -f npci=0x2000

try this ... i found LPC was not loading so i faked device id ich8 lpc

Attached Files



#24
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
I have a MacPro1,1 SMBIOS because I have a Pentium D (thinking that 1,1 is closest in manufacturing year to the Pentium D), is this wrong?

The npci flag fixed it! :D Before it would boot successfully but a garbled screen would be displayed; as far as I know there were no errors, but now it will boot with QE/CI in 10.6.8! Thank you, thank you!! :D (I did add the npci flag in my org.chameleon.boot.plist)

Now, there are a couple annoyances; for one, wireless is having problems again...this time, when I try to turn it on in Sys Prefs, it beachballs for about 5 seconds and doesn't end up turning AirPort on. What do you think is the matter? Fixed by installing /System/Library/SystemConfiguration/IO80211AirPortMonitor.bundle. :) I've noticed that the computer is in general not as fast to respond as in 10.6.7 (and the login window doesn't come in as smoothly as usual), and looking in activity monitor the kernel_task process takes up 60-65 threads? Is this normal?

I still need to load the DSDT; once I do I will report back with results.

#25
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
ive noticed in laptops the macbookpro4,1 made wireless not work and laggy overall response.. make sure u check smbios with chameleon wizard
try imac8 or 9 or 10

io80211AirportMonitor.bundle

#26
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
I loaded the new DSDT and swapped out nawcom's legacy kernel with AnV's, and now the lag is gone...:) So that leaves one issue left:

I can't figure out for the life of me how to switch en1 and en0. Now I'm getting the "Your device or computer can't be verified" error in the App Store that I didn't have w/ 10.6.7...I tried unloading and reloading the reloading the networking kexts one at a time, but that didn't work. What can I do?

Thank you for all the help. :)

#27
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
isli seems related to usb wakeup for windows or linux.
dells sometimes have sbus missing.
if rtc was fixed with 0x10 .. thats news to me

#28
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
Sorry - RTC was not fixed by 0x10; I had forgotten what I had fixed it with and apparently I gave you the wrong DSDT w/out the RTC fix...I used 0x02. :)

Do you know what I can do to swap en0 and en1? Fixed; changed NetworkInterfaces.plist inside /Library/Preferences/SystemConfiguration. :) However, the App Store still doesn't work right... Fixed by enabling EthernetBuiltIn in org.chameleon.boot.plist. :D With the exception of audio aggregate devices, my hackintosh is fully functional now!! Thank you so much for your great help!

#29
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
yes i left it 0x10 cause u mentioned u fixed. change it to 0x08 or 0x02

#30
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
I use 0x02.

#31
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
Problem again...

Wireless is dropping again...what could be up this time?

My DSDT: Attached File  dsdt.aml.zip   4.61KB   1 downloads

#32
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
try the netkas patched iopcifamilly (darwinx posted a link in the dsdt gguide for m1330 m1530)

#33
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
I'm thinking that it might have also been a kernel issue...my new build with a Core 2 Quad (using vanilla kernel) has not had a connection drop in Snow or Lion. I'll report back if something does happen (I'll try the patched IOPCIFamily first).

#34
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
yea kernel will do it.

#35
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
Now another problem...my oh my, I am getting frustrated...:P

Well, now it's with the 10.7.4 update. When I upgraded to Lion (10.7.2 initially), I patched the AirPortAtheros21.kext with 168c,29, and it worked right away. Then, when I updated to 10.7.3, it gave me an error something like "The super class viable for xxxx is incorrect - make sure your kext is built with the correct headers". Super weird, I thought, so I simply restored (via Time Machine) my old kext (the entire IO80211Family, not just the Atheros plugin) and it worked again. Now, I've updated to 10.7.4, I got the same error, but the kext from 10.7.2 did not work this time. :( Upon googling some info, I tried a few different kexts that said they would change things. All of them said that same build error. I also tried the IO80211Family.kext from my MacBook with 10.7.4 (also uses AirPortAtheros21.kext), but no go. As a last resort, I tried restoring the 10.7.2 IO80211Family.kext with the 10.7.4 AirPortAtheros21 plugin, and...the Atheros plugin has the same problems as the IO80211Family. :(

The only kext I can get to fully load is the one from 10.7.2, but with that kext it says "WiFi - no hardware found", and of course I cannot turn WiFi on in Sys Prefs either. Is this a DSDT issue? Is the IO80211Family open-sourced, so I could manually build it correctly? I am completely confused at the moment...

Thanks,
Pooky

#36
LatinMcG

LatinMcG

    Insanely digesting DSDT

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,508 posts
  • Gender:Male
  • Location:Tampa, Florida
sounds like dependency issues of ionetworkingfamily. or apppleacpi 1.3.5 needed.or platform kext.

try a fresh install on a partition.

#37
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
Got it. :) I was using another IONetworkingFamily from the ModCD that was overriding the Lion one...deleting the old one worked, my network interfaces (Ethernet & WiFi) work again. :D

#38
SunLizard

SunLizard

    InsanelyMac Protégé

  • Members
  • PipPip
  • 82 posts
PookyMac Man,

I have a similar card (also a late gift) the TL-WN851ND. I put it in a 10.7.0 Lion build on a similar motherboard to you.

The card is recognized but there are other interface problems which I believe are left over from the previous Wifi card I had in the machine. What combination of .kexts did you actually end up using to get your wifi back?

Thanks!

#39
PookyMacMan

PookyMacMan

    InsanelyMac Legend

  • Moderators
  • 1,445 posts
  • Gender:Male
  • Location:Earth–Western Hemisphere, specifically
  • Interests:Computer science, engineering, trumpet performance, and a host of others. :D
The card is recognized? Have you verified that for certain? Check in System Information > Software > WiFi.

All I did was patch the AirPortAtheros21.kext inside /System/Library/Extensions/IO80211Family/Contents/PlugIns with my device ID, in my case 0029, like so (in Terminal)
sudo nano /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros21.kext/Contents/Info.plist
Then I looked for:
<key>IOPCINameMatch</key>
Below it I deleted all the entries except for <string>pci168c,2a</string> and changed the 2a to 29 (my device ID). Then Save by pressing Control-X > y > Enter. Update the kext caches and that should get your card working.

#40
SunLizard

SunLizard

    InsanelyMac Protégé

  • Members
  • PipPip
  • 82 posts
PookyMacMan,

It seems to be recognized in software (see Screenshot) but I can't turn on the device in network settings...

I've discovered there is a chipset difference between the 851N and the 851ND... so perhaps the DeviceID change you suggested (that I did try) might not fix my issues.

I looked at trying to fool around with the DSDT file to add the device ID there but, quite frankly, I get lost in that stuff quite quickly, I'm afraid.

Thanks for your response though, it was something I hadn't tried.

Take care.

Attached Files







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy