From: Philipp <philipp@riseup.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Problems with igbe
Date: Sun, 25 Nov 2007 00:51:50 +0100 [thread overview]
Message-ID: <20071124235150.GB12094@localdomain> (raw)
In-Reply-To: <a9a2c5cdd51a6e4de496f3531b7b86f3@quanstro.net>
On 16:27 Sat 24 Nov , erik quanstrom wrote:
> the datasheet for this part says that the eeprom checksum
> for this part must be 0xbaba. its calculated at the end of
> /sys/src/9/pc/etherigbe.c:^/at93c46r.
>
> the reason for two bad checksum messages is likely that you
> have a two port card. both ports share the same eeprom.
> if this is true, you may need to change :1775 from
> if ((ctlr->id == i82546gb || ctlr->id == i82546eb) &&
> to
> if ((ctlr->id == i82546gb || ctlr->id == i82546eb || ctlr->id == i82547ei) &&
> (this isn't really the correct test, but i don't have the datasheet
> for the 82547 handy. close enough.)
>
> it is possible that the eeprom does have an invalid signature
> but will still work. you can attempt this by commenting out
> /sys/src/9/pc/etherigbe.c:1767.
>
> - erik
Hi!
Commenting out /sys/src/9/pc/etherigbe.c:1767 worked for me, at
least, for a while. It was kind of obvious, so maybe my mail was
kind of spam. But commenting it out is not all. #l is set up now,
but /net/ether0/addr gives me now sth. like ffffffff, so maybe
that's why i never get a connection to my dhcpd. I think that
has sth. to do with some function which sets up/reads the mac
address and isn't (correctly) implemented for my controller,
but I don't know much about nic drivers.
Best regards,
Philipp
next prev parent reply other threads:[~2007-11-24 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 16:25 Philipp
2007-11-24 21:27 ` erik quanstrom
[not found] ` <a9a2c5cdd51a6e4de496f3531b7b86f3@quanstro.net>
2007-11-24 23:51 ` Philipp [this message]
2007-11-25 12:25 ` erik quanstrom
2007-11-25 13:45 ` Philipp
2007-11-25 14:26 ` 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=20071124235150.GB12094@localdomain \
--to=philipp@riseup.net \
--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).