According to Ed Chen: While burning my CPU.
>
> Greetings,
>
> Just been having these errors while bootin up. Can't seem to
> pinpoint exactly what's going wrong. I get these error messages while
> booting up :
>
> /lib/modules/2.2.9-19mdk/misc/opl3.o init_module: Device or resource busy.
>
> i think this has to do with my sound card, which works. But this error
> shows up nonetheless.
Yes it is sound related, it would appier that your sound driver gets loaded
and possably has opl3.o as a dependancy (as per
/lib/modules/2.2.9-19mdk/modules.dep) after that some other command or
daemon is trying to load opl3.o again which would produce;
"init_module: Device or resource busy" Of course it could be caused in some
other way, but the above is the most common problem.
Places to look for problems would be /etc/conf.modules and
/var/log/messages, syslog, boot.msg, etc.
>
> it also shows another error :
>
> /var/lib/nfs/xtab
>
> NFS mountd failed.
NFS at starttime writes to /var/lib/nfs/xtab the information it writes there
is obtained from /etc/exports so if /etc/exports is an empty file or is
non-existant then quite possably NFS will fail, if you do not want to export
parts of your filesystems to other computers then dont start NFS at bootime.
Judgeing by the directory structure of your system i guess you are running
Redhat, you can use "linuxconf" to stop NFS being started at bootime.
>
> Im not sure what that one means :/
>
> any help would be greatly appreciated.
>
> ed
>
--
Regards Richard.
[EMAIL PROTECTED]