Soundblaster Audigy 2 drivers?


Recommended Posts

Can i do an apt-get for them and install them that way?

585745266[/snapback]

I think you already have ALSA which should support Audigy 2. But you can always type:

apt-cache search alsa

and see what it finds. Also I suggested in another thread, you should type:

apt-get update
apt-get install synaptic

And then go through your menus and execute Synaptic. Gives a good GUI front-end for APT and also makes searching for apps on it a breeze.

ur steps didnt work at all

and not even the steps off here

http://www.ubuntuforums.org/showthread.php?t=21211

WTF DO I DO?!!!

585748646[/snapback]

If you have the Audigy 2 Value (SB0400) it seems to not work with many distros ATM. ALSA 1.0.8 supports this card but for some reason Mepis, ubuntu, debian and many others dont' currently support it even though they should. Now I tried Linspire Five-O just for kicks and for some crazy reason they actually support this sound card even though I think they use ALSA 1.0.6 but I think Linspire works with this card because it uses something called I think Jack Audio or something. I have a funny feeling that this jack software is what is supporting this card. I've tried getting this card to work with the latest stable version of Fedora Core 3 and it only worked after I installed ALSA 1.0.8 from source but I haven't tried Fedora Core 4 test 1 yet nor the latest version of Mandrake or Mandriva as they call it now.

Edit...Oh and if you don't mind using something a little older you can use Ubuntu Warty because I'm pretty sure this card worked with that version because I remember quite clearly how ****ed off I was when Hoary came out and refused to work with my soundcard. I quit using Ubuntu once they moved to Xorg because the thing just refused to work with my Dell E173FP LCD while the same version of Xorg works fine with other distros. I'm understanding more and more why I hate Xorg over Xfree86 because it never works.

Edited by SeaClearly

see, i'm not gonna reformatt, i just got the right kernel and nvidia drivers setup right for this pc. And don''t plan on going through that headache again. anyways (on the link i posted)

cd /usr/src

sudo wget ftp://ftp.alsa-project.org/pub/driv...r-1.0.8.tar.bz2

tar xvjf alsa-driver-1.0.8.tar.bz2 <---^ is this step just one line or 2 seperate lines? ive tried both and they seem to download the drivers

cd alsa-driver-1.0.8 <---- this is where i get stuck, i do this and it says no such file or directory

sudo ./configure --with-cards=emu10k1 --with-sequencer=yes

sudo make

sudo make install

sudo nano /etc/modules

add in

snd-pcm-oss

snd-emu10k1

snd-mixer-oss

Can someone help me. I know if do these steps it will work.

First line is this below which is downloading the file with wget.

sudo wget ftp://ftp.alsa-project.org/pub/driv...r-1.0.8.tar.bz2

Second line is unpacking the file or un tarring it.

tar xvjf alsa-driver-1.0.8.tar.bz2. Now I think to untar it you might need to be root and as such its a safe bet to instead type in this below.

sudo tar xvjf alsa-driver-1.0.8.tar.bz2

Now to be on the safe side I would enter into a root console while you do the rest.

Now if you typed those top two lines first that I think would cause your no such file or directory because nothing was ever unpacked.

Once you get the sudo make you might get an error asking to specify your kernel sources and those I had to ask Ubuntu support where they were and I can't think of what they said ATM but I would ask for this while your at it. After that everything should work very well. Now the Kernel sources could have been called kernel headers and for some reason I might be getting those two mixed up.

Also to add the modules you would enter this below and just in case I could be wrong and am going by pure memory right now.

type "sudo pico etc/modules/alsa.conf" without the quotes. You should see text and a list of modules and just add the modules listed into this file and save it as always making a backup of the file first. Now at a root console type lsmod and see if those modules are listed and if so they are loaded.

But I'm telling you know that at least for me getting my audigy 2 value to work under ubuntu was a pain and even after your done you need to type at a console alsamixer and unmute or mute one of the digital outputs to actually get the sound to work plus increasing all the volume levels. If you don't want to bother with this you would always use the warty release and if that doesn't come with KDE 3.4 for example or the latest gnome for example you can always just apt-get them with great ease and save yourself all this trouble. Bottom line is that there are some problems with Hoary with soundcards and video not working when they worked great in the previous warty.

Edited by SeaClearly
First things first, have you made sure sound isnt just muted?

Fire up alsamixer (type alsamixer) and unmute everything...

585750812[/snapback]

That most likely won't help because there are known issues with Hoary with many soundcards that should be supported and have been supported in Warty and all Ubuntu says is that those will be fixed after hoary final is released which has happened so now we have to wait and see how long until this has been fixed. Also Xorg is having major problems that need fixing as well.

That most likely won't help because there are known issues with Hoary with many soundcards that should be supported and have been supported in Warty and all Ubuntu says is that those will be fixed after hoary final is released which has happened so now we have to wait and see how long until this has been fixed.  Also Xorg is having major problems that need fixing as well.

585750823[/snapback]

When I used to use Ubuntu, it picked up my Audigy 2 without any configuration needed...

When I used to use Ubuntu, it picked up my Audigy 2 without any configuration needed...

585750827[/snapback]

You have an older Audigy 2 while I think this user has the newer Audigy 2 Value (SB0400) which has never worked in Ubuntu Hoary but only in Warty. Those two models are a big difference.

First line is this below which is downloading the file with wget.

sudo wget ftp://ftp.alsa-project.org/pub/driv...r-1.0.8.tar.bz2

Second line is unpacking the file or un tarring it.

tar xvjf alsa-driver-1.0.8.tar.bz2.  Now I think to untar it you might need to be root and as such its a safe bet to instead type in this below.

sudo tar xvjf alsa-driver-1.0.8.tar.bz2

Now to be on the safe side I would enter into a root console while you do the rest.

Now if you typed those top two lines first that I think would cause your no such file or directory because nothing was ever unpacked.

Once you get the sudo make you might get an error asking to specify your kernel sources and those I had to ask Ubuntu support where they were and I can't think of what they said ATM but I would ask for this while your at it.  After that everything should work very well.  Now the Kernel sources could have been called kernel headers and for some reason I might be getting those two mixed up.

Also to add the modules you would enter this below and just in case I could be wrong and am going by pure memory right now.

type "sudo pico etc/modules/alsa.conf" without the quotes.  You should see text and a list of modules and just add the modules listed into this file and save it as always making a backup of the file first.  Now at a root console type lsmod and see if those modules are listed and if so they are loaded.

But I'm telling you know that at least for me getting my audigy 2 value to work under ubuntu was a pain and even after your done you need to type at a console alsamixer and unmute or mute one of the digital outputs to actually get the sound to work plus increasing all the volume levels.  If you don't want to bother with this you would always use the warty release and if that doesn't come with KDE 3.4 for example or the latest gnome for example you can always just apt-get them with great ease and save yourself all this trouble.  Bottom line is that there are some problems with Hoary with soundcards and video not working when they worked great in the previous warty.

585750784[/snapback]

tha don't work. and alsammixer, everything is turned on. but the "Analog/digital output Jack is [off] how do i turn that on?

Good job (Y)

Although I thought "m" unmuted :unsure: I've never used digital out anyway...

585753959[/snapback]

Funny because I could never get Ubuntu to actually run alsamixer so maybe I should submit another bug for this. Now for the user that fixed it was is your actual sound card model number. Is this an Audigy 2 Value SB0400 or another model.

uhm, i think it its the SB0400 cant check right now though. I'm at work, but yes, alsamixer turned it on for me. :p And my sound seems soo much clearer in Linux than Windows, the bass is deeper and i have turned off the bass on my wub and in Alsamixer. I'm not complaining i love it, i'm just imressed.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!