Search Criteria
Package Details: mt7630-pcie-wifi-dkms 1:2.1.0.r12.5193c55-1
Git Clone URL: | https://aur.archlinux.org/mt7630-pcie-wifi-dkms.git (read-only) |
---|---|
Package Base: | mt7630-pcie-wifi-dkms |
Description: | MT7630e PCIe Wifi (DKMS) |
Upstream URL: | https://github.com/neurobin/MT7630E |
Licenses: | |
Submitter: | benjarobin |
Maintainer: | 0x9fff00 |
Last Packager: | 0x9fff00 |
Votes: | 12 |
Popularity: | 0.000127 |
First Submitted: | 2015-03-03 20:40 |
Last Updated: | 2019-11-10 22:07 |
Dependencies (3)
- dkms
- git (git-git) (make)
- linux-headers (linux-lts-ck-headers, linux-xanmod-git-headers, linux-ryzen-amd-staging-drm-next-git-headers, linux-ryzen-git-headers, linux-surfacepro3-git-headers, linux-aarch64-rock64-bin-headers, linux-ec2-headers, linux-pf-lts-headers, linux-mainline-bcachefs-lts-headers, linux-asus-aura-headers, kernel-uek-devel, linux-bootsplash-headers, linux-galliumos-headers, linux-xanmod-rt-headers, linux-lts316-headers, linux-mainline-bcachefs-headers, linux-amd-raven-headers, linux-slim-headers, linux-amd-headers, linux-nitrous-git-headers, linux-xanmod-headers, linux-ck-headers, linux-lts414-headers, linux-lts44-headers, linux-lts49-headers, linux-bcachefs-git-headers, linux-pds-headers, linux-gc-headers) (optional) – If running standard kernel, otherwise find matching headers for your kernel
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
Atsuri commented on 2015-07-02 15:46
The 100% cpu load on a single core still persists with kernel 4.0.7-2-ARCH. The dmesg | tail gives this when one of the cores runs at 100%:
[ 337.987781] SwitchChannel#14
[ 338.104140] BW=40 EXTCHA_BELOW CentralChannel=9
[ 338.104144] ==>rt2800_config_channel_rf7630 ch9
[ 338.104502] SwitchChannel#9
[ 338.111896] 0x400000a1 (status)
[ 338.111912] rt2800pci_txdone status = 0x400000a1
[ 338.111915] rt2800pci_txdone qid = 0x0
[ 338.112643] 0xa1 (status)
[ 338.112656] rt2800pci_txdone status = 0xa1
[ 338.112659] rt2800pci_txdone qid = 0x0
ArthurBorsboom commented on 2015-06-23 14:38
The messages in the kernel log has also been fixed by a developer, see comment #245 from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220146
Maybe you can do the same?
ArthurBorsboom commented on 2015-06-19 12:43
I hereby confirm that the 100% cpu core load is gone with the update. My battery
usage has been reduced by 50%. Thanks Benjarobin!
The amount of kernel messages is less too. On my system it is reduced to a long list with these type of messages.
...
[ 71.092849] ==>rt2800_config_channel_rf7630 ch12
[ 71.209642] ==>rt2800_config_channel_rf7630 ch1
[ 71.416487] ==>rt2800_config_channel_rf7630 ch13
[ 71.533344] ==>rt2800_config_channel_rf7630 ch1
[ 71.740245] ==>rt2800_config_channel_rf7630 ch14
[ 71.857026] ==>rt2800_config_channel_rf7630 ch1
...
ArthurBorsboom commented on 2015-06-19 10:59
I have the exact same issue.
After that it is even hard to start my laptop again, since the bios has a hard time to initialize.
So, confirmed.
mvci commented on 2015-06-19 10:56
even with the new update (18-6) I still most times when I turn off wifi my system get frozen
does anyone have the same problem? (I use Gnome)
ArthurBorsboom commented on 2015-06-19 06:56
Cool! I will test the updated driver a bit later and report back.
Did you also had time to make all the prinkt statements only appear when the kernel/system is in debugging level?
As reported before, for me the statement below did not had the effect I was hoping for.
printk(KERN_DEBUG "example debug message\n");
Coming from:
https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks
Maybe DKMS or modules have a different mechanism / level?
benjarobin commented on 2015-06-18 23:17
I did update the source code using https://github.com/kuba-moo/mt7630e/
I back ported the fix that produce high CPU load.
If you were talking about another deposit please name it. Thank you :-)
ArthurBorsboom commented on 2015-06-18 21:21
@benjarobin
In the post below I noticed a lot of people reporting success of using a fixed driver for the mt7630. Maybe this can be of use?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220146
ArthurBorsboom commented on 2015-06-07 08:02
If the printk("xxx") statements are replaced by printk(KERN_DEBUG "xxx"), for some reason the messages still end up in the logs, while have kernel log level at 4 (= KERN_WARNING).
When I removed all the printk statements from rt2800pci.c, rt2800lib.c and rt2x00dev.c, the output is reduced a lot not, but not stopped.
Unfortunately, the removal of the printk statments does not have an effect on the performance issue.
benjarobin commented on 2015-06-06 21:36
I am going to fix it properly, I am kind of busy now (sorry). The update will be in aur4 since I think I may not have the time tomorrow (Sunday 7 June)