[SLE] Creative Labs PCI128
Yes, I know it has been discussed many times. Yes, I already checked the archive. Yes I already checked in deja news. The problem: I can play CD audio with this card but I cannot play any .wav files nor I can have any system sound in KDE. This is what I get when I do a wavplay /usr/share/sounds/wav/gong.wav Pathname: /usr/share/sounds/wav/gong.wav Sampling Rate: 11025 Hz Mode: Mono Samples: 143343 Bits: 8 Invalid argument: Audio block size (64 bytes) In the archive I found that someone else had this problem (system sounds in KDE) and he said that he could solve it but didn't post the details. If someone knows how to solve this problem (I can play CD audio but I cannot play wav files) ... Thanks Maurizio -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 1 Mar 2000, Maurizio Firmani wrote:
Yes, I know it has been discussed many times. Yes, I already checked the archive. Yes I already checked in deja news.
The problem: I can play CD audio with this card but I cannot play any .wav files nor I can have any system sound in KDE. This is what I get when I do a wavplay /usr/share/sounds/wav/gong.wav
Pathname: /usr/share/sounds/wav/gong.wav Sampling Rate: 11025 Hz Mode: Mono Samples: 143343 Bits: 8
Invalid argument: Audio block size (64 bytes)
In the archive I found that someone else had this problem (system sounds in KDE) and he said that he could solve it but didn't post the details. If someone knows how to solve this problem (I can play CD audio but I cannot play wav files) ...
Thanks
Maurizio
Easy. Nothing wrong with PCI128 or PCI64. It works great with OSS and ALSA. Your problem's not Linux nor PCI128. It's wavplay. I had the same problem with PCI64. So try a different wav-player, like "play" that comes with ALSA package (Suse 6.3). KDE needed some stabbing, too. See my earlier message about the topic (PCI64) in this mailing list. --Jyry -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, Mar 01, 2000 at 12:04:02PM +0200, Jyry Kuukkanen wrote:
Easy. Nothing wrong with PCI128 or PCI64. It works great with OSS and ALSA. Your problem's not Linux nor PCI128. It's wavplay. I had the same problem with PCI64.
Speaking of ALSA, I decided to try it out the other day.... ooops. Didn't work. Lot' of "*** Unresolved symbols in /lib/modules/2.2.13...." messages about the modules from the rpm. Is this a common problem, or do I have somethin hosed? -- Brad Shelton On Line Exchange http://online-isp.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 1 Mar 2000, Brad Shelton wrote:
On Wed, Mar 01, 2000 at 12:04:02PM +0200, Jyry Kuukkanen wrote:
Easy. Nothing wrong with PCI128 or PCI64. It works great with OSS and ALSA. Your problem's not Linux nor PCI128. It's wavplay. I had the same problem with PCI64.
Speaking of ALSA, I decided to try it out the other day.... ooops. Didn't work. Lot' of "*** Unresolved symbols in /lib/modules/2.2.13...." messages about the modules from the rpm.
Is this a common problem, or do I have somethin hosed?
-- Brad Shelton On Line Exchange http://online-isp.com
I confed my sound support to be compiled as module, same for ES1371 driver. It might be a good idea trying the same and then make clean make dep make make modules make install make modules_install reboot depmod -a modprobe es1371 That should do the trick, hopefully :-) --Jyry -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, Mar 02, 2000 at 10:54:36AM +0200, Jyry Kuukkanen wrote:
On Wed, 1 Mar 2000, Brad Shelton wrote:
On Wed, Mar 01, 2000 at 12:04:02PM +0200, Jyry Kuukkanen wrote:
Easy. Nothing wrong with PCI128 or PCI64. It works great with OSS and ALSA. Your problem's not Linux nor PCI128. It's wavplay. I had the same problem with PCI64.
Speaking of ALSA, I decided to try it out the other day.... ooops. Didn't work. Lot' of "*** Unresolved symbols in /lib/modules/2.2.13...." messages about the modules from the rpm.
Is this a common problem, or do I have somethin hosed?
-- Brad Shelton On Line Exchange http://online-isp.com
I confed my sound support to be compiled as module, same for ES1371 driver. It might be a good idea trying the same and then
make clean make dep make make modules make install make modules_install reboot depmod -a modprobe es1371
That should do the trick, hopefully :-)
Hmmm. I am using a stock kernel with reiser support and the only modules I use are for sound, ethernet and SCSI. The ALSA package puts the modules into the modules directory and when I did a depmod -a I got a whole SCREEN full of "*** Unresolved symbols in /lib/modules/2.2.13/misc/snd-*.o" scrolling off the screen on a "158 Columns by 72 Lines" terminal session. `*8-| So. I ask again, > > Is this a common problem, or do I have somethin hosed? Do I need to add some module to the mix that I haven't added already... or remove one? Thanks for the thoughts so far. -- Brad Shelton On Line Exchange http://online-isp.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Brad Shelton (bshelton@online-isp.com) [20000302 19:12]:
Hmmm. I am using a stock kernel with reiser support and the only modules I use are for sound, ethernet and SCSI.
UP or SMP? The modules from the rpm only work on UP systems. For starting
alsa, first run alsaconf. That will configure your card and put the
appropriate entries in your /etc/modules.conf. Check that
/sbin/init.d/alsasound exists and that links in /sbin/init.d/rc[23].d to it
exist. For manually starting or stopping ALSA, use 'rcalsasound start' or
'rcalsasound stop'.
Philipp
--
Philipp Thomas
On Thu, Mar 02, 2000 at 10:08:54PM +0100, Philipp Thomas wrote:
* Brad Shelton (bshelton@online-isp.com) [20000302 19:12]:
Hmmm. I am using a stock kernel with reiser support and the only modules I use are for sound, ethernet and SCSI.
UP or SMP? The modules from the rpm only work on UP systems. For starting alsa, first run alsaconf. That will configure your card and put the appropriate entries in your /etc/modules.conf. Check that /sbin/init.d/alsasound exists and that links in /sbin/init.d/rc[23].d to it exist. For manually starting or stopping ALSA, use 'rcalsasound start' or 'rcalsasound stop'.
Single processor. Basically a stock system, however the stock kernel has OSS
support compiled as a module. Is this a problem?
Here's the result of my attempts to run alsaconf:
========================================
----------------------------------------------------------------------
- Select card -
- ------------------------------------------------------------------ -
- - 0 No_more_cards - -
- - 0x1 Gravis_UltraSound_Classic - -
- - 0x2 Gravis_UltraSound_Extreme - -
- - 0x3 Gravis_UltraSound_ACE - -
- - 0x4 Gravis_UltraSound_MAX - -
- - 0x5 Gravis_UltraSound_PnP - -
- - 0x5 Dynasonic_3-D/Pro - -
- - 0x6 SoundBlaster_1.0 - -
- - 0x7 SoundBlaster_2.0 - -
- - 0x8 SoundBlaster_Pro - -
- - 0x9 SoundBlaster_16_(PnP) - -
- - 0xa SoundBlaster_AWE_32_(PnP) - -
- - 0xa SoundBlaster_AWE_64_PnP << ====== My Card - -
- ----(+)----------------------------------------------------------- -
----------------------------------------------------------------------
- < OK > <Cancel> -
----------------------------------------------------------------------
--------------------------------------------------
- Card identifier. -
- -
- ---------------------------------------------- -
- -CARD_1 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- IO port. -
- (0x220,0x240,0x260) -
- ---------------------------------------------- -
- 0x220 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- MPU IO port. -
- (0x300,0x330,-1) -
- ---------------------------------------------- -
- 0x330 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- EMU8000 synthesizer port. -
- (?) -
- ---------------------------------------------- -
- -1 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- IRQ. -
- (5,7,9,10) -
- ---------------------------------------------- -
- 5 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- 8-bit DMA. -
- (0,1,3) -
- ---------------------------------------------- -
- 1 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- Max. 8-bit DMA size in kB. -
- (4-64) -
- ---------------------------------------------- -
- 64 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- 16-bit DMA. -
- (5,6,7) -
- ---------------------------------------------- -
- 5 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- Max. 16-bit DMA size in kB. -
- (4-128) -
- ---------------------------------------------- -
- 128 - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
--------------------------------------------------
- Mic. Auto-Gain-Control -
- ---------------------------------------------- -
- - 0 Disable - -
- - 1 Enable - -
- ---------------------------------------------- -
--------------------------------------------------
- < OK > <Cancel> -
--------------------------------------------------
----------------------------------------------------------------------
- Select card -
- ------------------------------------------------------------------ -
- - 0 No_more_cards << ===== Now this choice - -
- - 0x1 Gravis_UltraSound_Classic - -
- - 0x2 Gravis_UltraSound_Extreme - -
- - 0x3 Gravis_UltraSound_ACE - -
- - 0x4 Gravis_UltraSound_MAX - -
- - 0x5 Gravis_UltraSound_PnP - -
- - 0x5 Dynasonic_3-D/Pro - -
- - 0x6 SoundBlaster_1.0 - -
- - 0x7 SoundBlaster_2.0 - -
- - 0x8 SoundBlaster_Pro - -
- - 0x9 SoundBlaster_16_(PnP) - -
- - 0xa SoundBlaster_AWE_32_(PnP) - -
- - 0xa SoundBlaster_AWE_64_PnP - -
- ----(+)----------------------------------------------------------- -
----------------------------------------------------------------------
- < OK > <Cancel> -
----------------------------------------------------------------------
--------------------------------------------------
- Do you want to modify /etc/modules.conf? -
--------------------------------------------------
- < Yes > < No > -
--------------------------------------------------
------------------------------------------------------------
- -
- -
- OK, 1 card(s) configured. -
- -
- ALSA CONFIGURATOR -
- -
- will prepare the card for playing now. -
- -
- Now I'll run 'rcalsasound start', then use I'll -
- use amixer to raise the 'Master' and 'PCM' volumes. -
- If you want to use the commandline-based mixer -
- amixer also, read the man page: 'man amixer' -
- -
------------------------------------------------------------
- < OK > -
------------------------------------------------------------
Loading driver:
Starting sound driver: snd-card-sbawe modprobe: Can't locate module snd-card-sbawe
done
alsactl: The soundcard 'CARD_1' was not found...
alsactl: The soundcard 'CARD_1' was not found...
Setting the PCM volume to 100% and the Master output volume to 50%
The ALSA sound driver was not detected in this system.
Could not initialize the mixer, the card was probably
not detected correctly.
Host: dartboard on Thu Mar 2 20:43:37
User: root in [~]
Root Command? #
=====================================
That's how the session went.
Here's what's in my /etc/modules.conf file:
--------8<------------
#
# Copyright (c) 1996-1999 SuSE GmbH Nuernberg, Germany. All rights reserved.
#
# Author: Hubert Mantel
On Thu, 02 Mar 2000, Brad Shelton wrote:
Single processor. Basically a stock system, however the stock kernel has OSS support compiled as a module. Is this a problem?
Sound is okay (preferred) as a module. It makes things like IO, DMA, etc to be addressed (in options lines).
Here's the result of my attempts to run alsaconf:
- - 0xa SoundBlaster_AWE_64_PnP << ====== My Card - -
As per the subject line, this is a mistake. Are we talking about two different cards now? Being the paranoid type, I usually build my own kernel within 6 operating hours of getting a machine running, especially when I plan on using external modules for something like ALSA. As part of the kernel-building procedure, I `rm -rf /lib/modules/$VER/*' to get rid of depmod nastiness. After this is done, and the new kernel has been built, installed, and booted, I begin the ALSA procedures, starting with the latest release from ftp.alsa-project.org, and building it myself. NOTE: The es137x family now has limited support for a Sequencer device, as of ALSA-0.5.x :]. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x121 | http://www.atipa.com _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, Mar 03, 2000 at 09:22:51AM -0600, Jon Pennington wrote:
On Thu, 02 Mar 2000, Brad Shelton wrote:
Single processor. Basically a stock system, however the stock kernel has OSS support compiled as a module. Is this a problem?
Sound is okay (preferred) as a module. It makes things like IO, DMA, etc to be addressed (in options lines).
Here's the result of my attempts to run alsaconf:
- - 0xa SoundBlaster_AWE_64_PnP << ====== My Card - -
As per the subject line, this is a mistake. Are we talking about two different cards now?
AWE64, ISA, PnP is what I'm using. Works fine with OSS. Just wanted to try ALSA and have been so far deeply disappointed.
...........Being the paranoid type, I usually build my own kernel within 6 operating hours of getting a machine running, especially when I plan on using external modules for something like ALSA. As part of the kernel-building procedure, I `rm -rf /lib/modules/$VER/*' to get rid of depmod nastiness.
Same here, except that I haven't had the courage with this last kernel to compile since I haven't had the time to figure out the back-out strategies with my reiser file system. So, I've opted to stay stock, for now.
After this is done, and the new kernel has been built, installed, and booted, I begin the ALSA procedures, starting with the latest release from ftp.alsa-project.org, and building it myself. NOTE: The es137x family now has limited support for a Sequencer device, as of ALSA-0.5.x :].
Maybe I should give the tar ball a try, since the RPM contains modules that just don't work on my system. What the heck.... -- Brad Shelton On Line Exchange http://online-isp.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 01 Mar 2000, Maurizio Firmani wrote:
In the archive I found that someone else had this problem (system sounds in KDE) and he said that he could solve it but didn't post the details. If someone knows how to solve this problem (I can play CD audio but I cannot play wav files) ...
You need to edit /opt/kde/bin/startkde like so: # # now try to start the services # tartifaudio kaudioserver & startifaudio kwmsound & See the &'s? That's in the SuSE manual, though sort of hidden. As for playing .wav files, I'd advise that you install sox from series [snd] on the CDs and use it's `play' command. If that doesn't work, you've got a bad problem. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x107 | http://www.atipa.com _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (6)
-
bshelton-applix＠online-isp.com -
bshelton＠online-isp.com -
jpennington＠atipa.com -
jyry＠neutech.fi -
maurizio＠adriatico.prisma.rm.cnr.it -
pthomas＠suse.de