Bug: speech not coming up on boot

[Gaijin]

On Sun, Apr 27, 2008 at 05:09:58AM -0700, Tony Baechler wrote:
> I strongly suggest not using the Shane Etch kernel.  It has known 
> security flaws and has not been updated in over a year.  That's one of 
> the reasons why I built the 2.6.24 kernel packages.  Since you're 
> already running unstable, there's no reason not to upgrade to my kernel 

	<grins> Yeah, but *MY* computer is working. <dodges thrown ISA
cards>  I've already downloaded your packages, but haven't gotten around
to installing them yet with everything else that's going on.  Linux is
my only working OS without JAWS for the Win-XP laptop, and I'm in no
hurry to do yet another full re-install of Lenny from Shane's Etch CD.
I'm nowhere near ready to ride the bleeding edge with the rest of youse
guys.  Hell, I have yet to even figure out how to copy a file to CDRW.
I'm too busy communicating with people again after 4 years of isolation,
surrounded by people who throw full-blown panic attacks when I ask them
to read the screen.  Eh...whatever.  OT stuff.
	Have you tried going back to default settings to see if that
fixes the problem, and then work in kernel changes a bit at a time?  I'm
running a Celeron myself and was pleasantly surprised the compile only
took a half hour, rather than the 4-hour compile time it took with my
last computer.  So, not even an:

	echo -e "\a"

...makes the system beep for you?  If that's the case, then I would
definitely compile the kernel with  default options, except for choosing
the CPU, and see if even that worked first.    Then I'd let the system
run for a week befor trying to modify anything, but then that's me.  I'm
the kind of person who'd run lilo three times at full verbosity after a
new kernel installation before rebooting into it.  Then again, I have
few, if any, options open to me wherehacking disfunctional systems are 
concerned.  If you can't even get the speaker to beep, then the new
kernel probably isn't reading BIOS properly, or something.  I would
start with a clean, scratch configuration to see if it would give me a
working kernel, and then whittle it down from there.  Then again, I
would probably just go back to my sexy, fully functional, 2.6.18 Shane 
kernel. <grins>  I'm no linux guru yet.

			Michael