Six month install nightmare!!

[RichardF]

Five years ago I dabbled with Slackware version 1. Despite the primative nature of the beast, I had it up and running in a couple of days without too much trouble.

Now I'm trying to install Caldera Open Linux 2.3. I'm using the same machine that I installed Slackware on all those years ago, and I just can't get it to work. Becuase of the age of the CD-ROM, I'm using the floppy install method, but still no joy. The annoying thing is, is that there isn't even any instructions on how to create a boot disk. I have limited time, but have been trying to get this thing installed for over 6 months now. I'm beginning to think that Linux distros are going backwards. :mad:

[bdg1983]

I see you've also posted the eServer install problem in Technical. Now I'm getting confused going back and forth between the two posts.

Which one is the correct one to post to?

Please delete the other if not needed.

Caldera eServer 2.3 documentation (http://www.caldera.com/products/eserver/)

[RichardF]

Sorry, yes reply here! I've only just stubbled across these forums, and in deparation posted to the first one.

I've read all the documentation there is on this as far as I know. I've spent hours searching Google etc. etc. and I'm hoping someone out there has had a similar experience. Maybe I just need to go back to using Slackware.

[bdg1983]

There will be instructions on the CD for creating the install and MODULES diskette images. Should be in the install or dosutils directory and will have a readme on how to use the rawrite utility.

What is the exact problem you are having? Can't detect the old cdrom?

The modules diskette has scsi, network and cdrom modules to help out during the install process.

Lots of stuff on this at Caldera's support knowledgebase.
http://support.caldera.com/caldera

[bdg1983]

I've been using Caldera steadily since their version 2.2 and have never really had a problem with installation.

On my laptop (not cd bootable), I just use the install and modules diskettes and the modules disk helps to get everything detected including pcmcia.

[RichardF]

I'm using the LISA install, as the standard Lizard install hangs when trying to install from CD-ROM. It can't seems to detect my SCSI card.

I have created the modules diskette and run the LISA install. It goes through all the configuration questions, like date, ip addresses, printers, mouse etc. but after configuring LILO, I get this strange message about being unable to find the EXECVP directory. I've searched the Caldera site, the Google search engine and in many other places, but still can't get any joy.

Another odd thing is that if I use the Lizard install, it won't recognise my modules diskette. :confused:

Thanks for you patients.

[bdg1983]

Lizard install? I think there is a way to get it to ask for a modules disk. It's posted at their knowledgebase. I'll have a look and post back.

Is it eServer 2.3 or OpenLinux 2.3?

execvp has something to do with process execution.

This is part of the man page for execvp. What it means, I really not too sure.

The execv and execvp functions provide an array of pointers to null-terminated strings that represent the argument list available to the new program. The first argument, by
convention, should point to the file name associated with the file being executed. The array of pointers must be terminated by a NULL pointer.

Where did you get the 2.3 CD from? Download or retail package?

If download, then it could be a bad download or burn. If from a retail package, then I guess it doesn't like something about your pc.

Could you describe your pc and components and how you have partitioned the drive etc.?

Any chance you could try eDesktop 2.4 to see if it works? Do you have a fast connection?

[bdg1983]

There's usually a way to get something to work.

Here you go.

Description:

The Lizard install has an "er=" boot parameter that can be helpful when installing OpenLinux 2.x.

Solution:

At the LILO "boot:" prompt you may enter a special parameter er= for the install image:
boot: install er=xxxxxx

This will change the behaviour of the new install and turn on/off certain features.

The following special parameters are supported with the Lizard install:

er=modules
will force to ask for a modules floppy and try until successfully mounted. The normal behaviour (if the parameter is NOT specified) is the following, depending on the case:
a) You booted from a small initrd or the install floppy It will display a line Mounting modules floppy........ WAIT and gives you 5 seconds and one try to insert the modules floppy. If it fails or you are too slow it will just continue.
b) You booted from CD or the big initrd or from Windows/DOS No line at all will be displayed about modules because we already have all modules in the initrd.

er=cautious
will just do a cautious autoprobing. If you do NOT specify this parameter Lizard will do a more aggressive autoprobing. What actually gets autoprobed depends on the available modules. So if you use just the install floppy, you should insert the modules floppy to make all modules available and to get a broader probing.

er=noether
will exclude all ethernet card probing. If you do not specify this parameter all available ethernet card modules will be probed. This may take too long for you or even hang your machine. (watch the output on tty5 to see what currently gets probed)

er=hwinfo
After the autoprobes are done and before starting lizard it will ask you, on tty5, to insert a MSDOS formatted floppy and write a debug file hwinfo0.txt Which could be helpful in troubleshooting why Lizard isn't autoprobing your hardware.

[RichardF]

I've tried again; when I run the install.bat (which runs LOADLIN) I do not get the BOOT: prompt. It just goes straight into the GUI screen, loads the Kernel, skips the load modules, regardless of whether the floppy is in or not, and then hangs trying to install from the CD-ROM. The CD was from Novell, so I'm assuming it is a good one.

I was looking at editing the install.bat file and using the AHA152x parameter, but this didn't seem to work either. I will need to read the documentation on this a bit more tonight.

Any further thoughts would be appreciated.

[bdg1983]

Are you booting from the install floppy? I think there are different floppies you can create. Lizard, Lisa and perhaps another.

Try the Lizard install diskettes if available.

The install parameters for scsi cards may be in a readme on the cd or available at Caldera's knowledgebase. I'll have a look.

[RichardF]

You're right, there are different floppies you can create, LISA and Lizard. I've just create the Lizard install floppy and booted, which then gives me BOOT: option. Entered "install er=modules" and the install waits for the modules disk but can't load it! It fails! :eek: What now? This software doesn't want to get installed on my PC that's for sure.