Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
After kernel update, the version of kernel in uname is not updated itself.
It is a problem because all the modules are loaded through it, so I had to rename the folder with new modules to the old version (as a temporary solution) but I would like to solve this problem properly.
~: pacman -Q linux
linux 4.9.11-1
~: uname -r
4.9.8-1-ARCH
Have you replace the kernel image (bzImage or vmlinuz)?. If yes then there is some issue with your grub conf parameter. Otherwise you need to replace the kernel image as well as.
Below are the steps which you need to update the kernel:
1) Replace your kernel image (vmlinuz or bzImage you can check the name from your grub conf parameters) with the existing kernel image..
2) Copy the new module folder (containing all new modules) into the /lib/modules folder..
3) Sometimes there may be issue during module loading. So you can run the depmod -a command inside your new module folder.
4) Reboot the board and check the kernel version and your kernel image details (like kernel version and date of compiled kernel image) though uname -a command.*
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am on termux with root permission.
My phone has aarch64 cpu architecture.
I'm trying to chroot a ubuntu filesystem with amd64 architecture
i've seen and this https://unix.stackexchange.com/a/222981
here's my command
sudo chroot ubuntu /bin/qemu-x86_64-static /bin/bash --login
i logged in successfully but when i run command
ls or any
it's give an error like Exec format error
then i tried that command with qemu-x86_64-static like qemu-x86_64-static /bin/ls it's execute successfully
any idea for this???
i think i can add alias for all command for starts with qemu-x86_64-static but that's not good idea...
You need to tell the kernel that when it sees an arm64 binary it should run it by launching QEMU. The mechanism for this is called "binfmt-misc", and to configure it you need to write data in the correct format to special files in the host system's /proc/sys/fs/binfmt_misc/ directory. Most Linux distros will do this for you automatically when you install their QEMU packages, but obviously Android won't do this for you.
First check that your phone's kernel has binfmt-misc support compiled in at all: there should be a file /proc/sys/fs/binfmt_misc/status and if you cat its contents it should read enabled. If not, try modprobe binfmt_misc. If after that the status file is still not there then you won't be able to get this working unless you can somehow build a new kernel for your phone.
If the support is present in your phone's kernel, you can try the qemu-binfmt-conf.sh script that upstream QEMU ships as a mechanism for registering QEMU with the binfmt-misc machinery:
https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh
(This is just a script which writes the correct lines of data to /proc/sys/fs/binfmt_misc/register.)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am using GPT/UEFI system. I installed KDE Neon and I was using it without any problem since the summer. Then today, I deleted /EFI/ubuntu/ and after I reboot the system, it stuck at grub command line "grub> ".
1- I can boot the system by writing following command to the grub command line
configfile (hd0,gpt1)/EFI/neon/grub.cfg
2- Also following command works
configfile (hd0,gpt2)/boot/grub/grub.cfg
3- Also following command works
set prefix=(hd0,gpt2)/boot/grub
set root=(hd0,gpt2)/boot
normal
4- I tried followings to fix by booting the system but non of them works
- boot-repair program
- update-grub
- apt install --reinstall grub-efi && update-grub
So this is the situation. How can I fix the problem ?
Thanks in advance.
I have just fixed the problem!
I boot the system manually by entering command to grub> command line. (one of the command that I mentioned in the question)
I opened a terminal.
cd /boot/efi/EFI
cp -r ./neon ./ubuntu
Reboot and it works fine.
I think the problem is specific for KDE Neon because it gave me exactly same problem when I installed it to a new computer. Grub is not looking inside the "/EFI/neon" directory. Instead, it is looking inside "/EFI/ubuntu" but cannot find it so it causes problem.
BTW, the reason I named new folder as "ubuntu" is that KDE Neon is Ubuntu based.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
It goes wrong when I reboot my CentOS7.0 system, after executing yum update -y kernel and selecting the latest kernel version during rebooting.
Executing yum update -y kernel command, the kernel version like below:
current kernel version is 3.10.0-514.el7.x86_64, and the latest version is 3.10.0-693.2.2.el7.x86_64,
After executing reboot command, I select the first kernel (the latest version),
but it goes wrong, wrong details like below:
wn-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tained 3.10.0-693.2.2.el7.x86_64
Hadware name: ...
Call trace:
...
Kernel Offset: disables
My CentOS version is 7.0, and it was installed basing on VirtualBox.Why does it go wrong?
I have solved the problem, if you want to upgrade your CentOS system kernel, you must excute following steps:
excuting yum install -y kernel or yum update -y kernel command;
excuting vi /etc/default/grub command, set GRUB_DEFAULT=0, it means that the first kernel will be default kernel;
excuting grub2-mkconfig -o /boot/grub2/grub.cfg command(CentOS 7.0 version), it aimes to generate a new kernel configuration;
reboot your system;
Maybe I use this method just in my case, someone who have a good method can add a comment at bellow, thanks.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am trying to install Anaconda for Linux (Linux Mint 17.2 Rafaela, 14.04.3 LTS, Trusty Tahr).
I see a warning:
WARNING:
Machine does not appear to be ppc64le. This software was sepicically
build for POWER8 running Ubuntu 14.04 LTS.
Are sure you want to continue the installation? [yes|no]
What should I do?
Is the machine a power8 or x86? More than likely you have an x86 cpu so you need to install that version of Anaconda. Anaconda Repo. You can use the command uname -a from the command line to print the kernel version. Normally you would see something in the output that says like "x86_64".
As for the anaconda versions, notice the differences between these two file names.
Anaconda2-4.4.0-Linux-x86_64.sh
Anaconda2-4.4.0-Linux-ppc64le.sh
:::EDIT:::
Based on the your warning "WARNING: Machine does not appear to be ppc64le.", it sounds like you have an x86 cpu. To be sure, run the command uname -a.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I was trying to down-version glib library installed on my Red Hat 6.4 server. First, I uninstalled it using-
rpm -e --nodeps glib
After that I am unable to execute terminal commands (e.g. ls, cd). Now, I want to recover my system. How can do that? Thanks.
[I have Red Hat 6.4 iso. I tried to see any option given while booting from it. But unable to find.]
Boot the machine to rescue mode.
Mount the CD/DVD to some temp directory
mkdir temp
mount /dev/hdc temp
Check the output of the to find any missing files and dependencies.
rpm -Va
Now find the rpm location on the CD/DVD/ISO.
Install the RPM manually.
rpm -ivh --force --noscripts --root=/mnt/sysimage /path/to/glibc.rpm /path/to/other/missing.rpm
Reboot the system and run rpm -Va again