From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 51157] New: GeForce GT 540M not working anymore
Date: Sat, 16 Jun 2012 20:22:07 +0000 [thread overview]
Message-ID: <bug-51157-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=51157
Bug #: 51157
Summary: GeForce GT 540M not working anymore
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: aiguo.fernandez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 63117
--> https://bugs.freedesktop.org/attachment.cgi?id=63117
dmesg from kernel 3.4
I have a Sager NP5160 with Nvidia GeForce GT 540M Optimus card and running Arch
Linux.
Bumblebee was working fine with previous kernels, but it stopped working since
around kernel 3.1. I tried solving this with the Bumblebee team at
https://github.com/Bumblebee-Project/Bumblebee/issues/156 but no luck. I'm
thinking it may be something with the DRM module in the kernel.
Fortunately, it still works with the current LTS kernel in Arch (3.0.34) which
may help get some insight. I'm attaching my dmesg from both the lts kernel and
from the current kernel (3.4.2). I'm also attaching my vbios.rom from
/sys/kernel/debug/dri/0/vbios.rom
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-06-16 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 20:22 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-51157-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-06-16 20:11 ` [Bug 51157] GeForce GT 540M not working anymore bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 20:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 20:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-01 13:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 23:39 ` [Bug 51157] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-07 17:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-07 17:47 ` 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-51157-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.