> > The pcic module contains a reference to a symbol that's only present in > > the kernel when the card* devices are statically compiled in. Ie. if > > you remove pcic* and card* you can't load the pcic module. > > I have card* compiled in (perhaps I should have mentioned that?), and > pcic* kldloaded. > > > This makes the pcic module useless, and, as I said, renders any > > combination other than 100% static *broken*. > > Rubbish! Why is my system working?
Because you have an horrific mishmash of bits; it's not meant to be broken up as you have. > > > Two solutions; 1) don't compile pcic into your kernel; 2) remove the > > > kldload pcic from rc.pccard; 3) fix kldload to not load modules when > > > their functionality is already compiled in (_Three_ Solutions!!). > > > > 1) is a non-solutuion. 3) is where the correct answer lies, but until > > the file/module dichotomy is resolved, it's not possible to do that. > > 1) works (and needs tidying up). > > Any suggestions for a kernel neophyte on how to get stuck into 3)? Not really; you'd need to study how KLD currently works, then go back over the discussions that Peter, Doug, I and others have had about how we might identify modules within a file, and implement it. I fear that it will result in binary incompatability (again). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
