public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tim Burgess" <tim@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: kernel re-compilation
Date: Thu, 18 May 2000 17:15:22 +0100	[thread overview]
Message-ID: <000001bfc0e4$5f4afe50$ffc0c0c0@feenix> (raw)
In-Reply-To: <x71z30djl0.fsf@speech.braille.uwo.ca>

Hi,

Thanks, Kirk, you were right about copying the System.map file - I copied it
into /boot and the errors went away.

I've booted a few times now and found that SpeakUp can be made to carry on
talking - it seems to depend on when I hit the Control key during system
initialisation - I haven't yet pinned down a recognisable point when it's a
good idea.  If I don't press ctrl then SpeakUp stops talking eventually (I
assume a buffer overflow), but it can also clam up if I press it at the
"wrong" time during the start-up process.  I'll carry on fiddling and see if
I can pin this behaviour down.  I can usually get success after two or three
restarts, so it's not too bad.

My plan for tomorrow is to rebuild the kernel again - firstly to try and get
rid of my i586 errors and secondly to get my rtl-8029 Ethernet card to work.

Thanks again for all the help.

Tim Burgess
Technical Support
Voice:  +44 (0)1827 716000
Fax:  +44 (0)1827 715442
E-mail:  tim@blazie.co.uk

General enquiries:

Blazie Engineering Ltd.
Windermere House
Kendal Avenue
London
W3 0XA

Voice:  +44 (0)208 752 8650
Fax:  +44 (0)208 752 8658
E-mail:  info@blazie.co.uk
Web:  http://www.blazie.co.uk



-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Kirk Reiser
Sent: Thursday, May 18, 2000 3:22 PM
To: speakup@braille.uwo.ca
Cc: 'Geoff Shang'
Subject: Re: kernel re-compilation


Hi Again Tim:  No.  That warning is telling you that you didn't copy
the System.map file in /usr/src/linux into either / or /boot after the
compile.  It depends on what your distribution is expecting as where
to find the file.  It is a warning though and should not cause a
problem running, but you'll want to correct the situation to avoid
continuous messages when running ps and the like.

  Kirk

--

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0005182230260.10566-100000@data.home>
 ` Tim Burgess
   ` Kirk Reiser
     ` Tim Burgess [this message]
       ` Kirk Reiser
       ` Geoff Shang
 Kernel re-compilation Tim Burgess
 ` Kirk Reiser

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='000001bfc0e4$5f4afe50$ffc0c0c0@feenix' \
    --to=tim@blazie.co.uk \
    --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).