Proper permanent setup of 1394 drivers

[Mark Knecht]

On Tue, 12 Oct 2004 10:39:36 -0700, Rick Stevens
<rstevens at vitalstream.com> wrote:
> Mark Knecht wrote:

f
> > a repeat of yesterday until I better understand what I'm doing:
> >
> > <SNIP>
> > alias wlan0 ndiswrapper
> >
> > #install ohci1394 /etc/modules.special
> > #install ieee1394 /etc/modules.special
> > #install sbp2 /etc/modules.special
> >
> > # ALSA portion
> > alias char-major-116 snd
> > alias snd-card-0 snd-atiixp
> > <SNIP>
> 
> Hmmm.  The only alias is for ndiswrapper.  So the driver loads are
> invoked via hotplug--not via the kernel monitor.

No, sorry. There were more aliases in the file - for Ethernet and for
USB. I jsut didn't include them.
> 
> > modules.special looked like:
> >
> > /sbin/modprobe ohci1394 > /dev/null 2>&1
> > /sbin/modprobe ieee1394 > /dev/null 2>&1
> > /sbin/modprobe sbp2 > /dev/null 2>&1
> >
> > Permissions are:
> >
> > flash etc # ls -al modules.special
> > -r-xr-xr-x  1 root root 119 Oct 11 15:26 modules.special
> > flash etc #
> 
> That all looks legit.  As I said, the modprobe of sbp2 should also bring
> in scsi_mod if it's not already loaded.

It does when I do this by hand.




> > To the extent 'top' would respond there was no process taking up the
> > CPU cycles. The disk drive was in a 100% used state visually - light
> > on and drive head moving a bunch. To me it looked like a run away
> > write process to a log file, but I saw nothing obvious in /var/log/.
> > messages just seemed to have normal boot messages.
> 
> As I said, it could have been an updatedb or prelink run.  Those can
> flog the drive.  A "ps -ax" and scanning for "prelink" or "updatedb"
> would have been nice.  I hate coincidences.

updatedb was my first thought. It definately wasn't running. I didn't
look for preliink, but as I say, I ran top. It said 1% CPU. The top
processes displayed weren't using the CPU.


> >
> > I haven't been quite brave enough to try again just yet. I have no
> > problem with loading the 1394 drivers every time as I pretty much use
> > 1394 hard drives for all of my audio work. Maybe rc.local is actually
> > a good choice in my case...
> 
> It's certainly the easiest place to control.  I'll have to look at the
> hotplug configs to see if there's an easy way to make sure your drivers
> get loaded.  I don't know why I didn't think of that before, since 1394
> is a hotplug thing.  Sheesh!

Also, this is a FC2 system but I'm running a new kernel -
2.6.9-rc2-mm4-VP-S7. Possibly this is kernel related. I could try
droppin gback to the standard FC2 kernel and making sure that works.
I'm just worried about creating another fsck situation.

Thanks,
Mark