Please post the output of:
lspcidrake -v

Assignee: bugsquad => mageia
Source RPM: xorg-server => x11-driver-video-intel

(In reply to comment #1)
> Please post the output of:
> lspcidrake -v

________________________________

atl1c           : Atheros Communications|AR8132 Fast Ethernet [NETWORK_ETHERNET] (vendor:1969 device:1062 subv:1025 subd:0212) (rev: c0)
iwlagn          : Intel Corporation|WiFi Link 5100 [NETWORK_OTHER] (vendor:8086 device:4232 subv:8086 subd:1206)
i2c_i801        : Intel Corporation|82801I (ICH9 Family) SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:2930 subv:1025 subd:0212) (rev: 03)
ahci            : Intel Corporation|ICH9M/M-E SATA AHCI Controller [STORAGE_SATA] (vendor:8086 device:2929 subv:1025 subd:0212) (rev: 03)
iTCO_wdt        : Intel Corporation|ICH9M LPC Interface Controller [BRIDGE_ISA] (vendor:8086 device:2919 subv:1025 subd:0212) (rev: 03)
unknown         : Intel Corporation|82801 Mobile PCI Bridge [BRIDGE_PCI] (vendor:8086 device:2448) (rev: 93)
ehci_hcd        : Intel Corporation|82801I (ICH9 Family) USB2 EHCI Controller #1 [SERIAL_USB] (vendor:8086 device:293a subv:1025 subd:0212) (rev: 03)
uhci_hcd        : Intel Corporation|82801I (ICH9 Family) USB UHCI Controller #6 [SERIAL_USB] (vendor:8086 device:2939 subv:1025 subd:0212) (rev: 03)
uhci_hcd        : Intel Corporation|82801I (ICH9 Family) USB UHCI Controller #3 [SERIAL_USB] (vendor:8086 device:2936 subv:1025 subd:0212) (rev: 03)
uhci_hcd        : Intel Corporation|82801I (ICH9 Family) USB UHCI Controller #2 [SERIAL_USB] (vendor:8086 device:2935 subv:1025 subd:0212) (rev: 03)
uhci_hcd        : Intel Corporation|82801I (ICH9 Family) USB UHCI Controller #1 [SERIAL_USB] (vendor:8086 device:2934 subv:1025 subd:0212) (rev: 03)
shpchp          : Intel Corporation|82801I (ICH9 Family) PCI Express Port 3 [BRIDGE_PCI] (vendor:8086 device:2944) (rev: 03)
shpchp          : Intel Corporation|82801I (ICH9 Family) PCI Express Port 2 [BRIDGE_PCI] (vendor:8086 device:2942) (rev: 03)
shpchp          : Intel Corporation|82801I (ICH9 Family) PCI Express Port 1 [BRIDGE_PCI] (vendor:8086 device:2940) (rev: 03)
snd_hda_intel   : Intel Corporation|82801I (ICH9 Family) HD Audio Controller (vendor:8086 device:293e subv:1025 subd:0212) (rev: 03)
ehci_hcd        : Intel Corporation|82801I (ICH9 Family) USB2 EHCI Controller #2 [SERIAL_USB] (vendor:8086 device:293c subv:1025 subd:0212) (rev: 03)
uhci_hcd        : Intel Corporation|82801I (ICH9 Family) USB UHCI Controller #4 [SERIAL_USB] (vendor:8086 device:2937 subv:1025 subd:0212) (rev: 03)
unknown         : Intel Corporation|Mobile 4 Series Chipset Integrated Graphics Controller [DISPLAY_OTHER] (vendor:8086 device:2a43 subv:1025 subd:0212) (rev: 09)
Card:Intel 810 and later: Intel Corporation|Mobile 4 Series Chipset Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:2a42 subv:1025 subd:0212) (rev: 09)
unknown         : Intel Corporation|Mobile 4 Series Chipset Memory Controller Hub [BRIDGE_HOST] (vendor:8086 device:2a40 subv:1025 subd:0212) (rev: 09)
hub             : Linux 2.6.38.7-server-1.mga uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 2.6.38.7-server-1.mga uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 2.6.38.7-server-1.mga uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 2.6.38.7-server-1.mga uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
usbhid          : Logitech|USB Receiver [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:046d device:c52b)
hub             : Linux 2.6.38.7-server-1.mga uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
option          : ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ|HUAWEI Mobile (vendor:12d1 device:1001)
hub             : Linux 2.6.38.7-server-1.mga ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
uvcvideo        : Chicony Electronics Co., Ltd.|CNF7017 [Video|Video Control] (vendor:04f2 device:b044)
hub             : Linux 2.6.38.7-server-1.mga ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)

Well for the resolution I guess I managed to get it working fine and got ride of that ugly look of Mageia by importing windows font , applying some themes and so on.. 

The only remaining issue is the suitable X-server driver . Im running " vermilion based card " driver which doesn't support 3D effect and which isn't supposed to be the one I should be running because on the last Mandriva release I was having " Intel 810 and later " working just fine . please help :)

please do not misunderstand , I don't mean that Mageia's look is ugly, I meant by ugly that everything were to big and unsupportable :) at least on my box.

HI guys .. you told me to fill a bug .. I did and now there is no answers or solution !! are you guys fucking with us or what =? Jesus Christ!

I'm sorry but I've been rather busy with various work commitments. We do this as a hobby and when people comment with the kind of tone like above, it really does motivate us to try harder and not ignore you......</sarcasm>.

Honestly, what do you expect? I'm just some guy without the same hardware as you. What do you want me to do? Go out and buy the same hardware? Please lower your expectations and try and behave in a reasonable, responsible and respectful manner and the various volunteers will be more inclined to help you.

Sorry guys .. I just wanna get this Mageia 1 well working because I´ll have to stuck with it, since Mageia 2 will be integrating Gnome3 which isnot gonna work in my box ..excuse my tone and my impolite !

If possible can you boot up and then wait for things to fail.

Log in via the console and then get the file /var/log/Xorg.0.log (or possibly Xorg.0.log.old) and attach it hear. That will give some clues as to what is failing and if necessary we can then seek the help of people upstream with more intimate knowledge of the individual hardware involved here.

HI Mr.Colin 

hmm what I can do is boot up and attach that file . for the rest I have no Idea how to do it . is that fine ?

Yes absolutely. The first step is to get the log output and then we can take things further.

Just out of curiosity, is your system really frozen or you can get a login access
by pressing ctrl-alt-f2 or by ssh on it from another system?

CC: (none) => anaselli

Created attachment 624 [details]
Xorg.0.log.old

here is the file attached :)

Hi Angelo 

we are talking here about X-server's driver , my system is not frozen , I just cant get the driver working as its supposed to .

I'm not an expert to login in with a console mode and do all these crazy stuffs :)

well mine, was an interested question :) i have in a school four P4 machines that freeze often (talking about X) and they are mandriva 2010.1. I found that is a drm problem, but the problem has not been solved since mandriva 2010.1 was out.
That caused me problems in that school and we probably change SO migrating to ubuntu there :/
I've found threads in which they talked about some drm patches like in this one
https://bugs.archlinux.org/task/18356
but i was not able to investigate a lot...
Maybe Colin... ;)

Created attachment 625 [details]
Xorg.0.log.old but uncomressed for easier viewing.

Attachment 624 is obsolete: 0 => 1

OK, there are at least three things wrong here.....

 1. You are using the server kernel. You should be using the desktop kernel which is optimised for desktop use, including graphical logins. The server kernel is specifically tailored for systems that will typically not run a graphical display. Ensure you install kernel-desktop-latest and then uninstall kernel-server-latest.

 2. You are currently using the VESA driver, not the intel driver. There is no mention of the intel driver here. I suggest you rerun drakconf and configure the graphical display again to ensure the correct drivers are used.

 3. The error log seems to suggest that the error actually lies in the configuration of the synaptics touchpad driver and not the display at all.


I suspect you may have a rather messed up xorg.conf file. It's perhaps best to just rename this file and run drakconf to start with a clean slate.

OK Colin:

1, I installed Kernel-desktop-latest and removed the server one 

Question : why is the kernel-server-latest is installed by default in Mageia ? 

2. as you said . I changed the driver from VESA to Intel the fact which takes me back to the beginning ( freeze and background's lights are not coming up while booting " 

3.the synaptic touchpad is working just fine . I mean it may be causing the problem somehow . but I can't say .

 
for the file xorg.conf I cant say if it's messed up or not . as you know I just a normal user and looking for help here .

Angelo :

yes this problem started with me when I tried to install Mandriva 2010.2 . on the 2010.1 the Xserver were working just fine .. I'm gonna look at that topic from Archlinux . I'll maybe figure out something .. Thanks

Angelo , 

my system doesn't freeze while using the Intel driver , my system boots without background's lights with that driver, which means , DARKNESS . I can't see anything ;(

On Comment #17 
>Question : why is the kernel-server-latest is installed by default in Mageia ? 
IIRC it was installing RC1, at least that happened to me.

Anyway now I installed the Kernel-desktop-latest ! 

any thoughts about what may be causing that disaster with the low contrast ?

I mean the driver is surely gonna be working as its supposed to if background´s lights come up !

Not sure but, before freezing to avoid the black background i changed the KDE theme, and that worked. I can't remeber in which though...

OK, so it is the boot sequence that busted? Does a normal X11 session startup after that?

Or is it just the backlight on a built in laptop screen that is not working? i.e. you can see everything fine and everything work, but it's just far too dark?

If so then this is likely a very different problem to anything driver related. Thomas you may know more about this as the backlight controls just confuse me! It could be that an updated kernel is all that's needed to fix that, but thomas may know this from previous perusal of the kernel logs.

CC: (none) => tmb

yeah when I boot with the Intel driver , everything seems to be working fine, except that the backlight is not shining .. you understand at least the situation , its like you are in your room in the dark , you can see but you can´t recognize what you are seeing .. I can´t explain better than that ! sorry :)

Have you tried to use Fn + function keys to rise brightness? Or maybe try to suspend and resume, no effect?

Intel + no backlight seems to be common problem if you search google :/

CC: (none) => sander.lepik

yeah I tried using Fn + to rise brightness but no effect 

God help .. Im starting losing hope to get this resolved :(

(In reply to comment #25)
> God help .. Im starting losing hope to get this resolved :(

Dude, we only just started discussing it properly a day ago and there are still many, many, many things to look at here regarding the kernel code that is in here.

I'm guessing you've not even consulted the archives (or posted in) the intel-gfx mailing list where all the intel graphics guys hang out for example. That's likely going to be where I'll be looking/asking next after Thomas has given some input.

It's certainly a long, long way from giving up point! Have patience :D

No I have not consulted the archives because I don´t know where they are , I just posted my problem on the Mageia forum and I discussed it with Ahmed , after that he told me to fill a bug about it , and I did .. here I go with you guys I´m having patience and I am really glad for your ready- being to help !

Can you grab the output from "xrandr --prop" from your hard to read screen?

" xrandr --prop" if this is a command that I should type in a terminal and post its output here . its not working . it says " command not found " , 

if its something else . please tell me what it is :)

Please install the xrandr pacakge then retry.

(In reply to comment #30)
> Please install the xrandr pacakge then retry.

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       61.0* 
   800x600        61.0  
   640x480        60.0

Wow, is that all it tells you? Mine's much more details and has info about backlight too :s

Are you sure you passed the --props arguments?

Also I'm not sure why it's called "default" that's strange... Can you try booting up without an xorg.conf file as I fear it's perhaps confusing things. It should run OK without the xorg.conf file, but keep it safe (i.e. don't just rm it!) incase things go wrong.

its all what I got with that command and I'm quit sure of that :)) .. 

what do you mean " boot up without an xorg.conf " I can't remove it or rename it :'(

Why not? In terminal as root (using command su and entering root password):

mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

(In reply to comment #34)
> Why not? In terminal as root (using command su and entering root password):
> 
> mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

yes I did so , and rebooted .. 

well the first Mageia booting screen was fine and after that while loading the log screen oops the backlight is just gone and since then I've never seen it again !

Anyway I'm not depressed about it .. I just did a quick upgrade with the Mageia DVD and now I'm back to the start .. let's try out something else ;D

Can you get into the machine (e.g. by booting to runlevel 3) and copy out the /var/log/Xorg.0.log* files and attach them?

There are lots of other debugging things that can be done too, but it's quite complex to explain how to do them, so I'll refrain for now.

HI , 

Can you please tell me how do I boot to runlevel 3 , I've been looking in internet how to do it and find this 

" su > root password
nano -w  /etc/inittab " but this command nano is not found !

Created attachment 626 [details]
Xorg.0.log.old and Xorg.0.log

(In reply to comment #38)
> HI , 
> 
> Can you please tell me how do I boot to runlevel 3 , I've been looking in
> internet how to do it and find this 
> 
> " su > root password
> nano -w  /etc/inittab " but this command nano is not found !

I just rebooted and then waited for the bootloader screen and then I pressed F3 and chosen Default , a command line appeared with some crazy details , I just added 3 to that line and pressed Enter .. I hope its right what I did !

OK, so a few points. 

1. Please do not upload compressed files as attachments here. If the attachments are compressed they cannot be viewed in line. When plain text files are uploaded it's much simpler. You should have seen how I manually fixed the last time you did this and asked you not to do it again above. Please keep this in mind when adding future attachments.

2. Booting to runlevel 3 by adding a 3 to the end of the kernel load line is correct.

3. Both the logs inside your tarball suggest you are using the VESA driver and the /etc/X11/xorg.conf file. Are you sure the file /etc/X11/xorg.conf does not exist as per previous instructions? If so, then let me know, as it'll change things somewhat in the way I investigate this.

Ok sorry I just wanted to provide the 2 files in one single attachment .. anyway its not a big problem .. I wont do it again . 

for the xorg.conf Im not sure that I understand what you mean , but I took a look at it and I see no changes , its the same as in the runlevel 5 !

Created attachment 627 [details]
Xorg.conf

The whole point is we do not want ANY xorg.conf file. It should be moved out of the way. I asked you to do this in comment 32 which Sander clarified in comment 34.

Does the file just get regenerated automatically if you move it out out of the way? (this is possible, I'm not sure of the state of xorg.conf generation these days).

Please double check and if possible upload a log when X is started without a conf file which should mean the intel driver is used.

Failing that, please run drakx11 tools from the console and configure to use the intel driver. This should mean that the xorg.conf file generated will have the line
  Driver "intel"

in it somewhere.


In short, I need you to actually start your X server with the actual intel driver.... (and the fact it's taken until comment 44 to get here is very surprising!!)

Oh my God . I just did not understand your point . I think you meant that I should remove the Xorg.conf and try to boot up with runlevel 3 !

IN comment 35 you said you rebooted (after removing the xorg.conf file) and you said you couldn't see anything. Due to this I wanted to get the log files generated from this failed run in order to analyse them. That's why I asked you to boot to runlevel 3 to extract them so I could analyse.

This bug is reported against the x11-driver-video-intel, but so far none of the debug output has indicated that this package has been used yet!


Hopefully you can work out how to actually use this driver and then upload a useful log of me to look into! If you do manage to run the intel driver, I'd also very much like to see the output from "xrandr --props" as indicated above too :)

I can't give you a log when booting without Xorg.conf . as I said X crashes after the first Mageia booting screen and while loading log screen . so I can't see anything which means I can't use the computer .. 

actually I run drakx11 from a console and set up settings to Intel driver . of course that warning keeps showing up ( using thia graphic card my freeze your system , yes or no ) and I know that its gonna freeze and bring my system into darkness .. 

now I have changed it and I still need to log out and log in to take effect and its obvious that the backlight is not gonna come up . because I have done this at least 1000 times now .. 

what should I do now ?

1. Remove current xorg.conf
2. Reboot and let X crash
3. Reboot again, this time into init 3
4. Make a copy of Xorg logs that Colin asked for
5. Attach those logs to this bug

(In reply to comment #47)
> I can't give you a log when booting without Xorg.conf . as I said X crashes
> after the first Mageia booting screen and while loading log screen . so I can't
> see anything which means I can't use the computer .. 

This is exactly why we asked you to boot into runlevel 3 immediately after the crash so that we could get the logs from the crash to analyse! Without these kind of details we are all lost at sea.

Please follow Sanders' instructions.

(In reply to comment #48)
> 1. Remove current xorg.conf
> 2. Reboot and let X crash
> 3. Reboot again, this time into init 3
> 4. Make a copy of Xorg logs that Colin asked for
> 5. Attach those logs to this bug

 1. I removed the current xorg.conf 

 2. I rebooted and let X crash 

 3. I rebooted again to runlevel 3 , X crashes again and at the log screen everything becomes black . the backlights are gone :( 

__

anyway I did a quick upgrade with the DVD and this time I let the default installation of Mageia . which means Mageia installs the driver " Intel 810 and later " by default . of course X crashes after the bootlaoder screen . what I did is using init 3 under " safe setting " and look what I've got 

fatal server error : no screen found 

please consult the X.org foundation support at  https://bugs.mageia.org/

for help , please check the log file at var/log/xorg.0.log 

xinit: giving up 

xinit: unable to connect to a server : connection refused 

xinit: server error

OK, so I'm super confused.... X crashes after the bootloader screen? X does not start until quite late in the boot process, so I cannot see how it can possibly crash immediately after the bootloader screen.

I'm wondering if the terminology used here is confusing things for you.

By "bootloader screen" do you mean the menu where you can pick which kernel to boot or do you mean the screen that shows the progress of boot. The term bootloader referes to the system menu. The actual screen that shows the progress of the boot is different.

Also the output there tells you to check the log file.... I presume you copied the log file for analysis seeing is this is what we need to proceed. Without this log file there is very little we can do to help.

Some additional tips that may help you debug.

 1. When the screen goes blank when X11 kicks in, does typing "CTRL+ALT+F1" return you to a text console?

 2. When you edit the boot command line to enter runlevel 3, does adding i915.modeset=0 help?

(In reply to comment #51)
> OK, so I'm super confused.... X crashes after the bootloader screen? X does not
> start until quite late in the boot process, so I cannot see how it can possibly
> crash immediately after the bootloader screen.
> 
> I'm wondering if the terminology used here is confusing things for you.
> 
> By "bootloader screen" do you mean the menu where you can pick which kernel to
> boot or do you mean the screen that shows the progress of boot. The term
> bootloader referes to the system menu. The actual screen that shows the
> progress of the boot is different.
> 
> Also the output there tells you to check the log file.... I presume you copied
> the log file for analysis seeing is this is what we need to proceed. Without
> this log file there is very little we can do to help.

Im also confused ., we have that menu where I pick the kernel , and when I choose the kernel there is another screen which shows up which explains the boot process I think .. after this boot process screen X crashe and makes the screen go black .

when the screen goes black,. and type CTRL+ALT+F1 it takes me to the text console but also backlights are still gone .

for the command line . Im gonna try it out and tell you .

Ok, one more try:

1. Remove xorg.conf
2. Reboot
3. Let the X crash
4. Switch to console (Alt + Ctrl + F1)
5. You should see prompt, or if you don't just typle blindly:
    a) root
    b) hit Enter
    c) root users password
    d) hit Enter
    e) cp /var/log/Xorg.0.log* /home/YOUR_USERNAME_HERE/
    f) exit
    g) hit Enter
6. Make your X work again and then attach Xorg log files from your home direcory

(In reply to comment #54)
> Ok, one more try:
> 
> 1. Remove xorg.conf
> 2. Reboot
> 3. Let the X crash
> 4. Switch to console (Alt + Ctrl + F1)
> 5. You should see prompt, or if you don't just typle blindly:
>     a) root
>     b) hit Enter
>     c) root users password
>     d) hit Enter
>     e) cp /var/log/Xorg.0.log* /home/YOUR_USERNAME_HERE/
>     f) exit
>     g) hit Enter
> 6. Make your X work again and then attach Xorg log files from your home
> direcory



I did all of this , and when I checked my home I found nothing there . and to make sure I did again with text console with the working X , 

 cp /var/log/Xorg.0.log* /home/YOUR_USERNAME_HERE/: no such file or dictionary 

just one stupid question: how do I write ( = ) in text console mode , I couldn't find it anywhere , I should try what Colin told me !

You do not type YOUR_USERNAME_HERE, you are meant to type your own username.... It's just a method to save those files so they do not get overwritten on next boot, such that you can then supply them to us.

I have no idea what you are asking with your "one stupid question"...

Of course I typed my own user name .. its obvious :) 

what I mean why my question is . I want to add ( i915.modeset=0 ) to that command line to boot with init3 . but I dont know where that equal symbol is !

I doubt the modeset thing will help much. The Xorg.0.logs are by far and away the most interesting things, so please do concentrate on getting those logs for us.

I do not know where the = sign is on your keyboard as your layout will be different to mine. I'm afraid we cannot support this kind of question on a bug as it's already getting out of hand with tangential questions. Please consult Google or forums or other places to work this out.

Ok guys I'll do my best to get you these Logs ,, I'LL retry everything we have done here . I did not give up .so its your turn not to give up :)

(In reply to comment #59)
> Ok guys I'll do my best to get you these Logs ,, I'LL retry everything we have
> done here . I did not give up .so its your turn not to give up :)

Can this bug be closed?

CC: (none) => shlomif

Please do not close it. Thanks!

I have the same problem on an Aspire 5736Z of a friend of mine with the same video card.

So, when I installed Mageia on that laptop, Mageia choosed the driver "Intel 810 an later" (intel driver in xorg.conf) but that darkenes the monitor on X start as described above. It is very hard to recognize anything. Changing to Ctrl + Atl + F1 it remains dark.

Changing the driver with drakx to "Vermilion-based cards" it uses the vesa driver in xorg.conf. With that driver X starts but without 3D effects and the icons seem to be streched.

If you're still interested in solving this bug (if it is not solved already somewhere else), I can ask my friend to bring the laptop to me again so i can send you the logs you asked before.

Pleas let me know. 

Thanks
egc

CC: (none) => egc

Created attachment 970 [details]
Xorg.0.log file with no xorg.conf file

I must correct myself: the monitor does not get dark only on X start but already  when boot messages output starts.

Choosing secure setting in the grub menu (F3) with no xorg.conf file brings up the X, but i don't know which driver is used.

is this bug closed?

(In reply to comment #65)
> is this bug closed?

Its status is still open. Does anyone have any fix to this problem?

@ Colin
@ Thierry's

I don't know why this bug was assigned to Colin, x11-driver-video-intel is Thierry's package. (BTW, Colin, I'm impressed by your patience :) )

egc made some comments in this report and added an Xorg.0.log
Can one of you please have a look?

CC: (none) => marja11, thierry.vignaud

I'm not really sure what's going on here.

It's hard to say exactly what the problem is, but I'd expect some kind of kernel problem if the early boot screen is also not visible.

Can you try with one of the mga2 Live CDs (from alpha1 or similar as I don't think alpha3 ones are available) and see if you still get the problem?

(In reply to comment #68)
> I'm not really sure what's going on here.
> 
> It's hard to say exactly what the problem is, but I'd expect some kind of
> kernel problem if the early boot screen is also not visible.
> 
> Can you try with one of the mga2 Live CDs (from alpha1 or similar as I don't
> think alpha3 ones are available) and see if you still get the problem?

There appears to be one here:

http://mirrors.kernel.org/mageia/iso/cauldron/Mageia-2-alpha3-x86_64/

Should I use it?

Regards,

-- Shlomi Fish

(In reply to comment #69)
> (In reply to comment #68)
> > I'm not really sure what's going on here.
> > 
> > It's hard to say exactly what the problem is, but I'd expect some kind of
> > kernel problem if the early boot screen is also not visible.
> > 
> > Can you try with one of the mga2 Live CDs (from alpha1 or similar as I don't
> > think alpha3 ones are available) and see if you still get the problem?
> 
> There appears to be one here:
> 
> http://mirrors.kernel.org/mageia/iso/cauldron/Mageia-2-alpha3-x86_64/
> 
> Should I use it?
> 
> Regards,
> 
> -- Shlomi Fish

Only DVD's there atm, no LiveCD's

cc'ing tmb

@ tmb

Can the old Mageia 2 alpha  LiveCD isos still be downloaded somewhere?

2 weeks extra because the Live CD isn't available yet

(In reply to comment #71)
> 2 weeks extra because the Live CD isn't available yet

and again 2 weeks extra

@  Aizen, egc, Shlomi, anybody else who had this bug

The Mageia 2 beta 3 Live CD's are available, please test and report whether the problem is still there.

http://blog.mageia.org/en/2012/04/18/last-run-for-mageia-2-test-beta-3/

(In reply to comment #73)
> @  Aizen, egc, Shlomi, anybody else who had this bug
> 
> The Mageia 2 beta 3 Live CD's are available, please test and report whether the
> problem is still there.
> 
> http://blog.mageia.org/en/2012/04/18/last-run-for-mageia-2-test-beta-3/

With the x86-64 GNOME Europe 1 LiveCD, I can start X and the GNOME 3 environment (with its rudimentary effects) fine. My machine's specifications are:

    An Intel Core i3 CPU (x86-64).
    8 GB of RAM.
    Intel Corporation Sandy Bridge Integrated Graphics Controller (rev 09)
    A 2 TB hard-disk.
    A 19×´ LCD Screen by ViewSonic.
    Intel Corporation Cougar Point High Definition Audio Controller.
    Intel Corporation 82579V Gigabit Network Connection.

Regards,

-- Shlomi Fish

@ Shlomi

Thanks for the feed back :)

@ Aizen
@ egc

Is the bug fixed for both of you in LiveCD 2 beta 3, too?

Sorry, I have no access to the Aspire 5736Z laptop anymore, so I can't tell.

Thx egc for the feedback.

OK, Aizen didn't reply, but for Shlomi it was fixed in Mageia 2 beta 3

I would be nice to know what fixed it :)

Anyway, Mageia 1 users with this problem: there is light at the end of the tunnel, Mageia 2 stable is expected to be released next month :)

Removing the NEEDINFO keyword, because Colin's question was answered by Shlomi for the beta 3 LiveCD

Keywords: NEEDINFO => (none)

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

This bug is still valid on Mageia 2. 
I had once again the chance to try a USB live version of Mageia on the Aspire 5736Z laptop and the bug was still there. For the future I can not test anymore on this laptop because the owner wanted me to put Win7 on it :-(

(In reply to comment #80)
> This bug is still valid on Mageia 2. 
> I had once again the chance to try a USB live version of Mageia on the Aspire
> 5736Z laptop and the bug was still there. For the future I can not test anymore
> on this laptop because the owner wanted me to put Win7 on it :-(

Thanks for the feedback.

AFAIK, this bug was solved for everyone else, so there only seems to be a problem left with the Intel GM45 chipset (I read in your attachment 970 [details] that is the graphic card involved). But if there is a problem with that chipset, why doesn't Luc Menut have it too, then? 
https://www.mageia.org/pipermail/mageia-dev/2012-May/015388.html

@ lmenut

You didn't get a problem with that chipset later on, did you?

CC: (none) => lmenut
Version: 1 => 2
Target Milestone: Mageia 1 => ---
Whiteboard: LiveCD => MGA1TOO

(In reply to comment #81)
[...]
> 
> AFAIK, this bug was solved for everyone else, so there only seems to be a
> problem left with the Intel GM45 chipset (I read in your attachment 970 [details] that is
> the graphic card involved). But if there is a problem with that chipset, why
> doesn't Luc Menut have it too, then? 
> https://www.mageia.org/pipermail/mageia-dev/2012-May/015388.html
> 
> @ lmenut
> 
> You didn't get a problem with that chipset later on, did you?

I have no problem with my laptop (Dell Latitude E 4300 with Intel GM45) with mga 1 or mga 2. So it's not a general issue with Intel GM45 chipset.
But even if my laptop uses the same chipset video, it's not the same laptop, so not the same motherboard, not the same bios, not the same screen, ... lots of differents components that can be implied in this bug !!

regards,
Luc

See also bug 6077

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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