On Sat, 20 Mar 2004 10:30:54 -0800 (PST) x m <[EMAIL PROTECTED]> wrote: > > hey all. > > i have a list of problems with my SBLive card. i > though it was related to one source but apperantly its > a bunch of problems mixed up in all together. > > so if u guys could help me up to solve some of them > that would be one step twards victory :) > > (1) ALSA cant detect my card: > --------------------------------------------------- > [EMAIL PROTECTED]:/etc/rc.d# cat /proc/asound/cards > --- no soundcards ---
[ snip ]
> pretty wierd. just by going though the syslog i
> noticed that ALSA was tryn to open the snd-emu10k1.o
> library when what i have in that directory is
> snd-emu10k1.o.gz. should i unpack it??
That's odd. I don't know whether you need to or not -- whether the
kernel module loader has the gunzip functionality or not -- but
I've never seen kernel modules gzipped like that before.
> also:
> -----------------------------------------------------
> [EMAIL PROTECTED]:/lib/modules/2.4.22/kernel/sound/pci/emu10k1#
> lsmod
> Module _ _ _ _ _ _ _ _ _Size _Used by _ _Not tainted
> snd-pcm-oss _ _ _ _ _ _37828 _ 0 _(autoclean) (unused)
> snd-pcm _ _ _ _ _ _ _ _56640 _ 0 _(autoclean)
> [snd-pcm-oss]
> snd-timer _ _ _ _ _ _ _13508 _ 0 _(autoclean)
> [snd-pcm]
> snd-page-alloc _ _ _ _ _6356 _ 0 _(autoclean)
> [snd-pcm]
> snd-mixer-oss _ _ _ _ _12728 _ 0 _(autoclean)
> [snd-pcm-oss]
> snd _ _ _ _ _ _ _ _ _ _30148 _ 0 _(autoclean)
> [snd-pcm-oss snd-pcm snd-timer snd-mixer-oss]
> soundcore _ _ _ _ _ _ _ 3332 _ 0 _(autoclean) [snd]
> emu10k1-gp _ _ _ _ _ _ _1352 _ 0 _(unused)
> gameport _ _ _ _ _ _ _ _1452 _ 0 _[emu10k1-gp]
It looks like you have some OSS modules installed (emu10k1-gp,
gameport). That's likely the source of your problem; the
presence of that module prevents the loading of snd-emu10k1 and
the modules which depend on it.
Check /etc/modules to see if you're demanding these modules
be loaded at boot-time. If so, remove them.
If not, check to see if you have "discover" installed, or something
similar to it. This is a boot-time hardware detection application.
It's normally set up to run in boot scripts at an earlier time than
the ALSA initialization scripts. If it detects a soundcard, and
it hasn't been told otherwise, it'll install the relevant OSS
modules. If you do have discover installed, you can edit
/etc/discover and tell it explicitly not to load the modules in
question, or not to scan for soundcards.
There are other applications that do what discover does that you
may have installed (I don't know Slack; I run Debian); but then
you're on your own and will have to do some digging, since I
dunno what to tell you about how to change their behavior.
> i was also wonderring where do i put the parameter
> pci=biosirq?? i tried putting it into modules.conf and
> into lilo.conf, but nothing interesting happend, in
> particular... :)
First of all, it's an argument to the kernel invocation itself --
it's something that's passed to the linux kernel when it first is
booted. So in LILO, you put it in lilo.conf in the "append" string
(don't forget to rerun lilo afterwards). In grub, just edit your
menu file and add that to the end of the "kernel" line.
Second, before doing so, first make sure that you need to; and if you
do need to, make sure it's the best solution. I've seen this message
before on my machine and it didn't end up causing any problem. In
case it does . . .the message indicates that the kernel was not able
to assign an IRQ to that PCI device. The suggested kernel option
(pci=biosrq) tells the kernel to:
Use PCI BIOS calls to get the interrupt routing table.
These calls are known to be buggy on several machines
and they hang the machine when used, but on other
computers it's the only way to get the interrupt routing
table. Try this option if the kernel is unable to
allocate IRQs or discover secondary PCI buses on your
motherboard.
(from /usr/src/linux/Documentation/kernel-parameters.txt)
However, the most common reason that the kernel is unable to
assign an IRQ to a PCI device won't be solved by this. Instead,
look at your BIOS settings. in particular, look for an option
that sets your OS to "Windows" or "Other" (you want "Other"), or
look for an option that sets whether you'll be running a
"Plug and Play OS" (you want "No"). This makes the BIOS
take care of configuring devices.
Finally, any time you play with kernel options, be sure to include
more than one selection for that kernel in your lilo.conf or your
grub menu (one listing with a set of kernel options that you've
been using and *know* will allow the machine to boot, and one with
the new options). That way, you can't get in trouble by adding
kernel options that suddenly make your machine unbootable (thus
making it a pain in the butt to fix the kernel options).
-c
--
Chris Metzler [EMAIL PROTECTED]
(remove "snip-me." to email)
"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear
pgp00000.pgp
Description: PGP signature
