Hi,
I've following problems with 2.5.5-dj2:
If I try to enable numlock I get this message: hid-core.c: control queue full
and the numlock LED doesn't shine but numlock is enabled
This is on a USB keyboard (Cherry xyz... the one with included USB hub)
While booting I get this message: hid-core.c: ctrl urb status -32 received
Next problem is the ALSA driver.
I've compiled ALSA directly into the kernel and now I get this messages while booting up:
Advanced Linux Sound Architecture Driver Version 0.9.0beta12 (Tue Feb 26 09:34:24 2002 UTC).
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-0, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-1, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-2, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-3, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-4, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-5, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-6, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
kmod: failed to exec /sbin/modprobe -s -k snd-card-7, errno = 2
PCI: Found IRQ 12 for device 00:12.0
devfs_register(midi): could not append to parent, err: -17
ALSA device list:
#0: ESS ES1938 (Solo-1) rev 0, irq 12
The sound works right but this messages are confusing ;)
Bye
On Mon, Mar 04, 2002 at 09:19:49PM +0100, Sebastian Dr?ge wrote:
> Hi,
> I've following problems with 2.5.5-dj2:
> If I try to enable numlock I get this message: hid-core.c: control queue full
> and the numlock LED doesn't shine but numlock is enabled
> This is on a USB keyboard (Cherry xyz... the one with included USB hub)
> While booting I get this message: hid-core.c: ctrl urb status -32 received
Can you please try 2.5.6-pre2 and let us know if you still have the USB
problem with that kernel?
thanks,
greg k-h
On Mon, Mar 04, 2002 at 02:35:31PM -0800, Greg KH wrote:
> > I've following problems with 2.5.5-dj2:
> > If I try to enable numlock I get this message: hid-core.c: control queue full
> > and the numlock LED doesn't shine but numlock is enabled
> > This is on a USB keyboard (Cherry xyz... the one with included USB hub)
> > While booting I get this message: hid-core.c: ctrl urb status -32 received
>
> Can you please try 2.5.6-pre2 and let us know if you still have the USB
> problem with that kernel?
My money is on it being ok. -dj has vojtech's various new input layer
trickery, which I'm suspecting is the real cause of the problem.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
On Tue, 5 Mar 2002 01:16:04 +0100
Dave Jones <[email protected]> wrote:
> On Mon, Mar 04, 2002 at 02:35:31PM -0800, Greg KH wrote:
> > > I've following problems with 2.5.5-dj2:
> > > If I try to enable numlock I get this message: hid-core.c: control queue full
> > > and the numlock LED doesn't shine but numlock is enabled
> > > This is on a USB keyboard (Cherry xyz... the one with included USB hub)
> > > While booting I get this message: hid-core.c: ctrl urb status -32 received
> >
> > Can you please try 2.5.6-pre2 and let us know if you still have the USB
> > problem with that kernel?
>
> My money is on it being ok. -dj has vojtech's various new input layer
> trickery, which I'm suspecting is the real cause of the problem.
Yes right... 2.5.6-pre2 doesn't compile properly but 2.5.5 doesn't have this problem
If it's really important to test it with 2.5.6-pre2 I'll try it again this evening or tomorrow
Bye
On Wed, 6 Mar 2002 19:32:18 +0100
Sebastian Droege <[email protected]> wrote:
> On Tue, 5 Mar 2002 01:16:04 +0100
> Dave Jones <[email protected]> wrote:
>
> > On Mon, Mar 04, 2002 at 02:35:31PM -0800, Greg KH wrote:
> > > > I've following problems with 2.5.5-dj2:
> > > > If I try to enable numlock I get this message: hid-core.c: control queue full
> > > > and the numlock LED doesn't shine but numlock is enabled
> > > > This is on a USB keyboard (Cherry xyz... the one with included USB hub)
> > > > While booting I get this message: hid-core.c: ctrl urb status -32 received
> > >
> > > Can you please try 2.5.6-pre2 and let us know if you still have the USB
> > > problem with that kernel?
> >
> > My money is on it being ok. -dj has vojtech's various new input layer
> > trickery, which I'm suspecting is the real cause of the problem.
> Yes right... 2.5.6-pre2 doesn't compile properly but 2.5.5 doesn't have this problem
> If it's really important to test it with 2.5.6-pre2 I'll try it again this evening or tomorrow
>
> Bye
Oh shit...
I've named the kernel image wrong... that wasn't 2.5.5 :(
But in 2.5.6-pre2 the error exists, too
Sorry
Bye