01:19jhol: extremely good news with those EVO docs
01:19jhol: I havn't done much with the TV stuff for a couple of months
01:19jhol: I might resume that work some time
01:44mlankhorst: ooh nice docs
01:45jhol: so would the normal procedure here be to import these into the rnndb?
01:45mlankhorst: yeah likely
01:48mlankhorst: that would make it possible to do decode evo stuff at least
01:49jhol: and do nouveau regs in the driver code and db get renamed to match the manufacturer names?
01:49skeggsb: i'll be using nvidia's class headers when i write atomic, yes
01:52jhol: but what about the pre-existing code?
01:52skeggsb: it won't exist anymore?
01:52skeggsb: by the time you convert to primary and cursor planes, and then atomic.. you've rewritten it
01:53jhol: oh I see
01:53jhol: n00b questions
04:33swiftgeek: anyone with tesla + LVDS output + dpi > 96 ?
09:42moben-: I tried reclocking my ddr3 NVA8 with v3.19-rc4 and it locked up the gpu. dmesg: http://dpaste.com/11QBH9M.txt
09:42moben-: Is that the expected result and/or should I produce more logs?
09:43moben-: '[0000:01:00.0] invalid/missing rammap entry' is when I downclocked before starting X, which appeared to work
09:43pmoreau: RSpliet: -^
09:44moben-: the lockup happened when going back to the default clock and (iirc) down again, while X was running
09:44pmoreau: moben-: Reclocking should work for NVA8+GDDR3
09:46pmoreau: You should fill a bug report and RSpliet will have a look at it
09:48moben-: okay, will do
10:04RSpliet: moben- yes please, file a bug report and attach both a full log (no grepping plox) and your VBIOS
10:14moben-: RSpliet: https://bugs.freedesktop.org/show_bug.cgi?id=88415
10:22moben-: RSpliet: feel free to poke me in case you need anything tested
10:52RSpliet: moben-: ah yes, I think I remember staring at your VBIOS
10:53RSpliet: it's a bit strange, because the mapping from "strap" to timings and parameters is non-regular
10:53RSpliet: skeggsb looked into that a while ago, but not sure if he completely figured it out
10:54RSpliet: (not at your case specifically, but in understanding that mapping better)
11:55pmoreau: Does anyone know what interrupt 0x04000000 means? I get it on my G96 when starting X and the MCP79 is the one driving the screen. (dmesg -> https://phabricator.pmoreau.org/P2)
12:25RSpliet: pmoreau: isn't that documented in envytools?
12:25RSpliet: not entirely sure which interrupt reg that is
12:25RSpliet: (phabricator? is that phabulous?)
12:26pmoreau: RSpliet: if lookup is correct, it is documented as UNK26 ;)
12:26RSpliet: then... I can only assume what Queens of the Stone Age told us years ago
12:26pmoreau: rather, iirc the PFIFO.INTR reg
12:26RSpliet: "no one knows"
12:27pmoreau: (and yes, it is phabulous :) )
12:28pmoreau: iirc, imirkin told me it could be related to PDISPLAY, maybe some conflic between PDISPLAY on the G96 and the one on MCP79, but it was a long time ago, so I'm probably mixing things
12:59moben-: RSpliet: I have no idea what that means, except for "my vbios is a special snowflake" :)
13:00RSpliet: moben-: very special indeed, it's yellow
13:00RSpliet: (don't eat it)
13:02moben-: I'll try not to. Would be hard anyway, the gpu seems to be the hardest part to get out of the laptop, after the motherboard.
17:00CptRageToaster_: hi, odd question here
17:00CptRageToaster_: I'm booting with an AMD card, and an NVideo both install physically
17:00CptRageToaster_: but I intended for this linux install to only use the AMD
17:01CptRageToaster_: dmesg is filled with chatter about how nouveau isn't happy, (I'll fetch a log)
17:01CptRageToaster_: What would I need to remove to stop these from occuring?
17:07moben-: CptRageToaster_: you should just be able to blacklist the nouveau module
17:07urjaman: blacklist the nouveau kernel module? or maybe nouveau.modeset=0 on the kernel command line to mostly disable it
17:07moben-: CptRageToaster_: create a .conf file in /etc/modprobe.d and add a line 'blacklist nouveau'
17:08CptRageToaster_: well... I was able to apt-get remove a couple of unused nvidea things
17:08CptRageToaster_: and didn't realize I needed to sudo update-initramfs -u
17:08CptRageToaster_: would I still need to blacklist the nouveau driver as well?
17:09CptRageToaster_: apt's libdrm-nouveau1a package is still installed
17:10moben-: the module will load regardless of what is installed, so blacklist it
17:10CptRageToaster_: will do
17:10CptRageToaster_: I'll give it a reboot, and we'll see how it goes :D
17:10moben-: you might have /etc/modprobe.conf instead of /etc/modprobe.d/, depending on how recent the distro is
17:11CptRageToaster_: I have a modprobe.d directory, full of .conf's
17:11CptRageToaster_: would I need to create a new <filename>.conf?
17:12moben-: you don't need to, but it's best to do it, so it won't be overwritten and you remember which one it is (could also add it to an existing one though)
17:12CptRageToaster_: there's already a modprobe.d/blacklist.conf
17:13CptRageToaster_: oh, but you're saying that it is automatically generated... and I should make my own so it isn't touched
17:14moben-: might be. shouldn't, but it depends on the distro and I don't know how ubuntu handles it
17:14CptRageToaster_: I would expect it to break later
17:15CptRageToaster_: I'll just make a new one here
17:16moben-: and you might have to rebuild the initramfs (if the nouveau module is in the initramfs, you need to rebuild it so that your blacklist is also included)
17:16CptRageToaster_: do I need to refresh anything
17:17moben-: though again, I don't know if the module is in the initramfs in ubuntu :)
17:17CptRageToaster_: well, a reboot may give us a clue :)
17:19CptRageToaster_: moben-: Tyvm
17:20CptRageToaster_: dmesg has a much higher percentage of useful information now!
17:22moben-: CptRageToaster_: np
19:34DYO_1: I'm looking for the solution to this:
19:37DYO_1: Debian 7, nouveau driver, DVI-I-1 reported by xrandr, black borders. I did http://nouveau.freedesktop.org/wiki/TroubleShooting/#index9h3 and http://nouveau.freedesktop.org/wiki/TroubleShooting/#index4h3 but it does not work right.
19:37DYO_1: Can someone help me?
19:40DYO_1: VGA compatible controller: NVIDIA Corporation nForce 220/420 NV11 [GeForce2 MX] (rev b1
20:25DYO_1: I'm looking for the solution to this: Debian 7, nouveau driver, DVI-I-1 reported by xrandr, black borders. I did http://nouveau.freedesktop.org/wiki/TroubleShooting/#index9h3 and http://nouveau.freedesktop.org/wiki/TroubleShooting/#index4h3 but it does not work right. Can someone help me? VGA compatible controller: NVIDIA Corporation nForce 220/420 NV11 [GeForce2 MX] (rev b1)
20:52DYO_1: I'm looking for the solution to this: Debian 7, nouveau driver, DVI-I-1 reported by xrandr, black borders. I did http://nouveau.freedesktop.org/wiki/TroubleShooting/#index9h3 and http://nouveau.freedesktop.org/wiki/TroubleShooting/#index4h3 but it does not work right. Can someone help me? VGA compatible controller: NVIDIA Corporation nForce 220/420 NV11 [GeForce2 MX] (rev b1)