i d/l slack 9.0 it went into the system fine the 1st time. that was the trial and error install. so i go to reistall repartition the drives do a full install set up swap and target partitions. while its installing the packages it locks up and does this everytime after. so going on a tip that maybe the iso is corrupt and numorous tries to nail the prob down i buy a 4 cd set. it does the same exact thing in the same area installing the packages. heres the system:
mobo asus a7m266-d
dual amd mp 1800 cpus
1024mb ecc ddr ram registered
hda 25 gig ide maxtor
hdb 80 gig wd caviar (somethin like that anyway 7200 spin)
hdc creative 52x cd rom
hdd 27 gig maxtor
video is a nivida gforce 2 i think
2 3com ethernet cards
and some nec usb card
( all cards were detected on my 1st sucessfull install)

now heres the kicker mdk 8.0 and rh 7.2 load in fine detect everything but only have smp issues the same as i had w/ slack install.

what gives any ideas? i even messed w/ the bios to turn the fsb down. also to mention in the package install its not 1 specific program or kernal going in its random.

for smp in slack you need to install with smp kernel (don't think they have one) or compile krnel after install. also as for lock-ups it might be cpu temp from extracting tgz's might be a hard drive error (specially if it worked till you partitioned a different way) might be the fac that you have amd cpu's (kidding, I am an intel fan) could be you scratched the cd between then and now. you have to play with options

well i wasnt concerned abot the smp for now till i got partitions up to par and system installed. i had previously d/l the noarch kern which i unsderstood to clear that up. cpu temps i never checked them after but had no probs trying to reinstal right afterwards. i did ever partition combo possible. scratches im very careful w/ them and rite otta the box the bought distro did the same thing in the same spot thats why im curious and why i could installit once and not more. there are less minor marks on this cd than mdk also i failed to mention that when the install locks my keyboard i can still hit enter and the screen moves up but the cd wont eject if thats means anything. there must be something else going on. i'm currently running on mdk 8.0 on this system. no more windows. smoked my laptop h/d last weekend, only have the refresh disks not xp software and unwilling to buy it. and am having certain issues w/ mdk although impressed w/ what it detected.

ok, first off slack 9.0 has some usb glitches in fact my usb keyboard fails altogether on boot, but only install use ps/2 for install if you have it

2) whena cd-rom is mounted in linux it cannot be ejected until it is unmounted (eather a reboot or typing one of the following at a copmmand prompt: eject /dev/cdrom, umount /dev/cdrom)

3) if it locks at same spots then it is likely cd or ram.

hrmm ok well so to speak i have plenty of ram (swap partitions i have tried in sizes from 0-double my ram and same thing.) could it be the type i'm useing w/ bare.i ? . cd i guess could be a possibility although it works fine installing others. now i also have a cd usb burner that plays cds. anyway i can boot /dev/scd0 ? my keyboard is a ps2 and always has been. should i remove the usb card and try again eventhogh it detected it on the 1st install. i'm sure i can fig out how to install later as that would be on list# 2next to smp to correct.

tia

uhm.. if I understood that correctly then no you do not need to remove usb card bare.i shoudl work.. as for the boot thing.. I do not understand the question.

booting any chance i could use the burner as a boot device w/ the slack cd? i havent heard of this possible yet.

only if bios has option for booting from usb device (some do)

I've had troubles in the past when installing Slack from CD. Try copying the slackware directory to one of your other hard drives, then when you run setup, use that drive and directory as the source.

Enjoy!
--- Cerbere

I had issues with Slack9 not recognizing my USB keyboard when I tried to use any of the kernels that came with it.

It's possible that Slack is detecting your USB device and not really knowing what to do with it. The first thing I'd try is disconnecting any USB stuff (the burner for example) and give it another shot.

Once you've got it installed (assuming this works) you can go to /etc/rc.d/rc.modules and uncomment the line that deals with USB device support.

ok time for surgury. i'll try removing the usb card. i'll post when i'm back up w/ slack or drake

well i'm back online. tried slack 9 again 2 times w/ usb card unplugged and same results. i even for giggles lookes at cpu temps cpu0 114 degrees and cpu1 108 degrees. so i have no idea but i think i'm going to stay w/ and mod mdk 8.0

well i found the problem. hda had alot of bad blocks. would have never known this untill i installed rh 9.0 w/ issues point to that and same did w/ rh7.2. so i switched drives around and deleted it from the system and now im up on slack.