That doesn't appear to help, as the setup program seems to want to load the other module regardless. So, it just locks the system up a little faster. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, August 20, 2003 7:02 PM To: Hirayama, Pat Cc: suse-autoinstall@lists.suse.com Subject: Re: [suse-autoinstall] Two Questions Hirayama, Pat wrote: <<snip>>
2. When I use AutoYaST with a control file, as the system gets to the
that it will read the control file, it goes through and looks at hardware, and loads what modules it needs to. So, I was wondering if it was
to PREVENT a specific module from loading? I have found that when I have a Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a QLogic driver, and a Megaraid driver, which is a problem, since they are
point possible the
same card. My workaround at the moment is to run a manual setup, answering yes/no to whichever modules to load. This defeats the purpose of having a hands-off autoinstallation routine. Any thoughts?
What about loading the right module before yast2 even starts with insmod=<module name> as a kernel parameter, would this help? Anas
Thank you!
-p
Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam@fhcrc.org