I have done a fresh install of M6 into a btrfs partition; I already have M4 working on another partition. The installation proceeded without problem and I accepted all the default options. When I boot the process fails early on and gets itself into a loop. The final messages are from the nouveau driver: nouveau 0000:01:00.0: DRM: evicting buffers ... nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle ... nouveau 0000:01:00.0: DRM: suspending kernel object trees ... nouveau 0000:01:00.0: DRM: suspending kernel object tree ... I have got a screenshot of the log file but haven't worked out how to attach it to this report. Below is a paste of part of Xorg.0.log: [ 43.595] (II) NOUVEAU(1): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video. [ 43.595] (II) NOUVEAU(1): [XvMC] Extension initialized. [ 43.595] (**) NOUVEAU(1): DPMS enabled [ 43.595] (II) NOUVEAU(1): RandR 1.2 enabled, ignore the following RandR disabled message. [ 43.595] (--) RandR disabled [ 43.600] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 43.600] (II) AIGLX: enabled GLX_ARB_create_context [ 43.600] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 43.600] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile [ 43.600] (II) AIGLX: enabled GLX_INTEL_swap_event [ 43.600] (II) AIGLX: enabled GLX_SGI_swap_control [ 43.600] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 43.600] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 43.600] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float [ 43.600] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 43.600] (II) AIGLX: enabled GLX_ARB_create_context_robustness [ 43.600] (II) AIGLX: Loaded and initialized i965 [ 43.600] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 43.629] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 43.629] (II) AIGLX: enabled GLX_ARB_create_context [ 43.629] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 43.629] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile [ 43.629] (II) AIGLX: enabled GLX_INTEL_swap_event [ 43.629] (II) AIGLX: enabled GLX_SGI_swap_control [ 43.629] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 43.629] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 43.629] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float [ 43.629] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 43.629] (II) AIGLX: Loaded and initialized nouveau [ 43.629] (II) GLX: Initialized DRI2 GL provider for screen 1 [ 43.631] (II) intel(0): switch to mode 1920x1080@60.0 on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none [ 43.644] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 1, position (0, 0), rotation normal, reflection none [ 43.649] (II) intel(0): Setting screen physical size to 508 x 285 [ 43.650] (II) NOUVEAU(1): NVEnterVT is called. [ 43.650] (EE) [ 43.650] (EE) Backtrace: [ 43.650] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x5880a9] [ 43.651] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f065cce3bff] [ 43.651] (EE) 2: /usr/libexec/Xorg (xf86RandR12CreateScreenResources+0x544) [0x4b2ca4] [ 43.651] (EE) 3: /usr/libexec/Xorg (InitExtensions+0x5a0) [0x4a62f0] [ 43.651] (EE) 4: /usr/libexec/Xorg (InitFonts+0x2bd) [0x43913d] [ 43.651] (EE) 5: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f065c940600] [ 43.651] (EE) 6: /usr/libexec/Xorg (_start+0x29) [0x424339] [ 43.651] (EE) [ 43.651] (EE) Segmentation fault at address 0x0 [ 43.651] (EE) Fatal server error: [ 43.651] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 43.651] (EE) [ 43.651] (EE) Please consult the Mageia support at https://bugs.mageia.org for help. [ 43.651] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 43.651] (EE) [ 43.651] (II) AIGLX: Suspending AIGLX clients for VT switch [ 43.665] (II) AIGLX: Suspending AIGLX clients for VT switch [ 43.665] (II) NOUVEAU(1): NVLeaveVT is called. [ 43.718] (EE) Server terminated with error (1). Closing log file. I have marked this critical since its consequence is that I can't run M6 at all, so I'll have to continue with M4.
Created attachment 9560 [details] Xorg.0.log
Created attachment 9561 [details] dmesg
I have now added Xorg.o.log and dmesg as attachments so in etrospect not all the text in the report was necessary.
And if you add modprobe.blacklist=nouveau to the kernel before booting it, does that change the situation?
Try adding $vt_handoff as well.
CC: (none) => hamnisdude
Did you install from a Live iso, or from a classical (non-Live) iso?
CC: (none) => isobuild, kernel, marja11Keywords: (none) => NEEDINFO
Thanks for those suggestions. I have tried them and can confirm that setting modprobe.blacklist=nouveau on the boot line works - problem solved thanks very much. For anyone else with this problem here's what you need to do: 1) boot in recovery mode then give the root password at the console when prompted 2) attach to the bootloader directory: cd /boot/grub2 3) edit the config file: vi grub.cfg 4) locate the first menuentry: menuentry 'Mageia' 5) search forward for the line starting: linux16 /boot/vmlinuz 6) append the following: modprobe.blacklist=nouveau 7) write the file and exit the editor 8) install the new loader: ./install.sh This should report no errors. Now reboot and the graphics should start up so that you can login. Once logged in use the GUI boot setup and add modprobe.blacklist=nouveau to the boot argument list for all images.
(In reply to Marja van Waes from comment #6) > Did you install from a Live iso, or from a classical (non-Live) iso? I installed from a classic (64-bit) iso.
(In reply to Simon Geard from comment #7) > For anyone else with this problem here's what you need to do: ... The easier way is to press 'e' in the grub2 boot menu and modify the command line just for that boot. Then, when the system has booted, you can use the GUI boot setup in MCC to make the changes permanent. (In reply to Simon Geard from comment #8) > I installed from a classic (64-bit) iso. From your Xorg.0.log, it looks like you have Optimus (hybrid Intel/NVIDIA) graphics. Towards the end of the install, you should have been asked how to handle the multiple heads. Did you select the "Use Intel only" option (as recommended in the errata) or one of the other options?
CC: (none) => mageia
I opted for the default - configure all heads independently. That's what I did for Mageia4 which worked - I confess I did not look at the errata before installing. I tried 'e' in the grub2 menu and was able to add the 'modprobe...' but it wasn't at all clear what to do next. I tried exit, boot, continue without success. 'Esc' continued with the boot but it still failed so I assume that wasn't correct either. So having failed with that I used the method I described above (comment 7).
(In reply to Simon Geard from comment #10) > I opted for the default - configure all heads independently. The problem here is that the installer doesn't know that you have hybrid graphics - it just sees two graphics devices and assumes you have two independent graphics cards. Configuring the heads independently is known to cause problems on some hybrid graphics systems, so the best bet is to select the Intel only option. Improving support for hybrid graphics is on the to do list for Mageia 7... > That's what I did for Mageia4 which worked - I confess I did not look at the > errata before installing. To be fair, the errata isn't as clear as it could be. > I tried 'e' in the grub2 menu and was able to add the 'modprobe...' but it > wasn't at all clear what to do next. I tried exit, boot, continue without > success. 'Esc' continued with the boot but it still failed so I assume that > wasn't correct either. So having failed with that I used the method I > described above (comment 7). Ctrl-X should boot with your edited options. Did you add the option on the line starting "linux16 "?
(In reply to Martin Whitaker from comment #9) > > From your Xorg.0.log, it looks like you have Optimus (hybrid Intel/NVIDIA) > graphics. Towards the end of the install, you should have been asked how to > handle the multiple heads. Did you select the "Use Intel only" option (as > recommended in the errata) or one of the other options? Thanks for all your help with this report, Martin. Closing it as duplicate of bug #16245 *** This bug has been marked as a duplicate of bug 16245 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED