Hi, I downloaded this driver
https://github.com/cilynx/rtl88x2BU_WiF ... 80427-5959
and separately compiled it for each Xenial64 and Bionic64. The Xenial works like a champ.
The Bionic does work but it throws a error when trying to associate with the router via wpa_supplicant.
Even though it does this, I can still DHCP successfully.
And I get a usable internet connection.
Because this is happening, I have to manually go through network setup each boot. Not Fun!
So what am I doing wrong here?
What logs will you need me to post?
Thanks in advance!
Dave
Overdrive
RTL8822bu wifi drivers work in Xenial but not Bionic(Solved)
RTL8822bu wifi drivers work in Xenial but not Bionic(Solved)
- Attachments
-
- UnableToConnect.png
- After trying to associate to router
- (39.97 KiB) Downloaded 133 times
Last edited by OverDrive on Mon 14 Oct 2019, 05:26, edited 1 time in total.
Instant Puppy Fan!!!
Have you done Bionicpup64 8.0 updates? Quickpet>Info>Bionicpup updates.
This will bring Bionicpup64 8.0 up to date with all the bug fixes at the time you do this.
What WPA setting are you using?
Is this a USB wifi device?
If yes.
Tried it plugged into a USB 2 port or different USB 3?
I know, you may have it plugged into the port that works with Xenialpup, but this is troubleshooting.
Xenialpup and Bionicpup are different OS.
This will bring Bionicpup64 8.0 up to date with all the bug fixes at the time you do this.
What WPA setting are you using?
Is this a USB wifi device?
If yes.
Tried it plugged into a USB 2 port or different USB 3?
I know, you may have it plugged into the port that works with Xenialpup, but this is troubleshooting.
Xenialpup and Bionicpup are different OS.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Found a workaround
OK, Found a workaround.
TL;DR: Use Frisbee network setup if you compile a wifi driver.
Detailed answer:
Well after trying to figure how to get the driver to work with network wizard which has been my favorite net setup utility since it's inception as I have found it to be quite versatile at anything I would throw at it over the years.
I dug into the source code and discovered that the Bionic64 version testInterface() function starting at line 1011 of /user/local/network-wizard/net-setup.sh has some substantial differences from the zenial64 version. Specifically, I noticed the removal of "ifplugstatus" in the test function. I am thinking those differences are what is tripping up the utility from working correctly. BTW, RTL8821cu compiled driver also failed on the utility.
Not wanting to hack a custom version for this laptop as my bash/shell scripting skills are not well developed. I decided to try the other two options: Simple Network Setup (SNS) and Frisbee.
Well SNS *did* setup correctly without errors but would not activate correctly after a reboot.
Frisbee did. Yay!
So I am considering this solved (Well, sort of solved) and hoping the Devs will look into making the network-wizard testInterface() function more robust in the future as it really is my favorite net setup utility.
Warm Regards
Overdrive
P.S. Thank you bigpup for your prompt and thoughtful response! I *did* try them all before digging into the source code.
TL;DR: Use Frisbee network setup if you compile a wifi driver.
Detailed answer:
Well after trying to figure how to get the driver to work with network wizard which has been my favorite net setup utility since it's inception as I have found it to be quite versatile at anything I would throw at it over the years.
I dug into the source code and discovered that the Bionic64 version testInterface() function starting at line 1011 of /user/local/network-wizard/net-setup.sh has some substantial differences from the zenial64 version. Specifically, I noticed the removal of "ifplugstatus" in the test function. I am thinking those differences are what is tripping up the utility from working correctly. BTW, RTL8821cu compiled driver also failed on the utility.
Not wanting to hack a custom version for this laptop as my bash/shell scripting skills are not well developed. I decided to try the other two options: Simple Network Setup (SNS) and Frisbee.
Well SNS *did* setup correctly without errors but would not activate correctly after a reboot.
Frisbee did. Yay!
So I am considering this solved (Well, sort of solved) and hoping the Devs will look into making the network-wizard testInterface() function more robust in the future as it really is my favorite net setup utility.
Warm Regards
Overdrive
P.S. Thank you bigpup for your prompt and thoughtful response! I *did* try them all before digging into the source code.
Instant Puppy Fan!!!
Now you know why there are 3 network connection programs in most Puppies.
Never have been able to get one to work 100% for every possible computer/hardware.
I use Network Wizard for the reasons you stated.
So, far it has worked for me.
If you think you may have found a bug in the latest version of Network Wizard.
We the users help and work on Puppy code.
Start a topic offering your fix.
Others will test and offer help.
Could also post a pull request at Woof-CE
https://github.com/puppylinux-woof-CE/woof-CE
Never have been able to get one to work 100% for every possible computer/hardware.
I use Network Wizard for the reasons you stated.
So, far it has worked for me.
If you think you may have found a bug in the latest version of Network Wizard.
We the users help and work on Puppy code.
Start a topic offering your fix.
Others will test and offer help.
Could also post a pull request at Woof-CE
https://github.com/puppylinux-woof-CE/woof-CE
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)