Recent content by jukes

I seem to be experiencing this iTunes related crash using the current set of kexts installed by the nuc repository version 6736d31 (FakeSMC, IntelGraphicsFixup, IntelMauseEtherney, Lilu). Has anyone else seen this happening? I'm not sure what the appropriate thing to do to fix this is. There's...

FWIW, 10.13.2 supplemental update appears to have installed on top of 10.13.2/apfs without problems.

It's identified as a bluetooth device, but it's not functional (can't be turned on and off, doesn't pair, etc).

Okay, I have tested these configurations, along with alt#0 (the unmodified config.plist from the nuc repository). For each configuration I captured 4 ioreg files (attached). hdmi: boot with HDMI hdmi_usb: boot with HDMI, hotplug USB-C usb: boot with USB-C usb_hdmi: boot with USB-C, hotplug...

Okay, now that I can boot again I'll try these out. Quick question. In emacs, my config.plist as Find/Replace as <data>...</data> where "..." is a sequence of letters (not hex) and `/` characters. you're listing hex values. Do I need to perform some sort of transformation of your values to...

Worked! I boot into recovery, started the terminal, unmounted the install disk, and remounted it as writable, then touched the SLE directory. Reboot and selected "without caches" in Clover. Boot process took quite some time, did not get stuck at DSMOS, but did restart back to Clover. Booted...

I would love to try this, but I can't seem to boot, so I can't run Terminal.app. I can get into the terminal in the Recovery boot, but that loads the volume read-only so I can't touch that file. I'll probably end up re-installing, unless I can figure out how to deal with this problem. It's an...

I don't know, I can no longer boot. Still working on that. To make sure we're on the same page, the thread for this issue comes through this post. The problem that I was dealing with was that booting HDMI and hotplugging USB-C was working after a clean high sierra (apfs) installation. After...

I mean that I can no longer boot into OSX on the system so I used the recovery terminal in order to copy the results onto a USB drive and post them here. This is probably irrelevant to the discussion, so ignore it. No results were produced during recovery. You asked for the Problem Reporting...

These are the results collected as you asked (HDMI-only, HDMI with hotplugged USB-C, USB-C-only (unstable). USB-C with hotplugged HDMI doesn't seem to be different than USB-C only). I can no longer boot after the USB-C experiment, so I had to go and copy them off of the drive using the recovery...

No. I was trying to collect this data and have run into a problem. Both HDMI and HDMI+USB-C hotplug worked fine. USB-C was completely unstable. OS X seems to think that there are two monitors connected, even though there are not. The USB-C monitor would auto power off every 30-ish seconds...

This happened to me as well. Try disabling the onboard Intel bluetooth in the system's BIOS, that should let your dongle work again. I have no idea why this wasn't necessary in Sierra.

Also, I have a BCM20702A0 bluetooth dongle and I had to disable the NUC's Intel bluetooth in the BIOS for this to work again.

I disabled both of these patches in config.plist and now hot-plugging the USB-C monitor worked. Thank you.

No, I have the same SMBIOS section in both. The pre-install is using the raw config_install_nuc7.plist with my SMBIOS data, and the post install is using the config_nuc7.plist from the nuc.git repo with the same SMBIOS data. Oh, okay. I can re-install from scratch again, and extract the...