From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: fc6 disk problems
Date: Sat, 17 Mar 2007 13:41:00 -0500 [thread overview]
Message-ID: <001501c768c3$cf5b0a30$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <Pine.BSF.4.64.0703161751370.65347@server2.shellworld.net>
I made myself a new batch of FC6 CD's. Booting up for the install, I tried
text speakup_synth=ltlk nodmraid
and in the end got the same nonsense about inserting disc -99.
Sorry about the bad news. Alternatively, tell me if I did it wrong.
Al
p.s. What's nodmraid?
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, March 16, 2007 4:56 PM
Subject: re: fc6 disk problems
> Will everyone having these problems please try something for me and send
> the results to the speakup mailing list? Sighted people are having these
> problems too so you're not alone. The research I've done on the web
> recently seems to point at a problem fedora had hanging over from fc5.
> The way around it for the writer I read was to include the nodmraid
> parameter on the boot: line and if any errors happened after that to keep
> hitting the retry button. One of those retries worked and that writer got
> fc6 installed anyway. Might those results be replicable?
>
>
>
> _______________________________________________
> 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 Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.12/724 - Release Date: 3/16/2007 12:12 PM
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Albert E. Sten-Clanton [this message]
Jude DaShiell
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='001501c768c3$cf5b0a30$6405a8c0@ALBERTLC7SN0ZA' \
--to=albert.e.sten_clanton@verizon.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).