|
EMU10K1
Dec 12, 2010 10:34:25 GMT -5
Post by musicman on Dec 12, 2010 10:34:25 GMT -5
I have the Creative Tech\E-mu 1212M audio systems in 2 different computers. These use the EMU10K1 audio chip [referred to in your Beta 2 postings to Jerry]. Will be glad to test the drivers when they arei incorporated into KNOS. [That is, unless they already are...I have the audio output from the EMU10K1's going into my stereo system, and have the stereo system powered off all of the time unless I am actually listening to music ]
|
|
|
EMU10K1
Dec 12, 2010 17:53:51 GMT -5
Post by Kevin McAleavey on Dec 12, 2010 17:53:51 GMT -5
I have the Creative Tech\E-mu 1212M audio systems in 2 different computers. These use the EMU10K1 audio chip [referred to in your Beta 2 postings to Jerry]. Will be glad to test the drivers when they arei incorporated into KNOS. [That is, unless they already are...I have the audio output from the EMU10K1's going into my stereo system, and have the stereo system powered off all of the time unless I am actually listening to music ] Sorry to say, bad news on that front. The developer who was trying to figure out that card got absolutely nowhere with it and finally gave up a couple of months ago. Dell was unwilling to provide any technical details and their attempts to hack it to get it to work lead nowhere either. Between Linux and BSD, it's the only sound card in existence that nobody was able to figure out. As the story goes, Creative was willing to provide the data since that card is long-since discontinued, but Dell vetoed it, and that pretty much wedged any hopes of support for it. If you have any other sound cards around (assuming that your motherboard doesn't already have sound on it) they should work just fine. We're proud to support every known sound card out there from any manufacturer other than this one.
|
|
|
EMU10K1
Dec 12, 2010 19:52:10 GMT -5
Post by musicman on Dec 12, 2010 19:52:10 GMT -5
Hi Kevin, Jerry....ok - I understand what you said about the Dell. Now, just to make sure I didn't mis-state anything. I believe the card Jerry has had the X on the end of - making it EMU10K1 - the DELL version Card.
The card that I have -and again, I will check - is different. It was sold in 2 retail [i.e. non-Dell specific] packages - as the 1212/1212M and the 1820/1820M. The 1820 series connected to external interface connection; the1212 series were all internal. Both series have 2 internal cards. The one card common to both series is the "heart" of the system. I pulled a 3rd card I have from a system to get these specs:
E-MU Model Number EM8810
In the manual, this card is referred to as the E-MU 1010.
The manual also lists these forums:
Unofficial E-MU Forum............................http://www.productionforums.com/emu/ E-MU Newsgroup (Yahoo) .......................http://groups.yahoo.com/group/e-mu_1820/ KVR Forum.................................................http://www.kvr-vst.com/forum/search.php Driver Heaven Forum ...............................http://www.driverheaven.net/search.php?s MIDI Addict Forum...................................http://forum.midiaddict.com/search.php Home Recording Forum...........................http://homerecording.com/bbs/ search.php?s=d866b60193933eb726660e7bd 90dfb27 Sound-On-Sound Forum..........................http://sound-on-sound2.infopop.net/2/ OpenTopic?a=srchf&s=215094572 Studio-Central Cafe Forum......................http://studio-central.com/phpbb/search.php Sound Card Benchmarking .....................http://audio.rightmark.org
From the Wikipedia page on E-MU, section "Non-Creative Sound Cards:
the core DSP chip (EMU10K2) of the cards is the same one designed by E-MU and used in Creative's Sound Blaster Audigy2
I know the "Unoffical E-MU Forum" has some E-MU employees monitoring it. And in the past, when I have asked for any kind of information, even by telephone, the techs have been extremely helpful.
|
|
|
EMU10K1
Dec 12, 2010 20:48:55 GMT -5
Post by Kevin McAleavey on Dec 12, 2010 20:48:55 GMT -5
Hi Kevin, Jerry....ok - I understand what you said about the Dell. Now, just to make sure I didn't mis-state anything. I believe the card Jerry has had the X on the end of - making it EMU10K1 - the DELL version Card. Ah! Right you are! So busy with the others, I slipped on this one perhaps. It might be likely that we have a vendor ID conflict and maybe yours is supported after all, just not "known" as yet. Yes, the "X" is the problem one, no hope for that one ... you might have the standard blaster "Audigy2" type card with a special OEM ID instead of the proper one. Just for laughs and giggles, give this a shot. Go up to Appplications, then Accessories, and select terminal. Once it's open type in su and hit enter to get a second prompt. Once there, type in the following and hit enter afterward: kldload snd_emu10k1 It won't give you any indication of success or failure, but if you go to the menu bar up top in any area that's blank, right click there and select "Add to panel." Down towards the bottom, there will be an item marked "volume control." Click add and a volume control thingy will appear on the top panel. See if you can get sound then after doing the kldload trick. I will need diagnostics from that machine in order to pick out the OEM ID for the card if it works and we'll put that into the next build as an autodetect. If this doesn't do it, then it too might be that "X" chipset. I was certain that we had ALL of the vendor ID's, but this one sounds like one of those one-offs, and if they somehow changed the OEM ID for the chipset, that could be the problem. The 10k1, 10k2 and 10k3 chipsets should all be detected already though.
|
|
|
EMU10K1
Dec 13, 2010 0:18:51 GMT -5
Post by musicman on Dec 13, 2010 0:18:51 GMT -5
Terminal: actually I did get an error message:
kldload: can't load snd_emu10k1: File exists
the volume control kept "waiting for the system to respond".
HOWEVER - part of THIS problem is.....I typed in what you said....but the EMU 1010 "heart of the system" card that I have - that pairs to make either the 1212 series or the 1820 series...AND is the "twin" in terms of the Creative product like....the EMU 1010 [model on pci card says 8810] uses the emu10k2 chipset!!!!!
after unloading the snd_emu10k1 I tried kjidload snd_emu10k2 and received the error can't load snd_emu10k2: No such file or directory
Do I need to type in something differetly to load the file for snd_emu10k2?
|
|
|
EMU10K1
Dec 13, 2010 0:52:39 GMT -5
Post by Kevin McAleavey on Dec 13, 2010 0:52:39 GMT -5
Terminal: actually I did get an error message: kldload: can't load snd_emu10k1: File exists the volume control kept "waiting for the system to respond". HOWEVER - part of THIS problem is.....I typed in what you said....but the EMU 1010 "heart of the system" card that I have - that pairs to make either the 1212 series or the 1820 series...AND is the "twin" in terms of the Creative product like....the EMU 1010 [model on pci card says 8810] uses the emu10k2 chipset!!!!! after unloading the snd_emu10k1 I tried kjidload snd_emu10k2 and received the error can't load snd_emu10k2: No such file or directory Do I need to type in something differetly to load the file for snd_emu10k2? That's actually a VERY good sign. The "file exists" error when you tried the kldload indicates that KNOS did INDEED detect that card and configured the driver for it. For all of those EMU chipsets, it's all the same driver (except for the pesky "X" chipset) - the k2 and k3 chipsets also use the k1 driver for all of those. So what you encountered tells me that the card was detected, driver loaded and ready to go. Your problem might be very simple - that the volume controls aren't configured or set loud enough. Of course, diagnostics on that machine will tell all for sure. Up on the top right panel on your desktop there is a red circle with an "f" in it. And right next to that, you should see a volume control icon. It defaults to a setting of 75% volume. The media player has a default level of 50% and so between the two of them at default setting, volume may not be set loud enough to hear anything possibly. There are also some other cards we've encountered that might require an additional volume boost beyond that, but the control for that is not normally configured. KNOS is designed in this version to be as quiet as possible since our main "show and tell" here is for commercial/military use where you don't want "loud" surprises unless you intend to play multimedia or similar deliberately. So with that in mind in this particular layout, we have everything cranked back on purpose. Try turning those up for now and give it a try. You should hear something even if it's still a bit low in volume. There's an option to introduce a second "mixer" by going up to the top panel, find a spot on it where it's blank, right click and select "add to panel." A list will pop up and down towards the bottom you will find "volume control" listed as an option. Highlight that, click "add" and then click "close" and a second volume control will appear on the panel. If you right click on the new volume control, there's "preferences" which allows you to assign one input or output to THAT volume control. One of them will be the setting you will need to crank it up a good bit louder. The proper one depends on that card. It's possible that one of those are completely muted and that's why there's no sound. If the sound device isn't working, then any icons on that top panel will have an X next to it indicating a problem ... no X there means that there is sound somewhere ... And here, a copy of diagnostics data will tell me all about your hardware in that particular box to allow me to dig further if we need to.
|
|
|
EMU10K1
Dec 13, 2010 7:41:31 GMT -5
Post by musicman on Dec 13, 2010 7:41:31 GMT -5
well - that DOES sound promising - I know - it's too early for a play on words....anyway, there was no volume control on the toolbar. I added one, and it DOES have the red box with the X in it. when I select Windows > Preferences > Sound I get an info box "waiting for sound system to respond"
I believe I sent you a copy of the diagnostics via email.
Thank you
|
|
|
EMU10K1
Dec 14, 2010 1:20:39 GMT -5
Post by Kevin McAleavey on Dec 14, 2010 1:20:39 GMT -5
well - that DOES sound promising - I know - it's too early for a play on words....anyway, there was no volume control on the toolbar. I added one, and it DOES have the red box with the X in it. when I select Windows > Preferences > Sound I get an info box "waiting for sound system to respond" I believe I sent you a copy of the diagnostics via email. Thank you Indeed you did, and it was interesting! :) This, like your missing drive problem, is another hardware conflict in that machine of yours. From the diagnostics: Dec 13 05:57:08 KNOS-32bit kernel: emu: setmap (150b8000, 800), nseg=1, error=0 Dec 13 05:57:08 KNOS-32bit kernel: emu: setmap (12feb000, 1000), nseg=1, error=0 Dec 13 05:57:08 KNOS-32bit kernel: pcm0: AC97 reset timed out. Dec 13 05:57:08 KNOS-32bit kernel: pcm0: ac97 codec invalid or not present (id == 0) Dec 13 05:57:08 KNOS-32bit kernel: device_attach: pcm0 attach returned 6Hardware Conflict ... you have an EMU soundcard which is being detected, but you also have a motherboard sound card which is apparently not disabled in BIOS. KNOS is seeing both, and the second one is failing because its interrupt is owned by the carded sound card. So you have two options to choose from here. You can either remove the EMU card and use the sound card already on your motherboard, or you'll need to go into BIOS and actually disable the "on board" sound device. When KNOS sees only one sound card, whichever you choose should light up merrily. Given that the on-board PCM sound does Dolby and at least 5.1 digital, I'd choose that one myself and drop the Creative thingy but that's entirely up to you. One of them though has to go ... Interesting OTHER thing as a result of the conflict - not sure of what this is about, but there's repeated errors out of the EMU card trying to contact and run a javascript from the emu.com site ... that ain't natural and don't know why this is happening unless there's some "over the network" configuration thingy for it. Personally, I'd find hardware that needs to talk to a remote host worrisome, so just to let you know ... this is the mothership it was trying to contact, and why whatever it was up to failed, probably because of KNOS' security. console message: www.emu.com/bin/js/TopNav_kana.js @73:ReferenceError: Can't find variable: hideAll
|
|
|
EMU10K1
Dec 14, 2010 8:56:18 GMT -5
Post by musicman on Dec 14, 2010 8:56:18 GMT -5
Okay....this is REALLY interesting! I am about ready to revoot from KNOS into Windows anyway, so I will check. But the VERY FIRST THING I did on installing the motherboard, was to DISABLE the onboard sound in the BIOS!!!! I have never gone back to enable it. So I will check to see if it is still set to "DISABLE" or not.
|
|
|
EMU10K1
Dec 14, 2010 9:04:09 GMT -5
Post by musicman on Dec 14, 2010 9:04:09 GMT -5
have just looked at the javascript link - "Purpose - This file should contain all of the javascript nessesary for the top-nav drop-down menus on www.americas.creative.com." I KNOW it is not needed for program / soundcard functionality, as the computer was disconnected from the internet for several months, but still in constant use for audio production. Anyway, now to check the BIOS setting for the AC97
|
|
|
EMU10K1
Dec 14, 2010 9:26:53 GMT -5
Post by musicman on Dec 14, 2010 9:26:53 GMT -5
OK - the BIOS Setting......AC97 onboard audio is STILL DISABLED!!!
In another setting, PCI slot #2 has it's Interrupt setting manually set to IRQ 11. This was done because according to the tech specs on the mb manufacturer's website, this is the ONLY possible assignable IRQ number which was NOT shared with another PCI slot on the mb. I want to keep the EMU card because I do all of my audio work at sample rates of 192K & 96K; I was hoping to trry some of this in KNOS , depending on the kinds of software I could find. In any case, I'll play with a few thngs, like changing the BIOS interrupt to AUTOMATIC for the E-MU card, and see if that makes a difference. Would like to see it load and test in KNOS, even if it is just for playback.
Thank you so much for the info. Leaves me some new things to check.
|
|
|
EMU10K1
Dec 14, 2010 21:03:07 GMT -5
Post by Kevin McAleavey on Dec 14, 2010 21:03:07 GMT -5
OK - the BIOS Setting......AC97 onboard audio is STILL DISABLED!!! In another setting, PCI slot #2 has it's Interrupt setting manually set to IRQ 11. This was done because according to the tech specs on the mb manufacturer's website, this is the ONLY possible assignable IRQ number which was NOT shared with another PCI slot on the mb. I want to keep the EMU card because I do all of my audio work at sample rates of 192K & 96K; I was hoping to trry some of this in KNOS , depending on the kinds of software I could find. In any case, I'll play with a few thngs, like changing the BIOS interrupt to AUTOMATIC for the E-MU card, and see if that makes a difference. Would like to see it load and test in KNOS, even if it is just for playback. Thank you so much for the info. Leaves me some new things to check. Interesting times indeed! Well ... just so you know how KNOS works, during the boot sequence, it's asking BIOS "what ya got in there?" and it only goes after what BIOS tells KNOS it has. Then it probes what BIOS points to, grabs the ID data from the hardware, looks it up in our own database and then tries to hook it up with the appropriate driver. For reasons unknown, BIOS is telling us that the HDA audio is there and waiting for us. If you look at the diagnostics, KNOS is saying "can't find it." So something squirrely afoot with how that motherboard is wired or what BIOS is telling it. I'm kinda stuck for an answer because the Bronx handshake is coming out of BIOS which should be hiding its existence entirely. If we were doing a special build for a manufacturer using that motherboard, I could write in an override to ignore the device but it would require a special build to do so. Perhaps that IRQ trick might yield a solution ...
|
|
|
EMU10K1
Dec 15, 2010 14:34:15 GMT -5
Post by musicman on Dec 15, 2010 14:34:15 GMT -5
Smile - well - as I think we both expected - changing the BIOS Interrupte for PCI slot 2 on my motherboard to AUTOMATIC made absolutely no differnece in the audio. The motherboard is Intel D845PESVL. Will start a new post on what I have just discovered
|
|
|
EMU10K1
Dec 15, 2010 17:13:32 GMT -5
Post by musicman on Dec 15, 2010 17:13:32 GMT -5
referring to the "original" computer - PESVL, for which you have the diagnostics on...the new beta d/l DOES boot up, and it DOES still have the problem with the audio - the volume control shows the X. HOWEVER, the latest build DOES show the listing for the CREATIVE AUDIGY / EMU10K2 as enabled - EXACTLY the same as on the EMU10K2 WN computer,. AND it also shows that the driver for the AC97 as disabled and the driver not present. I did create a diagnostic foir he Intel PESVL computer again, since I can get all the way into KNOS.
<118>Checking for any wifi cards ... <118>Loading snd_emu10k1.ko... pci0: driver added pci1: driver added pci2: driver added found-> vendor=0x1102, dev=0x0004, revid=0x03 domain=0, bus=2, slot=1, func=0 class=04-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0105, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x02 (500 ns), maxlat=0x14 (5000 ns) intpin=a, irq=22 powerspec 2 supports D0 D1 D2 D3 current D0 pci0:2:1:0: reprobing on driver added pci3: driver added pci0: driver added pci1: driver added pci2: driver added found-> vendor=0x1102, dev=0x0004, revid=0x03 domain=0, bus=2, slot=1, func=0 class=04-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0105, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x02 (500 ns), maxlat=0x14 (5000 ns) intpin=a, irq=22 powerspec 2 supports D0 D1 D2 D3 current D0 pci0:2:1:0: reprobing on driver added pcm0: <Creative Audigy (EMU10K2)> port 0xdc00-0xdc1f irq 22 at device 1.0 on pci2 pcm0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xdc00 emu: setmap (15e1d000, 800), nseg=1, error=0 emu: setmap (12ee5000, 1000), nseg=1, error=0 pcm0: AC97 reset timed out. pcm0: ac97 codec invalid or not present (id == 0) device_attach: pcm0 attach returned 6 pci3: driver added <118>[OK] <118> <118>Wed Dec 15 16:37:58 UTC 2010 <118>Dec 15 16:38:46 KNOS-32bit seahorse-daemon[3551]: init gpgme version 1.2.0 <118>Dec 15 16:39:01 KNOS-32bit pulseaudio[3566]: module.c: Failed to load module "module-detect" (argument: ""): initialization failed. <118>Dec 15 16:39:01 KNOS-32bit pulseaudio[3566]: main.c: Module load failed. <118>Dec 15 16:39:01 KNOS-32bit pulseaudio[3566]: main.c: Failed to initialize daemon. <118>Dec 15 16:39:01 KNOS-32bit pulseaudio[3565]: main.c: Daemon startup failed. <118>Dec 15 16:39:06 KNOS-32bit pulseaudio[3569]: module.c: Failed to load module "module-detect" (argument: ""): initialization failed.
[repeated lots of times]
|
|
|
EMU10K1
Dec 15, 2010 17:20:56 GMT -5
Post by musicman on Dec 15, 2010 17:20:56 GMT -5
Sigh - apologies all around. I have worked on this several hours today. i just now reread everything, and realized that, on this computer at least [PESV], you already knew everything. I should have read the diagnostics code BEFORE the AC97 snippet you sent. Oh well. Enough for today.
|
|