Bugzilla – Bug 121869
standard sound card not working after booting SUSE 10.0 Live DVD
Last modified: 2006-04-25 15:07:12 UTC
The standard soundchip (description follows) is not functioning after booting from Live DVD. It works only after configuring it manually with YaST2. A live system for desktops should at least show sound capabilities with standard sound chips. Therefore a "CRITICAL" error. noname:/home/linux # hwinfo --sound 15: PCI 02.7: 0401 Multimedia audio controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1039_7012 Unique ID: 1sCg.t4EpD1HCpmC SysFS ID: /devices/pci0000:00/0000:00:02.7 SysFS BusID: 0000:00:02.7 Hardware Class: sound Model: "ASRock In Sound Controller" Vendor: pci 0x1039 "Silicon Integrated Systems Corp." Device: pci 0x7012 "Sound Controller" SubVendor: pci 0x1849 "ASRock Incorporation" SubDevice: pci 0x7012 Revision: 0xa0 Driver: "Intel ICH" I/O Ports: 0xd800-0xd8ff (rw) I/O Ports: 0xd400-0xd47f (rw) IRQ: 5 (141 events) Module Alias: "pci:v00001039d00007012sv00001849sd00007012bc04sc01i00" Driver Info #0: Driver Status: snd_intel8x0 is active Driver Activation Cmd: "modprobe snd_intel8x0" Driver Info #1: Driver Status: i810_audio is not active Driver Activation Cmd: "modprobe i810_audio" Config Status: cfg=yes, avail=yes, need=no, active=unknown
Torsten, it's your baby...
Yes, but depends on working hotplug. You wrote a patch for the 9.3 LiveDVDs, which I assumed got incorporated into the current development :-( Forwarding to udev maintainer.
Created attachment 52096 [details] Fix that worked on 9.3 Live DVDs
*** Bug 121849 has been marked as a duplicate of this bug. ***
I am really amazed how SUSE/Novell can consider this a "NORMAL" bug. One of the main goals of such live DVD is to convince new customers to switch to Linux, isn't it? So anyone using Windows audio capabilities will enjoy the silence as soon as he/she tries out this live DVD, playing CDs, sound files etc.? If this is "NORMAL" noone will believe that SUSE likes to get market share off the Windows market.
Fixed in 10.1