SCIENTIFIC-LINUX-USERS Archives

January 2019

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"S. Vergani" <[log in to unmask]>
Reply To:
S. Vergani
Date:
Tue, 29 Jan 2019 15:27:30 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
Dear Andrew,

uname -r reports "3.10.0-957.1.3.el7.x86_64". What should I search/do in 
/boot/grub2?


Many thanks,

Stefano



On 2019-01-29 11:42, Andrew C Aitchison wrote:
> On Mon, 28 Jan 2019, S. Vergani wrote:
> 
>> I am running scientific linux on a ThinkPad t440p. During the past 1.5 
>> years, I have been experiencing the same apparently unsolvable problem 
>> with SL 7.5. Every time I closed the pc without locking it or I tried 
>> to restart it, the pc froze and the only thing to do was to force shut 
>> down. I have been using GNOME classic but with any other desktop as 
>> well (I tried them all) the problem persisted.
>> 
>> I upgraded yesterday to SL 7.6 and finally the issue disappeared. This 
>> morning I started again the session and SL was back to 7.5. When I 
>> start the session (I have windows 7 dual-boot) I can choose only 
>> between some versions of SL 7.5 and windows. The aesthetics is then 
>> exactly as it was with SL 7.5, but when I check which version I am 
>> running it shows SL 7.6. The old issue came back and again it freezes 
>> every time.
>> 
>> Could someone help me with the matter? To summarize, the selections 
>> during boot phase, the aesthetics, and the old issues of SL 7.5 are 
>> back, but I upgraded to SL 7.6 and when I ask for the OS the output is
>> 
>> NAME="Scientific Linux"
>> VERSION="7.6 (Nitrogen)"
>> ID="scientific"
>> ID_LIKE="rhel centos fedora"
>> VERSION_ID="7.6"
>> PRETTY_NAME="Scientific Linux 7.6 (Nitrogen)"
>> ANSI_COLOR="0;31"
>> CPE_NAME="cpe:/o:scientificlinux:scientificlinux:7.6:GA"
>> HOME_URL=" 
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.scientificlinux.org__&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=a0amwAn6gauOoqL5j2vXdxFfTDRJFEhns9i6FkKaaeM&s=8CvDnyTcYae4a6uXNOdWjq9mNZ7DpGLmBWo9fBeu6Ws&e=
>> BUG_REPORT_URL="mailto:[log in to unmask]"
>> 
>> REDHAT_BUGZILLA_PRODUCT="Scientific Linux 7"
>> REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
>> REDHAT_SUPPORT_PRODUCT="Scientific Linux"
>> REDHAT_SUPPORT_PRODUCT_VERSION="7.6"
> 
> What does
> 	uname -r
> report ?
> 
> I'm guessing that the update did not upgrade the kernel properly
> (this is more likely sincx this is a dual-boot system)
> and the boot loader is not looking for the kernel where the update
> put the SL7.6 kernel, but found the old kernel from SL7.5.
> 
> I'm still on SL6 which uses grub as the boot loader;
> SL7 uses grub2 which is sufficiently different that I can't really
> say what you sould do to fix it; but looking in
> /boot /boot/grub or perhaps /boot/grup2 may give you a clue.
> - these directories will probably contain the new kernels,
> not the ones which are actually being used.
> 
> You might even have a separate /boot partition, or had one before you
> upgraded; that could confuse both you and the machine.
> 
> Sorry this is rather vague.

-- 
Stefano Vergani
Doctor of Philosophy Student
STFC Data Intensive Science Studentship Beneficiary
Department of Physics, Cavendish Laboratory
King's College, University of Cambridge

ATOM RSS1 RSS2