[04:00] hi it looks like the 195 nvidia driver causes sound problems on my 8200 igp, will the 260 driver help with this issue? [11:08] hi, audio doesnt work with either 195 or 260 on my 8200 based mainboard, what else can I try? === yofel_ is now known as yofel === udslogger is now known as transitlogger [18:44] all: i'm having trouble with ubuntu 10.10, X, an NVIDIA 9500GT, and the nvidia driver (nvidia_drv.so). [18:45] http://pastebin.com/C3s2KnmY [18:45] ^- X.org log. [18:48] ayan: it tells you to check the kernel log [18:49] i.e. dmesg [18:51] virtuald, ya -- doesn't reveal anything. [18:51] atleast nothing obvious to me. [18:52] so you don't have the kernel module available [18:53] it doesn't sayt eh module doesn't exist, so it's there [18:57] bjsnider: are you sure it would mention that? grepping the strings from the module doesn't give any apparent matches for that situation [18:58] would lsmod show it? [18:58] if it got loaded [18:59] if he was trying to load a nonexistent module it would say "module doesn't exist" and then try to load something else, such as nouveau [18:59] ayan, what happens after the nvidia driver fails? does it continue to the desktop? [18:59] no, that would happen if the x driver wasn't there [19:00] bjsnider, no -- it does not continue to the desktop. [19:00] though the fallbacks don't work with nvidia/fglrx aiui [19:00] ayan, when did this start happening? [19:01] a bit before uds. [19:01] i didn't have time to look into it. [19:02] maybe a week before uds. [19:02] ayan: something broken? got the machine up at plumbers? [19:02] get to a command prompt and type dkms status [19:02] Sarvatt: i will not be at plumbers. [19:03] Sarvatt: it is my desktop. [19:27] * bryceh waves [19:30] heyo bryceh! [19:30] thanks for the assorted medicines, they were a big help :) [19:30] Sarvatt, sure thing [19:31] I'm just fairly stunned I didn't need them myself this trip [19:31] especially when your roommate was sick from the start! [19:31] and my wife leading up to it... [19:33] how are you feeling now? getting recovered? [19:34] Sarvatt, well either your germ sanitation work paid off, or you were just getting caught up on UDS germs ;-) [19:34] just a nasty cough left, feel fine. I'm not regretting packing just for boston now with how cold it is up here :) the hotel is crap compared to orlando, funny because it costs about 3x more [19:35] yeah that orlando hotel was swank... don't get your expectations set by that, most places we've gone have not been nearly that nice === Bernardo is now known as Bernardo|Away === Bernardo|Away is now known as Bernardo [22:06] why does jockey-text not display any drivers but jockey-gtk does? (although jockey-gtk fails to install it) [22:12] 2010-10-31 23:11:14,075 ERROR: XorgDriverHandler.enable(): package or module not installed, aborting [22:27] knittl: did you install from the ati website at some point and not uninstall? [22:27] it's an nvidia-card, i don't think so [22:29] knittl: no headers for your current kernel maybe? [22:29] knittl, is nvidia-common installed? [22:29] ahh sorry, nevermind :) it should say somewhere else in that jockey log though, the aborting message happens so much [22:30] bjsnider: yes [22:30] Sarvatt: dunno. $ uname -a [22:30] Linux kbook 2.6.35-23-generic #36-Ubuntu SMP Tue Oct 26 17:03:18 UTC 2010 i686 GNU/Linux [22:30] knittl, what nvidia chip? [22:31] $ lspci|grep nVidia [22:31] 01:00.0 VGA compatible controller: nVidia Corporation G86M [Quadro FX 360M] (rev a1) [22:31] what happens if you try installing nvidia-current? [22:31] that works [22:32] so it's only a jockey issue [22:32] seems so [22:33] what about nvidia-current-modaiases? [22:33] is it installed? [22:34] $ apt-cache policy nvidia-current-modaliases [22:34] nvidia-current-modaliases: Installed: 260.19.06-0ubuntu1 [22:36] unless the log is more specific about what is missing i don't see how it can be easily troubleshot [22:37] hm. it looks like the driver gets installed, but then it fails somehow and bails out [22:37] but i need to go to bed [22:37] that error message is slightly more helpful than a typical microsoft one, such as "error 09842098365", but unless it's identifying the specific missing package...