Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-24-2003, 01:28 PM   #1
Registered: Jun 2003
Distribution: Slackware 12.2, CentOS
Posts: 42

Rep: Reputation: 15
Installation issues with hardware?

I've tried to install Mandrake, Red Hat 7.3 & Slackware 9 onto a PII 350 machine with 64 M RAM and 30G HD.

I get errors on each installation -

Red Hat - just stops and says I don't have enough disk space or my media isn't working right or have hardware issues.

Mandrake just freezes in the middle of the install

Slackware actually installed but then hung up in while starting x.

Is it my hd? is there a way to test the drive before tossing it for a new one?

Is it the motherboard?

How can I access and determine where the problem may lie?

Thanks for any help.

update: just got a *new* error while trying to load mandrake. "gzip: stdin: invalid compressed data--length error" -- ayy, ya, ya!

Last edited by absolute0net; 06-24-2003 at 01:30 PM.
Old 06-24-2003, 01:34 PM   #2
Senior Member
Registered: Apr 2002
Location: Arbovale, WV
Distribution: Slackware
Posts: 1,761

Rep: Reputation: 78
Try replacing thte RAM. I had a PC that did things like that and it was te RAM.
Old 06-27-2003, 10:12 PM   #3
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
Yeah, I go along with 'bad' memory stick. Another thing you can do, is download memtest 3.0, write it to a formatted floppy and 'test' your memory. You shouldn't see any errors on the test. If so, you can spend 20 bucks at circuit city for bestbuy and get a stick of memory for that computer (if still available, I think they take pc100 memory). Take the memory with you to the store, then you have an example of what you want.
Another way is to get a 'linux boot disk' (floppy) and try booting that into the console, if that works, then maybe you got a bad cdrom reader. Maybe a long q-tip and alcohol can clean the LED.
(of course, you do any of this at your own risk).

Or, you can make a windows boot disk and check out your hard drive if you need to do it that way:
I hope some of this will get you on your way!
Old 06-27-2003, 10:19 PM   #4
Senior Member
Registered: Apr 2002
Location: Arbovale, WV
Distribution: Slackware
Posts: 1,761

Rep: Reputation: 78
I had a server at work that would do lock up every once in a while. We had just installed dual CPU's. First I thought that it was the memory, but then I yanked the CPU's and replaced them with the original and everything worked fine.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Particular hardware issues Rick069 Linux - Hardware 0 02-13-2005 07:17 PM
Several Hardware Installation Issues cjwcash Linux - Hardware 0 08-06-2003 12:33 PM
Few more hardware issues Mega Man X Linux - Hardware 4 06-04-2003 12:36 PM
Hardware Issues cozman Linux - Hardware 3 11-13-2002 06:53 PM
hardware issues 1.1 matjaz85 Linux - General 0 05-02-2002 11:53 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:36 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration