[Mageia-dev] M3 beta - where to report problems?

Anne Wilson annew at kde.org
Thu Apr 4 16:59:16 CEST 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/04/13 17:50, Anne Wilson wrote:
> 
> This is an Acer Aspire One 533, with Intel N550 chipset, everything
>  on-board.  I wasn't doing anything unusual, so there does seem to
> be a real problem.  Tomorrow I'll try to get a console login - is
> there a boot log that I could rename to keep it so that you can see
> what went wrong?  Maybe some other logs too?  I don't want to
> jeopardise the chances of finding the cause of this.
> 
Not much progress.  My usual method of editing the kernel line to get
a level 3 boot doesn't work - same blank (but lit) screen.  Failsafe
appears to be doing better - at least I can see messages.  It reaches

Reached target Multi-User
Reached target Graphical Interface

and there it sticks.  Does that give any clue as to what is failing,
and what I need to do to rescue the system?

Anne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFdlToACgkQj93fyh4cnBdB+gCfdXhYmJtw/Eo5l79EDlS3yose
jUcAnjxI4SnlAsUYqKP+k053NkQVkM4e
=c5Ia
-----END PGP SIGNATURE-----


More information about the Mageia-dev mailing list