Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Christoph Hellwig 

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 kernel statically,
> otherwise we get a whole lot of kernel log spam on startup, see the
> exchange on the KBUILD list for more details.)
>
> [...]
>
> Any thoughts?

You could just try what I suggested back in t9p times:

adding hub.o to export-objs

I know this is an ugly hack - but it should work at least.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Greg KH 

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-pre4.1/drivers/usb/Makefile
> --- 0-test10-pre4.1/drivers/usb/Makefile Mon, 02 Oct 2000 15:28:44 +1100 kaos 
>(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
> +++ 0-test10-pre4.1(w)/drivers/usb/Makefile Thu, 19 Oct 2000 19:05:04 +1100 kaos 
>(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
> @@ -99,6 +99,10 @@
>  obj-m:= $(filter-out $(obj-y), $(obj-m))
>  int-m:= $(filter-out $(int-y), $(int-m))
>  
> +# Take multi-part drivers out of obj-y and put components in.
> +
> +obj-y:= $(filter-out $(list-multi), $(obj-y)) $(int-y)
> +
>  # Translate to Rules.make lists.
>  
>  O_OBJS   := $(filter-out $(export-objs), $(obj-y))


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 kernel statically,
otherwise we get a whole lot of kernel log spam on startup, see the
exchange on the KBUILD list for more details.)

Bleah, if we had the LINK_FIRST stuff in, then this rule could go back
and fix the problem.  Although I agree that not being able to compile at
all is _much_ worse than having to put up with a bunch of messages at
boot time.

Any thoughts?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Keith Owens 

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
>something here?

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-pre4.1/drivers/usb/Makefile
--- 0-test10-pre4.1/drivers/usb/Makefile Mon, 02 Oct 2000 15:28:44 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
+++ 0-test10-pre4.1(w)/drivers/usb/Makefile Thu, 19 Oct 2000 19:05:04 +1100 kaos 
+(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
@@ -99,6 +99,10 @@
 obj-m  := $(filter-out $(obj-y), $(obj-m))
 int-m  := $(filter-out $(int-y), $(int-m))
 
+# Take multi-part drivers out of obj-y and put components in.
+
+obj-y  := $(filter-out $(list-multi), $(obj-y)) $(int-y)
+
 # Translate to Rules.make lists.
 
 O_OBJS := $(filter-out $(export-objs), $(obj-y))

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Keith Owens 

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
something here?

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-pre4.1/drivers/usb/Makefile
--- 0-test10-pre4.1/drivers/usb/Makefile Mon, 02 Oct 2000 15:28:44 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
+++ 0-test10-pre4.1(w)/drivers/usb/Makefile Thu, 19 Oct 2000 19:05:04 +1100 kaos 
+(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
@@ -99,6 +99,10 @@
 obj-m  := $(filter-out $(obj-y), $(obj-m))
 int-m  := $(filter-out $(int-y), $(int-m))
 
+# Take multi-part drivers out of obj-y and put components in.
+
+obj-y  := $(filter-out $(list-multi), $(obj-y)) $(int-y)
+
 # Translate to Rules.make lists.
 
 O_OBJS := $(filter-out $(export-objs), $(obj-y))

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Greg KH 

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-pre4.1/drivers/usb/Makefile
 --- 0-test10-pre4.1/drivers/usb/Makefile Mon, 02 Oct 2000 15:28:44 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
 +++ 0-test10-pre4.1(w)/drivers/usb/Makefile Thu, 19 Oct 2000 19:05:04 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
 @@ -99,6 +99,10 @@
  obj-m:= $(filter-out $(obj-y), $(obj-m))
  int-m:= $(filter-out $(int-y), $(int-m))
  
 +# Take multi-part drivers out of obj-y and put components in.
 +
 +obj-y:= $(filter-out $(list-multi), $(obj-y)) $(int-y)
 +
  # Translate to Rules.make lists.
  
  O_OBJS   := $(filter-out $(export-objs), $(obj-y))


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 kernel statically,
otherwise we get a whole lot of kernel log spam on startup, see the
exchange on the KBUILD list for more details.)

Bleah, if we had the LINK_FIRST stuff in, then this rule could go back
and fix the problem.  Although I agree that not being able to compile at
all is _much_ worse than having to put up with a bunch of messages at
boot time.

Any thoughts?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-19 Thread Christoph Hellwig 

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 kernel statically,
 otherwise we get a whole lot of kernel log spam on startup, see the
 exchange on the KBUILD list for more details.)

 [...]

 Any thoughts?

You could just try what I suggested back in t9p times:

adding hub.o to export-objs

I know this is an ugly hack - but it should work at least.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Greg KH 

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 errors on all (?) exported symbols when I try to build all
> >of USB into the kernel.  Example (one of many):
> >
> >usbcore.o: In function `usb_set_address':
> >usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
> >usb.o(.text+0x1b90): first defined here
> 
> Remove usb.o from the list of objects that make up usbcore.

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
something here?

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Keith Owens 

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 kernel.  Example (one of many):
>
>usbcore.o: In function `usb_set_address':
>usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
>usb.o(.text+0x1b90): first defined here

Remove usb.o from the list of objects that make up usbcore.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

RE: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Dunlap, Randy 

Greg,

That's fine with me, especially if it fixes this problem.

Go for it.

~Randy
___
|Randy Dunlap |
|randy.dunlap_at_intel.com503-696-2055|
|NOTE: Any views presented here are mine alone|
|& may not represent the views of my employer.|
---

> -Original Message-
> From: Greg KH [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 18, 2000 1:54 PM
> To: Randy Dunlap
> Cc: Keith Owens; Claude LeFrancois (LMC); [EMAIL PROTECTED]
> 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 that anyway, so I'd recommend it.  Especially 
> if it fixes
> this problem.
> 
> Want a patch to do it?
> 
> thanks,
> 
> greg k-h
> 
> -- 
> greg@(kroah|wirex).com
> http://immunix.org/~greg
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Greg KH 

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,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Randy Dunlap 

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/Makefile Mon, 02 Oct 2000 15:28:44 +1100
> kaos (linux-2.4/n/b/19_Makefile 1.1.1.10 644)
> +++ 0-test10-pre3.1(w)/drivers/usb/Makefile Wed, 18 Oct 2000 13:17:59
> +1100 kaos (linux-2.4/n/b/19_Makefile 1.1.1.10 644)
> @@ -38,7 +38,7 @@ obj-  :=
> 
>  # Each configuration option enables a list of files.
> 
> -obj-$(CONFIG_USB)  += usbcore.o
> +obj-$(CONFIG_USB)  += usbcore.o usb.o
>  obj-$(CONFIG_USB_UHCI) += usb-uhci.o
>  obj-$(CONFIG_USB_UHCI_ALT) += uhci.o
>  obj-$(CONFIG_USB_OHCI) += usb-ohci.o

Keith-

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 kernel.  Example (one of many):

usbcore.o: In function `usb_set_address':
usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
usb.o(.text+0x1b90): first defined here


I guess that we could go ahead and merge usb-core.c into usb.c
if there's no good/simple solution to this.

Thanks,
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Randy Dunlap 

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/Makefile Mon, 02 Oct 2000 15:28:44 +1100
 kaos (linux-2.4/n/b/19_Makefile 1.1.1.10 644)
 +++ 0-test10-pre3.1(w)/drivers/usb/Makefile Wed, 18 Oct 2000 13:17:59
 +1100 kaos (linux-2.4/n/b/19_Makefile 1.1.1.10 644)
 @@ -38,7 +38,7 @@ obj-  :=
 
  # Each configuration option enables a list of files.
 
 -obj-$(CONFIG_USB)  += usbcore.o
 +obj-$(CONFIG_USB)  += usbcore.o usb.o
  obj-$(CONFIG_USB_UHCI) += usb-uhci.o
  obj-$(CONFIG_USB_UHCI_ALT) += uhci.o
  obj-$(CONFIG_USB_OHCI) += usb-ohci.o

Keith-

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 kernel.  Example (one of many):

usbcore.o: In function `usb_set_address':
usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
usb.o(.text+0x1b90): first defined here


I guess that we could go ahead and merge usb-core.c into usb.c
if there's no good/simple solution to this.

Thanks,
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

RE: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Dunlap, Randy 

Greg,

That's fine with me, especially if it fixes this problem.

Go for it.

~Randy
___
|Randy Dunlap |
|randy.dunlap_at_intel.com503-696-2055|
|NOTE: Any views presented here are mine alone|
| may not represent the views of my employer.|
---

 -Original Message-
 From: Greg KH [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, October 18, 2000 1:54 PM
 To: Randy Dunlap
 Cc: Keith Owens; Claude LeFrancois (LMC); [EMAIL PROTECTED]
 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 that anyway, so I'd recommend it.  Especially 
 if it fixes
 this problem.
 
 Want a patch to do it?
 
 thanks,
 
 greg k-h
 
 -- 
 greg@(kroah|wirex).com
 http://immunix.org/~greg
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Keith Owens 

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 kernel.  Example (one of many):

usbcore.o: In function `usb_set_address':
usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
usb.o(.text+0x1b90): first defined here

Remove usb.o from the list of objects that make up usbcore.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-18 Thread Greg KH 

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 errors on all (?) exported symbols when I try to build all
 of USB into the kernel.  Example (one of many):
 
 usbcore.o: In function `usb_set_address':
 usbcore.o(.text+0x1b90): multiple definition of `usb_set_address'
 usb.o(.text+0x1b90): first defined here
 
 Remove usb.o from the list of objects that make up usbcore.

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
something here?

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-17 Thread Keith Owens 

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 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
+++ 0-test10-pre3.1(w)/drivers/usb/Makefile Wed, 18 Oct 2000 13:17:59 +1100 kaos 
+(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
@@ -38,7 +38,7 @@ obj-  :=
 
 # Each configuration option enables a list of files.
 
-obj-$(CONFIG_USB)  += usbcore.o
+obj-$(CONFIG_USB)  += usbcore.o usb.o
 obj-$(CONFIG_USB_UHCI) += usb-uhci.o
 obj-$(CONFIG_USB_UHCI_ALT) += uhci.o
 obj-$(CONFIG_USB_OHCI) += usb-ohci.o

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-17 Thread Claude LeFrancois (LMC) 


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-test10-pre3.
When I recompile the kernel with the USB core as a module, everything works
fine.
Thanks a lot for your support,
Thanks,
Claude.
Greg KH wrote:
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 my
> /proc/ksyms related to USB with the USB core driver compiled into
the
> kernel. The __VERSIONED_SYMBOL seem strange to me. I think this is
why
> the symbols are unresolved. Is it a compiler problem ?
Can you send me your .config file that generates this?
And also can you do a 'sh scripts/ver_linux' from your 2.4.0-test10-pre1
directory?
thanks,
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg

-- 

Claude LeFrançois, System and Network Administrator
Ericsson Research Canada (LMC)
8300 Décarie, Ville Mont-Royal, Québec, Canada, H4P 2N2
Tel: (514) 345-7900 x7579, Fax: (514) 345-6149
Email: [EMAIL PROTECTED] 
 

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_M686FXSR is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_BYTES=32
CONFIG_X86_USE_STRING_486=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_TOSHIBA=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y

#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
CONFIG_CARDBUS=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
CONFIG_ACPI=y
# CONFIG_ACPI_INTERPRETER is not set
CONFIG_ACPI_S1_SLEEP=y
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_XD=m
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_BLK_DEV_LVM=m
CONFIG_LVM_PROC_FS=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
#

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-17 Thread Claude LeFrancois (LMC) 


Hello Greg,
Ihave 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-test10-pre3.
When I recompile the kernel with the USB core as a module, everything works
fine.
Thanks a lot for your support,
Thanks,
Claude.
Greg KH wrote:
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 my
> /proc/ksyms related to USB with the USB core driver compiled into
the
> kernel. The __VERSIONED_SYMBOL seem strange to me. I think this is
why
> the symbols are unresolved. Is it a compiler problem ?
Can you send me your .config file that generates this?
And also can you do a 'sh scripts/ver_linux' from your 2.4.0-test10-pre1
directory?
thanks,
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg

--

Claude LeFranois, System and Network Administrator
Ericsson Research Canada (LMC)
8300 Dcarie, Ville Mont-Royal, Qubec, Canada, H4P 2N2
Tel: (514) 345-7900 x7579, Fax: (514) 345-6149
Email: [EMAIL PROTECTED]


#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_M686FXSR is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_BYTES=32
CONFIG_X86_USE_STRING_486=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_TOSHIBA=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y

#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
CONFIG_CARDBUS=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
CONFIG_ACPI=y
# CONFIG_ACPI_INTERPRETER is not set
CONFIG_ACPI_S1_SLEEP=y
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_XD=m
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_BLK_DEV_LVM=m
CONFIG_LVM_PROC_FS=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-17 Thread Keith Owens 

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 +1100 kaos 
(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
+++ 0-test10-pre3.1(w)/drivers/usb/Makefile Wed, 18 Oct 2000 13:17:59 +1100 kaos 
+(linux-2.4/n/b/19_Makefile 1.1.1.10 644)
@@ -38,7 +38,7 @@ obj-  :=
 
 # Each configuration option enables a list of files.
 
-obj-$(CONFIG_USB)  += usbcore.o
+obj-$(CONFIG_USB)  += usbcore.o usb.o
 obj-$(CONFIG_USB_UHCI) += usb-uhci.o
 obj-$(CONFIG_USB_UHCI_ALT) += uhci.o
 obj-$(CONFIG_USB_OHCI) += usb-ohci.o

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-13 Thread Greg KH 

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 my
> /proc/ksyms related to USB with the USB core driver compiled into the
> kernel. The __VERSIONED_SYMBOL seem strange to me. I think this is why
> the symbols are unresolved. Is it a compiler problem ? 

Can you send me your .config file that generates this?

And also can you do a 'sh scripts/ver_linux' from your 2.4.0-test10-pre1
directory?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-13 Thread Claude LeFrancois (LMC) 


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. The __VERSIONED_SYMBOL
seem strange to me. I think this is why the symbols are unresolved. Is
it a compiler problem ?
c01dd8b0 __VERSIONED_SYMBOL(usb_ifnum_to_if)
c01dd904 __VERSIONED_SYMBOL(usb_epnum_to_ep_desc)
c01dd6b0 __VERSIONED_SYMBOL(usb_register)
c01dd83c __VERSIONED_SYMBOL(usb_deregister)
c01dd748 __VERSIONED_SYMBOL(usb_scan_devices)
c01ddce4 __VERSIONED_SYMBOL(usb_alloc_bus)
c01ddd54 __VERSIONED_SYMBOL(usb_free_bus)
c01ddd68 __VERSIONED_SYMBOL(usb_register_bus)
c01dde28 __VERSIONED_SYMBOL(usb_deregister_bus)
c01de298 __VERSIONED_SYMBOL(usb_alloc_dev)
c01de318 __VERSIONED_SYMBOL(usb_free_dev)
c01de348 __VERSIONED_SYMBOL(usb_inc_dev_use)
c01dded4 __VERSIONED_SYMBOL(usb_driver_claim_interface)
c01ddef4 __VERSIONED_SYMBOL(usb_interface_claimed)
c01ddf14 __VERSIONED_SYMBOL(usb_driver_release_interface)
c01defb4 __VERSIONED_SYMBOL(usb_root_hub_string)
c01dfd18 __VERSIONED_SYMBOL(usb_new_device)
c01e1640 __VERSIONED_SYMBOL(usb_reset_device)
c01df1c0 __VERSIONED_SYMBOL(usb_connect)
c01df0ac __VERSIONED_SYMBOL(usb_disconnect)
c01ddba4 __VERSIONED_SYMBOL(usb_check_bandwidth)
c01ddc68 __VERSIONED_SYMBOL(usb_claim_bandwidth)
c01ddca4 __VERSIONED_SYMBOL(usb_release_bandwidth)
c01df308 __VERSIONED_SYMBOL(usb_set_address)
c01df338 __VERSIONED_SYMBOL(usb_get_descriptor)
c01df3e8 __VERSIONED_SYMBOL(usb_get_class_descriptor)
c01df040 __VERSIONED_SYMBOL(__usb_get_extra_descriptor)
c01df498 __VERSIONED_SYMBOL(usb_get_device_descriptor)
c01df444 __VERSIONED_SYMBOL(usb_get_string)
c01dfbe0 __VERSIONED_SYMBOL(usb_string)
c01df4fc __VERSIONED_SYMBOL(usb_get_protocol)
c01df548 __VERSIONED_SYMBOL(usb_set_protocol)
c01df8cc __VERSIONED_SYMBOL(usb_get_report)
c01df928 __VERSIONED_SYMBOL(usb_set_report)
c01df588 __VERSIONED_SYMBOL(usb_set_idle)
c01df6a0 __VERSIONED_SYMBOL(usb_clear_halt)
c01df764 __VERSIONED_SYMBOL(usb_set_interface)
c01df97c __VERSIONED_SYMBOL(usb_get_configuration)
c01df7fc __VERSIONED_SYMBOL(usb_set_configuration)
c01de708 __VERSIONED_SYMBOL(usb_get_current_frame_number)
c01de350 __VERSIONED_SYMBOL(usb_alloc_urb)
c01de3a4 __VERSIONED_SYMBOL(usb_free_urb)
c01de3b8 __VERSIONED_SYMBOL(usb_submit_urb)
c01de3e8 __VERSIONED_SYMBOL(usb_unlink_urb)
c01de608 __VERSIONED_SYMBOL(usb_control_msg)
c01de6a0 __VERSIONED_SYMBOL(usb_bulk_msg)
Thanks,
Claude.
-- 
Claude LeFrançois, System and Network Administrator
Ericsson Research Canada (LMC)
8300 Décarie, Ville Mont-Royal, Québec, Canada, H4P 2N2
Tel: (514) 345-7900 x7579, Fax: (514) 345-6149
Email: [EMAIL PROTECTED] 
 

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-13 Thread Greg KH 

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 my
 /proc/ksyms related to USB with the USB core driver compiled into the
 kernel. The __VERSIONED_SYMBOL seem strange to me. I think this is why
 the symbols are unresolved. Is it a compiler problem ? 

Can you send me your .config file that generates this?

And also can you do a 'sh scripts/ver_linux' from your 2.4.0-test10-pre1
directory?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-05 Thread Greg KH 

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@(kroah|wirex).com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-05 Thread Greg KH 

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@(kroah|wirex).com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-03 Thread Greg KH 

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
> 'unresolved symbols' and the usb mouse works.

Very strange, I'll beat on this some more today and try to see what's
up.

thanks for letting us know.

greg k-h
(I must remember to keep chanting, "the Makefile is your friend, the
Makefile is your friend...")

-- 
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re:2.4.0-test9-pre8, usb, unresolved symbols

2000-10-03 Thread f5ibh 


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 modutils package the more recent one?
> Did this same thing happen for 2.4.0-test8?

modutils version is 2.3.16
I had not the problem with test8, the last one without problem was test9-pre7.
So the problem came with test9-pre8.

The .config file is basically the same as with previous versions.

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
'unresolved symbols' and the usb mouse works.

---

Regards
Jean-Luc

---

CONFIG_INPUT=m
# CONFIG_INPUT_KEYBDEV is not set
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_NS558 is not set
# CONFIG_INPUT_LIGHTNING is not set
# CONFIG_INPUT_PCIGAME is not set
CONFIG_INPUT_ANALOG=m
...
# USB support
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# Miscellaneous USB options
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# USB Controllers
CONFIG_USB_UHCI=m
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set
# USB Devices
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_USS720 is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_NET1080 is not set
# USB Human Interface Devices (HID)
CONFIG_USB_HID=m
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re:2.4.0-test9-pre8, usb, unresolved symbols

2000-10-03 Thread f5ibh 


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 modutils package the more recent one?
 Did this same thing happen for 2.4.0-test8?

modutils version is 2.3.16
I had not the problem with test8, the last one without problem was test9-pre7.
So the problem came with test9-pre8.

The .config file is basically the same as with previous versions.

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
'unresolved symbols' and the usb mouse works.

---

Regards
Jean-Luc

---

CONFIG_INPUT=m
# CONFIG_INPUT_KEYBDEV is not set
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_NS558 is not set
# CONFIG_INPUT_LIGHTNING is not set
# CONFIG_INPUT_PCIGAME is not set
CONFIG_INPUT_ANALOG=m
...
# USB support
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# Miscellaneous USB options
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# USB Controllers
CONFIG_USB_UHCI=m
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set
# USB Devices
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_USS720 is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_NET1080 is not set
# USB Human Interface Devices (HID)
CONFIG_USB_HID=m
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-03 Thread Greg KH 

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
 'unresolved symbols' and the usb mouse works.

Very strange, I'll beat on this some more today and try to see what's
up.

thanks for letting us know.

greg k-h
(I must remember to keep chanting, "the Makefile is your friend, the
Makefile is your friend...")

-- 
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-02 Thread Greg KH 

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 modules_install' ?
> 
> I've a Debian 2.2 system. With Debian, I use the "make-kpkg" command to build
> the kernel in a Debian package. I ALWAYS use the same process to compile
> kernel. Then, I install the new kernel with dpkg as any .deb package ... I think
> I've built 100's of them now. depmod reports the same error :
> 
> depmod: *** Unresolved symbols in /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o
> depmod: *** Unresolved symbols in 
>/lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o

Is your modutils package the most recent one?
Did this same thing happen for 2.4.0-test8?

Can you send me / the list your .config?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

RE: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-02 Thread Dunlap, Randy 

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]]
> 
> 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 "make-kpkg" 
> command to build
> the kernel in a Debian package. I ALWAYS use the same process 
> to compile
> kernel. Then, I install the new kernel with dpkg as any .deb 
> package ... I think
> I've built 100's of them now. depmod reports the same error :
> 
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o
> 
> I use the following in my modules.conf to load automatically 
> all the usb related
> stuff when starting 'gpm'. This works with the previous 
> test9-prex patches.
> 
> # USB mouse
> #--
> alias char-major-13 mousedev
> 
> post-install input modprobe -k hid
> post-install hid modprobe -k usb-uhci
> 
> ---

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re:2.4.0-test9-pre8, usb, unresolved symbols

2000-10-02 Thread f5ibh 


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 "make-kpkg" command to build
the kernel in a Debian package. I ALWAYS use the same process to compile
kernel. Then, I install the new kernel with dpkg as any .deb package ... I think
I've built 100's of them now. depmod reports the same error :

depmod: *** Unresolved symbols in /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o

I use the following in my modules.conf to load automatically all the usb related
stuff when starting 'gpm'. This works with the previous test9-prex patches.

# USB mouse
#--
alias char-major-13 mousedev

post-install input modprobe -k hid
post-install hid modprobe -k usb-uhci

---
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

RE: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-02 Thread Dunlap, Randy 

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 have
/etc/modules.conf setup to load it automatically?
Did you run depmod after 'make modules_install' ?

~Randy


> -- 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 i586 unknown
> Kernel modules 2.3.16
> Gnu C  2.95.2
> Binutils   2.9.5.0.41
> Linux C Library2.1.3
> Dynamic linker ldd: version 1.9.11
> Linux C++ Library  2.9.
> Procps 2.0.6
> Mount  2.10o
> Net-tools  2.05
> Console-tools  0.2.3
> Sh-utils   2.0
> Modules Loaded nls_iso8859-1 ide-cd cdrom isofs 
> parport_pc lp parport input autofs4 rtc serial isa-pnp unix
> 
> 
> 
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_deregister
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_set_idle
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol __usb_get_extra_descriptor
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_register
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_set_protocol
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_string
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_get_class_descriptor
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_submit_urb
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: unresolved 
> symbol usb_unlink_urb
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: insmod 
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o failed
> /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o: insmod hid failed
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_claim_bandwidth
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_release_bandwidth
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_check_bandwidth
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_alloc_bus
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_free_dev
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_inc_dev_use
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_deregister_bus
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_disconnect
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_connect
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_new_device
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_root_hub_string
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_alloc_dev
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_register_bus
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> unresolved symbol usb_free_bus
> /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> insmod /lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o failed
> i/lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o: 
> insmod usb-uhci failed
> 
> -
> Regards
>   Jean-Luc

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.0-test9-pre8, usb, unresolved symbols

2000-10-02 Thread Greg KH 

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 modules_install' ?
 
 I've a Debian 2.2 system. With Debian, I use the "make-kpkg" command to build
 the kernel in a Debian package. I ALWAYS use the same process to compile
 kernel. Then, I install the new kernel with dpkg as any .deb package ... I think
 I've built 100's of them now. depmod reports the same error :
 
 depmod: *** Unresolved symbols in /lib/modules/2.4.0-test9/kernel/drivers/usb/hid.o
 depmod: *** Unresolved symbols in 
/lib/modules/2.4.0-test9/kernel/drivers/usb/usb-uhci.o

Is your modutils package the most recent one?
Did this same thing happen for 2.4.0-test8?

Can you send me / the list your .config?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/