Does my 2.4 'SI-3.4.1' kernel
work with SI-3.5.1 and RHEL4?
http://world.anarchy.com/~peter/systemimager/kernel
I expect it to have a 40% chance of actually working.
For your development question, I can answer that.
http://wiki.sisuite.org/
leads to ->
Developer Access
The Subversion serve
David,
In playing around with the boel tar.gz file there is an interesting file under /usr/share once extracted. Perhaps this was the discovery that Steve was referring to. Performing a search on the pci.1st file shows that the Compaq 6i controller is listed as "unknown unknown." I'm curious
David,
I manually ran a "modprobe cciss" from the BOEL command line in order to insure than an lsmod would show the cciss module loaded, it seemed to work in my case, resulting in the /dev/cciss/host0/target0/disc directory structure that was I referring to in my pervious mail.
In this case
Thanks for the reply Seth ... I was beginning to think there was no one on the list.
The floppy/cd boots correctly and bombs exactly as you show below.
- from the shell at that point a lsmod does not show cciss loaded.
- /dev/cciss... does not exist.
- I would attempt to load ccisss.o if
Some more info on this now:
System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks
to the cciss device boel refers to the /dev as
/dev/cciss/host0/target0/disc, where as the autoinstall script refers
to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting
the error o
David,
Where does the imaging process bomb? Is it when parted starts trying
to create the partitions and format them?
I'm running into the same problem with some DL380 G4's (RHEL4 Install).
Partitioning /dev/cciss/disc0/disc...
Old partition tabe for /dev/cciss/disc0/disc
Error: Could not st
Peter,
I found that out after playing around a bit more. Way to big in fact.
On to other methods.
Thanks,
Seth
On 9/8/05, Peter Mueller <[EMAIL PROTECTED]> wrote:
>
> Webmail..
>
> I believe the problem is the default kernel & modules grew too big for
> diskette... can anyone else confi
Title: [Sisuite-users] System Imager 3.5.1 RHEL4 Question
Webmail..
I believe the problem is the
default kernel & modules grew too big for diskette... can anyone else
confirm?
Regards,
P
From: [EMAIL PROTECTED]
on behalf of Seth HainesSent: Thu 9/8/2005 8:41 AMTo:
sisuite-users@list
Title: [Sisuite-users] systemimager via pxe
webmail, sorry for my
format. Because I found it so useful (and hard to find!) I am mirroring
the NIFLHEIM paper on how to get PXE working with systemimager. I tried to
put the link in WIKI but I am very unfamiliar with it, so maybe it is not e
I've been working with Ole Holm Nielsen RHEL4 write up (excellent
work!) but have hit a bit of a snag. In system imager 3.4.X there was
the option to "mkautoinstalldiskette" which seems to have disappeared
in 3.5.1. Since we only image about 30 nodes simultaneously here
having floppy control over
10 matches
Mail list logo
