mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daya Cooppan <dcooppan@attbi.com>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.4.19 error with usbcore.o
Date: Tue, 17 Sep 2002 23:23:40 -0500	[thread overview]
Message-ID: <3D87FFCC.6040003@attbi.com> (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 dcooppan@attbi.com

Take Care,
Daya


             reply	other threads:[~2002-09-18  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  4:23 Daya Cooppan [this message]
2002-09-18  4:12 ` Brad Hards
2002-09-18  4:50 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D87FFCC.6040003@attbi.com \
    --to=dcooppan@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®