From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] intel ethernet
Date: Wed, 2 Jan 2008 12:00:48 +0100 [thread overview]
Message-ID: <16ff6b980801020300p15a307e6t14d2f341bfcc6411@mail.gmail.com> (raw)
In-Reply-To: <13426df10801012133i597908ecqe1ca2d4a5bc045c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Ah thx.
Here is the output attached then.
Mathieu.
On Jan 2, 2008 6:33 AM, ron minnich <rminnich@gmail.com> wrote:
> please send the output of the pci command. It could be something as
> simple as a devid change, which intel loves to do all the time.
> ron
>
--
GPG key on subkeys.pgp.net:
KeyID: | Fingerprint:
683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3
[-- Attachment #2: pci_out.txt --]
[-- Type: text/plain, Size: 1497 bytes --]
0.0.0: brg 06.00.00 8086/2a00 0
0.2.0: vid 03.00.00 8086/2a02 10 0:f8100004 1048576 1:00000000 16 2:e000000c 268435456 3:00000000 16 4:00001801 16
0.2.1: vid 03.80.00 8086/2a03 0 0:f8200004 1048576 1:00000000 16
0.25.0: net 02.00.00 8086/1049 11 0:fe000000 131072 1:fe025000 4096 2:00001841 32
0.26.0: usb 0c.03.00 8086/2834 11 4:00001861 32
0.26.1: usb 0c.03.00 8086/2835 11 4:00001881 32
0.26.7: usb 0c.03.20 8086/283a 11 0:fe226400 1024
0.27.0: --- 04.03.00 8086/284b 11 0:fe020004 16384 1:00000000 16
0.28.0: brg 06.04.00 8086/283f 11
0.28.1: brg 06.04.00 8086/2841 11
0.28.2: brg 06.04.00 8086/2843 11
0.28.3: brg 06.04.00 8086/2845 11
0.28.4: brg 06.04.00 8086/2847 11
0.29.0: usb 0c.03.00 8086/2830 10 4:000018a1 32
0.29.1: usb 0c.03.00 8086/2831 11 4:000018c1 32
0.29.2: usb 0c.03.00 8086/2832 11 4:000018e1 32
0.29.7: usb 0c.03.20 8086/2836 11 0:fe226800 1024
0.30.0: brg 06.04.01 8086/2448 255
0.31.0: brg 06.01.00 8086/2811 0
0.31.2: disk 01.01.80 8086/2828 255 0:00000001 16 1:00000001 16 2:00000001 16 3:00000001 16 4:00001c31 16 5:00001c21 16
0.31.3: smb 0c.05.00 8086/283e 11 0:fe226c00 256 4:00001c41 32
21.0.0: brg 06.07.00 1180/0476 10
21.0.1: --- 0c.00.10 1180/0832 11 0:f8301000 2048
21.0.2: --- 08.05.00 1180/0822 11 0:f8301800 256
21.0.3: --- 08.80.00 1180/0843 11 0:f8301c00 256
21.0.4: --- 08.80.00 1180/0592 11 0:f8302000 256
21.0.5: --- 08.80.00 1180/0852 11 0:f8302400 256
3.0.0: net 02.80.00 8086/4227 11 0:df3ff000 4096
next prev parent reply other threads:[~2008-01-02 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 15:36 lejatorn
2008-01-02 5:33 ` ron minnich
2008-01-02 11:00 ` Mathieu Lonjaret [this message]
2008-01-02 13:45 ` erik quanstrom
2008-01-02 19:07 ` lejatorn
2008-01-02 23:33 ` erik quanstrom
2008-01-02 22:23 ` Fazlul Shahriar
2008-01-02 22:34 ` ron minnich
2008-01-02 23:07 ` Fazlul Shahriar
2008-01-02 23:20 ` Mathieu Lonjaret
2008-01-02 23:24 ` Mathieu Lonjaret
2008-01-02 23:22 ` erik quanstrom
2008-01-02 23:27 ` erik quanstrom
2008-01-02 13:38 erik quanstrom
2008-01-02 13:47 ` lejatorn
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=16ff6b980801020300p15a307e6t14d2f341bfcc6411@mail.gmail.com \
--to=lejatorn@gmail.com \
--cc=9fans@cse.psu.edu \
/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).