This is a discussion on How do I use the Open Sound System? within the Gentoo Linux Support forums, part of the Unix Operating Systems category; --> On Sun, 30 Mar 2008 08:08:03 GMT, I waved a wand and this message magically appears in front of ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Sun, 30 Mar 2008 08:08:03 GMT, I waved a wand and this message magically appears in front of Mark Hobley: > > You want to do this why? > > I will be doing some OSS programming, and I will be replacing the OSS > code in the kernel with newer OSS code, which is available under GPL. > > I may eventually switching kernel, and I would like to stick with > OSS, if possible. Why? OSS is obselote. You should be changing over to ALSA. -- http://www.munted.org.uk Fearsome grindings. |
| |||
| In comp.os.linux.misc Mark Hobley <markhobley@hotpop.donottypethisbit.com> wrote: > cd /lib/modules/2.6.24.3/kernel/sound > tree > > . > |-- oss > | |-- opl3.ko > | |-- sb.ko > | |-- sb_lib.ko > | |-- sound.ko > | `-- uart401.ko > |-- sound_firmware.ko > `-- soundcore.ko > Examining the latest GPL source code for OSS-4.1, I find the following: oss-v4.1-build080323-src-gpl/kernel/drv/solo/solo.c I suspect that this file builds the driver for the soundcard. I don't appear to have a solo.c file in my current vanilla build tree, so maybe this card was not supported with the original OSS system, hence my OSS installation may not be complete. I suspect that if I can compile the solo.c file, it will create a module for the ESS solo card, which will enable my computer to make sound. Regards, Mark. -- Mark Hobley, 393 Quinton Road West, Quinton, BIRMINGHAM. B32 1QE. |
| |||
| markhobley@hotpop.donottypethisbit.com (Mark Hobley) writes: >In alt.os.linux.gentoo Unruh <unruh-spam@physics.ubc.ca> wrote: >> Get WHAT working with your soundcard. >I want some sound to come from my speakers whilst my kernel has OSS >modules loaded. >> You want to do this why? >I will be doing some OSS programming, and I will be replacing the OSS >code in the kernel with newer OSS code, which is available under GPL. And you want to do this why? alsa is the current sound driver. oss is deprecated. No distro installs oss anymore. Why not program for alsa instead. >I may eventually switching kernel, and I would like to stick with >OSS, if possible. >In order to do this, I need a working system prior to making >modifications. >> If you really want the oss, you might well find that there are no modules >> for your distro. But the OSS modules were the /lib/modules/*/kernel/sound >> modules. > cd /lib/modules/2.6.24.3/kernel/sound > tree > . > |-- oss > | |-- opl3.ko > | |-- sb.ko > | |-- sb_lib.ko > | |-- sound.ko > | `-- uart401.ko > |-- sound_firmware.ko > `-- soundcore.ko >> Or you pay the OSS people for their modules which are more up to >> date that those included in the kernel. >I have new OSS source code available, and I am working on compilation, >prior to inclusion. Remove all alsa modules which have been inserted, including all snd- modules Figure out which of the oss modules runs your soundcard (Your distro has very very few of the modules. here is my tree of the same directory) You might be better off compiling and inserting the new modules because there seem to be almost no oss modules in your kernel. Ie your current sound card probably has no oss driver in the current kernel. I find it astonishing that you would want to be programming new modules for your soundcard when your knowledge level of modules is so low. Sure it is a good learning experience, but.... |
| |||
| Mark Hobley wrote: > I am using Gentoo Linux with a 2.6.24 kernel, and I want to try out the > Open Sound System. I have compiled the kernel with the SOUND_PRIME option > as a module. > > My sound card is an ESS Solo 1 PCI card. > > What modules do I need to load in order to use OSS? I don't seem to be > able to find a user manual. > > I am aware of ALSA propeganda, but I really do want to try OSS. > > I am using udev, and I currently have no /dev/dsp device, but I do have > a /dev/dspW device. > > I issued the following commands: > > modprobe soundcore > modprobe sound > modprobe sound_firmware # I guess I should do this, but who knows? > > I also issues the following command: > > modprobe sb_lib # I have no idea whether this is the right thing to do > > I now type: > > cat /dev/random > /dev/dspW > > This gives an error: > > sh: /dev/dspW: No such device > > This is very strange. > > ls -l /dev/dsp* > crw-rw---- 1 root audio 14, 5 Mar 29 11:08 /dev/dspW > > whoami > mark > > groups > wheel audio mark > ^ > |- I should be OK to use the audio device. > > Thanks in advance to anyone who can help. > > Mark. > Here's what I do for alsa/oss support for my NVIDIA CK804 sound chips. Alter as required for your ESS SOLO1 (es1938 driver): In /etc/modules.d/alsa I have: # ALSA portion alias char-major-116 snd # OSS/Free portion alias char-major-14 soundcore ## ## IMPORTANT: ## You need to change this section for your specific sound card(s) ## Read alsa-driver's INSTALL file in /usr/share/doc for more info. ## ## ALSA portion alias snd-card-0 snd-intel8x0 # FOR YOU IT's snd-es1938 ## OSS/Free portion alias sound-slot-0 snd-card-0 # OSS/Free portion - card #1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss # Set this to the correct number of cards. options snd cards_limit=1 In my kernel config I have: # # Sound # CONFIG_SOUND=y # # Advanced Linux Sound Architecture # CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_RTCTIMER=m CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y # CONFIG_SND_DYNAMIC_MINORS is not set CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y CONFIG_SND_VERBOSE_PRINTK=y # CONFIG_SND_DEBUG is not set # # Generic devices # CONFIG_SND_MPU401_UART=m CONFIG_SND_AC97_CODEC=m # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_MTS64 is not set # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m # CONFIG_SND_PORTMAN2X4 is not set # # PCI devices # # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 is not set # CONFIG_SND_CS5535AUDIO is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # for you, set this to a module. # CONFIG_SND_ES1968 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_HDA_INTEL is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set CONFIG_SND_INTEL8X0=m # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_AC97_POWER_SAVE is not set # # Open Sound System # CONFIG_SOUND_PRIME=m # CONFIG_SOUND_TRIDENT is not set # CONFIG_SOUND_MSNDCLAS is not set # CONFIG_SOUND_MSNDPIN is not set CONFIG_SOUND_OSS=m CONFIG_SOUND_TRACEINIT=y CONFIG_SOUND_DMAP=y # CONFIG_SOUND_SSCAPE is not set # CONFIG_SOUND_VMIDI is not set # CONFIG_SOUND_TRIX is not set # CONFIG_SOUND_MSS is not set CONFIG_SOUND_MPU401=m # CONFIG_SOUND_PAS is not set # CONFIG_SOUND_PSS is not set # CONFIG_SOUND_SB is not set # CONFIG_SOUND_YM3812 is not set # CONFIG_SOUND_UART6850 is not set # CONFIG_SOUND_AEDSP16 is not set CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=y CONFIG_HID_DEBUG=y # CONFIG_HIDRAW is not set After compiling the kernel and rebooting... All I need do is run: /etc/init.d/alsasound start and the modules are loaded automatically. You MUST remember, the default volume for alsa/oss is MUTE. Run alsamixer and unmute and turn up the volumes a bit and go play some mp3's to test it... For your ESS SOLO 1... a visit to the ALSA website at: http://www.alsa-project.org/main/ind...:Module-es1938 Where it has ALL THE INFORMATION that you are asking to get sound working... Assuming the chips set is the same on your sound card and once you have the config file setup correctly, a simple modprobe snd-ess1938 would pull in all necessary drivers... I found all of this via a few minutes with GOOGLE and the ALSA website. You could have too! -- Jerry McBride (jmcbride@mail-on.us) |
| |||
| "J.O. Aho" <user@example.net> writes: >Mark Hobley wrote: >> I am using Gentoo Linux with a 2.6.24 kernel, and I want to try out the >> Open Sound System. I have compiled the kernel with the SOUND_PRIME option as >> a module. >> >> My sound card is an ESS Solo 1 PCI card. >> >> What modules do I need to load in order to use OSS? I don't seem to be >> able to find a user manual. >Enable loadable module support >[*] Automatic kernel module loading >Sound >< > Advanced Linux Sound Architecture ><M> Open Sound System (DEPRECATED) ><M> OSS sound modules ><M> Ensoniq SoundScape support ><M> 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support >Then load the right module, if the kernel hasn't already loaded it. >All you need is to modprobe the driver for your sound card, everything else >that hasn't been loaded and the sound card driver depends on is loaded >automatically. >> I am aware of ALSA propeganda, but I really do want to try OSS. >Alsa has the OSS emulation and is a good option and allows you to use all >applications that relay on the OSS. He wants to use the real OSS, not the emulation. Why is not clear, but that is what he wants. >-- > //Aho |
| |||
| Unruh wrote: > "J.O. Aho" <user@example.net> writes: >> Mark Hobley wrote: >>> I am aware of ALSA propeganda, but I really do want to try OSS. >> Alsa has the OSS emulation and is a good option and allows you to use all >> applications that relay on the OSS. > He wants to use the real OSS, not the emulation. Why is not clear, but that > is what he wants. Yes, I followed the thread and noticed that he wanted to code something that uses OSS instead of ALSA, but he still would be able to do taht even is he used ALSA with OSS emulation. The world is a strange place, there are some who want to use microsoft... -- //Aho |
| |||
| In comp.os.linux.misc Unruh <unruh-spam@physics.ubc.ca> wrote: > And you want to do this why? alsa is the current sound driver. oss is > deprecated. No distro installs oss anymore. Why not program for alsa > instead. I would eventually like to switch to a non-Linux based kernel, and OSS is a reasonable sound core for migration, and it has a much more simplistic interface, as far as I can tell. The new OSS core is now available under GPL, so some developers may choose to support the updated core. Mark. -- Mark Hobley, 393 Quinton Road West, Quinton, BIRMINGHAM. B32 1QE. |
| ||||
| In comp.os.linux.misc Mark Hobley <markhobley@hotpop.donottypethisbit.com> wrote: > The new OSS core is now available under GPL, so some developers may choose to > support the updated core. I managed to get the new OSS core working (on Gentoo). http://markhobley.yi.org:8000/OSSbuild Regards, Mark. -- Mark Hobley, 393 Quinton Road West, Quinton, BIRMINGHAM. B32 1QE. |
| Thread Tools | |
| Display Modes | |
|
|