Bug 176659 - Sound Card configuration
Summary: Sound Card configuration
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Sound (show other bugs)
Version: Final
Hardware: i386 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 148376
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-17 22:52 UTC by Johannes Nohl
Modified: 2007-02-26 14:18 UTC (History)
4 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Nohl 2006-05-17 22:52:25 UTC
+++ This bug was initially created as a copy of Bug #148376 +++

OLD DESCRIPTION: 

At installation, I configured the sound card correctly and it works fine. But after the system starts KDE, the soundcard isn't available (not installed).
A simple rcalsasound restart helps and the soundcard is available again. [...]

MY ADDITION: 

This is also true for Gnome! This is identical to a problem with 10.0 but not with 9.3 (I think it was reported before). I'm using emu10k1 but I read about the problem with other modules. 
If running aplay foo.wav in real console (Alt+Ctrl+Fn from X-Window) sound is playing. Same command from console window inside X-Window is saying "underrun" and stops (no difference as root except it quits without error message). No gnome-sound-app produces sound although it plays (without error message). Mixer-settings are correct. 
After doing rcalsasound restart / reload (not only rcalsasound start / rcalsasound stop and then rcalsasound start) everything works without anything further to do (gnome-volume-ma is restarting itself). 

In 10.0 I had the problem with KDE and Gnome, now (after clean install) with gnome (KDE not tested). 

The former report was closed, so what logs etc. can I provide to proove?
Comment 1 Takashi Iwai 2006-05-19 10:16:57 UTC
If it works fine on Linux console, it's somehow related with GNOME.
Passed to GNOME guys.
Comment 2 JP Rosevear 2006-05-19 16:22:40 UTC
Have you seen this at all Tim, Kelli, Pete?
Comment 3 Pete Goodall 2006-05-19 18:13:55 UTC
I reported Bug 176994 - Sound not configured after upgrade.  That may be related.  Don't know.  Though I just did a fresh install and it works just fine.
Comment 4 JP Rosevear 2006-05-20 15:35:20 UTC
Johannes could you paste the complete console output of aplay foo.wav?
Comment 5 JP Rosevear 2006-05-21 16:18:16 UTC
Also, could you attach /var/log/messages right after you try to play.
Comment 6 Johannes Nohl 2006-05-21 16:19:50 UTC
aplay is saying (beside bitrate): "underrun!!! (at least 0,038 ms long)"

again this is in console window, it works in linux console without error report...

Is it important that my card is *not* recognized by yast sound automatically? I have to choose the module by hand. It is a so called "Soundblaster Live! Player 1024" (which is based emu10k1 - boot.msg: "<6>gameport: EMU10K1 is pci0000:00:0a.1/gameport0, io 0x9800, speed 1325kHz"). 
I could test if problem exists if card is auto-detect; if you tell me how to add my cards info to database.

In addition it is not possible to edit sound settings after first install, resulting in crash of yast sound (y2.log tells "card not found"). But this maybe another bug I think I read about.

AfaIk rcalsasound is inserting kernel modules so I add some additional ("lsmod | grep snd")
After normal boot into gnome - sound not working, mixer loaded:

snd_pcm_oss            42752  0
snd_mixer_oss          16512  1 snd_pcm_oss
snd_emu10k1           104196  1
snd_rawmidi            23552  1 snd_emu10k1
snd_ac97_codec         82848  1 snd_emu10k1
snd_ac97_bus            2176  1 snd_ac97_codec
snd_pcm                80136  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_seq_device          7948  2 snd_emu10k1,snd_rawmidi
snd_timer              20868  2 snd_emu10k1,snd_pcm
snd_page_alloc          9608  2 snd_emu10k1,snd_pcm
snd_util_mem            4736  1 snd_emu10k1
snd_hwdep               8836  1 snd_emu10k1
snd                    51076  12 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_util_mem,snd_hwdep
soundcore               8672  1 snd

Now after I did rcalsasound reload - sound works (mixer-panel get reloaded now showing additional OSS-Sigmatel STAC9721 (?!)). script is saying it is loading emu10k1: 

snd_pcm_oss            42752  0
snd_mixer_oss          16512  2 snd_pcm_oss
snd_emu10k1           104196  1
snd_rawmidi            23552  1 snd_emu10k1
snd_ac97_codec         82848  1 snd_emu10k1
snd_ac97_bus            2176  1 snd_ac97_codec
snd_pcm                80136  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_seq_device          7948  2 snd_emu10k1,snd_rawmidi
snd_timer              20868  2 snd_emu10k1,snd_pcm
snd_util_mem            4736  1 snd_emu10k1
snd_hwdep               8836  1 snd_emu10k1
snd                    51076  10 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_util_mem,snd_hwdep
snd_page_alloc          9608  2 snd_emu10k1,snd_pcm
soundcore               8672  2 snd

- - - - - -
What to do?
Comment 7 Johannes Nohl 2006-05-21 16:32:55 UTC
addition for comment #5:

/var/log/message is saying (326x when starting gnome and every time aplay is run):

ALSA sound/core/pcm_lib.c:157: BUG: stream = 0, pos = 0xffbbe7, buffer size = 0x4000, period size = 0x100

No entry in message after rcalsasound reload or if run in console. 
Comment 8 JP Rosevear 2006-05-21 18:08:23 UTC
Well, gnome does try to play a sound on login, so that could be triggering the bug.  Try restarting alsasound and then esdplay /opt/gnome/share/sounds/startup3.wav after you log into gnome to check if that replicates the bug.  

I take it the kernel modules listed before you log in to gnome look correct?

You say you get the kernel error in /var/log/messages whenever you run aplay, is that even when you play on the command line?
Comment 9 JP Rosevear 2006-05-21 18:09:19 UTC
Takashi could the sound module here just be getting unloaded because of the above bug?  Looking at the kernel code the ALSA error in #7 seems pretty deep in the kernel, although its not clear to me exactly what would trigger it.
Comment 10 Johannes Nohl 2006-05-22 22:10:07 UTC
To comment #8:

With lsmod I wanted to show that modules are loaded correct after boot. Difference after eload although is that snd_pcm_oss is used by two not one (see above). 

AFTER rcalsasound reload esdplay as well as aplay work without problem. Problem occurs ONLY inside gnome (not on the "real" linux console, Alt+Ctrl+F1) and ONLY before doing rcalsasound reload (the "working"-state after reload survives even a suspend to disk!). It is NOT about different init states; inside init 5 with running gnome, it's working in linux console (like beeing in init 3). 
Message still says: ALSA sound/core/pcm_lib.c:157: BUG: stream = 0, pos = 0xffbbe7, buffer size = 0x4000, period size = 0x1000

To answer your question clearly: errors in message occure in terminal window of gnome while at the same time everything is ok out of console. 

esdplay startup.mp3 throws about 200 lines in message as well as aplay (only 10 lines, diffence maybe "period size esdplay=100, aplay=1000). 

To comment #9:
Do you really think it's a kernel bug? Why is it working then after reload? I myself (but I really don't have a clue about alsa modules) think it could be the problem that hardware detection isn't working. 
Can you - you're the professional here - tell me how I add the PCI vendor- and model-ID to alsa hardware db? Since my emu10k1 is exotic bulk ware the difference may be in hardware detection. 
Comment 11 Johannes Nohl 2006-05-23 01:08:05 UTC
Well I can't see a nexus but maybe it helps you:

I have problems with framebuffer, too. Didn't take this for serious. But now I ran "hwinfo --gfxcard" and (strange!) my sound card SB Live! ct 4832 is listed!!
I immediately did cross check "hwinfo --sound" resulting to an empty list. 

Is this related? Should I start an new bug report??
Comment 12 JP Rosevear 2006-05-23 01:59:41 UTC
Well, this leads me to two thoughts, conflicting IRQs and bogus pci ids.
Comment 13 Takashi Iwai 2006-05-23 11:11:00 UTC
The kernel messages in comment #7 implies that the hardware is not in order.  Usually I suspect a hardware problem in such a case.  But what I don't understand is that the problem happens only after logging to GNOME/KDE.

Might it be a problem with video driver?
Comment 14 JP Rosevear 2006-05-23 12:51:48 UTC
What is the output of hwinfo --gxfcard?  Lets check the vendor and device id.  

Lowering severity, pretty sure this is an isolated case.
Comment 15 Johannes Nohl 2006-05-23 16:53:00 UTC
For comment #14: 

Maybe it's realy isolated to my case... But I have no idea how to change. Anyway this explain why problem occur in 10.0 and 10.1.

hwinfo --gfxcard
18: PCI 0a.0: 0300 VGA compatible controller (VGA)
  [Created at pci.300]
  UDI: /org/freedesktop/Hal/devices/pci_1102_2
  Unique ID: bSAa.Ena9egpTSgD
  SysFS ID: /devices/pci0000:00/0000:00:0a.0
  SysFS BusID: 0000:00:0a.0
  Hardware Class: graphics card
  Model: "Creative CT4832 SBLive! Value"
  Vendor: pci 0x1102 "Creative Labs"
  Device: pci 0x0002 "SB Live! EMU10k1"
  SubVendor: pci 0x1102 "Creative Labs"
  SubDevice: pci 0x8027 "CT4832 SBLive! Value"
  Revision: 0x08
  Driver: "EMU10K1_Audigy"
  I/O Ports: 0xa000-0xa01f (rw,disabled)
  IRQ: 5 (no events)
  Module Alias: "pci:v00001102d00000002sv00001102sd00008027bc00sc01i00"
  Driver Info #0:
    Driver Status: emu10k1 is not active
    Driver Activation Cmd: "modprobe emu10k1"
  Driver Info #1:
    Driver Status: snd_emu10k1 is active
    Driver Activation Cmd: "modprobe snd_emu10k1"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

22: PCI(AGP) 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.300]
  UDI: /org/freedesktop/Hal/devices/pci_10de_110
  Unique ID: VCu0.jUxka8NKM_8
  Parent ID: vSkL.BQdp9bG_qCD
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GeForce2 MX/MX 400"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0110 "GeForce2 MX/MX 400"
  Revision: 0xa1
  Driver: "nvidia"
  Memory Range: 0xd6000000-0xd6ffffff (rw,non-prefetchable)
  Memory Range: 0xd8000000-0xdfffffff (rw,prefetchable)
  Memory Range: 0xd7ff0000-0xd7ffffff (ro,prefetchable,disabled)
  IRQ: 11 (808119 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v000010DEd00000110sv00000000sd00000000bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: nv
  Driver Info #1:
    XFree86 v4 Server Module: nvidia
    3D Support: yes
    Color Depths: 16
    Extensions:
    Options:
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #11 (PCI bridge)

Primary display adapter: #22



For comment #12: Video (IRQ 11) and sound (IRQ 5) don't seem to share same IRQ!

lspci -nv
00:0a.0 VGA compatible unclassified device: Creative Labs SB Live! EMU10k1 (rev 08)
        Subsystem: Creative Labs CT4832 SBLive! Value
        Flags: bus master, medium devsel, latency 32, IRQ 5
        I/O ports at a000 [disabled] [size=32]
        Capabilities: [dc] Power Management version 1

00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 08)
        Subsystem: Creative Labs Gameport Joystick
        Flags: bus master, medium devsel, latency 32
        I/O ports at 9800 [size=8]
        Capabilities: [dc] Power Management version 1

01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) (prog-if 00 [VGA])
        Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 11
        Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        [virtual] Expansion ROM at d7ff0000 [disabled] [size=64K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
Comment 16 JP Rosevear 2006-05-23 17:48:03 UTC
 Perhaps its simply listed because it has input devices in this case?  Steffen?
Comment 17 Steffen Winterfeldt 2006-05-24 07:30:48 UTC
The device class is 'VGA compatible unclassified device', so it
naturally shows up as graphics card and not as sound card.

To me it looks like a hardware problem. Maybe that SB Live doesn't work
in Johannes' mainboard?
Comment 18 JP Rosevear 2007-02-09 21:39:06 UTC
I think this should probably go to Takeshi, looking back the card isn't being recognized as a sound card.
Comment 19 Takashi Iwai 2007-02-26 14:18:57 UTC
It must be a hardware problem if it's reported as a video device.  No way to fix this from the kernel driver side...