From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 25 Nov 2007 14:45:52 +0100 From: Philipp To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Problems with igbe Message-ID: <20071125134552.GA9215@localdomain> References: <20071124235150.GB12094@localdomain> <493db713aadea2bcac0f0a9885f14f32@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <493db713aadea2bcac0f0a9885f14f32@quanstro.net> User-Agent: Mutt/1.5.13 (2006-08-11) Topicbox-Message-UUID: 0b021e80-ead3-11e9-9d60-3106f5b1d025 On 07:25 Sun 25 Nov , erik quanstrom wrote: > > 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 > > okay, the reason the eeprom checksum is wrong is that the data > coming from your card. this is where the station address aka mac is stored. > and other important defaults. so either we're doing it wrong or it really is corrupt. > > the first option is more attactive. in at93c46r() there's a switch statement > on what type of ctlr you have. try adding your controller type after > case i82546eb: > perhaps igbe is using the wrong method. > > - erik Hi! Yeah, exactly, that's it. And because igbe used the default case here (btw. we had a discussion in irc about default cases at the beginning of the switch statement) the some EEPROM stuff failed (there's also no bad EEPROM checksum message anymore), resulting in a invalid mac address. Thanks for this great remote diagnostics and keeping patient with me. Best regards, Philipp