_=3D=3Fus-asc?=
=?us-ascii?Q?ii=3FQ=3F=3D3D5Fme=3D3D3D2C=3D3D5FI=3D3D3DB4m=3D3D5Fan=3D3D?=
=?us-ascii?Q?5Fu=3D3F=3D3D
=5F=3D3D=3D3Fus-a=3F=3D
_=3D=3Fus-ascii=3FQ?=
=?us-ascii?Q?=3Fscii=3D3FQ=3D3Fseless=3D3D5Fheader=3D3D5F!=3D3D3F=3D3D3D?=
=?us-ascii?Q?=3D3F=3D3D=3F=3D?=
On Thu, Mar 09, 2000 at 02:09:51PM +0100, Diego Liziero wrote:
>
> Kernel 2.3.50
> depmod: *** Unresolved symbols in /lib/modules/2.3.50/misc/mad16.o
> depmod: exit_mad16
>
> I got the symbol resolved with this patch:
>
> --- mad16.c.2.3.50.original Thu Mar 9 11:59:38 2000
> +++ mad16.c Thu Mar 9 12:00:08 2000
> @@ -1098,7 +1098,7 @@
> return 0;
> }
>
> -static void __exit cleanup_mad16(void)
> +static void __exit exit_mad16(void)
> {
> if (found_mpu)
> unload_mad16_mpu(&cfg_mpu);
Ok, but module_exit needs to be adjusted, too.
>
> But when I issue a modprobe mad16 I get the following error:
>
> MSS: I/O port conflict
> /lib/modules/2.3.50/misc/ad1848.o: init_module: Device or resource busy
> /lib/modules/2.3.50/misc/ad1848.o: insmod /lib/modules/2.3.50/misc/ad1848.o failed
> /lib/modules/2.3.50/misc/ad1848.o: insmod mad16 failed
>
> If I use the ad1848.o of a 2.3.49 kernel all works fine.
Hmm, with ad1848 something seems to be not ok, I'll look at it ...
Christoph
--
Always remember that you are unique. Just like everyone else.
