Contribute
Register

[Guide] Lenovo T430 - El Capitan

Status
Not open for further replies.
Nope...
her "rebranded" the Atheros AR9285 with the Vendor-, Device-, SubVendor- and SubDevice-IDs from the Original Intel Wifi-Card.
In that case the BIOS "thinks" its an original Intel Wifi and wont block the boot process.
http://www.tonymacx86.com/threads/rebranding-the-atheros-928x-cards-the-guide.115110/
But you have to use either a DSDT-Patch for "Device (ARPT)" with the Original IDs or a dedicated AtherosWifiInjector.kext.

Here is my DSDT-Entry for my AR9280 to Original Intel Advanced-N 6205:
Code:
                Device (ARPT)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                    {
                        0x09,
                        0x04
                    })
                    Name (_SUN, One)  // _SUN: Slot User Number
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        Store (Package (0x14)
                            {
                                "AAPL,slot-name",
                                "AirPort",
                                "name",
                                "AirPort Extreme",
                                "model",
                                Buffer (0x37)
                                {
                                    "Atheros AR9x8x 802.11 a/b/g/n Wireless Network Adapter"
                                },

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

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

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

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

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

                                "built-in",
                                Buffer (One)
                                {
                                     0x00                                      
                                },

                                "compatible",
                                "pci168c,30"
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }
                }

Together with FakePCIID and FakePCIID_AR928x_as_xxxx.kext it should work fine.

But be aware... after that, there is no way of using the Card in a dual-boot scenerio, since Windows will also recognize the card as Intel Wifi, but the drivers will not be able to start the device.

With Linux you might be able to create a workaround.
Thank you so much, i'm going to try it out now...
 
Nope...
her "rebranded" the Atheros AR9285 with the Vendor-, Device-, SubVendor- and SubDevice-IDs from the Original Intel Wifi-Card.
In that case the BIOS "thinks" its an original Intel Wifi and wont block the boot process.
http://www.tonymacx86.com/threads/rebranding-the-atheros-928x-cards-the-guide.115110/
But you have to use either a DSDT-Patch for "Device (ARPT)" with the Original IDs or a dedicated AtherosWifiInjector.kext.

Here is my DSDT-Entry for my AR9280 to Original Intel Advanced-N 6205:
Code:
                Device (ARPT)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                    {
                        0x09,
                        0x04
                    })
                    Name (_SUN, One)  // _SUN: Slot User Number
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        Store (Package (0x14)
                            {
                                "AAPL,slot-name",
                                "AirPort",
                                "name",
                                "AirPort Extreme",
                                "model",
                                Buffer (0x37)
                                {
                                    "Atheros AR9x8x 802.11 a/b/g/n Wireless Network Adapter"
                                },

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

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

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

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

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

                                "built-in",
                                Buffer (One)
                                {
                                     0x00                                      
                                },

                                "compatible",
                                "pci168c,30"
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }
                }

Together with FakePCIID and FakePCIID_AR928x_as_xxxx.kext it should work fine.

But be aware... after that, there is no way of using the Card in a dual-boot scenerio, since Windows will also recognize the card as Intel Wifi, but the drivers will not be able to start the device.

With Linux you might be able to create a workaround.

Thank you for the guide, i was able to rebrand the card but it seems the card i have also has bluetooth built-in so now it failing during booting with error device id 0CF3 3000 is unidentified mini PCI. Any way to disable bluetooth from that card.
 
What is the correct model name of your Wifi-Card?
Maybe this is a special device which contains BT, but that's something we should have known before, since the AR9285 that I know don't have BT integrated.
 
What is the correct model name of your Wifi-Card?
Maybe this is a special device which contains BT, but that's something we should have known before, since the AR9285 that I know don't have BT integrated.

AR5B95: AR9285 WiFi only
AR5B195: AR9285 WiFi + AR3011 bluetooth
 
AR5B95: AR9285 WiFi only
AR5B195: AR9285 WiFi + AR3011 bluetooth

Yes it is AR9285 WiFi + AR3011 bluetooth. Anything can be done to get rid of the Bios error?
 
Yes it is AR9285 WiFi + AR3011 bluetooth. Anything can be done to get rid of the Bios error?

An AR9285 can be rebranded to something that is allowed by your BIOS. Depending on the extent of the rebrand, the card will no longer work in Windows and will require FakePCIID kexts to work on OS X.
 
An AR9285 can be rebranded to something that is allowed by your BIOS. Depending on the extent of the rebrand, the card will no longer work in Windows and will require FakePCIID kexts to work on OS X.
Thanks RehabMan, i have already rebranded it to intel centurion n6205 but the bluetooth device id is being blocked. is there a guide available to rebrand the bluetooth device id?

Thanks
 
Thanks RehabMan, i have already rebranded it to intel centurion n6205 but the bluetooth device id is being blocked. is there a guide available to rebrand the bluetooth device id?

Thanks

I've never seen a BIOS that blocks on a USB device. Are you sure? Please clarify.
 
Status
Not open for further replies.
Back
Top