public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kenneth Lee" <klee15@cox.net>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Installing Fedora - boot loader
Date: Mon, 22 Nov 2004 14:26:55 -0500	[thread overview]
Message-ID: <000001c4d0c9$3a499040$6500a8c0@LAPTALK> (raw)
In-Reply-To: <20041122012309.GA10340@bruzos.org>

Yes!!! Success at last.   Thanks to David for his tips he sent me offline.
What I Had to do was this.

First I reburned the images because for some reason the first ones didn't
verify.  (hmmm, to much dog hair around here I think)

Then going on David's suggestion, I manually created my partitions using his
recommendations.  This was the hardest part of all because I never did
figure out how to use druid.  For example, I could not figure how to change
from ext3 to swap when setting up my swap partition.  I did finally manage
to get it set to "swap" but I haven't clue how I did it.

Note to anyone using the howto from linux-speakup.org,  where it says to
press control+alt+f2 to switch to another console.  You do not get a '#'
prompt (at least not with the version I have).  I have the version pointed
to from the linux-speakup page.  Version FC2.

Anyway I now have linux (fedora) install...now if I only knew what to do
with it! <G>  I still need to get my email client setup and a web browser.


Regards, Ken


-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of David Bruzos
Sent: Sunday, November 21, 2004 8:23 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Installing Fedora - boot loader


Hello again:
If you can't get the initrd thing to work, drop me a message and I will 
try to help you as much as possible.  If you can get the system to boot, 
then don't worry, everything else is just a matter of a few commands...
Even if you can't get the initrd image installed and working you can 
still load your speakup module by hand by typing:
# modprobe speakup_xxxx
on the command line.  XXXX is the keyworkd for your synth.  For example, 
I have a Double talk and my keyword is ltlk.  So, I type, "modprobe 
speakup_ltlk and my system starts talking.  Remember to do this as root.

Oh, the syntax for mkinitrd is:
# /sbin/mkinitrd -f -v /boot/initrd-x.x.xx x.x.xx --with=speakup_xxx
--with=pcspkr 

Where the /boot/init-x.x.xx is the name that you want for your image 
file.  The second x.x.xx is the kernel version you have installed (look 
in /lib/modules and you will see a directory with a name like: 
2.6.5.something-something).).  The --with=speakup_xxxx tells mkinitrd to 
put your speakup module in the image and the --with=pcspkr adds the PC 
speaker driver to the image, so that your console can beep.
The pcspkr module is not required though.  That only is something that 
can make your console more friendly when you don't have speech.

Take care!

David B.

On Sun, Nov 21, 2004 at 07:23:04PM -0500, Kenneth Lee wrote:
> Thanks for the encouragement.  I know I will eventually succeed, if I have
> to install a hundred times!  I'm on my third time now.  I'm still not sure
> how to do the "initrd", but I'll keep googling around and find the right
> howto.
> 
> Regards, Ken
> 
> 
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of David Bruzos
> Sent: Sunday, November 21, 2004 7:15 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: Installing Fedora - boot loader
> 
> 
> Hello Ken:
> Yes, you need a boot loader!  If you don't install grub there will be no 
> boot info in the master boot record of the hard disc and your BIOS will
not 
> see the operating system.  So, when you get to the boot loader screen, 
> select grub and put it to the MBR (master boot record).
> If you do that, you should be able to boot after you restart...
> About your other problem I am not sure.  I have not installed Fedora in a 
> while and I don't remember having any problems like yours.
> Don't get discouraged however, Linux is a wonderful thing and the
community 
> around it is even more wonderful.  After a year you will be amazed of the 
> things you can do with your Linux machine.  It was hard at first for me,
but
> 
> once I understood what was going on, everything got easier and easier...
> 
> David B.



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

-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.4.1 - Release Date: 11/19/2004
 



  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kenneth Lee
 ` David Bruzos
   ` Kenneth Lee
     ` David Bruzos
       ` Kenneth Lee [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='000001c4d0c9$3a499040$6500a8c0@LAPTALK' \
    --to=klee15@cox.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).