pledge wrote: ↑
Sat Apr 18, 2020 7:42 pm
I have a question due to the WLAN Module Intel ax 200. And sorry, if my question seems to be stupid - I'm not a OS-Specialist.
In generally my WLAD should be supported in Linux if the kernel is 5.1 or higher (https://www.intel.de/content/www/de/de/ ... rking.html
But in the test with the Live-System from USB the wifi Intel ax 200 does not work, only some older Wifi-USB-Stick.
But the kernel of the live System seems to be 5.4, if I understood this correctly. Therefore it should work theoretically.
Then I read that the kernel is somehow custom built - if I understood correctly.
So my questions:
1. Is this the reason why the AX 200 doesn't work and
2. does this mean, that even after installation of AV Linux on my HD and getting all updates, my WLAN Module Intel ax 200 still won't work?
3. If this is the case, are there as well security updates, that usually come with new kernels and as well won't reach the kernel of AV Linux in a timely manner?
Hi, the solution is that you have to download a firmwarefile called "iwlwifi-cc-a0-46.ucode" from intel's homepage under https://www.intel.de/content/www/de/de/ ... rking.html
. This file you have to put in the folder "/lib/firmware" and after reboot the Wifi works well all the time
As the firmware is responsible for bluetooth as well, this theoretically should work as well.
Question: in my case bluetooth only works, if I make a restart from Windows 10 into AVL. If I start normally AVL, bluetooth does not work.
As well, If I do have bluetooth working in AVL and than go into Standby mode (I hope I translated "Bereitschaft" correctly - it's the left button in the second row in the power down menu that appears, if you hit the green on/off button) and wake up from standby, bluetooth is gone as well.
If I perform "dmesg | grep -i bluetooth" I get:
Code: Select all
[ 3.592930 Bluetooth: Core ver 2.22
[ 3.593359] Bluetooth: HCI device and connection manager initialized
[ 3.593364] Bluetooth: HCI socket layer initialized
[ 3.593367] Bluetooth: L2CAP socket layer initialized
[ 3.593374] Bluetooth: SCO socket layer initialized
[ 3.713553] Bluetooth: hci0: Firmware revision 0.0 build 186 week 6 2020
[ 5.088714] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.088717] Bluetooth: BNEP filters: protocol multicast
[ 5.088723] Bluetooth: BNEP socket layer initialized
[ 10.630602] Bluetooth: RFCOMM TTY layer initialized
[ 10.630624] Bluetooth: RFCOMM socket layer initialized
[ 10.630630] Bluetooth: RFCOMM ver 1.11
[ 23.987778] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 23.987783] Bluetooth: HIDP socket layer initialized
[ 23.988134] input: Bluetooth Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:1131:1616.0002/input/input31
[ 23.988219] hid-generic 0005:1131:1616.0002: input,hidraw1: BLUETOOTH HID v4.10 Mouse [Bluetooth Mouse] on d0:ab:d5:1a:94:c8
[ 45.481748] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 45.482725] Bluetooth: hci0: Device revision is 1
[ 45.482726] Bluetooth: hci0: Secure boot is enabled
[ 45.482727] Bluetooth: hci0: OTP lock is enabled
[ 45.482727] Bluetooth: hci0: API lock is enabled
[ 45.482728] Bluetooth: hci0: Debug lock is disabled
[ 45.482728] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 45.484966] bluetooth hci0: Direct firmware load for intel/ibt-20-1-3.sfi failed with error -2
[ 45.484982] Bluetooth: hci0: Failed to load Intel firmware file (-2)
I have the impression, that after standby mode, the system uses the old firmware insteand the new one. Does anybody know what might be the problem and how to fix this? Can I tell, that after start or going back from standby the right firmware has to be loaded? Or I just delete the old one in order to hope, that the the correct one is loaded?