Am Sonntag, 22. Oktober 2006 04:15 schrieb Adam D:
> Sebastian Muszynski wrote:
> > Am Samstag, 21. Oktober 2006 23:02 schrieb Adam D:
> >> [ 88.139217] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not
> >> available or load failed.
> >
> > The trouble is that you haven't used fwcutter to ex
Sebastian Muszynski wrote:
> Am Samstag, 21. Oktober 2006 23:02 schrieb Adam D:
>> [ 88.139217] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not
>> available or load failed.
>
> The trouble is that you haven't used fwcutter to extract the bcm43xx firmware
> of your mac osx drivers... try (
Am Samstag, 21. Oktober 2006 23:02 schrieb Adam D:
> [ 88.139217] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not
> available or load failed.
The trouble is that you haven't used fwcutter to extract the bcm43xx firmware
of your mac osx drivers... try (apt-cache search) fwcutter.
Regards,
Adam D wrote:
> The output when $ sudo ifup eth1
> SIOCSIFFLAGS: No such file or directory
> SIOCSIFFLAGS: No such file or directory
> Failed to bring up eth1.
>
>
> It looks like in dmesg the bcm43xx is found when booting (using ubuntu on
> this box). However the interface is not reconized or
The output when $ sudo ifup eth1
SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Failed to bring up eth1.
It looks like in dmesg the bcm43xx is found when booting (using ubuntu on this
box). However the interface is not reconized or connected to bcm43xx.
[snip}
5 matches
Mail list logo