Bug 6058

Hi,

now I've found somehow the solution. I just hope, my computer won't explode. :)

I've found the solution during attempts with installer, I've put the DVD again into the drive and then tested different options, always one in time, for the settings of graphics, and then let it be tested:
a) 740-based cards: failed to load module; i740 (module does not exist, 0); no devices detected
b) Intel Poulsbo US15W (GMA500):
PBDEV(0): FB atd. succeeded but modified
FBDEV(0): mode initialization failed
c)Intel 810 and later: No devices detected
d) somehow I experienced success (of some kind) (but during this test it doesn't look to me like big success - but it was the last chance after all to gain something - the success is now in fact, the machine is running - the graphics part) - the last option: Vermilion based cards

But!, when I looked at the hardware configuration in MCC, also Mageia "thinks",that: Graphical card is: Mobile 4 Series Chipset Integrated Graphics Controller -> Modul: Card: Intel 810 and later: it is probably right, but with autodetection and usage of whatever the Installer can use, the result led always to almost black screen. Now I shoul think about the resolution of the screen, the text is readable, but seemes (maybe) little different to me - 15,5": what the best resolution could be for it?!

Greetings, Pavel Fric

maybe this can help you:
http://ubuntuforums.org/showthread.php?t=1744809

Source RPM: (none) => drakx-kbd-mouse-x11

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #3)
> Hi,
> 
> This bug was filed against cauldron, but we do not have cauldron at the moment.
> 
> Please report whether this bug is still valid for Mageia 2.
> 
> Thanks :)
> 
> Cheers,
> marja

Hi,

thanks for tip - now I can't see my answer, that I sent as reply to "bugzilla" announcement in my sent messages. Also I would like to makelittle shorter summary:

1) the "manual" worked for eMachines, even if always at the start it seemes, that the little hesitation is present before the log in dialog appears clear (shortly there is "black screen" experience, than it switches to normal:

Because of "Vermillon based cards" setting during installation I had graphical mode (although with bad resolution), so I edited the file easily:

/etc/rc.local

I've inserted and saved the code:

Code:
---------------------------
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

setpci -s 00:02.0 F4.B=00

exit 0
---------------------------

To make sure no hibernation problem occures I've used the comment added there:

"Re: Black Screen after Upgrade 10.10 to 11.04 Acer eMachines
I own an emachines e527. Dealing with the hibernation was a hassle. This is the only computer I've had trouble running ubuntu on. I'm surprised this isn't fixed already.

As suggested above, I added the screen brightness command to /etc/rc.local. Adding the following command corrected the brightness setting at boot time."

Code:
---------------------------------
sudo nano /etc/rc.local
---------------------------------
The command is added before exit0 like so:
Code:

I didn't used first row in the dump of the commandline of that user, simply as describede on the other page of that page, I've inserted it into the file /etc/rc.local, and I don't now, what the command cat makes --> 
-----------------------------------------
"x@blacktop:/etc$ cat /etc/rc.local"
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

setpci -s 00:02.0 F4.B=00

exit 0
---------------------------------------------
in comment to the bug there on Ubuntu pages was something like following too: "I then noticed that when the computer hibernates the screen was staying black and not waking up again." So I did the following. I used the commands and text, (hopefully) as I think under superuser (root - su):
---------------------------------------------
touch /etc/pm/sleep.d/screen.brightness
chmod +x /etc/pm/sleep.d/screen.brightness
nano /etc/pm/sleep.d/screen.brightness
-------------------------------------------------
 And entered:
---------------------------------------------
#!/bin/bash
case "$1" in
    thaw|resume)
        /usr/bin/setpci -s 00:02.0 F4.B=00>/dev/null
        ;;
    *)
        ;;
esac
exit $?
---------------------------------------------

But later when I came back after some time, I found PC probably suspended/hibernated/fell asleep and that's why I think, when I didn't manage to wake it up - when black screen was still there after some attempts to hit some key, clicking with the mousebutton, I probably didn't manage to solve the problem (if any).

Further testing will be executed next week, Monday. Possibilities 1) wait until the PC sleeps/hibernates, or) repeat the command sequence for preventing it as was suggested (under superuser of cource).

Otherwise I shell look for disabling of hibernation/suspend in options.

Greetings, Pavel Fric

Fine report.
But regret to have to say pre-5 installers will not be changed.

@anyone:
If still applicable please set 'whiteboard' field to '5beta1' (or higher) and delete the 'Needinfo", provide any new detail, or if not applicable nowadays please close (with status --> resolved as 'OLD'.

thanks

Keywords: (none) => NEEDINFO

(In reply to Dick Gevers from comment #5)
> Fine report.
> But regret to have to say pre-5 installers will not be changed.
> 
> @anyone:
> If still applicable please set 'whiteboard' field to '5beta1' (or higher)
> and delete the 'Needinfo", provide any new detail, or if not applicable
> nowadays please close (with status --> resolved as 'OLD'.
> 
> thanks

Almost a year later, no reply, so closing as OLD

@ anyone who sees this issue is still valid in a currently maintained version of Mageia, please reopen this report and follow Dick's instructions

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