SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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.
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!
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.
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.
> 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.
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.
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!
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!
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!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
