public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: alsa driver
Date: Sat, 1 Dec 2001 02:03:50 -0500	[thread overview]
Message-ID: <010601c17a36$54f43e00$0100a8c0@polaris> (raw)
In-Reply-To: <Pine.LNX.4.33.0111301636210.9031-100000@darkstar.example.net>

Hi, for bz files use a program called bunzip and for bz2 use bunzip2.

To extract the alsa drivers do this.

bunzip2 alsa-version.tar.bz2
tar -xf alsa-version.tar

----- Original Message -----
From: "randy turner" <rturner2@texasisp.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, November 30, 2001 11:39 AM
Subject: alsa driver


>
> \
> hi,
> i have never uncompressed or installed a bz file,
> what program do i need to use to uncompress and install these bz files?
> thanks in advance.
>
>
> On Sat, 1 Dec 2001, Shaun Oliver wrote:
>
> > randy, try
> > using alsa-driver-0.9.0beta7
> > that's the version I'm using now.
> > On Thu, 29 Nov 2001 rturner2@texasisp.com
> > wrote:
> >
> > > hi adam,
> > > i got that working fine,
> > > i would like to ask you and the group
> > > i tried to compile the alsa drivers 0.5.2
> > > with slackware 8.0,
> > > i am getting an error with the sound.o module,
> > > i have installed soundcore,
> > > i compiled the kernal with sound
> > > but still get errors compiling the alsa-driver.
> > > thanks in advance
> > > randy
> > >
> > > On 2001-11-28 speakup@braille.uwo.ca said:
> > >  sp>It depends.  If you use the Speakup boot disk that comes with
> > >  sp>Slackware 8.0, and install its kernel, PPP probably won't work out
> > >  sp>of the box.  This is because whoever compiled it compiled it for
> > >  sp>SMP (symmetric multiprocessing) when all the modules are for
> > >  sp>single-processor machines. This causes a lot of trouble.  There
are
> > >  sp>a number of solutions.
> > >  sp>1: Build a new kernel.  The advantage here is you can clean out
the
> > >  sp>default modules and install just the ones you need.  You can also
> > >  sp>get rid of other junk and possibly add support for that odd card
or
> > >  sp>two. 2: replace the modules with those for 2.2.19 kernels with SMP
> > >  sp>support. They are provided on the Contrib CD.  You would copy the
> > >  sp>modules from the CD over the existing ones for 2.2.19.  The
> > >  sp>advantage of this method is you don't have to rebuild a kernel or
> > >  sp>replace it.
> > >  sp>3: get the modified Speakup boot disk from ftp.linux-speakup.org.
> > >  sp>You would then copy its vmlinuz over your existing one and if you
> > >  sp>use Lilo, rerun it by simply typing "lilo."  The advantage of this
> > >  sp>is that you don't have to replace a whole bunch of files.  I
> > >  sp>suspect that they will have this little issue fixed in the next
> > >  sp>Slackware release.
> > >  sp>I chose initially to install the SMP modules, then I downloaded
the
> > >  sp>latest kernel source once I was online and rebuilt.  I think
> > >  sp>rebuilding is a good thing in the long run as you can really cut
> > >  sp>your boot time since the kernel isn't looking for non-existent
> > >  sp>hardware plus, it makes your existing hardware work more reliably.
> > >  sp>Hope this information helps.
> > >  sp>_______________________________________________
> > >  sp>Speakup mailing list
> > >  sp>Speakup@braille.uwo.ca
> > >  sp>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> > > _______________________________________________
> > > 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
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 slackware 8.0 and ppp rturner2
 ` Shaun Oliver
   ` randy turner
   ` alsa driver randy turner
     ` Ryan Mann
       ` randy turner
     ` Thomas Ward [this message]
     ` Shaun Oliver
   ` slackware 8.0 and ppp randy turner
     ` Charles Hallenbeck
       ` randy turner
     ` Gregory Nowak
       ` slackware8.0 and the alsadrivers randy turner
   ` slackware 8.0 and ppp randy turner
     ` Shaun Oliver
       ` randy turner
     [not found] <Pine.LNX.4.10.10003061326210.776-100000@hudson.mhonline.net>
     [not found] ` <002301bf8808$c72a0940$fd105b80@wang>
     [not found]   ` <x7sny3qaaj.fsf@speech.braille.uwo.ca>
     ` alsa driver Victor Tsaran

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='010601c17a36$54f43e00$0100a8c0@polaris' \
    --to=tward@bright.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).