Skip to contentSkip to conversation

kernel 2.4.19 error with usbcore.o

DISCUSSION Daya Cooppan 3 participants 3 messages Sep 18, 2002

lore
Share & tools
lore
#0 lore raw

Hi

I think there is a bug in kernel 2.4.19 under the usb section. I proceeded to build kernel 2.4.19 on a RH7.3, DELL SMP system. I have a wireless usb mouse, usb SanDisk, etc. Anyway the problem showed up when I was trying to get the usb mouse to work. This is not a new system ...I did have all the hw and sw components working under 2.4.5.

The default for the USB section is to included USB support (y) in the kernel. I am assuming the usbcore.o got incorporated into the kernel build tree during [make dep; make bzImage; make modules; make modules_install]. I continued to get mousedev errors ...verified that I had mouse support, hid support, uhci support, all this look good. As soon as I changed "USB Support" from (y) to (m), i.e. made usbcore.o a loadable module WALLA! usb devices started to work. Question: Is there a bug with (y) support for "USB Support" ?

I also noticed usbdrv.o resulted in errors when included (y) in the kernel:
___________________________________
s.o ipc/ipc.o \
drivers/parport/driver.o drivers/char/char.o

drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/pcmcia/pcmcia.o drivers/net/pcmcia/pcmcia_net.o drivers/pnp/pnp.o drivers/video/video.o drivers/usb/usbdrv.o \
       net/network.o \
       /usr/src/linux-2.4.19/arch/i386/lib/lib.a 
/usr/src/linux-2.4.19/lib/lib.a /usr/src/linux-2.4.19/arch/i386/lib/lib.a \
       --end-group \
       -o vmlinux

drivers/usb/usbdrv.o: In function `hidinput_hid_event':
drivers/usb/usbdrv.o(.text+0x12b05): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12bae): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12c0e): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12c31): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12c4f): undefined reference to input_event' drivers/usb/usbdrv.o: In function hidinput_connect':
drivers/usb/usbdrv.o(.text+0x12ebc): undefined reference to input_register_device' drivers/usb/usbdrv.o: In function hidinput_hid_event':
drivers/usb/usbdrv.o(.text+0x12b30): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12b9b): undefined reference to input_event' drivers/usb/usbdrv.o(.text+0x12bd6): undefined reference to input_event' drivers/usb/usbdrv.o: In function hidinput_disconnect':
drivers/usb/usbdrv.o(.text+0x12ed9): undefined reference to `input_unregister_device'
make: *** [vmlinux] Error 1
_______________

Any ideas ?

Right now I am using usbcore.o as a loadable module and every thing works fine.

Please cc me at [email protected]

Take Care,
Daya

#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 7 lines · Daya Cooppan

Hi

I think there is a bug in kernel 2.4.19 under the usb section. I proceeded to build kernel 2.4.19 on a RH7.3, DELL SMP system. I have a wireless usb mouse, usb SanDisk, etc. Anyway the problem showed up when I was trying to get the usb mouse to work. This is not a new system ...I did have all the hw and sw components working under 2.4.5.

It has been reported before, but I couldn't reproduce it.

Quoted 8 lines

The default for the USB section is to included USB support (y) in the kernel. I am assuming the usbcore.o got incorporated into the kernel build tree during [make dep; make bzImage; make modules; make modules_install]. I continued to get mousedev errors ...verified that I had mouse support, hid support, uhci support, all this look good. As soon as I changed "USB Support" from (y) to (m), i.e. made usbcore.o a loadable module WALLA! usb devices started to work. Question: Is there a bug with (y) support for "USB Support" ?

Can you provide an exact copy of the CONFIG_USB and CONFIG_INPUT lines from your kernel .config for a working case, and a broken case?

Quoted 1 line

I also noticed usbdrv.o resulted in errors when included (y) in the kernel:

This is probably important :-|
Looks like some include breakage. I'll take another look if you send me the two cases for the kenrel .config.
<snip>

- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9h/0lW6pHgIdAuOMRAjIdAKC2P9R5LJ7QnoDbH/HPtGUnNWOqtACdGaTt MDIxcw51mvIcuhukjYpYm88=
=nuTs
-----END PGP SIGNATURE-----

#2 lore raw
In reply to Daya Cooppan
Quoted 10 lines · Daya Cooppan

Hi

The default for the USB section is to included USB support (y) in the kernel. I am assuming the usbcore.o got incorporated into the kernel build tree during [make dep; make bzImage; make modules; make modules_install]. I continued to get mousedev errors ...verified that I had mouse support, hid support, uhci support, all this look good. As soon as I changed "USB Support" from (y) to (m), i.e. made usbcore.o a loadable module WALLA! usb devices started to work. Question: Is there a bug with (y) support for "USB Support" ?

No, you need to set CONFIG_INPUT to y if you are also selecting the HID driver to be compiled into the kernel. That should solve your problem.

thanks,

greg k-h