public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: Sean McMahon <smcmahon@usgs.gov>,
	"Speakup is a screen review system for Linux."
	<speakup@braille.uwo.ca>
Subject: Re: speakers and shutdown that used to work and now don't work as well
Date: Thu, 7 Apr 2005 14:23:08 -0500	[thread overview]
Message-ID: <20050407192308.GA11039@blackbox> (raw)
In-Reply-To: <000701c53b9a$f10387f0$77ac7682@azwaterDOM.wr.usgs.gov>

Hi.

Your problems are because you are using an old 2.4.27 kernel and OSS
drivers.  Try upgrading to a 2.6 kernel and using the alsa support.

Hope this helps.
          Kenny
	  
On Thu, Apr 07, 2005 at 10:55:00AM -0700, Sean McMahon wrote:
> I really couldn't think of a better subject line.  I upgraded a gateway 400 MHZ
> system to debian sarge speakup kernel 2.4.27.  So far, these are the two things
> I've noticed.  Sound works but only with headphones and another pair of speakers
> I have.  Sound does not come out of the speakers I used to use when this system
> was windows.  The speakers are the kind with a sub-woofer and I believe the
> cable connecting them to the speaker jack is the digital cable.  They didn't
> work on my other linux or windows system either but I figured it was the type of
> soundcard.  What's going on here?  Is this some gateway propriotary thing going
> on here?  The sound under Windows was registered as a creative soundblaster 64
> or 128D depending on which drivers I was using.  Under Linux it reagisters as
> the ensonic S1371 chipset.  I figure that is correct sinse sound with other
> speakers works.  I'm using os sound modules.  My second annoyance is the
> computer doesn't fully shut off when I shutdown.  It used to do that almost all
> the time but not always.  I've shut the system down twice, and so far, it is
> consistant.  Power to the drives powers down, but you can still ear the fans
> wering and you really have to hold in that power button to get the system off.
> One thing I noticed from the bootup messages is the system apic couldn't be
> enabled because the bios was dectected as pre-1998.  However, Linux was able to
> enable it's own apic and I did technically purchase the system in 1999.    I
> don't know if I'm using apm or acbi.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Sean McMahon
 ` Kenny Hitt [this message]
 ` Toby Fisher

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=20050407192308.GA11039@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=smcmahon@usgs.gov \
    --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).