Re: finding out which parameters ("options") were passed to a driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]<


On Thu, Aug 07, 2003 at 10:51:49AM +0300, sting sting wrote:
> Hello,
> I want to know how can I
> find out which parameters ("options") were passed to a sound driver which 
> is currently loaded in memory ; this driver might have been loaded with 
> lsmod or modeprobe;
> Is there a way to find which were the parameters for this lsmod or modprobe
> command ?
> In fact , the problem I have is that I have two machines with the same card 
> ;
> the driver which is used in the first one is es1371.o; I want to use the 
> same driver on
> the second one. I do not know what are the parameters which are passed to 
> the
> es1371.o on the first machine; it is done automatically at start up (the 
> only thing
> which I find relevvant is that there is an alias in /etc/module.conf, but 
> with out
> any "options".
> How does the Linux know which parameters are passed to es1371.o upon 
> startup ?
> regards,
> sting

Do a

  cat /proc/pci | less

and look for your sound card.  It should list the IRQ and I/O ports

Bob McClure, Jr.             Bobcat Open Systems, Inc.
You can preach a better sermon with your life than with your lips.

Sound-list mailing list

[Index of Archives]     [Sound Cards]     [Kernel]     [Red Hat Install]     [Drives]     [Red Hat Development]     [Video 4 Linux]     [Gimp Users]     [Yosemite Trails]

  Powered by Linux