Moderator: Staff
-
Martin
- Posts: 36
- Joined: Fri Sep 16, 2016 10:34 am
Re: Error: current running kernel is NOT supported
Post
by Martin » Wed Oct 19, 2016 3:33 am
Hello,
Have you rebooted the server after installing cloudlinux ? The error should be fixed after rebooting the server.
Check the server kernel if you’re still getting this error after server reboot. You will get this error if the loaded kernel is not a cloudlinux kernel. Type the command «uname -a» to check the current kernel.
Edit grub.conf file and change the kernel to cloudlinux kernel, reboot the server.
Martin
Support Staff
Nixtree Solutions
Managed Backups || Server Management
https://www.nixtree.com
It seems to be a perpetual problem, almost like trying to find a winning lottery number. For example, the psp-8.6.0 (10 Sep 2010) for SLES 10 claims to support the following kernel versions (from the install log, after it fails):
2.6.16.60-0.34
2.6.16.60-0.37_f594963d
2.6.16.60-0.39.3
2.6.16.60-0.54.5
2.6.16.60-0.57.1
2.6.16.60-0.58.1
2.6.16.60-0.66.1
If you have SLES 10 SP3, then the kernel should be one of:
SP3-Oct-2009 2.6.16.60-0.54.5
Nov-12-2009 2.6.16.60-0.57.1
Dec-14-2009 2.6.16.60-0.58.1
Jan-22-2010 2.6.16.60-0.59.1
Mar-29-2010 2.6.16.60-0.60.1
Apr-26-2010 2.6.16.60-0.62.1 (x86_64 only)
Jun-11-2010 2.6.16.60-0.66.1
Aug-17-2010 2.6.16.60-0.67.1
Sep-03-2010 2.6.16.60-0.68.1
Sep-22-2010 2.6.16.60-0.69.1
So you have perhaps at best a 40% chance of getting the psp to install agents/drivers, more like a 0% chance if you keep your kernel up-to-date with security patches etc.
(If you still have older SLES 10 SP2, then there’s about 17 kernel possibilities, 3 of which are supported, not including the latest 6 kernels released after May 2009)
So if you do have, for example, the latest SLES 10 SP2 and want to install the psp, you can apply SLES 10 SP3 with no further patches, then should be able to install the psp. What happens after that when you install a current kernel update?
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Assignees
Comments
Kernels with usb hid gadgets where keyboard is hidg0 and mouse is hidg1 are supported. No other kernel is supported as I can’t verify the proper intended working of the app. Use the kernel provided for hammerhead with NetHunter 2019.4 Android6 or use https://github.com/mayankmetha/Nethunter-Hammerhead-Kernel if you using Lineage 14.x.
I have tested it with both these kernels and it works well.
I’m getting kernel not supported on my Nexus 5 running nethunteros. Are there any logs I can give you to figure out why it’s popping up?
Kernel does not have hid interface/device files hence it isn’t supported. NethunterOS isn’t supported as it’s a unsupported project. Only the Android Kali Linux NetHunter Builds on their website for nexus 5 is supported.
…
On Sun, Jan 19, 2020, 10:01 AM Mayank Metha D ***@***.***> wrote:
Kernel does not have hid interface/device files hence it isn’t supported.
NethunterOS isn’t supported as it’s a unsupported project. Only the Android
Kali Linux NetHunter Builds on their website for nexus 5 is supported.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8?email_source=notifications&email_token=AFURNMFD5FL7DP3OUPZ3553Q6SIODA5CNFSM4J6T7ISKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJKYGYA#issuecomment-576029536>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURNMGDSWFFTFUBXWF4JC3Q6SIODANCNFSM4J6T7ISA>
.
I installed «LOS-hammerhead-14.1-20170102-nethunteros» with kali-fs in the chroot is Rucky works great.
I’ll try that out. Thanks!
…
On Sun, Jan 19, 2020, 1:17 PM anduril-glitch ***@***.***> wrote:
I installed «LOS-hammerhead-14.1-20170102-nethunteros» with kali-fs in the
chroot is Rucky works great.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8?email_source=notifications&email_token=AFURNMETEZAYP5JLUXSTIYTQ6S7PTA5CNFSM4J6T7ISKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJK4ZVQ#issuecomment-576048342>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURNMHHXYAIAUYYUGIRR2DQ6S7PTANCNFSM4J6T7ISA>
.
I installed «LOS-hammerhead-14.1-20170102-nethunteros» with kali-fs in the chroot is Rucky works great.
Just tried it and I’m getting the same error. Are you sure you don’t have another kernel installed?
At home it works thunder with the kernel, I even tried without kali-fs
There are 3 in hammerhead, try the 3
Solution: used nethunteros-nethunter-hammerhead-cm-14.1-hammerh.zip from
build.nethunter.com.
Flashed kernel-nethunter-hammerheadmon-nougat-2019.03-13-0514.zip from
build.nethunter.com.
Setup the latest kalifs (armhf full version) opened androidsu shell, typed
in setprop sys.usb.config hid and then I was able to use Rucky.
Solution: used nethunteros-nethunter-hammerhead-cm-14.1-hammerh.zip from build.nethunter.com. Flashed kernel-nethunter-hammerheadmon-nougat-2019.03-13-0514.zip from build.nethunter.com. Setup the latest kalifs (armhf full version) opened androidsu shell, typed in setprop sys.usb.config hid and then I was able to use Rucky.
Nice work. Hope this solution will benefit others also. 🙂
Эта статья предоставит вам информацию о том, как установить исходный код ядра в системе CentOS / RHEL Linux.
В качестве альтернативы он проведет вас через простой процесс устранения неполадок в случае, если вы уже установили исходные коды / заголовки ядра, и все еще получаете сообщение об ошибке ниже:
ERROR: Unable to find the kernel source tree for the currently running kernel. Please make sure you have installed the kernel
source files for your kernel and that they are properly configured; on Red Hat Linux systems, for example, be sure you have
the 'kernel-source' or 'kernel-devel' RPM installed. If you know the correct kernel source files are installed, you may
specify the kernel source path with the '--kernel-source-path' command line option.
В этом уроке вы узнаете:
- Что такое kernel-headers
- Что такое kernel-devel
- Как проверить версию ядра
- Как проверить установленную версию kernel-devel
Как установить kernel headers и kernel devel на CentOS / RHEL
Вы можете установить либо заголовки ядра, либо ядро devel отдельно, либо установить их как часть пакета инструментов разработки.
Рекомендуемая и наиболее вероятная установка всего группового пакета средств разработки:
# dnf groupinstall "Development Tools"
В качестве альтернативы установите оба пакета kernel-devel и / или kernel-headers отдельно:
# dnf install kernel-headers # dnf install kernel-devel
Проверьте вашу установку и убедитесь, что оба пакета kernel-devel и / или kernel-headers соответствуют текущей загруженной версии ядра.
Вот пример.
Сначала проверьте версию ядра Linux:
$ uname -a Linux sandbox 4.18.0-80.11.2.el8_0.x86_64 #1 SMP Tue Sep 24 11:32:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Запишите версию ядра и сравните ее с пакетными версиями kernel-devel и / или kernel-headers:
# rpm -qa | grep -E "kernel-devel|kernel-headers" kernel-headers-4.18.0-80.11.2.el8_0.x86_64 kernel-devel-4.18.0-80.11.2.el8_0.x86_64
Если они совпадают с вашими, все ок!
В противном случае ваша система может быть не синхронизирована.
Выполните следующий шаг для решения этой проблемы:
С помощью команды dnf синхронизируйте вашу систему, чтобы убедиться, что вы используете самые последние пакеты:
Перезагрузите систему и еще раз проверьте, что версия ядра соответствует версиям пакета kernel-devel и / или kernel-headers.
You may also like
Leave a Comment
■ Requirement : check whether current running kernel is tainted(contaminated) or not
■ OS Environment : Linux, RHEL, Centos
■ Resolution :
The Linux kernel maintains a»taint state» which is included in kernel error messages. The taint state provides an indication whether something has happened to the running kernel that affects whether a kernel error or hang can be troubleshoot effectively by analysing the kernel source code. Some of the information in the taint relates to whether the information provided by the kernel in an error message can be considered trustworthy.
1. Following command could be used :
$ cat /proc/sys/kernel/tainted
536870912
Use the following to decipher the taint value :
Non-zero if the kernel has been tainted. Numeric values, which can be ORed together:
1 — A module with a non-GPL license has been loaded, this includes modules with no license. Set by modutils >= 2.4.9 and module-init-tools.
2 — A module was force loaded by insmod -f. Set by modutils >= 2.4.9 and module-init-tools.
4 — Unsafe SMP processors: SMP with CPUs not designed for SMP.
8 — A module was forcibly unloaded from the system by rmmod -f.
16 — A hardware machine check error occurred on the system.
32 — A bad page was discovered on the system.
64 — The user has asked that the system be marked «tainted». This could be because they are running software that directly modifies the hardware, or for other reasons.
128 — The system has died.
256 — The ACPI DSDT has been overridden with one supplied by the user instead of using the one provided by the hardware.
512 — A kernel warning has occurred.
1024 — A module from drivers/staging was loaded.
268435456 — Unsupported hardware
536870912 — Technology Preview code was loaded
The taint status of the kernel not only indicates whether or not the kernel has been tainted but also indicates what type(s) of event caused the kernel to be marked as tainted. This information is encoded through single-character flags in the string following «Tainted:» in a kernel error message.
* P: Proprietary module has been loaded, i.e. a module that is not licensed under the GNU General Public License (GPL) or a compatible license. This may indicate that source code for this module is not available to the Linux kernel developers.
* G: The opposite of P: the kernel has been tainted (for a reason indicated by a different flag), but all modules loaded into it were licensed under the GPL or a license compatible with the GPL.
* F: Module has been forcibly loaded using the force option «-f» of insmod or modprobe, which caused a sanity check of the versioning information from the module (if present) to be skipped.
* S: SMP with CPUs not designed for SMP. The Linux kernel is running with Symmetric MultiProcessor support (SMP), but the CPUs in the system are not designed or certified for SMP use.
* R: User forced a module unload. A module which was in use or was not designed to be removed has been forcefully removed from the running kernel using the force option «-f» of rmmod.
* M: System experienced a machine check exception. A Machine Check Exception (MCE) has been raised while the kernel was running. MCEs are triggered by the hardware to indicate a hardware related problem, for example the CPU’s temperature exceeding a treshold or a memory bank signaling an uncorrectable error.
* B: System has hit bad_page, indicating a corruption of the virtual memory subsystem, possibly caused by malfunctioning RAM or cache memory.
* U: Userspace-defined naughtiness.
* D: Kernel has oopsed before
* A: ACPI table overridden.
* W: Taint on warning.
* C: modules from drivers/staging are loaded.
* I: Working around severe firmware bug.
The taint flags above are implemented in the standard Linux kernel and indicate the information provided in kernel error messages is not necessarily to be trusted. Additionally, the following flags are used by the RHEL kernel:
* H: Hardware is unsupported.
* T: Technology Preview code is loaded.