Bug 131514 - YaST cannot configure sound.
Summary: YaST cannot configure sound.
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-30 17:38 UTC by Aaron Williams
Modified: 2006-05-17 09:09 UTC (History)
1 user (show)

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


Attachments
YaST2 log file (8.08 KB, text/plain)
2005-10-30 17:40 UTC, Aaron Williams
Details
File from /etc/modprobe.d/sound (60 bytes, text/plain)
2005-11-01 07:29 UTC, Aaron Williams
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2005-10-30 17:38:46 UTC
YaST insists my web cam is "Configured as sound card number" with "Driver snd-ens1370" which is incorrect.  My PCI sound card, a Sound Blaster PCI 128 which is listed as ES1370 says it is not configured.  The 1370 driver should be used for the ES1370.  If I attempt to edit or delete any of the items, YaST immediately terminates.  No reason for the termination is recorded in y2log
Comment 1 Aaron Williams 2005-10-30 17:40:13 UTC
Created attachment 55986 [details]
YaST2 log file
Comment 2 Ladislav Slezák 2005-11-01 06:37:12 UTC
Please, attach 'hwinfo --sound' output.
Comment 3 Aaron Williams 2005-11-01 06:54:39 UTC
# hwinfo --sound
14: PCI 09.0: 0401 Multimedia audio controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_1274_5000
  Unique ID: WL76.xqKuJL067p4
  SysFS ID: /devices/pci0000:00/0000:00:09.0
  SysFS BusID: 0000:00:09.0
  Hardware Class: sound
  Model: "Ensoniq ES1370 [AudioPCI]"
  Vendor: pci 0x1274 "Ensoniq"
  Device: pci 0x5000 "ES1370 [AudioPCI]"
  SubVendor: pci 0x4942
  SubDevice: pci 0x4c4c
  Revision: 0x01
  I/O Ports: 0xc800-0xc83f (rw)
  IRQ: 11 (46841 events)
  Module Alias: "pci:v00001274d00005000sv00004942sd00004C4Cbc04sc01i00"
  Driver Info #0:
    Driver Status: es1370 is not active
    Driver Activation Cmd: "modprobe es1370"
  Driver Info #1:
    Driver Status: snd_ens1370 is not active
    Driver Activation Cmd: "modprobe snd_ens1370"
  Config Status: cfg=yes, avail=yes, need=no, active=unknown
Comment 4 Aaron Williams 2005-11-01 06:58:17 UTC
Note that I am attempting to work around this... I have forced a reinstall of yast2-sound and alsa, but still no luck.  Where does YaST store the configuration information?
Comment 5 Ladislav Slezák 2005-11-01 07:19:17 UTC
The sound configuration is stored in /etc/modprobe.d/sound file and in /etc/sysconfig/hardware/hwcfg-* files (use grep -H sound /etc/sysconfig/hardware/hwcfg-* to find the right ones).

If you want to reset the configuration completely then remove the files and unoad ALSA drivers (rcalsasound unload). Please, attach the files here before removing them! Then you can start the yast module and configure the soundcard from scratch.
Comment 6 Aaron Williams 2005-11-01 07:29:37 UTC
Created attachment 56065 [details]
File from /etc/modprobe.d/sound
Comment 7 Aaron Williams 2005-11-01 07:32:15 UTC
I already deleted /etc/sysconfig/hardware/hwcfg-bus-pci-00:09:... which contained the sound information.  I could not find anything amiss with it.  I see no reference to the USB audio device YaST2 sees, which is my USB webcam.  Unplugging that does not help.
Comment 8 Aaron Williams 2005-11-01 07:38:25 UTC
After running rcalsasound unload and deleting the files everything appears to have worked.
Comment 9 Ladislav Slezák 2005-11-01 11:30:34 UTC
Just to get more info about the issue: Did you do an update or full installation? What did you do exactly?
Comment 10 Aaron Williams 2005-11-01 16:34:57 UTC
I did an update, which may be why I am having so many problems.  I am still seeing a problem where Alsa does not load the kernel module when booting up, but if I run /etc/init.d/alsasound restart that seems to fix it, though I'm getting frequent crashes in knotify.  Though perhaps I should open another bug for this.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1095242656 (LWP 6693)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x40007c5c in do_lookup_x () from /lib/ld-linux.so.2
#5  0x40007fd7 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#6  0x4000b4f1 in fixup () from /lib/ld-linux.so.2
#7  0x4000b2c0 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#8  0x417e9032 in snd_pcm_hw_open () from /usr/lib/libasound.so.2
#9  0x417e9360 in _snd_pcm_hw_open () from /usr/lib/libasound.so.2
#10 0x417d9274 in snd_pcm_free () from /usr/lib/libasound.so.2
#11 0x417d9be3 in snd_pcm_open_slave () from /usr/lib/libasound.so.2
#12 0x417f9a66 in _snd_pcm_plug_open () from /usr/lib/libasound.so.2
#13 0x417d9274 in snd_pcm_free () from /usr/lib/libasound.so.2
#14 0x417d9926 in snd_pcm_free () from /usr/lib/libasound.so.2
#15 0x4003e69e in aKode::ALSASink::open ()
   from /opt/kde3/lib/libakode_alsa_sink.so
#16 0x4177ad9f in aKode::AutoSink::open () from /opt/kde3/lib/libakode.so.1
#17 0x4177fa92 in aKode::Player::open () from /opt/kde3/lib/libakode.so.1
#18 0x40030808 in KDE::Multimedia::aKodePlayer::aKodePlayer ()
   from /opt/kde3/lib/kde3/kdemm_akode.so
#19 0x4003142a in KDE::Multimedia::aKodeBackend::createPlayer ()
   from /opt/kde3/lib/kde3/kdemm_akode.so
#20 0x4005a369 in KDE::Multimedia::Factory::createPlayer ()
   from /opt/kde3/lib/libkdemm.so.0
#21 0x4005b8d3 in KDE::Multimedia::SimplePlayer::SimplePlayer ()
   from /opt/kde3/lib/libkdemm.so.0
#22 0x4004952e in ?? () from /opt/kde3/lib/libkdeinit_knotify.so
#23 0x081c8190 in ?? ()
#24 0xbf87ba34 in ?? ()
#25 0x00000000 in ?? ()
#26 0xbf87b99c in ?? ()
#27 0x001a8180 in ?? ()
#28 0x40fb1650 in vtable for QGArray () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x081a85d8 in ?? ()
#30 0xbf87ad14 in ?? ()
#31 0xbf87ad54 in ?? ()
#32 0xbf87ad14 in ?? ()
#33 0x0001ad28 in ?? ()
#34 0x40df7ec4 in QCString::toInt () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x4004b620 in kdemain () from /opt/kde3/lib/libkdeinit_knotify.so
#36 0x4004c7dc in kdemain () from /opt/kde3/lib/libkdeinit_knotify.so
#37 0x40833620 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#38 0x40834c20 in DCOPClient::find () from /opt/kde3/lib/libDCOP.so.4
#39 0x40835278 in DCOPClient::find () from /opt/kde3/lib/libDCOP.so.4
#40 0x4084250d in KDE_IceProcessMessages () from /opt/kde3/lib/libDCOP.so.4
#41 0x4082d2f9 in DCOPClient::processSocketData ()
   from /opt/kde3/lib/libDCOP.so.4
#42 0x408359a6 in DCOPClient::qt_invoke () from /opt/kde3/lib/libDCOP.so.4
#43 0x40b50159 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#44 0x40b50731 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#45 0x40e91700 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#46 0x40b6f430 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#47 0x40af09f1 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#48 0x40af1369 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#49 0x4077797e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#50 0x40ae483d in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#51 0x40a9ede3 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#52 0x40b07903 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#53 0x40b077e6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#54 0x40af033f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#55 0x4004a254 in kdemain () from /opt/kde3/lib/libkdeinit_knotify.so
#56 0x41374ea0 in __libc_start_main () from /lib/tls/libc.so.6
#57 0x080485f1 in ?? ()
Comment 11 Ladislav Slezák 2006-04-28 07:19:46 UTC
Please, do not forget to change the status back to ASSIGNED when you provide requested info!

Anyway, the product is too old, could you test the latest 10.1 build (currently RC3)?
Comment 12 Ladislav Slezák 2006-05-17 09:09:22 UTC
No information provided, if it still happens in 10.1(final) then reopen please.