LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-27-2004, 04:21 AM   #1
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Rep: Reputation: 15
K6-200


I'm playing around with an old AMD K6-200 and I wanted to install slackware on it... I have the slack 9.1 cds, I just haven't gotten around to burning the 10.0 cds. Anyhow, I go to install it and I boot the bare.i kernel (the only one that will boot) and during the "uncompressing Linux" phase the computer reboots. Any ideas?

EDIT: After more testing, I have determined that this problem exists with whatever linux distro I use...

Last edited by RazorKnight; 09-27-2004 at 04:32 AM.
 
Old 09-27-2004, 05:57 AM   #2
skubee
LQ Newbie
 
Registered: Sep 2003
Location: Portland, OR
Distribution: slackware
Posts: 22

Rep: Reputation: 15
have you tried using the floppies? im assuming its rebooting while trying to install, not when its already installed.
 
Old 09-27-2004, 07:13 AM   #3
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 52
<ignore>

Last edited by gbonvehi; 09-27-2004 at 05:57 PM.
 
Old 09-27-2004, 05:53 PM   #4
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
That's the problem. As soon as the slackware install cd tries to boot, the system resets itself. As for a boot floppy, no; my other computer is a Mac... The problem isn't limited to just slackware either. I've tried disabling the internal cache (somewhere I heard that was a possible fix) but no go there.

As for posting lilo.conf, it's whatever's on the slackware cd. I even tried switching out with a PI 200 MHz I just happened to have on hand.

It loads vmlinuz1 and reboots either on loading initrd or uncompressing linux.
 
Old 09-27-2004, 06:23 PM   #5
slightcrazed
Member
 
Registered: May 2003
Location: Lisbon Falls, Maine
Distribution: RH 8.0, 9.0, FC2 - 4, Slack 9.0 - 10.2, Knoppix 3.4 - 4.0, LFS,
Posts: 789

Rep: Reputation: 30
2 guesses (and that's really all they are)..... either a RAM problem or a PSU problem. RAM issues can show up as almost anything, including reboots. It sounds to me like that is the most likely culprit, but an underperforming power supply can cause reboots as well. If your 12v rail is low, then any time the system is trying to use 2 drives at the same time (like CD and HD) then it might be trying to pull more power than the PSU can dish out, and thus EVERYTHING on the system is starved for power and that usually causes a shutdown. It's less likely that this is the cause, but it sounds like you're running on a pretty old system, and old PSUs can have undervoltage issues like this.

slight
 
Old 09-27-2004, 07:31 PM   #6
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
I'm going to run with the second option - I have tried multiple sets of RAM sticks to no avail. Unless, by some vast conspiracy, *all* my RAM has gone bad...
 
Old 09-27-2004, 07:35 PM   #7
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 52
Razor, does it works with some other OS (DOS or Windows)? Do you have some kind of antivirus protection enable on the bios (I use to have a problem with this on an old bios)?
 
Old 09-27-2004, 07:41 PM   #8
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
No A/V...
It will try to boot to Windows 95 (the old OS) but it crashes before it does that. At first, it said because it doesn't have a mouse, but the last time it got past the W95 startup screen but froze on C:\ on a blank screen.
 
Old 09-27-2004, 08:46 PM   #9
WMD
Member
 
Registered: Jul 2004
Location: Florida
Distribution: Slackware, Debian
Posts: 484

Rep: Reputation: 30
I'm betting on a bad power supply. Such a shame too...old PSUs tend to be more reliable. But oh well.
 
Old 09-27-2004, 09:12 PM   #10
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
OK, I just tried using two PSUs but to no avail...
 
Old 09-27-2004, 11:23 PM   #11
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
As an update, I am using the gentoo rescue cd (just because I happen to have it) and I was able to boot aida, the hardware diagnostic utility. However, the rescue cd kernel would not boot, nor would Darik's Boot 'n' Nuke. (as with slackware, as with trustix server linux, etc...) Aida is a DOS based system. So DOS did work, but Linux will not boot.

Here's the basics on my system:

AMD K6-200 200MHz / 66 MHz
40mb RAM
3 gb HDD
2x 200W AT PSU

Hmm... what else do you need to know?
 
Old 09-27-2004, 11:39 PM   #12
skubee
LQ Newbie
 
Registered: Sep 2003
Location: Portland, OR
Distribution: slackware
Posts: 22

Rep: Reputation: 15
have you tried knoppix or a similar cd linux?

is it possible you can't install via cdrom?

perhaps the ide cables are to blame?

i dunno too much so pardon my ignorance.

if you can get a hold of another pc, try making an install sloppy and using those. :/
 
Old 09-28-2004, 12:29 AM   #13
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
I don't think it's a cdrom issue, but I will attempt to boot PHLAK. The memtest runs have indicated no errors with 40M of RAM.
 
Old 09-28-2004, 12:39 AM   #14
kersten78
Member
 
Registered: Nov 2003
Location: Minneapolis, MN
Distribution: Slackware, Debian, Gentoo, openSuSE
Posts: 358

Rep: Reputation: 33
This is only a guess, but it may be worth a try. When you boot w/ the Slack installation cd, somewhere (I think it's when you have the option to set up the partition table) you get a warning about systems with 16 megs or less ram. Basically, it recommends that you set up the swap partition and activate it (I believe there's instructions for this along with the warning). It doesn't seem like it would be a problem since 40 > 16, but you never know. You've pretty much covered all your bases so far, so it may be worth a try.
 
Old 09-28-2004, 02:03 PM   #15
RazorKnight
Member
 
Registered: Sep 2004
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 15
I don't get a RAM warning but I was able to scrounge together some more sticks, bringing me up to 64 Mb of RAM. I'll try some of the memory cheats and stuff like that. Am I right in assuming this is probably not a BIOS problem? Can I transplant a BIOS chip from one mobo to another? I have an AMBIOS chip on another similar mobo (which won't boot for other reasons); if the problem is BIOS related I could try switching BIOSes.
 
  


Reply


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
Dsl-200 Casket Linux - Newbie 1 08-17-2005 11:23 AM
lose 200$ or sace 200! HELP HELP HELP! OMEGA-DOOM Linux - Software 8 10-23-2004 07:47 PM
OMG ! WIN XP is 200$ BajaNick General 17 08-15-2003 02:08 AM
Canon BJ-200 Odan Linux - Hardware 1 07-17-2003 03:40 PM
D-Link dsl 200 HmmLinux Linux - Networking 0 07-05-2003 07:36 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:10 PM.

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