Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: "Ruslan V.Pisarev" <jerry@izmiran.rssi.ru>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: dbau1200 ethernet driver?
Date: Fri, 06 May 2005 08:46:40 -0700	[thread overview]
Message-ID: <1115394400.5785.3.camel@localhost.localdomain> (raw)
In-Reply-To: <261758805.20050506155322@izmiran.rssi.ru>

On Fri, 2005-05-06 at 15:53 +0300, Ruslan V.Pisarev wrote:
>   Hi!
> 
>  I compiled last 2.6 kernel (2-3 weeks ago from cvs@linux-mips) and
> trying to start it on DBAu1200 development board. First problem I
> discovered with "nfsroot" configuration - is that kernel cannot find
> network interface at boot-time.
>  There is a smc91c111 network chip on board, so my question is - what
> driver is suitable with him?

The smc91x.c driver. However, I don't remember if that driver was
tested.  The board was tested with a different smc driver which I
couldn't push in the tree because it was old and would conflict with the
smc91x.c.

>  Is it "MIPS AU1000 Ethernet support"
> which fails to compile with "error: `NUM_ETH_INTERFACES' undeclared"
> (and it must be?) or something different? It seems that I have enabled
> all other options for ethernet functionality.

Well, that's a different driver.



Pete

> 
> 
> the part of boot log is:
> 
> loop: loaded (max 8 devices)
> nbd: registered device at major 43
> NET: Registered protocol family 2
> IP: routing cache hash table of 2048 buckets, 16Kbytes
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: No network devices available.
> Looking up port of RPC 100003/2 on 192.168.0.30
> RPC: sendmsg returned error 128
> portmap: RPC call returned error 128
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on 192.168.0.30
> RPC: sendmsg returned error 128
> portmap: RPC call returned error 128
> Root-NFS: Unable to get mountd port number from server, using default
> RPC: sendmsg returned error 128
> mount: RPC call returned error 128
> 
> 
>    ()_()
> --( °,° )---[21398845]-[jerry¤wicomtechnologies.com]-
>   (") (")                 -<The Bat! 3.0.1.33>- -<06/05/2005 15:35>-
> 
> 

  parent reply	other threads:[~2005-05-06 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 12:53 dbau1200 ethernet driver? Ruslan V.Pisarev
2005-05-06 13:32 ` sjhill
2005-05-06 14:12   ` Re[2]: " Ruslan V.Pisarev
2005-05-06 16:17     ` Pete Popov
2005-05-06 15:46 ` Pete Popov [this message]
2005-05-06 16:19   ` Ruslan V.Pisarev
2005-05-07 13:08   ` Bogdan Vacaliuc
2005-05-07 13:08     ` Bogdan Vacaliuc

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=1115394400.5785.3.camel@localhost.localdomain \
    --to=ppopov@embeddedalley.com \
    --cc=jerry@izmiran.rssi.ru \
    --cc=linux-mips@linux-mips.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox