oh, our libuuid only depends on libc, but that's because we made a system call to generate uuids, so they stay unique across zones without having to do special magic coordination between ngz's

since /var/sadm/system/uuid_state had different state in every zone before that

i think i managed to work around it (was trying to build something to go w/ a platform image

which uses libuuid

and the 36,000+ line autoconf generate makefile (yay!) was incorrectly trying to use bits on the build system

which is a bit older

but it was confusing gettign a versioning error from libvarpd when that shouldn't be anywhere near this thing

i think i managed to find the magic incantation to make it just look at the proto area libs

(that it by default tries to be fancy and hide everything it's building with just 'CC <file>' or 'CCLD <library>' wasn't helpful

Ugh, yeah, I hate Makefiles like that

alanc that's a nice change, and would address illumos 14571 too! (fenix)

BUG 14571: libuuid statefile woes (New)

↳ illumos.org/issues/14571

My new Z4 panics when I start X (independent of the NVIDIA graphics card):

> $C

fffffe00410466b0 vpanic()

fffffe0041046760 hat_devload+0x1f1(fffffe2ca0b0e3f8, fffffe2cba84f000, 1000, 9e, 403, 1)

fffffe00410467c0 gfxp_map_kernel_space+0xb8(9e000, 1000, 0)

fffffe2cb3f12ea0 _nv041482rm+0x35()

fffffe2cb3f12ee0 1()

wacki: Looks like that's being called from by the nvidia module?

Yes, I have used both, an Quadro RTX 5000 and an older Quadro K620 with the same result.

What's the panic message?

I can't see any. The screen stays empty with a blinking cursor and then after some seconds the machine reboots.

I have on familiarity with the closed driver, so going to be hard, but probably trying to load a free page or similar would be the most common.

*have no

wacki: i had a similar problem recently. the advice i got was to make sure the bios uses efi option rom of the gpu. i don't recall what the setting was called, but once I found it and set it correctly it "just worked".

I will look for it. Alas the BIOS settings of the Z4 are quite limited.

Ok, after some experiments I found a working configuration. I had to disable legacy and enable uefi boot (with secure boot disabled).