From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: switching from amd to p3
Date: Mon, 18 Jun 2007 09:32:19 -0600 [thread overview]
Message-ID: <010401c7b1bd$df4ba380$6401a8c0@GRANDMA> (raw)
In-Reply-To: <009701c7b0fb$4d3fb890$9501a8c0@yellobow>
got it. thanks for the help. :)
Thanks,
~~TheCreator~~
[My programs don't have bugs; just randomly added features]
msn:
compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
vertigo head coder
web: tysdomain.com
----- Original Message -----
From: "Scott Berry" <sberry@northlc.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Sent: Sunday, June 17, 2007 10:19 AM
Subject: RE: switching from amd to p3
> Just one more thing to add Tyler. Some of the more modern Bios also can
> use
> f2 to enter the bios setup.
>
> Scott
>
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
> [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Doug Sutherland
> Sent: Sunday, June 17, 2007 12:07 AM
> To: Speakup is a screen review system for Linux.
> Subject: Re: switching from amd to p3
>
> Tyler, I believe disk boot failure is a BIOS error, not a linux error.
> It can happen if there is no drive, or the drive is not bootable, it
> could also happen if the BIOS boot options are not set properly,
> usually listed as boot priority, you usually want something like
> floppy, cdrom, ide0, ide1 boot priority. If the cables all seem
> okay I the next thing to check would be if the BIOS is seeing
> the drive. On modern BIOS the drives will usually be set to
> auto but if you press F8 it will detect the drives and show you
> them in BIOS (may be a different function key for a different
> BIOS). Confirm that BIOS is seeing the drive, and showing it
> as master, then check the boot priority settings in BIOS to
> make sure IDE0 is in the boot priority list. There are also
> settings in BIOS for the hard drive DMA mode, the lowest
> mode being PIO0, which is original IDE. If still not booting
> try setting that the lowest possible mode. The highest mode
> is probably PIO5 or Ultra DMA, or UDMA 133.
>
> At this point, after checking BIOS, if it sees the drive as
> master, IDE0 is in the boot list, the DMA mode is lowest
> PIO0, and it still won't boot, I would suggest putting it
> back in the original machine and making sure it boots.
>
> If it doesn't boot there I would check the partition table
> using fdisk or cfdisk or similar, check the bootable flag and
> make sure a partition is marked as bootable, and it's the
> correct partition, the one with grub installed. You can do
> this by booting from a linux CD and running fdisk -l or
> cfdisk.
>
> If BIOS on target system is seeing the drive as master and
> the drive will boot in original machine, then I'd say its time
> to try a different drive in target motherboard to make sure
> the IDE controller is working okay.
>
> -- Doug
>
> _______________________________________________
> 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.472 / Virus Database: 269.9.0/852 - Release Date: 6/17/2007
> 8:23 AM
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Doug Sutherland
` Littlefield, Tyler
` Doug Sutherland
` Littlefield, Tyler
` Doug Sutherland
` Gaijin
` Littlefield, Tyler
` Gregory Nowak
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` jaffar
` Gregory Nowak
` Michael Whapples
` Littlefield, Tyler
` Doug Sutherland
` Scott Berry
` Littlefield, Tyler [this message]
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='010401c7b1bd$df4ba380$6401a8c0@GRANDMA' \
--to=compgeek13@gmail.com \
--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).