public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Ryan C. Bonham" <Ryan@srfarms.com>
Cc: "Linux Kernel List (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: Tyan Tomcat i815T(S2080) LAN problems
Date: Mon, 31 Dec 2001 11:18:53 -0700	[thread overview]
Message-ID: <3C30AC0D.9010700@candelatech.com> (raw)
In-Reply-To: <19AB8F9FA07FB0409732402B4817D75A1251C7@FILESERVER.SRF.srfarms.com>



Ryan C. Bonham wrote:

> Hi,
> 
> Well my first problem, once I got my brain working, was to realize that eth1 was DOA.. so as soon as I get a replacement board, I will try again.. Using the e100 driver, how did you force setting the MAC address?? 
> 
> Ryan


Make sure you enable the second port in the BIOS, btw.

I forget the exact syntax (I do it in c++ code, not with ifconfig or ip), but
both ifconfig and ip programs can set the mac address.  Try
/sbin/ip link help

That should point you in the right direction...  Note that MAC == Hardware-Address

Ben


> 
> 
>>-----Original Message-----
>>From: Ben Greear [mailto:greearb@candelatech.com]
>>Sent: Sunday, December 30, 2001 10:31 PM
>>To: Ryan C. Bonham
>>Cc: Linux Kernel List (E-mail)
>>Subject: Re: Tyan Tomcat i815T(S2080) LAN problems
>>
>>
>>I sort of got it working by using the e100 driver from Intel, and then
>>forcefully setting the MAC address to something other than 0xFF...FF
>>
>>Neither Becker, I, nor someone at Intel could figure out why
>>the MAC (EEPROM) was all FFs.  The best guess was that the BIOS
>>was screwed up somehow (that's what the Intel guy said...)
>>
>>I'd be interested if you get it working...I have two of these marginal
>>boards gathering dust!!
>>
>>Ben
>>
>>Ryan C. Bonham wrote:
>>
>>
>>>Hi,
>>>
>>>I installed kernel 2.4.17 and this problem still exists. I 
>>>
>>have attached the important stuff from demesg and from eepro100-diag. 
>>
>>>
>>>>Has anyone gotten the Dual built-in LAN cards to work on the 
>>>>Tyan S2080 Motherboard?  I am running a Redhat kernel 
>>>>2.4.9-13.. I haven't tried the latest kernel yet.. I saw some 
>>>>talk about this board in the archives but I found no 
>>>>solutions. It says it has a Intel 82559 LAN controller and a 
>>>>ICH2 LAN Controller. I am only seeing one NIC when I boot up. 
>>>>And dmesg is showing
>>>>eth0: Invalid EEPROM checksum 0xFF00, check setting before 
>>>>activating this device!
>>>>
>>>>
>>>>
>>>Thanks,
>>>
>>>
>>>eepro100.c:v1.09j-t 9/29/99 Donald Becker 
>>>
>>http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>>
>>>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey 
>>>
>>V. Savochkin <saw@saw.sw.com.sg> and others
>>
>>>PCI: Found IRQ 11 for device 01:08.0
>>>eth0: Invalid EEPROM checksum 0xff00, check settings before 
>>>
>>activating this device!
>>
>>>eth0: OEM i82557/i82558 10/100 Ethernet, FF:FF:FF:FF:FF:FF, IRQ 11.
>>>  Board assembly ffffff-255, Physical connectors present: 
>>>
>>RJ45 BNC AUI MII
>>
>>>  Primary interface chip unknown-15 PHY #31.
>>>    Secondary interface chip i82555.
>>>  General self-test: passed.
>>>  Serial sub-system self-test: passed.
>>>  Internal registers self-test: passed.
>>>  ROM checksum self-test: passed (0x04f4518b).
>>>
>>>----------------------------------  eerpro100-diag -aaeef
>>>
>>>eepro100-diag.c:v2.06 12/10/2001 Donald Becker (becker@scyld.com)
>>> http://www.scyld.com/diag/index.html
>>>Index #1: Found a Intel i82562 Pro/100 V adapter at 0xc800.
>>>i82557 chip registers at 0xc800:
>>>  0c000050 07036000 00000000 00080002 3fe1ffff 00000600
>>>  No interrupt sources are pending.
>>>   The transmit unit state is 'Suspended'.
>>>   The receive unit state is 'Ready'.
>>>  This status is normal for an activated but idle interface.
>>> The Command register has an unprocessed command 0c00(?!).
>>>EEPROM contents, size 256x16:
>>>    00: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x08: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x10: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x18: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x20: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x28: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x30: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x38: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x40: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x48: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x50: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x58: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x60: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x68: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x70: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x78: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x80: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x88: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x90: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0x98: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xa0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xa8: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xb0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xb8: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xc0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xc8: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xd0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xd8: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xe0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xe8: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xf0: ffff ffff ffff ffff ffff ffff ffff ffff
>>>  0xf8: ffff ffff ffff ffff ffff ffff ffff ffff
>>> *****  The EEPROM checksum is INCORRECT!  *****
>>>  The checksum is 0xFF00, it should be 0xBABA!
>>>Intel EtherExpress Pro 10/100 EEPROM contents:
>>>  Station address FF:FF:FF:FF:FF:FF.
>>>  Board assembly ffffff-255, Physical connectors present: 
>>>
>>RJ45 BNC AUI MII
>>
>>>  Primary interface chip i82555 PHY #-1.
>>>    Secondary interface chip i82555, PHY -1.
>>>   Sleep mode is enabled.  This is not recommended.
>>>   Under high load the card may not respond to
>>>   PCI requests, and thus cause a master abort.
>>>   To clear sleep mode use the '-G 0 -w -w -f' options..
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe 
>>>
>>linux-kernel" in
>>
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>Please read the FAQ at  http://www.tux.org/lkml/
>>>
>>>
>>>
>>
>>-- 
>>Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
>>President of Candela Technologies Inc      http://www.candelatech.com
>>ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear
>>
>>
>>
>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2001-12-31 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 13:44 Tyan Tomcat i815T(S2080) LAN problems Ryan C. Bonham
2001-12-31 18:18 ` Ben Greear [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-05  1:48 Ryan C. Bonham
2001-12-28 17:45 Ryan C. Bonham
2001-12-31  3:31 ` Ben Greear
2001-12-28 14:35 Ryan C. Bonham

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=3C30AC0D.9010700@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Ryan@srfarms.com \
    --cc=linux-kernel@vger.kernel.org \
    /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