All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Song Sam <samlinuxppc@yahoo.com.cn>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Linux 2.6.x on 8xx status
Date: Mon, 20 Sep 2004 09:02:13 +0300	[thread overview]
Message-ID: <414E7265.4090105@intracom.gr> (raw)
In-Reply-To: <20040918201154.53000.qmail@web15602.mail.cnb.yahoo.com>

Song Sam wrote:
> Pantelis Antoniou <panto@intracom.gr> wrote:
> 
>>>Well, as I have tested so far, 2.6.x can only work
>>>right on 8xx with RAMDISK root file system. As for
>>>NFS, still no luck.
>>
>>Well it could have fooled me since I have it running
>>right here...
>>
>>Don't use the old etherner driver.
> 
> 
> After following your instruction, I tested fec_8xx
> driver on RPXlite DW.
> Changes were made as follows:
> 1. Mask __fw_getenv and 'ethaddr' code in
> fec_8xx-netta.c to avoid compiling error 'undefined
> reference to __fw_getenv';
> 2. Replace NETTA as RPXLITE in ..fec_8xx/Makefile &&
> Kconfig;
> 
> Yeah, the result is so close to work right on RPXlite
> DW. So great, a lot improvement. But still a pity...
> 
> ---------------------------------------------------
> 
> U-Boot 1.1.2 (Aug 31 2004 - 09:47:03)
> 
> CPU:   PPC823EZTnnB2 at 48 MHz: 16 kB I-Cache 8 kB
> D-Cache
> Board: RPXlite_DW
> DRAM:  64 MB
> FLASH: 16 MB
> Hit any key to stop autoboot:  0
> u-boot>run net_nfs
> Using SCC ETHERNET device
> TFTP from server 172.16.115.6; our IP address is
> 172.16.115.7
> Filename 'uImage.rpx26nfs919'.
> Load address: 0x200000
> Loading:
> #################################################################
> done
> Bytes transferred = 726996 (b17d4 hex)
> ## Booting image at 00200000 ...
>    Image Name:   Linux-2.6.9-rc2
>    Image Type:   PowerPC Linux Kernel Image (gzip
> compressed)
>    Data Size:    726932 Bytes = 709.9 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Uncompressing Kernel Image ... OK
> Linux version 2.6.9-rc2 (root@shu.edu.net) (gcc
> version 3.2.2 20030217 (Yellow Dog Linux 3.0
> 3.2.2-2a_1)) #1 Sun Sep 19 02:33:02 CST 2004
> Built 1 zonelists
> Kernel command line: root=/dev/nfs rw
> nfsroot=172.16.115.6:/workspace/myfilesystem/target/
> ip=172.16.115.7:172.16.115.6:172.16.115.254:255.255.255.0::eth0:off
> panic=1
> PID hash table entries: 512 (order: 9, 8192 bytes)
> Decrementer Frequency = 180000000/60
> Dentry cache hash table entries: 16384 (order: 4,
> 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768
> bytes)
> Memory: 63104k available (1272k kernel code, 288k
> data, 72k init, 0k highmem)
> Mount-cache hash table entries: 512 (order: 0, 4096
> bytes)
> NET: Registered protocol family 16
> Serial: CPM driver $Revision: 0.01 $
> ttyCPM0 at MMIO 0xfa200a80 (irq = 20) is a CPM UART
> ttyCPM1 at MMIO 0xfa200a00 (irq = 46) is a CPM UART
> RAMDISK driver initialized: 16 RAM disks of 4096K size
> 1024 blocksize
> loop: loaded (max 8 devices)
> fec_8xx.c:v0.1 (May 6, 2004)
> FEC Reset timeout!
> fec_8xx: eth0 No PHY detected!
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 4096 bind
> 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> FEC Reset timeout!
> IP-Config: Complete:
>       device=eth0, addr=172.16.115.7,
> mask=255.255.255.0, gw=172.16.115.254,
>      host=172.16.115.7, domain=, nis-domain=(none),
>      bootserver=172.16.115.6, rootserver=172.16.115.6,
> rootpath=
> Looking up port of RPC 100003/2 on 172.16.115.6
> portmap: server 172.16.115.6 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server,
> using default
> Looking up port of RPC 100005/1 on 172.16.115.6
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> portmap: server 172.16.115.6 not responding, timed out
> Root-NFS: Unable to get mountd port number from
> server, using default
> NETDEV WATCHDOG: eth0: transmit timed out
> [snip]
> NETDEV WATCHDOG: eth0: transmit timed out
> mount: server 172.16.115.6 not responding, timed out
> Root-NFS: Server returned error -5 while mounting
> /workspace/myfilesystem/target/
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or
> unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(2,0)
>  <0>Rebooting in 1 seconds..<6>NETDEV WATCHDOG: eth0:
> transmit timed out
> -----------------------------------------------
> 
> Idea?
> 
> Best regards,
> 
> Sam

Ahem, the new ethernet driver is for the FEC not the SCC.

By the bootload messages RPXlite uses the SCC ethernet.

I'm afraid someone has to step up and fix the old ethernet
driver. I don't have any hardware that uses it.

Regards

Pantelis

  reply	other threads:[~2004-09-20  6:24 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040916201505.E723B2BDB2@ozlabs.org>
2004-09-17 10:06 ` Linux 2.6.x on 8xx status Song Sam
2004-09-17  9:55   ` Pantelis Antoniou
2004-09-18 20:11     ` Song Sam
2004-09-20  6:02       ` Pantelis Antoniou [this message]
2004-09-20 11:47         ` Song Sam
2004-09-20 17:49     ` Tom Rini
2004-09-20 18:02       ` Robert P. J. Day
2004-09-20 18:17         ` Tom Rini
2004-09-21  1:38       ` Song Sam
2004-09-21  6:12         ` Pantelis Antoniou
2004-09-21 10:35           ` Song Sam
2004-09-21 10:41             ` Pantelis Antoniou
2004-10-15 15:47               ` Marcelo Tosatti
2005-02-22 11:20 Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2004-10-25 15:00 Sam Song
2004-09-21 11:59 Smith, Craig
2004-09-21 11:53 ` Pantelis Antoniou
2004-09-21 16:54   ` Dan Malek
2004-09-21 17:03 ` Dan Malek
2004-09-22 11:09   ` Sam Song
2004-10-15 15:49   ` Marcelo Tosatti
2004-10-16  2:13     ` Marcelo Tosatti
2004-10-16  9:08       ` Sam Song
2004-10-18  5:59         ` Pantelis Antoniou
2004-10-18  6:22           ` Sam Song
2004-10-18  3:10     ` Dan Malek
2005-02-10 15:04   ` Marcelo Tosatti
2005-02-10 19:26     ` Dan Malek
2005-02-10 17:06       ` Marcelo Tosatti
2005-02-10 17:08         ` Marcelo Tosatti
2005-03-21 21:45           ` Guillaume Autran
2005-03-21 21:53             ` Robert P. J. Day
2005-03-22 13:04             ` Marcelo Tosatti
2005-03-22 20:57               ` Dan Malek
2005-03-22 17:58                 ` Marcelo Tosatti
2005-03-22 22:53                   ` Dan Malek
2005-03-23 10:25                     ` Marcelo Tosatti
2005-03-23 16:12                       ` Dan Malek
2005-03-23 16:05                         ` Marcelo Tosatti
2005-03-24 14:05                           ` Pantelis Antoniou
2005-03-23 14:06                   ` Guillaume Autran
2005-02-11  3:42         ` Dan Malek
2005-02-21 21:12       ` Armin Schindler
2005-02-21 23:45         ` Guillaume Autran
2004-09-17 13:57 Smith, Craig
2004-09-17 13:50 ` Pantelis Antoniou
2004-09-16 18:56 Smith, Craig
2004-09-16 20:07 ` Dan Malek
2004-09-17  5:43   ` Pantelis Antoniou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=414E7265.4090105@intracom.gr \
    --to=panto@intracom.gr \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.