Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 14777 - emu10k1 post-install and similar entries in modules.conf can cause analog output to fail
Summary: emu10k1 post-install and similar entries in modules.conf can cause analog out...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High major
Assignee: SpanKY
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-30 09:18 UTC by Zack Gilburd
Modified: 2003-02-11 00:38 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zack Gilburd 2003-01-30 09:18:59 UTC
User-Agent:       
Build Identifier: 

i have found that such entries in my modules.conf *will* cause modprobe / insmod
emu101k to fail.  i do not believe this is restricted to just me, as it happens
to me on any box i own that i do this on. unless the lines are removed from the
modules.conf, the errors continue 

Error: Bad Output in route name: Digital
Error: Bad route specified
Error: Bad input in route name: fx15
Error: Bad route specified
Error: Bad input in route name: fx15
Error: Bad route specified
Error: Bad line name
/lib/modules/2.4.20-lolo-r1/kernel/drivers/sound/emu10k1/emu10k1.o: post-install
emu10k1 failed
/lib/modules/2.4.20-lolo-r1/kernel/drivers/sound/emu10k1/emu10k1.o: insmod
emu10k1 failed


Reproducible: Always
Steps to Reproduce:
1. emerge emu10k1
2. modprobe emu10k1
3. emu-script -- is this step optional?
4. emu-config -a
5. rmmod emu10k1
6. modprobe emu10k1
7. test output (should be analog, this can be done with an mp3, whatever)
Actual Results:  
step 6 failed with the errors in the details section

Expected Results:  
it should have modprobed without failure

when the lines are removed from modules.conf as previously stated, it probes
without failure
Comment 1 tercero12 2003-02-01 02:12:18 UTC
I confirm this bug.  It is not a kernel version at fault, it has happened to me with 
Gentoo, Vanilla, and CK sources.  I get (just for the record): 
 
Error: Bad input in route name: fx15 
Error: Bad route specified 
Error: Bad input in route name: fx15 
Error: Bad route specified 
Error: Bad line name 
/lib/modules/2.4.19-gentoo-r10/kernel/drivers/sound/emu10k1/emu10k1.o: 
post-install emu10k1 failed 
/lib/modules/2.4.19-gentoo-r10/kernel/drivers/sound/emu10k1/emu10k1.o: insmod 
emu10k1 failed 
 
My card is a the 24-bit Audigy X-Gamer with Firewire.  The previous emu10k1 worked 
perfectly. 
Comment 2 Zack Gilburd 2003-02-02 13:16:43 UTC
tercero12:  if the problem is blocking your ability to use the emu10k1 stuff 
properly, you can just delete /etc/modules.d/emu10k1 .  so far, this fix has given 
me no problems, but it may cause some ill effects that i am not aware of. 
Comment 3 SpanKY gentoo-dev 2003-02-03 02:16:00 UTC
actually, this doesnt happen to everyone :P
i have an emu10k1 and it works fine for me ... also works fine for everyone ive asked who uses the emu10k1 package ...

try tweaking your /etc/emu10k1.conf file and rmmod/modprobe emu10k1 until it works

once you find out what settings are causing you trouble, post your findings here and ill update the default emu10k1.conf file accordingly
Comment 4 Zack Gilburd 2003-02-03 21:04:36 UTC
eh, maybe you didnt fully understand my problems.  unless those two specific 
lines are removed that are in the stock /etc/modules.d/emu10k1 -- analog sound 
doens't output.  and as for it not happening with everyone, that's why it's a bug.  
if it happened to everyone, it would be broken software ;). 
Comment 5 Zack Gilburd 2003-02-03 21:09:31 UTC
btw, sorry if my previous comment came off as rude...it hasn't been the best of 
days for me. :-\ 
 
i just tried to replicate the bug on my sisters computer that also has an audigy 
gamer in it, and it replicated 100%, even down to the fix. 
Comment 6 SpanKY gentoo-dev 2003-02-03 21:53:58 UTC
i understood what you said i still maintain it's not broken for all soundcards.  i dont use 
digital output, i use analog output ... 
 
please try doing what i said (and that is tweaking your emu10k1.conf) to see if you can 
get it to work with those lines in your modules.conf 
just run `modules-update` to add the lines back 
Comment 7 ebnf 2003-02-09 06:15:19 UTC
I've gotten this to work without complaint by reverting to the audigy scripts provided when there was a seperate audigy ebuild.

in /etc/modules.d/emu10k1
-post-install emu10k1 /usr/bin/emu-script restore
-pre-remove emu10k1 /usr/bin/emu-script save
+post-install emu10k1 /usr/bin/audigy-script restore
+pre-remove emu10k1 /usr/bin/audigy-script save

There is quite a lot different in those two scripts, so I'm not sure what the problem parts are.
Comment 8 SpanKY gentoo-dev 2003-02-10 02:35:12 UTC
ok, the errors come from the fact that the emu cards have different named routes than audigy cards ...

so when i run audigy-restore on my emu card, i get similar errors ...

ill try to write a wrapper script and detect the card somehow