From owner-freebsd-questions@FreeBSD.ORG  Mon Jun 22 22:54:37 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@nevdull.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C80A4405
 for <freebsd-questions@nevdull.freebsd.org>;
 Mon, 22 Jun 2015 22:54:37 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 89B37B3A
 for <freebsd-questions@freebsd.org>; Mon, 22 Jun 2015 22:54:37 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from r56.edvax.de (port-92-195-85-234.dynamic.qsc.de [92.195.85.234])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 99F97276AF;
 Tue, 23 Jun 2015 00:54:33 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id t5MMsXmu002084;
 Tue, 23 Jun 2015 00:54:33 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Tue, 23 Jun 2015 00:54:33 +0200
From: Polytropon <freebsd@edvax.de>
To: Quartz <quartz@sneakertech.com>
Cc: FreeBSD questions <freebsd-questions@freebsd.org>
Subject: Re: Current state of firewire support?
Message-Id: <20150623005433.a999ebee.freebsd@edvax.de>
In-Reply-To: <55887DE4.3070207@sneakertech.com>
References: <mailman.59.1434974401.37644.freebsd-questions@freebsd.org>
 <201506221439.t5MEddYe026712@sdf.org>
 <55887DE4.3070207@sneakertech.com>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2015 22:54:37 -0000

On Mon, 22 Jun 2015 17:28:04 -0400, Quartz wrote:
> > Also nonsense all he needs to do is
> >
> > kldload /boot/kernel/firewire.ko
> > or
> > echo 'firewire_load="YES"' >> /boot/loader.conf
> > and reboot
> 
> Ok awesome, so I can add a line to loader.conf or if for some weird 
> reason that fails just recompile the kernel?

Kernel options:

# FireWire support
device          firewire        # FireWire bus code
#device         sbp             # SCSI over FireWire (Requires scbus and da)
device          fwe             # Ethernet over FireWire (non-standard!)
device          fwip            # IP over FireWire (RFC 2734,3146)
device          dcons           # Dumb console driver
device          dcons_crom      # Configuration ROM for dcons

The kernel has several FireWire settings you could apply.
However, using kernel modules is easier and works in most
cases out of the box. That's often a better approach than
dealing with a custom (!) kernel.

Just re-compiling GENERIC usually won't change anything. :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...