14:24:23 <jperkin> andyf: which ooce-* branch will be the first to drop the frame-pointer patch? I'll need to update my packages at that point
15:56:37 <Guest32> 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?
16:15:24 <andyf> 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.
16:15:43 <andyf> Whether it will ever make it into a stable release is unknown (see my last reply to the mailing list thread)
16:17:55 <tsoome> Guest32 what type is usb port? usb3? usb2?
16:20:31 <Guest32> tsoome usb3
16:20:56 <jperkin> andyf: how does that map to the branches in omniosorg/gcc?
16:21:10 <jperkin> or are you applying the patch to omnios-itself?
16:22:21 <tsoome> Guest32 if that NUC has USB2, you could try that
16:24:24 <Guest32> tsoome it doesn't
16:26:04 <andyf> it's to omnios itself, the omniosorg/gcc will probably not get updated until a decision is made
16:27:54 <tsoome> Guest32 do you have keyboard from different vendor? 
16:28:28 <Guest32> tsoome I have tried a different keyboard, unfortunately
16:28:52 <jperkin> andyf: ok, thanks
16:36:03 <Guest32> 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.'
16:36:10 <Guest32> tsoome
16:36:29 <tsoome> have you checked for firmware update?
16:36:30 <jperkin> 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.
16:36:54 <andyf> Yes, omnios bloody (and the upcoming r151044) are almost entirely built with gcc 12
16:37:06 <andyf> I think there are a couple of packages that still need attention, but that's it
16:37:14 <jperkin> good to know!
16:37:51 <Guest32> tsoome will look into it
16:40:25 <jbk> 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)
16:46:47 <Guest32> jbk thanks for the info!
16:57:58 <Guest32> tsoome yup, still same situation after bios update
17:05:01 <tsoome> out of immediate ideas, sorry.
17:05:19 <tsoome> rest is about debugging xhci, I'm afraid
17:05:45 <tsoome> but that would require some access to the machine, which you do not have.
17:08:14 <Guest32> alright thank you anyways! tsoome
17:08:40 <tsoome> well, other option is to try some other illumos, omnios or openindiana or tribblix or ..
17:08:49 <tsoome> just to see if the defect is the same
17:10:39 <Guest32> will do