Bug 26961 - system doesn't boot after replacing hardware
Summary: system doesn't boot after replacing hardware
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-16 17:45 CEST by peter lawford
Modified: 2020-07-19 20:37 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description peter lawford 2020-07-16 17:45:07 CEST
Description of problem:
I have replaced my old stuff:
mobo: chipset X58 socket lga1366  CPU: core i7960 Intel graphic card: nvidia gtx 9800+
by a more recentone:
mobo: chipset x99 socket 2011-3  CPU: core i7 6800  Intel  graphic card: nvidia gtx 1060

I used an usb key on which I have installed an iso image of mga7.1 with etcher
in order to update the system according to the new stuff; the update successfully happened, but the system is unable to boot
I try to add a new boot kernel option:  nokmsboot, but the result was the same
herebelow my graphic driver:

[root@magaux alain4]# rpm -qa|grep nvidia
nvidia-current-utils-430.64-8.mga7.nonfree
x11-driver-video-nvidia-current-430.64-8.mga7.nonfree
nvidia-current-doc-html-430.64-8.mga7.nonfree
nvidia-cuda-toolkit-10.1.168-1.2.mga7.nonfree
dkms-nvidia-current-430.64-8.mga7.nonfree
[root@magaux alain4]#

which is the latter ones



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2020-07-16 21:16:56 CEST
To make sure I understand: you changed the motherboard & retained the same disc. Then used a Mageia 7.1 ISO to update the installed system for the changed hardware? If so, did you notice what if anything was updated? Possibly nothing if you did not enable on-line media.
Was that step necessary? The processor/memory should not matter. I think USB etc is detected on boot. The changed video hardware would be the main thing: was there a change of driver from the previous nvidia gtx 9800+ to the new nvidia gtx 1060 ?
Did you try booting the new system without any change?
In what way does the 'updated' system not boot? To a blank scree, a Grub2 prompt? Do you see the Grub2 boot menu, and it does not boot from that?
Are you able to boot to a virtual console - rescue mode, or Ctl/Alt/Fn ?

CC: (none) => lewyssmith

Comment 2 peter lawford 2020-07-17 00:42:00 CEST
(In reply to Lewis Smith from comment #1)
> To make sure I understand: you changed the motherboard & retained the same
> disc. Then used a Mageia 7.1 ISO to update the installed system for the
> changed hardware? 
yes
> If so, did you notice what if anything was updated?
I think so, no package were downloaded and installed
> Possibly nothing if you did not enable on-line media.
yes, I have enabled internet link and all media depos <core, nonfree,tainted><release,updates>
> Was that step necessary? The processor/memory should not matter. I think USB
> etc is detected on boot. The changed video hardware would be the main thing:
> was there a change of driver from the previous nvidia gtx 9800+ to the new
> nvidia gtx 1060 ?
no change, strangely my gtx 9800+ works very well with nvidia-430-64-8.mga7.nonfree drivers
> Did you try booting the new system without any change?
yes, but unsuccessfully
> In what way does the 'updated' system not boot? To a blank scree, a Grub2
> prompt? Do you see the Grub2 boot menu, and it does not boot from that?
> Are you able to boot to a virtual console - rescue mode, or Ctl/Alt/Fn ?
at the beginning I see the grub2 menu, and the boot process initiates normally; but a couple of steps after "research of new peripherals", the boot process stalls, and at the left bottom corner of the screen, a dash is endless blinking.
the best is that I do a snapshot of the screen just at this moment, when the boot process stalls
Comment 3 Morgan Leijström 2020-07-17 10:55:21 CEST
If you try rescue mode, do you get to a prompt?

If not, i would try a reinstall, keep in all partitions, update media enabled.
That is what you tried?

Failing that, i would try the same but only keeping /home (and if you have other partitions with user data)

CC: (none) => fri
Summary: system doesn't boot after replacing old stuff by a more recent one => system doesn't boot after replacing hardware

Comment 4 peter lawford 2020-07-17 13:03:07 CEST
(In reply to Morgan Leijström from comment #3)
> If you try rescue mode, do you get to a prompt?
 yes, I attempted two boot methods:
 - on kernel-5.6.14-server-2 with no option
 - on kernel-5.6.14-desktop-2 with options faisafe nokmsboot
both failed as above describded
> If not, i would try a reinstall, keep in all partitions, update media
> enabled.
possible, but I don't remember the line command which keeps in memory all already installed packages in order to reinstall them at once
> That is what you tried?
I didn't yet tried
> Failing that, i would try the same but only keeping /home (and if you have
> other partitions with user data)
Comment 5 Frank Griffin 2020-07-17 14:09:04 CEST
I did this once years ago (transplanted a harddrive from one laptop to another with different graphics hardware).  The boot got to harddrake2 ("Checking for new hardware") and appeared to stall.  I left the machine, not knowing what to do other than reinstall.  I happened to check back an hour or two later, and the boot had completed and graphics worked fine.

I have no idea what the machine was doing all that time, but I was quite impressed that MGA had figured everything out and reconfigured the system for the new hardware.

CC: (none) => ftg

Comment 6 peter lawford 2020-07-17 17:52:17 CEST
(In reply to Frank Griffin from comment #5)
> I did this once years ago (transplanted a harddrive from one laptop to
> another with different graphics hardware).  The boot got to harddrake2
> ("Checking for new hardware") and appeared to stall.  I left the machine,
> not knowing what to do other than reinstall.  I happened to check back an
> hour or two later, and the boot had completed and graphics worked fine.
> 
> I have no idea what the machine was doing all that time, but I was quite
> impressed that MGA had figured everything out and reconfigured the system
> for the new hardware.

thank you very much for this good new; perhaps I am too impatient and hate to wait a long while; I'll follow your experience and report the result on this post
Comment 7 peter lawford 2020-07-18 14:21:15 CEST
I have checked on the nvidia's site that the driver nvidia-430.64 is suitable for the card gtx-1060
Comment 8 peter lawford 2020-07-19 17:02:05 CEST
the problem seems to be solved:
1) when upgrading with the usb key iso media, I have forgotten to set the graphic driver to "Geforce 635 serie and later"
2) it is necessary to add the boot option kernel "nokmsboot"
and now with the new stuff I boot much more quickly than with the old one
Comment 9 Lewis Smith 2020-07-19 20:37:10 CEST
> the problem seems to be solved
Godd. Thank you Peter for your efforts.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.