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>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150623005433.a999ebee.freebsd>