SUSE - your bit is down the bottom, but you might want to read the
complete message.
chesty wrote:
>
> > Damien Curtain wrote:
> > > install the kernel source in /usr/src/linux and do a make config,
> On Tue, Oct 03, 2000 at 11:32:06AM +1100, Terry Collins wrote:
> > The problem has nothing to do with the message produced.
> > The kernel distributed with Suse 6.4 does load modules.
> > I can insmond/rmmod/etc with no problems.
> > "make bttv" produces an erroneous message.
>
> Look at the Makefile, how does it test to see if you kernel
> supports modules? How hard could it be?
You've actually hit upon what my brain had been crystalising around, but
didn't have a bit of the knowledge to know where to look as I've never
written a program under linux.
Suse link /usr/src/linux to /usr/src/linux-2.2.14.SuSE which has NO
.config.
The Makefile for bttv installs to /usr/src/$(CURRENT)/misc, where
CURRENT = $( shell uname -r ) i.e 2.2.14.
/usr/src/linux-2.2.14 has a .config with CONFIG_MODULES=y
So, I gather what was happening was that the make was looking in
/usr/src/linux-2.2.14.SuSE and not seeking a .config and thus deciding
that the kernel was not configured for modules
>
> I'd bet damien gave good advise, you probably need the kernel source
> installed to be able to make kernel modules (makes sense to me), and
> the makefile may look at /usr/src/linux/.config to check for module
> support?
I had already been through installing the source, so that was not the
problem.
There is nothing wrong with the advice given by Damien and Kevin in a
general sense (which is why I posted this reply to the list), but it was
not applicable in this case. I apologize if I had not made the
circumstances clear enough.
The important point was that the kernel was loading modules, but "make
bttv" generated a erroneous message. I wanted to know where that message
was coming from and hopefully why.
Now I know about .config files. A softlink from
/usr/src/linux-2.2.14.SuSE/.config to /usr/src/linux-2.2.14/.config has
fixed the problem.
This is actually the second time I've come across this problem, but the
first time it went away with attempts to fix it, so the real problem and
fix was not found on that occassion.
Suse, Redhat and others who want to do no standard stuff are going to
have to be aware of this problem. It is not something that the average
linux users should have to know.
..........................................................
Bit for SUSE
This is the message you sent me. The solution to the problem is in the
stuff above. i.e - you link /usr/src/linux to /usr/src/linux-ver.SuSE
and this causes the problem as there is no .config file there.
This is some of the message you sent me, so you can follow it up.
----------------------------------------------------------------------
Dear SuSE Linux User,
thank you very much for your message regarding "Error "Modules support
not in kernel""
to [EMAIL PROTECTED]
As you might know, [EMAIL PROTECTED] has been set up for collecting
ideas,
bug reports and comments about our Linux Distribution, SuSE Linux.
--
Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861
email: [EMAIL PROTECTED] www: http://www.woa.com.au
or [EMAIL PROTECTED]
WOA Computer Services <lan/wan, linux/unix, novell>
snail: PO Box 1047, Campbelltown, NSW 2560.
"People without trees are like fish without clean water"
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
