Introduction
Intel works with periodic releases of the iwlwifi driver that are tested with a specific combination of components. They are called LinuxCore releases and are numbered sequentially, e.g. LinuxCore11 is the latest stable release as of May 2015. These releases can be seen as snapshots of the development trees (including upstream) that are tested thoroughly together with a specific version of the firmware and userspace components (i.e. hostap).
Components
The components used in each release are specific stabilization versions of the following:
Who are you?
If you use a well known distribution
If you use a well maintained distribution, your device should be supported out of the box. If your device doesn't work at all (you can't even see it in the interface list), then it might mean that your kernel is too old or that you don't have the proper firmware. You can contact your distribution to have them fix this. In the meantime, you can use the backport tree to make your device work. Make sure to install the proper firmware as well. If your device works minimally (you can see it in the interface list), but you experience issues, please check the support section. You can also use the backport tree to check if the issue you are suffering from has been fixed in different releases. The backport tree is also an excellent tool to bisect regressions. Note that when you install the backport drivers, you disallow the usage of any WLAN device that is not supported by iwlmvm. To check if your device is supported by iwlmvm, please check here in the module column.
If you are building your own system
If you are building your own system and you know that the only WLAN device you'll have is from Intel, the backport tree is what you need. You'll be able to get a driver / firmware combo that has been validated together. As a rule of thumb, you should take the latest Core version available.
A note about upstream policy
The fact that Intel published a backport tree for its WLAN drivers doesn't impact its commitment to upstream all the code to the mainline kernel. It simply allows users who can't choose their kernel to work with a more recent driver. The backport tree allows us to provide a combo of the driver / firmware that has been fully validated. For a simple reason of capacity, we cannot test as thoroughly all the kernel versions / firmwares / devices matrix. There is code in the backport tree that is not in the mainline kernel, but this is transient. Eventually, all the code in the backport tree will reach mainline unless it has dependencies (platform drivers etc…).
Core release
A Core release includes all the components described above . Here is the way to match all these components together. backport, iwlwifi, mac80211 and cfg80211 come from the backport-iwlwifi git repository. You'll find the relevant Core branches there (release/LinuxCoreX). For all the Core releases, the master branch hostap should be taken. The firmware can be found in iwlwifi's linux-firmware clone. Please don't open bugs on versions that are advertised as End of life. Here is the table to help you finding the right version of the different components:
| Core release | status | backport-iwlwifi | Firmware API number |
|---|---|---|---|
| Core14 | Last version for 7260, 7265 and 3160 | LinuxCore14 | -17.ucode 7260 3160 7265 |
| Core26 | Last version for 3168 and 7265D | LinuxCore26 | -29.ucode 7265D3168 |
| Core33 | Last version for 8260 and 8265 | core33 | -36.ucode 82608265 |
| Core43 | Last version for 9260 and 9000 | core43 | -46.ucode 92609000AX 200 |
| Core45 | maintained | core45 | -48.ucode AX 200 |
| Core47 | maintained | core47 | -48.ucode AX 200 |
Devices not maintained in mainline
From time to time, we remove support for existing devices from the mainline code base of the firmware. This means that those devices won't benefit from new features, but bug fixes will be back-ported to the Core release branch on which they are supported. For those devices, it is recommended to take the latest Core available for the driver and the latest firmware. For example for 7260, the Core14 firmware should be used together with the latest Core available for the driver. The driver for all those devices is maintained as part of the kernel, but they won't get newer firmware features. Those devices and the latest Core firmware that supports them are:
Что такое файлы core на сервере?
Хотел скопировать файл сертификатов с локального компьютера на сервер командой » scp -i «путь_до_id_rsa путь_до_файла_моего_сертификата centos@99.99.99.99:/etc/ssl/certs».
Сервер спросил про подтверждение подключения по ssh. Я 2 раза ввел yes и yes и терминал завис — началось что-то типа
»
y
y
y
y
y
»
И так до бесконечности. Я сбросил процесс ctrl+C. В итоге на сервере — куча файлов core. И оказывается они по 20Mb в среднем
Core Release
When Eve enters Awakening Mode, Eve goes into Core Release mode and materializes the Queen’s Core. The Queen’s Core will follow Eve and react to help Eve by changing during offensive and defensive situations.
Queen’s Core
In Core Release mode, every successful command or Active hit or Special Active skill use will charge up the Queen’s Core. Once it appears at a certain charge, you can see when it reaches the next stage when the core flashes for a brief moment as it starts to shine brighter. The higher the level of the core, the more damage will be dealt when it fires and the more times it will be able to defend Eve from attacks.
Queen’s Shield
When Eve is attacked from the front on the ground while Queen’s Core is active, the core will switch to defense mode and cover Eve in a shield that absorbs a portion of the damage. While the core covers Eve in the Shield, pressing 
will allow Eve to phase back from the target in the same manner as Photon Flash. The core loses a level after defending. However, if you are continuously attacked, the core will only lose its level once the defending sequences stop.
Queen’s Laser
When Eve uses an Active or Special Active and hits a target, the Queen’s Core switches to offense mode and fires a blue laser at a target. The laser does multiple hits and will not knock down. The laser will lock on to the nearest target and track that target until all hits are dealt. The damage of the laser done depends on the core’s level.
The lasers will fire the moment the skill lands a successful hit and the target does not die on that hit. Certain skills will not cause the laser to fire immediately however. Illusion Stinger will only trigger the laser once an explosion hit connects, not when the spears do. Sonic Wave, Heaven’s Fist — Sweeper, and Surface Cutting will only fire the laser at the end of the skill. Some skills will also not trigger Queen’s Laser, such as Heaven’s Fist — Pressure.
At level 3 Awakening, a Powerful Queen’s Core is created. Unlike the normal Queen’s Core, the Queen’s Laser fired by this core will be colored red and can deal splash damage to groups of enemies. In addition, if the target is moved while they are being hit by the laser, the Powerful Queen’s Core will adjust its trajectory to lock onto the target.