Skip to contentSkip to conversation

mad16 & ad1848 problems in kernel 2.3.50.

DISCUSSION Christoph Hellwig 2 participants 6 messages Mar 9, 2000 Sound

lore
Share & tools
lore
#0 lore raw
Quoted 10 lines · Diego Liziero

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 line 1104

Quoted 8 lines
mad16.c renamed from mad16.c.2.3.50.original +1 -1
@@ -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.

Quoted 9 lines

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

Signature · 1 line
Always remember that you are unique.  Just like everyone else.
#1 lore raw
Quoted 10 lines · Diego Liziero

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 line 1104

Quoted 8 lines
mad16.c renamed from mad16.c.2.3.50.original +1 -1
@@ -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.

Quoted 9 lines

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

Signature · 1 line
Always remember that you are unique.  Just like everyone else.
#2 lore raw
In reply to Christoph Hellwig

_=?us-a? =?us-ascii?Q?scii?Q?seless=5Fheader=5F!=3F=3D?=?

Quoted 10 lines · Diego Liziero

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 line 1104

Quoted 8 lines
mad16.c renamed from mad16.c.2.3.50.original +1 -1
@@ -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.

Quoted 9 lines

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

Signature · 1 line
Always remember that you are unique.  Just like everyone else.
#3 lore raw
In reply to Christoph Hellwig

_=?us-asc? =?us-ascii?Q?ii?Q?=3D5Fme=3D3D2C=3D5FI=3D3DB4m=3D5Fan=3D? =?us-ascii?Q?5Fu=3F=3D _=3D=3Fus-a?=
_=?us-ascii?Q? =?us-ascii?Q??scii=3FQ=3Fseless=3D5Fheader=3D5F!=3D3F=3D3D? =?us-ascii?Q?=3F=3D?=?

Quoted 10 lines · Diego Liziero

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 line 1104

Quoted 8 lines
mad16.c renamed from mad16.c.2.3.50.original +1 -1
@@ -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.

Quoted 9 lines

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

Signature · 1 line
Always remember that you are unique.  Just like everyone else.
#4 lore raw
In reply to Christoph Hellwig

_=?us-asc? =?us-ascii?Q?ii?Q?=3D5Fme=3D3D2C=3D5FI=3D3DB4m=3D5Fan=3D? =?us-ascii?Q?5Fu=3F=3D
_=3D=3Fus-a?=
_=?us-ascii?Q? =?us-ascii?Q??scii=3FQ=3Fseless=3D5Fheader=3D5F!=3D3F=3D3D? =?us-ascii?Q?=3F=3D?=?X-Mutt-References: <[email protected]>
X-Mutt-Fcc: /home/toffi/Mail/sent
Status: RO
Content-Length: 1078
Lines: 38

Quoted 10 lines · Diego Liziero

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 line 1104

Quoted 8 lines
mad16.c renamed from mad16.c.2.3.50.original +1 -1
@@ -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.

Quoted 9 lines

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

Signature · 1 line
Always remember that you are unique.  Just like everyone else.
#5 lore raw
In reply to Christoph Hellwig

Hi Christoph,

I seem to be getting a very similar problem with 2.3.50. I have sound stuff compiled into the kernel. One observation is that in 2.3.50, when sound support is compiled into the kernel, I no longer have the option of specifying the IRQ, Port and DMA values. It seems to be trying to use Plug and Play.

Mar  8 23:14:06 spot kernel: ad1848/cs4248 codec driver Copyright (C) by
Hannu Savolainen 1993-1996 
Mar  8 23:14:06 spot kernel: MSS: I/O port conflict 
Mar  8 23:14:06 spot kernel: YM3812 and OPL-3 driver Copyright (C) by
Hannu Savolainen, Rob Hooft 1993-1996
Mar  8 23:14:06 spot kernel: cs4232.c: I/O port 0xffffffff not free 
Mar  8 23:14:06 spot kernel: adlib: must specify I/O address. 
Quoted 39 lines · Christoph Hellwig
Quoted 10 lines · Diego Liziero

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 Thu Mar 9 12:00:08 2000 line 1104

Quoted 8 lines
mad16.c Thu Mar 9 12:00:08 2000 renamed from mad16.c.2.3.50.original Thu Mar 9 11:59:38 2000 +1 -1
@@ -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.

Quoted 9 lines

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.