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 21:29:35 -0600 [thread overview]
Message-ID: <001e01c7b08f$be6af140$6401a8c0@GRANDMA> (raw)
In-Reply-To: <001f01c7b08c$21f2aa90$ab00a8c0@tenstac>
It's in the right way, and it's master...
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 9:03 PM
Subject: Re: switching from amd to p3
> Tyler said:
> The cables are ok. do I just move it around on the cable?
>
> The disk boot error is severe, and I would think that needs
> to be solved even if you want to do a network boot. It is
> hard to say without trying some things, but I would check
>
> Is the IDE cable inserted the right way up in the drive.
> Some drives will only let you insert it one way, others
> will let you do it upside down.
>
> Is the IDE cable inserted into the first IDE controller
> port on motherboard. Best way to check is in BIOS,
> you should see the drive as master.
>
> Is the power cable inserted in the drive.
>
> If more than one drive on same cable, one must be
> set as master, one as slave, done by jumpers using
> the label on drive as guide. As suggested before if
> there already is another drive, try removing it and
> boot with just the newly setup drive.
>
> If all the physical connections seem okay, the next
> thing I would do is boot from a CD or floppy and
> do what I said before, at the boot prompt enter
>
> kernel-name root=/dev/hda1 noinitrd ro
>
> where kernel-name is the name of kernel on the
> removable media, and the kernel is a "bare" one,
> not specific to hardware, ie its 386 and generic
> controllers. On slackware its called bare.i but
> there should be an equivalent on debian. And
> make sure the root= points to the right drive
> letter and number of the partition with the root
> file system.
>
> You could also try loading a generic kernel on
> the AMD, making sure it boots there, then
> moving the kernel over. You'll have to check
> the debian docs to find out which kernel to use.
> I haven't use debian in a while.
>
> > How hard are these floppies to get for deb?
>
>
http://http.us.debian.org/debian/dists/etch/main/installer-i386/current//images/floppy/
> http://www.debian.org/releases/stable/i386/ch04s03.html.en
>
> -- Doug
>
>
>
>
>
>
>
> > 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
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next 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 [this message]
` 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='001e01c7b08f$be6af140$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).