> 
Hi,

I do not know of sun boxes, but we also had the problem with the 
old aic79xx in the boel-kernel, but I could successfully get a new 
aic79xx into the boel. As base for my works I used the 
systemimager-3.1.4.tar file. 
aic79xx is stable from version 1.3.8, i copied the source of 
aic79xx to the boel-kernel-sources and did a new kernel. 
my procedure was the same as described in the faq's of the system imager 
manual chap 5. 

- untar systemimager-3.1.4.tar
- make patches_kernel-stamp
- have the new aic79xx source merged into the kernel 
- make a new kernel 
- make the entries/copy the modules to initrd_source/my_modules 
- edit the FLAVOR
- make binaries_install 

I did all this on a RedHat 8.0 system. 

best regards, 
Hildburg
_____________________________________________________________________________
Hildburg Asano, Fujitsu Siemens Computers GmbH, High Performance Computing,
Otto-Hahn-Ring 6, 81730 Muenchen
mail:[EMAIL PROTECTED],[EMAIL PROTECTED]
Tel:+49-89-636-45304, Fax: +49+89-636-43604
http://www.hpcline.de
_____________________________________________________________________________


> 
> 
> My lab has been experimenting with Systemimager for the
> past few weeks with mixed results. Our inital builds
> used the Sun V65 for the server machine and a collection
> of LX50s for the target/clients. This deployment went
> very well. We were very impressed with the tool and
> excited to be able to use it for some future projects.
> 
> Our problems started when we moved to V60s as the client/
> target machines. We encountered the issue of not being 
> able to partition a disk because the disk was not found.
> This was what have learned from reading your newsgroup is
> the classic aic79xx driver dilemma.
> 
> Since then we have tried several things suggested by the
> manual, the help pages and the newsgroup.
> 
> We tried moving the modules scsi_mod.o and aic79xx.o to
> my_modules, adding instructions to the INSMOD file and
> rebuilding the kernel.
> 
> We tried moving from the stable 3.01 to the unstable 3.1.5
> release because it looked like there was support for aic79xx.
> 
> We even tried replacing the SIS kernel with a RH ES2.1 kernel
> only to get ramdisk errors.
> 
> Before we wander down any more dark holes on our own, I wanted
> to ask the builders and the community if anyone has had
> success with this tool and Sun V6x clients. If so, where have
> we gone wrong?
> 
> We've also examined the patches and we are unclear where we
> might want to jump in.
> 
> Any advice would be greatly appreciated. The initial success
> with this tool showed us what we might do. Now if we can just
> use it on a wider variety of Sun boxes, we would have something
> pretty exciting. If you can help get us there, we would appreciate
> it.
> 
> 
> -- 
> Stan Heller
> Systems Engineer
> Sun Microsystems Professional Services
> Customer Ready Systems   (415) 254-5667
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Sisuite-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
> 


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to