<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28"> <TITLE>RE: FC6t2 Anaconda/installer bug with dd: loads wrong module</TITLE> </HEAD> <BODY>  >"modules.alias" is now required file, and "pcitable" is not used anymore. Nice to know. I guess keeping it backward compatible is going to save a lot of headache for other people. Or anacoda is modified to let user know that this dd kit is using old format which is not supported anymore. For new format the requirement is to use module.alias instead of pcitable. Basically some notification to let user know what's wrong with their ddkit. Ravi -----Original Message----- From: fedora-devel-list-bounces@redhat.com on behalf of Pasi Kärkkäinen Sent: Thu 9/14/2006 2:01 AM To: fedora-devel-list@redhat.com Subject: Re: FC6t2 Anaconda/installer bug with dd: loads wrong module Problem solved.. Driver disk format has changed since RHEL4. FC5 and FC6 (and upcoming RHEL5) are using the new format. "modules.alias" is now required file, and "pcitable" is not used anymore. The checks for these files are broken in FC6 test2, but will be hopefully fixed in the later versions. So if you don't have "pcitable" file installer/anaconda will tell you the driver disk is broken.. but that file is not used anymore, the check is bogus. Also the installer does not check the existence of "modules.alias", which is a required file now.. if that file is missing, the driver disk will _not_ be loaded. Jeremy Katz from Redhat helped to solve this problem. Hopefully the documentation for FC6/RHEL5 will be updated with this new information/format. - Pasi On Wed, Sep 13, 2006 at 08:34:31PM +0300, Pasi Kärkkäinen wrote: > Hi! > > I'm using IBM Blade servers with Qlogic qla4xxx iSCSI HBA adapters. > > Fedora Core kernels don't include the qla4xxx driver for these HBAs. > > I've made my own custom driver disk (dd) images for FC6 test2 [1], but can't get > these images to work. Same kind of custom made dd images work well in RHEL4.. so > something has changed with the driver disk support, I just can't figure out what. > > The problem seems to be that fedora installer (anaconda) loads wrong > module.. for some unknown reason it loads tg3 module instead of qla4xxx. See > screenshots [2]. > > If I load the cd/floppy dd-images over http, then the installer won't load > anything.. and just gives error: "no devices of the appropriate type were > found on this driver disk". In this case the tg3 is already loaded.. > > My driver disk (dd) images [1] look like 100% OK to me.. PCI IDs are double > checked. In fact all the files containing PCI IDs are the same as in RHEL4 > dd images (which work OK). I've also checked the "official" qla4xxx dd > images for RHEL4 by Qlogic. My images look like the same (except that the > modules are compiled for FC kernels - of course). > > Ravi Anand from Qlogic also checked out my dd image, and said it looks > correct. > > I had the same issue with FC5 also.. > > So, what has changed after RHEL4 in the driver disk handling? > I think it Would be quite important to get this working for final FC6.. and RHEL5. > > Thanks! > > [1] <A HREF="http://pasik.reaktio.net/fc-dd/">http://pasik.reaktio.net/fc-dd/</A> > [2] <A HREF="http://pasik.reaktio.net/fc-dd/problem_screenshots/">http://pasik.reaktio.net/fc-dd/problem_screenshots/</A> > > -- Pasi > -- fedora-devel-list mailing list fedora-devel-list@redhat.com <A HREF="https://www.redhat.com/mailman/listinfo/fedora-devel-list">https://www.redhat.com/mailman/listinfo/fedora-devel-list</A> </BODY> </HTML>