Bug 16245 - Nouveau errors at boot time and complete desktop freeze on several systems with optimus hybrid graphics
Summary: Nouveau errors at boot time and complete desktop freeze on several systems wi...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
: 18808 21438 (view as bug list)
Depends on: 15734
Blocks: 14069
  Show dependency treegraph
 
Reported: 2015-06-28 21:17 CEST by Rémi Verschelde
Modified: 2017-09-10 16:47 CEST (History)
16 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Here's my Xorg.log (22.53 KB, text/x-log)
2016-01-29 01:30 CET, Kristoffer Grundström
Details

Description Rémi Verschelde 2015-06-28 21:17:14 CEST
+++ This bug was initially created as a clone of Bug 15734 comment 39 +++

I tried to install Mageia 5 on my new laptop (UEFI) an ASUS N551J with two graphical cards (intel and nvidia). I have tried every option mentioned in the errata (hybrid graphics). I have tried the Live KDE 64 DVD and the classical 64 DVD. Nothing works. I am now 'doomed' to use Mint, that works at once, but I like Mageia much better (if it is installable).

LiveKDE64DVD:

Sometimes at boottime (LiveDVD) I get many nouveau errors and after a while I get a KDE desktop (intel detected?). I can than install it and after reboot I sometimes can configure a user and can log in into KDE. After a few seconds everything freezes. Poweroff and poweron and than it freezes already at boottime (blank screen or with nouveau errors with sometimes I see kernel panic).

Sometimes at boottime (LiveDVD) I get less nouveau errors and it freezes already (no KDE).

I tried boot options as suggested 'optimus' and/or 'rd.blacklist=nouveau rd.blacklist=nvidia xdriver=intel' â> No effect. Still nouveau errors at boottime and/or freezes.

ClassicalKDE64DVD:

Installation works until after reboot. Same problems as with the LiveDVD.
I tried the boot options, no effect. At the point of the installer to configure the graphics, it suggested 'Intel 810 and later' and not 'use intel only' as told in the errata. Even with Intel selected I get nouveau errors at boottime, with or without boot options.

It seems a problem like mentioned in the errata with the hybrid graphics (Intel+Nvidia), but the suggested options does not work.

Linux Mint 17.1:

No problem, works at once. No errors.
Comment 1 Rémi Verschelde 2015-06-28 21:18:29 CEST
Please also refer to:

attachment 6786 [details] boot screen LiveKDE64DVD on ASUS N551J nouveau errors (part1)

attachment 6787 [details] boot screen LiveKDE64DVD on ASUS N551J nouveau errors (part2)

attachment 6788 [details] Xorg log of LiveKDE64DVD on ASUS N551J (if I am lucky to get so far)
Comment 2 isadora 2015-06-28 22:52:57 CEST
Same issues on my new laptop:
MSI GE70 2PC

4th Gen Core Processor Integrated Graphics Controller
GeForce GTX 850M

Went back to Mageia 4, no issues there, as there never were.

CC: (none) => isis2000

Comment 3 Martin Whitaker 2015-06-28 23:08:01 CEST
A quick search found this:

https://lists.archlinux.org/pipermail/arch-general/2015-March/038729.html

My recollection is that using rd.blacklist didn't work for me, because the nouveau driver got loaded later in the boot sequence. You could try adding

  blacklist nouveau

to /etc/modprobe.conf on the installed system to see if that helps.

I see in Peter's log that he is also experiencing bug 16033, although that is probably not important at this stage.
Comment 4 Martin Whitaker 2015-06-28 23:58:49 CEST
Just done some experiments on my laptop, and I need both the boot option *and* the entry in /etc/modprobe.conf to prevent the nouveau module being loaded.

Furthermore, the required boot option is "rdblacklist=nouveau", not "rd.blacklist=nouveau".
Alejandro Cobo 2015-06-29 00:03:52 CEST

CC: alejandrocobo => (none)

Comment 5 Peter Woldering 2015-06-29 22:08:07 CEST
It is working now :-)

I use the boot options 'rdblacklist=nouveau nouveau.runpm=0 xdriver=intel'

nouveau.runpm=0 is a tip from doktor500, with this the LiveDVD/USB gives nouveau errors but I get at least at every boot a KDE desktop.

The same boot options I use for the installed system.
Right after install with the first boot I selected 'Safe Mode' and added 'blacklist nouveau' to /etc/modprobe.conf.

After this I get no errors and get a beautiful Mageia KDE desktop.

Thanks for all the help.
Samuel Verschelde 2015-06-30 09:28:34 CEST

Assignee: bugsquad => tmb

Comment 6 isadora 2015-07-04 16:38:20 CEST
Same here.
Installed Mageia 5 in a free partition, so i could leave Mageia 4 in place, in case of.

But, so far the abovementioned workaround worked.
Comment 7 Angelo Naselli 2015-09-06 18:59:11 CEST
Acer aspire 5750g installed on external usb3.0 disk, same problem here
black listed nouveau workarounded here also

CC: (none) => anaselli

Comment 8 Kristoffer Grundström 2016-01-29 01:30:24 CET
I have the model from Asus called N550JK and I have the exact same problem.

My fix was to add blacklist=nouveau the kernel boot line.

Is there an ETA on this fix?

Before the release of Mageia 6?

CC: (none) => kristoffer.grundstrom1983

Comment 9 Kristoffer Grundström 2016-01-29 01:30:58 CET
Created attachment 7386 [details]
Here's my Xorg.log
Marja van Waes 2016-06-29 16:45:56 CEST

Summary: Nouveau errors at boot time and complete desktop freeze on ASUS N551J with optimus hybrid graphics => Nouveau errors at boot time and complete desktop freeze on several systems with optimus hybrid graphics

Comment 10 Marja van Waes 2016-06-29 16:49:47 CEST
*** Bug 18808 has been marked as a duplicate of this bug. ***

CC: (none) => olivier_le_roy
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=18808

Comment 11 Marja van Waes 2017-09-10 16:46:58 CEST
*** Bug 21438 has been marked as a duplicate of this bug. ***

CC: (none) => simon

Marja van Waes 2017-09-10 16:47:38 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=13986


Note You need to log in before you can comment on or make changes to this bug.