SOLVED: Mageia 6 Fails to boot after installing updates

SOLVED: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 6th, '19, 20:16

I got a new hp laptop 17-BY1053DX with Windows intending to install Linux initially as dual boot. Unfortunately almost every distro I tried failed to boot the live image including attempting to install Mageia 7 from the network install image. But I tried a USB I already had for Mageia 6 and it successfully booted the live usb without any apparent problems and successfully installed to the system and ran great.

Since I wanted to use this system for some time, I decided to install all updates but after updating, the system would no longer boot.

I tried other distributions and I was able to run Debian live usb by editing grub to boot to runlevel 3, so my suspicion was that something was wrong with my graphics drivers. But then attempting to install Debian (from the non-graphical installer) so I could look at XOrg log files, etc, the system became unresponsive at the "Detecting Hardware to Find CD-ROM device" semi-graphical screen. Also other distros hang detecting hardware for example at lvm startup actions, so it is not certain it is (only) the graphics causing problems.

So I have re-installed Mageia 6 and my plan is to install updates one at a time (or at least in some systematic way) to try to find what hardware/driver/version is causing problems.

Any recommendations of best ways to do this are welcome.

Here is some info about my system and hardware:

My graphics card is an Intel UHD Graphics 620.

lspci says:
Code: Select all
00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Device 3ea0 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Device 9df9 (rev 30)
00:14.0 USB controller: Intel Corporation Device 9ded (rev 30)
00:14.2 RAM memory: Intel Corporation Device 9def (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 9de8 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 9de9 (rev 30)
00:16.0 Communication controller: Intel Corporation Device 9de0 (rev 30)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30)
00:1c.0 PCI bridge: Intel Corporation Device 9dbc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 9db0 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Device 9db1 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 9db4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 9d84 (rev 30)
00:1f.3 Audio device: Intel Corporation Device 9dc8 (rev 30)
00:1f.4 SMBus: Intel Corporation Device 9da3 (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 9da4 (rev 30)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device d723
04:00.0 Non-Volatile memory controller: Sandisk Corp Device 5003 (rev 01)

lsusb says:
Code: Select all
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0408:5321 Quanta Computer, Inc.
Bus 001 Device 002: ID 046d:c024 Logitech, Inc. MX300 Optical Mouse
Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsblk says:
Code: Select all
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sr0          11:0    1  1024M  0 rom 
nvme0n1     259:0    0 238.5G  0 disk
├─nvme0n1p5 259:5    0  50.3G  0 part /
├─nvme0n1p3 259:3    0  76.6G  0 part /media/windows
├─nvme0n1p1 259:1    0   260M  0 part /boot/EFI
├─nvme0n1p6 259:6    0     4G  0 part [SWAP]
├─nvme0n1p4 259:4    0   471M  0 part
├─nvme0n1p2 259:2    0    16M  0 part
└─nvme0n1p7 259:7    0 106.9G  0 part /var

Comments are welcome if anyone sees any hardware known to cause problems in that list or a better command to show more hardware details.

Thanks

Phil
Last edited by sln123 on Dec 11th, '19, 02:19, edited 2 times in total.
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby doktor5000 » Dec 7th, '19, 01:27

sln123 wrote:Since I wanted to use this system for some time, I decided to install all updates but after updating, the system would no longer boot.

How and at what point did it fail during the boot process? Before the boot loader, after boot loader, how far did it get? What about single-user/failsafe mode ?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby sln123 » Dec 7th, '19, 06:52

At the time, I was fed up with repeated failures and didn't track as carefully as I should have. I think I got past boot loader, but not very far after that.

Anyway, I just repeated the update with a different result. Halfway through updates I got a large font message on the screen that overflowed the screen so some contents were lost. Most of what it said was:
Screen locker is broken and unlocking is not possible any
rder to unlock switch to a virtual terminal (e.g. Ctrl+Alt+
log in and execute the command:

loginctl unlock-sessions

afterwards switch back to the running session (Ctrl+Alt+F


Ctrl-Alt-F2 got me to a command line loging screen where I was able to login.

Running loginctl unlock-sessions ran, but no Ctrl-Alt combinations got me back to the gui.

Note that I never rebooted this time.

I'll try more experiments, but gotta go now.

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby doktor5000 » Dec 7th, '19, 16:21

sln123 wrote:
Screen locker is broken and unlocking is not possible any
rder to unlock switch to a virtual terminal (e.g. Ctrl+Alt+
log in and execute the command:

loginctl unlock-sessions

afterwards switch back to the running session (Ctrl+Alt+F


That is pretty much normal when you run it inside a graphical session, and unlocking or switching back and forth between tty's should not be an issue, I've already done this several times without issues.

You can prevent that from doing all of the upgrade in runlevel 3. This is also recommended in the release notes:
https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_online.2C_using_urpmi_.28CLI.29 wrote:The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby sln123 » Dec 10th, '19, 00:08

Now that I found time, I rebooted the system and it hung immediately after starting kernel from grub. The last message on the screen appeared before without affecting the boot, but for reference it was:
Code: Select all
[     2.630574] Bluetooth: hci0: didn't find patch for chip id 2

After that the cursor is not flashing and keyboard is unresponsive.
Then restart by holding power button down for 5 seconds, waiting several seconds and pressing power, grub does not accept keystrokes, but power off and on in grub allows input. Once grub allows input, select Advanced options for Mageia, select Mageia (4.14.145-desktop-2.mga6) (recovery mode)
Boot (into recovery mode) gets much further, but hangs with last output:
Code: Select all
[    38.844077] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff

Power off and on again, grub is again finicky, but after several power off/on, grub accepts keystrokes, so now type e at normal Mageai entry, replace splash quiet with 3 and press Ctrl-X and boot hangs with same last msg as above regarding nvme.
Power off and on again, grub is again finicky, but eventually select Advanced options for Mageia, now select Mageia (4.9.35-desktop-1.mga6) 6 (recovery mode).
This time it gets to prompt: "Give root password for maintenance (or press Control-D to continue):", then outputs more system messages, but entering root password gets me to command prompt.
journalctl --list-boots lists 7 boots: 3 from last Friday when I updated and 4 from this morning following up. I have captured journalctl -ab for each of these 7 boots on a usb stick, but the smallest is 793 lines and the largest is 10212, so I'll wait to post pending advice on usefulness of specific boot logs or other information. The system is still running in this recovery command line for now.

I believe this is the same behavior as last time I tried updating, but with more careful notes and extra debugging.

Let me know how you recommend to proceed. I am willing to re-install and repeat, but I will wait to retain the opportunity for additional debugging with this running command line.

Thanks

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby doktor5000 » Dec 10th, '19, 00:31

I'd suggest to try to install on something that's not attached via NVMe, if that's a possibility. Even if only for temporary testing.
And if you get to recovery mode, then it should also be possible to switch to multi-user mode (init 3 or systemctl isolate multi-user.target) to get the network up, then try urpmi --auto-update to check if the upgrade has completed.

Also what about booting any of the live DVD media, do they boot and work properly ?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby sln123 » Dec 10th, '19, 01:07

A quick review of boot logs shows boot -4 is the update boot and runs through the weekend. That log shows update starting Dec 06 and kscreenlocker_greet messages at Dec 06 20:53:04 and system shutdown at Dec 09 11:54:29. It is very long, but nothing jumps out at me of particular value.

Boot -3 ends with the following lines:
Code: Select all
Dec 09 11:55:02 localhost kernel: Linux video capture interface: v2.00
Dec 09 11:55:02 localhost systemd-udevd[551]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:1d.4/0000:04:00.0': No such file or directory
Dec 09 11:55:02 localhost systemd[1]: Found device /dev/nvme0n1p1.
Dec 09 11:55:02 localhost systemd[1]: Mounting /boot/EFI...
Dec 09 11:55:02 localhost systemd[1]: Found device /dev/nvme0n1p3.
Dec 09 11:55:02 localhost kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Dec 09 11:55:02 localhost kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 09 11:55:02 localhost systemd[1]: Mounting /media/windows...
Dec 09 11:55:02 localhost kernel: uvcvideo: Found UVC 1.00 device HP Webcam (0408:5321)
Dec 09 11:55:02 localhost kernel: r8169 0000:02:00.0 eth0: RTL8168h/8111h at 0xffffa6cd40d91000, 00:68:eb:66:a4:ba, XID 14100800 IRQ 137
Dec 09 11:55:02 localhost kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Dec 09 11:55:02 localhost systemd[1]: Found device /dev/nvme0n1p6.
Dec 09 11:55:02 localhost systemd[1]: Activating swap /dev/nvme0n1p6...
Dec 09 11:55:02 localhost kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Dec 09 11:55:02 localhost kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Dec 09 11:55:02 localhost kernel: ACPI: AC Adapter [AC] (on-line)
Dec 09 11:55:02 localhost kernel: input: HP Wireless hotkeys as /devices/virtual/input/input5
Dec 09 11:55:02 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 7 was not initialized!
Dec 09 11:55:02 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Processing 2 was not initialized!
Dec 09 11:55:02 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized!
Dec 09 11:55:02 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 4 was not initialized!
Dec 09 11:55:02 localhost kernel: input: HP Webcam: HP Webcam as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input6
Dec 09 11:55:02 localhost kernel: usbcore: registered new interface driver uvcvideo
Dec 09 11:55:02 localhost kernel: USB Video Class driver (1.1.1)
Dec 09 11:55:02 localhost kernel: Adding 4194300k swap on /dev/nvme0n1p6.  Priority:-2 extents:1 across:4194300k SSFS
Dec 09 11:55:02 localhost systemd[1]: Mounted /boot/EFI.
Dec 09 11:55:02 localhost systemd[1]: Activated swap /dev/nvme0n1p6.
Dec 09 11:55:02 localhost systemd[1]: Reached target Swap.
Dec 09 11:55:02 localhost systemd[1]: Mounting Temporary Directory...
Dec 09 11:55:02 localhost systemd[1]: Found device /dev/nvme0n1p7.
Dec 09 11:55:02 localhost systemd[1]: Starting File System Check on /dev/nvme0n1p7...
Dec 09 11:55:02 localhost systemd[1]: Mounted Temporary Directory.
Dec 09 11:55:02 localhost systemd-fsck[572]: /dev/nvme0n1p7: clean, 981/7004160 files, 659607/28007424 blocks
Dec 09 11:55:02 localhost systemd[1]: Started File System Check on /dev/nvme0n1p7.
Dec 09 11:55:02 localhost systemd[1]: Mounting /var...
Dec 09 11:55:02 localhost kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: (null)
Dec 09 11:55:02 localhost systemd[1]: Mounted /var.
Dec 09 11:55:02 localhost systemd[1]: Starting Load/Save Random Seed...
Dec 09 11:55:02 localhost kernel: fuse init (API version 7.26)
Dec 09 11:55:02 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 09 11:55:02 localhost systemd[1]: Started Load/Save Random Seed.
Dec 09 11:55:02 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Dec 09 11:55:02 localhost kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Dec 09 11:55:02 localhost kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Dec 09 11:55:02 localhost kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Dec 09 11:55:02 localhost kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Dec 09 11:55:02 localhost kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Dec 09 11:55:02 localhost systemd-journald[459]: System journal (/var/log/journal/) is 40.0M, max 4.0G, 3.9G free.
Dec 09 11:55:02 localhost systemd-journald[459]: Time spent on flushing to /var is 51.154ms for 788 entries.


Boot -2 last lines are similar:
Code: Select all
Dec 09 12:21:22 localhost systemd-udevd[548]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:1d.4/0000:04:00.0': No such file or directory
Dec 09 12:21:22 localhost kernel: ACPI: AC Adapter [AC] (on-line)
Dec 09 12:21:22 localhost kernel: input: HP Wireless hotkeys as /devices/virtual/input/input5
Dec 09 12:21:22 localhost systemd[1]: Found device /dev/nvme0n1p1.
Dec 09 12:21:22 localhost systemd[1]: Mounting /boot/EFI...
Dec 09 12:21:22 localhost kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Dec 09 12:21:22 localhost kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 09 12:21:22 localhost kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Dec 09 12:21:22 localhost kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Dec 09 12:21:22 localhost kernel: r8169 0000:02:00.0 eth0: RTL8168h/8111h at 0xffffc1a800d91000, 00:68:eb:66:a4:ba, XID 14100800 IRQ 137
Dec 09 12:21:22 localhost kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Dec 09 12:21:22 localhost systemd[1]: Found device /dev/nvme0n1p3.
Dec 09 12:21:22 localhost systemd[1]: Mounting /media/windows...
Dec 09 12:21:22 localhost systemd[1]: Found device /dev/nvme0n1p6.
Dec 09 12:21:22 localhost systemd[1]: Activating swap /dev/nvme0n1p6...
Dec 09 12:21:22 localhost systemd[1]: Found device /dev/nvme0n1p7.
Dec 09 12:21:22 localhost systemd[1]: Starting File System Check on /dev/nvme0n1p7...
Dec 09 12:21:22 localhost kernel: Adding 4194300k swap on /dev/nvme0n1p6.  Priority:-2 extents:1 across:4194300k SSFS
Dec 09 12:21:22 localhost systemd[1]: Activated swap /dev/nvme0n1p6.
Dec 09 12:21:22 localhost systemd[1]: Reached target Swap.
Dec 09 12:21:22 localhost kernel: ACPI: Battery Slot [BAT0] (battery present)
Dec 09 12:21:22 localhost systemd-fsck[565]: /dev/nvme0n1p7: recovering journal
Dec 09 12:21:22 localhost systemd[1]: Mounting Temporary Directory...
Dec 09 12:21:22 localhost systemd[1]: Mounted Temporary Directory.
Dec 09 12:21:22 localhost kernel: uvcvideo: Found UVC 1.00 device HP Webcam (0408:5321)
Dec 09 12:21:22 localhost kernel: fuse init (API version 7.26)
Dec 09 12:21:22 localhost kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Dec 09 12:21:22 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 7 was not initialized!
Dec 09 12:21:22 localhost systemd-fsck[565]: /dev/nvme0n1p7: clean, 982/7004160 files, 659591/28007424 blocks
Dec 09 12:21:22 localhost kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Dec 09 12:21:22 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Processing 2 was not initialized!
Dec 09 12:21:22 localhost kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Dec 09 12:21:22 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized!
Dec 09 12:21:22 localhost kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Dec 09 12:21:22 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 4 was not initialized!
Dec 09 12:21:22 localhost kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Dec 09 12:21:22 localhost kernel: input: HP Webcam: HP Webcam as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input7
Dec 09 12:21:22 localhost kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Dec 09 12:21:22 localhost kernel: usbcore: registered new interface driver uvcvideo
Dec 09 12:21:22 localhost systemd[1]: Started File System Check on /dev/nvme0n1p7.
Dec 09 12:21:22 localhost kernel: USB Video Class driver (1.1.1)
Dec 09 12:21:22 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-nvme0n1p7 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 12:21:22 localhost systemd[1]: Mounting /var...
Dec 09 12:21:22 localhost kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: (null)
Dec 09 12:21:22 localhost systemd[1]: Mounted /var.
Dec 09 12:21:22 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 09 12:21:22 localhost systemd[1]: Starting Load/Save Random Seed...
Dec 09 12:21:22 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 12:21:22 localhost systemd[1]: Started Load/Save Random Seed.
Dec 09 12:21:22 localhost systemd-journald[474]: System journal (/var/log/journal/) is 48.0M, max 4.0G, 3.9G free.
Dec 09 12:21:22 localhost systemd-journald[474]: Time spent on flushing to /var is 11.435ms for 819 entries.


Boot -1 shows a couple of errors near the end, but continues with entries after them. The errors are:
Code: Select all
Dec 09 13:04:29 localhost systemd-udevd[530]: Process '/sbin/display_driver_helper --load pci:v00008086d00003EA0sv0000103Csd00008530bc03sc00i00' failed with exit code 1.

and
Code: Select all
Dec 09 13:04:29 localhost systemd-udevd[555]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:1d.4/0000:04:00.0': No such file or directory

and finally some messages about nvme. Since that is where the boot failed, I'll include that sequence to the end of the log (but nvme errors could simply be because of the hard hang and power off of the system rather than the cause of the hard hang this time):
Code: Select all
Dec 09 13:04:29 localhost kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 09 13:04:29 localhost systemd[1]: Reached target Swap.
Dec 09 13:04:29 localhost systemd-fsck[566]: /dev/nvme0n1p7: recovering journal
Dec 09 13:04:29 localhost systemd[1]: Mounting Temporary Directory...
Dec 09 13:04:29 localhost systemd-fsck[566]: /dev/nvme0n1p7: clean, 983/7004160 files, 661639/28007424 blocks
Dec 09 13:04:29 localhost systemd[1]: Mounted Temporary Directory.
Dec 09 13:04:29 localhost kernel: fuse init (API version 7.26)
Dec 09 13:04:29 localhost systemd[1]: Mounted /boot/EFI.
Dec 09 13:04:29 localhost systemd[1]: Started File System Check on /dev/nvme0n1p7.
Dec 09 13:04:29 localhost systemd[1]: Mounting /var...
Dec 09 13:04:29 localhost kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: (null)
Dec 09 13:04:29 localhost systemd[1]: Mounted /var.
Dec 09 13:04:29 localhost systemd[1]: Starting Load/Save Random Seed...
Dec 09 13:04:29 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 09 13:04:29 localhost systemd[1]: Started Load/Save Random Seed.
Dec 09 13:04:29 localhost kernel: ACPI: Battery Slot [BAT0] (battery present)
Dec 09 13:04:29 localhost systemd-journald[478]: System journal (/var/log/journal/) is 56.0M, max 4.0G, 3.9G free.
Dec 09 13:04:29 localhost systemd-journald[478]: Time spent on flushing to /var is 11.454ms for 791 entries.

And for comparison, final boot starting at nvme mount and continuing up to mounting my external usb to capture logs. This one is a little longer since it boots successfully:
Code: Select all
Dec 09 13:12:20 localhost kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 09 13:12:20 localhost systemd[1]: Mounting /media/windows...
Dec 09 13:12:20 localhost kernel: fuse init (API version 7.26)
Dec 09 13:12:20 localhost systemd[1]: Mounting /var...
Dec 09 13:12:20 localhost systemd[1]: Reached target Swap.
Dec 09 13:12:20 localhost systemd[1]: Mounting Temporary Directory...
Dec 09 13:12:20 localhost systemd[1]: Mounted Temporary Directory.
Dec 09 13:12:20 localhost kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: (null)
Dec 09 13:12:20 localhost systemd[1]: Mounted /boot/EFI.
Dec 09 13:12:20 localhost systemd[1]: Mounted /var.
Dec 09 13:12:20 localhost systemd[1]: Starting Load/Save Random Seed...
Dec 09 13:12:20 localhost kernel: uvcvideo: Found UVC 1.00 device HP Webcam (0408:5321)
Dec 09 13:12:20 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:20 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 09 13:12:20 localhost systemd[1]: Started Load/Save Random Seed.
Dec 09 13:12:20 localhost systemd-journald[497]: System journal (/var/log/journal/) is 64.0M, max 4.0G, 3.9G free.
Dec 09 13:12:20 localhost systemd-journald[497]: Time spent on flushing to /var is 10.453ms for 806 entries.
Dec 09 13:12:20 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 7 was not initialized!
Dec 09 13:12:20 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Processing 2 was not initialized!
Dec 09 13:12:20 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized!
Dec 09 13:12:20 localhost kernel: uvcvideo 1-6:1.0: Entity type for entity Extension 4 was not initialized!
Dec 09 13:12:20 localhost kernel: input: HP Webcam as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input7
Dec 09 13:12:20 localhost kernel: usbcore: registered new interface driver uvcvideo
Dec 09 13:12:20 localhost kernel: USB Video Class driver (1.1.1)
Dec 09 13:12:20 localhost kernel: r8169 0000:02:00.0 eno1: renamed from eth0
Dec 09 13:12:20 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:20 localhost systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Dec 09 13:12:20 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:20 localhost systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 09 13:12:20 localhost systemd[1]: Started Load/Save RF Kill Switch Status.
Dec 09 13:12:20 localhost systemd[1]: Starting Show Plymouth Boot Screen...
Dec 09 13:12:20 localhost systemd[1]: Mounting FUSE Control File System...
Dec 09 13:12:20 localhost kernel: intel_rapl: Found RAPL domain package
Dec 09 13:12:20 localhost kernel: intel_rapl: Found RAPL domain core
Dec 09 13:12:20 localhost kernel: intel_rapl: Found RAPL domain uncore
Dec 09 13:12:20 localhost kernel: intel_rapl: Found RAPL domain dram
Dec 09 13:12:20 localhost systemd[1]: Mounted FUSE Control File System.
Dec 09 13:12:20 localhost systemd[1]: Started Flush Journal to Persistent Storage.
Dec 09 13:12:20 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:20 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:20 localhost systemd[1]: Started Show Plymouth Boot Screen.
Dec 09 13:12:20 localhost mount[619]: Windows is hibernated, refused to mount.
Dec 09 13:12:20 localhost mount[619]: The disk contains an unclean file system (0, 0).
Dec 09 13:12:20 localhost mount[619]: Metadata kept in Windows cache, refused to mount.
Dec 09 13:12:20 localhost mount[619]: Falling back to read-only mount because the NTFS partition is in an
Dec 09 13:12:20 localhost mount[619]: unsafe state. Please resume and shutdown Windows fully (no hibernation
Dec 09 13:12:20 localhost mount[619]: or fast restarting.)
Dec 09 13:12:20 localhost ntfs-3g[679]: Version 2017.3.23 external FUSE 29
Dec 09 13:12:20 localhost ntfs-3g[679]: Mounted /dev/nvme0n1p3 (Read-Only, label "Windows", NTFS 3.1)
Dec 09 13:12:20 localhost ntfs-3g[679]: Cmdline options: rw,umask=000
Dec 09 13:12:20 localhost ntfs-3g[679]: Mount options: rw,allow_other,nonempty,relatime,ro,default_permissions,fsname=/dev/nvme0n1p3,blkdev,blksize=4096
Dec 09 13:12:20 localhost ntfs-3g[679]: Global ownership and permissions enforced, configuration type 1
Dec 09 13:12:20 localhost systemd[1]: Mounted /media/windows.
Dec 09 13:12:21 localhost kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5d4f01)
Dec 09 13:12:21 localhost kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x71, 0x1a, 0x0b.
Dec 09 13:12:21 localhost kernel: psmouse serio1: elantech: Elan sample query result 02, b7, 97
Dec 09 13:12:21 localhost kernel: input: HP WMI hotkeys as /devices/virtual/input/input8
Dec 09 13:12:21 localhost kernel: input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Started udev Wait for Complete Device Initialization.
Dec 09 13:12:21 localhost systemd[1]: Starting Wait for storage scan...
Dec 09 13:12:21 localhost systemd[1]: Started Wait for storage scan.
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fedora-wait-storage comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Starting Initialize storage subsystems (RAID, LVM, etc.)...
Dec 09 13:12:21 localhost kernel: device-mapper: uevent: version 1.0.3
Dec 09 13:12:21 localhost kernel: device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
Dec 09 13:12:21 localhost fedora-storage-init[691]: Setting up Logical Volume Management: [  OK  ]
Dec 09 13:12:21 localhost systemd[1]: Started Initialize storage subsystems (RAID, LVM, etc.).
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fedora-storage-init comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Starting Initialize storage subsystems (RAID, LVM, etc.)...
Dec 09 13:12:21 localhost fedora-storage-init[714]: Setting up Logical Volume Management: [  OK  ]
Dec 09 13:12:21 localhost systemd[1]: Started Initialize storage subsystems (RAID, LVM, etc.).
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fedora-storage-init-late comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Reached target Local File Systems.
Dec 09 13:12:21 localhost systemd[1]: Starting Create Volatile Files and Directories...
Dec 09 13:12:21 localhost systemd[1]: Starting Restore /run/initramfs on shutdown...
Dec 09 13:12:21 localhost systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Dec 09 13:12:21 localhost systemd[1]: Started Restore /run/initramfs on shutdown.
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Started Create Volatile Files and Directories.
Dec 09 13:12:21 localhost systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Dec 09 13:12:21 localhost audit[735]: SYSTEM_BOOT pid=735 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Started Update UTMP about System Boot/Shutdown.
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rescue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Reached target System Initialization.
Dec 09 13:12:21 localhost systemd[1]: Started Rescue Shell.
Dec 09 13:12:21 localhost audit[739]: SYSTEM_RUNLEVEL pid=739 uid=0 auid=4294967295 ses=4294967295 msg='old-level=N new-level=1 comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Reached target Rescue Mode.
Dec 09 13:12:21 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes...
Dec 09 13:12:21 localhost systemd[1]: Listening on D-Bus System Message Bus Socket.
Dec 09 13:12:21 localhost systemd[1]: Starting Bluetooth service...
Dec 09 13:12:21 localhost systemd[1]: Started Update UTMP about System Runlevel Changes.
Dec 09 13:12:21 localhost bluetoothd[740]: Bluetooth daemon 5.45
Dec 09 13:12:21 localhost systemd[1]: Started D-Bus System Message Bus.
Dec 09 13:12:21 localhost kernel: random: crng init done
Dec 09 13:12:21 localhost systemd[1]: Started Bluetooth service.
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost bluetoothd[740]: Starting SDP server
Dec 09 13:12:21 localhost systemd[1]: Reached target Bluetooth.
Dec 09 13:12:21 localhost systemd[1]: Startup finished in 2.751s (kernel) + 1.778s (userspace) = 2min 11.896s.
Dec 09 13:12:21 localhost kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec 09 13:12:21 localhost kernel: Bluetooth: BNEP filters: protocol multicast
Dec 09 13:12:21 localhost kernel: Bluetooth: BNEP socket layer initialized
Dec 09 13:12:21 localhost dbus[742]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Dec 09 13:12:21 localhost bluetoothd[740]: Bluetooth management interface 1.14 initialized
Dec 09 13:12:21 localhost systemd[1]: Starting Hostname Service...
Dec 09 13:12:21 localhost systemd[1]: Received SIGRTMIN+21 from PID 304 (plymouthd).
Dec 09 13:12:21 localhost dbus[742]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec 09 13:12:21 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:21 localhost systemd[1]: Started Hostname Service.
Dec 09 13:12:23 localhost kernel: snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
Dec 09 13:12:24 localhost kernel: snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x000f0000
Dec 09 13:12:25 localhost kernel: snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
Dec 09 13:12:25 localhost kernel: snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec
Dec 09 13:12:25 localhost kernel: snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec
Dec 09 13:12:25 localhost systemd[1]: Reached target Sound Card.
Dec 09 13:12:25 localhost kernel: input: HDA Intel HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
Dec 09 13:12:25 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:25 localhost kernel: audit_printk_skb: 84 callbacks suppressed
Dec 09 13:12:25 localhost kernel: audit: type=1131 audit(1575925945.628:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:51 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 13:12:51 localhost kernel: audit: type=1131 audit(1575925971.895:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'


Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 10th, '19, 01:09

I'm changing the subject since it noticed it is not accurate. I was not upgrading from Mageia 6 to Mageia 7, but simply installing updates for installed packages in Mageia 6. But the intent is to get to a current version (e.g. Mageia 7) at some point.
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 7 Fails to boot after updating from Mageia 6

Postby sln123 » Dec 10th, '19, 06:35

doktor5000 wrote:I'd suggest to try to install on something that's not attached via NVMe, if that's a possibility. Even if only for temporary testing.


Hi doktor500 and thanks for the response.

I know nothing about NVMe. My system is a new laptop with a single 256GB SSD, pre-installed with Windows 10 S. I hate S-Mode and Windows 10 for that matter, so my plan was to simply install Linux. I have repartitioned the SSD so Windows only has about 80G and the rest was setup for Mageia including I think 11GB for swap following Ubuntu recommendations for hibernation.

Given that there is only a single SSD drive, is it possible to turn off NVMe?

I'll try your suggested commands and post results in a second response.

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 10th, '19, 07:48

doktor5000 wrote:And if you get to recovery mode, then it should also be possible to switch to multi-user mode (init 3 or systemctl isolate multi-user.target) to get the network up, then try urpmi --auto-update to check if the upgrade has completed.

Also what about booting any of the live DVD media, do they boot and work properly ?


  • init 3 successfully gets me to login prompt.
  • urpmi --auto-update reports "Packages are up to date"

Booting from a Mageia 7.1 Plasma Live DVD fails with last message:
Code: Select all
A start job is running for udev Wait for Complete Device Initialization (27s / 2min 30s)

Using grub to change splash quiet to 3 has basically same result, just 3s faster.

I have not tried other desktops - I have tried other distros (with other desktops) and all behave similarly, so I suspect it is not strictly/only the graphics adapter.

Phil

PS. I just looked up my ssd info on Windows and device manager reports it as a WDC PC SN520 SDAPNUW-256G-1006.
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 11th, '19, 02:14

I successfully booted the updated Mageia 6 by editing grub with the fix in https://community.wd.com/t/linux-suppor ... 018/225446

Specifically in the post by chrisyuan for ubuntu 18.04:
And I found solution how to fix it.

In the GRUB boot menu, press e to edit startup parameter
Add nvme_core.default_ps_max_latency_us=5500 by the end of quiet splash

This fix worked for me in Debian/Ubuntu/Mint, so I decided to try it in my updated Mageia too and IT WORKED!

I booted to login screen and full graphics with this boot option.

Using the same boot option for Mageia 7.1 Plasma live successfully boots to Plasma desktop.

After this much effort, I plan to do more experiments to see what distro and desktop best supports my hardware before committing, but Mageia is now working, so I'll mark this thread as solved.

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby doktor5000 » Dec 11th, '19, 20:20

Could you please post the output of
Code: Select all
lspcidrake -v
? As the workaround seems to be working, I'd add an entry to our Errata afterwards as this might affect other laptops / NVMe controllers as well.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 11th, '19, 23:34

Hi doktor5000,

The arch wiki page at: https://wiki.archlinux.org/index.php/Ta ... drive/NVMe gives a better explanation for what this setting is doing and why 5500 vs 0, etc.

I'm trying another distro at the moment, but using Mageia 7.1 live running on that system, here is the output from lspcidrake -v:
Code: Select all
i2c_i801        : Intel Corporation|Cannon Point-LP SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:9da3 subv:103c subd:8530) (rev: 30)
xhci_pci        : Intel Corporation|Cannon Point-LP USB 3.1 xHCI Controller [SERIAL_USB] (vendor:8086 device:9ded subv:103c subd:8530) (rev: 30)
Card:Intel 810 and later: Intel Corporation|UHD Graphics 620 (Whiskey Lake) [DISPLAY_VGA] (vendor:8086 device:3ea0 subv:103c subd:8530) (rev: 02)
unknown         : Sandisk Corp|WD Black 2018/PC SN520 NVMe SSD (vendor:15b7 device:5003) (rev: 01)
unknown         : Intel Corporation|Cannon Point-LP Shared SRAM [MEMORY_RAM] (vendor:8086 device:9def subv:103c subd:8530) (rev: 30)
unknown         : Intel Corporation|Cannon Point-LP PCI Express Root Port #9 [BRIDGE_PCI] (vendor:8086 device:9db0) (rev: f0)
intel_lpss_pci  : Intel Corporation|Cannon Point-LP Serial IO I2C Controller #0 (vendor:8086 device:9de8 subv:103c subd:8530) (rev: 30)
unknown         : Intel Corporation|Cannon Point-LP PCI Express Root Port #13 [BRIDGE_PCI] (vendor:8086 device:9db4) (rev: f0)
intel_pch_thermal: Intel Corporation|Cannon Point-LP Thermal Controller [SIGNAL_OTHER] (vendor:8086 device:9df9 subv:103c subd:8530) (rev: 30)
unknown         : Intel Corporation|Device 3e34 [BRIDGE_HOST] (vendor:8086 device:3e34 subv:103c subd:8530) (rev: 0c)
snd_hda_intel   : Intel Corporation|Cannon Point-LP High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:9dc8 subv:103c subd:8530) (rev: 30)
unknown         : Intel Corporation|Cannon Point-LP SPI Controller (vendor:8086 device:9da4 subv:103c subd:8530) (rev: 30)
mei_me          : Intel Corporation|Cannon Point-LP MEI Controller #1 [COMMUNICATION_OTHER] (vendor:8086 device:9de0 subv:103c subd:8530) (rev: 30)
processor_thermal_device: Intel Corporation|Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [SIGNAL_OTHER] (vendor:8086 device:1903 subv:103c subd:8530) (rev: 0c)
unknown         : Intel Corporation|Device 9db1 [BRIDGE_PCI] (vendor:8086 device:9db1) (rev: f0)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:103c subd:8530) (rev: 15)
unknown         : Intel Corporation|Cannon Point-LP LPC Controller [BRIDGE_ISA] (vendor:8086 device:9d84 subv:103c subd:8530) (rev: 30)
intel_lpss_pci  : Intel Corporation|Cannon Point-LP Serial IO I2C Controller #1 (vendor:8086 device:9de9 subv:103c subd:8530) (rev: 30)
unknown         : Intel Corporation|Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [SYSTEM_OTHER] (vendor:8086 device:1911 subv:103c subd:8530)
unknown         : Intel Corporation|Cannon Point-LP PCI Express Root Port #5 [BRIDGE_PCI] (vendor:8086 device:9dbc) (rev: f0)
unknown         : Intel Corporation|82801 Mobile SATA Controller [RAID mode] [STORAGE_RAID] (vendor:8086 device:282a subv:103c subd:8530) (rev: 30)
8723de          : Realtek Semiconductor Co., Ltd.|RTL8723DE 802.11b/g/n PCIe Adapter [NETWORK_OTHER] (vendor:10ec device:d723 subv:103c subd:8319)
hub             : Linux 5.1.14-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
usb_storage     : USB|Disk 2.0 [Mass Storage|SCSI|Bulk-Only] (vendor:ffff device:5678)
usbhid          : B16_b_02|USB-PS/2 Optical Mouse [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c024)
uvcvideo        : Quanta|HP Webcam [Video|Video Control] (vendor:0408 device:5321)
btusb           : Realtek|802.11n WLAN Adapter [Wireless|Radio Frequency|Bluetooth] (vendor:0bda device:b009)
hub             : Linux 5.1.14-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003)
hid_generic     : B16_b_02 USB-PS/2 Optical Mouse


Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby jiml8 » Dec 14th, '19, 19:05

doktor5000 wrote:Could you please post the output of
Code: Select all
lspcidrake -v
? As the workaround seems to be working, I'd add an entry to our Errata afterwards as this might affect other laptops / NVMe controllers as well.

Likely.

Looks like the kernel is not waiting long enough for the controller to respond while enumerating devices.
jiml8
 
Posts: 1186
Joined: Jul 7th, '13, 18:09

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby doktor5000 » Dec 15th, '19, 09:21

FWIW, this is what I added to Errata: https://wiki.mageia.org/en/Mageia_7_Err ... il_to_boot
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 16th, '19, 21:36

Great!

But note that "After installing all Mageia 7 updates" is not accurate. It prevents even booting the Mageia 7.1 Live USB/DVD and from installing. Mageia 6 was the only distro I found that booted fully and it failed after installing updates - I couldn't get Mageia 7 to ever boot without this workaround. In fact, all distros I tried failed to fully boot or install without this workaround.

So positioning in terms of installing updates might cause people to think this is not what they are seeing.

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby doktor5000 » Dec 17th, '19, 09:29

I've adjusted it. It wasn't really clear from your initial description.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: SOLVED: Mageia 6 Fails to boot after installing updates

Postby sln123 » Dec 17th, '19, 21:59

doktor5000 wrote:I've adjusted it. It wasn't really clear from your initial description.


Looks great now. Thanks.

Yes, for my initial post, I had no idea what was going on, so the real problem was not discovered and described until later making the thread a little hard to wade through.

Phil
sln123
 
Posts: 24
Joined: Nov 13th, '19, 02:18


Return to Video

Who is online

Users browsing this forum: No registered users and 1 guest