AW: Driver replacement

[Frank Morawietz]

Hello Pasquale,

if your compute nodes are identical and all of them need the Nvidia driver, you can use a basefile that already has Nouveau removed and Nvidia installed. Then there is no need for a Nvidia installation script at all.

Just as an unconventional idea…

Best,
Frank
--
Frank Morawietz

Von: linux-fai <linux-fai-bounces at uni-koeln.de> Im Auftrag von Pasquale Cantiello
Gesendet: Donnerstag, 25. Februar 2021 11:14
Cc: fully automatic installation for Linux <linux-fai at uni-koeln.de>
Betreff: Re: Driver replacement


[WARNING – EXTERNAL EMAIL] Do not open links or attachments unless you recognize the sender of this email. If you are unsure please click the button "Report suspicious email"

Dear John,
thanks for your answer.
Putting a script in the /srv/fai/config/scripts/ is the way I was trying but, if the system boots with the nouveau driver already installed, the sequence to install correctly the new one is:

- blacklist the nouveau
- reboot
- install the proper nvidia driver
- reboot again
- continue with software installation

And this sequence, I think, cannot be fully automated with those scripts.
So I have been searching for a way to prevent the nouveau installation since the beginning. I will study the fai-scripts in order to better understand how this happens.

Best regards

  Pasquale

---
ing. PhD Pasquale Cantiello
Istituto Nazionale di Geofisica e Vulcanologia
Sezione di Napoli - Osservatorio Vesuviano
Via Diocleziano, 328 - 80124 Napoli
Tel. 081-6108.332


Il giorno mer 24 feb 2021 alle ore 14:15 John G Heim <jheim at math.wisc.edu<mailto:jheim at math.wisc.edu>> ha scritto:
FAI works a lot like an installation you'd do "by hand". You boot from a
live image, partition the hard drive, install a base system via
debootstrap then chroot to do the rest of the installation steps
(install a kernel, install packages, configure grub). So, if you want to
blacklist a module, you have to do it on the new system, not on the live
boot image. In other words, in your case, you'd have to fcopy the module
configuration files to the new system after the base system is
installed. This is done by putting a script in the scripts folder of
your FAI config root. By default this would be /srv/fai/config/scripts/.

On 2/24/21 4:20 AM, Pasquale Cantiello wrote:
> Hi all
>
> I'm new to fai (only two weeks) and trying to use it to install a
> cluster with a front-end and 10 compute nodes. At present stage I am
> able to install all machines with related software and little
> customization from the faiserver with almost no problem.
>
> Now, since the nodes have a GPU card I want to install the nvidia driver
> and related sdk to the frontend and all nodes. I've downloaded all the
> files (.run file for driver and .deb files for sdk) on faiserver and put
> them in nfsroot in order to launch the installation on the nodes.
>
> My problems are now:
> How to prevent the installation of the nouveau driver on nodes? This
> will conflict with the new driver. I've also put a modeprobe.conf file
> with blacklist in /nfsroot/etc/modeprobe.d/ but with no success.
>
> And, how to use the PRELOAD or PRELOADRM command in the package
> configuration to install sdk from nfsroot? I've found no samples and
> tried all combinations...
>
> Thanks in advance to all who can help me.
>
> Best regards
>       Pasquale
>
> ---
> ing. PhD Pasquale Cantiello
> Istituto Nazionale di Geofisica e Vulcanologia
> Sezione di Napoli - Osservatorio Vesuviano
> Via Diocleziano, 328 - 80124 Napoli
> Tel. 081-6108.332



This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20210226/c64ab826/attachment.html>