Thanks for reply, But still nothing USB here except the Keyboard, i'll try out the system wihtout the USB keyboard, in, but the keyboard is working simply very fine, thruout the installation system, till it comes over crashing. But still i will try it again in morning, first thing, and get back. ... Thanks a lot On Thu, 17 Feb 2005 13:46:38 -0600, Peter Eisch <peter@xxxxxxxx> wrote: > > Are you installing via USB? If so, do you have the USB drivers in your > stage2.img for the kernel that the cdrom is booting? Changing drives isn't > as important as know that the controller that the drive is connected through > has driver support available. > > I hate to keep harping on the stage2.img, but after the kernel loads using > initrd.img as it's root filesystem and before the installer starts, > pivotroot flips in the stage2.img. So everything may boot just fine from > the cdrom but the installer can't find the install media because the > driver's no longer available after the pivotroot. > > This pretty much exhausts my ideas and experiences. > > peter > > On 2/16/05 10:09 PM, "Jaswinder Singh Kohli" <jskohli@xxxxxxxxx> wrote: > > > I checked the CD Media for errors, worked very fine otherwise. > > Did a installation from same CD to different hardware piece eServer > > xSeries Blade thing > > from IBM, worked like charm. > > > > Now since i changed the ROM drive and other things in the machine, > > either there is some > > incompatibility b/w the hardware and kernel 2.6.x or anaconda. > > > > Since the same CD works on different hardware as mentioned. > > The hardware is cPCI-6860A based system from ADLINK Technologies, comes with > > SCSI card from MPT > > > > Details over here. > > http://www.powerbridge.de/daten_e/p_picmg2.16-cpu/cpci-6860/cpci-6860.htm > > ours is, 2Ghz 2 way LV Xeon processors > > > > > > > > > > On Wed, 16 Feb 2005 21:29:06 +0800, John Summerfield > > <debian@xxxxxxxxxxxxxxxxxxxxxx> wrote: > >> On Wednesday 16 February 2005 13:07, Jaswinder Singh Kohli wrote: > >>> It is always giving same error, > >>> error -2147483630 reading header: cpio read failed - Success > >> > >> There's a buif in cpio right there. > >> The negative number is nonseens, and "cpio read failed - Success" > >> means that cpio detected an error, presumably in a read operation, and then > >> then used some function that worked before saving errno or creating a useful > >> error message. > >> > >> The missing information _may_ help you resolve the problem. You could, > >> perheps, check your media for errors; I can imagine (without investingating) > >> that at some points cpio gets to read from the install CD/DVD. > >> > >> -- > >> > >> Cheers > >> John Summerfield > >> tourist pics: http://environmental.disaster.cds.merseine.nu/ > >> > >> _______________________________________________ > >> Anaconda-devel-list mailing list > >> Anaconda-devel-list@xxxxxxxxxx > >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list > >> > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Regards JSK jskohli (AT) gmail (DOT) com
