Bug 32370 - After install, boots once, on second boot after login becomes unresponsive, no video then computer reboots spontaneously
Summary: After install, boots once, on second boot after login becomes unresponsive, n...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-11 00:37 CEST by jeff deifik
Modified: 2023-10-14 20:00 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description jeff deifik 2023-10-11 00:37:16 CEST
Description of problem:
I am doing a fresh install of mageia 9 64 bit, UEFI on a computer with an epyc milan, 128gb of ram, and a nvidia p400 graphics card.
The computer used to run mageia 8 without issue.

I configure mageia to not start graphics at boot.
I am using the open source graphics driver.
After install, I get the normal boot process, I log in, start graphics with startx, configure mirrors, and update all software.
Then I reboot.

When booting, there is absolutely no video output until I get a login prompt.
When I log in, the screen goes blank. After a few minutes, the computer reboots.
I can't get any access to the computer to examine logs or anything.

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


How reproducible:
Pretty reproducible. Before today, some times I wan unable to log in the first time, and sometimes there was no graphics output.
I have done fresh install at least 8 times.


Steps to Reproduce:
1. Do a fresh install
2. Boot mageia
3. Reboot, and computer becomes unusable
jeff deifik 2023-10-11 00:37:47 CEST

Summary: After install, boots once, on second boot after login becomes unresponsive, no video then computer reboots => After install, boots once, on second boot after login becomes unresponsive, no video then computer reboots spontaneously

Comment 1 jeff deifik 2023-10-11 00:39:57 CEST
The computer was running mageia 9 without incident until about a week ago.
I booted mageia, and updated it, which got a new version of glibc. Then it couldn't boot it again.

I was thinking the issue may have something to do with the mageia servers being down, but I tried today, and though I could boot the first time and update the system, I couldn't do anything after a second boot.
Comment 2 katnatek 2023-10-11 01:36:17 CEST
Try the tips on https://wiki.mageia.org/en/Mageia_9_Errata#Nvidia
Comment 3 jeff deifik 2023-10-13 23:08:09 CEST
I tried installing mageia 8. I was able to boot and update everything, but when I rebooted, I was unable to get to a login prompt.

I tried installing kubuntu 23.10. I never got to an interactive prompt; it just hung.

I tried installing mageia 9 using the framebuffer video driver. I was able to boot, and update everything. When I rebooted, I didn't get any booting video.

I can run live distros such as knoppix 9.1

My graphics card is a nvidia quadro P400, which is almost the same as a geforce 1030. It is of the Pascal generation.
Comment 4 katnatek 2023-10-13 23:33:47 CEST
Try after install disable mandriva-everytime in Mageia Control Center -> System -> Manage System services
Then update and reboot
The service autodetect hardware and maybe is changing your graphic configuration
Comment 5 jeff deifik 2023-10-14 00:02:59 CEST
I stopped mageia-everything.
I un-checked the box which I presume disabled it from starting at boot.

I rebooted. I was able to login, but as soon as I did, there were some video artifacts and I was unable to type anything.

I rebooted, and while booting there were some video artifacts and no boot progress.

I have another machine, which has the previous generation supermicro motherboard (H11SSL-i), the previous generation epyc rome processor, 128gb of ram and a nvidia quadro k420 video card. It is running mageia 9 without issue.

I am currently running windows 10 on the computer which is unable to run mageia 9, without issue.
Comment 6 jeff deifik 2023-10-14 18:25:22 CEST
I have successfully installed mageia 8 and it is fully updated, and works great.
It is likely that rather than doing a fresh install of mageia 9, I did an update to get mageia-9 on my system previously.

When I do a fresh install of mageia 9, I can boot it up once, but after that, I am unable to start mageia 9. No graphics of the bouncing ball, and when I press <esc> no kernel messages.

When I do a fresh install of kubuntu 23.10, the install is uneventful. When I boot, I can enter my username, but the system becomes unresponsive after that.

The only change I made to my system was to remove a usb 3.2 gen 2 card made by inateck, model KU 5211. It is possible it was not in my system when I originally installed mageia 8 successfully.

I suspect there may be some kernel issue that allows me to run mageia 8, but not mageia 9. I plan on running mageia 8 as long as it gets updates.
Comment 7 katnatek 2023-10-14 20:00:07 CEST
(In reply to jeff deifik from comment #6)
> I have successfully installed mageia 8 and it is fully updated, and works
> great.
> It is likely that rather than doing a fresh install of mageia 9, I did an
> update to get mageia-9 on my system previously.
> 
> When I do a fresh install of mageia 9, I can boot it up once, but after
> that, I am unable to start mageia 9. No graphics of the bouncing ball, and
> when I press <esc> no kernel messages.
> 
> When I do a fresh install of kubuntu 23.10, the install is uneventful. When
> I boot, I can enter my username, but the system becomes unresponsive after
> that.
> 
> The only change I made to my system was to remove a usb 3.2 gen 2 card made
> by inateck, model KU 5211. It is possible it was not in my system when I
> originally installed mageia 8 successfully.
> 
> I suspect there may be some kernel issue that allows me to run mageia 8, but
> not mageia 9. I plan on running mageia 8 as long as it gets updates.
If you decide to switch again to mageia 9, after the update in the boot menu select advanced options and boot with the old kernel

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