How To Use An Own Ks.cfg Booting From A Usb-device (CentOS 8 & 9)

Home » CentOS » How To Use An Own Ks.cfg Booting From A Usb-device (CentOS 8 & 9)
CentOS 3 Comments

Hallo, I try to use a usb-boot stick for installation on a newer pc.UEFI can
t be disabled . Everythings works fine until I try to use a own ks.cfg for automation. I tried serveral tutorials but no one worked. Installtin stops in the first screen where to select language etc..

Has anyone hints or links for working examples?

Thanks Ralf

3 thoughts on - How To Use An Own Ks.cfg Booting From A Usb-device (CentOS 8 & 9)

  • Hello Ralf,

    Does your kickstart file contain all obligatory settings? Like e.g. language. Otherwise the installation will prompt for these, at least it did in previous CentOS versions.

    In my kickstart file I have these settings for an old CentOS 5 version (used ks a lot then):
    # use whatever fits you
    # System keyboard keyboard no
    # System language lang nb_NO

    From a running CentOS 7 system’s kickstart files (generated from the installation):
    – /root/anaconda-ks.cfg and/or
    – /root/initial-setup-ks.cfg
    # Keyboard layouts keyboard –vckeymap=no –xlayouts=’no’
    # System language lang en_US.UTF-8

    As you see, the directives for v5 and v7 differs slightly. I don’t know whether v5 directives would work on v7 or the other way around. Anyway, if you install a system manually, copying the necessary configuration directives from the then generated /root/*ks.cfg-files should give you a working ks-file.

    Also check that the path to the ks-file is correct. If possible host it on a webserver or any other way you can check, by logs or other means, that the ks-
    file is requested and correctly retrieved.

    Good luck, hope it helps!

    Kind regards, Christer M. Fekjan

  • Zitat von “Christer M. Fekjan” :

    Hallo, thanks for the hints. In which file do you refere to the ks.cfg and which syntax are you using?
    Is it isolinux.cg?

    Ralf

  • Am 05.01.24 um 21:26 schrieb Christer M. Fekjan:

    IIRC – the kernel parameters must be namespaced:

    inst.ks= and inst.ks.device