• 0
reggie51

stuck in no debugger device

Question

no debugger device

First of all, I apologize for my bad English.

I'm trying to install Niresh Sierra on my PC, since I have installed Niresh Yosemite without problems ...

Start the installation from chameleon, but at the beginning of the same is stuck in ¨dp_poll: no debugger device¨ I tried different boot flags but still throwing the error.

Features of my PC.

  • Intel Motherboard 
  • Intel Core I3 Processor
  • 6GB RAM
  • AtiRadeon HD6450 Video Card

Thank you so much.

Share this post


Link to post
Share on other sites

8 answers to this question

  • 0

Sierra requires SSE4.1 Instruction set as minimum CPU Requirements, in most cases without SSE4.1 there is a possibility of Kernel panic with text "Waiting for remote debugger connection"

Does you CPU supports SSE4.1 instruction set?

Share this post


Link to post
Share on other sites
  • 0
15 hours ago, Niresh said:

Sierra requires SSE4.1 Instruction set as minimum CPU Requirements, in most cases without SSE4.1 there is a possibility of Kernel panic with text "Waiting for remote debugger connection"

Does you CPU supports SSE4.1 instruction set?

Yes, exactly that message ("Waiting 
for remote debugger connection") 
appears before hanging up, but 
according to the manufacturer's page, 
my processor supports SSE4.1

Intel® Core ™ i3-3220 Processor

https://ark.intel.com/es/products/65693/Intel-Core-i3-3220-Processor-3M-Cache-3_30-GHz

Share this post


Link to post
Share on other sites
  • 0

Use CPU X to verify SSE4.1

Can you post a Picture of Verbose mode error, if possible take a HD video and upload it to youtube post link here

Share this post


Link to post
Share on other sites
  • 0

Hi, I asked for a screenshot of CPU-X, its ok you have posted as a video, Your CPU Support SSE4.1

I want a video while you boot USB from Chameleon

Share this post


Link to post
Share on other sites
  • 0

 

Ok Niresh here I leave the video you asked me

 

 

1 person likes this

Share this post


Link to post
Share on other sites
  • 0

Try booting with

cpus=1 -v

 

Share this post


Link to post
Share on other sites
  • 0

 

Thanks Niresh

I tested with cpus = 1 and threw the same error

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now