00:10njsg: imirkin_: I'll look at this again tomorrow and paste a full dmesg, but here's what happens when I set 1024x768i: http://dpaste.com/2KJFF46.txt
00:11imirkin_: Modeline 66:""
00:11imirkin_: thanks, world
00:11imirkin_: real helpful description there =/
00:11njsg: what should have been there?
00:11imirkin_: not the empty string :)
00:11imirkin_: not your fault
00:12imirkin_: so to confirm - you were switching from 800x600 into 1024x768i - yes?
00:12njsg: I think I was in 800x600, and I'm sure I was switching to 1024x768i
00:12imirkin_: it looks like you were.
00:13imirkin_: i'll look at some code later on
00:13imirkin_: this is all well beyond what i generally "know" about
00:13njsg: Is there any reason why Modeline 66 would be associated with different modes?
00:14imirkin_: 66 is 800x600
00:14imirkin_: 68 is 1024x768i
00:14imirkin_: it's hard to tell just by looking at it, but the info is all there.
00:15njsg: I mean, http://dpaste.com/03BP508.txt
00:15imirkin_: it'd really be helpful if you just included the whole dmesg
00:15imirkin_: it's definitely weird that it changes.
00:16imirkin_: might be getting deleted/re-added
00:16imirkin_: probably ok to grep for nouveau|drm
00:17imirkin_: if you're worried about extraneous info being revealed
00:31imirkin_: njsg: an important point is that things like the literal clock rate aren't actually part of the modeline - only the pixclk is, which is set correctly
00:31imirkin_: the rest of the values are derived directly from those values
00:32njsg: nouveau\|drm messages: http://dpaste.com/3891BVR.txt
00:36njsg: I think I tried to understand modelines a long time ago but either I didn't look at it or I forgot how it works.
00:45karolherbst: HdkR: the PSU came with a US power plug of course :D
00:45HdkR: Oh, hah, yea of coursei t would have
00:45imirkin_: njsg: fwiw i just glanced at the code that handles interlacing, and it appears identical
00:45HdkR: Hopefully you have a million PSU power cables like I do :P
00:45karolherbst: HdkR: but I still have one EU one which I can use
00:45karolherbst: nope, just one
00:46karolherbst: ohh, actually two
00:46karolherbst: but the other one is in use
00:46imirkin_: njsg: oh actually, i think i see what might be a difference.
00:46karolherbst: HdkR: I also have my kepler laptop I could use for the CI stuff as well... mhhh
00:47HdkR: Oh fun, laptops in CI
00:47HdkR: Nothing could go wrong
00:48imirkin_: njsg: ok yeah, i think i see what's going on.
00:48imirkin_: it's a mismatch between whether vdisplay is in frame-rate or field-rate
00:49HdkR: karolherbst: Make sure to double check hertz and voltage for your region on the PSU? No idea what you have there
00:49imirkin_: er wait. no. vdisplay is something else.
00:49imirkin_: that's the width.
00:50imirkin_: er height. wtvr.
00:53karolherbst: HdkR: ehh.. 220V
00:53HdkR: Make sure to toggle the switch on the PSU then :P
00:53karolherbst: no need
00:53karolherbst: most hardware these days can do 100-220V
00:54karolherbst: anyway, mhhh, without the case I can't easily turn it on.. well, I could bridge the pins
00:54HdkR: Yea, nice when the PSUs automatically handle it for you
00:55HdkR: Some of the lower end ones still have a hard hardware toggle
00:55karolherbst: anyway, the stock fan couldn't be any bigger, otherwise it would press against the RAM :D
00:55HdkR: Woo for motherboard vendors being required to follow the "keep out zone" guidance
00:56karolherbst: I think the assume you have a custom fan anyway
00:57HdkR: Yea, price range for this kit is getting to the region where people move away from the box cooler
00:58karolherbst: mhh, I still need more stuff, like a power plug with integrated fuse and stuff.. but that's for later
00:58karolherbst: maybe even a power meter for fun :D
01:00HdkR:adds to the list
01:03karolherbst: ufff, oh wait. PoE is 48V
01:04karolherbst: I need something like this: https://www.aliexpress.com/item/32677165482.html just different
01:04HdkR: Which PoE is Tegra?
01:05karolherbst: but I'd like to have a poe splitter to ethernet + jack
01:05karolherbst: USB only accepts 2A on the nano, the power jack does 4A
01:05karolherbst: there are pins though
01:05HdkR: Oh, 5v is usually for those small injectors
01:06HdkR: not very standard in the switch space, they really want higher voltage so you're pushing less amps on the wire
01:09HdkR: They have splitters that ingest 48v and output 5v
01:09HdkR: That's nice
01:09karolherbst: something like that
01:10njsg: imirkin_: I'll get some sleep now, let me know if there's anything I should check tomorrow
01:11HdkR: karolherbst: Yea, I see TP link has one of those as well
01:12HdkR: Allows 12v,9v, and 5v
01:13karolherbst: but the nano has a real J38 PoE pin thing, just for 5V sadly
01:13karolherbst: maybe I can just buy a 48V -> 5V converter and be done with it
01:13karolherbst: but I still need to split it though
01:15karolherbst: but anyway, I think a splitter might be good enough
01:16HdkR: Sounds reasonable to do a splitter+converter box
01:17HdkR: Would be nice to have a direct 48v POE -> 5v POE inline converter but I doubt anyone makes those
01:19karolherbst: I just need a reliable way to power cycle the jetson
01:19HdkR: I know of ethernet controlled relay switches
01:19HdkR: or USB controller relay if you want that
01:20HdkR: Makes sense if there is a header for power or reset
01:21karolherbst: there actually is a j40 header
01:21karolherbst: but PoE has the advantage of not needing an additonal power supply
01:22HdkR: https://www.ebay.com/itm/MICRO-USB-5V-2-Channel-Relay-Module-USB-Control-Relay-Module-serial-port/222062841371 I use this for controller my TR system when it hangs
01:22HdkR: for controlling*
01:22karolherbst: but then I rely on USB on the controller... and USB cable length and stuff
01:23HdkR: They have ethernet controlled ones, just need to find it
01:23karolherbst: then I need two ports per device
01:23karolherbst: the only thing which is a bit annoying to deal with are force resetting the other desktop machines
01:24karolherbst: huh, 8 in one
01:24HdkR: desktop machines you can just use the front panel headers :P
01:24karolherbst: that's a cable mess
01:25karolherbst: HdkR: but I need soemthing to still trigger the resets and stuff
01:26karolherbst: but I think with a proper hangcheck and watchdog thingy that should work reliable enough
01:26karolherbst: I guess I will have to experiment a bit to see what works properly and what not
01:26HdkR: ooh, people are selling 16 channel ones as well :D
01:26karolherbst: best case, machines never die :p
01:27HdkR: https://www.ebay.com/itm/Ethernet-Control-Module-Lan-Wan-Network-Web-Server-RJ45-Port-16-Channel-Rel-C6E3/113917978781 Love it
01:28karolherbst: the cables
01:28karolherbst: HdkR: imagine wiring up 16 desktops with that
01:28HdkR: Nightmare fuel
02:36imirkin: njsg: the reason the 1024 modes get pruned out originally is the video=800x600 thing. makes sense.
10:16njsg: imirkin: yes, and I guess the modeline numbers can get reused (explaining why would it get 800x600 in 66)
17:32imirkin_: njsg: so ... i spent a bit of time perusing code, it doesn't seem like there are any differences directly linked to interlacing
17:32imirkin_: HOWEVER the PLL calculation stuff is _entirely_ different
17:32imirkin_: or at least not obviously the same
18:59karolherbst: HdkR: I've got the case now as well :) I guess next step is to configure Lava and see how I can add the tegra as a runner :)
18:59HdkR: woop woop
22:17njsg: imirkin_: how specific is the code that might cause the issue? Is this something that'd affect a wide range of cards?
22:19imirkin_: the pll calc stuff is different for all GPUs
22:19njsg: I suppose the next step would be learning enough about GPU drivers to look at the code and try to figure out what might need to be tweaked. Any chance there's actual documentation for this GPU? (Probably not, but I guess it's worth asking...)
22:22njsg:is not surprised
22:23njsg: I still had to ask, I could have been wrong :-)
22:23imirkin_: there's the -nv code
22:23HdkR: Welcome to GPU driver development? :P
22:23imirkin_: there's also a "nvidiafb" driver in the kernel
22:23imirkin_: which is a fbdev driver
22:23imirkin_: which is also based on the -nv code
22:46imirkin_: oh - there's also a haiku driver or something crazy like that
22:46imirkin_: all slightly different
23:10njsg: At least there's plenty of code to read, should help understanding it
23:11imirkin_: uh huh
23:12imirkin_: and i'm not even saying that the PLL logic is wrong
23:12imirkin_: i'm just saying it's different :)