When upgrading CentOS7.0 kernel version, it goes wrong when rebooting [closed] - linux

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.

Related

Grub can't find grub.cfg file -- Stuck at GRUB Command Line [closed]

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.

Kernel version doesn't update in uname -r (Arch Linux) [closed]

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.*

How to avoid GRUB errors after running apt-get upgrade - Ubuntu [closed]

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 6 years ago.
Improve this question
I'm running ubuntu 14.04 on an EC2
After running apt-get upgrade
I'm prompted with a screen that asks me to reinstall GRUB boot loader
The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices.
How do I know which device should I select?
What if I have mounted on my machine some additional EBS, should I select them as well?
Can I avoid this prompt, during the upgrade or supply some defaults to the command?
The following prompt is
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.
install the package maintainer's version
keep the local version currently installed
show the differences between the versions
show a side-by-side difference between the versions
show a 3-way difference between available versions
do a 3-way merge between available versions (experimental)
start a new shell to examine the situation
The same q's here:
How do I know which one should I select?
Can I avoid this prompt, during the upgrade or supply some defaults to the command?
I had similar problem.
1) If you take a look man apt-get, you will find a configuration option-o.
It allows to set options for Debian package manager dpkg.
2) In the manual man dpkg you can find set of options --force-confdef(force to keep default option without prompting) and --force-confold (force to keep old conf files)
In some sources I found, that people pass env variable DEBIAN_FRONTEND=noninteractive as well, but I could not find it in any manual.
So, the final command in .sh script, that I use to run upgrade:
sudo DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" upgrade

Recovering Red Hat 6.4 [closed]

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

Fedora 20 - how to install applications? [closed]

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 6 years ago.
Improve this question
I just installed Fedora 20 on my laptop.
I've never been the Administrator of a Linux machine and so...I don't know how to install application on it! :D
Could you please help me ?
I tried using some command like :
sudo apt-get ....
But it fails because something is not installed, and I also tried to use the new software center, but there are no applications inside, I can only see some squares with 3 points inside them and that's all.
I just started using Linux, so I'm sorry in advance if I'll make stupid questions!
Thank'you all!
You need to type: sudo yum install "whatever without parenthesis".
Or, switch to the root account and you won't have to type sudo in front of everything.
You can use yum install application to install softwares on Fedora also refer http://www.wikihow.com/Install-Software-in-Fedora for your reference
On Fedora 22, it seems the app for managing software is no longer yum, but dnf. So, first update by running dnf updateinfo and then run gnome-software which is a GUI, or dnf search <something>.
dnf search java
dnf install java-1.8.0-openjdk

Resources