[05:36] RAOF: heh, indeed [10:06] merged -wacom 0.13 in git [10:20] ..which doesn't build [10:20] ../../test/fake-symbols.c:467:16: error: redefinition of 'struct _InputOption' [10:20] /usr/include/xorg/input.h:226:16: note: originally defined here [10:20] ../../test/fake-symbols.c:471:3: error: conflicting types for 'InputOption' [10:20] /usr/include/xorg/input.h:230:3: note: previous declaration of 'InputOption' was here [10:22] ahah, need to add more stuff to the buildfix patch [10:25] yep, worked [10:37] uploaded -wacom to canonical/x-staging === yofel_ is now known as yofel [13:55] I'm having issue with a machine that X won't show on the screen (monitor is going to sleep) sometime, the only way to ""fix"" it is to reboot until it works. [13:56] i'm on lucid 10.04 fully updated, i have those message in dmesg : http://paste.ubuntu.com/824176/ [13:57] the one on top doesn't work and the one on the bottom works. [13:57] When i do xrandr, on both machine by ssh, both seems to be configured correctly. [14:44] mgariepy: try a newer kernel, you have plenty to choose from [14:44] linux-image-generic-lts-backport-* [15:13] tjaalton, i tried oneiric one and it didn't fix the issue. [15:14] then try 3.2 from the kernel mainline ppa [15:14] do you have to run 10.04 btw? [15:16] tjaalton, yes i do [15:16] sorry to hear :) [15:21] tjaalton, this kernel ? http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/ [15:21] 3.2.2? [15:25] yes [15:25] ok [15:31] tjaalton, the machine was working fine on karmic [15:31] which chip is it? [15:32] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) [15:32] what i find weird is that it boots a RO filesystem and sometimes it works but not other. [15:32] maybe best to file a bug upstream if 3.2 doesn't work [15:33] hm? [15:33] stock lucid or 3.2? [15:33] stock lucid [15:34] X starts with the right resolution and all be the monitor goes to sleep [15:34] ok then. might test karmic to see if it still works, and if not it's your hw failing [15:34] i got a lot of machine that does that. [15:37] so you're on #intel-gfx, tried asking there, or better yet, filed a bug upstream? [15:37] might be KMS that does something weird? [15:37] it's all it has [15:37] no ums for intel [15:38] #intel-gfx didn't answer yesterday [15:39] try a daily livecd? [18:29] tjaalton, linux-image-generic-lts-backport-natty seems to do the trick [18:29] * apw has just updated a nvidia box with a GeForce GTX 580 (GF110) in it, and its hanging at the login screen with PFIFO: read fault, ringing any bells ? [18:29] (and indeed any suggestions?) [18:30] (and update to precise) [18:36] hi apw, [18:36] not ringing any bells for me. tried removing and reinstalling nvidia? [18:37] apw, there've been some problems with people who had installed nvidia-173 instead of nvidia; I might doublecheck that. (jockey-text should reveal it) [18:38] hello, some time around last week in Precise, the scroll area of my trackpad went a little crazy [18:39] bryce, will do thanks [18:39] if i don't use the scroll area for a while, the next time i use it, the acceleration is extreme [18:39] and i'll scroll half a page at a time [18:40] after the first touch, then scrolling goes back to "normal" [18:40] bryce, so the only nvidia i have is nvidia-common, is that right or am i missing something [18:41] that is right [18:41] wait, no [18:41] you should also have nvidia-current installed [18:41] (I think you can do it manually, but it's better to do via jockey if possible) [18:42] apw, does jockey indicate that nvidia is installed? If so, may need to forcibly uninstall more nvidia bits. If not, then try reinstalling [18:44] mgariepy: nice. but you said the oneiric one didn't work, meaning it has regressed again since natty? [18:44] bryce, i actually have a held xserver-xorg-video-all [18:44] depending on a bunch of -xxx h/w specific drivers [18:45] tjaalton, maybe, i need to do more testing. [18:45] apw, aha [18:45] i'll skip oneiric tho, i'll go with precise since i won't work with oneiric.. [18:46] apw, prior to this last update had you updated the system within the last week or so? might be you're just still hung up on the transition [18:46] bryce, nope this was very old, i booted it and updated it [18:46] apw, uninstall those h/w specific drivers and then make the update complete [18:46] mgariepy: good plan [18:47] apw, lately there've been a handful of dropped drivers; theoretically they should have automatically been purged [18:47] presumably they weren't for some reason in your case (I've run into this myself in the past) [18:48] bryce, yeah, i presume this is something missing on the new packages to make it occur if you have a release cd level version [18:48] * bryce nods [18:48] bryce, i will also note that nothing told me this had occured [18:48] apw, it's hardly likely worth your time to debug it; if it looks like it's going to be a hassle I would just backup user files and do a fresh install [18:49] apw, that's ungood [18:50] bryce, is there any way to tell which is the broke -video- thats installed [18:50] apw, with these installation problems, usually the apt guys want to have a reproducible test case. If you think you can reconstruct it, it may be worth reporting [18:50] apw, hmm [18:51] apw, not sure, other than individually removing them until you've purged enough [18:51] bryce, i suspect a scratch to the oneiric release cd and then an update will repro it [18:51] bryce, but will prove that this is the issue first [18:51] apw, are you attempting apt-get install -f ? [18:51] install -f is happy [18:51] it just says 13 not upgraded [18:52] bryce, getting the errors when i attempt to install ubuntu-desktop^ [18:52] apw, if it can be repro'd from a stock oneiric release, that would be double bad. However, I would expect we'd have other reports in that case (but possibly you're just the first?) [18:52] most of us update more regularly, this being unpdated for months is unusual [18:53] bryce, so basically uninstall *-video-* and then reinstall ubuntu-desktop^ [18:54] apw, yep [18:54] apw: do you get plymouth/kms? [18:54] ie. does nouveau work [18:54] tjaalton, yeah he gets to the login screen [18:55] "PFIFO: read fault" [18:55] console? [18:56] nevermind [18:56] tjaalton, yep [18:57] bryce, but till i have X all at the same level i am ignorign the error [19:05] bryce, ok didn't improve anything any [19:08] apw, ok at this point I need logs and such [19:08] apw, either do up a ubuntu-bug xorg or pastebin the usual stuff [19:09] the PFIFO: read fault error message appears to be a nouveau-specific message [19:10] so presumably you have two problems, a) nouveau is busted, and b) nvidia isn't running properly [19:13] bryce, i am not expecting to have binary drivers on here [19:13] bryce, should i install them ? [19:14] apw, yes [19:14] apw, well let me ask - you said "this is an nvidia box" initially, by which I mean your intention is to have binary drivers installed. [19:15] if that's not the case, then I've been woefully misleading you [19:15] bryce, no my intenton is to use the graphical interface... i've not used nvidia drivers before on it though [19:15] bryce, jockey-text offers nothing anyhow [19:16] ah, ok nouveau then [19:17] apw, can you pastebin your Xorg.0.log or file a bug report? [19:17] bryce, whats the incantation for a nvidia bug report [19:17] ubuntu-bug xorg [19:18] bryce, http://paste.ubuntu.com/825488/ [19:18] (there is a separate command for making nvidia binary driver bug reports, but that's not used for nouveau problems) [19:18] gpu lockup on nouveau [19:19] where did you see the PFIFO error? dmesg? pastebin that too [19:21] [ 100.328] [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. [19:21] [ 100.328] [mi] mieq is *NOT* the cause. It is a victim. [19:21] heh [19:21] bryce, http://paste.ubuntu.com/825492/ === ashams_ is now known as ashams [20:24] apw: you have the drm-next mainline builds, try one ;) [22:07] evening! [22:17] tjaalton, heh thanks [22:55] apw, I dug through the kernel code and drm-next changelogs but didn't spot anything that'd give hope. I think you need to go to ben skeggs, but testing drm-next first is not a bad idea. [22:55] apw, I've forwarded your bug to fdo, in case you want to ref it when talking with him [22:56] I'm not fully up with the context, but are we building nouveau's next tree, too? There's generally a bunch of stuff on there that's not in any of the drm-* kernels. [22:57] mesa 8 from ppa:canonical-x/x-staging might be worth trying too (but it will be a PITA to remove if you're on x64), it could very well be mesa 7.11 causing it :) [22:58] RAOF, we are not. git.freedesktop.org has been down so I couldn't review it [22:58] Yay infrastructure! [22:59] Sarvatt, however the freeze occurs on the login screen. guessing it to be occurring before the fun 3d stuff kicks in [23:00] oh, i was equating 100 seconds after boot to possibly being when unity started [23:01] I assume it freezes before he types login [23:03] Hm, nvc8 [23:04] nvc0 [23:04] IIRC, that's a sufficiently-different nvcX, and there's not been much testing of it. [23:04] It's nvc0 generation, you need to read the specific chip from 0x0c8000a1 (ie: c8) [23:05] RAOF, yes I know [23:06] I think it's possible that the difference between 11.10 and Precise is that there wasn't any acceleration for nvc0 class chips in 11.10? [23:09] thats true, yep [23:09] was no microcode for it until 3.1 or 3.2