9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bela Valek <bvalek2@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] unrecognized ethernet card
Date: Wed, 24 Feb 2010 21:52:49 +0100	[thread overview]
Message-ID: <4ecada1e1002241252u29851b26j6942a7b08b92efb8@mail.gmail.com> (raw)

Hi Everybody,

I installed Plan 9 on a new computer (Erik's 9atoms.iso), it doesnt
recognize the ethernet device (there is no /net/ether0). I wonder if
something can be done. If changing configuration doesnt help, I hope
its similar enough to an already supported device, so a few changes
here and there can make it work.

By the way, I was also wondering, when will Erik's SATA support arrive
in the main distribution?

Anyway, here are the details of the unrecognized device, from Linux:

- lshw says:
     *-bridge
          description: Ethernet interface
          product: MCP61 Ethernet
          vendor: nVidia Corporation
          physical id: 7
          bus info: pci@0000:00:07.0
          logical name: eth0
          version: a2
          serial: 00:1d:92:0b:b5:23
          size: 100000000
          capacity: 100000000
          width: 32 bits
          clock: 66MHz
          capabilities: bridge pm msi ht bus_master cap_list ethernet
physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
          configuration: autonegotiation=on broadcast=yes
driver=forcedeth driverversion=0.64 duplex=full latency=0 link=yes
maxlatency=20 mingnt=1 multicast=yes port=MII speed=100MB/s
          resources: irq:27 memory:dfff9000-dfff9fff ioport:e480(size=8)

- lspci says:
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
	Subsystem: Micro-Star International Co., Ltd. Device 7309
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (250ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 27
	Region 0: Memory at dfff9000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at e480 [size=8]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
	Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable+
		Address: 00000000fee0100c  Data: 4181
		Masking: 000000fe  Pending: 00000000
	Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
	Kernel driver in use: forcedeth
	Kernel modules: forcedeth

Greetings: Béla



             reply	other threads:[~2010-02-24 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 20:52 Bela Valek [this message]
2010-02-24 21:11 ` erik quanstrom

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=4ecada1e1002241252u29851b26j6942a7b08b92efb8@mail.gmail.com \
    --to=bvalek2@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).