CentOS - May 2007 - custom kernel for Centos 5 kickstart?

Hi,

 Has any one tried to merge a custom kernel into vmlinuz/initrd.img for
Centos 5 kickstart? Or similar Linux distribution? 

 I am rebuilding a custom kernel from stock kernel source to build some
hardware modules into static form, so that the hardware detection
sequence can be altered in a hard way. Quick examples are: tg3 drivers
will be loaded before e1000, 3w-9xxx be loaded before 3w-9xxx, etc.

 Please advice. If the object could be achieved through adjustment to
/etc/modules.conf or similar files, then it could be even more
fantastic.


 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070530/0b8be97a/attachment.html>

On Wed, 2007-05-30 at 10:49 -0700, Guolin Cheng wrote:
>  I am rebuilding a custom kernel from stock kernel source to build
> some hardware modules into static form, so that the hardware detection
> sequence can be altered in a hard way. Quick examples are: tg3 drivers
> will be loaded before e1000, 3w-9xxx be loaded before 3w-9xxx, etc.
> 
>  Please advice. If the object could be achieved through adjustment
> to /etc/modules.conf or similar files, then it could be even more
> fantastic.
Take a look at the --preload option in mkinitrd.

-- 
Ignacio Vazquez-Abrams <ivazqueznet at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070530/2ce83404/attachment.sig>

Hi,

 Thanks a lot for your great suggestions.

 I've tried ksdevice options as well. It does work for some cases. But
the main problems. We have tens different network/harddrive
combinations. And so it turns a simple issue into a unmanageable
complex. Originally we use a custom booting kernel plus in-house
sysimager solution to handle it, custom kernel fix the detection
sequence problem and sysimager dumps a few tarball/images to hard
drives.

 If we can find a way to use a custom kernel to replace default
Kickstart kernel+initrd.img. Then we can fix the problem very elegantly.

 Any ideas on hacking Kickstart initrd.img?

--Guolin

-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Byrne, Nicholas
Sent: Wednesday, May 30, 2007 3:40 PM
To: Discussion list about Kickstart; centos at centos.org
Subject: RE: custom kernel for Centos 5 kickstart?

possibly "ksdevice=" which has a number of options that are useful but
it depends on what exactly he's trying to achieve. The other method i
thought of is to not setup network in main kickstart but instead do it
with netconfig in %post where you can use the --hwaddr switch (and
determine the target interface by it's mac address).
 
Or perhaps, since anaconda does a good job of setting up interfaces for
you, so just configure them up as you would like ignoring the fact that
they may be pointing to the wrong NIC and then change /etc/modprobe.conf
and /etc/sysconfig/network-interfaces/ifcfg-ethX files in %post to suite
your needs (again determine the target via mac address)
 
The first 3 bytes of the mac addresses are the manufacture code so you
should be able to work our a list for your hardware using
http://coffer.com/mac_find/
 
 

________________________________

From: kickstart-list-bounces at redhat.com on behalf of Callahan, Tom
Sent: Wed 30/05/2007 18:58
To: Discussion list about Kickstart; centos at centos.org
Subject: Re: custom kernel for Centos 5 kickstart?


I remember there being an option to define which MAC addr is defined as
eth0, etc. This was something you could define on the kickstart command
line.... Check out the documentation for anaconda.


On 5/30/07 1:49 PM, "Guolin Cheng" <guolin at alexa.com> wrote:



	Hi,
	
	Has any one tried to merge a custom kernel into
vmlinuz/initrd.img for Centos 5 kickstart? Or similar Linux
distribution? 
	
	I am rebuilding a custom kernel from stock kernel source to
build some hardware modules into static form, so that the hardware
detection sequence can be altered in a hard way. Quick examples are: tg3
drivers will be loaded before e1000, 3w-9xxx be loaded before 3w-9xxx,
etc.
	
	 Please advice. If the object could be achieved through
adjustment to /etc/modules.conf or similar files, then it could be even
more fantastic.
	
	 
	
	
________________________________

	_______________________________________________
	Kickstart-list mailing list
	Kickstart-list at redhat.com
	https://www.redhat.com/mailman/listinfo/kickstart-list
	




-------------------------------
Tom Callahan
TDS Engineering
410-229-1361  Tel
410-588-7605  Mobile 
410-229-1512  Fax 
callahant at TESSCO.com

TESSCO
Your Total Source for Wireless
http://www.tessco.com <http://www.tessco.com/> 

Network Infrastructure Equipment | Mobile Devices & Accessories |
Installation, Test, Equipment & Supplies



This e-mail is the property of Quadriga Worldwide Ltd, intended for the
addressee only and confidential.  Any dissemination, copying or
distribution of this message or any attachments is strictly prohibited.

If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer.

Messages sent to and from Quadriga may be monitored.

Quadriga cannot guarantee any message delivery method is secure or
error-free.  Information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses.

We do not accept responsibility for any errors or omissions in this
message and/or attachment that arise as a result of transmission.

You should carry out your own virus checks before opening any
attachment.

Any views or opinions presented are solely those of the author and do
not necessarily represent those of Quadriga.

_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list