9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Thu,  3 Jan 2008 00:24:17 +0100	[thread overview]
Message-ID: <16ff6b980801021524u605fb109p7f1561198e86b78e@mail.gmail.com> (raw)
In-Reply-To: <16ff6b980801021520j2ee809cue0f567fbc3b8e7c4@mail.gmail.com>

ah nevermind the first question, now I indeed see the "net" line with 1049...

On Jan 3, 2008 12:20 AM, Mathieu Lonjaret <lejatorn@gmail.com> wrote:
>  Hmm, sorry for being such a noob in decoding those logs, but where do
> you see whether or not I have 1047?
> Anyway, it's not even my main issue since I can't boot on any other
> kernel than the one which is already installed.
> So even if adding the 1047 to the driver is the solution to the
> network part, I won't even be able to try it...
>
>
> On Jan 3, 2008 12:07 AM, Fazlul Shahriar <fshahriar@gmail.com> wrote:
> > > Right, you have this:
> > >
> > >         1049  82566MM Gigabit Network Connection
> > >
> > > And it's clearly covered in the driver. Hmm.
> > >
> > > what do you get when you cat /dev/drivers
> >
> > Ok, I meant lejatorn's pci output didn't have 1047 either. Maybe I wasn't clear.
> >
> > Anyway, here is /dev/drivers:
> >
> >         #/ root
> >         #c cons
> >         #P arch
> >         #$ pnp
> >         #e env
> >         #| pipe
> >         #p proc
> >         #M mnt
> >         #s srv
> >         #d dup
> >         #r rtc
> >         #D ssl
> >         #a tls
> >         #¤ cap
> >         #K kprof
> >         #k devfs
> >         #l ether
> >         #I ip
> >         #i draw
> >         #m mouse
> >         #v vga
> >         #κ kbmap
> >         #S sd
> >         #f floppy
> >         #L lpt
> >         #A audio
> >         #Y cardbus
> >         #y i82365
> >         #t uart
> >         #U usb
> >
>
>
>
>
> --
> GPG key on subkeys.pgp.net:
>
> KeyID:   | Fingerprint:
> 683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3
>



-- 
GPG key on subkeys.pgp.net:

KeyID:   | Fingerprint:
683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3

  reply	other threads:[~2008-01-02 23:24 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
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 [this message]
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=16ff6b980801021524u605fb109p7f1561198e86b78e@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).