Geofrey Rainey <mailto:Geofrey.Rainey@xxxxxxxxxx> scribbled on Monday, October 22, 2007 11:08 PM: That's strange. I recently installed three machines with RHEL4u3 (which is rather old by now) with scsi-harddrives and using Adaptec 29320LPE-cards and had no problem with the OS seeing the cards and the connected harddrives. Anaconda correctly identified and used the adaptec 79xx drivers at boot and install. I did however have serious problems continuining installation after the initial boot with the sata-cdrom drives. Turns out after a while that the settings in bios were set wrong for sata-drives; for some reason the sata was set to emulate pata and not native ahci-something (default settings in bios to emulate pata with sata-drives? Legacy settings?)... After changing that sata drives were correctly identified and correct drivers used. In any case, I always set the "PnP-enabled OS" in bios to "yes". With linux this has always worked for me. Maybe you should try too and see if it makes a difference? YMMV of course and so on. 8-] HTH. > Hello, > > I recently had a similar problem installing RHEL5.0 on a box with an > Adaptec 7901x controller. > > To resolve I had to select "linux noprobe" during the install and > explicitly select the required > Drivers. In my case I needed the following drivers to get the kernel to > recognize the scsi device: > > I2o_block > Aic79xx (because my controller was a 7901x) > > And also the tg3 (network driver, but didn't work, see below) > > After this the kernel could see the scsi driver and enabled me to > install onto the scsi device. > However the same problem then emerged with the network driver and I > couldn't seem to resolve > This by explicitly specifying the tg3 driver during install, so I > installed RHEL5 anyway minus network. > To resolve this I downloaded the latest kernel source from kernel.org > and recompiled it enabling both the > Requisite drivers for the network card and the scsi device by compiling > the drivers into the kernel > Itself - as opposed to LKM's. > > So to summarise, the linux noprobe method allowed me to install the > RHEL5 operating system onto > The scsi device by explicitly selecting the requisite scsi drivers (but > without network), and a > kernel recompile of a generic kernel was necessary to get the network > drivers to install as well > as the scsi drivers. > > This was as interesting problem that despite logging a job with Redhat, > the problem was unable to be > Resolved using the Redhat kernel even though I also unpacked the initrd > image and verified that > All the drivers I needed were indeed contained in the image. > > Let me know how you get on, and if you need more help with anything > above. > > Regards, > Geofrey Rainey. > > > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Johan Booysen > Sent: Monday, 22 October 2007 9:09 p.m. > To: sorin.srbu@xxxxxxxxxxxxx; General Red Hat Linux discussion list > Subject: RE: Adaptec SCSI RAID 2000S > > I don't think management over here will go for CentOS. Besides, if > CentOS is the same as Red Hat, I assume that it too will not have the > driver I need..? > > Thanks for the suggestion, though! > > Johan > > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Sorin Srbu > Sent: 22 October 2007 07:51 > To: 'General Red Hat Linux discussion list' > Subject: RE: Adaptec SCSI RAID 2000S > > Johan Booysen <> scribbled on Friday, October 19, 2007 6:28 PM: > > You should do fine with CentOS5 as a replacement for RHEL5. CentOS is > binary compatible, a clone if you want, of RHEL. Only real difference > (and the one I can care slightly about) is that CentOS has had all the > RHEL-logos etc stripped and that it uses yum for updating instead of > RHEL's up2date and the RHN. > > I use CentOS myself for trying out stuff before deploying to our RHEL3/4 > machines. So far so good. I also like the fact that CentOS is supported > as long as RHEL is. Redhat will support v5 until 2011?), and since > CentOS is basically the same thing as RHEL, the same will be true for > support and updates for CentOS. > > See this thread on the CentOS forums, it might help you decide: > http://www.centos.org/modules/newbb/viewtopic.php?topic_id=3107&forum=35 > . 8-) > > [off-track] > I used Fedora before to try out stuff before, but thought the fast > update-cycle was a bit too bleeding edge. I searched around a while and > came across CentOS and haven't looked back since. > [on-track] > > HTH. > > > >> Matt, >> >> Good question, and a very valid point. But anyway, this box is kind >> of a test-lab Oracle server, and needs to be RHEL5 for that purpose. >> I believe it will be pretty heavily used, so virtualizing it won't happen >> - I'll bet my last penny on that, and on the Springboks, by the way! :) >> >> >> I think the next thing to do is to perhaps flash the Adaptec adapter's > >> BIOS to a newer version, and then see if the driver will load...I'm >> pretty certain that I've exhausted all other options for now. >> >> Will see what the boss says on Monday... >> >> Thanks very much for your reply. >> >> Johan >> >> -----Original Message----- >> From: redhat-list-bounces@xxxxxxxxxx >> [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Matt >> Sent: 19 October 2007 17:18 >> To: 'General Red Hat Linux discussion list' >> Subject: RE: Adaptec SCSI RAID 2000S >> >> Perhaps this is not the answer you are looking for, but maybe you can >> install another distro (Fedora or an older CENTOS) to get driver support. >> Also, could using a virtual server work? I am just wondering if you >> can place something like CENT as the host OS then run VMWare and maybe > >> create a virtual machine with RHEL5? Perhaps this VM will not require > >> direct hardware support for the controller? You might be able to >> virtualize part of your infrastructure as well and run a legacy OS >> which supports your controller - then, include this box in the virtual > >> infrastructure. >> >> Maybe the real question is why is it that you need to run RHEL5 on a 4 > >> year old box? I am not saying there is a problem with it, but is it >> essential that REHL5 is run on this one? >> >> Just some thoughts for you... >> >> -----Original Message----- >> From: redhat-list-bounces@xxxxxxxxxx >> [mailto:redhat-list-bounces@xxxxxxxxxx] >> On Behalf Of Andrew Bacchi >> Sent: Friday, October 19, 2007 11:41 AM >> To: General Red Hat Linux discussion list >> Subject: Re: Adaptec SCSI RAID 2000S >> >> I hope you've already solved this problem. Have you checked the >> Adaptec web site for a Linux driver? If anyone has one, it would be the >> OEM. >> >> >> Johan Booysen wrote: >>> I urgently need advice on this: I need to install RHEL5 on a server >>> that is probably about 4 years old. It contains an Adaptec SCSI RAID > >>> 2000S adapter, and there is no driver available that I can track down > >>> on short notice (and none included on the RHEL5 discs). Anaconda >>> does not detect any disks on the server during installation. >>> >>> Anyone know what my best bet is to get around this, or where to find a >>> driver that will work? >>> >>> Thanks very much. >>> >>> Johan >> >> -- -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
