Re: DS207 fails to auto boot (Bad Magic Number)

--089e013d19f85b1b4104eec17ac1
Content-Type: text/plain; charset=ISO-8859-1

> > MAC address 00:11:32:03:52:af
> > 100Mbps-FDX
>
> The MAC address looks correct and the link-negotiation also worked.
>
> Is it a Marvell 88E8001? What does the kernel print? There should
> be something like this (from my DS-101g+):
>
> skc0 at pci0 dev 15 function 0: irq 18
> skc0: interrupt moderation is 0 us
> skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
> sk0 at skc0 port A: Ethernet address 00:11:32:00:xx:xx
> makphy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5
> makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto


So it appears that I have the Marvel 88E1011.

skc0 at pci0 dev 15 function 0: irq 18
skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk0 at skc0 port A: Ethernet address 00:11:32:01:65:56
makphy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
vmmask 1c000000 schedmask 1c000000 highmask 7c000000


> This is especially strange because it worked from PPCBoot before,
> so the chip was already correctly initialized. And when the NetBSD
> kernel booted the NIC works again?


Well yes, I have network when I am inside NetBSD, but I would say taht I
also have that in PPCBoot, because the tftpload command works.

--089e013d19f85b1b4104eec17ac1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">
&gt; MAC address 00:11:32:03:52:af<br>
&gt; 100Mbps-FDX<br>
<br>
</div>The MAC address looks correct and the link-negotiation also worked.<b=
r>
<br>
Is it a Marvell 88E8001? What does the kernel print? There should<br>
be something like this (from my DS-101g+):<br>
<br>
skc0 at pci0 dev 15 function 0: irq 18<br>
skc0: interrupt moderation is 0 us<br>
skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)<br>
sk0 at skc0 port A: Ethernet address 00:11:32:00:xx:xx<br>
makphy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5<br>
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000bas=
eT-FDX, auto</blockquote><div><br>So it appears that I have the Marvel 88E1=
011.<br><br>skc0 at pci0 dev 15 function 0: irq 18<br>skc0: Marvell Yukon L=
ite Gigabit Ethernet rev. (0x9)<br>

sk0 at skc0 port A: Ethernet address 00:11:32:01:65:56<br>makphy0 at sk0 ph=
y 0: Marvell 88E1011 Gigabit PHY, rev. 5<br>makphy0: 10baseT, 10baseT-FDX, =
100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto<br>vmmask 1c000000=
 schedmask 1c000000 highmask 7c000000<br>

=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
This is especially strange because it worked from PPCBoot before,<br>
so the chip was already correctly initialized. And when the NetBSD<br>
kernel booted the NIC works again?</blockquote><div>=A0<br>Well yes, I have=
 network when I am inside NetBSD, but I would say taht I also have that in =
PPCBoot, because the tftpload command works.<br></div></div></div></div>


--089e013d19f85b1b4104eec17ac1--