Greetings, I had a couple of questions I'm wrestling with right now. 1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation? 2. When I use AutoYaST with a control file, as the system gets to the point 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 possible 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 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? Thank you! -p Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam@fhcrc.org
Hirayama, Pat wrote:
Greetings,
I had a couple of questions I'm wrestling with right now.
1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation?
Thats right, create_package_descr creates a new database to be used when installing a system. Only then customized packages can be installed.
2. When I use AutoYaST with a control file, as the system gets to the point 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 possible 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 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What I ended up doing here was to take "/boot/root" from the installation media, remove the qla1280 driver, and create a new "/boot/root" to get around that problem on a Dell 6600. You will need to be familiar with using "losetup" and manipulating (c)ramfs images. HTH. HAND. On Wednesday 20 August 2003 10:02 pm, Anas Nashif wrote:
Hirayama, Pat wrote:
Greetings,
I had a couple of questions I'm wrestling with right now.
1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation?
Thats right, create_package_descr creates a new database to be used when installing a system. Only then customized packages can be installed.
2. When I use AutoYaST with a control file, as the system gets to the point 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 possible 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 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
- -- begin sig.txt Jean L. Francois - Enterprise Linux Architect "Failure is only postponed success as long as courage 'coaches' ambition. The habit of persistence is the habit of victory." end -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: No Good Deed Goes Unpunished iD8DBQE/RS5CgP5boHtr6J8RAge/AKDFPwCMJyZrcu4vYW69T5DiflSrQwCeNJpj FMHRWe63l8hCY0VjzEXaBIk= =5Hlc -----END PGP SIGNATURE-----
participants (3)
-
Anas Nashif -
Hirayama, Pat -
jfranc46＠ford.com