It's committed so wait for new snaps and you can avoid this step.
On 2011/12/19 17:10, Wesley M. wrote:
> Hi Stuart,
>
> I tried this : boot -c at boot prompt (startup)
> I have this message : "kbc cmd word write error" just after.
> And i can't use keyboard at UKC Prompt :(
>
> Wesley.
>
> On Mon, 19 Dec 2011 12:51:58 +0000, Stuart Henderson <s...@spacehopper.org>
> wrote:
> > On 2011/12/19 16:10, Wesley M. wrote:
> >> So i
> >> tried to use 5.0 RELEASE.
> >> This time, it formats quickly. But it is the same
> >> way : kernel panic when it starts the network.
> >>
> >> The following message
> >> appear :
> >> Starting network
> >> panic: mii_phy_setmedia
> >> Stopped at
> >> Debugger+0x4:popl %ebp
> >>
> >> a "show panic" at the ddb prompt:
> >> mii_phy_setmedia
> >
> > You can try this patch. Apply, run 'cd /sys/dev/mii && make', then build
> > a new kernel. Obviously you will need to get the new kernel on to the
> > machine somehow; you can probably get it to boot with "boot -c",
> > "disable bge", "quit" - then you will need to either use a USB ethernet
> > device to get the source tree onto the machine, or copy a kernel built
> > on another machine via USB storage.
> >
> > Index: brgphy.c
> > ===================================================================
> > RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
> > retrieving revision 1.93
> > diff -u -p -r1.93 brgphy.c
> > --- brgphy.c 24 May 2010 21:23:23 -0000 1.93
> > +++ brgphy.c 19 Dec 2011 12:43:02 -0000
> > @@ -174,6 +174,8 @@ static const struct mii_phydesc brgphys[
> > MII_STR_xxBROADCOM2_BCM5709S },
> > { MII_OUI_xxBROADCOM2, MII_MODEL_xxBROADCOM2_BCM5709CAX,
> > MII_STR_xxBROADCOM2_BCM5709CAX },
> > + { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57765,
> > + MII_STR_xxBROADCOM3_BCM57765 },
> > { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57780,
> > MII_STR_xxBROADCOM3_BCM57780 },
> > { MII_OUI_BROADCOM2, MII_MODEL_BROADCOM2_BCM5906,
> > Index: miidevs
> > ===================================================================
> > RCS file: /cvs/src/sys/dev/mii/miidevs,v
> > retrieving revision 1.116
> > diff -u -p -r1.116 miidevs
> > --- miidevs 21 Jan 2011 09:46:13 -0000 1.116
> > +++ miidevs 19 Dec 2011 12:43:02 -0000
> > @@ -159,6 +159,7 @@ model xxBROADCOM2 BCM5709C 0x003c BCM570
> > model xxBROADCOM2 BCM5761 0x003d BCM5761 10/100/1000baseT PHY
> > model xxBROADCOM2 BCM5709S 0x003f BCM5709S 1000/2500baseSX PHY
> > model xxBROADCOM3 BCM57780 0x0019 BCM57780 10/100/1000baseT PHY
> > +model xxBROADCOM3 BCM57765 0x0024 BCM57765 10/100/1000baseT PHY
> > model BROADCOM BCM5400 0x0004 BCM5400 1000baseT PHY
> > model BROADCOM BCM5401 0x0005 BCM5401 1000baseT PHY
> > model BROADCOM BCM5411 0x0007 BCM5411 1000baseT PHY
> >
> > Actually I don't see any reason why not to commit this as-is.
> > It may not work but it's certainly not going to make things worse.
> > Any OKs for this?
> >
> >> I can't note "trace" message, i have no serial port on the mac... :(
> >
> > Yes you can, just re-type it from the text on-screen. But in this case
> > the ramdisk dmesg you included is enough.
