Problem installing Slackware
 

Hi (yeah I know it's my first post)
I'm trying to install Slackware from the Slackware 10.0 ISO which resides on my SuSE install.
The problem is that the setup program after giving the proper information about the swap partition, the / source directory and so on, gives me the question which packets I would like to install. I give in my preference's and after that within a second the setup program returns with the anouncement that everything is installed according to my wishes. A big laugh ofcourse, but a problem, cause obviously it didn't install anything.

What I did prior to run setup:
mounted the iso in the following way:

mkdir /iso
mount /dev/hdb6 /iso
mkdir /iso1
mount -t iso9660 -o loop /iso/home/hoolie_v/slackware-10.0-install-d1.iso /iso1
After that I try to intall from a pre-givven directory (/iso1) and then the shit begins.

The strange thing is that setup recognizes the slackware packets and displaying them, but when I want to install them the problem occurs?

Where did I go wrong, or what did I forget?

did you select 'install from pre mounted directory' when it asked the install method ?
you should have done. then when it asks what directory, give the directory which all the package folders live in ( a/ e/ ap/ and all the rest )

if you will also be installing the graphical environment on disk 2. Mount disk 2, then create a directory called somthing like /link then fill it with symbolic links to tll the packages on disk1 and disk 2. this way you can install both cd's at the same time.

I did gave in the " premounted directory's" at the setup " Source directory's" question. But after that setup asks me which way I want to install, and whatever feature I give in it reponds within a few seconds: Instalation and configuration complete, you can now reboot.. (or something like that :) )

and when you reboot, what happens ?
sounds to me like its installed.

Nothing.. :) (Wished that I had that kind of fast computer..)
The setup doesn't respond at all, only the screen that everything is installed within the second..

After those steps, can you see anything with
ls -l /iso1
?


Cheers,
Tink

soo... you basically have to remove modutils and install module-init-tools ;)

I had the same problem about 2 years ago
 

About 2 years ago I had the 2 second installation problem that hoolie_v describes although at the time I was installing from CDs not from an ISO on the hard drive. I had tried to install Slackware 8.1 or Slackware 9.0 and the setup program would spend about 2 seconds installing all the software and then announce that it was done. I knew that the Slackware setup program could not possibly have copied all that stuff from the CDs in two seconds. Back then, I also ran into a couple of different issues when attempting to install Slackware and I am not totally sure if I am remembering correctly which one caused that to happen. I believe that is was caused by the fact that my Soyo KT-400 Dragon Ultra Platinum Plus motherboard had two IDE controllers built into it instead of just one.

So anyway do you have more than two of the 40-pin IDE connectors on your motherboard? I am only referring to the 40-pin IDE connectors which the 40 or 80 pin IDE cables connect to for hard drives or the CD-ROM drive. I am not referring to the 32-pin connector that the floppy drive(s) connect to. Do you have a Soyo KT-400 Dragon motherboard? Before going into a long winded explanation of my experiences I should probably ask you those questions to see if it sounds like a similar problem. I also had a different problem installing Slackware whenever I already had more than about 16 Linux partitions. For the first problem, I had to go into the BIOS setup menu to disable the extra IDE RAID connectors before Slackware or most other Linux distros could be installed. For the second problem, I had to temporarily disconnect my second hard drive so that I would have less than about 16 Linux partitions while intalling Slackware. Afterwards, I was able to reconnect the extra hard drive. Does your hardware setup have any resemblance to either of the situations that I described? I hope I am remembering correctly what it was that caused the 2 second Slackware installation problem. I also have two CD-ROM drives and discovered that Slackware could only be installed from one CD-ROM drive but not the other. Basically, I had a hard time getting the Slackware setup program to work properly and ran into at least 3 different issues and do not remember for sure which one caused the 2 second intallation problems.

It could be that you are having a similar problem for somewhat different reasons. I have never tried installing from a Slackware or any other distro from an ISO which was already in a partition on the hard drive and do not even know how to do that. With Linux all I have ever done was install from CDs.

Just to bring clarity, there should be no problem installing Slack on
a mobo with 2 IDE controllers. Almost all modern mobos have this.
In fact, this mobo has 2 IDE controllers and a RAID controller.
I have installed Slack on this comp with 2 hard drives, a CD-RW, and
a DVD+-RW. I've also installed Slack to two different hard drives when
I had 3 hard drives and the CD-RW in this comp. The number of IDE
controllers or drives isn't the problem, IMO. In fact, every computer
to which I've installed Slack (except lappys) has 2 IDE controllers, and
I've never had this issue at all - and no trouble installing Slack.

Yeah I can see the normal directory structure as can be expected from a CD.
and for Rick485, tnx for your extended reply :) but I don't recognize any of the hardwareproblems you described.

I have a two ide controller board as well. It didn't give me any problems installing several versions of Slackware. But I think the question Tinkster was asking is relevant here to analyse the problem. So boot from the Slackware floppy disks, repeat the steps you took and after mounting the iso do a dir listing using ls -l /dir/where/you/mounted/the/iso. :)

See you next week...

Here is the ls output from the mounted iso:

linux:/test2 # ls
. CHECKSUMS.md5.asc isolinux Slackware-HOWTO
.. COPYING kernels SPEAK_INSTALL.TXT
ANNOUNCE.10_0 COPYRIGHT.TXT PACKAGES.TXT SPEAKUP_DOCS.TXT
bootdisks CRYPTO_NOTICE.TXT README.TXT UPGRADE.TXT
BOOTING.TXT FAQ.TXT RELEASE_NOTES
ChangeLog.txt FILELIST.TXT rootdisks
CHECKSUMS.md5 GPG-KEY slackware

I did this under SuSE because obviously I can't copy paste from the slackware prompt. But I get the same output in the slackware install promt. You'll have to take my word for that :)

[edit after irc contact:]
sorry here is the ls -l output:

drwxr-xr-x 7 root root 4096 2004-06-22 23:33 .
drwxr-xr-x 24 root root 560 2004-07-16 04:35 ..
-rw-r--r-- 1 root root 9681 2004-06-22 08:53 ANNOUNCE.10_0
drwxr-xr-x 2 root root 4096 2004-06-19 01:24 bootdisks
-rw-r--r-- 1 root root 18606 2002-04-06 22:51 BOOTING.TXT
-rw-r--r-- 1 root root 125321 2004-06-22 10:35 ChangeLog.txt
-rw-r--r-- 1 root root 93284 2004-06-22 23:33 CHECKSUMS.md5
-rw-r--r-- 1 root root 189 2004-06-22 23:33 CHECKSUMS.md5.asc
-rw-r--r-- 1 root root 17976 1994-06-10 04:28 COPYING
-rw-r--r-- 1 root root 15234 2004-02-29 03:32 COPYRIGHT.TXT
-rw-r--r-- 1 root root 602 2002-04-06 22:48 CRYPTO_NOTICE.TXT
-rw-r--r-- 1 root root 32425 2004-06-21 16:38 FAQ.TXT
-rw-r--r-- 1 root root 117520 2004-06-22 10:55 FILELIST.TXT
-rw-r--r-- 1 root root 1565 2003-02-27 00:34 GPG-KEY
drwxr-xr-x 3 root root 2048 2004-06-20 06:29 isolinux
drwxr-xr-x 19 root root 4096 2004-06-15 04:26 kernels
-rw-r--r-- 1 root root 275105 2004-06-22 10:37 PACKAGES.TXT
-rw-r--r-- 1 root root 12530 2004-06-21 16:38 README.TXT
-rw-r--r-- 1 root root 5191 2004-06-22 09:07 RELEASE_NOTES
drwxr-xr-x 2 root root 4096 2004-06-20 06:29 rootdisks
drwxr-xr-x 15 root root 4096 2004-06-22 23:32 slackware
-rw-r--r-- 1 root root 70561 2004-06-22 21:02 Slackware-HOWTO
-rw-r--r-- 1 root root 15434 2002-06-18 00:43 SPEAK_INSTALL.TXT
-rw-r--r-- 1 root root 14826 2002-06-18 00:41 SPEAKUP_DOCS.TXT
-rw-r--r-- 1 root root 5136 2004-06-21 01:04 UPGRADE.TXT

what you can do is give an That will give much more details and will be readable using your SuSE. Looks much more easy to do then typing it all from a piece of paper :D