Followup:

More detailed output from lspci -k -v -n
about my broadcom crad is here:

03:00.0 0280: 14e4:4311 (rev 01)
        Subsystem: 103c:1363
        Flags: bus master, fast devsel, latency 0, IRQ 255
        Memory at b6000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Express Legacy Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel

Kjetil

On Fri, Dec 2, 2011 at 13:30, Kjetil brinchmann Halvorsen
<kjetil1...@gmail.com> wrote:
> I have the same problem as the original poster! In synaptic I have
> installed the relevant driver packages for my broadcom wifi card. Here
> are outputs from some of the commands suggested to use above:
>
> kjetil@kjetil:~$ lspci | grep "BCM"
> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 
> 01)
>
> lsmod | grep "BCM"   -> no output
> dmesg | grep "BCM"   -> no output
>
> kjetil@kjetil:~$ sudo ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:1b:24:63:ae:59
>          inet addr:192.168.1.133  Bcast:192.168.1.255  Mask:255.255.255.0
>          inet6 addr: fe80::21b:24ff:fe63:ae59/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:42361 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:29133 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:46260691 (44.1 MiB)  TX bytes:4317285 (4.1 MiB)
>          Interrupt:20 Base address:0x2000
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:291 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:291 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:8439 (8.2 KiB)  TX bytes:8439 (8.2 KiB)
>
> (That is, no output for wireless!)
>
> kjetil@kjetil:~$ nm-tool
>
> NetworkManager Tool
>
> State: connected (global)
>
> - Device: eth0  [Wired connection 1] 
> -------------------------------------------
>  Type:              Wired
>  Driver:            forcedeth
>  State:             connected
>  Default:           yes
>  HW Address:        00:1B:24:63:AE:59
>
>  Capabilities:
>    Carrier Detect:  yes
>    Speed:           100 Mb/s
>
>  Wired Properties
>    Carrier:         on
>
>  IPv4 Settings:
>    Address:         192.168.1.133
>    Prefix:          24 (255.255.255.0)
>    Gateway:         192.168.1.3
>
>    DNS:             132.248.10.2
>    DNS:             132.248.204.1
>    DNS:             132.248.237.250
>    DNS:             132.248.64.250
>
>
> (again, no output for wireless is seen!)
>
> Is there anything I can do manually to install the relevant driver in
> the kernel, as it is installed on my system, by the debian package
> firmware-b43-installer, broadcom-sta-common, broadcom-sta-source.
>
> Kjetil
>
>
> On Thu, Dec 1, 2011 at 15:09, Nitebirdz <nitebi...@sacredchaos.com> wrote:
>> On Thu, Dec 01, 2011 at 12:07:24PM -0800, Colin Reinhardt wrote:
>>> Im new to Debian/Linux...
>>> I have tried following the Debian Wireless-HowTo and other related
>>> Linux WiFi HowTos.
>>>
>>> I downloaded and installed the firmware-b43-installer and
>>> b43-fwcutter, (synaptic shows them as installed packages now).
>>>
>>> In Gnome, using network-manager (applet) there is nothing about
>>> wireless networks shown at all, only my wired LAN ethernet network is
>>> an option.
>>>
>>> How can I tell if my PCI card is being detected and firmware loaded
>>> correctly, and what are the next steps to get WiFi working?
>>> Thanks, Colin
>>>
>>
>> Commands like 'lspci' and 'lshw' should help you figure out whether or not
>> the actual hardware is detected.  Then, 'lsmod' displays whether or not
>> the kernel module is loaded.  You can also run 'ifconfig -a' as root.  As
>> far as I know, even if the interface is not configured, it should still
>> show it in the output, as long as it is detected and the kernel module is
>> successfully loaded.
>>
>> Here is a troubleshooting document that may be of some help, even though
>> it was written for Ubuntu:
>>
>> https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide
>>
>>
>>
>> --
>> Nitebirdz
>> http://www.sacredchaos.com/
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>> Archive: 
>> http://lists.debian.org/20111201210937.ge4...@dhcppc7.sacredchaos.com
>>
>
>
>
> --
> "If you want a picture of the future - imagine a boot stamping on the
> human face - forever."
>
> George Orwell (1984)



-- 
"If you want a picture of the future - imagine a boot stamping on the
human face - forever."

George Orwell (1984)


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAH=m5MgY0Rpz+fENPycG5CNg=ehbc-Ryw4mLF9+99=+xmk3...@mail.gmail.com

Reply via email to