Discussion:
Unresolved symbols with mga_vid on 2.4
Martin Collins
2005-06-14 13:21:51 UTC
Permalink
This is a bit of a head-scratcher.

I've been running 2.4.20 happily with mga_vid for months. I
recompiled the kernel to enable UDF writing. When I rebooted mga_vid
wouldn't load.
Naturally I recompiled mga_vid but I get the same result.

depmod -ae says:

depmod: *** Unresolved symbols in
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o
depmod: pci_scan
depmod: map_phys_mem
depmod: unmap_phys_mem
depmod: _GLOBAL_OFFSET_TABLE_
depmod: puts
depmod: printf
depmod: strerror
depmod: mtrr_set_type

modprobe mga_vid says:

/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: couldn't
find the kernel version the module was compiled for
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: insmod
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o failed
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: insmod
mga_vid failed

Can anyone suggest how I might fix this?

Martin
Attila Kinali
2005-06-15 08:21:07 UTC
Permalink
On Tue, 14 Jun 2005 14:21:51 +0100
Post by Martin Collins
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: couldn't
find the kernel version the module was compiled for
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: insmod
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o failed
/lib/modules/2.4.20/kernel/drivers/video/matrox/mga_vid.o: insmod
mga_vid failed
I assume you are using mga_vid from the MPlayer cvs.

Then it's most probably that you compiled mga_vid against the
wrong kernel. The Makefile assumes that you want to compile
mga_vid for the currently running kernel and that it has
a /lib/modules/<kernel-version>/build directory. IIRC 2.4.20
does not yet have one, thus you have to change the KERNEL_DIR
variable at the beginning of the Makefile to somehting like
this:
KERNEL_DIR = /usr/src/linux/

HTH

Attila Kinali
--
郷に入れば郷に従え
Martin Collins
2005-06-15 14:30:01 UTC
Permalink
On Wed, 15 Jun 2005 10:21:07 +0200
Post by Attila Kinali
I assume you are using mga_vid from the MPlayer cvs.
Yes indeed.
Post by Attila Kinali
Then it's most probably that you compiled mga_vid against the
wrong kernel. The Makefile assumes that you want to compile
mga_vid for the currently running kernel and that it has
a /lib/modules/<kernel-version>/build directory. IIRC 2.4.20
does not yet have one, thus you have to change the KERNEL_DIR
variable at the beginning of the Makefile to somehting like
KERNEL_DIR = /usr/src/linux/
Actually there is a build directory at least as far back as 2.4.14.
My problem was that I was trying to build the wrong mga_vid, the
one in the vidix/drivers directory. Looking for KERNEL_DIR gave me
the clue to that, so thanks!
It's still a bit of a mystery why it broke in the first place. Maybe
I wasn't running the kernel I thought I was.

Martin
Attila Kinali
2005-06-16 08:43:52 UTC
Permalink
On Wed, 15 Jun 2005 15:30:01 +0100
Post by Martin Collins
Actually there is a build directory at least as far back as 2.4.14.
My problem was that I was trying to build the wrong mga_vid, the
one in the vidix/drivers directory. Looking for KERNEL_DIR gave me
the clue to that, so thanks!
It's still a bit of a mystery why it broke in the first place. Maybe
I wasn't running the kernel I thought I was.
LOL, yes vidix is vidix and not kernel.
Maybe i should place a note there.

Attila Kinali
--
郷に入れば郷に従え
Loading...