Kernel 1394 debugging with WinDbg

shawn

unread,

Mar 1, 2002, 10:30:48 AM3/1/02

to

I'm trying to setup remote kernel 1394 debugging between a pair of XP 2600
machines. I've setup the boot.ini on the target and configured 1394 on the
host via the WinDbg GUI. I'm getting this error:

Symbol search path is: c:\temp;c:\windows\symbols
Using 1394 for debugging
Failed to open 1394 channel 44
If this is the first time KD was run, this is why this failed.
Virtual 1394 Debugger Driver Installation will now be attempted
Kernel Debugger failed initialization, 0x80070079

As anyone got this working? Any ideas?

Thanks,
Shawn

Stephan Wolf

unread,

Mar 1, 2002, 11:22:30 AM3/1/02

to

Hmm, don't know about 1394 stuff... "standard" reply only:

Make sure you have the latest WinDbg installed, download here:

http://www.microsoft.com/ddk/debugging/

Stephan
---
On Fri, 1 Mar 2002 10:30:48 -0500, "shawn" <sh...@att.com.SPAM1>
wrote:

Andre Vachon [MS]

unread,

Mar 2, 2002, 11:43:17 AM3/2/02

to

And the same error message apears the next time you try ?
Check in device manager to see if there is a 1394 debug driver installed.
if yes, you can try removing it and reinstall the debugger package from the
web over again.

-Andre
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

"shawn" <sh...@att.com.SPAM1> wrote in message
news:OqJTaYTwBHA.2020@tkmsftngp02...

Brent Stevens

unread,

Mar 21, 2002, 4:31:18 PM3/21/02

to

I've had the same problem.

Here is what my error says:

Using 1394 for debugging
Could not update 1394 device drivers - error e000020b
Failed to open 1394 channel 10

If this is the first time KD was run, this is why this failed.
Virtual 1394 Debugger Driver Installation will now be attempted

Kernel debugger failed initialization, Win32 error 2
"The system cannot find the file specified."

I'm not sure what file the system can't find because it never tells
me. No 1394 debug driver ever gets started, so I can't follow the
advise that Andre gives. I tried uninstalling and then reinstalling
Windbg but that didn't fix the problem. Does anyone have any advise on
how to fix this?

Thanks
Brent

"Andre Vachon [MS]" <andrev...@microsoft.com> wrote in message news:<ulTJTlgwBHA.2840@tkmsftngp05>...

Andre Vachon [MS]

unread,

Mar 21, 2002, 11:58:25 PM3/21/02

to

Did you try rebooting your host machine ?
We have seen a few cases where the driver did not get updated dynamically on
someones machine, and reboot helped.

-Andre
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

"Brent Stevens" <baste...@hotmail.com> wrote in message
news:c4bbff4.02032...@posting.google.com...

Brent Stevens

unread,

Mar 22, 2002, 9:04:19 AM3/22/02

to

Yes, I tried that several times. I know windbg is at least partially
installed properly because I can still debug over serial. Since
uninstalling didn't seem to completely uninstall everything, I tried
to do a bit of manual cleanup by removing some of the registry entries
that windbg set for the XP and .NET Server 1394 drivers. I also
deleted the 1394 debug drivers in system32\drivers. That still didn't
work. I know this isn't a problem with the 6.x windbg series because
it was also happening with the 4.x before I upgraded. The strange
thing is, this used to work. I was actually doing 1394 debugging a few
weeks ago and then had to locally debug a user mode app with windbg
and ever since the 1394 debugging hasn't worked.

Also, here is my command line startup command: windbg -k
1394:channel=10,symlink=Channel

Any help would be appreciated.

Brent

"Andre Vachon [MS]" <and...@online.microsoft.com> wrote in message news:<#iFKs4V0BHA.2804@tkmsftngp05>...

Andre Vachon [MS]

unread,

Mar 23, 2002, 3:28:46 AM3/23/02

to

One thing I would do it take out the "symlink" thing. You should not
specify that.

But if things are delete here and there, I think you''ll need to make sure
you delete absolutely everything related to 1394 debugging (the renamed
infs, the drivers, the services, the enumerated devnodes) and then reinstall
the debuggers again.

-Andre

shawn

unread,

Mar 28, 2002, 4:02:05 PM3/28/02

to

Tried rebooting and upgrading from 4.x to 6.x. I'm using a unibrain 1394 PCI
card on the host and the target is a dell with 1394 integrated.

Thanks,
Shawn

"Andre Vachon [MS]" <and...@online.microsoft.com> wrote in message
news:#iFKs4V0BHA.2804@tkmsftngp05...

Bill McKenzie

unread,

Mar 28, 2002, 5:22:50 PM3/28/02

to

I have had some problems with UniBrain cards. Is it OHCI compliant? Does
WinDbg require OHCI?

--
Bill McKenzie

"shawn" <sh...@att.com.SPAM1> wrote in message

news:#Xj#Cvp1BHA.2484@tkmsftngp07...

shawn

unread,

Mar 29, 2002, 9:34:11 AM3/29/02

to

The description of the "Location" in the Network Configuration Manager for
the adapter reads: "on Texas Instruments OHCI Compliant IEEE 1394 Host
Controller". I just plugged the hardware in and let XP install the software.

Shawn

"Bill McKenzie" <bmck...@driver.attbbs.com> wrote in message
news:#tsoqbq1BHA.2228@tkmsftngp07...