I am currently working on performing an install of RH62 onto the DL360G2 (5i controller - cciss driver needed). So I've successfully built the cciss driver for 2.2.14-5.0BOOT. I've updated boot.img with the cciss.o driver, updated pcitable, and module-info. I can boot to the updated boot.img floppy and get the installer to load the cciss driver (text expert mode - choose hard drive install, load cciss driver, choose back, then choose CDRom install). I can manually fdisk and mke2fs the drives on the 5i controller during installation (at the F2 - BASH# prompt). Anaconda doesn't seem to want to work right with the device nodes. Do I need to redo anaconda so that it understands the /dev/cciss/c0d0 structure? When the cciss driver loads, on screen #4 <5>RAMDISK: Compressed image found at block 0 <4>VFS: Mounted root (ext2 filesystem). <7>VFS: Disk change detected on device fd(2,0) <7>cciss: Device b178 has been found at 1 20 <6>Compaq CISS Driver (v 1.0.4) <6>Found 1 controller(s) <6> blocks= 35553120 block_size= 512 <6> heads= 255, sectors= 32, cylinders= 4357 <4> <4> ccissa: ccissa1 ccissa2 <7>VFS: Disk change detected on device ide0(3,0) <7>ISO 9660 Extensions: RRIP_1991A Notice the strange line: <4> ccissa: ccissa1 ccissa2 what is ccissa? I can't find it anywhere in /usr/src/linux-2.2.14-5.0. It appears that this value is generated and is cciss + a for the first controller. I went as far as creating device nodes for cciss: c0d0 and c0d0p1 - c0d0p9. I placed these device nodes in /dev and in /dev/cciss of the initrd on the boot.img image I modified above. I even created a "ccissa b 104 0", and "cissa1 b 104 "1 thru "ccissa9 b 104 9" in the dev directory of the initrd. The installer didn't pick up any of these device nodes and I'm not sure how to tell what I need to give it. I have more notes at http://www.cpqlinux.com/rh62_cciss.html Any ideas on how to get RH62 installer to understand the dev structure would be great. Also If I could get the download locations for the floppies too. Sincerely, Richard Black http://www.cpqlinux.com http://www.compaq.com/linux -----Original Message----- From: Peter Bowen [mailto:pzb@xxxxxxxxxxxxxx] Sent: Thursday, December 12, 2002 7:06 PM To: Mary Deck Cc: anaconda-devel-list@xxxxxxxxxx Subject: Re: questions about anaconda updates on a RH6.2 cd On Thu, 2002-12-12 at 19:29, Mary Deck wrote: > Hi, Peter, > > I saw your instructions for building RH6.2 CD, and it's got me > somewhat encouraged and quite a bit frustrated. I'm glad to hear that people find them useful. > > Let me start with what I'm trying to accomplish: I'm trying to get > RH6.2 running on a Compaq DL380G2, which is not supported because the > array controller on that box ("5i") requires cciss. > There are two problems with this: anaconda doesn't recognize drives on > the cciss controller (so I can't install to those drives), and even if > it did, the image that it installs doesn't know about cciss. > > I've been given some updates (for anaconda and dd) that are supposed > to make anaconda recognize the drives; from RH, I have > boot-20000407.img and update-disk-20001025.img; from my CPQ contact, I > have anaconda updates and cciss dd. I haven't been able to get them > to work because the combination is too big to fit on a floppy, and I > can't find any way to read more than one update disk during install. > One much more involved question: I think all the above will get > anaconda to be able to recognize drives on the 5i controller, but I > don't think that's all I need. Is there a way to update the kernel > that is installed from the CD, as well as anaconda? I've tried to distill your email down to the key problems: You need to install RHL6.2 on a Compaq DL380G2, which as a Compaq raid controller which uses the cciss driver. Compaq has given you two floppy images -- an updates floppy, and a driver disk. RH has released an updated set of boot floppies, and an updates floppy. You need to make everything work together. First, you should join anaconda-devel-list@xxxxxxxxxxx That list includes many people who want to do similar things, myself included. Second, you should know that anaconda can use as many as _three_ floppies during install -- a boot disk, an updates disk, and a driver disk. So really, your only problem is going to be merging the two updates floppies together. The first step is to figure out how many of the files on the update floppies overlap, and, of those, how many of them are identical? Thanks. Peter _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/anaconda-devel-list