Hi,
My new i840 chipset motherboard has onboard networking.
It ises the Intel chipset and the FXP driver detects it.
However, it reports PHY Unknown PHY 17 type 2.
on the 4.0-current 2307 snapshot.
Is there a quick fix for this? I'd really like to get
networking going with this board.
Thank
>Hi,
>My new i840 chipset motherboard has onboard networking.
>It ises the Intel chipset and the FXP driver detects it.
>
>However, it reports PHY Unknown PHY 17 type 2.
>on the 4.0-current 2307 snapshot.
>
>Is there a quick fix for this? I'd really like to get
>networking going with this boar
David
>Can you look on the motherboard and find out what type of chip it uses?
> It should be one of: 82557, 82558, or 82559. Let me know.
The lid is off.
It says GD82559
I wonder if we can get Jordan to allow a quick commit fix for this one.
The board (from SuperMicro) is a top end server b
On Thu, Mar 09, 2000 at 18:11:58 +, Roger Hardiman wrote:
> David
> >Can you look on the motherboard and find out what type of chip it uses?
> > It should be one of: 82557, 82558, or 82559. Let me know.
>
> The lid is off.
> It says GD82559
>
> I wonder if we can get Jordan to allow a qu
> Hi,
> My new i840 chipset motherboard has onboard networking.
> It ises the Intel chipset and the FXP driver detects it.
>
> However, it reports PHY Unknown PHY 17 type 2.
> on the 4.0-current 2307 snapshot.
>
> Is there a quick fix for this? I'd really like to get
> networking going with
Hi
> > However, it reports PHY Unknown type 17 addr 2.
> Mike wrote:
> This is just a diagnostic message; the interface ought to work
> regardless. Have you tried it?
Oops.
It works.
I can ping the machine next to me.
Pass me the pointy hat.
Roger
To Unsubscribe: send mail to [EMAIL PROTE
>> > However, it reports PHY Unknown type 17 addr 2.
>
>> Mike wrote:
>> This is just a diagnostic message; the interface ought to work
>> regardless. Have you tried it?
>
>Oops.
>
>It works.
>I can ping the machine next to me.
>
>Pass me the pointy hat.
Actually, it doesn't completely work.
> >> > However, it reports PHY Unknown type 17 addr 2.
> >
> >> Mike wrote:
> >> This is just a diagnostic message; the interface ought to work
> >> regardless. Have you tried it?
> >
> >Oops.
> >
> >It works.
> >I can ping the machine next to me.
> >
> >Pass me the pointy hat.
>
>Actually,
>here is:
>
>GD82559
>L942SH98
>
>There's what might be the PHY next to it (assuming it's not internal).
>
>MVT203011 CW
>722490-001
>
>I don't recognise the logo on this, unless it's a new/changed
>International Rectifier logo (looks like two diodes pointing at each
>other inside a circle and s
> >There's what might be the PHY next to it (assuming it's not internal).
> >
> >MVT203011 CW
> >722490-001
> >
> >I don't recognise the logo on this, unless it's a new/changed
> >International Rectifier logo (looks like two diodes pointing at each
> >other inside a circle and square).
>
>T
Hmm. That reminds me: I've also got a box with an onboard
8255X that isn't recognized. The relevant parts of "boot -v"
output are:
found-> vendor=0x8086, dev=0x1209, revid=0x09
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=11
>Hmm. That reminds me: I've also got a box with an onboard
>8255X that isn't recognized. The relevant parts of "boot -v"
>output are:
>
>found-> vendor=0x8086, dev=0x1209, revid=0x09
>class=02-00-00, hdrtype=0x00, mfdev=0
>subordinatebus=0secondarybus=0
>intpin=a
I wrote:
>Hmm. That reminds me: I've also got a box with an onboard
>8255X that isn't recognized. The relevant parts of "boot -v"
>output are:
>
>found-> vendor=0x8086, dev=0x1209, revid=0x09
>class=02-00-00, hdrtype=0x00, mfdev=0
>subordinatebus=0secondarybus=0
>
David Greenman wrote:
>
> >Hmm. That reminds me: I've also got a box with an onboard
> >8255X that isn't recognized. The relevant parts of "boot -v"
> >output are:
> >
> >found-> vendor=0x8086, dev=0x1209, revid=0x09
> >class=02-00-00, hdrtype=0x00, mfdev=0
> >subordinatebus=0
14 matches
Mail list logo
