From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Wed, 16 Nov 2005 18:53:18 +0100 Subject: [U-Boot-Users] Network problem in u-boot. In-Reply-To: <518B77BB6246D54D9E88FC49AFB0389D2F1C48@seskoptronicmsx.optronic.local> References: <518B77BB6246D54D9E88FC49AFB0389D2F1C48@seskoptronicmsx.optronic.local> Message-ID: <200511161853.19164.sr@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Andre, On Wednesday 16 November 2005 14:09, Andr? Berggren wrote: > I made some more tests and found that the old 405enet driver wont halt > forever like the old 440 and the latest 4xx driver does. The old 405enet > only outputs "ENET Speed is 100 Mbps - FULL duplex connection" sleeps for a > while and then resumes the transfer. > > Observe that the problem only occurs when another computer send packets to > u-boot or broadcasting on the network. If non of this occurs the transfer > is always successful. OK. > I enabled debug and got following output: > > => run setup > miiphy_register: non unique device name 'ppc_4xx_eth0' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is a problem recently added to the 4xx ethernet driver. I haven't found the time to fix it yet. > ENET Speed is 100 Mbps - FULL duplex connection > BOOTP broadcast 1 > DHCPHandler: got packet: (src=67, dst=68, len=300) state: 3 > Filtering pkt = 0 > DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 3 > DHCP: state=SELECTING bp_file: "/tftpboot/kernel.img" > TRANSITIONING TO REQUESTING STATE > Bootfile: /tftpboot/kernel.img > DhcpSendRequestPkt: Sending DHCPREQUEST > Transmitting DHCPREQUEST packet: len = 343 > DHCPHandler: got packet: (src=67, dst=68, len=300) state: 4 > Filtering pkt = 0 > DHCPHandler: got DHCP packet: (src=67, dst=68, len=300) state: 4 > DHCP State: REQUESTING > Bootfile: /tftpboot/kernel.img > DHCP client bound to address 172.18.22.66 > TFTP from server 172.18.22.110; our IP address is 172.18.22.66 > Filename '/tftpboot/kernel.img'. > Load address: 0x200000 > Loading: ################################################################# > ################################################################# > ################################################################# > ################################################################# > ##########################################T miiphy_register: non > unique device name 'ppc_4xx_eth0' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ See above. I assume, that you don't have CONFIG_NET_MULTI enabled right now. Correct? As a simple workaround for this problem, please enable CONFIG_NET_MULTI in your config file. And please let me know, if this helped. Best regards, Stefan