* Why eth0 does not work
@ 2000-07-12 10:21 Wentao Xu
2000-07-12 22:15 ` Frank Rowand
0 siblings, 1 reply; 6+ messages in thread
From: Wentao Xu @ 2000-07-12 10:21 UTC (permalink / raw)
To: linuxppc-embedded
Hi, everyone,
I am porting the linux code from mvista to IBM redwood
board. Now it seems like the eth0 is not registered
because the NFS uses loopback device. Who can give me
an idea? Thanks in advance.
the output is
-----------------------------------------------------
Linux version 2.3.39 (xwt@stb_dev) (gcc version 2.95.2
19991024 (release)) #393
Wed Jul 12 17:02:16 CST 2000
walnut_setup_arch()
---------- progress: 0x3eab arch: exit
On node 0 totalpages: 00001800
zone(0): 6144 pages.
zone(1): 0 pages.
zone(2): 0 pages.
ERROR: ppc4xx_pic_init() detected wrong PVR_VER
----- in walnut_calibrate_decr()
bip:
bi_s_version 1.3
bi_r_version 1.13
bi_memsize 0x1800000
bi_enetaddr 123456-7890ab
bi_pci_enetaddr 000002-f34f60
bi_procfreq 0x2f34f60
bi_plb_busfreq 0x4e800021
bi_pci_busfreq 0x0
Calibrating delay loop... 49.25 BogoMIPS
Memory: 22704k available (800k kernel code, 580k data,
48k init) [c0000000,c1800
000]
Buffer-cache hash table entries: 1024 (order: 0, 4096
bytes)
Page-cache hash table entries: 8192 (order: 3, 32768
bytes)
POSIX conformance testing by UNIFIX
---------- progress: 0xffff
Linux NET4.0 for Linux 2.3
Based upon Swansea University Computer Society
NET3.039
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind
4096)
Starting kswapd v1.6
tty_init() -- calling rs_init()
Serial driver version 4.91 (1999-11-17) with no serial
options enabled
ttyS00 at 0x0000 (irq = 20) is a 16550A
tty_init() -- returned from rs_init()
RAMDISK driver initialized: 16 RAM disks of 4096K size
1024 blocksize
eth0: National DP83902AV at 12:34:56:78:90:ab, found
at 0xf1400000, using IRQ 26
.
Looking up port of RPC 100003/2 on 7.1.1.21
Device lo is down.
Device lo is down.
Device lo is down.
Device lo is down.
portmap: server 7.1.1.21 not responding, timed out
Root-NFS: Unable to get nfsd port number from server,
using default
Looking up port of RPC 100005/1 on 7.1.1.21
Device lo is down.
Device lo is down.
Device lo is down.
Device lo is down.
portmap: server 7.1.1.21 not responding, timed out
Root-NFS: Unable to get mountd port number from
server, using default
Device lo is down.
Device lo is down.
Device lo is down.
Device lo is down.
mount: server 7.1.1.21 not responding, timed out
Root-NFS: Server returned error -5 while mounting
/opt/hardhat/devkit/ppc/8xx/ta
rget_ftest4
VFS: Unable to mount root fs via NFS, trying floppy.
request_module[block-major-2]: Root fs not mounted
VFS: Cannot open root device 02:00
Kernel panic: VFS: Unable to mount root fs on 02:00
Rebooting in 180 seconds..
-------------------------------------------------------
Wentao
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why eth0 does not work
2000-07-12 10:21 Wentao Xu
@ 2000-07-12 22:15 ` Frank Rowand
0 siblings, 0 replies; 6+ messages in thread
From: Frank Rowand @ 2000-07-12 22:15 UTC (permalink / raw)
To: Wentao Xu; +Cc: linuxppc-embedded
Wentao Xu wrote:
>
> Hi, everyone,
> I am porting the linux code from mvista to IBM redwood
> board. Now it seems like the eth0 is not registered
> because the NFS uses loopback device. Who can give me
> an idea? Thanks in advance.
>
> the output is
> -----------------------------------------------------
> Linux version 2.3.39 (xwt@stb_dev) (gcc version 2.95.2
> 19991024 (release)) #393
> Wed Jul 12 17:02:16 CST 2000
> walnut_setup_arch()
> ---------- progress: 0x3eab arch: exit
> On node 0 totalpages: 00001800
> zone(0): 6144 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> ERROR: ppc4xx_pic_init() detected wrong PVR_VER
I don't know what changes you have made to ppc4xx_pic_init(), make sure you have
initialized the pic correctly.
>
> ----- in walnut_calibrate_decr()
>
> bip:
>
> bi_s_version 1.3
> bi_r_version 1.13
> bi_memsize 0x1800000
> bi_enetaddr 123456-7890ab
> bi_pci_enetaddr 000002-f34f60
> bi_procfreq 0x2f34f60
> bi_plb_busfreq 0x4e800021
> bi_pci_busfreq 0x0
>
> Calibrating delay loop... 49.25 BogoMIPS
> Memory: 22704k available (800k kernel code, 580k data,
> 48k init) [c0000000,c1800
> 000]
> Buffer-cache hash table entries: 1024 (order: 0, 4096
> bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768
> bytes)
> POSIX conformance testing by UNIFIX
> ---------- progress: 0xffff
> Linux NET4.0 for Linux 2.3
> Based upon Swansea University Computer Society
> NET3.039
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind
> 4096)
> Starting kswapd v1.6
> tty_init() -- calling rs_init()
> Serial driver version 4.91 (1999-11-17) with no serial
> options enabled
> ttyS00 at 0x0000 (irq = 20) is a 16550A
> tty_init() -- returned from rs_init()
> RAMDISK driver initialized: 16 RAM disks of 4096K size
> 1024 blocksize
> eth0: National DP83902AV at 12:34:56:78:90:ab, found
> at 0xf1400000, using IRQ 26
> .
> Looking up port of RPC 100003/2 on 7.1.1.21
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
I have seen similar messages when the driver for eth0 was not registered or
not working properly.
> portmap: server 7.1.1.21 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server,
> using default
> Looking up port of RPC 100005/1 on 7.1.1.21
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
> portmap: server 7.1.1.21 not responding, timed out
> Root-NFS: Unable to get mountd port number from
> server, using default
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
> mount: server 7.1.1.21 not responding, timed out
> Root-NFS: Server returned error -5 while mounting
> /opt/hardhat/devkit/ppc/8xx/ta
But this may indicate that you actually were communicating with the server
over ethernet??? I haven't looked up NFS error -5. What does it mean?
Is it something as simple as needing to export your root files system
("/opt/hardhat/devkit/ppc/8xx/ta") on your host system? Did you mis-type
the path of the root file system in the command line passed to the linux
kernel or is the path just truncated in the error message?
> rget_ftest4
> VFS: Unable to mount root fs via NFS, trying floppy.
> request_module[block-major-2]: Root fs not mounted
> VFS: Cannot open root device 02:00
> Kernel panic: VFS: Unable to mount root fs on 02:00
> Rebooting in 180 seconds..
> -------------------------------------------------------
>
> Wentao
>
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why eth0 does not work
@ 2000-07-13 1:50 xuwentao
2000-07-13 4:12 ` ben bodley
0 siblings, 1 reply; 6+ messages in thread
From: xuwentao @ 2000-07-13 1:50 UTC (permalink / raw)
To: frowand, benb; +Cc: linuxppc-embedded
Currently I only modify ppc4xx_pic_init() to init IRQ 20 and 26, which is
used by
ttys00 and eth0. That error occurs because my CPU is a ppc401 not a 405gp.
I have exported /opt/hardhat/devkit/ppc/8xx/target_ftest4 according
instructions from
mvista. The output is broken into 2 lines.
BTW, I disabled the loopback in the config file, and the msg "lo is down'
still
appears.
I start the tcpdump at the server, I found that the server recieved many
ARP packets
issued from the linux box(7.1.1.5) looking for the server(7.1.1.21). It
seems that
the box can not resolve 7.1.1.21 (can not read MAC addr, as Ben said).
Xu Wentao
IBM China Research Lab
Tel: (86-10) 62986677-216
Internet: xuwentao@cn.ibm.com
Frank Rowand <frank_rowand@mvista.com> on 2000-07-13 06:15:13 AM
Please respond to frowand@mvista.com
To: Wentao Xu <xuwentao@yahoo.com>
cc: linuxppc-embedded@lists.linuxppc.org (bcc: Wen Tao Xu/China/IBM)
Subject: Re: Why eth0 does not work
Wentao Xu wrote:
>
> Hi, everyone,
> I am porting the linux code from mvista to IBM redwood
> board. Now it seems like the eth0 is not registered
> because the NFS uses loopback device. Who can give me
> an idea? Thanks in advance.
>
> the output is
> -----------------------------------------------------
> Linux version 2.3.39 (xwt@stb_dev) (gcc version 2.95.2
> 19991024 (release)) #393
> Wed Jul 12 17:02:16 CST 2000
> walnut_setup_arch()
> ---------- progress: 0x3eab arch: exit
> On node 0 totalpages: 00001800
> zone(0): 6144 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> ERROR: ppc4xx_pic_init() detected wrong PVR_VER
I don't know what changes you have made to ppc4xx_pic_init(), make sure you
have
initialized the pic correctly.
>
> ----- in walnut_calibrate_decr()
>
> bip:
>
> bi_s_version 1.3
> bi_r_version 1.13
> bi_memsize 0x1800000
> bi_enetaddr 123456-7890ab
> bi_pci_enetaddr 000002-f34f60
> bi_procfreq 0x2f34f60
> bi_plb_busfreq 0x4e800021
> bi_pci_busfreq 0x0
>
> Calibrating delay loop... 49.25 BogoMIPS
> Memory: 22704k available (800k kernel code, 580k data,
> 48k init) [c0000000,c1800
> 000]
> Buffer-cache hash table entries: 1024 (order: 0, 4096
> bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768
> bytes)
> POSIX conformance testing by UNIFIX
> ---------- progress: 0xffff
> Linux NET4.0 for Linux 2.3
> Based upon Swansea University Computer Society
> NET3.039
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind
> 4096)
> Starting kswapd v1.6
> tty_init() -- calling rs_init()
> Serial driver version 4.91 (1999-11-17) with no serial
> options enabled
> ttyS00 at 0x0000 (irq = 20) is a 16550A
> tty_init() -- returned from rs_init()
> RAMDISK driver initialized: 16 RAM disks of 4096K size
> 1024 blocksize
> eth0: National DP83902AV at 12:34:56:78:90:ab, found
> at 0xf1400000, using IRQ 26
> .
> Looking up port of RPC 100003/2 on 7.1.1.21
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
I have seen similar messages when the driver for eth0 was not registered or
not working properly.
> portmap: server 7.1.1.21 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server,
> using default
> Looking up port of RPC 100005/1 on 7.1.1.21
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
> portmap: server 7.1.1.21 not responding, timed out
> Root-NFS: Unable to get mountd port number from
> server, using default
> Device lo is down.
> Device lo is down.
> Device lo is down.
> Device lo is down.
> mount: server 7.1.1.21 not responding, timed out
> Root-NFS: Server returned error -5 while mounting
> /opt/hardhat/devkit/ppc/8xx/ta
But this may indicate that you actually were communicating with the server
over ethernet??? I haven't looked up NFS error -5. What does it mean?
Is it something as simple as needing to export your root files system
("/opt/hardhat/devkit/ppc/8xx/ta") on your host system? Did you mis-type
the path of the root file system in the command line passed to the linux
kernel or is the path just truncated in the error message?
> rget_ftest4
> VFS: Unable to mount root fs via NFS, trying floppy.
> request_module[block-major-2]: Root fs not mounted
> VFS: Cannot open root device 02:00
> Kernel panic: VFS: Unable to mount root fs on 02:00
> Rebooting in 180 seconds..
> -------------------------------------------------------
>
> Wentao
>
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why eth0 does not work
2000-07-13 1:50 Why eth0 does not work xuwentao
@ 2000-07-13 4:12 ` ben bodley
0 siblings, 0 replies; 6+ messages in thread
From: ben bodley @ 2000-07-13 4:12 UTC (permalink / raw)
To: xuwentao; +Cc: mailing list
xuwentao@cn.ibm.com wrote:
> Currently I only modify ppc4xx_pic_init() to init IRQ 20 and 26, which is
> used by
> ttys00 and eth0. That error occurs because my CPU is a ppc401 not a 405gp.
>
> I have exported /opt/hardhat/devkit/ppc/8xx/target_ftest4 according
> instructions from
> mvista. The output is broken into 2 lines.
>
> BTW, I disabled the loopback in the config file, and the msg "lo is down'
> still
> appears.
>
> I start the tcpdump at the server, I found that the server recieved many
> ARP packets
> issued from the linux box(7.1.1.5) looking for the server(7.1.1.21). It
> seems that
> the box can not resolve 7.1.1.21 (can not read MAC addr, as Ben said).
>
> Xu Wentao
> IBM China Research Lab
> Tel: (86-10) 62986677-216
> Internet: xuwentao@cn.ibm.com
if you could send the tcpdump output that would help.. dont worry about the
'device lo is down' message, it wont effect any of your ethernet work.. i
think you will need to modify the board info struct, and get the proper mac
address from it.. maybe what is happening is you are configuring linux to use
a mac address different than the actual hardware setting??
also, have you set the io pins correctly?? the stb chip needs a lot of gpio
setting up to work properly.. you also need to configure the xilinx fpga's to
select input from the ethernet mac, etc..
cheers,
ben
--
/\\------------------------------------------------------------------
:::::::::::..ben.b..m2technologyltd.nz..64.9.4448307.130..:::::::::::
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why eth0 does not work
@ 2000-07-17 6:21 xuwentao
2000-07-17 23:06 ` ben bodley
0 siblings, 1 reply; 6+ messages in thread
From: xuwentao @ 2000-07-17 6:21 UTC (permalink / raw)
To: ben bodley; +Cc: linuxppc-embedded
I found that the client can not receive packet correctly. I put some
printk()
in fucntion ei_receive() in file driver/net/8390.c as the following:
if (rx_frame.next != next_frame
&& rx_frame.next != next_frame + 1
&& rx_frame.next != next_frame - num_rx_pages
&& rx_frame.next != next_frame + 1 - num_rx_pages)
{()
/* the following lines are added by Wentao */
printk("----------rx
error---------------------\n");
printk("rx_frame.next =
%d,next_frame=%d\n",rx_frame.nex
t,next_frame); /* Wentao adds */
printk("num_rx_pages=%d,ei_local->current_page=%d\n\n",n
um_rx_pages, ei_local->current_page);
/* end of addtion by Wentao */
.....
BTW, the related receive buffer registers are initialized with value(my
board has
a 32k sram for packet buffer);
page start reg: 44
current page reg: 44
page stop reg: 64
boundary poiter: 63
The output in the client is :
.......
eth0: National DP83902AV at 12:34:56:78:90:ab, found at 0xf1400000, using
IRQ 26.
Looking up port of RPC 100003/2 on 7.1.1.21
----------rx error---------------------
rx_frame.next = 45,next_frame=109
num_rx_pages=20,ei_local->current_page=44
----------rx error---------------------
rx_frame.next = 46,next_frame=110
num_rx_pages=20,ei_local->current_page=45
----------rx error---------------------
rx_frame.next = 47,next_frame=111
num_rx_pages=20,ei_local->current_page=46
Device lo is down.
----------rx error---------------------
rx_frame.next = 48,next_frame=112
num_rx_pages=20,ei_local->current_page=47
----------rx error---------------------
rx_frame.next = 49,next_frame=113
num_rx_pages=20,ei_local->current_page=48
----------rx error---------------------
rx_frame.next = 50,next_frame=114
num_rx_pages=20,ei_local->current_page=49
Device lo is down.
----------rx error---------------------
rx_frame.next = 51,next_frame=115
num_rx_pages=20,ei_local->current_page=50
----------rx error---------------------
rx_frame.next = 52,next_frame=116
num_rx_pages=20,ei_local->current_page=51
----------rx error---------------------
rx_frame.next = 53,next_frame=117
num_rx_pages=20,ei_local->current_page=52
Device lo is down.
----------rx error---------------------
rx_frame.next = 54,next_frame=172
num_rx_pages=20,ei_local->current_page=53
----------rx error---------------------
rx_frame.next = 55,next_frame=119
num_rx_pages=20,ei_local->current_page=54
----------rx error---------------------
rx_frame.next = 56,next_frame=120
num_rx_pages=20,ei_local->current_page=55
----------rx error---------------------
rx_frame.next = 57,next_frame=121
num_rx_pages=20,ei_local->current_page=56
Device lo is down.
portmap: server 7.1.1.21 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 7.1.1.21
----------rx error---------------------
rx_frame.next = 58,next_frame=122
num_rx_pages=20,ei_local->current_page=57
........
the output of the tcpdump -i eth0 host 7.1.1.5 in the NFS server is:
13:47:08.224173 B arp who-has 7.1.1.21 tell 7.1.1.5
13:47:08.224207 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
0:20:35:b1:fc:d8 (
12:34:56:78:90:ab)
13:47:09.335805 B arp who-has 7.1.1.21 tell 7.1.1.5
13:47:09.335826 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
0:20:35:b1:fc:d8 (
12:34:56:78:90:ab)
13:47:10.447399 B arp who-has 7.1.1.21 tell 7.1.1.5
13:47:10.447413 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
0:20:35:b1:fc:d8 (
12:34:56:78:90:ab)
13:47:13.604779 B arp who-has 7.1.1.21 tell 7.1.1.5
13:47:13.604794 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
0:20:35:b1:fc:d8 (
12:34:56:78:90:ab)
.......
I also tried other vlaues for the buffer registers such as
page start reg: 0
current page reg: 1
page stop reg: 32
boundary poiter: 0
and also got rx errors. I dont know what to do next.
Wentao
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why eth0 does not work
2000-07-17 6:21 xuwentao
@ 2000-07-17 23:06 ` ben bodley
0 siblings, 0 replies; 6+ messages in thread
From: ben bodley @ 2000-07-17 23:06 UTC (permalink / raw)
To: xuwentao; +Cc: mailing list
xuwentao@cn.ibm.com wrote:
>
> the output of the tcpdump -i eth0 host 7.1.1.5 in the NFS server is:
> 13:47:08.224173 B arp who-has 7.1.1.21 tell 7.1.1.5
> 13:47:08.224207 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
> 0:20:35:b1:fc:d8 (
> 12:34:56:78:90:ab)
> 13:47:09.335805 B arp who-has 7.1.1.21 tell 7.1.1.5
> 13:47:09.335826 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
> 0:20:35:b1:fc:d8 (
> 12:34:56:78:90:ab)
> 13:47:10.447399 B arp who-has 7.1.1.21 tell 7.1.1.5
> 13:47:10.447413 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
> 0:20:35:b1:fc:d8 (
> 12:34:56:78:90:ab)
> 13:47:13.604779 B arp who-has 7.1.1.21 tell 7.1.1.5
> 13:47:13.604794 > arp reply 7.1.1.21 (0:20:35:b1:fc:d8) is-at
> 0:20:35:b1:fc:d8 (
> 12:34:56:78:90:ab)
> .......
> I also tried other vlaues for the buffer registers such as
> page start reg: 0
> current page reg: 1
> page stop reg: 32
> boundary poiter: 0
> and also got rx errors. I dont know what to do next.
>
> Wentao
>
okay... well i'm not sure what patches you are using, but as i recall
montavista did not use grant's latest kernel patch with a very major (but very
small :) ethernet fix..
in the drivers/net/oaknet.c file please check the function
oaknet_get_8390_hdr().. at the end of this function make sure you have the
following code segment (the byte swap is the changed line):
---------------
else
ei_isb(E8390_BASE + E8390_DATA, hdr,
sizeof(struct e8390_pkt_hdr));
/* byte swap the packet byte count */
hdr->count = le16_to_cpu(hdr->count);
ei_obp(ENISR_RDC, base + EN0_ISR); /* ACK Remote DMA interrupt */
ei_status.dmaing &= ~0x01;
return;
----------------
let me know if this helps..
cheers,
ben
--
/\\------------------------------------------------------------------
:::::::::::..ben.b..m2technologyltd.nz..64.9.4448307.130..:::::::::::
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2000-07-17 23:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-07-13 1:50 Why eth0 does not work xuwentao
2000-07-13 4:12 ` ben bodley
-- strict thread matches above, loose matches on Subject: below --
2000-07-17 6:21 xuwentao
2000-07-17 23:06 ` ben bodley
2000-07-12 10:21 Wentao Xu
2000-07-12 22:15 ` Frank Rowand
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).