andyf: which ooce-* branch will be the first to drop the frame-pointer patch? I'll need to update my packages at that point

hello, I've been trying to install smartos locally on a NUC and whenever I boot the installer, the keyboard seems to stop being recognized. I even tried to boot on rescue mode but still no luck. does anyone have any idea what the issue might be?

jperkin - it will be the bloody (master) branch, some time after the next stable r151044 release is away. Assuming it does not cause a load of packages to regress when it's tested, that is.

Whether it will ever make it into a stable release is unknown (see my last reply to the mailing list thread)

Guest32 what type is usb port? usb3? usb2?

tsoome usb3

andyf: how does that map to the branches in omniosorg/gcc?

or are you applying the patch to omnios-itself?

Guest32 if that NUC has USB2, you could try that

tsoome it doesn't

it's to omnios itself, the omniosorg/gcc will probably not get updated until a decision is made

Guest32 do you have keyboard from different vendor?

tsoome I have tried a different keyboard, unfortunately

andyf: ok, thanks

I get this warning before booting, if it helps: WARNING: 'Couldn't read ACPI SRAT table from BIOS. lgrp support will be limited to one group.'

tsoome

have you checked for firmware update?

andyf: out of interest have you done much testing with gcc12? going to stick with 10 for next LTS but after that will be interested to try out whatever's latest.

Yes, omnios bloody (and the upcoming r151044) are almost entirely built with gcc 12

I think there are a couple of packages that still need attention, but that's it

good to know!

tsoome will look into it

Guest32: IIUC, unless you have multiple physical chips w/ different latencies, it's largely harmless (and even then, I think it just means that the system doesn't have any locality (think NUMA) info to optimize certain things)

jbk thanks for the info!

tsoome yup, still same situation after bios update

out of immediate ideas, sorry.

rest is about debugging xhci, I'm afraid

but that would require some access to the machine, which you do not have.

alright thank you anyways! tsoome

well, other option is to try some other illumos, omnios or openindiana or tribblix or ..

just to see if the defect is the same

will do