LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 11-16-2020, 07:48 PM   #1
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Rep: Reputation: 66
asus laptop w/intel wifi problems


OK - I am back again, obviously have learned not my lesson from the last time (https://www.linuxquestions.org/quest...ci-4175666364/)

I bought a new Asus laptop (F510UA) and did what I always do - copying a working slackware-14.2-32 and a working mx-18.3-64 from my previous asus laptop. Obviously had to change the UUIDs for booting and in /etc/fstab - otherwise it should be plug-n-play - and it was (kind-of).

MX-18.3-64 worked a treat from the very go, and Slackware was fine as well, but it would NOT recognize the wi-fi chip :-(

Unfortuneately - the wifi-chip is different this time around and it does no longer seem to use the atheros firmware. The only thing I can see loading this time is 'iwlwifi-8265-36.ucode' which is present on both systems and are exactly equal (according to 'cmp -l')

Anyways - I have copied the appropriate dmesg-bits and 'lspci -v' from both systems. I would appreciate if someone could have a quick look-see and tell me something I have overlooked.

Thank yall in advance!

By the way - my slackware has the latest .240-kernel.

Code:
### -----------------
### slackware-14.2-32
### -----------------
~ # dmesg|grep -e wl -e 02:00
[    0.427887] pci 0000:02:00.0: [8086:24fd] type 00 class 0x028000
[    0.428055] pci 0000:02:00.0: reg 0x10: [mem 0xef000000-0xef001fff 64bit]
[    0.428567] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[    0.707426] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt

~ # lspci -v
02:00.0 Network controller: Intel Corporation Device 24fd (rev 78)
	Subsystem: Intel Corporation Device 0010
	Flags: bus master, fast devsel, latency 0, IRQ 10, NUMA node 0
	Memory at ef000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number a0-a4-c5-ff-ff-5f-4d-b7
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] L1 PM Substates


### ----------
### MX-18.3-64
### ----------
~ # dmesg|grep -e wl -e 02:00
[    0.679528] pci 0000:02:00.0: [8086:24fd] type 00 class 0x028000
[    0.679638] pci 0000:02:00.0: reg 0x10: [mem 0xef000000-0xef001fff 64bit]
[    0.680234] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[    7.483004] input: Asus Wireless Radio Control as /devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input11
[    7.582366] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-8265-36.ucode
[    7.583164] iwlwifi 0000:02:00.0: Found debug destination: EXTERNAL_DRAM
[    7.583906] iwlwifi 0000:02:00.0: Found debug configuration: 0
[    7.585077] iwlwifi 0000:02:00.0: loaded firmware version 36.79ff3ccf.0 op_mode iwlmvm
[    7.595632] wl: loading out-of-tree module taints kernel.
[    7.597014] wl: module license 'MIXED/Proprietary' taints kernel.
[    7.628670] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[    7.636364] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[    7.638192] iwlwifi 0000:02:00.0: Allocated 0x00400000 bytes (order 10) for firmware monitor.
[    7.693826] iwlwifi 0000:02:00.0: base HW address: a0:a4:c5:5f:4d:b7
[    7.776429] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   11.457366] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.465949] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[   11.598595] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[   11.666062] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
[   11.694143] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.721867] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[   11.858112] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[   11.926279] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
[   11.950300] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   12.040164] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   15.511691] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   15.548780] wlan0: authenticate with 1c:3b:f3:9a:fd:83
[   15.561699] wlan0: send auth to 1c:3b:f3:9a:fd:83 (try 1/3)
[   15.567513] wlan0: authenticated
[   15.568465] wlan0: associate with 1c:3b:f3:9a:fd:83 (try 1/3)
[   15.575333] wlan0: RX AssocResp from 1c:3b:f3:9a:fd:83 (capab=0x1011 status=0 aid=1)
[   15.578398] wlan0: associated
[   15.805970] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

~ # lspci -v
02:00.0 Network controller: Intel Corporation Device 24fd (rev 78)
	Subsystem: Intel Corporation Device 0010
	Flags: bus master, fast devsel, latency 0, IRQ 128
	Memory at ef000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number a0-a4-c5-ff-ff-5f-4d-b7
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] L1 PM Substates
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi, wl

Last edited by perbh; 11-16-2020 at 07:53 PM.
 
Old 11-16-2020, 09:05 PM   #2
vtel57
Senior Member
 
Registered: Jul 2006
Location: VPN Tunnel, USA
Distribution: Slackware64 14.2
Posts: 1,371

Rep: Reputation: 348Reputation: 348Reputation: 348Reputation: 348
Code:
#lspci
or

Code:
#iwconfig
to get your wifi card info.
 
Old 11-16-2020, 09:11 PM   #3
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,543
Blog Entries: 4

Rep: Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189
Quote:
Originally Posted by perbh View Post
02:00.0 Network controller: Intel Corporation Device 24fd (rev 78)
According to that it is the Intel 8265 802.11AC + BT 4.2, which should work with any kernel 4.6 and newer if the firmware is present.
 
Old 11-16-2020, 09:22 PM   #4
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 16,758
Blog Entries: 27

Rep: Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084Reputation: 5084
From the demsg output:

Quote:
7.628670] iwlwifi 0000:02:00.0: Detected , REV=0x230
This post from the Mint forums indicates it may be an issue with the version of the Linux kernel you are currently runnning.
 
Old 11-16-2020, 10:48 PM   #5
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,151

Rep: Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167Reputation: 3167
Use the working MX version of "lsmod" and compare to that of Slackware, and pay attention to what kernel, Huge or Generic, you are using as it is possible the config has that driver unchecked and neither it nor it's associated firmware are loading. You could first just try a "modprobe foo" once you've identified what "foo" is or use "KCompare" or "diff" to examine the differences in kernel config. It isn't the distro. It's the kernel.
 
Old 11-16-2020, 11:30 PM   #6
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by Timothy Miller View Post
According to that it is the Intel 8265 802.11AC + BT 4.2, which should work with any kernel 4.6 and newer if the firmware is present.
That is probably my problem - I have kernel 4.4.240
Guess I have to roll a newer kernel - darn it!! (I used to do it, now I'm too lazy)
And MX-distro uses kernel 4.19.0-5

Actually, I have another problem with my slackware-14.2 on this lappie as well (but I wasn't going to bother anyone with it) - it is a lot less responsive than what I am used to and certainly lags way behind MX, especially mouse movements ...
Just maybe I should wait for slackware-15 ...

In any case, thank you so much! - I believe you hit the nail on the head!

I will mark this as solved.

Last edited by perbh; 11-16-2020 at 11:47 PM.
 
Old 11-16-2020, 11:37 PM   #7
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by enorbet View Post
Use the working MX version of "lsmod" and compare to that of Slackware, and pay attention to what kernel, Huge or Generic, you are using as it is possible the config has that driver unchecked and neither it nor it's associated firmware are loading. You could first just try a "modprobe foo" once you've identified what "foo" is or use "KCompare" or "diff" to examine the differences in kernel config. It isn't the distro. It's the kernel.
Because I have two disks in this lappie, I need the generic kernel with initrd to boot it. Before I installed the 2nd drive, I used the huge kernel (no initrd) - same difference.

I have checked lsmod under both MX and slackware. As you see from the above, iwlwifi-8265-36.ucode is loaded by the kernel under MX, but not slackware, so obviously there's a difference here in the modules loaded. I have not checked all the other modules - was really only worried why iwlwifi wasn't loaded.
 
Old 11-16-2020, 11:40 PM   #8
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by frankbell View Post
From the demsg output:



This post from the Mint forums indicates it may be an issue with the version of the Linux kernel you are currently runnning.
Yup - somebody else mentioned the kernel version as well - probably this is the culprit.
 
Old 11-16-2020, 11:44 PM   #9
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by vtel57 View Post
Code:
#lspci
or

Code:
#iwconfig
to get your wifi card info.
I gave you the appropriate results from lspci in my first post. As for iwconfig, I haven't tried that but seeing there is no firmware loaded, nor any modules (like iwlwifi or wl or anything else), there is no reason to assume iwconfig to give any meaningful results. However, the next time I reboot this machine, I will try it.
 
Old 11-17-2020, 09:18 AM   #10
vtel57
Senior Member
 
Registered: Jul 2006
Location: VPN Tunnel, USA
Distribution: Slackware64 14.2
Posts: 1,371

Rep: Reputation: 348Reputation: 348Reputation: 348Reputation: 348
> I gave you the appropriate results from lspci in my first post.

Ah! You're absolutely correct. I missed that. Apologies...
 
Old 11-17-2020, 06:33 PM   #11
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by vtel57 View Post
> I gave you the appropriate results from lspci in my first post.

Ah! You're absolutely correct. I missed that. Apologies...
No problems - I do it all the time!!
Btw - I did try to run 'iwconfig', but as expected - "no device" (or something like that).
If no firmware/modules are loaded, the 'device' is just not there, there is nothing to support it.
 
1 members found this post helpful.
Old 11-17-2020, 08:01 PM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,517

Rep: Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169Reputation: 5169
If you haven't already, it's pretty easy to grab the kernel config Pat uses in -current (this is for the 64bit generic config) and use it on building your own kernel. I've done that several times on my 14.2 system and am currently running a 5.4.66 kernel (I know I should probably update it further, but I'm lazy).

Just unpack the latest 5.4.x kernel from kernel.org, place that config in there named as .config and then you should simply be able to run make bzImage modules and then make modules_install followed by copying the kernel to /boot (or your UEFI partition), generating a new initrd, and then making sure your bootloader points to the proper location.

I'd also recommend grabbing the kernel-firmware package from -current or building your own from his kernel-firmware.SlackBuild script (don't forget the slack-desc). The kernel-firmware script will grab the latest firmware from their git and package it.
 
1 members found this post helpful.
Old 11-18-2020, 02:19 AM   #13
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by bassmadrigal View Post
If you haven't already, it's pretty easy to grab the kernel config Pat uses in -current (this is for the 64bit generic config) and use it on building your own kernel. I've done that several times on my 14.2 system and am currently running a 5.4.66 kernel (I know I should probably update it further, but I'm lazy).

Just unpack the latest 5.4.x kernel from kernel.org, place that config in there named as .config and then you should simply be able to run make bzImage modules and then make modules_install followed by copying the kernel to /boot (or your UEFI partition), generating a new initrd, and then making sure your bootloader points to the proper location.

I'd also recommend grabbing the kernel-firmware package from -current or building your own from his kernel-firmware.SlackBuild script (don't forget the slack-desc). The kernel-firmware script will grab the latest firmware from their git and package it.
Thank you so much! I know it ain't hard, I have just lost a lot of 'go' over the years.
As it is, my slackware-14.2 is the 32-bit (because of some xerox-printer-driver problems and some 32-bits only Dells I used to have but are now scrapped), but honestly, there is nothing really to stop me going to a 64-bit version (like 'current' or even 14.2). Just pure laziness on my part. Since I am very happy with my MX, I just might wait until the 64-bit 15.0 arrives (surely it must be right around the corner) - but again, thank you so much!
 
Old 11-18-2020, 09:59 AM   #14
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,543
Blog Entries: 4

Rep: Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189
Quote:
Originally Posted by perbh View Post
Thank you so much! I know it ain't hard, I have just lost a lot of 'go' over the years.
As it is, my slackware-14.2 is the 32-bit (because of some xerox-printer-driver problems and some 32-bits only Dells I used to have but are now scrapped), but honestly, there is nothing really to stop me going to a 64-bit version (like 'current' or even 14.2). Just pure laziness on my part. Since I am very happy with my MX, I just might wait until the 64-bit 15.0 arrives (surely it must be right around the corner) - but again, thank you so much!

Define "right around the corner"...
 
Old 11-18-2020, 04:44 PM   #15
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 374

Original Poster
Rep: Reputation: 66
Quote:
Originally Posted by Timothy Miller View Post
Define "right around the corner"...
lol - your guess is as good as mine! I know, "it's ready when it's ready" ... which is one of the things I have always admired about slackware, and it's why I _always_ have a slackware on my rigs (must be about 8 of them). I might not use it all the time, kind-of seldom infact, but I never want to be without it! Plus - on numerous usb-sticks. If any of my friends ever get into trouble, I go visiting with a usb-stick, boot from it and get things sorted out - and I don't need no frigging high-res screen, the cli will give me all the power I want!

That being said, thank you so much for pointing out the required kernel version. I had checked the firmware between MX and slackware and they were identical. It never dawned on me that the kernel version would come into the equation. My bad! I _am_ getting old!
 
  


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
Ubuntu 20LTS dual boot Laptop Dell Inspiron 5548 I can not turn on wifi and in wifi settings indicates no wifi device was found Shra94 Linux - Hardware 1 05-19-2020 05:22 PM
Wifi option is there but no wifi scanning or wifi not working Aakash447 Linux - Newbie 3 06-29-2018 12:48 AM
Want to share my wifi by creating a wifi hotspot ( While staying connected to wifi)? shadyXV Linux - Desktop 4 07-20-2015 06:37 PM
Wifi on Asus p5q3 Delus wifi and Suse 11.1? brianpbarnes Linux - Software 0 02-06-2009 07:06 PM
Ralink WIFI with Asus@Home WIFI wavemachine Linux - Hardware 0 10-20-2004 04:10 PM

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

All times are GMT -5. The time now is 09:40 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
Open Source Consulting | Domain Registration