public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: high memory versus alsa drivers
Date: Sat, 9 Oct 2004 14:10:41 -0500	[thread overview]
Message-ID: <20041009191041.GA26667@blackbox> (raw)
In-Reply-To: <Pine.LNX.4.60.0410091344060.3034@sent.com>

Oopse, didn't realize you are using a 2.6 kernel.  Forget what I said
about modules not getting compiled when you build the kernel.

Teach me to reply without thinking.

          Kenny
	  
On Sat, Oct 09, 2004 at 01:50:47PM -0400, Chuck Hallenbeck wrote:
> 
> I appreciate your suggestions, Kenny. The card is an sb-live pci card.
> Slackware uses stock kernels without any Slackware specific patches, so
> I doubt this problem is distro specific. I could be wrong about that
> recompiling thing I suppose, but the config file sure looks like it to
> me. I am a little uncertain how to handle the more traditional alsa
> packages now that alsa seems integrated into the kernel, but I guess I
> could always grab the latest tarballs and start from scratch compiling
> and installing alsa using a kernel with highmem selected.
> 
> Chuck
> 
> On Sat, 9 Oct 2004, Kenny Hitt wrote:
> 
> >Hi.  The agpgart modules is used so programs can access the video card
> >on the AGP bus.  I haven't seen the alsa modules get automatically
> >compiled before, so that must be something specific to Slackware.  Like
> >I said, my idea probably wasn't helpful but I had to ask just in case.
> >I have another idea which probably won't be helpful either.  In the past
> >with my older sound cards and earlier Alsa, I remember an option to tell
> >the driver to reserve DMA in low memory.  Don't know what card you have
> >or if the option has changed, but it might be something to look for in
> >the docs for the alsa drivers.
> >
> >Good luck figuring it out.
> >         Kenny
> >
> >On Sat, Oct 09, 2004 at 11:45:01AM -0400, Chuck Hallenbeck wrote:
> >>Hi Kenny,
> >>
> >>Prior to kernel 2.4.26, I used to have to do that after every recompile
> >>that involved a change of modules, but with 2.4.26 the alsa drivers
> >>compile with the kernel, evidently. They are loading okay. The output of
> >>lsmod is identical with and without highmem selected, and all the alsa
> >>components are there, same sizes and dependencies.
> >>
> >>Oh -- there is one additional line in the lsmod output when highmem is
> >>selected. It is "agpgart" and I am not familiar with that piece.
> >>
> >>Chuck
> >>
> >>
> >>
> >>
> >>--
> >>The Moon is Waning Crescent (21% of Full)
> >>Home page at http://www.mhcable.com/~chuckh
> >>Speakfreely address 24.105.197.112:2074
> >>
> >>_______________________________________________
> >>Speakup mailing list
> >>Speakup@braille.uwo.ca
> >>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> -- 
> The Moon is Waning Crescent (20% of Full)
> Home page at http://www.mhcable.com/~chuckh
> Speakfreely address 24.105.197.112:2074
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chuck Hallenbeck
 ` Igor Gueths
   ` Chuck Hallenbeck
 ` Kenny Hitt
   ` Chuck Hallenbeck
     ` Kenny Hitt
       ` Chuck Hallenbeck
         ` Kenny Hitt [this message]
 ` Janina Sajka

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=20041009191041.GA26667@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=speakup@braille.uwo.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).