On Mon, Aug 07, 2006 at 08:00:47AM -0500, Jay Cliburn wrote: > On Mon, Aug 07, 2006 at 08:38:28AM +0100, Paul Howarth wrote: > > > > For a driver disk to be recognized as such by anaconda, it needs far > > more than the module itself to be present. You might take a look at the > > Advansys driver disk I made to support installation of FC1, FC3, and > > FC4: > > > > http://www.city-fan.org/ftp/contrib/drivers/advansys/ > > Thanks Paul. I neglected to state in the OP that I had constructed the > requisite files into an image that was transferred to the floppy, but I > was confused as to whether the .o or the .ko should be included in the > modules.cgz file. Some references on the web, and even a "build a driver > disk" script from Via Technologies, include only the .o file, and that > seems counterintuitive. In the end, I included both. (Still doesn't > work, though.) I also used your and Pasi's June 2006 exchange on > fedora-list relating to this topic as one of my references. > Some links related to driver disks: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=3266&forum=29 http://forums.fedoraforum.org/showthread.php?t=113660 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195899 I've successfully built custom driver disk (floppy) images for RHEL4.x and CentOS 4.x, as you can figure out from the urls above. But because of some unknown reason I can't get my driver disks working with FC5 or FC6t1.. (see the bug above). > > > > However, it is possible to manually load the driver if all you have is > > the .ko file. See for example: > > > > http://www.keffective.com/mvsata/ > > Thanks for this. I ran across it early in my information search, but I > didn't realize its significance until just now with your comment. I'll > try this method this evening when I get home. > Hmm.. I should try this too. -- Pasi ^ . . Linux / - \ Choice.of.the .Next.Generation. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
