SuSE 9.2 and Creative Labs SB Audigy 2 Value
I just purchased and installed a Creative Labs SB Audigy 2 Value sound card model SB0400 on my SuSE 9.2 box but have so far had no luck in getting it past the configure stage. SuSE did show the "new hardware found" popup after the first reboot after the install and lead me to the sound configuration dialog but the card is not listed in the dialog and if I try to add it clicking "Add sound card" then I get "An error occurred during the installation of SB Audigy. The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters." snd-emu10k1 is already loaded according to lsmod. I tried moving it to another PCI slot but that makes no difference. I also tried disabling the motherboard onboard sound in the BIOS setup and deleting the entry in the sound configuration dialog but that makes no difference either. I have the latest ALSA packages installed from Packman. I don't know what else to try. Can anyone help?
On Thu, 2005-03-03 at 00:39 -0800, Claus Olesen wrote:
I just purchased and installed a Creative Labs SB Audigy 2 Value sound card model SB0400 on my SuSE 9.2 box but have so far had no luck in getting it past the configure stage.
SuSE did show the "new hardware found" popup after the first reboot after the install and lead me to the sound configuration dialog but the card is not listed in the dialog and if I try to add it clicking "Add sound card" then I get "An error occurred during the installation of SB Audigy. The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters."
snd-emu10k1 is already loaded according to lsmod.
I've got an Audigy 2 ZS and have similar problems. Here's the best I've managed so far. Hold on we're in for a bumpy ride! Before you start, check /etc/sysconfig/sound. (You should only need to do this once which is why I've kept it out of the numbered steps.) You want it to contain the following lines: LOAD_SEQUENCER="yes" SOUNDFONT_FILES="xxx.sf2" LOAD_OSS_EMUL_MODULES="yes" replace the xxx.fs2 with the name of the soundfont you want loaded. This file should be in the /usr/share/sounds/sf2 directory. 1) run "/etc/init.d/alsasound stop" This is just so that the sound is "officially" off. It looks like it's meant to kill off all processes using the sound devices, then remove all the sound modules. I've found it doesn't remove all of the modules - it leaves sound, soundcore and emu10k1 (if they had been loaded) and sometimes other snd-* modules as well. This means that if you try to restart, it fails while trying to load the modules and bails out :( 2) Now run: lsmod|egrep '^(snd|sound|emu10k1)' then carefully rmmod any listed modules. You can probably leave emu10k1_gp - it's for the joystick port. Also, you should probably leave snd_page_alloc loaded because the alsasound script explicitly avoids this one, the implication being that it's not safe to unload. Essentially, you need to get the audio system back to the way it was before any sound initialisation was performed. If there are a lot of sound modules to be unloaded, you may need several passes unless you're careful with the dependencies. Some versions of rmmod will do a recursive removal of modules, but it appears that the one that ships with SuSE 9.2 has had this option removed so you need to do it the hard way. 3) Run "yast2 sound". It may say that the number of sound cards running does not match the configured number and ask if you want to restart the sound system. Say no, then delete the entry for the card, exit yast and repeat steps 1 and 2 (yast will probably have loaded the soundcore and snd modules again) 4) Rerun "yast2 sound". You should go straight to the SB Audigy "Sound card configuration" page. Select "Normal setup" (the only one that works consistently for me). If you want, select "Configure joystick". Click Next. Press Test, and you should hear the sample. If not, I'm afraid I can't help you - you're on your own :( (Actually, it's possible that your /etc/modprobe.conf and its relatives need tweaking. If so, I can post my settings. 5) If you're still with me, before you press "finish", go to a shell and type "alsamixer" (or "alsamixergui" if you're running X). If it runs, great - you can quit yast, it's done all it can (bless it). If yast didn't manage to set up the mixer, (it will say "No mixer elems found") again, you're on your own. By now, you may find that everything you need works fine, in which case, enjoy! If, like me, you want to use rosegarden or something else that needs loaded soundfonts, you'll probably find the app appears to run, but you get no midi output. Warning: if you've previously loaded soundfonts since the last time you powered on, you might be deceived into thinking all is well. Unfortunately, the next time you power up, you'll probably find silence greets you. Fear not.
From the shell run "/etc/alsa.d/emu10k1". This little file *should* get run by the alsasound init script, but I've found that it doesn't (not sure why yet). This will load the soundfont you named in the sysconfig file.
One last thing you might need is to load the emu10k1 module. Most programs are fine without it, but if you find a program that complains about "device not found" or something like that, "modprobe emu10k1" and try again. Hopefully you'll be in business. Sheesh! There appears to be a real problem with both yast and the alsa init scripts. This seems to be caused when modules are already loaded. They get part way through, hit a spurious "error" (e.g. "cannot load module" when the module is already loaded) and then they give up, leaving the system half set up and therefore doomed to fail when you retry! Unfortunately, I find I have to do this every time I reboot (it's a good job this is Linux - I only usually need to reboot when I've powered off to install some new hardware ;-) I'm trying to automate the above process to replace the alsasound init script, but there is something that yast does when it is "Starting the sound system" that is not done by any of the init scripts. So far I've got two scripts, one to "clean" the system before running yast2 and one to do the additional bits after yast2. They could be stuck together, but until I've figured out what yast is doing that the init scripts don't, I need to keep them apart. Once I've got to the bottom of this, I'll post the results, unless someone else has a better solution in the meantime. If any of the yast developers are monitoring this list, I'd be interested in hearing what you do during a restart that the normal boot process doesn't. You should also investigate why yast only gets it right from a clean start. I'll be happy to test any patches. The ideal solution is for yast2 to "always work" (duh!) i.e. regardless of the current state of the sound system. Then, whatever it does when it restarts, should be transferred to the alsasound init script so that it can cleanly start the system on boot-up (warm or cold). If anyone has a better workaround than mine, PLEASE let us know. I hope I've been of some help. Phil Betts
Thank you very much for your elaborate write up! It's been very helpful in understanding a little more of what goes on behind the scenes. I followed your recipe e.g. removing any sound related kernel modules but the card still does not show up in YaST and adding it clicking the "Add sound card" button results in the same error. I get the sense that your card did show up in YaST after you had followed the recipe. I used "modprobe -r" to remove the modules that "/etc/init.d/alsasound stop" did not remove. They were only "soundcore" and "snd_page_alloc". I noticed that YaST has loaded all the modules back in again already when the YaST sound UI shows up e.g. before the user has had a chance to do anything using the UI. I googled for sb0400 and emu10k1 and see that 2.6.11 has just been released and that it addresses the SB0400 in particular - http://lwn.net/Articles/125753/ I suspect my kernel is too old/the card too new and that I have to get the new kernel to resolve this. I'm on stock SuSE 2.6.8-24.11-default. I'm a little hesitant compiling a new kernel because last time I did that - on SuSE 9.1 - some things stop working - like detection of new hardware if I remember right. I don't mind the work. My worry is getting the kernel parameters correct whereever there is a discrepancy between old and new. Now if SuSE also posted kernel updates (as opposed to only kernel fixes and mostly only security related) as FC does then my card would probably be playing by now. I'd still purchase SuSE 9.3 or whatever it's name becomes but some might not. And after I install the new kernel will YaST now recognize the card - will it show up in the list in YaST? Or will also YaST be "too old"? Anyone know of a place that posts SuSE 9.2 kernel updates? I know of only the Packman site (ftp.gwdg.de) for SuSE and Dag Wieers site for FC. The card might work on FC but I'm not running FC at home - only at work. Again, thank you very much for your reply. Claus On Thursday 03 March 2005 18:18, Phil Betts wrote:
On Thu, 2005-03-03 at 00:39 -0800, Claus Olesen wrote:
I just purchased and installed a Creative Labs SB Audigy 2 Value sound card model SB0400 on my SuSE 9.2 box but have so far had no luck in getting it past the configure stage.
SuSE did show the "new hardware found" popup after the first reboot after the install and lead me to the sound configuration dialog but the card is not listed in the dialog and if I try to add it clicking "Add sound card" then I get "An error occurred during the installation of SB Audigy. The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters."
snd-emu10k1 is already loaded according to lsmod.
I've got an Audigy 2 ZS and have similar problems. Here's the best I've managed so far. Hold on we're in for a bumpy ride!
Before you start, check /etc/sysconfig/sound. (You should only need to do this once which is why I've kept it out of the numbered steps.) You want it to contain the following lines: LOAD_SEQUENCER="yes" SOUNDFONT_FILES="xxx.sf2" LOAD_OSS_EMUL_MODULES="yes"
replace the xxx.fs2 with the name of the soundfont you want loaded. This file should be in the /usr/share/sounds/sf2 directory.
1) run "/etc/init.d/alsasound stop" This is just so that the sound is "officially" off. It looks like it's meant to kill off all processes using the sound devices, then remove all the sound modules. I've found it doesn't remove all of the modules - it leaves sound, soundcore and emu10k1 (if they had been loaded) and sometimes other snd-* modules as well. This means that if you try to restart, it fails while trying to load the modules and bails out :(
2) Now run: lsmod|egrep '^(snd|sound|emu10k1)' then carefully rmmod any listed modules. You can probably leave emu10k1_gp - it's for the joystick port. Also, you should probably leave snd_page_alloc loaded because the alsasound script explicitly avoids this one, the implication being that it's not safe to unload. Essentially, you need to get the audio system back to the way it was before any sound initialisation was performed. If there are a lot of sound modules to be unloaded, you may need several passes unless you're careful with the dependencies. Some versions of rmmod will do a recursive removal of modules, but it appears that the one that ships with SuSE 9.2 has had this option removed so you need to do it the hard way.
3) Run "yast2 sound". It may say that the number of sound cards running does not match the configured number and ask if you want to restart the sound system. Say no, then delete the entry for the card, exit yast and repeat steps 1 and 2 (yast will probably have loaded the soundcore and snd modules again)
4) Rerun "yast2 sound". You should go straight to the SB Audigy "Sound card configuration" page. Select "Normal setup" (the only one that works consistently for me). If you want, select "Configure joystick". Click Next. Press Test, and you should hear the sample. If not, I'm afraid I can't help you - you're on your own :( (Actually, it's possible that your /etc/modprobe.conf and its relatives need tweaking. If so, I can post my settings.
5) If you're still with me, before you press "finish", go to a shell and type "alsamixer" (or "alsamixergui" if you're running X). If it runs, great - you can quit yast, it's done all it can (bless it).
If yast didn't manage to set up the mixer, (it will say "No mixer elems found") again, you're on your own.
By now, you may find that everything you need works fine, in which case, enjoy!
If, like me, you want to use rosegarden or something else that needs loaded soundfonts, you'll probably find the app appears to run, but you get no midi output. Warning: if you've previously loaded soundfonts since the last time you powered on, you might be deceived into thinking all is well. Unfortunately, the next time you power up, you'll probably find silence greets you. Fear not.
From the shell run "/etc/alsa.d/emu10k1". This little file *should*
get run by the alsasound init script, but I've found that it doesn't (not sure why yet). This will load the soundfont you named in the sysconfig file.
One last thing you might need is to load the emu10k1 module. Most programs are fine without it, but if you find a program that complains about "device not found" or something like that, "modprobe emu10k1" and try again. Hopefully you'll be in business.
Sheesh!
There appears to be a real problem with both yast and the alsa init scripts. This seems to be caused when modules are already loaded. They get part way through, hit a spurious "error" (e.g. "cannot load module" when the module is already loaded) and then they give up, leaving the system half set up and therefore doomed to fail when you retry!
Unfortunately, I find I have to do this every time I reboot (it's a good job this is Linux - I only usually need to reboot when I've powered off to install some new hardware ;-)
I'm trying to automate the above process to replace the alsasound init script, but there is something that yast does when it is "Starting the sound system" that is not done by any of the init scripts. So far I've got two scripts, one to "clean" the system before running yast2 and one to do the additional bits after yast2. They could be stuck together, but until I've figured out what yast is doing that the init scripts don't, I need to keep them apart.
Once I've got to the bottom of this, I'll post the results, unless someone else has a better solution in the meantime.
If any of the yast developers are monitoring this list, I'd be interested in hearing what you do during a restart that the normal boot process doesn't. You should also investigate why yast only gets it right from a clean start. I'll be happy to test any patches.
The ideal solution is for yast2 to "always work" (duh!) i.e. regardless of the current state of the sound system. Then, whatever it does when it restarts, should be transferred to the alsasound init script so that it can cleanly start the system on boot-up (warm or cold).
If anyone has a better workaround than mine, PLEASE let us know.
I hope I've been of some help.
Phil Betts
Well, I took the plunge - and I now have music from the SB0400. With plunge I mean I installed the just released 2.6.11 - and that's really all there was to it. I did not do anything really besides from that. Thank you to the kernel developers. To install 2.6.11 I read chapter 8 of the SuSE admin guide http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.2/suselinux-adminguide_en/... and some notes I had from previously having compiled a kernel. The steps I used are 1. download linux-2.6.11.tar.bz2 from http://www.kernel.org/ to home directory. 2. cd 3. su 4. mv linux-2.6.11.tar.bz2 /usr/src/ 5. cd /usr/src 6. tar xvfj linux-2.6.11.tar.bz2 7. ln -sf linux-2.6.11 linux 8. cd linux 9. cp ../linux-2.6.8-24.11/.config . 10. make oldconfig (I replied by hitting the return key to all prompts except for the Audigy LS prompt for which I replied "m") 11. make clean 12. make bzImage 13. make modules 14. cp -a /boot /boot-org (I did this for backup in case I or something else should screw up /boot. I have a knoppix cd readily available for such event) 15. INSTALL_PATH=/boot make install 16. make modules_install 17. cd /boot 18. cp /usr/src/linux/System.map . 19. mkinitrd -k vmlinuz-2.6.11 -i initrd-2.6.11 20. cd grub 21. I edited menu.lst to add an entry for the new kernel as a modifed copy of the entry for the SuSE kernel and to modify the entry for the SuSE kernel such that it still works to boot the SuSE kernel in case the new kernel should misbehave. My menu.lst after editing: # Modified by YaST2. Last modification on Wed Nov 24 07:39:14 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,1)/boot/message title SUSE LINUX 9.2 with home built kernel 2.6.11 kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 vga=0x31a selinux=0 splash=silent resume=/dev/sda1 desktop elevator=as showopts initrd (hd0,1)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.2 kernel (hd0,1)/boot/vmlinuz-2.6.8-24.11-default root=/dev/sda2 vga=0x31a selinux=0 splash=silent resume=/dev/sda1 desktop elevator=as showopts initrd (hd0,1)/boot/initrd-2.6.8-24.11-default ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.2 kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd0,1)/boot/initrd 22. reboot 23. The new hardware found popup did not show. So I went to YaST. It did not list the card. So I hit "Add sound card","Creative Labs","Audigy" and "Quick setup" and then YaST listed a new entry that said... SB Audigy running. I clicked the Test sound button in the Volume panel and got the fanfare. But - initially no music from XMMS. I don't have 5.1, 6.1 or 7.1 speakers - just 2.1 speakers (but reasonable ones). Besides, there isn't much music in surround sound, is there? I have the speaker system plugged into the green hole on the backplate of the SB0400 - a guess. There is also an orange, black, blue, pink and a white hole. I can't find any doc on the web about these or for that matter anything else about this card. I think it is a conspiracy. Mine is an OEM - comes without anything but the anti-static bag that the card comes in. I then launched KMix, switched from "NVidia nForce2" to "Sound Blaster Audigy2_Value" in the upper right hand corner of KMix, pushed the buttons and pulled the sliders. But no music. I then went to preferences in XMMS, the "Audio I/O Plugins","Configure","Devices" and switched the audio device to EMU10K1 and the Mixer device to "SigmaTel STAC9750/51",restarted XMMS and ... voila - music. The sound quality is better than that from the motherboard builtin AC97 (it better be). I haven't disabled the AC97 but nor tried if it still works. Also, 2.6.11 is more responsive and I haven't come across anything yet that misbehaves. So - both are keepers. KMix appears to have a bug. The system tray volume slider doesn't work with the card but did work with the AC97 (I haven't checked if it still does). The AC97 and card are sound device no. 1 and 2 respectively on my box. Maybe the KMix tray slider works only on the first sound device. But no reason to dispair - the Master slider under the output tab in KMix does work with card. The above procedure for installing 2.6.11 is from memory. Double check for your own sake if you decide to use any of it. Now, if just the !@#$% fan noise from the computer wasn't so loud then I could also enjoy the music. Claus On Friday 04 March 2005 11:48, Claus Olesen wrote:
Thank you very much for your elaborate write up! It's been very helpful in understanding a little more of what goes on behind the scenes.
I followed your recipe e.g. removing any sound related kernel modules but the card still does not show up in YaST and adding it clicking the "Add sound card" button results in the same error. I get the sense that your card did show up in YaST after you had followed the recipe.
I used "modprobe -r" to remove the modules that "/etc/init.d/alsasound stop" did not remove. They were only "soundcore" and "snd_page_alloc".
I noticed that YaST has loaded all the modules back in again already when the YaST sound UI shows up e.g. before the user has had a chance to do anything using the UI.
I googled for sb0400 and emu10k1 and see that 2.6.11 has just been released and that it addresses the SB0400 in particular - http://lwn.net/Articles/125753/
I suspect my kernel is too old/the card too new and that I have to get the new kernel to resolve this. I'm on stock SuSE 2.6.8-24.11-default. I'm a little hesitant compiling a new kernel because last time I did that - on SuSE 9.1 - some things stop working - like detection of new hardware if I remember right. I don't mind the work. My worry is getting the kernel parameters correct whereever there is a discrepancy between old and new. Now if SuSE also posted kernel updates (as opposed to only kernel fixes and mostly only security related) as FC does then my card would probably be playing by now. I'd still purchase SuSE 9.3 or whatever it's name becomes but some might not. And after I install the new kernel will YaST now recognize the card - will it show up in the list in YaST? Or will also YaST be "too old"?
Anyone know of a place that posts SuSE 9.2 kernel updates? I know of only the Packman site (ftp.gwdg.de) for SuSE and Dag Wieers site for FC. The card might work on FC but I'm not running FC at home - only at work.
Again, thank you very much for your reply. Claus
On Thursday 03 March 2005 18:18, Phil Betts wrote:
On Thu, 2005-03-03 at 00:39 -0800, Claus Olesen wrote:
I just purchased and installed a Creative Labs SB Audigy 2 Value sound card model SB0400 on my SuSE 9.2 box but have so far had no luck in getting it past the configure stage.
SuSE did show the "new hardware found" popup after the first reboot after the install and lead me to the sound configuration dialog but the card is not listed in the dialog and if I try to add it clicking "Add sound card" then I get "An error occurred during the installation of SB Audigy. The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters."
snd-emu10k1 is already loaded according to lsmod.
I've got an Audigy 2 ZS and have similar problems. Here's the best I've managed so far. Hold on we're in for a bumpy ride!
Before you start, check /etc/sysconfig/sound. (You should only need to do this once which is why I've kept it out of the numbered steps.) You want it to contain the following lines: LOAD_SEQUENCER="yes" SOUNDFONT_FILES="xxx.sf2" LOAD_OSS_EMUL_MODULES="yes"
replace the xxx.fs2 with the name of the soundfont you want loaded. This file should be in the /usr/share/sounds/sf2 directory.
1) run "/etc/init.d/alsasound stop" This is just so that the sound is "officially" off. It looks like it's meant to kill off all processes using the sound devices, then remove all the sound modules. I've found it doesn't remove all of the modules - it leaves sound, soundcore and emu10k1 (if they had been loaded) and sometimes other snd-* modules as well. This means that if you try to restart, it fails while trying to load the modules and bails out :(
2) Now run: lsmod|egrep '^(snd|sound|emu10k1)' then carefully rmmod any listed modules. You can probably leave emu10k1_gp - it's for the joystick port. Also, you should probably leave snd_page_alloc loaded because the alsasound script explicitly avoids this one, the implication being that it's not safe to unload. Essentially, you need to get the audio system back to the way it was before any sound initialisation was performed. If there are a lot of sound modules to be unloaded, you may need several passes unless you're careful with the dependencies. Some versions of rmmod will do a recursive removal of modules, but it appears that the one that ships with SuSE 9.2 has had this option removed so you need to do it the hard way.
3) Run "yast2 sound". It may say that the number of sound cards running does not match the configured number and ask if you want to restart the sound system. Say no, then delete the entry for the card, exit yast and repeat steps 1 and 2 (yast will probably have loaded the soundcore and snd modules again)
4) Rerun "yast2 sound". You should go straight to the SB Audigy "Sound card configuration" page. Select "Normal setup" (the only one that works consistently for me). If you want, select "Configure joystick". Click Next. Press Test, and you should hear the sample. If not, I'm afraid I can't help you - you're on your own :( (Actually, it's possible that your /etc/modprobe.conf and its relatives need tweaking. If so, I can post my settings.
5) If you're still with me, before you press "finish", go to a shell and type "alsamixer" (or "alsamixergui" if you're running X). If it runs, great - you can quit yast, it's done all it can (bless it).
If yast didn't manage to set up the mixer, (it will say "No mixer elems found") again, you're on your own.
By now, you may find that everything you need works fine, in which case, enjoy!
If, like me, you want to use rosegarden or something else that needs loaded soundfonts, you'll probably find the app appears to run, but you get no midi output. Warning: if you've previously loaded soundfonts since the last time you powered on, you might be deceived into thinking all is well. Unfortunately, the next time you power up, you'll probably find silence greets you. Fear not.
From the shell run "/etc/alsa.d/emu10k1". This little file *should*
get run by the alsasound init script, but I've found that it doesn't (not sure why yet). This will load the soundfont you named in the sysconfig file.
One last thing you might need is to load the emu10k1 module. Most programs are fine without it, but if you find a program that complains about "device not found" or something like that, "modprobe emu10k1" and try again. Hopefully you'll be in business.
Sheesh!
There appears to be a real problem with both yast and the alsa init scripts. This seems to be caused when modules are already loaded. They get part way through, hit a spurious "error" (e.g. "cannot load module" when the module is already loaded) and then they give up, leaving the system half set up and therefore doomed to fail when you retry!
Unfortunately, I find I have to do this every time I reboot (it's a good job this is Linux - I only usually need to reboot when I've powered off to install some new hardware ;-)
I'm trying to automate the above process to replace the alsasound init script, but there is something that yast does when it is "Starting the sound system" that is not done by any of the init scripts. So far I've got two scripts, one to "clean" the system before running yast2 and one to do the additional bits after yast2. They could be stuck together, but until I've figured out what yast is doing that the init scripts don't, I need to keep them apart.
Once I've got to the bottom of this, I'll post the results, unless someone else has a better solution in the meantime.
If any of the yast developers are monitoring this list, I'd be interested in hearing what you do during a restart that the normal boot process doesn't. You should also investigate why yast only gets it right from a clean start. I'll be happy to test any patches.
The ideal solution is for yast2 to "always work" (duh!) i.e. regardless of the current state of the sound system. Then, whatever it does when it restarts, should be transferred to the alsasound init script so that it can cleanly start the system on boot-up (warm or cold).
If anyone has a better workaround than mine, PLEASE let us know.
I hope I've been of some help.
Phil Betts
On Sat, 2005-03-05 at 02:40 -0800, Claus Olesen wrote:
Well, I took the plunge - and I now have music from the SB0400.
Excellent! Damn those confounded PCI IDs. I read the article you pointed to in you last post, and it seems that all it needed was an entry in em10k1's list of recognised card IDs. I've been bitten by this problem myself: when I tried to read the memory stick in my Clie PDA (which was listed under supported devices), I found that the European version had a different ID. After a quick hack and recompile, all was well. It may be possible, e.g. using a kernel parameter, to force an association between an ID and a device, but if it is, I couldn't find the info.
Now, if just the !@#$% fan noise from the computer wasn't so loud then I could also enjoy the music.
Hear, hear! (If only we could) If it helps, my system just got considerably quieter after changing the case (it's still too loud though). My old case had cooling problems which I put down to poor airflow, with not much scope for improving it. This meant that the fans were always on full blast. The case I replaced it with (Jeantech Apollo - recommended) has fans everywhere. I did a count of the total number of fans (i.e. including mobo, PSU & GFX card) in the box and it came to nine! I was prepared for an unholy cacophony when I switched on, but was pleasantly surprised. As the system is cooling more efficiently, the fans are much less stressed, and the overall effect is to reduce the noise. Glad you've got the card sorted, Phil
participants (2)
-
Claus Olesen -
Phil Betts