LinuxQuestions.org
Help answer threads with 0 replies.
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 06-02-2018, 09:14 PM   #1
narke
Member
 
Registered: Apr 2010
Posts: 197

Rep: Reputation: 4
ASUS fx63vd WiFi Not Appear


Hi,

The new laptop is ASUS fx63vd, with an Intel Dual Band Wireless-AC 8265 WiFi chip. The system is slack 14.2.

The problem is I didnít find any sign in the dmesg showing exists of the WiFi, I tried keywords such ad WiFi, Wireless, wlan with case insensitive. I checked the kernel already buit with iwlwifi driver module, it even has firmware file located in /lib/firmware. I can manually load the module with modprobe and see no error reported, but still can not get the wlan0 interface.

Please you expert give me an advice, I cannot live without WiFi. Thanks!

Woody
 
Old 06-02-2018, 10:31 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,950

Rep: Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217
According to Intel's page, your chipset will be identified with Linux Kernel 4.6.+. Unfortunately Slackware 14.2 shipped with Linux kernel 4.4.x, so that means that you need to build your own kernel in order to get the device recognized by the kernel or try to use the modules iwlwifi-8265-ucode-22.361476.0.tgz
 
Old 06-02-2018, 10:36 PM   #3
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Posts: 512

Rep: Reputation: 172Reputation: 172
Have you looked here?
https://www.linuxquestions.org/hcl/

Or here?
https://www.linux-laptop.net/

EDIT - willysr beat me to the draw

Last edited by Gordie; 06-02-2018 at 10:38 PM.
 
Old 06-02-2018, 10:44 PM   #4
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by willysr View Post
According to Intel's page, your chipset will be identified with Linux Kernel 4.6.+. Unfortunately Slackware 14.2 shipped with Linux kernel 4.4.x, so that means that you need to build your own kernel in order to get the device recognized by the kernel or try to use the modules iwlwifi-8265-ucode-22.361476.0.tgz
Thank you Willy for giving the important information. Since my power resume also not work, so I like to build a new kernel. I just not familiar with those firmware files in /lib/firmware, if I follow the doc and build a 4.6 kernel, will it take care for me all the firmware things?

Thanks.

-Woody
 
Old 06-02-2018, 11:08 PM   #5
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Posts: 512

Rep: Reputation: 172Reputation: 172
You should be able to upgrade your kernel to the one from the current tree (4.14.47) easy enough
 
Old 06-03-2018, 01:48 AM   #6
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by Gordie View Post
You should be able to upgrade your kernel to the one from the current tree (4.14.47) easy enough
This is what I was doing half hour ago. But so weird, the 4.14.47 from the current tree did not boot ... I just can saw a very quick flash and the screen went back to the elilo boot menu again. Is that possible the binary kernel image has a problem?

Now I am going to rebuild it from the source on my laptop using the same config as that 'curent' provided.

Hope me good luck
 
Old 06-03-2018, 03:52 AM   #7
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,950

Rep: Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217
Don't use kernel from -current as it was built with different GCC and toolchain that's available from your system (14.2). Best to build your own kernel using the -current SlackBuild script
 
Old 06-03-2018, 04:39 AM   #8
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by willysr View Post
Don't use kernel from -current as it was built with different GCC and toolchain that's available from your system (14.2). Best to build your own kernel using the -current SlackBuild script
I just built a 4.14.47 kernel, the kernel tar.xz got from the "current", the ".config" also got from the "current" config-huge-4.14.47. I did the building with following:
- make bzImage
- make modules
- make modules_install
- remove the old /lib/firmware
- install the "current" version of kernel-firmware package
- then copy the bzImage to my EFI partiton and adjusted the elilo.conf

This time, I still cannot get a boot of the new kernel, it immediately reset the machine when loading the kernel.

What's possibly the problem? I feel this is quit unusual because I think, at least, the kernel should be loaded with success and a problem should only happen in a later driver initializing stages. I never met this kind of situation before.

Please ...

-woody
 
Old 06-03-2018, 04:42 AM   #9
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,950

Rep: Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217Reputation: 1217
did you run elilo after editing your elilo.conf ?

why not use the proper SlackBuild from -current source tree instead of building them manually?
 
Old 06-03-2018, 07:04 AM   #10
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by willysr View Post
did you run elilo after editing your elilo.conf ?

why not use the proper SlackBuild from -current source tree instead of building them manually?
There is no 'elilo' command in the system. As what I understood so far, I just need to edit the elilo.conf in the efi partition, the efi boot loader of the Slackware will read the elilo.conf file at booting time. Is this right?

I think I have to try the SlackBuild from the "current" source tree later.
 
Old 06-03-2018, 10:54 AM   #11
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by willysr View Post
Don't use kernel from -current as it was built with different GCC and toolchain that's available from your system (14.2). Best to build your own kernel using the -current SlackBuild script
I just built the 4.14.47 using the SlackBuild scripts from the -current source tree (actually it's the build-all-kernels.sh help script), but the kernel still cannot boot.
 
Old 06-03-2018, 11:24 AM   #12
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Posts: 512

Rep: Reputation: 172Reputation: 172
How entrenched are you in using the stable release? Is it possible to you to try the latest LIVE current release to see if things work better for you?

http://slackware.uk/people/alien-sla...ve-current.iso
 
Old 06-03-2018, 11:27 AM   #13
slac-in-the-box
Member
 
Registered: Mar 2010
Location: oregon
Distribution: slackware64-14.2
Posts: 300

Rep: Reputation: 113Reputation: 113
the reason the huge-4.14.47 is looping under elilo is because it is too large for elilo unless a patch is applied... but if you use the generic-4.14.47 with an initrd it should boot all the way
 
Old 06-04-2018, 12:29 AM   #14
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by slac-in-the-box View Post
the reason the huge-4.14.47 is looping under elilo is because it is too large for elilo unless a patch is applied... but if you use the generic-4.14.47 with an initrd it should boot all the way
Yes, thanks. This confirmed my guess, I think the size limit in elilo is around 8MB.
 
Old 06-04-2018, 12:32 AM   #15
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by Gordie View Post
How entrenched are you in using the stable release? Is it possible to you to try the latest LIVE current release to see if things work better for you?

http://slackware.uk/people/alien-sla...ve-current.iso
Thanks. Yes the live-current ISO works. Also I can not make 4.14.47 and 4.16.13 works. The reason why I previous attempts fail is because elilo has a size limitation as pointed by 'slack-in-the-box'.
 
  


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
Wifi connection problem on Asus aamirsq Ubuntu 6 10-07-2017 03:20 AM
No wifi on asus T200TA laurent1 Linux - Hardware 1 09-09-2015 04:44 PM
asus N73 wifi raden Linux - Laptop and Netbook 4 07-10-2011 04:11 AM
Wifi on Asus p5q3 Delus wifi and Suse 11.1? brianpbarnes Linux - Software 0 02-06-2009 06:06 PM
Ralink WIFI with Asus@Home WIFI wavemachine Linux - Hardware 0 10-20-2004 03:10 PM

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

All times are GMT -5. The time now is 06:09 PM.

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