Originally Posted by zander
@phred_sd: this looks like a different problem, possibly Fedora Core 4 related; do you have SELinux enabled?
Yes. Maybe that's the issue.
It seemed harmless enough when it asked...I tried 'setenforce 0' and that didn't allow the driver to work...though it may have to do with how it apparently modifies the kernel rather than whether it is enabled or not at the time.
I haven't really gotten anywhere, so maybe I'll just reinstall without SELinux and try again.