Mageia 2 - x86_64 boot-up problem

[pinnerite]

I recently installed the 64-bit version of Mageia 2 on a second machine. Like
the first this has an AMD microprocessor but only 2 cores and it also has ATI
graphics.

As before, I had to get into run level 3 from where I could install the ATI
proprietory drivers in order to prevent the system hanging on boot-up.

However on this machine that was not enough. It hangs after issuing a line
stating that it was 'Starting Wait for Plymouth Boot Screen to Quit'.

I can however get in by booting into safe mode, executing ^D, logging in at the
text prompt and then executing startx.

Just as I was generally customising the desktop, the hard drive failed. I had an
identical spare drive for this machine and made a second surgically clean
install. The results were identical to the first attempt.

Is this a known condition? Is there a fix.

[sglafata]

In my case, once I was up in Safe Mode, I would make sure networking was started, and issue a "urpmi --auto-update -v". Once I knew the computer was updated, then I would follow the Release Notes https://wiki.mageia.org/en/Mageia_2_Release_Notes#Upgrading_online.2C_using_urpmi_.28CLI.29 to upgrade via the CLI. It takes a while, and you may still not boot into the graphical interface, but all your packages should be upgraded to the default repositories. You can then issue the kernel command found in the Errata https://wiki.mageia.org/en/Mageia_2_Errata#Proprietary_graphics_card_drivers to get into the GUI. Then I had to enable the non-free repository to upgrade the ATI drivers. Enable any repositories you need in addition to the default, and upgrade again. You should be golden after that.

[pinnerite]

Following the replacement of the 'duff' drive. I reinstalled Mageia 2 x86_64 from the DVD as before but it still hangs at
'Starting Wait for Plymouth Boot Screen to Quit'.

Even so I went through a ll the steps that you pointed to in your reply. There was not a single change.
What on earth can be causing this problem, seemingly only on my machine?

I previously had several variants of Mandriva on this machine ending with Mandriva 2010.2.
I never had a problem with booting up.

[gohlip]

At grub menu, edit the kernel line and remove 'splash' and 'quiet' (make sure 'nokmsboot' is there) and boot up.
If it can boot up, then you need to 'reestablish' the plymouth screen. (edit: most probably just the screen resolution)

And while you're at it, please let us know the readings of vga=xxx is.

[pinnerite]

The kernel line in grub.lst did not contain 'splash'; 'quiet' or 'nokmsboot'. I inserted the last after 'nolapic'.
The system still stalls after See 'systemctl status plymouth-quit-wait-service' for details.

vga=788 by the way.

It may be irrelevant but I see 'fglrx (8,961-1.mga2 nonfrree): Already installed on this kernel
during the boot up sequence.

One welcome change though. I can now reboot from the command line (but not execute a 'halt' that actually turns off the power)!

[gohlip]

Good thing you can boot up.
"'fglrx (8,961-1.mga2 nonfrree): Already installed on this kernel" is ATI proprietary driver.
Whether it's the right one....

After booting, at Mageia control center, detect hardware to check ATI card, then go to "set up graphical server", redo setup
Finally go to boot and set up boot system. at advanced, check if acpi and apic is checked for you (let the default handle it)
All the above is at Mageia Control Center.
summary....
o hardware detect
o graphical server
o boot

You may have to reboot.
Let us know how it turns out. preferably advise any kernel line change at grub menu.lst
(particularly if 'nokmsboot' is there)

Good luck.
notes:
o Mageia uses grub legacy, so it should be menu.lst, not grub.lst
Are you booting with other OS bootloader? If yes, careful here, boot up using Mageia bootloader first to verify boot is okay (you can chainload from grub2).
Booting Mageia directly with grub2 needs modifications. Let us know, will advise.

o As for 'nolapic' or 'noacpi', that depends on your processor; for most, it is not necessary, but I am not sure in your case.
see
http://en.wikipedia.org/wiki/Advanced_C ... _Interface
http://osdev.berlios.de/pic.html

[doktor5000]

o As for 'nolapic' or 'noacpi', that depends on your processor; for most, it is not necessary, but I am not sure in your case.

Minor nit, it does not depend on the processor, more the mainboard and the ACPI/APIC implementation

[pinnerite]

Taking each suggestion in turn:

Resetting the ATi card was tortuous.
The card on this machine is a Radeon HD3450.

I first tried to change the driver to 'Radeon HD2000 or later without free driver (vesa/fglrx').
When I selected 'test' there were no vertical coloured bars that I used to see but I did see
the dialog 'Is this OK?' (more or less). Selecting 'Yes' resulted in the screen going black, the
keyboard lamps extinguishing and the computer being unable to react to any key sequence.

Trying again but accepting the original (proprietary) setting, resulted in a purple screen.
(Purple screen of death? Uhg!)

Next
I rebooted, accessing via safe mode.
I set both nolapic and noapic in menu.lst (not grub.lst as I mistakenly wrote a few days ago).
I made sure that nokmsboot was present too. However this somehow disappeared after the
the next reboot (?)

In the mcc->boot-setup->advanced, all are unchecked except 'enable smp'

Result? Hanging at 'Checking for new hardware'.
Now even 'Safe Mode' crashes at the ^D although I can get in at runlevel 3.

Sorry to be causing head-scratching but grateful for your help.

[gohlip]

If hardware detected is Radeon HD3450, then use it for the graphical server. If screen black, still click 'ok' (its important to use what the OS detect, otherwise driver may not work). Then remember to go to set up boot AFTER that.

notes:
o modifying menu.lst manually at grub boot will not change it, permanent changes is through the Mageia Control Center.
o Please check again if 'enable smp' is still there (it shouldn't and we should see 'nokmsboot' at grub kernel line). Mageia somehow enables the video driver through the kernel.

Good luck again, or better luck this time?

[pinnerite]

OK I re-entered setting up the graphical server and OK'd the default selection and then the offer of the ATi proprietary driver.
I then went to 'Set up boot system', then Advanced. Only smp was checked.
I returned to 'Set up boot system' then next. Selected the top line 'linux' and selected 'Modify'.
The revealed line read 'nolapic noapic resume==UUID=25e.......... acpi=ht
No sign of nokmsboot.

After getting back to the desktop, opened a terminal and executed reboot.
As before, the system hangs after the Plymouth' line.

All this yet if I boot via setting the grub line to runlevel 3, logging in at the prompt and then executing startx seems to circumvent whatever is causing the hitch when I boot into runlevel 5. It'd beyond me.

[gohlip]

I returned to 'Set up boot system' then next. Selected the top line 'linux' and selected 'Modify'.
The revealed line read 'nolapic noapic resume==UUID=25e.......... acpi=ht
No sign of nokmsboot.

Finally go to boot and set up boot system. at advanced, check if acpi and apic is checked for you (let the default handle it)

Let the default handle it. Do it without modifications at all.

[pinnerite]

That is exactly what I did.

[gohlip]

Alright then, but sorry, but I have no more ideas.
Can somebody here especially with Radeon HD3450 help out pinnerite here?

Good luck and wish you all the best.

[gohlip]

Pinnerite, maybe you need to install directly from ATI the drivers. The following is where you can get it.
http://driverscollection.com/?H=Radeon% ... x%20x86_64
But since I don't use ATI (mine is nvidia), it is also best that someone else here help you with it.

Good luck.

[tom_]

mageia already has a bug opened on a problem like yours:

https://bugs.mageia.org/show_bug.cgi?id=6719

and there is also some similar bug recently fixed on systemd

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=761656

but I can't help you on this matter

however you can try to see if the discussion on the fedora bug helps you...

[pinnerite]

Just to add to the picture. I have just installed gdm and successfully booted into run level 5.

[gohlip]

Just to add to the picture. I have just installed gdm and successfully booted into run level 5.

That is very strange, indeed. If, and it is entirely up to you, you can uninstall completely (purge all) and then reinstall kdm, it would be good if you boot up to kdm, it will still give problems. I don't think so; and of course, if there are problems in kdm, you still have gdm to boot to.

Anybody has any comment on this?

ps: I haven't used gdm for years.

[pinnerite]

Before I commit myself, can you clarify what you mean by 'all'?

[gohlip]

Before I commit myself, can you clarify what you mean by 'all'?

and dependencies that gdm or other apps do not need.

Like....
Default-kde-config, akonadi, kdebase, kdegames, konsole, oxygen-gtk, plasma..and usually all those starting with k

[pinnerite]

I should have paid more attention to Aesop's fables.
I did as requested but the system hung on the reboot.
Even going in via runlevel 3 now doesn't get me far because at the prompt, 'startx' is now not recognised.
DISPLAYMANAGER still points to gdm

OK I've got it back. I'll stick with gdm until ......

Thanks again,

Alan

[pinnerite]

I've hit a few snags, probably related:
1) No desktop icons display.
2) Right-clicking on the desktop to get into folder view settings displays only two menu options: View and Mouse Actions.
3) Konqueror no longer lists files but seems to display modern art.

[gohlip]

I should have paid more attention to Aesop's fables.

Still one of my favourite stories too...but I did say...

...and it is entirely up to you...

I did as requested but the system hung on the reboot.
Even going in via runlevel 3 now doesn't get me far because at the prompt, 'startx' is now not recognised.
DISPLAYMANAGER still points to gdm
OK I've got it back. I'll stick with gdm until ......
Thanks again,
Alan

Okay, Alan, understand completely; but what I am saying is that video driver issues go deeper than just the GUI level (kdm,gdm, etc..) and so GUI has no bearing.
Anyway, there are much more stories in Aesop than just the man, boy and the donkey.
Have you heard about the crow and the jar of water....

Alan, whatever you do, we're all here to help. Again, wish you the best.

[gohlip]

I did as requested but the system hung on the reboot.
Alan

Did you remove .kde also?
It is a hidden file at your /home.
Repeat: You should remove it also before starting kdm.

[pinnerite]

I didn't remove .kde because I created a dummy user and tried it from there with the same result. I'll do a clean install in a day or two. Thanks for all the support. It is never really wasted.

Regards

Alan

[parlamentaru]

Hello ppl, i have the same problem like pinnerite, i have amd radeon hd 6850 grafical card and my mageia 2 kde want start.
I don't know why all this problems with amd cards.