Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-19-2006, 10:27 PM
|
#1
|
Member
Registered: Jul 2005
Posts: 273
Rep:
|
am i doing something wrong?
hello all,
I've been trying to install a fresh copy of slackware 10.2 on my system that used to run it with out a problem. I deceided to try to run a differnt distro and wasnt as happy with it.
so i tried installing and somehow i have corrupt cd's. so i d/l new copies, and install. crc errors, and a hole bunch more. it seemed like every reboot was a differnt error. the latest being invalid tree.
ive downloaded this off of slackware about 5 or 6 times, ran the check sums and what not and was told they were all okay. so why is this not working still? is it my computer? am i checking the md5's wrong, i'm using md5summer for windows xp. they claim to be compatable with linux.
and to write the iso to cd im using iso recorder.
if im fucking this up somehow can you let me know, i just want to install my fileserver back, and i'm getting beyond frustrated here.
thanks,
Last edited by neocontrol; 05-06-2010 at 02:32 PM.
|
|
|
04-19-2006, 10:43 PM
|
#2
|
Member
Registered: Oct 2005
Distribution: Slackware
Posts: 228
Rep:
|
The first thing you should do is to determine, beyond a doubt, that your Slackware CD's are perfect.
You can do this by following the instructions on this tutorial:
http://www.troubleshooters.com/linux/coasterless.htm
Take your time and understand what he's saying, and let us know how it goes.
Good Luck!
|
|
|
04-20-2006, 12:18 AM
|
#3
|
Member
Registered: Jul 2004
Location: [jax][fl][usa]
Distribution: Slackware64-current
Posts: 796
Rep:
|
you might also consider a low-level format
plus any other tools on your drive repair floppy
|
|
|
04-20-2006, 01:18 AM
|
#4
|
Senior Member
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Rep:
|
It sounds like bad media. This can be caused by bad CDs or a failing CDROM drive. Have you a CD lens cleaner around? Might want to run that through the drive.
-- Shade
|
|
|
04-20-2006, 02:06 AM
|
#5
|
LQ Veteran
Registered: Mar 2003
Location: Boise, ID
Distribution: Mint
Posts: 6,642
Rep:
|
Or maybe you are trying to burn them too fast. Regardless of your CD's top rated speed, just burn at a slow speed, maybe 8X or 16X. It's a one time thing so if it takes 5 or 6 minutes instead of 2 or 3, no big deal
|
|
|
04-20-2006, 02:11 AM
|
#6
|
Member
Registered: Oct 2004
Location: Norway
Distribution: Slackware, CentOS
Posts: 641
Rep:
|
I have had similar problems in the past which was caused by faulty hardware on my system, not faulty CDs. Thus I recommend that once you have verified beyond doubt that the media you downloaded from Slackware.com and burned on slow speed is OK, do a full system check of your hardware.
1-2 years ago I bought a second-hand server off eBay which ran SuSE Linux just fine, but kept giving me checksum errors during the install on Slackware (on random locations). After a couple of seriously frustrating days, I identified the problem as being the system RAM - it had 2 different RAM chips of 256MB each, one a bit faster than the other, and this caused the Slackware kernel some serious problems... Once I replaced one of the RAM chips, the system installed fine, and has to this date an uptime of 252 days (would've been longer if it wasn't for a power failure last summer)
-Y1
|
|
|
04-20-2006, 08:01 AM
|
#7
|
Member
Registered: Jul 2005
Posts: 273
Original Poster
Rep:
|
Thanks for all the replies, there's a couple of things i'm going to try.
I did drop the speed when i wrote teh cd. i think i have a 24speed writer. so i dropped it down to 12.
I thought it was a ram issue, cuase i had problems with that before, so i took out the questionable ram and still had the sam problems.
Ill go thru checking my media again, its gotta be fine, but ill do it again to be sure.
i have an extra cd rom, thats one of my ideas of whats wrong, but thats more of just a guess.
thanks for all the suggestions, ill let you know what happens.
Last edited by neocontrol; 05-06-2010 at 02:32 PM.
|
|
|
04-20-2006, 08:17 AM
|
#8
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,971
|
Quote:
Originally Posted by neocontrol
Thanks for all the replies, there's a couple of things i'm going to try.
I did drop the speed when i wrote teh cd. i think i have a 24speed writer. so i dropped it down to 12.
I thought it was a ram issue, cuase i had problems with that before, so i took out the questionable ram and still had the sam problems.
Ill go thru checking my media again, its gotta be fine, but ill do it again to be sure.
i have an extra cd rom, thats one of my ideas of whats wrong, but thats more of just a guess.
thanks for all the suggestions, ill let you know what happens.
charlie
|
Hi,
Just a few suggestions!
If you are over-clocking then step back your speed. OC can cause
I/O issues with peripherals. Clocking issue with RAM can be intermittent.
Another problem can be media, I've notice lately a lot of the cheap on-sale cd-r media causes compatibility issues.
You could be having a compliance problem between your CDR and CDROM. That is if your boot cdrom is different from your cdr. Meaning if you burn your cd on one drive and move to another to do the read. The drive alignment can be a problem. Usually this doesn't occur to often. The optics will either pick the signal or not.
|
|
|
04-20-2006, 09:30 AM
|
#9
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Run a check on your hdd.
|
|
|
04-20-2006, 09:46 AM
|
#10
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
Did you do any firmware upgrade to you cdrom?
|
|
|
All times are GMT -5. The time now is 05:33 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|