Bug 26045 - kernel panic after updating new M7 installations
Summary: kernel panic after updating new M7 installations
Status: RESOLVED DUPLICATE of bug 26996
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-09 19:48 CET by Otto Rothbauer
Modified: 2020-08-26 13:50 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Otto Rothbauer 2020-01-09 19:48:52 CET
I tried to install mageia 7 on a 32 bit system. The installation was canceled. No packages could be installed.
Something like that is useless.
Comment 1 Lewis Smith 2020-01-09 22:14:03 CET
Your complaint is not helpful. We of course test Mageia ISOs on 32-bit systems.
Please say what you are doing:
* A brief description of the system
* What ISO you are trying to install from [Classic-32 or XfceLive-32]
* Did you checksum it before making the installation medium?
* How did you make the installation medium?
* Installing from USB or DVD?
* Did the installation medium boot to a menu? What entry did you choose? How far did it get?

Keywords: (none) => NEEDINFO
CC: (none) => lewyssmith

Comment 2 Otto Rothbauer 2020-02-05 18:37:58 CET
My system is as follows:
Processor: Pentium ® M 1.86 GHz
RAM: 1020632 KiB
Graphics: 1024 x 768 (Unknown)
The X. org. Foundation
Disc: DVD player

I did the upgrade. That worked until an update came. Then the ad came Kernelpanic.
Then I installed from the DVD. Everything went well. After the restart, Kernelpanic came.
I installed the plasma.
I have now also tested Xfce-Live. It was very slow and ultimately got stuck.
I installed without updates.
The kernel did not panic during the installation.
I had no problems with version 6.
I also have 64-bit systems that also have problems.
After a long break, the system hangs and can only be accessed with Ctrl, Alt and Delete. Be opened again.
Graphics problems also occur. With a computer, the desktop flickers constantly when logging on.
I think version 7 is not mature.
Comment 3 Lewis Smith 2020-02-05 21:27:28 CET
There are too many things here. It might be better to discuss them on a forum (there is a German one https://forums.mageia.org/de/). The sort of thing that looks necessary is just one ordered sequence:
* Your system description, but knowing the graphics hardware is important. Does the BIOS not tell you? Or when Mageia *is* working initially, from a terminal:
 $ lspci -v
and select just the section starting "VGA compatible controller", which also shows the graphics driver being used.
* What ISO you installed (if the Classic, what desktop).
* Confirm the installation worked, and (or not) the first re-boot.
* Confirm that you updated the newly installed & re-booted system.
* Confirm that the kernel panic happens on the subsequent re-boot.
If you are able to photograph the kernel panic screen, do; and attach the image.

One thing that recurs is that you seem to be able to *install* Mageia OK, and get the kernel panic only after updating the system. The trouble is, now there will be a large number of updates to apply to a newly installed system.

We recommend one of the 'lightweight' desktops for 32-bit or limited hardware (e.g. like yours, memory): LXDE, Mate, or Xfce. Plasma is not a good idea in these circumstances.
RAM: I recently installed Mageia 7 on an old 64-bit Pentium4 computer with just 1Gb of memory, and it (especially browsers) was/were very slow. Upgrading the memory to 2Gb improved things usefully..

> I think version 7 is not mature
It went through a very long testing period. And some people praise it in relation to other distributions; so it is better than you think. There will always be odd systems on which different distributions work or do not. I would hope that you can, with help, win in the end.

Keywords: NEEDINFO => (none)
Summary: installation mageia 7 => kernel panic after updating new M7 installations

Comment 4 Aurelien Oudelet 2020-08-26 13:50:05 CEST
Thanks for the bug report.
This particular issue has already been investigated in 26996, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 26996 ***

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


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