Summary: | x11-drivers/nvidia-drivers-295.20-r1 breaks input devices? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus Becker <marcus.disi> |
Component: | [OLD] Core system | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | jer, spock |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
xorg.log with the new nvidia driver
dmesg emerge --info |
Description
Marcus Becker
2012-02-17 21:55:34 UTC
Created attachment 302303 [details]
xorg.log with the new nvidia driver
Created attachment 302439 [details]
dmesg
Created attachment 302441 [details]
emerge --info
I tested without any external screen or keyboard and the same happens
Any update? Am I the only one? In the meantime I cannot update Xorg or evdev anymore: (x11-base/xorg-server-1.12.0::gentoo, ebuild scheduled for merge) conflicts with <x11-base/xorg-server-1.11.99 required by (x11-drivers/nvidia-drivers-290.10-r2::gentoo, installed) and: (x11-base/xorg-server-1.12.0::gentoo, ebuild scheduled for merge) pulled in by >=x11-base/xorg-server-1.11.99.901 required by (x11-drivers/xf86-input-evdev-2.7.0::gentoo, ebuild scheduled for merge) Unfortunately I don't have a DisplayLink device. I also haven't seen any reports on the forums about this. Your best bet is to run nvidia-bug-report.sh and send the results to linux-bugs@nvidia.com. The last issue you've observed has been fixed in the tree. This is not DisplayLink related, as I stated above. I disconnected all devices but the pure laptop display, keyboard and touchpad. The same happened with nvidia-drivers-295.x the new evdev-2.7.0 builds fine against gentoo-sources-3.2.12 now. nvidia-drivers-290.10-r2 fail against gentoo-sources-3.3.0 I am going to look for nvidia bug reports tomorrow, thanks :) Perhaps it is related to this very old bug? https://bugs.freedesktop.org/show_bug.cgi?id=30344 (In reply to comment #7) > Perhaps it is related to this very old bug? > https://bugs.freedesktop.org/show_bug.cgi?id=30344 Pretty good guess. Have you contacted upstream Marcus or has this resolved itself for you? Sorry, I didn't update. In the meantime I use my AMD card again and cannot reproduce the problem. (In reply to comment #9) > Sorry, I didn't update. In the meantime I use my AMD card again and cannot > reproduce the problem. Alright well as long as you have a workaround then I guess that's ok. |