Can't get Windbg to use 1394

I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
this in the past many times without any trouble; but I’m getting nowhere
this time. This is just the host side; I haven’t even gotten to the
target yet.

I’m running Win7 64-bit; I installed the latest WinDbg from the online
SDK installer (that’s the only thing from the SDK I installed). Next, I
ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
1394, and entered channel 42.

When I click OK, it tries to install the 1394 debug driver; but after
spinning awhile, it fails. I tried deleting the device and installing
again; no luck. Then I tried deleting the 1394 controller, rebooting,
and reinstalling; it did the same thing (tried to install the debug
driver, then failed).

I tried updating the driver through driver manager by pointing it at the
one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
it just tells me the latest driver is already installed.

I must be making some obvious mistake, but I am just not seeing it. Any
suggestions?

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

Did you try restarting Windbg without messing with the driver? A long time ago, it would load the driver, but you had to exit Windbg for Windbg to actually use it. Not sure if that’s still the case…

Phil

Not speaking for LogRhythm
Phil Barila | Senior Software Engineer
720.881.5364 (w)
LogRhythm, Inc.
A LEADER in the 2013 SIEM Magic Quadrant
Perfect 5-Star Rating in SC Magazine for 5 Consecutive Years

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Michael Jones
Sent: Wednesday, November 06, 2013 3:06 PM
To: Kernel Debugging Interest List
Subject: [windbg] Can’t get Windbg to use 1394

I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done this in the past many times without any trouble; but I’m getting nowhere this time. This is just the host side; I haven’t even gotten to the target yet.

I’m running Win7 64-bit; I installed the latest WinDbg from the online SDK installer (that’s the only thing from the SDK I installed). Next, I ran WinDbg (X64) as Administrator, selected File | Kernel Debug… | 1394, and entered channel 42.

When I click OK, it tries to install the 1394 debug driver; but after spinning awhile, it fails. I tried deleting the device and installing again; no luck. Then I tried deleting the 1394 controller, rebooting, and reinstalling; it did the same thing (tried to install the debug driver, then failed).

I tried updating the driver through driver manager by pointing it at the one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but it just tells me the latest driver is already installed.

I must be making some obvious mistake, but I am just not seeing it. Any suggestions?

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________


WINDBG is sponsored by OSR

OSR is hiring!! Info at http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

I did try restarting the machine; however, the problem seems to be with
the 1394kdbg.sys driver (it comes up yellow-banged). I did notice that
the latest SDK appears to be for Windows 8.1; I assumed it would still
work on Windows 7 (or at least warn me when I installed it), but perhaps
that was an invalid assumption?

Is it worth tracking down an older WinDBG? What are other folks using?
I’m currently running a Win7/64 host, and the target will be primarily
Win7 (both 32 and 64), but I’ll probably have to run XP and Win8 on it
eventually.

–mkj

On 11/6/2013 5:16 PM, Phil Barila wrote:

Did you try restarting Windbg without messing with the driver? A long time ago, it would load the driver, but you had to exit Windbg for Windbg to actually use it. Not sure if that’s still the case…

Phil

Not speaking for LogRhythm
Phil Barila | Senior Software Engineer
720.881.5364 (w)
LogRhythm, Inc.
A LEADER in the 2013 SIEM Magic Quadrant
Perfect 5-Star Rating in SC Magazine for 5 Consecutive Years

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists…osr.com] On Behalf Of Michael Jones
Sent: Wednesday, November 06, 2013 3:06 PM
To: Kernel Debugging Interest List
Subject: [windbg] Can’t get Windbg to use 1394

I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done this in the past many times without any trouble; but I’m getting nowhere this time. This is just the host side; I haven’t even gotten to the target yet.

I’m running Win7 64-bit; I installed the latest WinDbg from the online SDK installer (that’s the only thing from the SDK I installed). Next, I ran WinDbg (X64) as Administrator, selected File | Kernel Debug… | 1394, and entered channel 42.

When I click OK, it tries to install the 1394 debug driver; but after spinning awhile, it fails. I tried deleting the device and installing again; no luck. Then I tried deleting the 1394 controller, rebooting, and reinstalling; it did the same thing (tried to install the debug driver, then failed)…

I tried updating the driver through driver manager by pointing it at the one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but it just tells me the latest driver is already installed.

I must be making some obvious mistake, but I am just not seeing it. Any suggestions?

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________


WINDBG is sponsored by OSR

OSR is hiring!! Info at http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

I can delete both the “1394 Debugger Device” and the “VIA 1394 OHCI
Compliant Host Controller” from Device Manager, reboot, and then run
WinDBG again to trigger reinstallation of the “1394 Debugger Device” (by
selecting Kernel Debug, 1394, Channel 42).

However, the installation (of the debug device) fails. There is nothing
in setupact.log; the only thing that changes (in C:\Windows) is
WindowsUpdate.log (it appears that Automatic Update ran to check for new
updates).

If I reboot the machine, the “1394 Debugger Device” comes up
yellow-banged, and it shows Code 39 in the Properties (from Device
Manager). “C:\Windows\System32\drivers\1394kdbg.sys” is present, so
something got installed.

I tried re-running “C:\Program Files (x86)\Windows
Kits\8.1\Debuggers\Redist\X64 Debuggers And Tools-x64_en-us.msi”, and
then going through the whole process again (delete devices, reboot, run
Windbg, select kernel debug, 1394, channel 42), but same result.

I am completely at a loss as to what might be going wrong, or even what
to try next. Any and all suggestions welcome.

–mkj

On 11/6/2013 5:06 PM, Michael Jones wrote:

I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
this in the past many times without any trouble; but I’m getting nowhere
this time. This is just the host side; I haven’t even gotten to the
target yet.

I’m running Win7 64-bit; I installed the latest WinDbg from the online
SDK installer (that’s the only thing from the SDK I installed). Next, I
ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
1394, and entered channel 42.

When I click OK, it tries to install the 1394 debug driver; but after
spinning awhile, it fails. I tried deleting the device and installing
again; no luck. Then I tried deleting the 1394 controller, rebooting,
and reinstalling; it did the same thing (tried to install the debug
driver, then failed).

I tried updating the driver through driver manager by pointing it at the
one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
it just tells me the latest driver is already installed.

I must be making some obvious mistake, but I am just not seeing it. Any
suggestions?

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

This is driving me crazy. I bought a 1394 card from OSR, installed it
(and disabled the VIA 1394 controller on the motherboard); it behaves
exactly the same way!

The “1394 Windows Debug Driver (Kernel Mode)” says “Windows cannot load
the device driver for this hardware. The driver may be corrupted or
missing. (Code 39)”. The SYS file is there, and I’ve re-installed twice
now, so I’m reasonably sure it’s NOT corrupted.

Does anyone have any idea what might be going on? Or even what to try
next? 1394 is my only option for this project, and I haven’t even
gotten to setting up the target…

–mkj

On 11/6/2013 5:06 PM, Michael Jones wrote:

I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
this in the past many times without any trouble; but I’m getting nowhere
this time. This is just the host side; I haven’t even gotten to the
target yet.

I’m running Win7 64-bit; I installed the latest WinDbg from the online
SDK installer (that’s the only thing from the SDK I installed). Next, I
ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
1394, and entered channel 42.

When I click OK, it tries to install the 1394 debug driver; but after
spinning awhile, it fails. I tried deleting the device and installing
again; no luck. Then I tried deleting the 1394 controller, rebooting,
and reinstalling; it did the same thing (tried to install the debug
driver, then failed).

I tried updating the driver through driver manager by pointing it at the
one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
it just tells me the latest driver is already installed.

I must be making some obvious mistake, but I am just not seeing it. Any
suggestions?

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

So, I dug out my old Windows Driver Kit 7.1.0 disk and installed that
(which contains WinDbg 6.12.0002.633). That worked as expected–the
1394 driver installed just fine, and WinDbg sat there patiently waiting
for a connection. I don’t know what’s up with the 8.1 kit, but it sure
was a waste of many hours. Now, on the to the target!

–mkj

On 11/12/2013 4:33 PM, Michael Jones wrote:

This is driving me crazy. I bought a 1394 card from OSR, installed it
(and disabled the VIA 1394 controller on the motherboard); it behaves
exactly the same way!

The “1394 Windows Debug Driver (Kernel Mode)” says “Windows cannot load
the device driver for this hardware. The driver may be corrupted or
missing. (Code 39)”. The SYS file is there, and I’ve re-installed twice
now, so I’m reasonably sure it’s NOT corrupted.

Does anyone have any idea what might be going on? Or even what to try
next? 1394 is my only option for this project, and I haven’t even
gotten to setting up the target…

–mkj

On 11/6/2013 5:06 PM, Michael Jones wrote:
> I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
> this in the past many times without any trouble; but I’m getting nowhere
> this time. This is just the host side; I haven’t even gotten to the
> target yet.
>
> I’m running Win7 64-bit; I installed the latest WinDbg from the online
> SDK installer (that’s the only thing from the SDK I installed). Next, I
> ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
> 1394, and entered channel 42.
>
> When I click OK, it tries to install the 1394 debug driver; but after
> spinning awhile, it fails. I tried deleting the device and installing
> again; no luck. Then I tried deleting the 1394 controller, rebooting,
> and reinstalling; it did the same thing (tried to install the debug
> driver, then failed).
>
> I tried updating the driver through driver manager by pointing it at the
> one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
> it just tells me the latest driver is already installed.
>
> I must be making some obvious mistake, but I am just not seeing it. Any
> suggestions?
>
> TIA,
>
> – mkj
> _______________________________________________
> //
> // Michael K. Jones
> // Stone Hill Consulting, LLC
> // http://www.stonehill.com
> //_______________________________________________
>

“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

And, FYI: it also works just fine using the built-in VIA 1394 controller
on the motherboard.

–mkj

On 11/13/2013 9:53 AM, Michael Jones wrote:

So, I dug out my old Windows Driver Kit 7.1.0 disk and installed that
(which contains WinDbg 6.12.0002.633). That worked as expected–the
1394 driver installed just fine, and WinDbg sat there patiently waiting
for a connection. I don’t know what’s up with the 8.1 kit, but it sure
was a waste of many hours. Now, on the to the target!

–mkj

On 11/12/2013 4:33 PM, Michael Jones wrote:
> This is driving me crazy. I bought a 1394 card from OSR, installed it
> (and disabled the VIA 1394 controller on the motherboard); it behaves
> exactly the same way!
>
> The “1394 Windows Debug Driver (Kernel Mode)” says “Windows cannot load
> the device driver for this hardware. The driver may be corrupted or
> missing. (Code 39)”. The SYS file is there, and I’ve re-installed twice
> now, so I’m reasonably sure it’s NOT corrupted.
>
> Does anyone have any idea what might be going on? Or even what to try
> next? 1394 is my only option for this project, and I haven’t even
> gotten to setting up the target…
>
> --mkj
>
> On 11/6/2013 5:06 PM, Michael Jones wrote:
>> I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
>> this in the past many times without any trouble; but I’m getting nowhere
>> this time. This is just the host side; I haven’t even gotten to the
>> target yet.
>>
>> I’m running Win7 64-bit; I installed the latest WinDbg from the online
>> SDK installer (that’s the only thing from the SDK I installed). Next, I
>> ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
>> 1394, and entered channel 42.
>>
>> When I click OK, it tries to install the 1394 debug driver; but after
>> spinning awhile, it fails. I tried deleting the device and installing
>> again; no luck. Then I tried deleting the 1394 controller, rebooting,
>> and reinstalling; it did the same thing (tried to install the debug
>> driver, then failed).
>>
>> I tried updating the driver through driver manager by pointing it at the
>> one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
>> it just tells me the latest driver is already installed.
>>
>> I must be making some obvious mistake, but I am just not seeing it. Any
>> suggestions?
>>
>> TIA,
>>
>> – mkj
>> _______________________________________________
>> //
>> // Michael K. Jones
>> // Stone Hill Consulting, LLC
>> // http://www.stonehill.com
>> //_______________________________________________
>>
>

“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________