All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7 make modules_install error (oss)
Date: Tue, 19 Mar 2002 10:51:07 -0800	[thread overview]
Message-ID: <3C97889B.6060301@lexus.com> (raw)
In-Reply-To: <86256B81.005C508A.00@smtpnotes.altec.com>

Agreed, the oss drivers should _at least_
be maintained as an alternative, e.g. for
those of us who want reliable sound with
*low latency*

<explanation>
I haven't checked lately, but not too long
ago the alsa drivers were found to be one
of the worst sources of latency in the kernel.
</explanation>

Joe

Wayne.Brown@altec.com wrote:

>
>I really wish the OSS drivers would be fixed.  They worked perfectly with my
>Crystal SoundFusion card, but the ALSA drivers are very unreliable with it.
>Sometimes they work, sometimes they don't.  (One day a couple of weeks ago I
>rebooted about ten times, and the sound worked consistently *on alternate boots*
>(that is, it didn't work after the first boot, worked on the second boot, didn't
>work on the third, worked on the fourth, etc.).  The next day it worked on every
>boot.  Since then it works sometimes, and sometimes doesn't, with no discernible
>pattern.  Even when it's working, it works sporadically -- some sound effects in
>Gnome work, others don't, then a few minutes later they all work again;
>RealPlayer works OK until I open a new window, then the sound cuts out and won't
>start again until I restart RealPlayer; and so forth.  The OSS drivers don't
>give me any of these problems.
>
>
>
>
>
>bonganilinux@mweb.co.za on 03/19/2002 08:10:03 AM
>
>To:   Corporal Pisang <Corporal_Pisang@Counter-Strike.com.my>,
>      linux-kernel@vger.kernel.org
>cc:    (bcc: Wayne Brown/Corporate/Altec)
>
>Subject:  Re: 2.5.7 make modules_install error (oss)
>
>
>
>>Hi,
>>
>>make -C  arch/i386/lib modules_install
>>make[1]: Entering directory `/usr/src/linux/arch/i386/lib'
>>make[1]: Nothing to be done for `modules_install'.
>>make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
>>cd /lib/modules/2.5.7; \
>>mkdir -p pcmcia; \
>>find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
>>if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.7; fi
>>depmod: *** Unresolved symbols in /lib/modules/2.5.7/kernel/sound/oss/sound.o
>>depmod:         virt_to_bus_not_defined_use_pci_map
>>
>
>The OSS driver that you selected has not been converted to use the new pci API
>I'm not sure if it will ever be updated though, since alsa is now part of 2.5
>try to use the alsa drivers instead. If you read this
>virt_to_bus_not_defined_use_pci_map carefully yo will see that it says
>virt_to_bus not defined use pci_map nice way to get people to fix the old
>drivers
>;)
>
>---------------------------------------------
>This message was sent using M-Web Airmail.
>JUST LIKE THAT
>http://airmail.mweb.co.za/
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>



  parent reply	other threads:[~2002-03-19 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 16:48 2.5.7 make modules_install error (oss) Wayne.Brown
2002-03-19 17:15 ` Alan Cox
2002-03-19 18:51 ` J Sloan [this message]
2002-03-19 19:14   ` Alan Cox
2002-03-19 19:07     ` J Sloan
2002-03-20  8:30   ` Jaroslav Kysela
2002-03-20  9:17     ` J Sloan
  -- strict thread matches above, loose matches on Subject: below --
2002-03-19 14:10 bonganilinux
2002-03-19  6:24 Corporal Pisang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C97889B.6060301@lexus.com \
    --to=jjs@lexus.com \
    --cc=Wayne.Brown@altec.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.