From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 79522] New: [NV67] Possible Regression 3.14.4+
Date: Mon, 02 Jun 2014 03:18:13 +0000 [thread overview]
Message-ID: <bug-79522-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1844 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79522
Priority: medium
Bug ID: 79522
Keywords: regression
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [NV67] Possible Regression 3.14.4+
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: storkus-FfzuIwEQ1aBBDgjK7y7TUQ@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Note: this may be related to Bug#70972.
My Acer Aspire 5520-5092 with a GeForce 7000M/nForce 610M MCP-67 running
Slackware 14.1 was working fine until I updated to kernel 3.14.4. I had
previously upgraded to 3.14.3 and nothing happened then. Upgrading again today
to 3.14.5 did not fix the problem, although it behaves slightly differently.
The problem is that, during boot, upon KMS loading and the framebuffer starting
up, the laptop backlight does not turn on most of the time; part of the time
when it does, I still have a blank screen. Sometimes the machine seems to have
booted up, but most of the time it appears locked, yet without a blinking LED.
This has all the hallmarks of a race as rebooting enough times gives a working
system. I haven't yet tried using an external monitor.
The only other update the Slackware has done since this started is messing with
LibELF--still 0.8.13, but with new compile options. This was done
simultaneously with the kernel updates. I don't see how this could affect the
kernel prior to mounting anything, though.
Thanks for any help, and a needed project! Mike
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3333 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-06-02 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 3:18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-79522-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-06-02 3:28 ` [Bug 79522] [NV67] Possible Regression 3.14.4+ bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-28 8:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-79522-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.