[Alsa-user] ymfpci and floppy
Hi, as already mentioned, there is a correlation between bit 11 (SMOD LSB) of the Extended Legacy Audio Control register (0x42-0x43) of the YMF chips and the "floppy access crashes with alsa ymfpci driver" phenomenon, i.e. I can avoid these crashes if I add this line to the alsa source legacy_ctrl2 |= 1 << 11; (or if dma8=1). The kernel ymfpci driver uses v = 0x8800; to initialize this register - and is well behaved. If I change this to v = 0x8000; and load the module with parameters, the machine locks up if I try to access the floppy drive. The number 0x8800 seems to come from the old ymf_sb driver. Unfortunately it doesn't mention the origin of this value (Yamaha sample code?), but wouldn't it be a good idea to patch the alsa driver, e.g. to adopt the behaviour of the kernel ymfpci, or to add a snd_sbdma8 parameter, so people can try to use the chipset default (dma8=1) instead of the alsa default? Achim ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ymfpci and floppy
On Sun, 3 Mar 2002, Achim Linder wrote:
> Hi,
>
> as already mentioned, there is a correlation between bit 11 (SMOD
> LSB) of the Extended Legacy Audio Control register (0x42-0x43) of
> the YMF chips and the "floppy access crashes with alsa ymfpci driver"
> phenomenon, i.e. I can avoid these crashes if I add this line to the
> alsa source
>
> legacy_ctrl2 |= 1 << 11;
>
> (or if dma8=1). The kernel ymfpci driver uses v = 0x8800;
> to initialize this register - and is well behaved. If I change this
> to v = 0x8000; and load the module with parameters, the machine
> locks up if I try to access the floppy drive.
>
> The number 0x8800 seems to come from the old ymf_sb driver.
> Unfortunately it doesn't mention the origin of this value
> (Yamaha sample code?), but wouldn't it be a good idea to patch
> the alsa driver, e.g. to adopt the behaviour of the kernel ymfpci,
> or to add a snd_sbdma8 parameter, so people can try to use the
> chipset default (dma8=1) instead of the alsa default?
Do this patch fix your problem?
Index: ymfpci.c
===
RCS file: /cvsroot/alsa/alsa-kernel/pci/ymfpci/ymfpci.c,v
retrieving revision 1.11
diff -u -r1.11 ymfpci.c
--- ymfpci.c25 Feb 2002 11:50:13 - 1.11
+++ ymfpci.c3 Mar 2002 19:56:00 -
@@ -109,7 +109,7 @@
}
legacy_ctrl = 0;
- legacy_ctrl2 = 0;
+ legacy_ctrl2 = 0x0800; /* SMOD = 01 */
if (id->device >= 0x0010) { /* YMF 744/754 */
if (snd_fm_port[dev] < 0)
Jaroslav
-
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linuxhttp://www.suse.com
___
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ALSA and RedHat 7.2 Config Issue
On Sat, 02 Mar 2002 19:00:37 -0800 AJ <[EMAIL PROTECTED]> wrote: > I have been using and developing against ALSA on a RedHat 6.2 machine > for some time. > > But.I have recently installed the stable ALSA 0.5.10 packages for > drivers, libs, and utils on freshly built machine with Red Hat 7.2 > running a 2.4 kernel. I had absolutely no build problems, but am > running into problems when attempting to get aplay to play a sound file. > > I am using a Midiman Delta 66 soundcard. > > Below I have include information relevant to the error I am seeing from > aplay, kernel version, modules.conf text, and modules loaded. > > Any help that someone could give me to get ALSA working would be greatly > appreciated. > > Thanks in advance, > AJ > > 1. aplay invocation and error > - > [ajames@localhost wav]$ aplay -w exploBig.wav > Aplay: version 0.5.10 by Jaroslav Kysela <[EMAIL PROTECTED]> > Using soundcard 'M Audio Delta 66 at 0x1060, irq 10' > Playing WAVE 'exploBig.wav' : Unsigned 8-bit, Rate 22050 Hz, Mono > Aplay: unable to set channel params > > 2. kernel version > - > [ajames@localhost wav]$ uname -a > Linux localhost.localdomain 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 > unknown > > 3. modules.conf > > [ajames@localhost wav]$ cat /etc/modules.conf > alias parport_lowlevel parport_pc > alias usb-controller usb-uhci > > # ALSA native device support > alias char-major-116 snd > alias snd-card-0 snd-card-ice1712 > > # OSS/Free setup > alias char-major-14 soundcore > alias sound-slot-0 snd-card-0 > 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 > > 4. modules loaded > --- > [ajames@localhost wav]$ lsmod > Module Size Used by > snd-pcm-oss19008 0 (autoclean) > snd-pcm-plugin 17680 0 (autoclean) [snd-pcm-oss] > ppp_deflate41376 0 (autoclean) > bsd_comp4384 0 (autoclean) > ppp_async 6736 1 (autoclean) > ppp_generic19296 3 (autoclean) [ppp_deflate bsd_comp > ppp_async] > slhc5280 1 (autoclean) [ppp_generic] > ide-cd 27072 0 (autoclean) > cdrom 28512 0 (autoclean) [ide-cd] > snd-mixer-oss 4864 0 (autoclean) [snd-pcm-oss] > snd-card-ice17122752 0 (autoclean) > snd-ice171213696 0 (autoclean) [snd-card-ice1712] > snd-pcm31968 0 (autoclean) [snd-pcm-oss snd-pcm-plugin > snd-ice1712] > snd-timer 8432 0 (autoclean) [snd-pcm] > snd-ac97-codec 24640 0 (autoclean) [snd-ice1712] > snd-mixer 24448 0 (autoclean) [snd-mixer-oss snd-ice1712 > snd-ac97-codec] > snd-mpu401-uart 2576 0 (autoclean) [snd-card-ice1712 > snd-ice1712] > snd-rawmidi10080 0 (autoclean) [snd-mpu401-uart] > snd-seq-device 3888 0 (autoclean) [snd-rawmidi] > snd34672 1 (autoclean) [snd-pcm-oss snd-pcm-plugin > snd-mixer-oss snd-card-ice1712 snd-ice1712 snd-pcm snd-timer > snd-ac97-codec snd-mixer snd-mpu401-uart snd-rawmidi snd-seq-device] > soundcore 4464 2 (autoclean) [snd] > binfmt_misc 6416 1 > parport_pc 14768 1 (autoclean) > lp 6416 1 (autoclean) > parport25600 1 (autoclean) [parport_pc lp] > autofs 11520 0 (autoclean) (unused) > ipchains 39200 0 > keybdev 2160 0 (unused) > hid19024 0 (unused) > usbkbd 3424 0 (unused) > input 3840 0 [keybdev hid usbkbd] > usb-uhci 21536 0 (unused) > usbcore51712 1 [hid usbkbd usb-uhci] > ext3 64624 2 > jbd40992 2 [ext3] Well, I don't see anything wrong, maybe it has something to do with the fact that the Midiman Delta 66 is an advanced multichannel soundcard? Since you mentioned developing for ALSA: the current ALSA development is done in the 0.9.x beta series. That is also the basis for the merge of ALSA in the 2.5.y development kernels. From lurking on the alsa-devel list I understand the 0.9 API differs considerably from the 0.5 one. So I think it would be best to use ALSA 0.9.x. Btw, IIRC several people are using the Midiman Delta 66 succesfully. Good luck! -Frans ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ymfpci and floppy
On Sun, 3 Mar 2002 20:56:51 +0100 (CET)
Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> On Sun, 3 Mar 2002, Achim Linder wrote:
> > as already mentioned, there is a correlation between bit 11 (SMOD
> > LSB) of the Extended Legacy Audio Control register (0x42-0x43) of
> > the YMF chips and the "floppy access crashes with alsa ymfpci driver"
> > phenomenon, i.e. I can avoid these crashes if I add this line to the
> > alsa source
> >
> > legacy_ctrl2 |= 1 << 11;
> Do this patch fix your problem?
>
> Index: ymfpci.c
> ===
> RCS file: /cvsroot/alsa/alsa-kernel/pci/ymfpci/ymfpci.c,v
> retrieving revision 1.11
> diff -u -r1.11 ymfpci.c
> --- ymfpci.c25 Feb 2002 11:50:13 - 1.11
> +++ ymfpci.c3 Mar 2002 19:56:00 -
> @@ -109,7 +109,7 @@
> }
>
> legacy_ctrl = 0;
> - legacy_ctrl2 = 0;
> + legacy_ctrl2 = 0x0800; /* SMOD = 01 */
>
> if (id->device >= 0x0010) { /* YMF 744/754 */
> if (snd_fm_port[dev] < 0)
>
Yes. But who came up with the 0x8800 and why?
Achim
___
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] alsa-oss
Hi guys! What do I need alsa-oss for? The oss emulation modules already seem to be in alsa-driver package... BTW the oopsing I reported about 2 weeks ago didn't resurface, it seems to be stable now. Bye, Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023 -- rm -f /bin/laden msg02261/pgp0.pgp Description: PGP signature
Re: [Alsa-user] cs46xx no sound in games
Hi Takashi , Takashi Iwai wrote: >Hi Darryl, > >At Sat, 23 Feb 2002 19:54:24 +1000, >Darryl Cording wrote: > >>Darryl Cording wrote: >> >>>Takashi Iwai wrote: >>> As default ALSA cs46xx doesn't support OSS mmap (I forgot why..) and some games require mmap inevitablly. You can try to enable it by defining SND_CONFIG_CS46XX_ACCEPT_VALID (around line 51 of pci/cs46xx/cs46xx_lib.c). >>>Thanks Takashi, this has got it working. :-) >>>No real problems discovered yet, shall let you know if something come up. >>> >>>darryl >>> >>Well it seems I didn't do enough testing. Rtcw mutilplayer is OK but >>single player freezes when initialising sound. >> > >hmm, that's bad.. no kernel oops? > No oops, just a slient hang... One thing I have noticed, that in rtcw muilt-player the sound works ok but when you exit the game, it doesn't exit cleanly. The driver is kept open and in use until I issue an interrupt in the terminal window that the game was run in. Not sure if this is significant or not but I thought I better mention it just in case. >>Have no option but to kill it at this point. Unfortunately no error is >>produced either, so I have no clue where the problem >>may lie. >> >>I'll try compiling some debugging options in and re-test. Are there any >>specific options that maybe handy for the cs46xx?? >> > >the attached patch will add an option snd_mmap_valid. > Thanks. I applied the patch ok, configured and compiled ok. Unfortunately I get the same original "cannot open /dev/dsp" error message. I went back and specifically added the directive for SND_CONFIG_CS46XX_ACCEPT_VALID to cs46xx_lib.c, but the problem persists. If I try it without the patch in, the 'cannot open' error message goes away. The patch seems to not use the SND_CONFIG_CS46XX_ACCEPT_VALID options anymore but instead uses directives of the form CS46XX_BAx_... .I wonder then if SND_CONFIG_CS46XX_ACCEPT_VALID should be define somewhere else or is it retired for this round of testing?? I tried compiling the cvs without the patch in and configured it with debug=full, when I get the hang in rtcw single-user mode, no error message is produced either on the console or in the system log. There is no core dump produced either. I can't seem to get the system to cough up an error message so we can move forward with this. > > >Takashi > regards Darryl > ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Intel i8x0 support
Hello. I ended up providing support for lab that use Dell 933 Mhz with Intel i8x0 sound card built in (into the motherboard). PC runs Mandrake 8.1 with kernel 2.4.17 OK .. I did play around with OSS sound driver demo. Sound was So so ... cracking when adjusting volume from applications like jMax. Other programs (Pure Data)were complaining that they could not open midi output. I did look at the alsa website for info regarding support for this card. Accodording to support information, alsa provides only Audio support for Intel i8x0. That is, no MIDI. I was wondering if that site information is up to date. It's quite a common sound card (Intel i8x0). Assuming the worst (if Alsa does not support MIDI in this card) let me ask for advice on what other card I could get that is not very expensive (below 70 USD) and does have Alsa support for MIDI and audio (and hopefully latency is not too bad as well). Best Regards ... Jarek Myszewski _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
