problem on netdevice

problem on netdevice

[zhonglei]

hi
   Sorry for bothering you! But would you please give me a hand.When I insert a Intel Pro/100s server Adapter into the PCI slot on Lite5200(motorola MPC5200 development kit) and start the embedded kernel,the kernel run into a dead lock. (Before that I used 'make xconfig' to enable the e100 driver in kernel)
The reports are as follows:
.
.
.
IP-Config: Retrying forever (NFS root)...
eth1: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
eth1: Waiting for the link to be up...
eth1: status: link up, 100 Mbps Full Duplex, auto-negotiation complete.
e100: eth0 NIC Link is Up 100 Mbps Full duplex
Sending DHCP requests ...... timed out!
    Please tell me how can I handle it! Thanks in advance!
Best Regards
zhonglei

Re: problem on netdevice

[Marc Leeman]

>    Sorry for bothering you! But would you please give me a hand.When I in=
sert a Intel Pro/100s server Adapter into the PCI slot on Lite5200(motorola=
 MPC5200 development kit) and start the embedded kernel,the kernel run into=
 a dead lock. (Before that I used 'make xconfig' to enable the e100 driver =
in kernel)

1. The kernel is not in a deadlock; it's just not able to mount a root
filesystem.

2. As Wolfgang told you in the U-boot mailing list, check if the DHCP
packets actually arrive on the server

# tail -f /var/log/syslog

If you do not check this first; doing anything else is useless.

--=20
ash nazg durbatul=FBk, ash nazg gimbatul,
ash nazg thrakatul=FBk agh burzum-ishi krimpatul

Re: problem on netdevice

[Marc Leeman]

> 2. As Wolfgang told you in the U-boot mailing list, check if the DHCP
> packets actually arrive on the server

2b. and verify if your DHCP server handles them: sends out an IP and
has that IP linked to a particular NFS share.

You should have something like:
Nov 24 08:35:17 gemini dhcpd: BOOTREQUEST from 00:04:a5:04:05:53 via eth0
Nov 24 08:35:17 gemini dhcpd: BOOTREPLY for 150.158.231.130 to
hydra_stream_malm.01 (00:04:a5:04:05:53) via eth0
Nov 24 08:35:21 gemini rpc.mountd: authenticated mount request from
150.158.231.130:800 for /home/firmware/mleeman/targets/target.3.0.0.0
(/home/firmware/mleeman/targets/target.3.0.0.0)


--=20
ash nazg durbatul=FBk, ash nazg gimbatul,
ash nazg thrakatul=FBk agh burzum-ishi krimpatul

Re: problem on netdevice

[Marc Leeman]

> [root@198 linuxppc_2_4_devel]# tail -f /var/log/syslog
> tail: /var/log/syslog: No such file or directory
> tail: no files remaining

Depends on your system, the messages might also be directed to
/var/log/messages.

> And I found that my u-boot has detected 2 net adapters.
> But I didn't assign the 2nd one an ip address.Is it the key of the proble=
m?

No.

Either you have stored your kernel in flash in which case whatever IP
configuration the bootloader makes is useless or you have obtained
your kernel over the network; in that case your bootloader
configuration is also not relevant.

--=20
ash nazg durbatul=FBk, ash nazg gimbatul,
ash nazg thrakatul=FBk agh burzum-ishi krimpatul

Re: problem on netdevice

[Marc Leeman]

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

Make certain that your DHCP server is set up correctly (see the attached file).

For the kernel config; make certain you have the following enabled:
[mleeman@gemini linux-2.4.28]$ cat config.nfs |grep NFS
CONFIG_NFS_FS=y
CONFIG_ROOT_NFS=y
[mleeman@gemini linux-2.4.28]$ cat config.nfs |grep ROOT
CONFIG_ROOT_NFS=y
[mleeman@gemini linux-2.4.28]$ cat config.nfs |grep AUTO
CONFIG_AUTOFS4_FS=y
[mleeman@gemini linux-2.4.28]$ cat config.nfs |grep BOOTP  
CONFIG_IP_PNP_BOOTP=y

Yours is not going to be bootp, but something similar with DHCP (same
goes with the att. file).

P.S. reply to the list too

-- 
ash nazg durbatulûk, ash nazg gimbatul,
ash nazg thrakatulûk agh burzum-ishi krimpatul

[-- Attachment #2: NFSSystem.txt --]
[-- Type: text/plain, Size: 5563 bytes --]


   Barco home TWiki > Firmware > FirmwareDocumentation > NFSSystem TWiki webs:
   Firmware | Software | Servers
   Firmware . { Changes | Index | Search | Go ________________ }

   Loading a cramfs is time consuming and during a testing/debugging/development cycle, if this is done quite often. Therefore
   a NFS filesystem, where changes can be done on the fly, is more useful. The boards are configured to use BOOTP for booting.
   In the following, the basic modifications are described to configure a GNU/Linux server to serve as a bootp server.

   First of all, a number of services need to be installed on the serving machine (gemini in this example):
     * a NFS server
     * a DHCP server

   On a GNU/Debian system, the following packages need to be installed:
[mleeman@gemini mleeman]$ dpkg -l |grep nfs
ii  nfs-common     1.0-2woody1    NFS support files common to client and serve
ii  nfs-kernel-ser 1.0-2woody1    Kernel NFS server support
[mleeman@gemini mleeman]$ dpkg -l |grep dhcp
ii  dhcp           2.0pl5-19      DHCP server for automatic IP address assignment

   Other distributions should have similarly named packages.

   The main configuration for this is done in a number of files:
     * /etc/exports contains the files of your files on the server which are exported over NetworkFileSystem (NFS). In this
       case, this will be the root filesystem for our embedded board.
     * /etc/dhcpd.conf contains the configuration of the DHCP server. You have to make certain that you are the only DHCP
       server in your netrange. If you do not, a lot of unpleasantness can occuur since your server will reply with DHCPNACK on
       requests for the official DHCP server.

   Extract a root filesystem tarball (or something similar) to your homedir (or a predetermined location). A free and general
   purpose PPC root filesystem can be found in ELDK (http://www.denx.de/ELDK/).
[mleeman@gemini mleeman]$ mkdir targets
[mleeman@gemini mleeman]$ tar xvfz target.scn.tar.gz -C targets/

   With the current BARCO builds, you can also use the CompressedFileSystem backup to create your NFS root FS:
# mkdir fs; cd fs
# bzcat ../target-2.0.0.10.cpio.bz2 | cpio -vi

   Do not forget to copy your stream.cfg file, which basically re-confirms your IP address to ppcserver into the
   /root/ppcstream directory.

   Secondly, add the following entry in the exports file, indicating that you want to export without any condition:
/home/mleeman/targets/target.scn.01 *(rw,no_root_squash,no_all_squash)

   Finally, restart the NFS server:
[mleeman@gemini mleeman]$ sudo /etc/init.d/nfs-kernel-server restart

   We're halfway through. We now need to link this NFS filesystem to the MAC address of our board. This is done by adding the
   following in the /etc/dhcpd.conf file:
# global configuration options
# allow bootp packages
allow bootp;
# the first subnet we listen to
subnet 150.158.231.0 netmask 255.255.255.0 {
  # options for the subnet in question
  option routers 150.158.231.1;
  default-lease-time 1209600;
  max-lease-time 31557600;
  # for each board, add the following configuration block.
  # It is best that you use different root FS directories
  # for each board.
  group {
    host scnhost01 {
      # MAC address
      hardware ethernet 00:d0:b7:85:f9:28;
      # The fixed address we will assign to the board
      fixed-address 150.158.231.20;
      # hm. not relevant here, is the kernel, which we load in FLASH
      filename "image";
      # our root FS that will be passed to the board
      option root-path "/home/mleeman/targets/target.scn.01";
    }
  }
}

   We now need to restart the dhcp server:
[mleeman@gemini mleeman]$ sudo /etc/init.d/dhcpd restart

   If you do not know the MAC address, and it is not indicated on the board in some way, just let the target boot (loaded with
   an NFS kernel of course) and watch the messages of the dhcp server, it will display the the MAC address (but will not pass a
   root FS).

[mleeman@gemini mleeman]$ sudo tail -f /var/log/messages

   and search for something like the following passing:
Apr  9 07:53:22 gemini dhcpd: BOOTREQUEST from 00:04:a5:00:05:19 via eth0
Apr  9 07:53:22 gemini dhcpd: No applicable record for BOOTP host 00:04:a5:00:05:19 via eth0

   More detailed information will be see in
sudo tail -f /var/log/syslog

Jul 13 15:57:08 gemini dhcpd: BOOTREQUEST from 00:04:a5:04:05:0c via eth0
Jul 13 15:57:08 gemini dhcpd: BOOTREPLY for 150.158.231.121 to hydra_stream_dmar (00:04:a5:04:05:0c) via eth0
Jul 13 15:57:13 gemini rpc.mountd: authenticated mount request from 150.158.231.121:800 for /home/dmartens/targets/target.01 (/home/d
martens/targets/target.01)

   In this case 00:04:a5:00:05:19 is our MAC address.

   More details about the kernel parameters are found in the attached file.

   -- MarcLeeman - 17 Jun 2004

   Attachment: Action: Size:        Date:           Who:                      Comment:
   nfsroot.txt action  8020  21 Jun 2004 - 10:00 MarcLeeman Kernel Documentation (2.6.7) about an nfsroot

   Topic NFSSystem . { Edit | Attach | Ref-By | Printable | Diffs | r1.9 | > | r1.8 | > | r1.7 | More }

   Revision r1.9 - 13 Jul 2004 - 14:00 GMT - MarcLeeman
   Parents: WebHome > FirmwareDocumentation Copyright © 1999-2003 by the contributing authors. All material on this
   collaboration platform is the property of the contributing authors.
   Ideas, requests, problems regarding TWiki? Send feedback.