public inbox for gentoo-powerpc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Herminio Hernandez, Jr." <herminio.hernandezjr@gmail.com>
To: Nuno Silva <nunojsilva@ist.utl.pt>
Cc: "gentoo-powerpc@lists.gentoo.org" <gentoo-powerpc@lists.gentoo.org>
Subject: Re: [gentoo-powerpc] Re: b43 wireless not working
Date: Wed, 15 Apr 2015 19:18:36 -0500	[thread overview]
Message-ID: <CAJRA9dyPhaFnO5rDtpETVxLkqAAesP=-c+ouEof=Z=scoqHyJA@mail.gmail.com> (raw)
In-Reply-To: <93950BA3-EB9D-442D-8A53-28E90E1D4DF9@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 6041 bytes --]

I ran with the -a parameter and saw the interface. I ran ifconfig wlan0 up
and now I see it when I just run ifconfig. However I am unable to join a
wireless network. I have networkmanager installed and running. I also saw
in this thread
<https://forums.gentoo.org/viewtopic-t-964764-view-previous.html> someone
suggested to enable wext in the kernel wich I did and still no luck. Below
is what I have.

rican-linux@ibookG4-gentoo ~ $ sudo zcat /proc/config.gz | grep WEXT
Password:
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211_WEXT=y


ibookG4-gentoo ~ # ifconfig
enP2p32s15f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.133  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 00:14:51:38:fa:f8  txqueuelen 1000  (Ethernet)
        RX packets 1370  bytes 100431 (98.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 232  bytes 42740 (41.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:14:51:e4:55:af  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


rican-linux@ibookG4-gentoo ~ $ dmesg |grep -e b43 -e Broadcom
[   15.303705] b43-pci-bridge 0001:10:12.0: enabling device (0004 -> 0006)
[   18.177921] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[   18.221598] b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
[   18.221622] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050,
Revision 8
[   18.245774] Broadcom 43xx driver loaded [ Features: PMNL ]
[   24.869604] b43-phy0: Loading firmware version 666.2 (2011-02-23
01:15:07)
[   24.889614] b43-phy0 debug: Chip initialized
[   24.890355] b43-phy0 debug: 32-bit DMA initialized
[   24.890396] b43-phy0 debug: QoS enabled
[   24.909980] b43-phy0 debug: Wireless interface started
[   24.910041] b43-phy0 debug: Adding Interface type 2
[  326.614085] b43-phy0 debug: Removing Interface type 2
[  326.614234] b43-phy0 debug: Wireless interface stopped
[  326.614244] b43-phy0 debug: DMA-32 rx_ring: Used slots 1/256, Failed
frames 0/0 = 0.0%, Average tries 0.00
[  326.614545] b43-phy0 debug: DMA-32 tx_ring_AC_BK: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[  326.625849] b43-phy0 debug: DMA-32 tx_ring_AC_BE: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[  326.633659] b43-phy0 debug: DMA-32 tx_ring_AC_VI: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[  326.641672] b43-phy0 debug: DMA-32 tx_ring_AC_VO: Used slots 2/256,
Failed frames 0/77 = 0.0%, Average tries 1.00
[  326.649658] b43-phy0 debug: DMA-32 tx_ring_mcast: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[  329.428242] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[  329.469600] b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
[  329.469630] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050,
Revision 8
[  329.493807] Broadcom 43xx driver loaded [ Features: PMNL ]
[  329.677611] b43-phy0: Loading firmware version 666.2 (2011-02-23
01:15:07)
[  329.697615] b43-phy0 debug: Chip initialized
[  329.698215] b43-phy0 debug: 32-bit DMA initialized
[  329.698256] b43-phy0 debug: QoS enabled
[  329.717981] b43-phy0 debug: Wireless interface started
[  329.718044] b43-phy0 debug: Adding Interface type 2


On Wed, Apr 15, 2015 at 9:35 AM, Herminio Hernandez Jr. <
herminio.hernandezjr@gmail.com> wrote:

> No I will try when I get home from work.
>
> Sent from my iPhone
>
> > On Apr 15, 2015, at 8:34 AM, Nuno Silva <nunojsilva@ist.utl.pt> wrote:
> >
> >> On April 15, 2015 4:32:52 PM EEST, "Herminio Hernandez Jr. " <
> herminio.hernandezjr@gmail.com> wrote:
> >> I am not seeing my wireless interface when I execute ifconfig
> >>
> >> Sent from my iPhone
> >>
> >>>> On Apr 15, 2015, at 1:58 AM, "Nuno J. Silva (aka njsg)"
> >>> <nunojsilva@ist.utl.pt> wrote:
> >>>
> >>>> On 2015-04-15, Herminio Hernandez, Jr.
> >> <herminio.hernandezjr@gmail.com> wrote:
> >>>> On Tue, Apr 14, 2015 at 8:34 PM, Herminio Hernandez Jr. <
> >>>> herminio.hernandezjr@gmail.com> wrote:
> >>>>
> >>>>> I am having issues with getting wireless to work on my iBook G4. I
> >> have
> >>>>> followed the FAQ and installed the b43-fwcutter tool then I
> >> downloaded and
> >>>>> extracted the firmware. Normally in Debian and Ubuntu I would run
> >> the
> >>>>> command sudo modprobe b43 to wireless working. However I cannot get
> >> it
> >>>>> work. I have verified the kernel modules are configured correctly.
> >> I am not
> >>>>> sure what else I am missing.
> >>>
> >>> How are you checking if the wireless is working?
> >>>
> >>> Does the card show up in "ifconfig -a"?
> >>>
> >>> I think that, nowadays, you're supposed to install b43-firmware,
> >> which
> >>> will pull in b43-fwcutter. But, as far as you get the firmware, I
> >> guess
> >>> it should be enough...
> >>>
> >>>>
> >>>> Here is more info
> >>>>
> >>>> rican-linux@ibookG4-gentoo ~ $ sudo lspci -vvn|grep 43 -A7
> >>>> Password:
> >>>> 0001:10:12.0 0280: 14e4:4318 (rev 02)
> >>>
> >>> ... except that you have a BCM4318. There's at least one report of
> >> the
> >>> latest version of the broadcom firmware not working that well with
> >>> BCM4318,
> >>>
> >>> https://bugs.gentoo.org/show_bug.cgi?id=541080
> >>>
> >>> (Unfortunately, https://bugs.gentoo.org/ appears to be down right
> >> now.)
> >>>
> >>> --
> >>> Nuno Silva
> >>> Helsinki, Finland
> >
> > Are you running it with the '-a' parameter?
> > --
> > Nuno Silva (aka njsg)
>

[-- Attachment #2: Type: text/html, Size: 8444 bytes --]

  reply	other threads:[~2015-04-16  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  1:34 [gentoo-powerpc] b43 wireless not working Herminio Hernandez Jr. 
2015-04-15  2:58 ` [gentoo-powerpc] " Herminio Hernandez, Jr.
2015-04-15  6:52   ` Joseph Jezak
2015-04-15  6:58   ` Nuno J. Silva (aka njsg)
2015-04-15 13:32     ` Herminio Hernandez Jr. 
2015-04-15 13:34       ` Nuno Silva
2015-04-15 14:35         ` Herminio Hernandez Jr. 
2015-04-16  0:18           ` Herminio Hernandez, Jr. [this message]
2015-04-16  5:27             ` Nuno J. Silva (aka njsg)
2015-04-16  1:58 ` Herminio Hernandez Jr. 
2015-04-16  4:30   ` Herminio Hernandez, Jr.
2015-04-16  5:28     ` Nuno J. Silva (aka njsg)

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='CAJRA9dyPhaFnO5rDtpETVxLkqAAesP=-c+ouEof=Z=scoqHyJA@mail.gmail.com' \
    --to=herminio.hernandezjr@gmail.com \
    --cc=gentoo-powerpc@lists.gentoo.org \
    --cc=nunojsilva@ist.utl.pt \
    /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