> Olivier Dugeon <[EMAIL PROTECTED]> writes:
>
> > Chmouel Boudjnah wrote:
> > > is the /etc/modules.conf do an alias from sound to nm256 driver ?
> > > Could you send to pixel your /proc/bus/pci/devices ?
> > >
>
> Jeff do you have an idea abou that ?
>
> > Currently i use my sound card in WSS emulation mode. this is my
> > modules.conf sound related stuff :
> >
> > pre-install sound insmod sound dmabuf=1
> > alias midi opl3
> > options opl3 io=0x388
> > options ad1848 io=0x530 irq=5 dma=1 dma2=0
> > alias sound ad1848
> >
> > If i comment the line "alias sound ad1848" and put "alias sound nm256" i
> > get the following :
> >
> > /sbin/insmod /lib/modules/2.2.17-15mdk/misc/soundcore.o
> > Using /lib/modules/2.2.17-15mdk/misc/soundcore.o
> > Symbol version prefix ''
> > /sbin/insmod /lib/modules/2.2.17-15mdk/misc/soundlow.o
> > Using /lib/modules/2.2.17-15mdk/misc/soundlow.o
> > /sbin/insmod /lib/modules/2.2.17-15mdk/misc/sound.o
> > Using /lib/modules/2.2.17-15mdk/misc/sound.o
> > /sbin/insmod /lib/modules/2.2.17-15mdk/misc/nm256.o
> > /lib/modules/2.2.17-15mdk/misc/nm256.o: init_module: Device or resource
> > busy
[...]
First of all, for safety's sake, I would comment out or remove -all-
sound-related lines in modules.conf, except for the nm256 line.
What does /bin/dmesg say, after making my recommended modules.conf
changes, and rebooting?
Whenever there is a "Device or resource busy" message, checking dmesg for
additional error output is a good first step... That is where the driver
"complains to" if it has problems.
Jeff
