Ok, then I think we've figured out our problem which to me looks like a bug, or probably better put, a "shortcoming" in the PCMCIA "loader" design. It looks like unlike most drivers, you cannot put the PCMCIA driver on the kickstart "driverdisk" device. The "driverdisk" info isn't loaded up at until after the PCMCIA code in "loader.c". It would be handy if you could put PCMCIA drivers on your "driverdisk" device though. The alternative for creating an unattended load, which is what we ended up doing, is building your own image with your modules in the "initrd" module ball "modules.cgz". Oh well... Am I correct? - Matt Erik Troan wrote: > > On Tue, 5 Jun 2001, Matt Fahrner wrote: > > > Is there any hope of getting this documented (other than the suggestion > > that I do it, which though fair is not the answer I'm looking for)? it > > really is a black hole. > > No chance at all. Very few people need it, and those who do should be > able do figure it out. > > > Also, if you've got a sec, if you used the "driverdisk" command, does it > > matter where in the kickstart file it goes? > > Well, it has to be lumped with the other commands (it can't be in > %post or %packages, for example), but within that, no. > > Erik > > ------------------------------------------------------------------------------- > | "Amazingly, there are significant numbers of 30-something women now who | > | want to learn how to box - something that most sensible American men gave | > | up years ago." - New York Times Magazine | > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list -- --------------------------------------------------------------------- Matt Fahrner 2 South Park St. Manager of Networking Willis House Burlington Coat Factory Warehouse Lebanon, N.H. 03766 TEL: (603) 448-4100 xt 5150 USA FAX: (603) 443-6190 Matt.Fahrner@xxxxxxxx ---------------------------------------------------------------------
