in_ntoa built error

in_ntoa built error

[Khai Trinh]

I downloaded the linuxppc2.4 devel tree from bitmover
and tried to build the the ebony kernel for my ebony
board. I got the built error in that in_ntoa is
referenced in the fs/nfs/nfsroot.c file but no include
lib for it.

What is this call anyway? It sounds like the root file
system is broken.

I then went and disable the NFS stuff in the defconfig
file. The kernel is then built. When I loaded the
kernel to Ebony, it failed on mounting the root
filesystem as expected.

Does anybody have a fix for this problem yet?

Regards,

--Khai


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: in_ntoa built error

[Dan Kegel]

Yes.  References to inet_ntoa must be replaced
with references to NIPQUAD. e.g.

printk("s_addr=%d.%d.%d.%d, data_saddr=%d.%d.%d.%d, data_sport=%d",
 NIPQUAD(ms->saddr), NIPQUAD(data_saddr), ntohs(data_sport));

%u is probably better than %d.
- Dan


-----Original Message-----
From: Khai Trinh
To: linuxppc-embedded@lists.linuxppc.org
Sent: 5/24/2002 2:57 PM
Subject: in_ntoa built error


I downloaded the linuxppc2.4 devel tree from bitmover
and tried to build the the ebony kernel for my ebony
board. I got the built error in that in_ntoa is
referenced in the fs/nfs/nfsroot.c file but no include
lib for it.

What is this call anyway? It sounds like the root file
system is broken.

I then went and disable the NFS stuff in the defconfig
file. The kernel is then built. When I loaded the
kernel to Ebony, it failed on mounting the root
filesystem as expected.

Does anybody have a fix for this problem yet?

Regards,

--Khai


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: in_ntoa built error

[Khai Trinh]

By the way, the snippet of the failing log of the
kernel when it was downloading are captured below:

Sending BOOTP requests . OK

IP-Config: Got BOOTP answer from 199.254.9.151, my
address is 199.254.9.207

IP-Config: Complete:

      device=eth0, addr=199.254.9.207,
mask=255.255.255.0, gw=199.254.9.254,

     host=199.254.9.207, domain=, nis-domain=(none),

     bootserver=199.254.9.151,
rootserver=199.254.9.151,
rootpath=/projects/hardhat/khai/devkit/ppc/405/target

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

kmod: failed to exec /sbin/modprobe -s -k
block-major-22, errno = 2

VFS: Cannot open root device "" or 16:01

Please append a correct "root=" boot option

Kernel panic: VFS: Unable to mount root fs on 16:01

 <0>Rebooting in 180 seconds..

Thanks,

--Khai
--- Dan Kegel <dkegel@ixiacom.com> wrote:
>
> Yes.  References to inet_ntoa must be replaced
> with references to NIPQUAD. e.g.
>
> printk("s_addr=%d.%d.%d.%d, data_saddr=%d.%d.%d.%d,
> data_sport=%d",
>  NIPQUAD(ms->saddr), NIPQUAD(data_saddr),
> ntohs(data_sport));
>
> %u is probably better than %d.
> - Dan
>
>
> -----Original Message-----
> From: Khai Trinh
> To: linuxppc-embedded@lists.linuxppc.org
> Sent: 5/24/2002 2:57 PM
> Subject: in_ntoa built error
>
>
> I downloaded the linuxppc2.4 devel tree from
> bitmover
> and tried to build the the ebony kernel for my ebony
> board. I got the built error in that in_ntoa is
> referenced in the fs/nfs/nfsroot.c file but no
> include
> lib for it.
>
> What is this call anyway? It sounds like the root
> file
> system is broken.
>
> I then went and disable the NFS stuff in the
> defconfig
> file. The kernel is then built. When I loaded the
> kernel to Ebony, it failed on mounting the root
> filesystem as expected.
>
> Does anybody have a fix for this problem yet?
>
> Regards,
>
> --Khai
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: in_ntoa built error

[Matt Porter]

On Fri, May 24, 2002 at 04:03:59PM -0700, Khai Trinh wrote:
>
> By the way, the snippet of the failing log of the
> kernel when it was downloading are captured below:

<snip>

> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>
> kmod: failed to exec /sbin/modprobe -s -k
> block-major-22, errno = 2
>
> VFS: Cannot open root device "" or 16:01
>
> Please append a correct "root=" boot option
>
> Kernel panic: VFS: Unable to mount root fs on 16:01

This is normal behavior for your configuration.  On the ebony
port, the default ROOT_DEV is 16:01 (/dev/hda1) if you
don't have CONFIG_BLK_DEV_INITRD or CONFIG_ROOT_NFS
configured.  You can even see kmod trying to load
an ide driver for you.

With CONFIG_ROOT_NFS enabled, it will attempt to root from 00:ff,
the nfs pseudo root device.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: in_ntoa built error

[Khai Trinh]

But Matt, if I turn on CONFIG_BLK_DEV_INITRD or
CONFIG_ROOT_NFS, the code will fail to build with
built error in in_ntoa as I stated earlier. Dan
suggested I replaced it with NIPQUAD. Did he mean
in_ntoa or inet_ntoa?

Regards,
--Khai

--- Matt Porter <porter@cox.net> wrote:
>
> On Fri, May 24, 2002 at 04:03:59PM -0700, Khai Trinh
> wrote:
> >
> > By the way, the snippet of the failing log of the
> > kernel when it was downloading are captured below:
>
> <snip>
>
> > NET4: Unix domain sockets 1.0/SMP for Linux
> NET4.0.
> >
> > kmod: failed to exec /sbin/modprobe -s -k
> > block-major-22, errno = 2
> >
> > VFS: Cannot open root device "" or 16:01
> >
> > Please append a correct "root=" boot option
> >
> > Kernel panic: VFS: Unable to mount root fs on
> 16:01
>
> This is normal behavior for your configuration.  On
> the ebony
> port, the default ROOT_DEV is 16:01 (/dev/hda1) if
> you
> don't have CONFIG_BLK_DEV_INITRD or CONFIG_ROOT_NFS
> configured.  You can even see kmod trying to load
> an ide driver for you.
>
> With CONFIG_ROOT_NFS enabled, it will attempt to
> root from 00:ff,
> the nfs pseudo root device.
>
> Regards,
> --
> Matt Porter
> porter@cox.net
> This is Linux Country. On a quiet night, you can
> hear Windows reboot.
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: in_ntoa built error

[Matt Porter]

On Fri, May 24, 2002 at 04:54:14PM -0700, Khai Trinh wrote:
> But Matt, if I turn on CONFIG_BLK_DEV_INITRD or
> CONFIG_ROOT_NFS, the code will fail to build with
> built error in in_ntoa as I stated earlier. Dan
> suggested I replaced it with NIPQUAD. Did he mean
> in_ntoa or inet_ntoa?

This problem has been fixed for sometime in _devel, your code is
stale.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/