Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Jul 2009 02:03:54 +0200
From:      Julian Stecklina <js@alien8.de>
To:        freebsd-firewire@freebsd.org
Subject:   Re: 8-CURRENT Firewire
Message-ID:  <87k52kt505.fsf@tabernacle.lan>
References:  <1246316092.3981.11.camel@Lappy> <87hbxxp5ot.fsf@tabernacle.lan> <1246483794.3443.6.camel@Lappy> <87fxdguj4a.fsf@tabernacle.lan> <878wj2r3t1.fsf@tabernacle.lan> <1246894876.2966.8.camel@Lappy>

next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno <sean.bruno@dsl-only.net> writes:

> On Sun, 2009-07-05 at 23:03 +0200, Julian Stecklina wrote:
>> Julian Stecklina <js@alien8.de> writes:
>> 
>> >> 2.  Can you boot with the firewire enabled in the BIOS and the following
>> >> in loader.conf:
>> >> 	firewire_load="NO"
>> >> If you can boot this way, what happens when you:
>> >> 	kldload sbp.ko
>> 
>> http://os.inf.tu-dresden.de/~jsteckli/fbsd/sbp-after-boot.txt
>> 
>> In summary: No devices are discovered, even though I have a DVD and a
>> disk attached to the bus.
>> 
>> Regards,
>
> Hrm ... I think that fwohci() or firewire() is getting stuck.
>
> Can you turn up debug and re-run your boot up sequence just like the
> above dmesg?
>
> firewire_debug=3
> sbp_debug=3

I think I am too stupid to set these variables. I tried
debug.firewire_debug=3 in loader.conf, but it doesn't work. After
loading the modules they are always set to zero. Setting via sysctl
doesn't work either, since they don't exist before loading
firewire/sbp. So how do I set these?

Regards,
-- 
Julian Stecklina

The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87k52kt505.fsf>