Pages: [1]   Go Down

Author Topic: ALSA has gone insane.  (Read 5899 times)

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« on: October 23, 2007, 04:20:54 am »
Quote
------ Initializing Sound ------
ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0,0
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default:0,0
Allocated 96 sources.
OpenAL info:
  Vendor:     OpenAL Community
  Version:    1.1
  Renderer:   Software
  Extensions: ALC_EXT_capture AL_EXT_capture AL_EXT_vorbis AL_EXT_MP3 AL_LOKI_quadriphonic AL_LOKI_play_position AL_LOKI_WAVE_format AL_LOKI_IMA_ADPCM_format AL_LOKI_buffer_data_callback ALC_LOKI_audio_channel
Sound initialization successful.
--------------------------------


No matter what I do, no sound. But every other application works, just not tremulous.
This is the kicker....

Even after recompiling my kernel three times, once with alsa built in, once with alsa as a module, once with alsa COMPLETELY REMOVED....

The "Dummy Device #0" is still there. Even after removing alsa entirely, the /proc/asound/cards shows a Dummy Device.

It's really frustrating. I'm running Gentoo amd64, alsa-lib-1.0.15_rc2, kernel 2.6.23 amd64. I rebuilt my kernel again normally, as I would.
I use snd-hda-intel for my Nvidia-chipset based sound card.

cat /proc/asound/cards:
Code: [Select]

 0 [Dummy          ]: Dummy - Dummy
                      Dummy 1
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xb0000000 irq 19


lspci:
Code: [Select]

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51 [Geforce 6150 Go] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)

uname -a:
Code: [Select]
Linux Dixie 2.6.23 #5 Wed Oct 10 19:48:33 PDT 2007 x86_64 AMD Turion(tm) 64 Mobile Technology MK-36 AuthenticAMD GNU/Linux
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

Odin

  • Spam Killer
  • *
  • Posts: 1767
  • Turrets: +113/-204
    • My Website
ALSA has gone insane.
« Reply #1 on: October 23, 2007, 04:57:58 am »
Are you running Gutsy? I've heard the ALSA drivers have broken some games.
Logged

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« Reply #2 on: October 23, 2007, 05:15:00 am »
Umm....maybe you missed something.

It's Gentoo 2007.1 amd64.
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

next_ghost

  • Posts: 892
  • Turrets: +3/-6
ALSA has gone insane.
« Reply #3 on: October 23, 2007, 07:01:37 pm »
New kernel means alsalib rebuild. Read what emerge says. :roll:
Logged
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.

Caveman

  • Guest
Re: ALSA has gone insane.
« Reply #4 on: October 23, 2007, 08:53:47 pm »
Quote from: "imperiumZero"
alsa-lib-1.0.15_rc2, kernel 2.6.23 amd64


How much do you get paid to run unstable soft, and how much do you pay us for trouble shooting?
Logged

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« Reply #5 on: October 24, 2007, 03:17:12 am »
And I forgot to mention, I went thorough EVERY ebuild of alsa-lib (after EVERY kernel recompile.) None worked, and that "Dummy Device is still there.
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

Caveman

  • Guest
ALSA has gone insane.
« Reply #6 on: October 24, 2007, 03:58:02 am »
then why don't you kill it from your asound.rc?
Logged

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« Reply #7 on: October 24, 2007, 04:12:07 am »
I tried setting a manual asound.conf in /etc to force the use of the #1 Nvidia Device which now makes sound work for everything, other that Tremulous. maybe it's SDL?

And yes, I quit every application, and even started tremulous through X by itself and still no dice.

fuser also shows in every situation that /dev/dsp isn't being used.
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

Caveman

  • Guest
ALSA has gone insane.
« Reply #8 on: October 24, 2007, 04:43:00 am »
/dev/dsp is OSS... do you have snd-pcm-oss loaded?
Logged

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« Reply #9 on: October 24, 2007, 05:21:53 am »
Quote from: "Caveman"
/dev/dsp is OSS... do you have snd-pcm-oss loaded?

It's built into the kernel at the moment.
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

Caveman

  • Guest
ALSA has gone insane.
« Reply #10 on: October 24, 2007, 06:53:13 am »
uhm.... why?
That'll only server to demand a reboot as soon as you change anything.
Logged

next_ghost

  • Posts: 892
  • Turrets: +3/-6
ALSA has gone insane.
« Reply #11 on: October 24, 2007, 02:54:06 pm »
Quote from: "imperiumZero"
and that "Dummy Device is still there.


Because your kernel is configured to provide a dummy device :roll:
Logged
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.

imperiumZero

  • Posts: 118
  • Turrets: +0/-4
ALSA has gone insane.
« Reply #12 on: October 25, 2007, 01:29:08 am »
Quote from: "next_ghost"
Quote from: "imperiumZero"
and that "Dummy Device is still there.


Because your kernel is configured to provide a dummy device :roll:

Do you know how to read? I already said that even with alsa COMPLETELY REMOVED FROM THE KERNEL, it still showed up.
Logged
lt;kevlarman> because microsoft's drivers are absolutely horrible that couldn't accelerate glxgears if they tried

Caveman

  • Guest
ALSA has gone insane.
« Reply #13 on: October 25, 2007, 08:47:14 am »
Quote from: "imperiumZero"

Do you know how to read?


I guess that's it then.
Take a look at the title of this here page. Does it say Tremulous or Linux?

Guess what?

Take the kernel documentation and learn how to read.
Logged

next_ghost

  • Posts: 892
  • Turrets: +3/-6
ALSA has gone insane.
« Reply #14 on: October 25, 2007, 01:09:43 pm »
Quote from: "imperiumZero"
Do you know how to read? I already said that even with alsa COMPLETELY REMOVED FROM THE KERNEL, it still showed up.


orly? Where does it come from then if the whole sound subsystem is diked out? If you have /proc/asound, you DO have ALSA in your kernel :roll:
Logged
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.
Pages: [1]   Go Up