Bug 113239 - No oss devices
Summary: No oss devices
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 3
Hardware: IA64 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-26 09:22 UTC by Andreas Schwab
Modified: 2005-09-15 19:39 UTC (History)
2 users (show)

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


Attachments
lsmod after rcalsound restart (2.15 KB, text/plain)
2005-08-26 11:44 UTC, Andreas Schwab
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Schwab 2005-08-26 09:22:23 UTC
/dev/mixer and /dev/dsp are missing.
Comment 1 Dr. Werner Fink 2005-08-26 10:08:35 UTC
What does missing mean?  No device file or the links are missed

/suse/werner> ll /dev/mixer
lrwxrwxrwx  1 root root 6 Aug 24 11:57 /dev/mixer -> mixer0
/suse/werner> ll /dev/dsp
lrwxrwxrwx  1 root root 4 Aug 24 11:57 /dev/dsp -> dsp0

or the driver is not loaded?
Comment 2 Takashi Iwai 2005-08-26 10:38:16 UTC
Check whether snd-pcm-oss module is loaded.  If it's there, create /dev/mixer
and /dev/dsp manually to check whether it works.

If it works indeed, the culprit might be udev/hal.  (Are you using ibook or
powerbook?)
Comment 3 Andreas Schwab 2005-08-26 11:40:58 UTC
I've just noticed that sound wasn't running, although configured (this is an 
update). 
 
# hwinfo --sound 
10: PCI a004.0: 0401 Multimedia audio controller                 
  [Created at pci.277] 
  UDI: /org/freedesktop/Hal/devices/pci_1319_801 
  Unique ID: 3rad.GGNWTM9aXXC 
  SysFS ID: /devices/pci0000:a0/0000:a0:04.0 
  SysFS BusID: 0000:a0:04.0 
  Hardware Class: sound 
  Model: "Fortemedia Xwave QS3000A [FM801]" 
  Vendor: pci 0x1319 "Fortemedia, Inc" 
  Device: pci 0x0801 "Xwave QS3000A [FM801]" 
  SubVendor: pci 0x1319 "Fortemedia, Inc" 
  SubDevice: pci 0x1319  
  Revision: 0xb2 
  I/O Ports: 0xa000-0xbfff (rw) 
  Module Alias: "pci:v00001319d00000801sv00001319sd00001319bc04sc01i00" 
  Driver Info #0: 
    Driver Status: forte is not active 
    Driver Activation Cmd: "modprobe forte" 
  Driver Info #1: 
    Driver Status: snd_fm801 is not active 
    Driver Activation Cmd: "modprobe snd_fm801" 
  Config Status: cfg=yes, avail=yes, need=no, active=unknown 
# cat /etc/modprobe.d/sound  
options snd-fm801 enable=1 index=0 
 
 
 
# YaST2: sound system dependent part 
# 
alias sound-slot-0 snd-card-0 
alias sound-service-0-0 off 
alias sound-slot-1 off 
alias sound-service-1-0 off 
alias sound-slot-2 off 
alias sound-service-2-0 off 
alias sound-slot-3 off 
alias sound-service-3-0 off 
alias char-major-14 off 
 
# Alsa sound support.  
# Warning: please don't modify comments over aliases 'snd-card-#' 
alias char-major-116 snd 
options snd cards_limit=1 major=116 
# 3rad.G_8shJkW852:Xwave QS3000A [FM801] 
alias snd-card-0 snd-fm801 
 
Comment 4 Andreas Schwab 2005-08-26 11:43:40 UTC
Even after rcalsasound restart the devices are missing and snd-pcm-oss is 
indeed not loaded. 
Comment 5 Andreas Schwab 2005-08-26 11:44:38 UTC
Created attachment 47758 [details]
lsmod after rcalsound restart
Comment 6 Takashi Iwai 2005-08-26 12:30:21 UTC
Do you have /etc/sysconfig/hardware/hwcfg-bus-pci* including snd-fm801 module?

alsasound start won't load the modules by itself (although restart/reload does).
The lack of snd-pcm-oss after restart will be fixed in the next update.
Comment 7 Andreas Schwab 2005-08-26 13:49:19 UTC
No, I don't. 
Comment 8 Takashi Iwai 2005-08-26 14:05:53 UTC
Strange, yast2 should create a hwcfg file there.
I guess reconfiguring sound via yast2 or alsaconf should help.
Comment 9 Andreas Schwab 2005-08-26 14:42:06 UTC
This was an update (with y2pmsh). 
Comment 10 Takashi Iwai 2005-08-26 16:16:58 UTC
Well, basically yast should take care of this update route, but apparently it's not.
Anyway, try to run alsaconf again to reconfigure the device.

Alternatively, I can add the module loading back to alsasound init script with a
check of sysconfig variable.  But I don't think it's needed if reconfiguring the
device solves the problem.
Comment 11 Gerald Pfeifer 2005-08-31 10:41:18 UTC
We'll definitely want this to work with the new shiny ia64 workstations to
arrive soon, don't we? ;-)
Comment 12 Takashi Iwai 2005-08-31 10:51:58 UTC
The system should work.  It's just a problem of updating.  The configuration
isn't completely copied if it wasn't set up via yast.

As mentioned above, it should be OK once if you reconfigure the sound device on
the new system.
Comment 13 Takashi Iwai 2005-09-15 19:39:22 UTC
I set this to WONTFIX since there is a workaround for the brokenness by the
update path.