Re: [opensuse-kernel] Re: [opensuse-factory] Re: Tumbleweed and Realtek based wifi nics
On 10/07/2016 05:27 AM, Matthias Brugger wrote:
If you can bisect the kernel and point to a particular commit that causes the increased packet loss, that would be very helpful. I know of no changes to any of the Realtek drivers that would cause these kinds of problems.
Larry
Thanks Larry - I have some idea of bisecting software, but no idea in regards to the Tumbleweed. Where can I find the various commits/versions to test as part of the bisection?
If openSUSE has a git repository for its kernels, I am not aware of its location. Perhaps someone will come up with that information.
You could clone the mainline repository from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git. Every change included in 4.7.X will be in that code. I would use the 4.7.5 configuration to build kernel 4.8 that is in that repo and test it. If you still get the packet loss, then use the commands 'git bisect start drivers/net/wireless/realtek/rtlwifi/', 'git bisect bad', and 'git bisect good v4.6'. Change that last one to whatever version you think is good.
That bisection will have roughly 5 steps to finish and should not take too long, even with the full configuration used in distribution kernels.
Larry
I keep getting errors when trying to star the git bisect.
Here is what I get:
git clone git://kernel.opensuse.org/kernel.git -b stable Cloning into 'kernel'... remote: Counting objects: 6374859, done. remote: fatal: inflateInit: out of memory (no message) remote: aborting due to possible repository corruption on the remote side. fatal: early EOF fatal: index-pack failed
how can I get around this error, maybe a git option to not compress or some such thing?
Strange, I don't get that error. You can try https://github.com/openSUSE/kernel.git instead.
Regards, Matthias
Thanks,
--Moby
Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now. -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable. Then I did the usual make mrproper, make menuconfig (and made sure btrfs and the realtek stuff was included, I made btrfs in kernel instead of module - the machine has / on btrfs), make modules, make modules_install, make bzImage, make install. After this, I booted into the newly minted 4.8X kernel - only to see that the realtek wifi (and associated realtek ethernet nic) were not detected, and the video driver was mangled as well since the display was horrible. I had no idea why the realtek drivers did not get built, and same for the video. A standard zypper in kernel-default from the regular tumbleweed repos installs a kernel that at least has the proper drivers (except that then the realtek wifi incurs heavy packet loss). What steps can I follow so that build my own kernel as part of the git bisect includes the same settings and drivers as the standard tumbleweed kernels? Thank you in advance for your help, -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/09/2016 01:47 PM, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable. Then I did the usual make mrproper, make menuconfig (and made sure btrfs and the realtek stuff was included, I made btrfs in kernel instead of module - the machine has / on btrfs), make modules, make modules_install, make bzImage, make install.
After this, I booted into the newly minted 4.8X kernel - only to see that the realtek wifi (and associated realtek ethernet nic) were not detected, and the video driver was mangled as well since the display was horrible. I had no idea why the realtek drivers did not get built, and same for the video. A standard zypper in kernel-default from the regular tumbleweed repos installs a kernel that at least has the proper drivers (except that then the realtek wifi incurs heavy packet loss).
What steps can I follow so that build my own kernel as part of the git bisect includes the same settings and drivers as the standard tumbleweed kernels?
Thank you in advance for your help,
Your configuration is faulty. I recommend using the one from openSUSE. You can find that in /proc/config.gz from a kernel that boots correctly, or in /boot/config-XXXX, where XXXX corresponds to the latest Tumbleweed kernel. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable. Then I did the usual make mrproper,
You forgot "make cloneconfig" from your original running kernel. Regards Dave P
make menuconfig (and made sure btrfs and the realtek stuff was included, I made btrfs in kernel instead of module - the machine has / on btrfs), make modules, make modules_install, make bzImage, make install. make xconfig is easier.
After this, I booted into the newly minted 4.8X kernel - only to see that the realtek wifi (and associated realtek ethernet nic) were not detected, and the video driver was mangled as well since the display was horrible. I had no idea why the realtek drivers did not get built, and same for the video. A standard zypper in kernel-default from the regular tumbleweed repos installs a kernel that at least has the proper drivers (except that then the realtek wifi incurs heavy packet loss).
What steps can I follow so that build my own kernel as part of the git bisect includes the same settings and drivers as the standard tumbleweed kernels?
Thank you in advance for your help,
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/2016 01:57 PM, Dave Plater wrote:
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable. Then I did the usual make mrproper,
You forgot "make cloneconfig" from your original running kernel. Regards Dave P
make menuconfig (and made sure btrfs and the realtek stuff was included, I made btrfs in kernel instead of module - the machine has / on btrfs), make modules, make modules_install, make bzImage, make install. make xconfig is easier.
After this, I booted into the newly minted 4.8X kernel - only to see that the realtek wifi (and associated realtek ethernet nic) were not detected, and the video driver was mangled as well since the display was horrible. I had no idea why the realtek drivers did not get built, and same for the video. A standard zypper in kernel-default from the regular tumbleweed repos installs a kernel that at least has the proper drivers (except that then the realtek wifi incurs heavy packet loss).
What steps can I follow so that build my own kernel as part of the git bisect includes the same settings and drivers as the standard tumbleweed kernels?
Thank you in advance for your help,
I've also been using make xconfig. It's a lot easier to read and configure. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/2016 08:06 PM, Roman Bysh wrote:
On 10/10/2016 01:57 PM, Dave Plater wrote:
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable.
I was able to compile, install, and boot into the 4.8.1 kernel using the steps mentioned above. I verified the problem existed, and it did. Now I am having difficulties with the next step in the bisect (I wish there was a guide to kernel bisecting for openSUSE/Tumbleweed!). I want to test kernel 4.6 or 4.5 now to see if it has the problem. However, whenever I do git bisect good v4.6 or git bisect bad v4.5, I get an error "No testable commit found". Any help in moving on with the bisection would be appreciated. -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/11/2016 08:23 AM, Moby wrote:
On 10/10/2016 08:06 PM, Roman Bysh wrote:
On 10/10/2016 01:57 PM, Dave Plater wrote:
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
<truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable.
I was able to compile, install, and boot into the 4.8.1 kernel using the steps mentioned above. I verified the problem existed, and it did. Now I am having difficulties with the next step in the bisect (I wish there was a guide to kernel bisecting for openSUSE/Tumbleweed!).
I want to test kernel 4.6 or 4.5 now to see if it has the problem. However, whenever I do git bisect good v4.6 or git bisect bad v4.5, I get an error "No testable commit found".
Any help in moving on with the bisection would be appreciated.
The general prescription is as follows: git bisect reset git bisect start git bisect bad git bisect good v4.5 Build and test the resulting kernel, then git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step. When yo do the above, what happens? If it fails, please post the console output. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/11/2016 10:55 AM, Larry Finger wrote:
On 10/11/2016 08:23 AM, Moby wrote:
On 10/10/2016 08:06 PM, Roman Bysh wrote:
On 10/10/2016 01:57 PM, Dave Plater wrote:
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote:
> <truncated> Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - I am working on doing the bisect with it now.
I did a git clone git://github.com/openSUSE/kernel.git -b stable.
I was able to compile, install, and boot into the 4.8.1 kernel using the steps mentioned above. I verified the problem existed, and it did. Now I am having difficulties with the next step in the bisect (I wish there was a guide to kernel bisecting for openSUSE/Tumbleweed!).
I want to test kernel 4.6 or 4.5 now to see if it has the problem. However, whenever I do git bisect good v4.6 or git bisect bad v4.5, I get an error "No testable commit found".
Any help in moving on with the bisection would be appreciated.
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
Thanks Larry ... ok, that seemed to go well. After git bisect good v4.5, I copied the running config over and now make menuconfig, make xmenuconfig etc all fail with errors messages as below. Makefile:439: *** mixed implicit and normal rules: deprecated syntax Makefile:1561: *** mixed implicit and normal rules: deprecated syntax make: *** No rule to make target 'menuconfig'. Stop. -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/11/2016 11:45 PM, Moby wrote:
On 10/11/2016 10:55 AM, Larry Finger wrote:
On 10/11/2016 08:23 AM, Moby wrote:
On 10/10/2016 08:06 PM, Roman Bysh wrote:
On 10/10/2016 01:57 PM, Dave Plater wrote:
On 09/10/2016 20:47, Moby wrote:
On 10/08/2016 05:20 PM, Moby wrote: >> <truncated> > Thanks Matthias, github.com/openSUSE/kernel.git worked just fine - > I am > working on doing the bisect with it now. > >
I did a git clone git://github.com/openSUSE/kernel.git -b stable.
I was able to compile, install, and boot into the 4.8.1 kernel using the steps mentioned above. I verified the problem existed, and it did. Now I am having difficulties with the next step in the bisect (I wish there was a guide to kernel bisecting for openSUSE/Tumbleweed!).
I want to test kernel 4.6 or 4.5 now to see if it has the problem. However, whenever I do git bisect good v4.6 or git bisect bad v4.5, I get an error "No testable commit found".
Any help in moving on with the bisection would be appreciated.
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
Thanks Larry ... ok, that seemed to go well. After git bisect good v4.5, I copied the running config over and now make menuconfig, make xmenuconfig etc all fail with errors messages as below.
Makefile:439: *** mixed implicit and normal rules: deprecated syntax Makefile:1561: *** mixed implicit and normal rules: deprecated syntax make: *** No rule to make target 'menuconfig'. Stop.
The correct command is "make xconfig", but the errors are due to revisions in make. The fix was made in commit 31110ebbec. If you want to try to work around that issue, then do the following: git bisect reset git show 31110ebbec > patch_31110ebbec git bisect start git bisect bad v4.6 git bisect good v4.5 make xconfig At this point, you will not get the Makefile error and you can make sudo make modules_install install and test the generated kernel. If you do get the Makefile error following a bisect step, then patch -p1 < patch_31110ebbec make xconfig sudo make modules_install install patch -p1 -R < patch_31110ebbec That restores the kernel source, which will be needed before the next bisection step. This procedure is complicated, but you should be able to handle it. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/11/2016 23:45, Moby wrote:
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
The bisect is done - I think. In addition to the bug with the Makefile, I also kept running into a kernel bug that kept causing segfaults in wpa_supplicant. I started with kernel 4.8.1, which had the packet loss, and I did a bisect bad on it. Then I checked out v4.5, which did not have packet loss in it, and I did bisect good on it. From then on, almost every bisect resulted in a kernel where wpa_supplicant kept segfaulting. Ikept doing a bisect good on these, since I wanted the bisection to "proceed towards 4.8.1" - I am not sure if this was the right thing to do. However, at the end of all this, I am sitting at version 4.6.0-rc7-1-default+, and git bisect good replies with: 2dcd0af568b0cf583645c8a317dd12e344b1c72a is the first bad commit commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun May 15 15:43:13 2016 -0700 Linux 4.6 :100644 100644 acf6155421cc244913b71c6d3b95cd17690e64ff 0f9cb36d45c2c59a589670679e7fa1d25ff9ee59 M Makefile I am not sure if all this effort is valid, since the wpa_supplicant segfaults in most revisions preventing me from testing them. Regards, -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/17/2016 07:23 PM, Moby wrote:
On 10/11/2016 23:45, Moby wrote:
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
The bisect is done - I think. In addition to the bug with the Makefile, I also kept running into a kernel bug that kept causing segfaults in wpa_supplicant. I started with kernel 4.8.1, which had the packet loss, and I did a bisect bad on it. Then I checked out v4.5, which did not have packet loss in it, and I did bisect good on it. From then on, almost every bisect resulted in a kernel where wpa_supplicant kept segfaulting. Ikept doing a bisect good on these, since I wanted the bisection to "proceed towards 4.8.1" - I am not sure if this was the right thing to do. However, at the end of all this, I am sitting at version 4.6.0-rc7-1-default+, and git bisect good replies with:
2dcd0af568b0cf583645c8a317dd12e344b1c72a is the first bad commit commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun May 15 15:43:13 2016 -0700
Linux 4.6
:100644 100644 acf6155421cc244913b71c6d3b95cd17690e64ff 0f9cb36d45c2c59a589670679e7fa1d25ff9ee59 M Makefile
I am not sure if all this effort is valid, since the wpa_supplicant segfaults in most revisions preventing me from testing them.
No, that merge is not correct. The place where you ended up only added the v4.6 tag - it had no code associated with it. By arbitrarily calling everything "good", you had no chance to find anything that was "bad". I have no idea what was causing the segfaults for wpa_supplicant. I have not seen anything like that. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/18/2016 00:18, Larry Finger wrote:
On 10/17/2016 07:23 PM, Moby wrote:
On 10/11/2016 23:45, Moby wrote:
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
The bisect is done - I think. In addition to the bug with the Makefile, I also kept running into a kernel bug that kept causing segfaults in wpa_supplicant. I started with kernel 4.8.1, which had the packet loss, and I did a bisect bad on it. Then I checked out v4.5, which did not have packet loss in it, and I did bisect good on it. From then on, almost every bisect resulted in a kernel where wpa_supplicant kept segfaulting. Ikept doing a bisect good on these, since I wanted the bisection to "proceed towards 4.8.1" - I am not sure if this was the right thing to do. However, at the end of all this, I am sitting at version 4.6.0-rc7-1-default+, and git bisect good replies with:
2dcd0af568b0cf583645c8a317dd12e344b1c72a is the first bad commit commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun May 15 15:43:13 2016 -0700
Linux 4.6
:100644 100644 acf6155421cc244913b71c6d3b95cd17690e64ff 0f9cb36d45c2c59a589670679e7fa1d25ff9ee59 M Makefile
I am not sure if all this effort is valid, since the wpa_supplicant segfaults in most revisions preventing me from testing them.
No, that merge is not correct. The place where you ended up only added the v4.6 tag - it had no code associated with it. By arbitrarily calling everything "good", you had no chance to find anything that was "bad". I have no idea what was causing the segfaults for wpa_supplicant. I have not seen anything like that.
Larry
Well, I did have a bisect bad - this was with the version I started the bisect with, 4.8.1. That version showed the packet loss issue. After that, I went to 4.5.1, and it was good - but almost all versions after 4.5.1 had the wpa_supplicant segfault in them and only way I could think of progressing closer to the "culprit commit" was to keep labeling them good. -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/18/2016 08:43 PM, Moby wrote:
On 10/18/2016 00:18, Larry Finger wrote:
On 10/17/2016 07:23 PM, Moby wrote:
On 10/11/2016 23:45, Moby wrote:
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
The bisect is done - I think. In addition to the bug with the Makefile, I also kept running into a kernel bug that kept causing segfaults in wpa_supplicant. I started with kernel 4.8.1, which had the packet loss, and I did a bisect bad on it. Then I checked out v4.5, which did not have packet loss in it, and I did bisect good on it. From then on, almost every bisect resulted in a kernel where wpa_supplicant kept segfaulting. Ikept doing a bisect good on these, since I wanted the bisection to "proceed towards 4.8.1" - I am not sure if this was the right thing to do. However, at the end of all this, I am sitting at version 4.6.0-rc7-1-default+, and git bisect good replies with:
2dcd0af568b0cf583645c8a317dd12e344b1c72a is the first bad commit commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun May 15 15:43:13 2016 -0700
Linux 4.6
:100644 100644 acf6155421cc244913b71c6d3b95cd17690e64ff 0f9cb36d45c2c59a589670679e7fa1d25ff9ee59 M Makefile
I am not sure if all this effort is valid, since the wpa_supplicant segfaults in most revisions preventing me from testing them.
No, that merge is not correct. The place where you ended up only added the v4.6 tag - it had no code associated with it. By arbitrarily calling everything "good", you had no chance to find anything that was "bad". I have no idea what was causing the segfaults for wpa_supplicant. I have not seen anything like that.
Larry
Well, I did have a bisect bad - this was with the version I started the bisect with, 4.8.1. That version showed the packet loss issue. After that, I went to 4.5.1, and it was good - but almost all versions after 4.5.1 had the wpa_supplicant segfault in them and only way I could think of progressing closer to the "culprit commit" was to keep labeling them good.
Suppose that the first one with the segfault was bad. When you called it good, that would mean that EVERY bisection you tried after that was bad. When you called that choice good, you kept getting further from a faulty selection. I have the openSUSE source tree on my system, and I will try to duplicate your result. If I can, then I will try the bisection. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Oct 19, 2016 at 4:43 AM, Moby <moby@mobsternet.com> wrote:
lmost all versions after 4.5.1 had the wpa_supplicant segfault in them and only way I could think of progressing closer to the "culprit commit" was to keep labeling them good.
You should skip commits that you can't test with $ git bisect skip man git-bisect has more details. Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/19/2016 02:27, Robert Munteanu wrote:
On Wed, Oct 19, 2016 at 4:43 AM, Moby <moby@mobsternet.com> wrote:
lmost all versions after 4.5.1 had the wpa_supplicant segfault in them and only way I could think of progressing closer to the "culprit commit" was to keep labeling them good. You should skip commits that you can't test with
$ git bisect skip
man git-bisect has more details.
Robert
Thanks Robert, I did now know about bisect skip. Thanks Larry for trying to reproduce the issue. All I do to reproduce it is to ping a node over the wifi - 100 pings shows about 50 to 70% drops ... -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/20/2016 01:52 PM, Moby wrote:
On 10/19/2016 02:27, Robert Munteanu wrote:
On Wed, Oct 19, 2016 at 4:43 AM, Moby <moby@mobsternet.com> wrote:
lmost all versions after 4.5.1 had the wpa_supplicant segfault in them and only way I could think of progressing closer to the "culprit commit" was to keep labeling them good. You should skip commits that you can't test with
$ git bisect skip
man git-bisect has more details.
Robert
Thanks Robert, I did now know about bisect skip. Thanks Larry for trying to reproduce the issue. All I do to reproduce it is to ping a node over the wifi - 100 pings shows about 50 to 70% drops ...
Sorry to take so long to get back to you. For some reason, the RTL8188EE card would not work in my laptop that I use for testing other Realtek devices. To get around that, I had to borrow a suitable laptop. I still do not know which commit is causing the problem, but I can duplicate the problem. As a work around, you should do the following: git clone http://github.com/lwfinger/rtlwifi_new.git cd rtlwifi_new make sudo make install Since our last communication, Realtek sent me a bunch of changes that are just now being submitted to mainline; however, the above GitHub repo has all of those changes and they fix the RTL8188EE problem. You will need to repeat the make and make install steps every time your kernel changes. Larry -- If I was stranded on an island and the only way to get off the island was to make a pretty UI, I’d die there. Linus Torvalds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Dave Plater -
Larry Finger -
Moby -
Robert Munteanu -
Roman Bysh