If you want to rebuild all the packages you can use :
rpmbuild -ba /usr/src/redhat/SPEC/systemimager.spec
To only build the boot package I used :
rpmbuild -ba --define "_build_only_boot 1" --define "_build_all 0" /usr/src/redhat/SPEC/systemimager.spec
Sure if you have a copy of the Grub patches it would be appreciated.
I'm currently sticking with 3.4.1 until the time I go to RH 4.
Thanks
Seth Haines <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2005/09/20 05:13
Please respond to sisuite-users
To: sisuite-users@lists.sourceforge.net
cc:
Subject: Re: [Sisuite-users] Smart Array 6i cciss not loading
David,
Once you edit the linux.i386.config how do you rebuild?
Mark S. came up with some excellent Grub patches for our HP equipment. You place reaplacement Grub.pm, grub-install, and one other file that I don't remember off the top of my head into the overrides folder and the install completes successfully. Would you like a copy of these? (There also in the systemimager archive)
As to your 3.5.X question wth 2.4.X machines, yes, I have successfully tested such an application however only by making changes to the master install script as noted from my previous emails in relation to the /dev file system mknod creations. The new version of the cciss driver included i nthe 3.5.X boel libraries appears to be the culprit at this point in time.
Thanks,
Seth
On 9/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
This is a resend from Friday Sept 16th with some of the history deleted - the msg was over the 40 KB limit
and was not posted.
Seth,
- Yes on the std boot pkg for 3.4.1 cciss does not load.
- By editing linux.i386.config as given below and rebuilding it
does work successfully. By doing this I also reduced the overall size
(turned off some hw I don't have) of the boot image soe it easily
fits on a floppy using si_mkautoinstalldiskette.
- suggest changing si_mkautoinstalldiskette and /etc/init.d/rcS to
default to the larger /dev/fd0u1680 so the default boot image fits in 3.4.1
- Yes a "modprobe cciss" also works on the std image.
- 3.4.1 uses linux-2.4.25 which has cciss 2.4.50
I latest 2.4 kernel driver I have is 2.4.54.RH1(from RH ES 3). I might try dropping this
in to see if it cahnges anything. The version with Systemimager 3.5.2 is v2.6.2 and yes
it has significantly changed.
- I gave up on grub long ago and use Lilo which works without a hitch(okay up2date
pukes on a kernel update even though lilo is updated sucessfully).
- One question I have is :
Does the new 3.5.x systemimager work correctly with 2.4.x kernel machines ?
Thanks
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED]
Seth Haines <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2005/09/16 07:06
Please respond to sisuite-users
To: sisuite-users@lists.sourceforge.net
cc:
Subject: Re: [Sisuite-users] Smart Array 6i cciss not loading
David,
I finally got a chance to play around with your issue a little bit.
System Imager 3.4.1
HP DL380 G4 with 6i
RHEL3 Update 4 ES install
Sure enough the cciss driver does not load!
I modified the computername.master script to include a single line:
modprobe cciss
Before the partitioning information and that seems to have resolved the drive detection and formatting issues.
Now back to the usual grub issues.
Did your modification to the discovery scripts solve this issue without the necessity of a modprobe?
Also apparently the cciss driver was significantly changed between 3.4.1 and 3.5.1 as the /dev/cciss/ device configuration in the 3.4.1 works with /disc0/disc as opposed to 3.5.1 /host0/target0/disc. I'd much prefer the use of 3.4.1driver in 3.5.1 binaries since in 3.5.1 it at least picks up properly.
Thanks,
Seth
On 9/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
Thanks Seth,
See other post and yes I am connected to a Cisco switch - all my current installations also take numerous pings before
connectivity.
Also from your first post I am currently running psp-7.20(haven't yet upgraded to 7.3) which as you
mentions replaces tg3 with bcm5700. This becomes a real pain because :
- if you use redhat network to keep your servers up2date then anytime you change the kernel(or kudzu
is run afterward) you have to re-install the support pack/reconfigure your network. I have tried to get Redhat to
incorporate the HP enhancements( push them from rhn) to no avail. I even have a ticket opened with RH where
they claim the bcm5700 driver is to blame and want me to test with the tg3 Ok rant over.
Seth Haines <[EMAIL PROTECTED] >
Sent by: [EMAIL PROTECTED]
20
