#217 Workqueue.h "fix" no longer works

[Robert McGwier]

with touch workqueue.h /usr/include/linux and touch
workqueue.h
in alsa-driver-0.9.5 and configuring with oss-support
and emu10k1,
I get the following errors which seem to be the same
workqueue
problem:
WARNING!!! The mixer channels for the ALSA driver are
muted by default!!!
**************************************************************************
You would use some ALSA or OSS mixer to set the
appropriate volume.

[root@MP alsa-driver-0.9.5]# modprobe
snd-emu10k1;modprobe snd-pcm-oss;modprobe
snd-mixer-oss;modprobe snd-seq-oss
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
unresolved symbol schedule_work
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o
failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod snd-emu10k1 failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
unresolved symbol schedule_work
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o
failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod snd-pcm-oss failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
unresolved symbol schedule_work
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o
failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod snd-mixer-oss failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
unresolved symbol schedule_work
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o
failed
/lib/modules/2.4.20-18.9custom/kernel/sound/acore/snd.o:
insmod snd-seq-oss failed

I have a in /usr/src/linux/include (point to linux-2.4
pointing to linux-2.4.20-18.9) a workqueue.h file
which is nonzero in length and which I don't want to
delete of course.

HELP. This all worked with 0.9.4 and now I cannot go
back, same errors. Why can't this be tested and
resolved rather than distributed like this?