Switching graphic output with keyboard doesn't help.

It goes very quickly to remember but I saw that gdm starts just before this.


BTW Live Mandriva 2010.1 runs fine from USB Flash.

can you *attach* /var/log/Xorg.0.log ?

Source RPM: mageia-1-beta2-live-kde-europa-cd-i586 => xorg

I'm sorry that I'm currently unable to provide more information about that. There are two reasons for that. First, I have never tried to remotely connect to other PC to grab some random file. At least I don't have clear picture how to do it. I'm familiar with "mc" and command line in general. If virtual consoles would work that would be trivial for me. Second but much smaller reason is that access to this notebook is not always easy.

CC: (none) => filip.komar

@ Filip

Did you still have the same problem with Mga1?

If so:

In the history I saw you filed this bug against mageia-1-beta2-live-kde-europa-cd-i586. You (?) chose the "installer" component, so I guess you installed from that CD. Is that correct?

If you did install, you can get /var/log/Xorg.0.log when using your Live Mandriva 2010.1 USB Flash on that notebook and mounting the / partition you made for your install

CC: (none) => marja11

Unfortunately I only tested Live KDE on that notebook. I think I also tried with Mga1 with the same results. I didn't install it because that bug prevent me to boot even live session. I didn't even manage to see X, screen went blank before it and virtual consoles were not available either. Maybe that was even kernel freeze but I don't remember exactly any more.

I also never tried to remotely connect to other PC to grab a file. It's not mine notebook but maybe I'll manage to try again later. I'll get back to this bug when that will happen.

(In reply to comment #5)
> It's not
> mine notebook but maybe I'll manage to try again later. I'll get back to this
> bug when that will happen.

Could you please try with the latest release, when you get a chance? That would be
Mageia-2-alpha1-LiveCD now.

In the pdf you referred to in the description, I read the laptop has a Mobile Intel GL40 Express graphic chipset. Do you happen to know whether that is correct?

Someone might close this bug report as OLD in the meantime, but please reopen it if the issue is still there.

CC: (none) => thierry.vignaud
Component: Installer => RPM Packages
Source RPM: xorg => drakx-kbd-mouse-x11

Same results are with Mageia-2-alpha2-LiveCD booted from USB as before.


> In the pdf you referred to in the description, I read the laptop has a Mobile
> Intel GL40 Express graphic chipset. Do you happen to know whether that is
> correct?
I'm not sure:
1. Reseller says: 	 Intel GMA 4500M, up to 1695 MB shared memory
2. Online Manual: 	 Mobile Intel® GL40 Express Chipset
3. Acer product support: VGA Driver For UMA

Product code is: eMachines E725-433G25W7.

(In reply to comment #7)
> Same results are with Mageia-2-alpha2-LiveCD booted from USB as before.
> 

Thanks for trying

> 
> > In the pdf you referred to in the description, I read the laptop has a Mobile
> > Intel GL40 Express graphic chipset. Do you happen to know whether that is
> > correct?
> I'm not sure:
> 1. Reseller says:      Intel GMA 4500M, up to 1695 MB shared memory
> 2. Online Manual:      Mobile Intel® GL40 Express Chipset
> 3. Acer product support: VGA Driver For UMA
> 
> Product code is: eMachines E725-433G25W7.



Please attach the output of 
lspcidrake -v

and attach  /var/log/Xorg.0.log too, please

Source RPM: drakx-kbd-mouse-x11 => ldetect

@ Filip

Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. I know it isn't your notebook, so you might need more time. If someone closes this report (that could even be me :/), feel free to reopen it when you have the requested information

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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