11:16Krutonium: Okay so I have a MacBook Pro 17" 3,1. It has an 8600M GT, which is NV50 on the feature matrix. I cannot get it to init the GPU, it cannot find the vBIOS whatsoever. I have tried all of of `NvBios` options from the website. https://i.imgur.com/gWa6wTu.png . I have tried Kernels 4.13 5.14 and 6.0. Right now I can only get a GUI with `nomodeset`. Anyone have any information or ideas that may help?
11:17Krutonium: (And when I say GUI I mean even TTY's)
11:21Krutonium: Okay, struggling with IRC, you guys can see this?
11:22Krutonium: Okay so I have a MacBook Pro 17" 3,1. It has an 8600M GT, which is NV50 on the feature matrix. I cannot get it to init the GPU, it cannot find the vBIOS whatsoever. I have tried all of of `NvBios` options from the website. https://i.imgur.com/gWa6wTu.png . I have tried Kernels 4.13 5.14 and 6.0. Right now I can only get a GUI with `nomodeset`. Anyone have any information or ideas that may help?
14:55RSpliet: Krutonium: is this still PowerPC?
14:57RSpliet: I vaguely remember that old PPC Macs had the VBIOS in OpenFirmware. nouveau.config=NvBios=OpenFirmware should be the option of choice.
14:59RSpliet: But I've never tried that myself, so I don't know about the caveats
15:02RSpliet: Ah no these are Intel ones...
15:04RSpliet: Krutonium: https://wiki.archlinux.org/title/Talk:Mac There's some useful info about early MacBooks on there. Extract the VBIOS through vbtracetool when booting in BIOS mode, then drop it in /lib/firmware and have the file loaded on boot.
15:05RSpliet: Ignore my openfirmware notes, those are PPC-specific AFAIK :-)
15:14Krutonium: I guess now I need to figure out how to boot in BIOS on here lol
15:15Krutonium: Thanks a ton though!
16:20KungFuJesus: karolherbst: tomorrow morning I'm about to find out if that #if UTIL_ARCH_BIG_ENDIAN in vbo validation is _actually_ endianness specific or if there's a bug that plagues all ISAs. I think it's the latter...that workaround actually sets vbo_fifo to ~0. The "prevalidate" function does too, if "push_hint" is set to 1 (which it is in this case), but, that code only ever executes if the resource isn't
16:20KungFuJesus: already mapped by the GPU
16:23KungFuJesus: But also there's something screwy about VBO handling in general. Randomly assets will be missing in a game that's using VBOs versus a version that uses legacy GL functions if I enable the modifications to allow it to run at a full 60fps instead of 30. Also when vsync is enabled I seem to get abysmal framerates, suggesting something weird is happening somewhere around that fencing
16:28KungFuJesus: the legacy version is using glDrawArrays. The missing assets seem to be almost entirely textuers
16:28KungFuJesus: textures*
16:28KungFuJesus: from what I can tell, draw_arrays uses vbos in nv30 now too, so maybe it suggests draw_arrays is doing something special compared to the user controlled vbos?
18:25KungFuJesus: Given that I can no longer trust the compiler, I will be relieved if I find the same class of issues on x86
18:27KungFuJesus: Now if I get different and weirder problems on x86, my grounding in reality will be shattered and utter confusion will haunt me