Skip to content
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

Open
phma opened this issue Sep 30, 2020 · 9 comments
Open

Fails to boot on NUC10i7FNH #334

phma opened this issue Sep 30, 2020 · 9 comments

Comments

@phma
Copy link

phma commented Sep 30, 2020

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.
img_0587

@phma
Copy link
Author

phma commented Oct 2, 2020

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
x86_feature: md_clear
x86_feature: mds_no
x86_feature: core_thermal
x86_feature: pkg_thermal
mem = 33258444K (0x7edef3000)

It is unresponsive to the keyboard.

@jasonbking
Copy link

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?

@phma
Copy link
Author

phma commented Oct 2, 2020

I assume you mean kmdb on boot (there are other options). It gives a [0]> prompt and does not respond to any key.

@jasonbking
Copy link

Hrm.. are there any USB options in the bios you could try to see if you can get a working keyboard?

@phma
Copy link
Author

phma commented Oct 2, 2020

The keyboard works. I selected kmdb, verbose mode, and prom_debug using the keyboard.

@jasonbking
Copy link

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 :c + enter at the kmdb prompt should make it continue to boot). If we can figure that out, it'd simplify figuring out the later hang (it's not the only option, but likely the quicker one if we're able to get it working).

@phma
Copy link
Author

phma commented Oct 2, 2020

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?

@phma
Copy link
Author

phma commented Oct 7, 2020

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.

@blackwood821
Copy link

@phma Did you ever get this working or did you switch hardware?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants