unresolved symbol __udivsi3_i4

unresolved symbol __udivsi3_i4

[Donald Duckie]

hi!

can somebody please help me how to overcome this
problem:
unresolved symbol __udivsi3_i4

I compiled the snull files that i got from 
http://www.oreilly.com.tw/editor_column/a138_read.htmland
ran depmod -a -F /proc/ksyms 2.4.18 snull.o

And in another machine (my running machine), I got the
following files from my compilation machine:
snull.o
/lib/modules/2.4.18/*

In my running machine, I ran modprobe but got this
error:
Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
  <cut>
modprobe: unresolved symbol __udivsi3_i4
  <cut>

The gcc version that is used is:
[aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
Reading specs from
/usr/lib/gcc-lib/sh-linux/3.0.3/specs
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man --target=sh-linux
--host=i686-pc-linux-gnu --build=i
686-pc-linux-gnu --disable-c99 --disable-nls
--enable-languages=c,c++ --with-system-zlib
--with-gxx-include-dir=/usr/sh-
linux/include/g++-v3
--includedir=/usr/sh-linux/include
--enable-threads=posix --enable-long-long
Thread model: posix
gcc version 3.0.3


Running nm -l-s snull.o
00000000 a *ABS*
  <cut>
         U __udivsi3_i4
/home/aphrodite/snull/snull3/snull/snull.c:355
  <cut>


the block in snull.c that contains ine 355 is:
    352     if (lockup && ((priv->stats.tx_packets +
1) % lockup) == 0) {
    353         /* Simulate a dropped transmit
interrupt */
    354         netif_stop_queue(dev);
    355         PDEBUG("Simulate lockup at %ld, txp
%ld\n", jiffies,
    356                         (unsigned long)
priv->stats.tx_packets);
    357     }
(which seems to  be okey)


The only modification to the downloaded snull files is
on snull.c:
     30 //#include <linux/malloc.h> /* kmalloc() */
     31 #include <linux/slab.h> /* kmalloc()
deprecated use slab.h instead*/


can anyone please tell me how to deal with this
unresolved symbol __udivsi3_i4?


thank you very much.
-donald



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

Re: unresolved symbol __udivsi3_i4

[Randy.Dunlap]

On Thu, 23 Sep 2004 19:10:50 -0700 (PDT) Donald Duckie wrote:

| hi!

Hi again, Donald-

Note:  I haven't forgotten your other question.
Is is still a problem?

| can somebody please help me how to overcome this
| problem:
| unresolved symbol __udivsi3_i4

That clearly shouldn't be happening, and that symbol isn't in
snull.o when I build it (on x86).

| I compiled the snull files that i got from 
| http://www.oreilly.com.tw/editor_column/a138_read.htmland
| ran depmod -a -F /proc/ksyms 2.4.18 snull.o

How did you build snull (or all of the LDD drivers)?
What command(s)?

| And in another machine (my running machine), I got the
| following files from my compilation machine:
| snull.o
| /lib/modules/2.4.18/*
| 
| In my running machine, I ran modprobe but got this
| error:
| Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
|   <cut>
| modprobe: unresolved symbol __udivsi3_i4
|   <cut>

So the problem machine is an sh-arch machine?
Maybe gcc 3.0.3 has some problem on sh.
Can you try this on some other architecture machine?

| The gcc version that is used is:
| [aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
| Reading specs from
| /usr/lib/gcc-lib/sh-linux/3.0.3/specs
| Configured with: ../configure --prefix=/usr
| --mandir=/usr/share/man --target=sh-linux
| --host=i686-pc-linux-gnu --build=i
| 686-pc-linux-gnu --disable-c99 --disable-nls
| --enable-languages=c,c++ --with-system-zlib
| --with-gxx-include-dir=/usr/sh-
| linux/include/g++-v3
| --includedir=/usr/sh-linux/include
| --enable-threads=posix --enable-long-long
| Thread model: posix
| gcc version 3.0.3
| 
| 
| Running nm -l-s snull.o
| 00000000 a *ABS*
|   <cut>
|          U __udivsi3_i4
| /home/aphrodite/snull/snull3/snull/snull.c:355
|   <cut>

Seeing an objdump of that function (snull_hw_tx) should/could be helpful.

| the block in snull.c that contains ine 355 is:
|     352     if (lockup && ((priv->stats.tx_packets +
| 1) % lockup) == 0) {
|     353         /* Simulate a dropped transmit
| interrupt */
|     354         netif_stop_queue(dev);
|     355         PDEBUG("Simulate lockup at %ld, txp
| %ld\n", jiffies,
|     356                         (unsigned long)
| priv->stats.tx_packets);
|     357     }
| (which seems to  be okey)

Yes.

| The only modification to the downloaded snull files is
| on snull.c:
|      30 //#include <linux/malloc.h> /* kmalloc() */
|      31 #include <linux/slab.h> /* kmalloc()
| deprecated use slab.h instead*/
| 
| 
| can anyone please tell me how to deal with this
| unresolved symbol __udivsi3_i4?


--
~Randy

Re: unresolved symbol __udivsi3_i4

[Randy.Dunlap]

On Thu, 23 Sep 2004 19:10:50 -0700 (PDT) Donald Duckie wrote:

| hi!
| 
| can somebody please help me how to overcome this
| problem:
| unresolved symbol __udivsi3_i4
| 
| I compiled the snull files that i got from 
| http://www.oreilly.com.tw/editor_column/a138_read.htmland
| ran depmod -a -F /proc/ksyms 2.4.18 snull.o
| 
| And in another machine (my running machine), I got the
| following files from my compilation machine:
| snull.o
| /lib/modules/2.4.18/*
| 
| In my running machine, I ran modprobe but got this
| error:
| Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
|   <cut>
| modprobe: unresolved symbol __udivsi3_i4
|   <cut>

Let me try this again.  I suspect that the problem is the '%' (mod)
operator at line 351.  Can you just delete part of that if-test
to prove or disprove my suspicion?


| The gcc version that is used is:
| [aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
| Reading specs from
| /usr/lib/gcc-lib/sh-linux/3.0.3/specs
| Configured with: ../configure --prefix=/usr
| --mandir=/usr/share/man --target=sh-linux
| --host=i686-pc-linux-gnu --build=i
| 686-pc-linux-gnu --disable-c99 --disable-nls
| --enable-languages=c,c++ --with-system-zlib
| --with-gxx-include-dir=/usr/sh-
| linux/include/g++-v3
| --includedir=/usr/sh-linux/include
| --enable-threads=posix --enable-long-long
| Thread model: posix
| gcc version 3.0.3
| 
| 
| Running nm -l-s snull.o
| 00000000 a *ABS*
|   <cut>
|          U __udivsi3_i4
| /home/aphrodite/snull/snull3/snull/snull.c:355
|   <cut>
| 
| 
| the block in snull.c that contains ine 355 is:
|     352     if (lockup && ((priv->stats.tx_packets +
| 1) % lockup) == 0) {
|     353         /* Simulate a dropped transmit
| interrupt */
|     354         netif_stop_queue(dev);
|     355         PDEBUG("Simulate lockup at %ld, txp
| %ld\n", jiffies,
|     356                         (unsigned long)
| priv->stats.tx_packets);
|     357     }
| (which seems to  be okey)
| 
| 
| The only modification to the downloaded snull files is
| on snull.c:
|      30 //#include <linux/malloc.h> /* kmalloc() */
|      31 #include <linux/slab.h> /* kmalloc()
| deprecated use slab.h instead*/
| 
| 
| can anyone please tell me how to deal with this
| unresolved symbol __udivsi3_i4?
| 
| 
| thank you very much.
| -donald

--
~Randy

Re: unresolved symbol __udivsi3_i4

[Donald Duckie]

hi randy!

thank you very much for your help.

it is indeed the % (mod) operator that generates the
unresolved symbol. it is also true with the /
(division) operator.  

is there any patch on this for
2.4.18-sh? or how will i do away with this problem
aside from commenting it out from the code?

btw, the previous unresolved symbol problems were
already solved. i just didn't copy the depmod
generated files in the running machine, that was why
those occured.

thank you.



--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:

> On Thu, 23 Sep 2004 19:10:50 -0700 (PDT) Donald
> Duckie wrote:
> 
> | hi!
> | 
> | can somebody please help me how to overcome this
> | problem:
> | unresolved symbol __udivsi3_i4
> | 
> | I compiled the snull files that i got from 
> |
>
http://www.oreilly.com.tw/editor_column/a138_read.htmland
> | ran depmod -a -F /proc/ksyms 2.4.18 snull.o
> | 
> | And in another machine (my running machine), I got
> the
> | following files from my compilation machine:
> | snull.o
> | /lib/modules/2.4.18/*
> | 
> | In my running machine, I ran modprobe but got this
> | error:
> | Using
> /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
> |   <cut>
> | modprobe: unresolved symbol __udivsi3_i4
> |   <cut>
> 
> Let me try this again.  I suspect that the problem
> is the '%' (mod)
> operator at line 351.  Can you just delete part of
> that if-test
> to prove or disprove my suspicion?
> 
> 
> | The gcc version that is used is:
> | [aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
> | Reading specs from
> | /usr/lib/gcc-lib/sh-linux/3.0.3/specs
> | Configured with: ../configure --prefix=/usr
> | --mandir=/usr/share/man --target=sh-linux
> | --host=i686-pc-linux-gnu --build=i
> | 686-pc-linux-gnu --disable-c99 --disable-nls
> | --enable-languages=c,c++ --with-system-zlib
> | --with-gxx-include-dir=/usr/sh-
> | linux/include/g++-v3
> | --includedir=/usr/sh-linux/include
> | --enable-threads=posix --enable-long-long
> | Thread model: posix
> | gcc version 3.0.3
> | 
> | 
> | Running nm -l-s snull.o
> | 00000000 a *ABS*
> |   <cut>
> |          U __udivsi3_i4
> | /home/aphrodite/snull/snull3/snull/snull.c:355
> |   <cut>
> | 
> | 
> | the block in snull.c that contains ine 355 is:
> |     352     if (lockup && ((priv->stats.tx_packets
> +
> | 1) % lockup) == 0) {
> |     353         /* Simulate a dropped transmit
> | interrupt */
> |     354         netif_stop_queue(dev);
> |     355         PDEBUG("Simulate lockup at %ld,
> txp
> | %ld\n", jiffies,
> |     356                         (unsigned long)
> | priv->stats.tx_packets);
> |     357     }
> | (which seems to  be okey)
> | 
> | 
> | The only modification to the downloaded snull
> files is
> | on snull.c:
> |      30 //#include <linux/malloc.h> /* kmalloc()
> */
> |      31 #include <linux/slab.h> /* kmalloc()
> | deprecated use slab.h instead*/
> | 
> | 
> | can anyone please tell me how to deal with this
> | unresolved symbol __udivsi3_i4?
> | 
> | 
> | thank you very much.
> | -donald
> 
> --
> ~Randy
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

Re: unresolved symbol __udivsi3_i4

[Randy.Dunlap]

On Thu, 23 Sep 2004 21:49:52 -0700 (PDT) Donald Duckie wrote:

| hi randy!
| 
| thank you very much for your help.
| 
| it is indeed the % (mod) operator that generates the
| unresolved symbol. it is also true with the /
| (division) operator.  
| 
| is there any patch on this for
| 2.4.18-sh? or how will i do away with this problem
| aside from commenting it out from the code?

Sorry, I don't track sh changes.  However, I do see in 2.4.26
that arch/sh/lib/udivdi3.c contains a __udivdi3() function,
so perhaps you could manage to use it or implement something
similar to it.

Or perhaps you could use a different kernel version.

| btw, the previous unresolved symbol problems were
| already solved. i just didn't copy the depmod
| generated files in the running machine, that was why
| those occured.

Good.

--
~Randy


| --- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| 
| > On Thu, 23 Sep 2004 19:10:50 -0700 (PDT) Donald
| > Duckie wrote:
| > 
| > | hi!
| > | 
| > | can somebody please help me how to overcome this
| > | problem:
| > | unresolved symbol __udivsi3_i4
| > | 
| > | I compiled the snull files that i got from 
| > |
| >
| http://www.oreilly.com.tw/editor_column/a138_read.htmland
| > | ran depmod -a -F /proc/ksyms 2.4.18 snull.o
| > | 
| > | And in another machine (my running machine), I got
| > the
| > | following files from my compilation machine:
| > | snull.o
| > | /lib/modules/2.4.18/*
| > | 
| > | In my running machine, I ran modprobe but got this
| > | error:
| > | Using
| > /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
| > |   <cut>
| > | modprobe: unresolved symbol __udivsi3_i4
| > |   <cut>
| > 
| > Let me try this again.  I suspect that the problem
| > is the '%' (mod)
| > operator at line 351.  Can you just delete part of
| > that if-test
| > to prove or disprove my suspicion?
| > 
| > 
| > | The gcc version that is used is:
| > | [aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
| > | Reading specs from
| > | /usr/lib/gcc-lib/sh-linux/3.0.3/specs
| > | Configured with: ../configure --prefix=/usr
| > | --mandir=/usr/share/man --target=sh-linux
| > | --host=i686-pc-linux-gnu --build=i
| > | 686-pc-linux-gnu --disable-c99 --disable-nls
| > | --enable-languages=c,c++ --with-system-zlib
| > | --with-gxx-include-dir=/usr/sh-
| > | linux/include/g++-v3
| > | --includedir=/usr/sh-linux/include
| > | --enable-threads=posix --enable-long-long
| > | Thread model: posix
| > | gcc version 3.0.3
| > | 
| > | 
| > | Running nm -l-s snull.o
| > | 00000000 a *ABS*
| > |   <cut>
| > |          U __udivsi3_i4
| > | /home/aphrodite/snull/snull3/snull/snull.c:355
| > |   <cut>
| > | 
| > | 
| > | the block in snull.c that contains ine 355 is:
| > |     352     if (lockup && ((priv->stats.tx_packets
| > +
| > | 1) % lockup) == 0) {
| > |     353         /* Simulate a dropped transmit
| > | interrupt */
| > |     354         netif_stop_queue(dev);
| > |     355         PDEBUG("Simulate lockup at %ld,
| > txp
| > | %ld\n", jiffies,
| > |     356                         (unsigned long)
| > | priv->stats.tx_packets);
| > |     357     }
| > | (which seems to  be okey)
| > | 
| > | 
| > | The only modification to the downloaded snull
| > files is
| > | on snull.c:
| > |      30 //#include <linux/malloc.h> /* kmalloc()
| > */
| > |      31 #include <linux/slab.h> /* kmalloc()
| > | deprecated use slab.h instead*/
| > | 
| > | 
| > | can anyone please tell me how to deal with this
| > | unresolved symbol __udivsi3_i4?
| > | 
| > | 
| > | thank you very much.
| > | -donald

Re: unresolved symbol __udivsi3_i4

[Paweł Sikora]

On Friday 24 of September 2004 04:10, Donald Duckie wrote:
> hi!
>
> can somebody please help me how to overcome this
> problem:
> unresolved symbol __udivsi3_i4

the kernel module tries to use a divide operation on machine
that doesn't support that. this could be caused by %,/ operators
or floating point arithmetic. gcc uses emulation in these cases.

# objdump -T /lib/libgcc_s.so.1|grep div
000024c0 g    DF .text  00000162  GLIBC_2.0   __divdi3
00002b80 g    DF .text  000001ed  GCC_3.0     __udivmoddi4
00002870 g    DF .text  00000120  GLIBC_2.0   __udivdi3

you can link module with libgcc.a or fix it.

-- 
/* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property. */

                           #define say(x) lie(x)

Re: unresolved symbol __udivsi3_i4

[Geert Uytterhoeven]

On Fri, 24 Sep 2004, [utf-8] Pawe? Sikora wrote:
> On Friday 24 of September 2004 04:10, Donald Duckie wrote:
> > can somebody please help me how to overcome this
> > problem:
> > unresolved symbol __udivsi3_i4
> 
> the kernel module tries to use a divide operation on machine
> that doesn't support that. this could be caused by %,/ operators
> or floating point arithmetic. gcc uses emulation in these cases.
> 
> # objdump -T /lib/libgcc_s.so.1|grep div
> 000024c0 g    DF .text  00000162  GLIBC_2.0   __divdi3
> 00002b80 g    DF .text  000001ed  GCC_3.0     __udivmoddi4
> 00002870 g    DF .text  00000120  GLIBC_2.0   __udivdi3
> 
> you can link module with libgcc.a or fix it.

Just add an implementation for __udivsi3_i4 to arch/sh/lib/. They already have
udivdi3.c over there.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: unresolved symbol __udivsi3_i4

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

On Fri, 2004-09-24 10:33:12 +0200, Geert Uytterhoeven <geert@linux-m68k.org>
wrote in message <Pine.GSO.4.61.0409241031410.27692@waterleaf.sonytel.be>:
> On Fri, 24 Sep 2004, [utf-8] Pawe? Sikora wrote:
> > On Friday 24 of September 2004 04:10, Donald Duckie wrote:
> > > can somebody please help me how to overcome this
> > > problem:
> > > unresolved symbol __udivsi3_i4
> > # objdump -T /lib/libgcc_s.so.1|grep div
> > 000024c0 g    DF .text  00000162  GLIBC_2.0   __divdi3
> > 00002b80 g    DF .text  000001ed  GCC_3.0     __udivmoddi4
> > 00002870 g    DF .text  00000120  GLIBC_2.0   __udivdi3
> > 
> > you can link module with libgcc.a or fix it.
> 
> Just add an implementation for __udivsi3_i4 to arch/sh/lib/. They already have
> udivdi3.c over there.

Either that (which I don't like!), or have a try compiling the kernel
with -ffreestanding, if your toolchain accepts that. Maybe that doesn't
create these external function calls at all...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: unresolved symbol __udivsi3_i4

[Geert Uytterhoeven]

On Fri, 24 Sep 2004, Jan-Benedict Glaw wrote:
> On Fri, 2004-09-24 10:33:12 +0200, Geert Uytterhoeven <geert@linux-m68k.org>
> wrote in message <Pine.GSO.4.61.0409241031410.27692@waterleaf.sonytel.be>:
> > On Fri, 24 Sep 2004, [utf-8] Pawe? Sikora wrote:
> > > On Friday 24 of September 2004 04:10, Donald Duckie wrote:
> > > > can somebody please help me how to overcome this
> > > > problem:
> > > > unresolved symbol __udivsi3_i4
> > > # objdump -T /lib/libgcc_s.so.1|grep div
> > > 000024c0 g    DF .text  00000162  GLIBC_2.0   __divdi3
> > > 00002b80 g    DF .text  000001ed  GCC_3.0     __udivmoddi4
> > > 00002870 g    DF .text  00000120  GLIBC_2.0   __udivdi3
> > > 
> > > you can link module with libgcc.a or fix it.
> > 
> > Just add an implementation for __udivsi3_i4 to arch/sh/lib/. They already have
> > udivdi3.c over there.
> 
> Either that (which I don't like!), or have a try compiling the kernel

Why don't you like that? It's done that way on most architectures.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: unresolved symbol __udivsi3_i4

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

On Fri, 2004-09-24 13:15:26 +0200, Geert Uytterhoeven <geert@linux-m68k.org>
wrote in message <Pine.GSO.4.61.0409241314530.27692@waterleaf.sonytel.be>:
> On Fri, 24 Sep 2004, Jan-Benedict Glaw wrote:
> > > > > unresolved symbol __udivsi3_i4
> > > > # objdump -T /lib/libgcc_s.so.1|grep div
> > > > 000024c0 g    DF .text  00000162  GLIBC_2.0   __divdi3
> > > > 00002b80 g    DF .text  000001ed  GCC_3.0     __udivmoddi4
> > > > 00002870 g    DF .text  00000120  GLIBC_2.0   __udivdi3
> > > > 
> > > > you can link module with libgcc.a or fix it.
> > > 
> > > Just add an implementation for __udivsi3_i4 to arch/sh/lib/. They already have
> > > udivdi3.c over there.
> > 
> > Either that (which I don't like!), or have a try compiling the kernel
> 
> Why don't you like that? It's done that way on most architectures.

Well, the kernel is (or should be) a freestanding program, so it
shouldn't use *any* external code (and it doesn't, intentionally).
We're working hard not linking in libgcc.a (IIRC some archs actually do
that) (because eg. your compiler was compiled for i686-pc-linux-gnu, you
want to compile for a real i386 and end up with Pentium-alike code in
your i386 kernel).

So people started doing freestanding implementations of eg. __udivsi3 in
their kernel files. But why should they? GCC also could have emitted
inlined code to do that task, without ever calling an external function
for that.

However, this topic has been discussed several times with no real
resolution, so I guess we won't find a real cool solution this time,
too.

MfG, JBG (and greetings from Oldenburg!)

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: unresolved symbol __udivsi3_i4

[Andreas Schwab]

Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:

> Well, the kernel is (or should be) a freestanding program, so it
> shouldn't use *any* external code (and it doesn't, intentionally).
> We're working hard not linking in libgcc.a

libgcc is an intrinsic part of the freestanding implementation provided by
the compiler, just like <stdarg.h>.

> So people started doing freestanding implementations of eg. __udivsi3 in
> their kernel files. But why should they? GCC also could have emitted
> inlined code to do that task, without ever calling an external function
> for that.

Inlining can be less efficient due to icache issues.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Invalid kernel header included in userspace; multi-line string literals are deprecated

[Donald Duckie]

hi!

thank you for the patience in explaining things.
there are some other things in linux that i still need
to understand.
and to answer the questions:
> 1) What is the output of the command uname -r
in my compilation machine, it is 2.4.21-4.EL.
   - and i was cross-compiling with 2.4.18-SH. 
     the /linux was linked to 2.4.18-SH/linux.
   - how do I set my environment such that uname -r
can get the 2.4.18-SH? i think depmod uses it right?
in the machine where i run modprobe but got the
unresolved linking errors (this is a separate
machine), it is 2.4.18-SH. 
> 2) What do you whant to use snull for.?
   - currently i am studying the socket_buffers and
ifc2 implementation and happen to see the snull
sample, and thought this would be a good example to
see how it runs/works.
> 3) What distro are you using.
   - using 2.4.18-SH (redhat)
> 4) [aphrodite@aphrodite2] whoami will return root.
     (though maybe i would admit that  in the several
attempts that i have done, there might be a time
wherein i was not root). but i performed the suggested
operations (insuring that i was root) and still got
the same results.

and here are what i have just noticed lately:
in the machine where i run modprobe with unresolved
linking errors, there is no depmod command, so i
assume that i will run depmod where i compiled the
snull files, transfer the makefile.dep to the other
machine for modprobe to use. is this okey?


and just a minute ago (just came back to this task
today since last week); i renamed /lib to /lib.redhat
and am no longer able to perform any other command to
the machine where i compiled. i can't run mv anymore.
is there a way for me to be able to return /lib.redhat
to /lib?

thank you very for your help  . . . 


--- Richard Adams <pa3gcu@zeelandnet.nl> wrote:

> On Wednesday 15 September 2004 03:30, Donald Duckie
> wrote:
> > hi!
> >
> > i do not want to be assuming now, since i only got
> > some errors from my assumptions. i have performed
> the
> > options mentioned below but got some errors.
> >
> >
> > what is sn0 and sn1?
> 
> They are interface names, that and that only,
> compare them to ethernet 
> devices, they are called ethX.
> 
> > can modprobe or insmod know that snull.o is snull?
> (or
> > am i getting the wrong idea here?)
> 
> Modprobe is the best to use as it is more
> intelligent, i suggest you read the 
> manual page for modprobe.
> Basicly modprobe looks in /lib/modules/`uname -r`/
> for modules, now that 
> suggests there is somthing wrong with your system IF
> everything is like you 
> say below.
> 
> >
> > planning to do the following:
> > > cd /to/snull/dir
> > > modprobe snull
> > > ifconfig sn0 10.1.2.11 up
> > > ifconfig sn1 10.1.2.12 up
> > > route add -net 10.1.2.0 netmask 255.255.255.0
> sn0
> > > route add -net 10.1.2.0 netmask 255.255.255.0
> sn1
> >
> > and the result:
> > ---> cd /lib/modules/2.4.18-sh/misc
> >      ls
> >          snull.o
> >      modprobe  snull
> >          modprobe: Can't locate module snull
> 
> This can be cause by at least 3 main factors,
> 1) You have not run 'depmod -a'
> 2) Your kernel is not called 2.4.18-sh
> 3) Your not root.
> 
> >      (i supposed that i cant continue from here,
> but
> > just tried)
> >      ifconfig sn0 101.11.21.111 up
> >          SIOCSIFADDR: No such device
> >          sn0: unknown interface: No such device
> >          sn0: unknown interface: No such device
> >      ifconfig sn1 101.11.21.121 up
> >          SIOCSIFADDR: No such device
> >          sn1: unknown interface: No such device
> >          sn1: unknown interface: No such device
> >      route add -net 101.11.21.0 netmask
> 255.255.255.0
> > sn0
> >          SIOCADDRT: No such device
> >      route add -net 101.11.21.0 netmask
> 255.255.255.0
> > sn1
> >          SIOCADDRT: No such device
> 
> You told me in a previous mail that you could load
> the module right.?
> But now trying it in anther way it fails right.???
> 
> >
> > planning to do the following:
> > > You can also place the snull modules in
> >
> > /lib/modules/2.4.18/kernel/drivers/net
> >
> > > run depmod -a
> > > place the following in /etc/modules.conf
> > > alias sn0 snull
> > > alias sn1 snull
> >
> > and the result:
> > ---> cp /lib/modules/2.4.18-sh/misc/snull.o
> > /lib/modules/2.4.18-sh/kernel/drivers/net/.
> >      depmod -a
> >      then edited /etc/modules.conf to add the
> > mentioned aliases
> 
> Here you need to do 'depmod -a' to update the
> modules database, if its not run 
> and you use modprobe you "should get a message"
> saying something like, 
> modules.conf is more recent than bla bla bla.
> 
> >      the redo the procedures: modprobe snull;
> ifconfig
> > sn0 101.11.21.111 up; ifconfig sn1 101.11.21.121
> up;
> > route add -net 101.11.21.0 netmask 255.255.255.0
> sn0;
> > route add -net 101.11.21.0 netmask 255.255.255.0
> sn1
> >          the same results were seen
> >
> >
> > what seems to be wrong with sn?
> 
> There should be nothing wrong with sn0 or sn1, you
> said the module compiled,
> i suggest you do the following to see once again if
> all is well.
> 
> su -
> enter passwd for root. (and press enter of course)
> cd /path/to/ldd2-samples-1.0.1/snull
> insmod snull
> ifconfig sn0 10.11.21.111 up
> ifconfig sn1 10.11.21.121 up
> 
> That works here and "should work there as well".
> 
> > am i doing something wrong in here?
> 
> 
> With all due respect, it certainly looks like it.
> 
> Now a few questions here,
> 1) What is the output of the command uname -r
> 2) What do you whant to use snull for.?
> 3) What distro are you using.
> 4) Again with all due respect, if one needs so much
> basic help to get    
> something like this to work then surely one would
> not even know what to use 
> them for would one, now i hope i am wrong on that
> one.
> 
> The following is showing that you dont seem to
> understand what i am saying,
> 
> > > [aphrodite@aphrodite2 snull]$ snull_unload
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The above indicates that you are NOT root.
> 
> > > snull: Operation not permitted
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This almost certainly indicates that you are _NOT_
> root.
> 
> >
> > thanks for all the information and assistance . .
> .
> 
> -- 
> If the Linux community is a bunch of theives because
> they
> try to imitate windows programs, then the Windows
> community
> is built on organized crime.
> 
> Regards Richard
> pa3gcu@zeelandnet.nl
> http://people.zeelandnet.nl/pa3gcu/
> 
> 
> 



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

unresolved symbol __udivsi3_i4

[Donald Duckie]

hi!


Thank you very much for your help on
Subject: Invalid kernel header included in userspace;
multi-line string literals are deprecated :-)
I finally understood where I should be doing depmod
and what I need to do with its generated files.


There is one thing that is currently bugging me
though. Upon running modprobe, this is what I
currently got:
Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
  <cut>
modprobe: unresolved symbol __udivsi3_i4
  <cut>


The gcc version that is used is:
[aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
Reading specs from
/usr/lib/gcc-lib/sh-linux/3.0.3/specs
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man --target=sh-linux
--host=i686-pc-linux-gnu --build=i
686-pc-linux-gnu --disable-c99 --disable-nls
--enable-languages=c,c++ --with-system-zlib
--with-gxx-include-dir=/usr/sh-
linux/include/g++-v3
--includedir=/usr/sh-linux/include
--enable-threads=posix --enable-long-long
Thread model: posix
gcc version 3.0.3


Running nm -l-s snull.o
00000000 a *ABS*
  <cut>
         U __udivsi3_i4
/home/aphrodite/snull/snull3/snull/snull.c:355
  <cut>


the block in snull.c that contains ine 355 is:
    352     if (lockup && ((priv->stats.tx_packets +
1) % lockup) == 0) {
    353         /* Simulate a dropped transmit
interrupt */
    354         netif_stop_queue(dev);
    355         PDEBUG("Simulate lockup at %ld, txp
%ld\n", jiffies,
    356                         (unsigned long)
priv->stats.tx_packets);
    357     }
(which seems to  be okey)


The only modification to the downloaded snull files is
on snull.c:
     30 //#include <linux/malloc.h> /* kmalloc() */
     31 #include <linux/slab.h> /* kmalloc()
deprecated use slab.h instead*/


can anyone please tell me how to deal with this
unresolved symbol __udivsi3_i4?


thank you very much.
-donald

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: unresolved symbol __udivsi3_i4

[Richard Adams]

On Wednesday 22 Sep 2004 12:23, Donald Duckie wrote:
> can anyone please tell me how to deal with this
> unresolved symbol __udivsi3_i4?

Compile it on the machine you intend to use it on.

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs