Topic: ks.cfg install problem

[Francois]

Hello,

I'm trying to install SME 5.6. I create a boot disk image with boot.img
and i boot to this floppy disk and i get an error message :

Error opening : kickstart file /tmp/ks.cfg : No such file or directory

Strange, no ?

What's happened ?

My hardware is a pentium 200 pro, mem 64 Mo, 6Go hd with a 1520 scsi card. hd is an ide disk. the cdrom is scsi.

Thanks for a response

[Bill Talcott]

Search for "/tmp/ks.cfg".

[francois]

of course, it search for ks.cfg but how can i have this message at the beginning of
the install process with a boot.img freshly  made ?

I think there is a big problem with the boot development.

How can i help the SME Developper community for this part of development.

I have good experience in Kickstart and could help the development.

I am going to analyse the boot disk and try to result this problem.
As i have read forums, theres is many persons who have the same problem.

I am sure if i change my hardware configuration (IDE CDROM instead of SCSI CDROM), that's working good.

That's means that SME Users who have SCSI Configuration cannot install SME with CDROM Solution. As i know it's a server distribution and many servers havent SCSI devices : There is a problem....

I will try to subscribe as a developper and i will give a boot.img that work good with SCSI Device... That's the challenge. It could take few weeks but if nobody do something, it could make a wrong publicity to the SME Distribution..

See you later

[Ray Mitchell]

Francois

Bill meant for you to search these forums using the search link. The question has probably been answered before and if you do a search here you will find the answer. Remember to select "All dates" so the search is not limited to only the last 30 days.
Here are the search results, you will probably find an answer there.

http://www.e-smith.org/bboard/search.php?search=%2Ftmp%2Fks.cfg&f=0&match=1&date=0&fldsubject=1&fldbody=1


There are instructions & a FAQ at www.e-smith.org for the correct way to make a boot disk.
see
http://www.e-smith.org/faq.php3
http://www.e-smith.org/docs/howto/
and the anser to exactly your issue (?)
http://www.e-smith.org/docs/howto/Boot_floppy_howto.php3

Regards
Ray Mitchell

[Ray Mitchell]

See

http://www.e-smith.org/bboard/read.php?v=t&f=2&i=242&t=239


Ray

[Robert]

I did a quick search as well and it seems that in a number of cases the SCSI driver didn't load. I couldn't find if anyone had reported this as a bug yet. Also, the old method for prompting for a driver disk ("accept dd") was reported to no longer work with 5.6. Possible workarounds are to temporarily install an IDE drive or do a network install.

[francois]

I am agree with Robert. This is a bug with the floppy boot disk.

All articles that Ray  shown me tells that there is a bug with a configuration with both IDE and SCSI devices.

The boot.img is done for IDE CD-ROM Only and doesn't work with SCSI CD-ROM.

So, that means the SCSI Drivers can't be used at all in boot.img

I am searching why it doesn't work and make a correction.

I will submit the correction to the dev for the release 6.0.

I am positive regarding this bug.

[Robert]

The driver for your SCSI adapter may well be on the driver disk. I haven't looked at the installer in a while, but perhaps typing "more options" or "plus d'options" will allow you to load additional drivers.

[Francois]

I know that i can add additional drivers but it cames too late.

IN SYSLINUX.CFG, there is a line that tells : cdrom:/images/ks_stub.cfg

This lines is apply when initrd.img is load and after the vmlinuz decompression kernel. The kernel will not find the SCSI drivers and look for IDE Cdrom drivers.
So when the kickstart begin, it search for cdrom and find nothing. That's why it says it can't find ks.cfg. In fact, it search for ks_stub.cfg.

The additional drivers installation is done later.

It can't work this way.

Tha't all for the moment... I investigate now the initrd.img of a redhat 7.3 to know how they have done to make it work...

[asotelo]

I'm doing a network install (http) using bootnet.img. The box I'm installing has no CD-ROM drive and uses and IDE hard drive.  I'm getting the same error, /tmp/ks.cfg not found and installation is aborted.

I copied the /install56/ks_stub.cfg to the boot disk and modified syslinux.cfg to point to the floppy drive for the location of ks_stub.cfg and I'm still getting the same problem.