LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-06-2019, 05:38 AM   #1
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Rep: Reputation: 1
slackware64-current no WiFi after upgrade from 27. 2. 2019


Configuration:
Slackware64-current upgraded 5. 3. 2019
kernel-4.19.16
Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

All worked well until I upgraded packages on 27. 2. 2019, then WiFi stops working.

Packages upgraded (from Slackware-current changelog):
Quote:
a/btrfs-progs-4.20.2-x86_64-1.txz: Upgraded.
a/openssl-solibs-1.1.1b-x86_64-1.txz: Upgraded.
ap/ddrescue-1.24-x86_64-1.txz: Upgraded.
ap/sqlite-3.27.2-x86_64-1.txz: Upgraded.
l/libssh-0.8.7-x86_64-1.txz: Upgraded.
l/talloc-2.1.16-x86_64-1.txz: Upgraded.
l/tdb-1.3.18-x86_64-1.txz: Upgraded.
l/tevent-0.9.39-x86_64-1.txz: Upgraded.
n/ca-certificates-20181210-noarch-2.txz: Rebuilt.
Use "c_rehash" rather than "openssl rehash" for compatibility with all
versions of OpenSSL.
n/epic5-2.1.1-x86_64-1.txz: Upgraded.
n/openssl-1.1.1b-x86_64-1.txz: Upgraded.
x/xorg-server-1.20.4-x86_64-1.txz: Upgraded.
x/xorg-server-xephyr-1.20.4-x86_64-1.txz: Upgraded.
x/xorg-server-xnest-1.20.4-x86_64-1.txz: Upgraded.
x/xorg-server-xvfb-1.20.4-x86_64-1.txz: Upgraded.
I set up network config with static data (no DHCP) in rc.inet1.conf.
Previously I set up networkmanager.
Both above setups worked, connected to WiFi router with WPA2 password.

After the above mentioned upgrades no WiFi:
Tested networkmanager - no WiFi APs listed, only eth0 (WiFi turned on)
Tested wpa_gui - no WiFi card selectable
Tested rc.inet1 start or executing wpa_supplicant the same error:

Code:
[~] # wpa_supplicant -c /etc/wpa_supplicant.conf -i wlan1
Successfully initialized wpa_supplicant
OpenSSL: Failed to set cipher string 'PROFILE=SYSTEM:3DES'
SSL: Failed to initialize TLS context.
Failed to initialize EAPOL state machines.
nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Code:
iwlist wlan1 scan
....
          Cell 02 - Address: 6C:B0:CE:24:71:3A
                    Channel:4
                    Frequency:2.427 GHz (Channel 4)
                    Quality=56/70  Signal level=-54 dBm
                    Encryption key:on
                    ESSID:"R7500"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000003738b04894a

....
/etc/wpa_supplicant.conf:
Code:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root
network={
  scan_ssid=0
  ssid="R7500"
  psk=encrypted password
  key_mgmt=WPA-PSK
  }
As wpa_supplicant shows SSL errors, I suspect openssl* or ca-certificates upgrades, as wpa_supplicant did not changed with above upgrades.

Any suggestions?
I need WiFi, as my slackware box uses WiFi and wired to connect two LANs together.
 
Old 03-06-2019, 05:52 AM   #2
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,624
Blog Entries: 3

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
you may need to recompile openssl.
rebuild wireless_tool
rebuild wpa_supplicant
or reinstall all 3 .
find the broken link
 
Old 03-06-2019, 05:57 AM   #3
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by Drakeo View Post
you may need to recompile openssl.
rebuild wireless_tool
rebuild wpa_supplicant
or reinstall all 3 .
find the broken link
Thanks Drakeo.
Would be glad to be more specific. If I rebuild all of them with the same configs, there would be no change. So, please give me a real hint.
 
Old 03-06-2019, 06:57 AM   #4
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
looks OpenSSL failure

As it looks OpenSSL failed. There is something wrong with a package from 27. 2. 2019.
I just tried to remotely connect to Slackware box mentioned in a first post with TigerVNC.
After valid authentication the X window appear for a fraction of a second then return:

TigerVNC Viewer -
Quote:
readTLS: Decryption has failed. (-24)
.

So wpa_supplicant and TigerVNC both returned OpenSSL error. This clearly point to crippled OpenSSL package.

Will we have to wait for a new one from Patrick or there is another trick?
 
Old 03-06-2019, 07:14 AM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,138

Rep: Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818Reputation: 1818
Your error is the same as reported here.
Openssl-1.1.1b is fine here.
 
Old 03-06-2019, 08:01 AM   #6
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by allend View Post
Your error is the same as reported here.
Openssl-1.1.1b is fine here.
Yes found that, but this is for wpa_supplicant-2.6 with mentioned patch.
The first I do after reading the above mentioned post, was fetching sources & scripts from slackware-current ftp and looking for above mentioned patch.
As wpa-supplicant-2.7 sources and scripts there do not have above mentioned patch I'm in a dark, so I posted this thread.

And after posting the below appear:

why TigerVNC reports the same error?
So I'm still convinced of a bad OpenSSL.
Please explain why two different applications returns OpenSSL error, but you say it's OK.
And the errors appear after OpenSSL was upgraded, not TigerVNC and wpa_supplicant.

So compiling wpa_supplicant is useless, TigerVNC will still return error (and possibly other applications using OpenSSL).

Last edited by zdolar; 03-06-2019 at 08:13 AM. Reason: added text
 
Old 03-06-2019, 09:20 AM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,439

Rep: Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692Reputation: 5692
Since that round of updates on 27 Feb, there have been several newer updates as well. And since 27 Feb (a week ago) no one else suffered from Wi-Fi or VNC issues.
I myself run a laptop with the latest Slackware64-current, using Wi-Fi without any issues (connecting to various WPA/WPA2 secured networks) and use the TigerVNC viewer every day, without any error or issue.
Perhaps there's an older non-Slackware package still on your computer that wants an older openssl library, and that's being picked up by other programs? Check your package list.
Also, do you always install the new packages when any get added to Slackware-current?
 
Old 03-06-2019, 01:58 PM   #8
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
Hello Eric!

I upgradepkg --reinstall --install-new new packages as they are available on a slackware FTP.
I do not install all new packages, only those I think my system needs and are already installed and new dependencies.

So this afternoon I deleted openssl-1.1.1b-x86_64-1 and openssl-solibs-1.1.1b-x86_64-1 and reinstalled them. WiFi not working.
Then delete them again and installed older versions openssl-1.1.1a-x86_64-1 and openssl-solibs-1.1.1a-x86_64-1. WiFi working.

So must be something with those new packages.
As you see on my first post, on 27. 2. 2019 I installed all new packages released that day.
When wpa_supplicant is executed with -dd no additional error data are printed nor any are available in any log files.

Regards,

Zdenko
 
Old 03-06-2019, 02:27 PM   #9
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by Alien Bob View Post
Since that round of updates on 27 Feb, there have been several newer updates as well. And since 27 Feb (a week ago) no one else suffered from Wi-Fi or VNC issues.
I myself run a laptop with the latest Slackware64-current, using Wi-Fi without any issues (connecting to various WPA/WPA2 secured networks) and use the TigerVNC viewer every day, without any error or issue.
Perhaps there's an older non-Slackware package still on your computer that wants an older openssl library, and that's being picked up by other programs? Check your package list.
Also, do you always install the new packages when any get added to Slackware-current?
And yes, I updated packages to the last released (5. 3. 2019) - no kernel, I compile it by myself as this is miniPC for a special purpose and I also hate initrd.

Older non-Slackware packages - could be, but I do not understand how this could influence on WiFi (wpa_supplicant) and VNC regarding to OpenSSL?
So how do I find those packages?

Regards,

Zdenko
 
Old 03-12-2019, 06:50 AM   #10
zdolar
LQ Newbie
 
Registered: Jul 2009
Location: Slovenija
Distribution: Slackware
Posts: 27

Original Poster
Rep: Reputation: 1
Yesterday I downloaded all packages from Slackware FTP and executed upgradepkg --reinstall --install-new on my Slackware64-current box over all packages.
Now all works excellent. Even more, WiFi router association takes around a second at boot time, opposed to previous > 10 seconds delay . Congratulate.
Looks I missed a package upgrade regardless careful upgrades.

Sincere apology to all involved especially Pat.

Regards,

Zdenko
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] glibc and multilib issues after -current upgrades 2019-02-01 kgha Slackware 36 02-03-2019 09:56 PM
Brightness function keys not working on Slackware64 & Slackware64 current Andersen Slackware 7 01-15-2018 04:27 AM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
Slackware64-current : can't have lilo updating the boot loader after kernel upgrade Didier Spaier Slackware 3 07-21-2009 08:00 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:53 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration