Description of problem:
Mageia cauldron sta2 .Net install launched yesterday evening.
I let the installation go on all the night (9 hours duration announced) .
When i come back this morning, the installation was waiting for root password but the screen was double and very small.
However, i succeded in finishing the installation, and Mageia sta2 has rebooted perfectly with a normal display.
i saw this too but "not all the time" :(
thierry any idea ?
if i reproduce i will take a picture
I can reproduce with net install too, using VBox (if you needed another confirmation).
This looks like a duplicate of:
(Installer graphics die at start of users screen in VBox)
(In reply to Barry Jackson from comment #3)
> This looks like a duplicate of:
> (Installer graphics die at start of users screen in VBox)
And there Barry reported updates (incuding kernel updates ) fixed it.
Is it fixed for you, too?
(In reply to Marja van Waes from comment #4)
> (In reply to Barry Jackson from comment #3)
> > This looks like a duplicate of:
> > https://bugs.mageia.org/show_bug.cgi?id=20354
> > (Installer graphics die at start of users screen in VBox)
> And there Barry reported updates (incuding kernel updates ) fixed it.
> @ Daniel
> Is it fixed for you, too?
Yes the bug is fixed, no duplicated or small screen, but i encountered a new problem :
At the choice of the monitor , the system has frozen.
I wait a moment but no mouse or keyboard responding.
I took a "instantané " (Menu/ machine "host T").I stopped the machine.
Then i restored it and the installation went on without any problem.
*** Bug 20504 has been marked as a duplicate of this bug. ***
@Thomas: any idea why fbdev does this?
Can it still be reproduced? Comments in bug 20354 (which is apparently related if not a duplicate) hint that it may be fixed now.
i got it yesterday with prestesting isos
(In reply to Nicolas Lécureuil from comment #9)
> i got it yesterday with prestesting isos
But what urpmi version do they have?
(In reply to Rémi Verschelde from comment #10)
> (In reply to Nicolas Lécureuil from comment #9)
> > i got it yesterday with prestesting isos
> But what urpmi version do they have?
Nevermind, wrong bug report.
This bug is still valid today.
Created attachment 9199 [details]
Installer report.bug.xz (from upgrade)
Just hit this when doing a mga5 -> mga6 upgrade in VirtualBox, using the Apr 7 Mageia-6-rc-x86_64-DVD.iso. In my case at least, the display corruption occurs when the system switches from using the framebuffer device to the vboxvideo drm device. The key section from the system log (extracted from report.bug) is:
<6>[ 215.672960] [drm] Initialized
<4>[ 215.688367] vboxguest: loading out-of-tree module taints kernel.
<4>[ 215.691310] vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
<6>[ 215.691411] input: Unspecified device as /devices/pci0000:00/0000:00:04.0/input/input5
<4>[ 215.691510] vboxguest: misc device minor 56, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
<7>[ 215.691511] vboxguest: Successfully loaded version 5.1.18 (interface 0x00010004)
<6>[ 215.694294] [drm] VRAM 01000000
<6>[ 215.694460] [TTM] Zone kernel: Available graphics memory: 2024542 kiB
<6>[ 215.694462] [TTM] Initializing pool allocator
<6>[ 215.694466] [TTM] Initializing DMA pool allocator
<7>[ 215.694648] checking generic (e0000000 1000000) vs hw (e0000000 1000000)
<6>[ 215.694650] fb: switching to vboxdrmfb from VESA VGA
<6>[ 215.694720] Console: switching to colour dummy device 80x25
<6>[ 215.694788] fbcon: vboxdrmfb (fb0) is primary device
<6>[ 215.694907] Console: switching to colour frame buffer device 100x37
<6>[ 215.694920] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
<6>[ 215.699951] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
and from Xorg.0.log:
[ 215.569] (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 /dev/dri/card0
[ 215.569] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 215.569] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 215.574] (II) LoadModule: "modesetting"
[ 215.574] (WW) Warning, couldn't open module modesetting
[ 215.574] (II) UnloadModule: "modesetting"
[ 215.574] (II) Unloading modesetting
[ 215.574] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 215.574] xf86: found device 0
Would this issue be related to bug 20354 too?
Remi: 20354, 20368, 20504 are the same bug.