Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
No Keyboard or mouse in X
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Tue Oct 29, 2013 7:39 am    Post subject: No Keyboard or mouse in X Reply with quote

I'm not sure what happened here but after an emerge world and reboot I can no longer use my keyboard or mouse to login at the KDM login prompt. I've tried
Code:
emerge -1 xf86-input-evdev xf86-input-keyboard xf86-input-mouse

and rebooted and yet still no input devices seem to work.

Everything seems to work outside of X-serv it's only in X that I seem to have this problem.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5526

PostPosted: Tue Oct 29, 2013 5:39 pm    Post subject: Reply with quote

So, anything of notice in xorg log ?
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Tue Oct 29, 2013 9:05 pm    Post subject: Reply with quote

I don't see anything un usual but here it is

Code:
[   129.119]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[   129.119] X Protocol Version 11, Revision 0
[   129.119] Build Operating System: Linux 3.10.7-gentoo-r1 x86_64 Gentoo
[   129.119] Current Operating System: Linux ramb00000 3.10.7-gentoo-r1 #14 SMP Mon Oct 21 00:14:19 PDT 2013 x86_64
[   129.119] Kernel command line: BOOT_IMAGE=/kernel-3.10.7-gentoo-r1 root=/dev/sdd1 ro
[   129.119] Build Date: 21 October 2013  11:31:51AM
[   129.119] 
[   129.119] Current version of pixman: 0.30.2
[   129.119]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   129.119] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   129.119] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 28 17:23:38 2013
[   129.121] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   129.121] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   129.121] (==) No Layout section.  Using the first Screen section.
[   129.121] (==) No screen section available. Using defaults.
[   129.121] (**) |-->Screen "Default Screen Section" (0)
[   129.121] (**) |   |-->Monitor "<default monitor>"
[   129.121] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
[   129.121] (**) |   |-->Device "nvidia"
[   129.121] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   129.121] (==) Automatically adding devices
[   129.121] (==) Automatically enabling devices
[   129.121] (==) Automatically adding GPU devices
[   129.122] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[   129.122]    Entry deleted from font path.
[   129.122] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   129.122]    Entry deleted from font path.
[   129.122] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   129.122]    Entry deleted from font path.
[   129.122] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   129.122]    Entry deleted from font path.
[   129.122]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   129.122] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   129.122]    Entry deleted from font path.
[   129.122]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   129.122] (==) FontPath set to:
   /usr/share/fonts/misc/
[   129.122] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   129.122] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   129.122] (II) Loader magic: 0x7fdbc0
[   129.122] (II) Module ABI versions:
[   129.122]    X.Org ANSI C Emulation: 0.4
[   129.122]    X.Org Video Driver: 14.1
[   129.122]    X.Org XInput driver : 19.1
[   129.122]    X.Org Server Extension : 7.0
[   129.124] (--) PCI:*(0:1:0:0) 10de:0641:3842:c945 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf4000000/33554432, I/O @ 0x00009c00/128, BIOS @ 0x????????/524288
[   129.125] Initializing built-in extension Generic Event Extension
[   129.125] Initializing built-in extension SHAPE
[   129.125] Initializing built-in extension MIT-SHM
[   129.125] Initializing built-in extension XInputExtension
[   129.125] Initializing built-in extension XTEST
[   129.125] Initializing built-in extension BIG-REQUESTS
[   129.125] Initializing built-in extension SYNC
[   129.125] Initializing built-in extension XKEYBOARD
[   129.125] Initializing built-in extension XC-MISC
[   129.125] Initializing built-in extension XINERAMA
[   129.125] Initializing built-in extension XFIXES
[   129.125] Initializing built-in extension RENDER
[   129.125] Initializing built-in extension RANDR
[   129.125] Initializing built-in extension COMPOSITE
[   129.125] Initializing built-in extension DAMAGE
[   129.125] Initializing built-in extension MIT-SCREEN-SAVER
[   129.125] Initializing built-in extension DOUBLE-BUFFER
[   129.125] Initializing built-in extension RECORD
[   129.125] Initializing built-in extension DPMS
[   129.125] Initializing built-in extension X-Resource
[   129.125] Initializing built-in extension XVideo
[   129.125] Initializing built-in extension XVideo-MotionCompensation
[   129.125] Initializing built-in extension XFree86-VidModeExtension
[   129.125] Initializing built-in extension XFree86-DGA
[   129.125] Initializing built-in extension XFree86-DRI
[   129.125] Initializing built-in extension DRI2
[   129.125] (II) LoadModule: "glx"
[   129.127] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   129.154] (II) Module glx: vendor="NVIDIA Corporation"
[   129.154]    compiled for 4.0.2, module version = 1.0.0
[   129.154]    Module class: X.Org Server Extension
[   129.154] (II) NVIDIA GLX Module  319.60  Wed Sep 25 14:24:11 PDT 2013
[   129.154] Loading extension GLX
[   129.154] (II) LoadModule: "nvidia"
[   129.154] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[   129.162] (II) Module nvidia: vendor="NVIDIA Corporation"
[   129.162]    compiled for 4.0.2, module version = 1.0.0
[   129.162]    Module class: X.Org Video Driver
[   129.218] (II) NVIDIA dlloader X Driver  319.60  Wed Sep 25 14:04:14 PDT 2013
[   129.218] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   129.218] (++) using VT number 7

[   129.222] (II) Loading sub module "fb"
[   129.222] (II) LoadModule: "fb"
[   129.222] (II) Loading /usr/lib64/xorg/modules/libfb.so
[   129.223] (II) Module fb: vendor="X.Org Foundation"
[   129.223]    compiled for 1.14.3, module version = 1.0.0
[   129.223]    ABI class: X.Org ANSI C Emulation, version 0.4
[   129.223] (WW) Unresolved symbol: fbGetGCPrivateKey
[   129.223] (II) Loading sub module "wfb"
[   129.223] (II) LoadModule: "wfb"
[   129.223] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[   129.225] (II) Module wfb: vendor="X.Org Foundation"
[   129.225]    compiled for 1.14.3, module version = 1.0.0
[   129.225]    ABI class: X.Org ANSI C Emulation, version 0.4
[   129.225] (II) Loading sub module "shadow"
[   129.225] (II) LoadModule: "shadow"
[   129.225] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[   129.225] (II) Module shadow: vendor="X.Org Foundation"
[   129.225]    compiled for 1.14.3, module version = 1.1.0
[   129.225]    ABI class: X.Org ANSI C Emulation, version 0.4
[   129.225] (II) Loading sub module "ramdac"
[   129.225] (II) LoadModule: "ramdac"
[   129.225] (II) Module "ramdac" already built-in
[   129.226] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   129.226] (II) NVIDIA(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[   129.226] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[   129.226] (==) NVIDIA(0): RGB weight 888
[   129.226] (==) NVIDIA(0): Default visual is TrueColor
[   129.226] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[   129.227] (**) NVIDIA(0): Enabling 2D acceleration
[   130.646] (II) NVIDIA(GPU-0): Display (ViewSonic VX2250 SERIES (DFP-0)) does not support
[   130.646] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[   130.649] (II) NVIDIA(0): NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)
[   130.649] (--) NVIDIA(0): Memory: 1048576 kBytes
[   130.649] (--) NVIDIA(0): VideoBIOS: 62.94.29.00.40
[   130.649] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[   130.652] (--) NVIDIA(0): Valid display device(s) on GeForce 9400 GT at PCI:1:0:0
[   130.652] (--) NVIDIA(0):     CRT-0
[   130.652] (--) NVIDIA(0):     CRT-1
[   130.652] (--) NVIDIA(0):     TV-0
[   130.652] (--) NVIDIA(0):     ViewSonic VX2250 SERIES (DFP-0) (boot, connected)
[   130.652] (--) NVIDIA(0):     DFP-1
[   130.652] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[   130.652] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[   130.652] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock
[   130.652] (--) NVIDIA(0): ViewSonic VX2250 SERIES (DFP-0): 330.0 MHz maximum pixel clock
[   130.652] (--) NVIDIA(0): ViewSonic VX2250 SERIES (DFP-0): Internal Dual Link TMDS
[   130.652] (--) NVIDIA(0): DFP-1: 330.0 MHz maximum pixel clock
[   130.652] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[   130.652] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[   130.652] (**) NVIDIA(0):     device ViewSonic VX2250 SERIES (DFP-0) (Using EDID
[   130.652] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[   130.655] (==) NVIDIA(0):
[   130.655] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[   130.655] (==) NVIDIA(0):     will be used as the requested mode.
[   130.655] (==) NVIDIA(0):
[   130.655] (II) NVIDIA(0): Validated MetaModes:
[   130.655] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select{}"
[   130.655] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[   130.683] (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
[   130.683] (--) NVIDIA(0):     option
[   130.683] (--) Depth 24 pixmap format is 32 bpp
[   130.683] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[   130.686] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   130.686] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   130.686] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   130.686] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   130.686] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   130.686] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   130.686] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   130.686] (II) NVIDIA(0):     Config Options in the README.
[   130.689] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select{}"
[   130.725] Loading extension NV-GLX
[   130.752] (==) NVIDIA(0): Disabling shared memory pixmaps
[   130.752] (==) NVIDIA(0): Backing store disabled
[   130.752] (==) NVIDIA(0): Silken mouse enabled
[   130.753] (==) NVIDIA(0): DPMS enabled
[   130.753] Loading extension NV-CONTROL
[   130.753] Loading extension XINERAMA
[   130.753] (II) Loading sub module "dri2"
[   130.753] (II) LoadModule: "dri2"
[   130.753] (II) Module "dri2" already built-in
[   130.753] (II) NVIDIA(0): [DRI2] Setup complete
[   130.753] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   130.753] (--) RandR disabled
[   130.760] (II) Initializing extension GLX
[   130.806] (II) config/udev: Adding drm device (/dev/dri/card0)
[   130.806] (II) xfree86: Adding drm device (/dev/dri/card0)
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5526

PostPosted: Tue Oct 29, 2013 10:40 pm    Post subject: Reply with quote

Assuming it's the complete log (xf86-input-keyboard and xf86-input-mouse should be meaningless, BTW), what does 'udevadm info' print about your input nodes (specifically those corresponding to your mouse/keyboard) ?
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 4646
Location: Saint Amant, Acadiana

PostPosted: Tue Oct 29, 2013 10:49 pm    Post subject: Reply with quote

This is hardly the complete log, input initialization part is missing - and that's the relevant part.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Tue Oct 29, 2013 11:17 pm    Post subject: Reply with quote

I copy/pasted what came up i'll try again
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 4646
Location: Saint Amant, Acadiana

PostPosted: Tue Oct 29, 2013 11:30 pm    Post subject: Reply with quote

Please pastebin it, forum software does not allow unlimited post lengths.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Wed Oct 30, 2013 5:56 am    Post subject: Reply with quote

Here is a pastebin link to my xorrg.log file http://pastebin.com/ctQiDcWS as you can see it looks the same

Last edited by <3 on Wed Oct 30, 2013 10:02 am; edited 1 time in total
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Wed Oct 30, 2013 5:57 am    Post subject: Reply with quote

VoidMage wrote:
Assuming it's the complete log (xf86-input-keyboard and xf86-input-mouse should be meaningless, BTW)


Should I uninstall those two then?
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Wed Oct 30, 2013 6:04 am    Post subject: Reply with quote

voidmage what is the exact syntax that I should tpye because "udevadm info" is giving a syntax error
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5526

PostPosted: Wed Oct 30, 2013 11:47 am    Post subject: Reply with quote

:roll: Well, you know, there's 'man udevadm' or even 'udevadm info --help', but with recent udev you can simply pass the full path to the node (and this has been noted in about every other thread about udev/input problems).
Back to top
View user's profile Send private message
bidibule
n00b
n00b


Joined: 02 Apr 2006
Posts: 20

PostPosted: Wed Oct 30, 2013 4:48 pm    Post subject: Reply with quote

Hello,

You should only use evdev, and remove xf86-input-keyboard and xf86-input-mouse

Update your INPUT_DEVICES variable in /etc/make.conf:

Code:
INPUT_DEVICES="evdev"


after that, you need to rebuild xorg-drivers. If you need to specify a keyboard layout, don't forget to update you /etc/X11/xorg.conf to use evdev :

Code:

Section "InputClass"
        Identifier  "keyboard-all"
        Driver      "evdev"
        Option      "XkbLayout" "us"
        Option      "XkbOptions" "terminate:ctrl_alt_bksp"
        MatchIsKeyboard "on"
EndSection


Hope this helps
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Wed Oct 30, 2013 9:26 pm    Post subject: Reply with quote

Thank you bidibule, I forgot to mention that I already tried that but I tryed it again after your post and still It's not working.

I found someone else with a similar problem http://forums.gentoo.org/viewtopic-t-973896-highlight-.html which is leading me to believe this could be some type on rare bug rather than user error.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5526

PostPosted: Thu Oct 31, 2013 5:16 am    Post subject: Reply with quote

:sigh: note that that thread talks about a virtual machine.
I'm asking about the info about the input nodes, as this looks more like xsever not detecting devices due to them being incorrectly tagged by udev.
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Fri Nov 01, 2013 10:04 am    Post subject: Reply with quote

I know that was about a VM but I figure the two could be related.

VoidMage wrote:
:roll: Well, you know, there's 'man udevadm' or even 'udevadm info --help', but with recent udev you can simply pass the full path to the node (and this has been noted in about every other thread about udev/input problems).

Can you just tell me what to do, I don't know WTF the output of udevadm info --help means. and please stop with the attitude.


Last edited by <3 on Mon Nov 04, 2013 8:30 pm; edited 1 time in total
Back to top
View user's profile Send private message
i92guboj
Moderator
Moderator


Joined: 30 Nov 2004
Posts: 9836
Location: Córdoba (Spain)

PostPosted: Fri Nov 01, 2013 10:38 am    Post subject: Reply with quote

There's definitely something going on with your logs, or else, a strange problem in your installation.

That can't possibly be the whole log, neither of them is complete. Where dri leaves, your graphics driver should init a lot more things, aiglx is not present either. So, not even the whole graphic stack log is being shown, and nothing at all about input devices, which is what we, in this thread, care about.

So, please, open your log with nano or your preferred editor, and double check that what you are pasting here is the whole log. Unless something very strange is happening in there, you should see a lot more info than what you are posting here.

It will be very difficult to help you otherwise, since we are shooting to a fly blindly.

Also, and regarding the post from some people above, note that, unless you are using a binary driver or a very particular configuration configuration you shouldn't be using an xorg.conf file at all. And, if you need to set the language or something, you can do so in /etc/X11/xorg.conf.d/30-keyboard.conf, /etc/X11/xorg.conf.d/40-touchpad.conf, etc.

There shouldn't be any harm in having evdev along with keyboard and mouse installed either.

I assume your system is up to date and you are not using overlays for X11, udev or something like that.

postdata: if the problem with the logs was that the log is too long (not the case, I assure you) then the post would have a broken layout, due to the missing final code tag which would also be stripped.
_________________
Gentoo Handbook | My website
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Fri Nov 01, 2013 11:17 am    Post subject: Reply with quote

thank you, I didn't make an xorg.conf file maybe the nvidia xconfig program did but I didn't. I don't use any language other than english. I will try removing the xorg.conf file when I get back in front of the computer if their is one.
Back to top
View user's profile Send private message
i92guboj
Moderator
Moderator


Joined: 30 Nov 2004
Posts: 9836
Location: Córdoba (Spain)

PostPosted: Fri Nov 01, 2013 11:25 am    Post subject: Reply with quote

<3 wrote:
thank you, I didn't make an xorg.conf file maybe the nvidia xconfig program did but I didn't. I don't use any language other than english. I will try removing the xorg.conf file when I get back in front of the computer if their is one.


If it was the nvidia config tool which put it there then you should probably keep it. But post it here so we can see if there's something wrong with it
_________________
Gentoo Handbook | My website
Back to top
View user's profile Send private message
i92guboj
Moderator
Moderator


Joined: 30 Nov 2004
Posts: 9836
Location: Córdoba (Spain)

PostPosted: Fri Nov 01, 2013 11:26 am    Post subject: Reply with quote

<3 wrote:
thank you, I didn't make an xorg.conf file maybe the nvidia xconfig program did but I didn't. I don't use any language other than english. I will try removing the xorg.conf file when I get back in front of the computer if their is one.


If it was the nvidia config tool which put it there then you should probably keep it. But post it here so we can see if there's something wrong with it
_________________
Gentoo Handbook | My website
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 4646
Location: Saint Amant, Acadiana

PostPosted: Fri Nov 01, 2013 2:15 pm    Post subject: Reply with quote

All configuration tools create bloated xorg.conf, all you need is a four-liner, without it nvidia driver won't load.

Code:
Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
EndSection

_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Fri Nov 01, 2013 3:41 pm    Post subject: Reply with quote

after reviewing this thread I did notice something weird from the xorg.log file
Code:
[   129.119] Kernel command line: BOOT_IMAGE=/kernel-3.10.7-gentoo-r1 root=/dev/sdd1 ro
I've been having odd problems and now I am wondering if this has something to do with it. And even if this is related to this problem. Am I crazy or shouldn't the / not be mounted as read-only? I don't have it mounted as ro in the fstab file.
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 4646
Location: Saint Amant, Acadiana

PostPosted: Sat Nov 02, 2013 2:09 am    Post subject: Reply with quote

Can you please use wgetpaste to pastebin the Xorg log? Not sure what is going on there, but it definitely looks like your log is incomplete.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Sun Nov 03, 2013 6:50 am    Post subject: Reply with quote

Since you guys don't seem to believe me when I say that is the entire log here is the wgetpastse output :lol:

http://bpaste.net/show/146282/. I'm starting to think there is some bug going on here.
Back to top
View user's profile Send private message
<3
l33t
l33t


Joined: 21 Oct 2004
Posts: 737

PostPosted: Mon Nov 04, 2013 8:27 pm    Post subject: Reply with quote

No one has any other ideas on how I can get this thing working?
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5526

PostPosted: Mon Nov 04, 2013 10:02 pm    Post subject: Reply with quote

<3 wrote:
No one has any other ideas on how I can get this thing working?

Well, seems I could have had an idea what could be wrong (or at least where things could have gone wrong), but you were not interested in checking that angle.
You're the one, who's sitting at your machine, after all.

Though since then, there were a few interesting posts about nvidia drivers misbehaving with some kernel versions (regarding signal handlers), which might be worth checking too.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum