public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
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: Sat, 16 Jun 2007 19:07:36 -0600	[thread overview]
Message-ID: <001801c7b07b$e8b2b3c0$6401a8c0@GRANDMA> (raw)
In-Reply-To: <004501c7b07b$46d700b0$ab00a8c0@tenstac>

The cables are ok. do I just move it around on the cable?
Thanks,
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: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 16, 2007 7:03 PM
Subject: Re: switching from amd to p3


> If you're getting disk boot failure then probably something 
> is not right with the physical connection, the IDE cable or
> possibly the BIOS needs to be tweaked to recognize the
> hard drive. If there is more than one drive in the system 
> make sure the one you are moving in is on the first IDE 
> port so it's drive A, also make sure there are no conflicts
> if you have two drives in there ie make sure one is set as
> master by jumper and the other is set as slave. 
> 
> I think you can get disk boot error even if there is no disk
> at all, so start by checking the physical connections and 
> jumpering of drives.
> 
> The other thing that sometimes happens when moving 
> drives around is that what was drive a becomes drive 
> c for example, in that case you will get a kernel panic 
> with message stating no root file system found. If this 
> happens, then the other procedure I mentioned will 
> work, booting from cdrom or floppy, loading the 
> kernel from removable storage with the boot param
> root= pointing to the proper location of root file system
> (follow that with noinitrd ro) and then once booted you
> can rebuild the kernel and update the bootloader.
> 
> What you are doing is definitely possible, I have done
> it many times, building an entire system on on PC then
> then moving the drive to a mobile system.
> 
>   -- Doug
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  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 [this message]
         ` 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

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='001801c7b07b$e8b2b3c0$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).