Hi!
While doing modprobe hid or modprobe usb-uhci, I get the following unresolved
symbols. Config is P200MMX, 64Mb SDRAM.
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux debian-f5ibh 2.4.0-test9 #1 lun oct 2 14:44:11 CEST 2000
Hi,
> From: f5ibh [mailto:[EMAIL PROTECTED]]
>
> Hi!
>
> While doing modprobe hid or modprobe usb-uhci, I get the
> following unresolved
> symbols. Config is P200MMX, 64Mb SDRAM.
All of the missing symbols are in usb.o (usbcore.o module or
usbdrv.o in-kernel). Is usbcore.o loaded or do you h
Hi,
Randy wrote :
> All of the missing symbols are in usb.o (usbcore.o module or
> usbdrv.o in-kernel). Is usbcore.o loaded or do you have
> /etc/modules.conf setup to load it automatically?
> Did you run depmod after 'make modules_install' ?
I've a Debian 2.2 system. With Debian, I use the "m
Well, let's see.
linux/drivers/Makefile did change for test9-pre8.
That's one possibility.
Are you building USB core support in-kernel or as a
module? (Maybe provide your .config file, or at least
the CONFIG_USB_xxx portion of it.)
Thanks,
~Randy
> From: f5ibh [mailto:[EMAIL PROTECTED]]
>
>
On Mon, Oct 02, 2000 at 11:18:49PM +0200, f5ibh wrote:
>
> Hi,
>
> Randy wrote :
> > All of the missing symbols are in usb.o (usbcore.o module or
> > usbdrv.o in-kernel). Is usbcore.o loaded or do you have
> > /etc/modules.conf setup to load it automatically?
> > Did you run depmod after 'make
Hi!
Randy wrote :
> Are you building USB core support in-kernel or as ai
> module? (Maybe provide your .config file, or at least
> the CONFIG_USB_xxx portion of it.)
I use modules, here is part of my .config file.
Remark : I've the same problem with 2.4.0-test9-pre9.
Greg wrote:
> Is your mod
On Tue, Oct 03, 2000 at 06:22:32PM +0200, f5ibh wrote:
> Christoph wrote :
> > Could you try undoing the -pre8 changes to drivers/usb/Makefile?
> THIS was the solution I've compiled 2.4.0-test9-pre9 with the
> drivers/usb/Makefile of the test9-pre7 version of the kernel. I've no more the
> 'u
On Tue, Oct 03, 2000 at 09:54:25AM -0700, Greg KH wrote:
>
> Very strange, I'll beat on this some more today and try to see what's
> up.
I tried this .config on test9 final last night and didn't have any
problems.
Could you see if this is still a problem with test9?
thanks,
greg k-h
--
greg
Hello,
I had the same problem with the USB core driver compiled statically
into the kernel 2.4.0-test10pre1. If I get the whole USB distribution compiled
as a modules, everything works fine. Here is the content of my /proc/ksyms
related to USB with the USB core driver compiled into the kernel. Th
On Fri, Oct 13, 2000 at 01:52:12PM -0400, Claude LeFrancois (LMC) wrote:
> Hello,
>
> I had the same problem with the USB core driver compiled statically into
> the kernel 2.4.0-test10pre1. If I get the whole USB distribution
> compiled as a modules, everything works fine. Here is the content of
Hello Greg,
I have reproduced the problem on 2.4.0-test10-pre3. The information
you have requested is attached to this message and. I also send you an
ouput of dmesg, the result of the command "depmod -ae" and the content
of /proc/ksyms. All the information I send to you are related to 2.4.0-test
Objects that export symbols must be explicitly listed before the
calculation of OX_OBJS. usb.o is not explicitly listed as an object,
it is implicitly included via the link of usbcore.
Index: 0-test10-pre3.1/drivers/usb/Makefile
--- 0-test10-pre3.1/drivers/usb/Makefile Mon, 02 Oct 2000 15:28:44
Keith Owens wrote:
>
> Objects that export symbols must be explicitly listed before the
> calculation of OX_OBJS. usb.o is not explicitly listed as an object,
> it is implicitly included via the link of usbcore.
>
> Index: 0-test10-pre3.1/drivers/usb/Makefile
> --- 0-test10-pre3.1/drivers/usb/M
On Wed, Oct 18, 2000 at 01:47:40PM -0700, Randy Dunlap wrote:
> I guess that we could go ahead and merge usb-core.c into usb.c
> if there's no good/simple solution to this.
I wanted to do that anyway, so I'd recommend it. Especially if it fixes
this problem.
Want a patch to do it?
thanks,
gre
t; Subject: Re: 2.4.0-test9-pre8, usb, unresolved symbols
>
>
> On Wed, Oct 18, 2000 at 01:47:40PM -0700, Randy Dunlap wrote:
> > I guess that we could go ahead and merge usb-core.c into usb.c
> > if there's no good/simple solution to this.
>
> I wanted to do t
On Wed, 18 Oct 2000 13:47:40 -0700,
Randy Dunlap <[EMAIL PROTECTED]> wrote:
>Keith Owens wrote:
>> +obj-$(CONFIG_USB) += usbcore.o usb.o
>
>We still need your help. Using this usb/Makefile change gives
>me errors on all (?) exported symbols when I try to build all
>of USB into the k
On Thu, Oct 19, 2000 at 10:45:36AM +1100, Keith Owens wrote:
> On Wed, 18 Oct 2000 13:47:40 -0700,
> Randy Dunlap <[EMAIL PROTECTED]> wrote:
> >Keith Owens wrote:
> >> +obj-$(CONFIG_USB) += usbcore.o usb.o
> >
> >We still need your help. Using this usb/Makefile change gives
> >me er
On Wed, 18 Oct 2000 22:20:15 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
>> >Keith Owens wrote:
>> >> +obj-$(CONFIG_USB) += usbcore.o usb.o
>I don't think that would work, for if the USB core code is compiled as a
>module, then usb.o has to be part of usbcore.o, or am I missing
>someth
On Thu, Oct 19, 2000 at 07:18:49PM +1100, Keith Owens wrote:
>
> See conclusion, jump to conclusion :(. There was a missing line from
> the boilerplate conversion of lists to old style Makefile variables.
> Forget my previous patch, use this one. Against 2.4.0-test10-pre4.
>
> Index: 0-test10-
In article <[EMAIL PROTECTED]> you wrote:
> Eeek! No, I took that out back in test9-pre7 to solve the ordering
> problem that we were having (the hub driver's __init function in the
> usbcore.o needed to be called _before_ the other driver's __init
> functions when everything is compiled into the
20 matches
Mail list logo