LinHES Forums http://forums.linhes.org/ |
|
R8.4 Realtek r8169 Module & a better tool http://forums.linhes.org/viewtopic.php?f=22&t=24353 |
Page 1 of 1 |
Author: | RacerX [ Tue May 24, 2016 3:28 pm ] |
Post subject: | R8.4 Realtek r8169 Module & a better tool |
I have two Asus AT3N7A-I motherboards. The on-board nic uses RTL8111/8112 driver. On the Asus Site I use the most current Bios. AT3N7A-I 0216 BIOS Dated 10//22/09 The exact same message show up with Ubuntu 1604 LTS and R8.4 Code: dmesg r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control So I setup a usb stick http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows and then the root password http://askubuntu.com/questions/189907/what-is-the-default-root-password and added a repository to find fwts http://installion.co.uk/ubuntu/vivid/universe/f/fwts/install/index.html then a added the package old school like back in the day Code: sudo apt-get install fwts after reading the askubuntu question about r8169 aspm, I ran http://askubuntu.com/questions/372363/what-does-r8169-cant-disable-aspm-os-doesnt-have-aspm-control-really-mean Code: root@ubuntu:/home/ubuntu# sudo fwts aspm Running 1 tests, results appended to results.log Test: PCIe ASPM test. PCIe ASPM ACPI test. PCIe ASPM registers test. 2 passed, 4 warning Code: Results generated by fwts: Version v15.03.01 (2015-04-01 03:46:20). Some of this work - Copyright (c) 1999 - 2015, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2015, Canonical. This test run on 25/05/16 at 03:52:45 on host Linux ubuntu 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64. Command: "fwts aspm". Running tests: aspm. aspm: PCIe ASPM test. -------------------------------------------------------------------------------- Test 1 of 2: PCIe ASPM ACPI test. PCIe ASPM is controlled by Linux kernel. Test 2 of 2: PCIe ASPM registers test. PASSED: Test 2, PCIe ASPM setting matched was matched. WARNING: Test 2, RP 00h:15h.00h L0s not enabled. WARNING: Test 2, RP 00h:15h.00h L1 not enabled. WARNING: Test 2, Device 03h:00h.00h L0s not enabled. WARNING: Test 2, Device 03h:00h.00h L1 not enabled. ADVICE: The ASPM L0s low power Link state is optimized for short entry and exit latencies, while providing substantial power savings. Disabling L0s of a PCIe device may increases power consumption, and will impact the battery life of a mobile system. ADVICE: The ASPM L1 low power Link state is optimized for maximum power savings with longer entry and exit latencies. Disabling L1 of a PCIe device may increases power consumption, and will impact the battery life of a mobile system significantly. PASSED: Test 2, PCIe ASPM setting matched was matched. ================================================================================ 2 passed, 0 failed, 4 warnings, 0 aborted, 0 skipped, 0 info only. ================================================================================ 2 passed, 0 failed, 4 warnings, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: NONE Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ aspm | 2| | | 4| | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 2| 0| 0| 4| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ Next I ran Code: root@ubuntu:/home/ubuntu/Downloads# fwts Running 43 tests, results appended to results.log The results.log is too big to fit in this post and I can't attach the results.log for some reason Code: The scope of the test is broken into four parts Test 1 of 4: Gather kernel signature. Signature: Ubuntu 4.4.0-21.37-generic 4.4.6 Test 2 of 4: Gather kernel system information. Kernel Version: Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 Test 3 of 4: Gather kernel boot command line. Kernel boot command line: file=/cdrom/preseed/ubuntu.seed boot=casper initrd= /casper/initrd.lz quiet splash --- maybe-ubiquity Test 4 of 4: Gather ACPI driver version. ACPI Version: 20150930 bios_info: Gather BIOS DMI information. -------------------------------------------------------------------------------- Test 1 of 1: Gather BIOS DMI information BIOS Vendor : American Megatrends Inc. BIOS Version : 0216 BIOS Release Date : 10/12/2009 Board Name : AT3N7A-I Board Serial # : MT709BK24300194 Board Version : Rev X.0x Board Asset Tag : To Be Filled By O.E.M. Chassis Serial # : Chassis Serial Number Chassis Type : 3 Chassis Vendor : Chassis Manufacture Chassis Version : Chassis Version Chassic Asset Tag : Asset-1234567890 Product Name : System Product Name Product Serial # : System Serial Number Product UUID : 805F5734-20DF-DE11-AD05-E0CB4EB664EE Product Version : System Version System Vendor : System manufacturer ================================================================================ 0 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 1 info only. ================================================================================ Here are the results of two the tests that have issues Code: Test 1 of 1: Legacy and PCI Interrupt Edge/Level trigger tests. FAILED [MEDIUM] NonLegacyIRQLevelTrig: Test 1, Non-Legacy interrupt 0 is incorrectly level triggered. FAILED [MEDIUM] NonLegacyIRQLevelTrig: Test 1, Non-Legacy interrupt 1 is incorrectly level triggered. FAILED [MEDIUM] NonLegacyIRQLevelTrig: Test 1, Non-Legacy interrupt 7 is incorrectly level triggered. FAILED [MEDIUM] NonLegacyIRQLevelTrig: Test 1, Non-Legacy interrupt 8 is incorrectly level triggered. FAILED [MEDIUM] NonLegacyIRQLevelTrig: Test 1, Non-Legacy interrupt 12 is incorrectly level triggered. ================================================================================ 0 passed, 5 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ wmi: Extract and analyse Windows Management Instrumentation (WMI). -------------------------------------------------------------------------------- Test 1 of 1: Windows Management Instrumentation test. \_SB_.PCI0.WMI0._WDG (1 of 10) GUID: A1799AF2-9429-4529-927E-DFE13736EEBA WMI Method: Flags : 0x02 (Method) Object ID : NV Instance : 0x01 PASSED: Test 1, A1799AF2-9429-4529-927E-DFE13736EEBA has associated method \_SB_.PCI0.WMI0.WMNV \_SB_.PCI0.WMI0._WDG (2 of 10) GUID: A1799A85-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0x85 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799A85-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. A WMI driver probably needs to be written for this WMI event. It can checked for using: wmi_has_guid("A1799A85-9429-4529-927E-DFE13736EEBA"). One can install a notify handler using wmi_install_notify_handler("A1799A85-9429-4529-927E-DFE13736EEBA", handler, NULL). http://lwn.net/Articles/391230 describes how to write an appropriate driver. \_SB_.PCI0.WMI0._WDG (3 of 10) GUID: A1799A86-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0x86 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799A86-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (4 of 10) GUID: A1799A87-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0x87 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799A87-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (5 of 10) GUID: A1799A88-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0x88 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799A88-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (6 of 10) GUID: A1799AC3-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0xc3 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799AC3-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (7 of 10) GUID: A1799AC5-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0xc5 Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799AC5-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (8 of 10) GUID: A1799ACA-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0xca Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799ACA-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (9 of 10) GUID: A1799ACB-9429-4529-927E-DFE13736EEBA WMI Event: Flags : 0x08 (Event) Notification ID: 0xcb Reserved : 0x00 Instance : 0x00 FAILED [MEDIUM] WMIUnknownGUID: Test 1, GUID A1799ACB-9429-4529-927E-DFE13736EEBA is unknown to the kernel, a driver may need to be implemented for this GUID. \_SB_.PCI0.WMI0._WDG (10 of 10) GUID: 05901221-D566-11D1-B2F0-00A0C9062910 WMI Object: Flags : 0x00 (None) Object ID : BA Instance : 0x01 ================================================================================ 1 passed, 8 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ Any thoughts would be appreciated.... |
Author: | sparks [ Sat Jun 04, 2016 8:47 am ] |
Post subject: | Re: R8.4 Realtek r8169 Module & a better tool |
I had the same problem on an old laptop, that being poor performance and linux using some module where the ethernet chipset name bore no resemblance to the kernel module name. Like an RTL8139 using an 8139too.ko module. Pretty good idea what to use in that situation. I spent a lot of time figuring out what was the correct driver module. I think using the wrong module might be the source of the problem. You have the RTL8112L chipset on your board (either version). It seems there are a lot of views on what is the correct driver is but the 8169 driver isn't mentioned a lot. What I finally did for my laptop was download the source from Realtek and compiled my own driver and used whatever Realtek thought was best. It worked better than any other solution. The good news is that the google can take you right to the source for the 8112L. The bad news is that it only supports up to kernel 3.X. But it wouldn't cost you anything but a little bit of time to try it. It might compile. It could happen. Or maybe small adjustments could be made in the source to fix compile errors. I have had problems compiling 3.X source on a 4.X system because of changes in the kernel source tree but it wouldn't hurt to try. Also, in my case, firmware was part of the tar ball so I would expect so in your case. You also might have to fiddle around with files in /etc/modules.d. There's always ndiswrapper. FWIW. This advice and 2 dollars can get you a cup of coffee. sparks |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |