I have to use firewire as my kernel extension loads before the target has an IP address.
My kernel extension calls PE_enter_debugger() in its start routine.
I see «waiting for debugger» twice, then just once the console says «kdp_poll: no debugger device».
I would think that means the nvram boot-args is wrong but I’ve followed the instructions:
The host is a late 2012 Mac Mini, macOS 10.12.4 build 16E195.
The target is a mid 2010 Mac Pro with the same macOS build.
My kernel debug kit matches the macOS build.
Google yields no joy. Have you a clue for me?
I’m trying to get MacOS Sierra installed on my new hackintosh from the USB device. I keep getting stuck on: BSD process name corre.
I’m trying to get MacOS Sierra installed on my new hackintosh from the USB device. I keep getting stuck on:
BSD process name corresponding to current thread: launchd
waiting for remote debugger connection.
kdp_poll: no debugger device.
I was wondering if someone could help me solve this problem. I’ve been searching and trying different things for a day or two now and have had no luck. Any help would be greatly appreciated!! Thanks!
Computer specs:
Intel Core i9-9900K
GIGABYTE Z390 AORUS PRO WiFi
Samsung 860 EVO 2TB 2.5 Inch SATA III Internal SSD
Sapphire 11265-05-20G Radeon Pulse RX 580 8GB GDDR5
Ballistix Sport LT 64GB Kit (16GBx4) DDR4 2666 MT/s (PC4-21300)
Corsair Hydro Series, H60 2018 (CW-9060036-WW)
I’m getting a ‘panic’ message on first run of OS 10.4.8. Help.
MacBook Pro, Mac OS X (10.4.8), Debugger called:
Posted on Feb 8, 2015 2:14 AM
Helpful answers
Generally a hardware problem, but let’s see if we can get any more info in Verbose mode.
- Shut down your Mac if it is on.
- Press the power button to start the computer.
- Immediately press and hold the Command key and the following:
the «v» key for verbose mode. (Command-V)
Feb 8, 2015 11:04 AM
So, no text displayed at all?
Does it boot to Single User Mode, CMD+s keys at bootup, if so try.
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck.
Any results at all?
Feb 8, 2015 2:23 PM
There’s more to the conversation
Loading page content
Page content loaded
Generally a hardware problem, but let’s see if we can get any more info in Verbose mode.
- Shut down your Mac if it is on.
- Press the power button to start the computer.
- Immediately press and hold the Command key and the following:
the «v» key for verbose mode. (Command-V)
Feb 8, 2015 11:04 AM
Thank you so much for responding. I just tried the Command-V thing, but when it had run, the Mac tried to start up again, but didn’t get passed the Keyboard Language screen before the ‘panic’ message came back.
Feb 8, 2015 1:42 PM
So, no text displayed at all?
Does it boot to Single User Mode, CMD+s keys at bootup, if so try.
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck.
Any results at all?
Feb 8, 2015 2:23 PM
Thanks again, I really appreciate your help. The screen now says…
Waiting for remote debugger connection.
kdp–poll: no debugger device
I’ve attached an image of the screen.
Feb 8, 2015 2:58 PM
Does it boot in Safe Mode with Shift key held at startup?
Do you have the original startup discs?
Boot off your *original* Install Disk while holding down the *d key*, (not c key), then run the extended Apple Hardware Test. Some disks require you to use the Option key at bootup to select AHT. Some Discs have it inexplicably on Disc #2. Some models have a separate AHT CD.
Have you done a PRAM reset, CMD+Option+p+r.
In fact, do 3 in a row, takes a bit of time.
Feb 8, 2015 3:39 PM
It’s very late here in the UK, so I’ll try running through those options in the morning and get back to you then if that’s OK with you. I do have original startup discs BTW.
