Bug 15967

Created attachment 6572 [details]
report.bug.xz

You can also blacklist the nouveau module at boot, without rebuilding a kernel.

CC: (none) => anssi.hannula, tmb

It is not and has never been compiled in:

i386.config:CONFIG_DRM_NOUVEAU=m
x86_64.config:CONFIG_DRM_NOUVEAU=m

and it will use the driver you configure.

If you want to use Intel only, you should be able to disable the nVidia card in the BIOS / UEFI FW

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

Hi,

back in 3.19.2-2.mga5 kernel the nouveau driver actually was compiled in and there was no way to blacklist it at boot.

So now, with 3.19.8-1.mga5, the system hangs before boot has completed. It is not frozen though, because ctrl+alt+del works.

There is another issue. I will investigate, and try to give a fix / or some boot log.

I re-open, because I made some findings.

In the 3.19.8-1.mga5 kernel, what causes the trouble is:

CONFIG_DRM_NOUVEAU=m
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y

If I re-compile with:

# CONFIG_DRM_NOUVEAU is not set

My Dell XPS 15 (model: xps_l502x) boots normally.


I made additional tests, if I compile with:


CONFIG_DRM_NOUVEAU=m
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=n

and blacklist the nouveau driver (or rename it in "nouveau.ko.bak"),

the boot process is stalled after 23s (key pressed are echoed and caps lock Led can be activated). The only thing that allows to progress is ctrl + alt + del (reboots).

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Same symptoms with:

initrd-linus.img -> initrd-3.19.8-1.mga5.img
vmlinuz-linus -> vmlinuz-3.19.8-1.mga5

It is not possible to disable the NVidia graphics card in the BIOS of these Dell laptops in order to keep only the Intel 810 card enabled.

That makes me think this is a serious bug, because the owners of these laptops will have their machine bricked, after install, if they can't revert to an old Mageia 4 kernel.

(In reply to Olivier LE ROY from comment #4)
> Hi,
> 
> back in 3.19.2-2.mga5 kernel the nouveau driver actually was compiled in and
> there was no way to blacklist it at boot.
> 

No it was not!

http://svnweb.mageia.org/packages/cauldron/kernel/releases/3.19.2/2.mga5/PATCHES/configs/x86_64.config?revision=819214&view=markup

(In reply to Olivier LE ROY from comment #7)
> It is not possible to disable the NVidia graphics card in the BIOS of these
> Dell laptops in order to keep only the Intel 810 card enabled.
> 

That's bad.

> That makes me think this is a serious bug, because the owners of these
> laptops will have their machine bricked, after install, 

It's not bricked. it just is isn't properly detecting wich gpu so send output on so you get a mismatch between what hw thinks and what the xorg server tries to use.

> if they can't revert to an old Mageia 4 kernel.


there should still be a boot menu option for the older kernel.


And you can try to boot with:

 rdblacklist=nouveau xdriver=intel

Hi,

sorry, nouveau was not compiled in the kernel in 3.19.2-2.mga5.

In the mean time, I have made other tests, and I have other elements:

"rdblacklist=nouveau xdriver=intel" options at boot don't solve the issue, either in 3.19.8-1.mga5 (linus or with Mageia patches). Failsafe mode doesn't help.

Same result if I rename nouveau.ko in nouveau.ko.bak.

Graphics card is initialized at boot, but X11.org doesn't start, kernel boot log is displayed on the screen. It is not possible to have a bash console.

The only way I have, for now, to boot up is re-compiling the kernel with "# CONFIG_DRM_NOUVEAU is not set".

My laptop was built in 2011, and is still performing well with Intel Core i7-2630QM CPU.

I think it may be a general problem accross all distributions.

I would like to add one more element:

I don't have the issue if booting with this kernel: 3.19.0-desktop-1.mga5

does kernel 4.1.7 in cauldron or mga5 updates testing work any better ?

Depends on: (none) => 16655

There is the same issue if booting with vmlinuz-4.1.8-desktop-1.mga5.

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Setting Version: to 5, because I don't see any comments about this happening with mga6 kernels.

CC: (none) => marja11
Version: Cauldron => 5
Whiteboard: MGA5TOO => (none)

Hi Olivier,

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

==> If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

No reply, so closing as OLD since Mageia 5 is no longer maintained.

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