Alexandre & others-
> NB. be sure to "/sbin/chkconfig kudzu off" otherwise
the setup will kernel
> panic at boot.
I've heard about such myths, but I find it hard to believe them. If
it's kudzu that causes the hang, it's long past the end of the kernel
boot. If it's kudzu that hangs the machine, the solution is to have
the following lines in your /etc/modprobe.conf:
alias ieee1394-controller ohci1394
alias scsi_hostadapter sbp2
This prevents kudzu from attempting to probe for the ohci1394 module
and then unload it, the latter of which causes a system hang.
you bring up a good point that i forgot to mention. i actually have those
two lines in my /etc/modprobe.conf already. i understand your skepticism about
/sbin/chkconfig kudzu off but there was orginally a bug in kudzu that caused a
kernel panic if kudzu was on with/without the above lines.
see
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118202
however, i just checked and it seems the kernel panic bug has been fixed...
/sbin/chkconfig kudzu off is no longer necessary. i tested this by booting with
/sbin/chkconfig kudzu on. but seriously, at one time, i could reproduce this
condition every single time with kudzu on (as did others).
so, i'm going to revise my ealier recommendations about how to get firewire
to work great under FC2 test3:
[root@markf78 home]# rpm -q fedora-release initscripts SysVinit kernel kudzu
fedora-release-1.92-1
initscripts-7.50-1
SysVinit-2.85-25
kernel-2.6.3-2.1.253.2.1
kudzu-1.1.58-1
and add the following lines to /etc/modprobe.conf (thanks for the reminder,
should have pointed this out earlier):
alias scsi-hostadapter sbp2
alias ieee1394-controller ohci1394
mark.
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover