Firewire blues

[Gerald Heinig]

Ulrich Spoerlein wrote:
> On Sun, 13.02.2005 at 22:46:29 -0500, Stephan Uphoff wrote:
> 
>>+device dcons
>>+device dcons_crom
>>
>>Then configured/compiled/installed the GENERIC.debug kernel.
>>Copied the kernel.debug file in the GENERIC.debug compile directory to
>>the debug station and rebooted the target machine.
> 
> 
> I tried this with modules first, and failed every time. It needs to be
> compiled into the kernel to really work, which brings me to the next
> problem.
> 
> When dcons_crom is loaded (module or not) and I boot my system (laptop),
> I only get the "kernel output" on screen. All the other output (starting
> from Mounting root from ufs) goes to the firewire console.

I don't know whether this will break other stuff, but in the course of 
my attempts to get the setup working, I tried setting

options		DCONS_FORCE_CONSOLE=1

This caused all the output of the console to go to the Firewire port. I 
could log in etc. as normal on the console (over Firewire of course).

> 
> But since I'm using GBDE on this laptop, the startup scripts want me to
> enter my passphrase, which in turn I can only enter via a second machine
> through firewire.
> 
> This _is_ rather unpractical :( and renders single-user console useless.
> What am I doing wrong here?
> 
> Other than that, remote gdb is working. Poking inside the fwmem itself
> is however not working, I get this after setting eui64_{hi,lo}
> % kgdb -c /dev/fwmem0.0 kernel.debug
> ...
> 0x00000000 in ?? ()

I got this as well. In my case I assumed it's due to the fact that I 
wasn't using the same kernel file for the debugger as was running on the 
target machine. I didn't investigate further because I can't spend any 
more time on this problem at the moment.
I'd be interested to know whether that is the problem though.

> 
> What's missing here?
> 
> Ulrich Spoerlein