[wplug] I'm a Linux whimp (need kernel help)

[Robert E. Coutch]

Just when I think things are going well.......................................

So I fix up my xorg.conf and manually load the savage.ko module with modprobe.
I fire up X and get a message about my DRI and kernel modules being different 
versions.

No direct rendering.

I fooled with merging in the /usr/src/kernel-modules/dri into 
the /usr/src/linux/drivers/char/drm directory.

After a make modules, still no savage modules.

I'm going to try the CVS stuff again tonight.

Is anyone out there following this and see what I might be doing wrong?


Thanks,

Bob


On Sunday 14 August 2005 01:55 pm, Robert E. Coutch wrote:
> The tips below seemed to work and I was able to do a make modules.
>
> Here's the problems I ran into.
>
> The modules I need made are in a directory called  /usr/src/kernel-modules
> There's nothing in that directory tree for Make to work.
> There are source and header files in there.
>
> I tried copying savage.c, savage.h and all other savage.* files
> into /usr/src/linux/drivers/char/drm and retried make modules.
> All modules were built except for the savage ones.
>
> I re-attempted running the install script from the dri project.
> Again it barked about no kernel config found.
>
> I googled and found these steps:
> cd /usr/src/linux
> zcat /proc/config.gz > .config
> make oldconfig
>
> Now the install script runs much further along until it states:
> Symbol version dump /usr/src/linux-2.6.11.4-21.8/Module.symvers is missing
>
> This file is not under /usr/src/linux either.
>
> On a whim,
> I copied the savage* files (.c and .h) over
> to /usr/src/linux-2.6.11.4-21.8/drivers/char/drm
> and did a make modules from the /usr/src/linux-2.4.11.4-21.8 directory.
> I saw it compile every module in the drm directory EXCEPT the ones I added
> in. Obviously I'm missing something.
>
> Then I do an ls and see that Module.symvers is now there.
>
> I re-run the install script from the dri people.
> Poof - it finally works.
>
> I still have no idea what happened and why inserting the .c and .h code
> from SuSE into the source tree did nothing.
>
> Any comments?
>
>
> Thanks,
>
> Bob
>
> On Friday 12 August 2005 02:53 pm, Robert E. Coutch wrote:
> > Hey - that's a hot tip.  Thanks!!
> >
> > I haven't had time to start fooling with that laptop since I send that
> > first email to the group.
> >
> > Work has been keeping me very busy so I'll take another swing at the
> > laptop this weekend.
> >
> > -Bob
> >
> > On Friday 12 August 2005 08:37 am, Poyner, Brandon wrote:
> > > > Well - It looks like I need to make a kernel config !!!
> > > >
> > > > These are the things I have nightmares about.
> > > > Wish me luck - I'm going in.
> > >
> > > Since I didn't see anybody else mention it, one thing SuSe does is
> > > include the current kernel configuration inside the kernel itself,
> > > which you can find at /proc/config.gz.  They have made it as simple as:
> > >
> > > cd /usr/src/linux && make cloneconfig
> > >
> > > Of course you could also 'zcat /proc/config.gz >
> > > /usr/src/linux/.config' and work it from there with 'make oldconfig'.
> > >
> > > Brandon Poyner
> > > Network Engineer III
> > > CCAC - College Office
> > > 412-237-3086
> > >
> > >
> > > _______________________________________________
> > > wplug mailing list
> > > wplug at wplug.org
> > > http://www.wplug.org/mailman/listinfo/wplug
> >
> > _______________________________________________
> > wplug mailing list
> > wplug at wplug.org
> > http://www.wplug.org/mailman/listinfo/wplug
>
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug