05:55 octet: Journaelctl -xe with Nvidia Turing 1660ti: Nouveau 0000:01:00.0: unknown chipset (168000a1) Nouveau: probe of 0000:01:00.0 failed with error -12
05:55 octet: I read that nouveau has Turing support as of kernel 5 which I am running, so I am curious why I get this error message and flashing cursor
10:12 karolherbst: octet: ohh, I guess there is no support for the 1660 ti yet
10:12 karolherbst: skeggsb: ?
17:31 letterrip: hi all, any suggestions on how to debug 'mouse pointer corruption'? The mouse pointer is displayed as a roughly 1 inch square of red on my screen instead of an arrow
17:31 letterrip: with the 'tip' apparently the upper left hand corner of the square
17:32 letterrip: the mouse displays normally with the VESA (nomodeset)
17:32 letterrip: so I suspect it might be nouveau related
17:39 diogenes_: letterrip, wayland?
17:39 letterrip: x11 I'm pretty sure
17:40 letterrip: whatever default is for disco
17:40 diogenes_: what if you change the size of the pointer and also the theme?
17:42 letterrip: i think the theme doesn't matter, I'm unaware of how to change the pointer size
17:43 letterrip: i'll see if i can change it in the xfce wm settings
17:44 diogenes_: yes there is setting to change pointer size and pointer theme in xfce settings
17:44 diogenes_: settings > mouse and touchpad > theme
17:45 letterrip: no change, tried all themes, all mouse pointers, and a variety of sizes
17:46 diogenes_: weird, never came across such a bug
17:46 diogenes_: btw
17:46 diogenes_: is compositor enabled?
17:46 letterrip: i'm a special snowflake bug.. fun
17:46 letterrip: nope compositor disabled
17:46 letterrip: it causes crashes if enabled
17:47 diogenes_: hmm, that's special case indeed XD
17:47 diogenes_: maybe you just need a newer kernel
17:47 letterrip: 5.0 kernel
17:48 letterrip: latest mesa
17:48 diogenes_: or it's too new
17:48 letterrip: (well not currently latest mesa, but with latest mesa also)
17:48 letterrip: have tried 4.x kernels
17:48 letterrip: i think this is present in old distros i've tried also
17:49 diogenes_: that;s why i like having the optimus systems so i run all the basic stuff with intel graphics and the heavy weight one with nouveau
17:50 letterrip: this has in an intel 945gm but it has same memory location and apparently isn't detected - might be disabled in bios?
17:50 letterrip: not sure
17:50 diogenes_: yess
17:50 diogenes_: look in bios
17:50 letterrip: the bios is extremely simple - no options for anything but boot order
17:50 diogenes_: there shold be the otion which graphics to use by default, onboard or discrete
17:50 letterrip: so would have to disasseble the bios and fiddle with bits
17:52 letterrip: not sure if i'm hardcore enough to try and do a custom rom :)
17:53 letterrip: er custom bios .. not rom
17:54 letterrip: i may be misunderstanding my dmesg
17:55 letterrip: is there a way to try and force it to use the 945gm as a kernel parameter and disable the noveau?
17:55 diogenes_: letterrip, lspci -nnk | grep VGA -A3
17:57 letterrip: https://pastebin.ubuntu.com/p/bbbWBTvRYV/
17:57 diogenes_: and: lsmod | grep i915
17:58 letterrip: empty
17:58 diogenes_: yeah, no intel onboard graphics
17:58 letterrip: ok
17:59 letterrip: so is 945gm something different then?
17:59 diogenes_: could be
17:59 diogenes_: we can try a trick to boost the performance though
17:59 diogenes_: and maybe it will have some positive impact
18:00 diogenes_: edit: /etc/default/grub
18:00 letterrip: ok
18:00 diogenes_: line: GRUB_CMDLINE_LINUX_DEFAULT="nouveau.config=NvClkMode=15...."
18:01 diogenes_: save, close, update-grub, reboot
18:01 letterrip: ok
18:01 letterrip: will give it a try
18:02 diogenes_: ok, now i need to go, if something positive improvement happens, hit me up later
18:02 letterrip: will do
18:02 letterrip: ttyl
18:02 diogenes_: also with this option, run: sensors to notice if your gpu doesn't get overheated
18:02 diogenes_: if it does then remove it
18:02 letterrip: ok
18:02 diogenes_:is offline
19:02 Hijiri: got a crash again, this is what the output of dmesg looks like https://pastebin.com/NZEXYk1a
19:04 Hijiri: it happened after playing a game for awhile
19:20 karolherbst: Hijiri: uff, essentially that means out of VRAM :/
19:32 Hijiri: it was a much shorter play than usual though, and only things else open were web browsers
19:32 Hijiri: could chromium consume all my vram?
19:33 Hijiri: the game itself is also pretty old and shouldn't be that demanding
19:33 karolherbst: might be
19:33 Hijiri: is it possible that VRAM might not be reclaimed from previous programs I had open
19:33 karolherbst: could also be that too many commands are submitted to the GPU
19:34 karolherbst: not quite sure which of the two issues that was
19:34 karolherbst: Hijiri: pretty low I think, normally all the memory should get released
19:34 Hijiri: I don't really feel like it's VRAM, since I've played minecraft for extended time without crashing
19:34 karolherbst: but we also don't really track the current VRAM usage
19:34 karolherbst: we should probably start doing that
19:34 Hijiri: which would use more VRAM probably
19:36 Hijiri: this game supports software rendering for some parts so I could turn that on and hope it doesn't crash
19:36 Hijiri: I've just played it without crashing for a long time since the last crash I reported (which had different error messages)
19:36 Hijiri: and that other crash went away I think when I stopped using the turn vsync off mesa env variable
19:38 Hijiri: forgot why I brought that up, it's because software rendering didn't prevent the other crash, but this crash seems different
19:43 Hijiri: so there isn't a way currently to check VRAM usage on nouveau?
19:44 karolherbst: no
19:44 karolherbst: sadly
19:44 Hijiri: rip