public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Shaun Oliver" <shauno@goanna.net.au>
To: <speakup@braille.uwo.ca>
Subject: Re: pentium 100 woes.
Date: Fri, 28 Dec 2001 01:01:06 +1100	[thread overview]
Message-ID: <001401c18ede$eed05880$4700a8c0@shaun> (raw)
In-Reply-To: <Pine.LNX.4.33.0112270648120.5796-100000@lnx1.holmesgrown.com>

I can't even get the thing to come up with 2.2.16 kernel
I've had people look at the screen and all I get is funny characters.
I get a lilo prompt but fuck all else.
after no less than 10 reboots I get it to come up talking.
I sometimes get a crc error which suggests that the checksums aren't quite
right
I've just about run out of ideas here.
and another thing, I can never get it to boot from the hard drive only via
the installation disk.
so for now i"m on windows until I can get it to boot first time every time.



------------------------------------
Make Unlimited phone calls from your PC to ANY phone in the World!
http://www.eboom.com/free/
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, December 28, 2001 12:51 AM
Subject: Re: pentium 100 woes.


> Sure can't hurt to try the LBA support but I doubt it is really necessary
> for the 2 gig drive. When it fails do you get any funky errors? I have one
> machine (old 486/66) which keeps giving me loss of interrupt messages with
> a 2 gig drive on the second IDE controler. When I put it on my primary
> controler, the machine just hangs and I don't even get a lilo boot prompt
> or any of that. LBA did not help that situation. I ended up having to
> stick to 2.2.19 kernel on that box to get around the loss of interrupt
> problems. For some strange reason, I could never get a 2.4 kernel to run
> on that box.
>
> On Thu, 27 Dec 2001, Shaun Oliver wrote:
>
> > hi guys,
> > I just recently aquired a pentium 100 to turn into a linux box.
> > my problem is however,
> > I cannot get the machinte to boot first time every time.
> > would anyone have any idea as to why this is?
> > just to give a quick background,
> > I have a 2Gb hard drive as my primary drive which has my root filesystem
> > mounted on it as well as a 165Mb swap partition.
> > my /usr/local and /home directories are mounted on my second drive which
> > is a 4Gb broken up into 3 partitions.
> > and the 3rd partition on that drive is a fat32 partition.
> > my question is, would I need to add a line to my lilo.conf to tell my
> > machine to use lba support or is the problem more serious than that?
> > I have found that after much swearing and at the very least 10 reboots,
I
> > get linux to come up.
> > thanks in advance for any help
> >
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>




  reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Shaun Oliver
 ` Steve Holmes
   ` Shaun Oliver [this message]
   ` Shaun Oliver
     ` Gregory Nowak
   ` Gregory Nowak
 ` Gregory Nowak
   ` Shaun Oliver
     ` Shaun Oliver
     ` Kerry Hoath
     ` Pete
       ` Shaun Oliver

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='001401c18ede$eed05880$4700a8c0@shaun' \
    --to=shauno@goanna.net.au \
    --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).