-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to boot on NUC10i7FNH #334
Comments
I tried the new modification which jbk made, still dated 09-22, but downloaded 09-30, again in verbose mode with prom_debug set. It outputs a long list of CPU properties, ending with this: x86_feature: clflushopt It is unresponsive to the keyboard. |
I think you confirmed this, but if you boot with kmdb from the boot option menu, when it hangs, does pressing F1+a do anything? |
I assume you mean kmdb on boot (there are other options). It gives a [0]> prompt and does not respond to any key. |
Hrm.. are there any USB options in the bios you could try to see if you can get a working keyboard? |
The keyboard works. I selected kmdb, verbose mode, and prom_debug using the keyboard. |
Unfortunately that's just in the boot loader (which is using the BIOS/firmware). Once the kernel loads, for some reason the kernel doesn't like something about the setup -- after kmdb loads, you should be able to type letters and see a response at the prompt (and typing |
The BIOS is FNCML357. I found something about legacy USB and EFI, but I don't know what that means. What should I set it to? |
I disabled legacy USB in the BIOS. It made no difference. I also tried the keyboard that I got less than a year ago instead of the old one I've been using. Still can't type anything once the kernel's booted. |
@phma Did you ever get this working or did you switch hardware? |
I bought a new NUC to run SmartOS on to test software portability. It doesn't boot; it says "microfind: could not calibrate delay loop". Here is the result of trying to boot 20200922T220422Z in verbose mode with prom_debug set.
The text was updated successfully, but these errors were encountered: