Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

The instructions on the webpage:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md,
the portion of the note:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices
may please be perused

The firmware was already in the directory: /lib/firmware/brcm, but
still error messages were read on the terminal. Solved the issue.

There was a simple trick involved:
I had to make the file read-only for all. Then restart the computer.

Now:
# dmesg | grep -i bluetooth # Shows all Bluetooth driver info

Output:
[   29.102165] Bluetooth: Core ver 2.22
[   29.102210] Bluetooth: HCI device and connection manager initialized
[   29.102219] Bluetooth: HCI socket layer initialized
[   29.102224] Bluetooth: L2CAP socket layer initialized
[   29.102230] Bluetooth: SCO socket layer initialized
[  105.688413] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  105.688419] Bluetooth: BNEP filters: protocol multicast
[  105.688426] Bluetooth: BNEP socket layer initialized

# dmesg | grep -i bluetooth | grep -i firmware # Shows Bluetooth firmware issues

Output: None

However, I am still receiving the same error messages for the other
commands as listed  on the post:
https://lists.debian.org/debian-user/2023/10/msg00871.html

I now would need your support to install specific packages and
reconfigure the settings so that I no longer receive the error
messages.

Best wishes

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

Again, I post the following output for the command:
# sudo pkexec dmesg | grep -i "BCM"

Output:
[3.731659] usb 1-4: Product: BCM43142A0
[   17.507884] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
Controller 6.30.223.271 (r587334)
[   18.939316] Bluetooth: hci0: BCM: chip id 70
[   18.940314] Bluetooth: hci0: BCM: features 0x06
[   18.956242] Bluetooth: hci0: BCM43142A
[   18.956249] Bluetooth: hci0: BCM43142A0 (001.001.011) build 
[   19.175963] bluetooth hci0: firmware: direct-loading firmware
brcm/BCM43142A0-0a5c-216d.hcd
[   19.175977] Bluetooth: hci0: BCM43142A0 'brcm/BCM43142A0-0a5c-216d.hcd' Patch
[   29.429513] Bluetooth: hci0: BCM: Patch command 227b failed (-110)
[   29.431433] Bluetooth: hci0: BCM: Patch failed (-110)
[   39.669304] Bluetooth: hci0: BCM: Reset failed (-110)

On the webpage:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md,
the portion of the note:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices
 may please be perused:

Some Bluetooth controller (for example, BCM4354 and BCM4356) are
integrated to WiFi chipset (this can be BCM43XX 802.11ac Wireless
Network Adapter or just simple generic Broadcom PCIE Wireless). These
devices requires two kinds of firmware - first for WiFi, and second
for Bluetooth. Without WiFi firmware Bluetooth will not initialize and
will not work properly. Firmware for WiFi already included to kernel,
but you may need to do additional work to place correct NVRAM.

Resolution needed for the above note.

I used the instructions on the Debian page to install the packages:

https://wiki.debian.org/BluetoothUser

I have installed the packages bluetooth, blueman and the rest.
Have the following installed:
blueman
bluetooth
bluez
bluez-obexd
libbluetooth3
connman

I typed on the terminal:
# blue
then used tab. The following applications are installed.
blueman-adapters   blueman-assistant  blueman-report
blueman-services   bluemoon
blueman-applet blueman-managerblueman-sendto blueman-tray
 bluetoothctl

>From the Start Menu/Preferences/Bluetooth Manager, but the tray icon
isn't visible.

Used:
# sudo blueman-services
blueman-services version 2.1.4 starting
root@debianHPRajib:/home/rajib# sudo service bluetooth status
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
 Active: active (running) since Sun 2023-10-29 06:41:39 IST; 9h ago
   Docs: man:bluetoothd(8)
   Main PID: 815 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4566)
 Memory: 1.4M
CPU: 49ms
 CGroup: /system.slice/bluetooth.service
 └─815 /usr/libexec/bluetooth/bluetoothd

Oct 29 06:41:34 debianHPRajib systemd[1]: Starting Bluetooth service...
Oct 29 06:41:35 debianHPRajib bluetoothd[815]: Bluetooth daemon 5.55
Oct 29 06:41:39 debianHPRajib systemd[1]: Started Bluetooth service.
Oct 29 06:41:39 debianHPRajib bluetoothd[815]: Starting SDP server
Oct 29 06:41:40 debianHPRajib bluetoothd[815]: Bluetooth management
interface 1.18 initialized

This is consistently reported as Running.

Then tried: # sudo blueman-assistant
A pop-up says no assistant found

Then:
# sudo blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 16.17.02 ERRORManager:118 on_dbus_name_appeared:
Default adapter not found, trying first available.
blueman-manager 16.17.02 ERRORManager:122 on_dbus_name_appeared:
No adapter(s) found, exiting

Then tried:
# sudo blueman-adapters
blueman-adapters version 2.1.4 starting
blueman-adapters 16.18.13 ERRORAdapter:53 __init__  : No adapter(s) found

Then tried:
# sudo blueman-applet
blueman-applet version 2.1.4 starting
There is an instance already running

Then tried:
# sudo blueman-tray
blueman-tray version 2.1.4 starting
There is an instance already running

Then tried:
# sudo blueman-services
blueman-services version 2.1.4 starting
A window opens with title: local services and presents options.

Then tried:
# sudo blueman-report
Terminating blueman-applet
Describe your next action (keep empty if done):
Traceback (most recent call last):
  File "/usr/bin/blueman-report", line 57, in 
response = urllib2.urlopen('https://api.github.com/gists',
data.encode('UTF-8')).read()
  File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
  File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
  File "/usr/lib/python3.9/urllib/request.py", line 561, in error
return self._call_chain(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

Dear Mr. ullrich, I am so concerned by the Biblical God-like
Commandment of some of the senior members of this mailing list that I
have to ask you a second time: have you meticulously perused all my
posts relating to this problematic hardware?:
"Network controller: Broadcom Inc. and subsidiaries BCM43142
802.11b/g/n (rev 01)" card

The relevant posts begin at:
(1)   https://lists.debian.org/debian-user/2019/10/msg00493.html
(2)   https://lists.debian.org/debian-user/2023/10/msg00452.html
(3)   https://lists.debian.org/debian-user/2023/10/msg00649.html
(4)   https://lists.debian.org/debian-user/2023/10/msg00650.html

Also, I assume you have noted that I still continue to use the
oldstable system:  [Official Debian GNU/Linux Live 11.6.0 lxde
2022-12-17T11:46]/ bullseye

Sometimes I feel that some posters are actually planted here on the
Mailing List, and are heavily paid for their disruptions, by the
Proprietary Universe, to make Free and Open Source users like me lose
hope on the FSF ecosystem, feel frustrated and compel us to return to
the Proprietary Universe, turning away from the FSF/OpenSource system
and the Social Contract.

Then again, there are some who express their goodness and then vanish.
The latter, like Mr. Davidson, Mr. Curt, et al, are the ones who keep
my hope on humanity and the social contract intact. I still believe
that man could admire the best way forward: the positive non-zero sum
cooperative games, if he chose wisely.

You appear to be here since May 2011 in the debian-user ML. So you
appear to be a fairly senior member. Also, it appears that you have
been suggesting module-assistant since Jul 2011, thus experienced in
using module-assistant.

I have installed the m-a package, but not the rest, yet.

I hope that I will hear from you a second time. If I don't, then still ...

Best wishes,
Rajib
Etc.

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Hans]

Am Samstag, 28. Oktober 2023, 13:08:21 CEST schrieb Susmita/Rajib:
>  BCM43142A0
Try the following.





Building kernel modue:


1. Install the packages module-assistant, broadcom-sta, broadcom-dkms and 
broadcom-sta-
source

2. start module-assistant, command: m-a

3. In GUI enter  UPDATE

4. In GUI enter  PREPARE 

5. In GUI enter  SELECT

6. In SELECT menu choose broadcom-sta and click ok

7. In GUI enter GET

8. In GUI enter BUILD

9. In GUI enter INSTALL

After finish enter BACK and EXIT.




You will need the firmware. The firmware is distribution independent, so you 
can get it from 
other distributions, like here from AUR:

https://aur.archlinux.org/packages/bcm43142a0-firmware[1]

Get it and put it manually into /lib/firmware





Now try again. Hope this helps.

Best regards

Hans


[1] https://aur.archlinux.org/packages/bcm43142a0-firmware

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

On Wed, 25 Oct 2023 at 08:31, Susmita/Rajib  wrote:
 [ ... ]
> > Install the package firmware-b43-installer and follow the prompts.
> >
> > I'm fairly sure that's all it takes. You may need to uninstall wl
> > and / or any other changes you've made.
> [ ... ]
>
> Ok, I will gradually try to learn about this firmware, 
> "firmware-b43-installer".
[ ... ]


Dear Mr. Cater,

I took time to go through the list/description of Wireless network
cards in the package Description for which the driver   is suitable.
The list is as follows:
...
Supported chipsets:
 * BCM4306/3 (chip revision 3 only);
 * BCM4311 (NOT PCI Id 14e4:4313);
 * BCM4312;
 * BCM43131;
 * BCM4318;
 * BCM4321 (only partial support, not all versions tested);
 * BCM43217;
 * BCM4322 (only partial support for some versions, not all versions tested);
 * BCM43222 (not all versions tested);
 * BCM43224 (not all versions tested);
 * BCM43225;
 * BCM43227;
 * BCM43228;
 * BCM4331;
 * BCM47xx (detection not reliable, may not support all versions).

If observed carefully, the card which my laptop has is:
BCM43142 802.11b/g/n (rev 01)

None of the list-items has the said card mentioned. So I am doubtful
if this driver would even work.

Further, the webpage
https://wireless.wiki.kernel.org/en/users/drivers/b43#contact for the
"firmware-b43-installer"  may please be perused:

On the webpage the list with the following columns has the following
entries for the said chipset:
PCI-ID Supported? Chip ID Modes PHY version Alternative
14e4:4365 no BCM43142 b/g/n LCN40 (r3) wl

So it can be seen that the driver isn't suitable for my laptop's said card.

I again post my query to all Senior Members of the debian-user Mailing List:
If senior members have gone through this ML subject thread, your
experience is invited on the issue.

Once again the detailed dmesg output for the "bluetooth" section for
the said card is at the post:
https://lists.debian.org/debian-user/2023/10/msg00649.html.
Particularly:

# dmesg | grep -i -e "bluetooth"

[191884.268151] Bluetooth: hci0: BCM: chip id 70
[191884.269117] Bluetooth: hci0: BCM: features 0x06
[191884.285185] Bluetooth: hci0: BCM43142A
[191884.285195] Bluetooth: hci0: BCM43142A0 (001.001.011) build 
[191884.286140] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[191884.286161] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[191884.286165] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[191884.286168] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd'
[191884.286171] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd'
[191886.293688] Bluetooth: hci0: command 0x1003 tx timeout
[191886.295091] Bluetooth: hci0: unexpected event for opcode 0x1003

The wifi section works perfectly well.

Therefore, I would again return to my earlier post at:
https://lists.debian.org/debian-user/2023/10/msg00650.html

That is, the thread with the Subject:
Which Network Controller Card handling Wi-Fi, Bluetooth, etc.,
connectivities, is GNU/Linux Approved/certified, and would be (1)
compatible with my HP laptop's motherboard, and (2) could replace the
"Network controller: Broadcom Inc. and subsidiaries BCM43142
802.11b/g/n (rev 01)"

I desire a Debian approved list for perfectly compatible
Wireless-Bluetooth Cards. Like the PCI list, with the heading:
DeviceDatabase/PCI - Debian Wiki
at
https://wiki.debian.org/DeviceDatabase/PCI

Best wishes,
Rajib,
Etc.

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

From: "Andrew M.A. Cater" 
Date: Tue, 24 Oct 2023 17:12:41 +
Message-id: <[] ztf7cq23nikqt...@einval.com>
In-reply-to: <[]
CAEG4cZW87bzq6SMO0HPJAfh+UcgJFEJ=jo6ahbrwecp22yb...@mail.gmail.com>
References: <[]
caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com>

<[] CAEG4cZW87bzq6SMO0HPJAfh+UcgJFEJ=jo6ahbrwecp22yb...@mail.gmail.com>

Dear Mr. Cater, thank you for your kind reply.

> On Tue, Oct 24, 2023 at 08:19:03PM +0530, Susmita/Rajib wrote:

[ ... ]
> Please ensure that your /etc/apt/sources.list includes entries
> for main contrib and non-free
>
> See, for example, the version for Debian Bullseye (oldstable) in this
> link: https://wiki.debian.org/SourcesList
>
> Then do an apt update ; apt upgrade to bring yourself up to date.

[ ... ]

It was already done, as recorded earlier and elsewhere. So otherwise,
I am ready.


[ ... ]
> Install the package firmware-b43-installer and follow the prompts.
>
> I'm fairly sure that's all it takes. You may need to uninstall wl
> and / or any other changes you've made.
[ ... ]

Ok, I will gradually try to learn about this firmware, "firmware-b43-installer".

[ ... ]
> As the author of the FAQ posting made here every month;
> Please do not post political / nationalistic / controversial
> points here - Debian is worldwide and Bharat nationalism may be
> misplaced as not everyone will appreciate what you are writing.
[ ... ]

Sure.

One note: the correct phrase would be "Inclusive Globalism", not
"Bharatiya Nationalism".

In the said post, as a reply to Mr. Dan Purgert  -'s
post dated: Tue, 24 Oct 2023 07:45:13 -0400, I couldn't help identify
the global anglo-Saxon ploy to enslave the world embedded within his
sentences.

I immediately remembered the information on the "The Creature From
Jekyll Island, G Edward Grifin", "The Tower Of Basel, Adam LaBor",
"Committee Of 300", the "Corporation Of London", et al. I was just
networking the extreme evil that ensues from a trans-generational
scarcity of resources, and my thought flowed to the tropics, where
ample sunlight and rainfall ensured a bewilderingly rich biome with
plenty of diverse foods, merriment and festivals round the year. I
remembered that the public is only 3 meals away from a revolution.
>From there the Maslow-ian hierarchy of needs arrived ... and the rest
 Control, Covid19, planned eradication of global population,
Control of Resources by Global Corporations, End of Freedoms,
including Free air and water ...

Readers interested to know the real story of Bharat could contact for
a text download link.

Best wishes,
Rajib
Etc.

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Andrew M.A. Cater]

On Tue, Oct 24, 2023 at 08:19:03PM +0530, Susmita/Rajib wrote:
> From: "Andrew M.A. Cater" 
> Date: Tue, 24 Oct 2023 10:50:48 +
> Message-id: <[] ztehic-dyzpii...@einval.com>
> In-reply-to: <[]
> caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com>
> 
> Dear Mr. Cater,
> 
> Once again, thank you for your post.
> 
> But Mr. Cater, I would have to request you to appreciate my
> limitations to follow your advice, given the gap in our competence
> levels.
> 

Dear Rajib,

I can't help you because I don't have such a card / chipset.

Please ensure that your /etc/apt/sources.list includes entries 
for main contrib and non-free

See, for example, the version for Debian Bullseye (oldstable) in this
link: https://wiki.debian.org/SourcesList

Then do an apt update ; apt upgrade to bring yourself up to date.

Install the package firmware-b43-installer and follow the prompts.

I'm fairly sure that's all it takes. You may need to uninstall wl
and / or any other changes you've made.

As the author of the FAQ posting made here every month; 
Please do not post political / nationalistic / controversial
points here - Debian is worldwide and Bharat nationalism may be
misplaced as not everyone will appreciate what you are writing.

With every good wish, as ever,

Andy Cater

(amaca...@debian.org)


> But I will try to learn more about b43-fwcutter.
> 
> Fortunately for me, I had opened the casing to check that the said
> wireless network card is inserted into a slot on the motherboard
> internally and could be removed and reinserted.
> 
> So, you could guide me a little further on b43-fwcutter and let us see
> if I could carry the mission a little further.
> 
> Best wishes,
> Rajib
> Etc.
> 

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

From: "Andrew M.A. Cater" 
Date: Tue, 24 Oct 2023 10:50:48 +
Message-id: <[] ztehic-dyzpii...@einval.com>
In-reply-to: <[]
caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com>

Dear Mr. Cater,

Once again, thank you for your post.

But Mr. Cater, I would have to request you to appreciate my
limitations to follow your advice, given the gap in our competence
levels.

But I will try to learn more about b43-fwcutter.

Fortunately for me, I had opened the casing to check that the said
wireless network card is inserted into a slot on the motherboard
internally and could be removed and reinserted.

So, you could guide me a little further on b43-fwcutter and let us see
if I could carry the mission a little further.

Best wishes,
Rajib
Etc.

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Andrew M.A. Cater]

ation 8 Series
> HECI #0 (rev 04)
> Audio device: Intel Corporation 8 Series HD Audio
> Controller (rev 04)
> PCI bridge  : Intel Corporation 8 Series PCI Express Root
> Port 1 (rev
> e4) (prog-if 00 [Normal decode])
> PCI bridge  : Intel Corporation 8 Series PCI Express Root
> Port 3 (rev
> e4) (prog-if 00 [Normal decode])
> PCI bridge  : Intel Corporation 8 Series PCI Express Root
> Port 5 (rev
> e4) (prog-if 00 [Normal decode])
> PCI bridge  : Intel Corporation 8 Series PCI Express Root
> Port 6 (rev
> e4) (prog-if 00 [Normal decode])
> ISA bridge  : Intel Corporation 8 Series LPC Controller (rev 04)
> SATA controller : Intel Corporation 8 Series SATA Controller 1 [AHCI
> mode] (rev 04) (prog-if 01 [AHCI 1.0])
> SMBus   : Intel Corporation 8 Series SMBus Controller (rev 04)
> Signal processing controller: Intel Corporation 8 Series
> Thermal (rev 04)
> Ethernet controller : Realtek Semiconductor Co., Ltd. RTL810xE PCI
> Express Fast Ethernet controller (rev 07)
> Display controller  : Advanced Micro Devices, Inc. [AMD/ATI] Sun 
> XT
> [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
> (rev 83)
> Network controller  : Broadcom Inc. and subsidiaries BCM43142
> 802.11b/g/n (rev 01)
> 
> USB Devices
> ---
> 
> -USB Devices-
> Linux Foundation 3.0 root hub
> Chicony Electronics Co., Ltd HP Truevision HD
> Broadcom Corp. BCM43142A0 Bluetooth 4.0
> Silicon Labs USB OPTICAL MOUSE
> Linux Foundation 2.0 root hub
> 
> Battery
> ---
> 
> -Battery: BAT1-
> State   : Full
> Capacity: 100 / Full
> Battery Technology  : Li-ion
> Manufacturer: COMPAL
> Model Number: PABAS0241231
> Serial Number   : 41167
> 
> Sensors
> ---
> 
> -Sensors-
> ../../thermal_zone0/temp1   Temperature 27.80°C
> ../../BAT1/in0  Voltage 16.44V
> ../../thermal_zone2/temp1   Temperature 47.50°C
> coretemp/temp1  Temperature 53.00°C
> coretemp/temp2  Temperature 49.00°C
> coretemp/temp3  Temperature 49.00°C
> thermal/thermal_zone2   Temperature 47.50°C
> thermal/thermal_zone0   Temperature 27.80°C
> thermal/thermal_zone3   Temperature 53.05°C
> thermal/thermal_zone1   Temperature 20.00°C
> thermal/thermal_zone4   Temperature 53.00°C
> 
> Input Devices
> -
> 
> -Input Devices-
>  AT Translated Set 2 keyboard
>  Lid Switch
>  Power Button
>  Power Button
>  Video Bus
>  SynPS/2 Synaptics TouchPad
>  HP Wireless hotkeys
>  PC Speaker
>  HP WMI hotkeys
>  HDA Intel HDMI HDMI/DP,pcm:3
>  HDA Intel HDMI HDMI/DP,pcm:7
>  HDA Intel HDMI HDMI/DP,pcm:8
>  HDA Intel HDMI HDMI/DP,pcm:9
>  HDA Intel HDMI HDMI/DP,pcm:10
>  HDA Digital PCBeep
>  HDA Intel PCH Mic
>  HDA Intel PCH Headphone
>  HP Truevision HD: HP Truevision
>  YSPRINGTECH USB OPTICAL MOUSE
> 
> Storage
> ---
> 
> 
> DMI
> ---
> 
> -Product-
> Name: HP Notebook (Hewlett-Packard, www.hp.com)
> Family  : 103C_5335KV G=N L=CON B=HP (Hewlett-Packard, www.hp.com)
> Vendor  : Hewlett-Packard (Hewlett-Packard, www.hp.com)
> Version : Type1ProductConfigId
> -BIOS-
> Date: 03/24/2015
> Vendor  : Insyde
> Version : F.02
> -Board-
> Name: 80C4
> Vendor  : Hewlett-Packard (Hewlett-Packard, www.hp.com)
> Version : 96.02
> Serial Number   : (Not available; Perhaps try running HardInfo as 
> root.)
> Asset Tag   : Type2 - Board Asset Tag
> -Chassis-
> Vendor  : Hewlett-Packard (Hewlett-Packard, www.hp.com)
> Type: [10] Notebook
> Version : Chassis Version
> Serial Number   : (Not available; Perhaps try running HardInfo as 
> root.)
> Asset Tag   : Chassis Asset Tag
> 
> Memory SPD
> --
> 
> -SPD-
> Please load the eeprom module to obtain information about memory SPD
> 
> Resources
> -
> 
> -I/O Ports-
> -  : PCI Bus :00
>   -: pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
> -  : pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
> -  : pnp 00:00
>   -: pnp 00:00
>   -: pnp 00:00
>   -: pnp 00

Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

[Susmita/Rajib]

My dear illustrious Team Leaders and Senior Members, Debian-User
group, debian-user@lists.debian.org

I rephrase my earlier question posted at:
https://lists.debian.org/debian-user/2023/10/msg00452.html
which didn't receive an insightful reply or guidance. Yes, Mr. Cater
did advise on B43 series firmware along with his suggestion to update
and I thank him for that. But I have progressed a bit further than the
situation I faced then. In the end, if we fail, I will change the
Wireless Network Card.

Any advice with usual codes and inputs will be welcome.

I have reached the post at https://wiki.debian.org/DeviceDatabase/PCI

The lspci -v for the Wireless Network Interface card is:
04:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142
802.11b/g/n (rev 01)
Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at c050 (64-bit, non-prefetchable) [size=32K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-b8-ff-ff-dc-ac-d1
Capabilities: [16c] Power Budgeting 
Kernel driver in use: wl
Kernel modules: bcma, wl

The LAN interface is:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE
PCI Express Fast Ethernet controller (rev 07)
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Flags: bus master, fast devsel, latency 0, IRQ 18
I/O ports at 4000 [size=256]
Memory at c070 (64-bit, non-prefetchable) [size=4K]
Memory at c040 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-36-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Kernel driver in use: r8169
Kernel modules: r8169

However, with the output of # dmesg | grep -i -e "bluetooth"

[191884.268151] Bluetooth: hci0: BCM: chip id 70
[191884.269117] Bluetooth: hci0: BCM: features 0x06
[191884.285185] Bluetooth: hci0: BCM43142A
[191884.285195] Bluetooth: hci0: BCM43142A0 (001.001.011) build 
[191884.286140] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[191884.286161] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[191884.286165] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[191884.286168] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd'
[191884.286171] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd'
[191886.293688] Bluetooth: hci0: command 0x1003 tx timeout
[191886.295091] Bluetooth: hci0: unexpected event for opcode 0x1003


So, brcm/BCM-0a5c-216d.hcd firmware isn't working properly.

I reached the ubuntu thread and the post:
https://ubuntuforums.org/showthread.php?t=2489817=14156420#post14156420
talks about the Bluetooth driver brcm.

I searched the internet with the firmware "BCM-0a5c-216d.hcd" and reached:
https://wiki.debian.org/BCMHybridBTFirmware#Missing_Firmware_Filename

Used:
#pkexec dmidecode -t01

Outputs:
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Hewlett-Packard
Product Name: HP Notebook
Version: Type1ProductConfigId
Serial Number: **edited**
UUID: **edited**
Wake-up Type: Power Switch
SKU Number: **edited**
Family: 103C_5335KV G=N L=CON B=HP

Went to github. Read the page README.md  at:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-0a5c-216d.hcd

Instruction raed and followed: "... Place required .hcd file to
/lib/firmware/brcm ..."

But there appears to be a problem:
#sudo dmesg | grep -i -e "bluetooth"

Outputs:
[   16.740380] Bluetooth: Core ver 2.22
[   16.740410] Bluetooth: HCI device and connection manager initialized
[   16.740414] Bluetooth: HCI socket layer initialized
[   16.740418] Bluetooth: L2CAP socket layer initialized
[   16.740423] Bluetooth: SCO socket layer initialized
[   17.477920] Bluetooth: hci0: BCM: chip id 70
[   17.478903] Bluetooth: hci0: BCM: features 0x06
[   17.494925] Bluetooth: hci0: ***edited***
[   17.494929] Bluetooth: hci0: BCM43142A0 (001.001.011) build 
[   17.719998] bluetooth hci0: firmware: direct-loadin

Re: ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for

[Andrew M.A. Cater]

On Sat, Oct 21, 2023 at 08:18:30AM +0530, Susmita/Rajib wrote:
> To,
> The Team User,
> debian-user@lists.debian.org,
> Debian.org
> 
> My dear illustrious Team Leaders,
> 
> Good morning.
> 
> May please my first post at
> https://lists.debian.org/debian-user/2019/10/msg00493.html with the
> subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding
> WAN non-allocation ..." be perused.
> 

Hi Rajib,

> Following the short post by Mr. Curt at:
> https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution
> was found and the Complete Solution was posted at:
> http://forums.debian.net/viewtopic.php?f=7=143930
> 

The above posts don't give much information. As requested beFore, please
don't refer to forum posts without giving the information here on the
mailing list.

> In Brief:
> I used Debian wiki page of wl. Added the sources.list line:
> deb http://deb.debian.org/debian bullseye contrib non-free
> Updated.  Uninstalled broadcom installed package. Installed
> broadcom-sta-dkms package.from synaptic. After the rest steps the
> Wi-Fi worked, and works, perfectly.
> 
> For example:
> 
> (1) # dmesg | grep -e "wl"
> 
> [output]
> [0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015
> [   15.567967] wl: loading out-of-tree module taints kernel.
> [   15.567973] wl: module license 'MIXED/Proprietary' taints kernel.
> [   15.571378] wl: module verification failed: signature and/or
> required key missing - tainting kernel
> [   15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
> Controller 6.30.223.271 (r587334)
> [   15.751248] wl :04:00.0 wlp4s0: renamed from wlan0
> [   44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [  436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [/output]
> 

I'm assuming that you are using Debian 11 bullseye.

Check your /etc/apt/sources.list file - I assume that it has main contrib and
non-free.

The usual method of installing broadcom wifi firmware has been to use the
b43-fwcutter package I think. 

e (2) # dmesg | grep -e "bluetooth"
> 
> [output]
> [   17.284222] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0a5c-216d.hcd (-2)
> [   17.284331] bluetooth hci0: firmware: failed to load
> brcm/BCM-0a5c-216d.hcd (-2)
> [ 6815.629661] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0a5c-216d.hcd (-2)
> [ 6815.629675] bluetooth hci0: firmware: failed to load
> brcm/BCM-0a5c-216d.hcd (-2)
> [/output]
> 
> # dmesg | grep -e "broadcom" has not output.
> 
> With my inability to pair my bluetooth headphone following
> instructions at https://wiki.debian.org/BluetoothUser,
> /usr/share/doc/bluez/README.Debian.gz and installing the necessary
> packages, like bluetooth, bluez and blueman my doubt again arises.
> 
> So my Necessary Question: Has the broadcom and wl created a
> conflicting situation?
> 

Possibly, yes. I would suggest getting hold of the broadcom firmware using
the b43 package. For various reasons, the original Broadcom firmware is not
distributable by Debian - the fwcutter downloads a file and extracts the
requisite firmware

You might find it worthwhile to update to Debian 12 bookworm at some point.
The installer includes most firmware and you can adapt the apt/sources.list
to include the non-free firmware repository but I think the B43 series 
firmware can still not be included directly.

> Best wishes,
> Rajib
> Etc.
>

With every good wish,

Andy Cater 

If Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for controlli

[Susmita/Rajib]

To,
The Team User,
debian-user@lists.debian.org,
Debian.org

My dear illustrious Team Leaders,

Good morning.

May please my first post at
https://lists.debian.org/debian-user/2019/10/msg00493.html with the
subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding
WAN non-allocation ..." be perused.

Following the short post by Mr. Curt at:
https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution
was found and the Complete Solution was posted at:
http://forums.debian.net/viewtopic.php?f=7=143930

In Brief:
I used Debian wiki page of wl. Added the sources.list line:
deb http://deb.debian.org/debian bullseye contrib non-free
Updated.  Uninstalled broadcom installed package. Installed
broadcom-sta-dkms package.from synaptic. After the rest steps the
Wi-Fi worked, and works, perfectly.

For example:

(1) # dmesg | grep -e "wl"

[output]
[0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015
[   15.567967] wl: loading out-of-tree module taints kernel.
[   15.567973] wl: module license 'MIXED/Proprietary' taints kernel.
[   15.571378] wl: module verification failed: signature and/or
required key missing - tainting kernel
[   15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
Controller 6.30.223.271 (r587334)
[   15.751248] wl :04:00.0 wlp4s0: renamed from wlan0
[   44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[  436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[/output]

(2) # dmesg | grep -e "bluetooth"

[output]
[   17.284222] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[   17.284331] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[ 6815.629661] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[ 6815.629675] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[/output]

# dmesg | grep -e "broadcom" has not output.

With my inability to pair my bluetooth headphone following
instructions at https://wiki.debian.org/BluetoothUser,
/usr/share/doc/bluez/README.Debian.gz and installing the necessary
packages, like bluetooth, bluez and blueman my doubt again arises.

So my Necessary Question: Has the broadcom and wl created a
conflicting situation?

Best wishes,
Rajib
Etc.

Re: ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for

[Susmita/Rajib]

Please DON'T post your reply on this Post. Subject Line Ill-formed.

ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for con

[Susmita/Rajib]

To,
The Team User,
debian-user@lists.debian.org,
Debian.org

My dear illustrious Team Leaders,

Good morning.

May please my first post at
https://lists.debian.org/debian-user/2019/10/msg00493.html with the
subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding
WAN non-allocation ..." be perused.

Following the short post by Mr. Curt at:
https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution
was found and the Complete Solution was posted at:
http://forums.debian.net/viewtopic.php?f=7=143930

In Brief:
I used Debian wiki page of wl. Added the sources.list line:
deb http://deb.debian.org/debian bullseye contrib non-free
Updated.  Uninstalled broadcom installed package. Installed
broadcom-sta-dkms package.from synaptic. After the rest steps the
Wi-Fi worked, and works, perfectly.

For example:

(1) # dmesg | grep -e "wl"

[output]
[0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015
[   15.567967] wl: loading out-of-tree module taints kernel.
[   15.567973] wl: module license 'MIXED/Proprietary' taints kernel.
[   15.571378] wl: module verification failed: signature and/or
required key missing - tainting kernel
[   15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
Controller 6.30.223.271 (r587334)
[   15.751248] wl :04:00.0 wlp4s0: renamed from wlan0
[   44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[  436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[/output]

(2) # dmesg | grep -e "bluetooth"

[output]
[   17.284222] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[   17.284331] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[ 6815.629661] bluetooth hci0: firmware: failed to load
brcm/BCM43142A0-0a5c-216d.hcd (-2)
[ 6815.629675] bluetooth hci0: firmware: failed to load
brcm/BCM-0a5c-216d.hcd (-2)
[/output]

# dmesg | grep -e "broadcom" has not output.

With my inability to pair my bluetooth headphone following
instructions at https://wiki.debian.org/BluetoothUser,
/usr/share/doc/bluez/README.Debian.gz and installing the necessary
packages, like bluetooth, bluez and blueman my doubt again arises.

So my Necessary Question: Has the broadcom and wl created a
conflicting situation?

Best wishes,
Rajib
Etc.

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[David Martin]

Salut,

Compile-le toi même en partant des sources.




Le mar. 29 mars 2022 à 15:05, hamster  a écrit :

> Le 29/03/2022 à 14:08, David Martin a écrit :
> > Salut,
> >
> > Tu as testé avec NDISwrapper ?
> > à l'ancienne quoi
>
> NDISwrapper n'est plus disponible dans debian 11.
>
> PS : le propriétaire de l'ordi m'a dit "tant pis pour la carte wifi". Je
> lui rend donc sa machine avec debian fonctionnel mais la wifi dans les
> choux. On saura pas ce qui aurait pu marcher…
>
>

-- 
david martin

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[hamster]

Le 29/03/2022 à 14:08, David Martin a écrit :

Salut,

Tu as testé avec NDISwrapper ?
à l'ancienne quoi


NDISwrapper n'est plus disponible dans debian 11.

PS : le propriétaire de l'ordi m'a dit "tant pis pour la carte wifi". Je 
lui rend donc sa machine avec debian fonctionnel mais la wifi dans les 
choux. On saura pas ce qui aurait pu marcher…

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[hamster]

Le 29/03/2022 à 10:55, didier gaumet a écrit :



Je ne sais pas trop pourquoi ta carte wifi ne marche pas mais au cas
où:
- tu peux désinstaller broadcom-sta-source: sa présence ne fait que
causer un risque de conflit de pilotes si tu construis le module par
accident (c'est un moyen de construire le module du pilote mais
manuellement à chaque changement de version de noyau, tandis que
broadcom-sta-dkms automatise la construction du module à chaque
changement de version de noyau)
- tu peux probablement désinstaller les firmwares broadcom que tu as
installés: je suppose que les firmwares nécessaires sont installés  par
broadcom-sta-dkms vu qu'il s'agit du pilote propriétaire WL de
Broadcom? Du coup installer des firmwares pourrait (au conditionnel)
écraser des firmwares nécessaires et installés par broadcom-sta-dkms.
La procédure d'installation de firmwares que tu as suivie est bénéfique
dans le cas de pilotes libres (ne comprenant pas de firmwares).
- du coup une petite réinstallation de broadcom-sta-dkms pourrait être
utile


C'est essayé, mais ca n'améliore pas.

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[hamster]

Le 28/03/2022 à 23:05, steve a écrit :

Salut,

Tu installes sur quelle machine ?

Il semble me souvenir qu'il y a une histoire de secure-boot qui
bloquerait le wifi sur certaines machines DELL. A voir dans le BIOS pour
désactiver cette « fonctionnalité ».


C'est un ordi toshiba et j'ai déjà désactivé le secure boot.

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[hamster]

Le 28/03/2022 à 23:01, Frederic Zulian a écrit :

Hmm, peut-être devrais-tu tenter cette page-là :

https://wiki.debian.org/fr/bcm43xx 


J'ai déjà vu cette page, j'ai regardé les differents pilotes dont elle 
parle et j'ai vu que la carte qui me pose problème est supportée par wl. 
J'ai donc suivi les indications dans la page dédiée a wl, que j'ai déjà 
citée.

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[David Martin]

Salut,

Tu as testé avec NDISwrapper ?
à l'ancienne quoi


Le lun. 28 mars 2022 à 22:29, hamster  a écrit :

> Salut a tous.
>
> Je suis entrain d'installer debian 11 et j'ai des soucis pour faire
> marcher la carte wifi.
>
> J'ai suivi cette page :
> https://debian-facile.org/doc:materiel:wifi:detecter
>
> J'ai fait :
> apt install firmware-brcm80211
> apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms
> broadcom-sta-source
> modprobe -r b44 b43 b43legacy ssb brcmsmac bcma
> modprobe wl
>
> # lspci -nnkd ::0280
> 05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries
> BCM43142 802.11b/g/n [14e4:4365] (rev 01)
>  Subsystem: XAVi Technologies Corp. BCM43142 802.11b/g/n [1b9a:3002]
>  Kernel driver in use: wl
>  Kernel modules: wl
>
> --> selon la page citée ca existe que le pilote est present, j'ai
> vérifié que cette carte graphique est bien supportée par wl
> https://wiki.debian.org/wl
>
> # ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1000
>  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>  inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
>  inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp1s0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>  link/ether 00:8c:fa:88:5a:88 brd ff:ff:ff:ff:ff:ff
>  inet 192.168.0.3/24 brd 192.168.0.255 scope global dynamic
> noprefixroute enp1s0
> valid_lft 257803sec preferred_lft 257803sec
>  inet6 fe80::28c:faff:fe88:5a88/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
> 3: wlp5s0:  mtu 1500 qdisc
> pfifo_fast state DORMANT group default qlen 1000
>  link/ether 4c:bb:58:43:86:73 brd ff:ff:ff:ff:ff:ff
>
> --> toujours selon cette page, ca indique que le firmware est présent,
> mais j'ai du mal a etre sur que c'est le bon
>
> Il me reste quand meme des messages d'erreur dans dmesg :
> [   16.774536] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0930-0225.hcd (-2)
> [   16.774633] firmware_class: See https://wiki.debian.org/Firmware for
> information about missing firmware
> [   16.774772] bluetooth hci0: firmware: failed to load
> brcm/BCM-0930-0225.hcd (-2)
> [   16.774840] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
> [   16.774898] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0930-0225.hcd'
> [   16.774953] Bluetooth: hci0: BCM: 'brcm/BCM-0930-0225.hcd'
>
> Je n'ai pas réussi a trouver le firmware BCM-0930 dans la doc de debian.
>
> La carte wifi ne marche toujours pas. J'ai vérifié qu'il n'y ait pas
> d'interrupteur materiel interdisant son fonctionnement, qu'elle n'est
> pas désactivée dans le BIOS et que le mode avion n'est pas activé.
>
> J'ai pas mal cherché sur le web, je n'ai pas trouvé d'indications
> meilleures que sur la page citée plus haut.
>
> Ne sachant plus quoi faire, je me tourne vers vous. Merci pour vos
> lumières.
>
>

-- 
david martin

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[didier gaumet]

Je ne sais pas trop pourquoi ta carte wifi ne marche pas mais au cas
où:
- tu peux désinstaller broadcom-sta-source: sa présence ne fait que
causer un risque de conflit de pilotes si tu construis le module par
accident (c'est un moyen de construire le module du pilote mais
manuellement à chaque changement de version de noyau, tandis que
broadcom-sta-dkms automatise la construction du module à chaque
changement de version de noyau)
- tu peux probablement désinstaller les firmwares broadcom que tu as
installés: je suppose que les firmwares nécessaires sont installés  par
broadcom-sta-dkms vu qu'il s'agit du pilote propriétaire WL de
Broadcom? Du coup installer des firmwares pourrait (au conditionnel)
écraser des firmwares nécessaires et installés par broadcom-sta-dkms.
La procédure d'installation de firmwares que tu as suivie est bénéfique
dans le cas de pilotes libres (ne comprenant pas de firmwares).
- du coup une petite réinstallation de broadcom-sta-dkms pourrait être
utile

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[steve]

Salut,

Tu installes sur quelle machine ?

Il semble me souvenir qu'il y a une histoire de secure-boot qui
bloquerait le wifi sur certaines machines DELL. A voir dans le BIOS pour
désactiver cette « fonctionnalité ».

Peut-être une piste…

Re: difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[Frederic Zulian]

Hmm, peut-être devrais-tu tenter cette page-là :

https://wiki.debian.org/fr/bcm43xx

Essayé et approuvé, mais j'y ai passé pas mal de temps.


Frédéric ZULIAN
--
Pour la santé de votre ordinateur, préférez les logiciels libres.
https://www.april.org/



Le lun. 28 mars 2022 à 22:29, hamster  a écrit :

> Salut a tous.
>
> Je suis entrain d'installer debian 11 et j'ai des soucis pour faire
> marcher la carte wifi.
>
> J'ai suivi cette page :
> https://debian-facile.org/doc:materiel:wifi:detecter
>
> J'ai fait :
> apt install firmware-brcm80211
> apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms
> broadcom-sta-source
> modprobe -r b44 b43 b43legacy ssb brcmsmac bcma
> modprobe wl
>
> # lspci -nnkd ::0280
> 05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries
> BCM43142 802.11b/g/n [14e4:4365] (rev 01)
>  Subsystem: XAVi Technologies Corp. BCM43142 802.11b/g/n [1b9a:3002]
>  Kernel driver in use: wl
>  Kernel modules: wl
>
> --> selon la page citée ca existe que le pilote est present, j'ai
> vérifié que cette carte graphique est bien supportée par wl
> https://wiki.debian.org/wl
>
> # ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1000
>  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>  inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
>  inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp1s0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>  link/ether 00:8c:fa:88:5a:88 brd ff:ff:ff:ff:ff:ff
>  inet 192.168.0.3/24 brd 192.168.0.255 scope global dynamic
> noprefixroute enp1s0
> valid_lft 257803sec preferred_lft 257803sec
>  inet6 fe80::28c:faff:fe88:5a88/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
> 3: wlp5s0:  mtu 1500 qdisc
> pfifo_fast state DORMANT group default qlen 1000
>  link/ether 4c:bb:58:43:86:73 brd ff:ff:ff:ff:ff:ff
>
> --> toujours selon cette page, ca indique que le firmware est présent,
> mais j'ai du mal a etre sur que c'est le bon
>
> Il me reste quand meme des messages d'erreur dans dmesg :
> [   16.774536] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-0930-0225.hcd (-2)
> [   16.774633] firmware_class: See https://wiki.debian.org/Firmware for
> information about missing firmware
> [   16.774772] bluetooth hci0: firmware: failed to load
> brcm/BCM-0930-0225.hcd (-2)
> [   16.774840] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
> [   16.774898] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0930-0225.hcd'
> [   16.774953] Bluetooth: hci0: BCM: 'brcm/BCM-0930-0225.hcd'
>
> Je n'ai pas réussi a trouver le firmware BCM-0930 dans la doc de debian.
>
> La carte wifi ne marche toujours pas. J'ai vérifié qu'il n'y ait pas
> d'interrupteur materiel interdisant son fonctionnement, qu'elle n'est
> pas désactivée dans le BIOS et que le mode avion n'est pas activé.
>
> J'ai pas mal cherché sur le web, je n'ai pas trouvé d'indications
> meilleures que sur la page citée plus haut.
>
> Ne sachant plus quoi faire, je me tourne vers vous. Merci pour vos
> lumières.
>
>

difficultes pour faire marcher une carte wifi BCM43142 802.11b/g/n

[hamster]

Salut a tous.

Je suis entrain d'installer debian 11 et j'ai des soucis pour faire 
marcher la carte wifi.


J'ai suivi cette page :
https://debian-facile.org/doc:materiel:wifi:detecter

J'ai fait :
apt install firmware-brcm80211
apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,') 
linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms 
broadcom-sta-source

modprobe -r b44 b43 b43legacy ssb brcmsmac bcma
modprobe wl

# lspci -nnkd ::0280
05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries 
BCM43142 802.11b/g/n [14e4:4365] (rev 01)

    Subsystem: XAVi Technologies Corp. BCM43142 802.11b/g/n [1b9a:3002]
    Kernel driver in use: wl
    Kernel modules: wl

--> selon la page citée ca existe que le pilote est present, j'ai 
vérifié que cette carte graphique est bien supportée par wl

https://wiki.debian.org/wl

# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp1s0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

    link/ether 00:8c:fa:88:5a:88 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.3/24 brd 192.168.0.255 scope global dynamic 
noprefixroute enp1s0

   valid_lft 257803sec preferred_lft 257803sec
    inet6 fe80::28c:faff:fe88:5a88/64 scope link noprefixroute
   valid_lft forever preferred_lft forever
3: wlp5s0:  mtu 1500 qdisc 
pfifo_fast state DORMANT group default qlen 1000

    link/ether 4c:bb:58:43:86:73 brd ff:ff:ff:ff:ff:ff

--> toujours selon cette page, ca indique que le firmware est présent, 
mais j'ai du mal a etre sur que c'est le bon


Il me reste quand meme des messages d'erreur dans dmesg :
[   16.774536] bluetooth hci0: firmware: failed to load 
brcm/BCM43142A0-0930-0225.hcd (-2)
[   16.774633] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   16.774772] bluetooth hci0: firmware: failed to load 
brcm/BCM-0930-0225.hcd (-2)

[   16.774840] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   16.774898] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0930-0225.hcd'
[   16.774953] Bluetooth: hci0: BCM: 'brcm/BCM-0930-0225.hcd'

Je n'ai pas réussi a trouver le firmware BCM-0930 dans la doc de debian.

La carte wifi ne marche toujours pas. J'ai vérifié qu'il n'y ait pas 
d'interrupteur materiel interdisant son fonctionnement, qu'elle n'est 
pas désactivée dans le BIOS et que le mode avion n'est pas activé.


J'ai pas mal cherché sur le web, je n'ai pas trouvé d'indications 
meilleures que sur la page citée plus haut.


Ne sachant plus quoi faire, je me tourne vers vous. Merci pour vos lumières.

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

cklist b43legacy
> root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
> b43
> rm: não foi possível remover 
> “/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
> Arquivo ou diretório não encontrado
> rm: não foi possível remover “b43”: Arquivo ou diretório não encontrado
> root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
> b43legacy
> rm: não foi possível remover 
> “/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
> Arquivo ou diretório não encontrado
> rm: não foi possível remover “b43legacy”: Arquivo ou diretório não
> encontrado
> root@JoaoBatistaFN:~# sudo modprobe -v b44
> insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/mii.ko
> insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/phy/libphy.ko
> insmod 
> /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/ethernet/broadcom/b44.ko
>
> root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote linux-firmware-nonfree
> root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote linux-firmware-nonfree
> root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280
> …
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
> WLAN [14e4:4311] (rev 01)
> 05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8055
> PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 11)
> root@JoaoBatistaFN:~# lsmod | grep -e b43 -e wl
> b43   362085  0
> bcma   36446  1 b43
> mac80211  425575  1 b43
> ssb51408  2 b43,b44
> pcmcia 44245  2 b43,ssb
> wl   6087369  0
> cfg80211  350041  3 wl,b43,mac80211
> rng_core   12645  1 b43
> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
> root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote bcmwl-kernel-source
>
> Com isso verificamos que alguns comandos não funcionaram.
>
> Algumas informações que podem ser uteis que obtive na reinicialização:
>
>
>
> Em qui, 18 de ago de 2016 às 01:32, Thiago Canuto <
> thiagocanuto...@gmail.com> escreveu:
>
> Boa noite real bas.
>
> Mais uma vez agradeço pela ajuda da comunidade.
>
> Então... testei os passos do tópico compartilhado, e parece que ajudou um
> pouco, mas ainda não solucionou o meu problema.
>
> Aqui esta os resultados dos comandos:
>
> joaobatistafn@JoaoBatistaFN:~$ sudo modprobe b43
> [sudo] password for joaobatistafn:
> joaobatistafn@JoaoBatistaFN:~$ lsmod | grep -e b43 -e wl
> b43   362085  0
> bcma   36446  1 b43
> mac80211  425575  1 b43
> ssb51408  1 b43
> pcmcia 44245  2 b43,ssb
> wl   6087369  0
> cfg80211  350041  3 wl,b43,mac80211
> rng_core   12645  1 b43
> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
> joaobatistafn@JoaoBatistaFN:~$ dmesg | grep b43
> [  663.728750] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
> [  663.760252] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8
> [  663.760264] b43-phy0 warning: 5 GHz band is unsupported on this PHY
> [  663.792089] b43 ssb0:0: firmware: direct-loading firmware b43/ucode5.fw
> [  663.801095] b43 ssb0:0: firmware: direct-loading firmware b43/pcm5.fw
> [  663.802371] b43 ssb0:0: firmware: direct-loading firmware
> b43/b0g0initvals5.fw
> [  663.808001] b43 ssb0:0: firmware: direct-loading firmware
> b43/b0g0bsinitvals5.fw
> joaobatistafn@JoaoBatistaFN:~$ iwconfig
> bash: iwconfig: comando não encontrado
> joaobatistafn@JoaoBatistaFN:~$ su -
> Senha:
> root@JoaoBatistaFN:~# iwconfig
> wlan0 IEEE 802.11bg  ESSID:off/any
>   Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
>   Retry short limit:7   RTS thr:off   Fragment thr:off
>   Encryption key:off
>   Power Management:on
>
> lono wireless extensions.
>
> eth0  no wireless extensions.
>
> root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote bcmwl-kernel-source
> root@JoaoBatistaFN:~# grep 'blacklist b43' /

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

vel encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280
…

03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
WLAN [14e4:4311] (rev 01)
05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8055
PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 11)
root@JoaoBatistaFN:~# lsmod | grep -e b43 -e wl
b43   362085  0
bcma   36446  1 b43
mac80211  425575  1 b43
ssb51408  2 b43,b44
pcmcia 44245  2 b43,ssb
wl   6087369  0
cfg80211  350041  3 wl,b43,mac80211
rng_core   12645  1 b43
mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote bcmwl-kernel-source

Com isso verificamos que alguns comandos não funcionaram.

Algumas informações que podem ser uteis que obtive na reinicialização:



Em qui, 18 de ago de 2016 às 01:32, Thiago Canuto <thiagocanuto...@gmail.com>
escreveu:

Boa noite real bas.

Mais uma vez agradeço pela ajuda da comunidade.

Então... testei os passos do tópico compartilhado, e parece que ajudou um
pouco, mas ainda não solucionou o meu problema.

Aqui esta os resultados dos comandos:

joaobatistafn@JoaoBatistaFN:~$ sudo modprobe b43
[sudo] password for joaobatistafn:
joaobatistafn@JoaoBatistaFN:~$ lsmod | grep -e b43 -e wl
b43   362085  0
bcma   36446  1 b43
mac80211  425575  1 b43
ssb51408  1 b43
pcmcia 44245  2 b43,ssb
wl   6087369  0
cfg80211  350041  3 wl,b43,mac80211
rng_core   12645  1 b43
mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
joaobatistafn@JoaoBatistaFN:~$ dmesg | grep b43
[  663.728750] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[  663.760252] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8
[  663.760264] b43-phy0 warning: 5 GHz band is unsupported on this PHY
[  663.792089] b43 ssb0:0: firmware: direct-loading firmware b43/ucode5.fw
[  663.801095] b43 ssb0:0: firmware: direct-loading firmware b43/pcm5.fw
[  663.802371] b43 ssb0:0: firmware: direct-loading firmware
b43/b0g0initvals5.fw
[  663.808001] b43 ssb0:0: firmware: direct-loading firmware
b43/b0g0bsinitvals5.fw
joaobatistafn@JoaoBatistaFN:~$ iwconfig
bash: iwconfig: comando não encontrado
joaobatistafn@JoaoBatistaFN:~$ su -
Senha:
root@JoaoBatistaFN:~# iwconfig
wlan0 IEEE 802.11bg  ESSID:off/any
  Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:on

lono wireless extensions.

eth0  no wireless extensions.

root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote bcmwl-kernel-source
root@JoaoBatistaFN:~# grep 'blacklist b43' /etc/modprobe.d/*
/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43
/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43legacy
root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
b43
rm: não foi possível remover
“/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
Arquivo ou diretório não encontrado
rm: não foi possível remover “b43”: Arquivo ou diretório não encontrado
root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
b43legacy
rm: não foi possível remover
“/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
Arquivo ou diretório não encontrado
rm: não foi possível remover “b43legacy”: Arquivo ou diretório não
encontrado
root@JoaoBatistaFN:~# sudo modprobe -v b44
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/mii.ko
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/phy/libphy.ko
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/ethernet/broadcom/b44.ko

root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280

03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
WLAN [14e4:4311] (rev 01)
05:00.0 Etherne

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Luis Teixeira]

.d/broadcom-sta-dkms.conf:blacklist”:
>> Arquivo ou diretório não encontrado
>> rm: não foi possível remover “b43”: Arquivo ou diretório não encontrado
>> root@JoaoBatistaFN:~# sudo rm 
>> /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
>> b43legacy
>> rm: não foi possível remover 
>> “/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
>> Arquivo ou diretório não encontrado
>> rm: não foi possível remover “b43legacy”: Arquivo ou diretório não
>> encontrado
>> root@JoaoBatistaFN:~# sudo modprobe -v b44
>> insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/mii.ko
>> insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/phy/libphy.ko
>> insmod 
>> /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/ethernet/broadcom/b44.ko
>>
>> root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
>> Lendo listas de pacotes... Pronto
>> Construindo árvore de dependências
>> Lendo informação de estado... Pronto
>> E: Impossível encontrar o pacote linux-firmware-nonfree
>> root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
>> Lendo listas de pacotes... Pronto
>> Construindo árvore de dependências
>> Lendo informação de estado... Pronto
>> E: Impossível encontrar o pacote linux-firmware-nonfree
>> root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280
>> …
>>
>> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
>> WLAN [14e4:4311] (rev 01)
>> 05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8055
>> PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 11)
>> root@JoaoBatistaFN:~# lsmod | grep -e b43 -e wl
>> b43   362085  0
>> bcma   36446  1 b43
>> mac80211  425575  1 b43
>> ssb51408  2 b43,b44
>> pcmcia 44245  2 b43,ssb
>> wl   6087369  0
>> cfg80211  350041  3 wl,b43,mac80211
>> rng_core   12645  1 b43
>> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
>> root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
>> Lendo listas de pacotes... Pronto
>> Construindo árvore de dependências
>> Lendo informação de estado... Pronto
>> E: Impossível encontrar o pacote bcmwl-kernel-source
>>
>> Com isso verificamos que alguns comandos não funcionaram.
>>
>> Algumas informações que podem ser uteis que obtive na reinicialização:
>>
>>
>>
>> Em qui, 18 de ago de 2016 às 01:32, Thiago Canuto <
>> thiagocanuto...@gmail.com> escreveu:
>>
>>> Boa noite real bas.
>>>
>>> Mais uma vez agradeço pela ajuda da comunidade.
>>>
>>> Então... testei os passos do tópico compartilhado, e parece que ajudou
>>> um pouco, mas ainda não solucionou o meu problema.
>>>
>>> Aqui esta os resultados dos comandos:
>>>
>>> joaobatistafn@JoaoBatistaFN:~$ sudo modprobe b43
>>> [sudo] password for joaobatistafn:
>>> joaobatistafn@JoaoBatistaFN:~$ lsmod | grep -e b43 -e wl
>>> b43   362085  0
>>> bcma   36446  1 b43
>>> mac80211  425575  1 b43
>>> ssb51408  1 b43
>>> pcmcia 44245  2 b43,ssb
>>> wl   6087369  0
>>> cfg80211  350041  3 wl,b43,mac80211
>>> rng_core   12645  1 b43
>>> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
>>> joaobatistafn@JoaoBatistaFN:~$ dmesg | grep b43
>>> [  663.728750] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
>>> [  663.760252] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8
>>> [  663.760264] b43-phy0 warning: 5 GHz band is unsupported on this PHY
>>> [  663.792089] b43 ssb0:0: firmware: direct-loading firmware
>>> b43/ucode5.fw
>>> [  663.801095] b43 ssb0:0: firmware: direct-loading firmware b43/pcm5.fw
>>> [  663.802371] b43 ssb0:0: firmware: direct-loading firmware
>>> b43/b0g0initvals5.fw
>>> [  663.808001] b43 ssb0:0: firmware: direct-loading firmware
>>> b43/b0g0bsinitvals5.fw
>>> joaobatistafn@JoaoBatistaFN:~$ iwconfig
>>> bash: iwconfig: comando não encontrado
>>> joaobatistafn@JoaoBatistaFN:~$ su -
>>> Senha:
>>> root@JoaoBatistaFN:~# iwconfig
>>> wlan0 IEEE 802.11bg  ESSID:off/any
>>>   Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
>>>   Retry short limit:7   RTS thr:off   Fragment thr:off
>>>   Encryption key:off
>>>  

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[real bas]

> root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote linux-firmware-nonfree
> root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280
> …
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
> WLAN [14e4:4311] (rev 01)
> 05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8055
> PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 11)
> root@JoaoBatistaFN:~# lsmod | grep -e b43 -e wl
> b43   362085  0
> bcma   36446  1 b43
> mac80211  425575  1 b43
> ssb51408  2 b43,b44
> pcmcia 44245  2 b43,ssb
> wl   6087369  0
> cfg80211  350041  3 wl,b43,mac80211
> rng_core   12645  1 b43
> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
> root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
> Lendo listas de pacotes... Pronto
> Construindo árvore de dependências
> Lendo informação de estado... Pronto
> E: Impossível encontrar o pacote bcmwl-kernel-source
>
> Com isso verificamos que alguns comandos não funcionaram.
>
> Algumas informações que podem ser uteis que obtive na reinicialização:
>
>
>
> Em qui, 18 de ago de 2016 às 01:32, Thiago Canuto <
> thiagocanuto...@gmail.com> escreveu:
>
>> Boa noite real bas.
>>
>> Mais uma vez agradeço pela ajuda da comunidade.
>>
>> Então... testei os passos do tópico compartilhado, e parece que ajudou um
>> pouco, mas ainda não solucionou o meu problema.
>>
>> Aqui esta os resultados dos comandos:
>>
>> joaobatistafn@JoaoBatistaFN:~$ sudo modprobe b43
>> [sudo] password for joaobatistafn:
>> joaobatistafn@JoaoBatistaFN:~$ lsmod | grep -e b43 -e wl
>> b43   362085  0
>> bcma   36446  1 b43
>> mac80211  425575  1 b43
>> ssb51408  1 b43
>> pcmcia 44245  2 b43,ssb
>> wl   6087369  0
>> cfg80211  350041  3 wl,b43,mac80211
>> rng_core   12645  1 b43
>> mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
>> joaobatistafn@JoaoBatistaFN:~$ dmesg | grep b43
>> [  663.728750] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
>> [  663.760252] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8
>> [  663.760264] b43-phy0 warning: 5 GHz band is unsupported on this PHY
>> [  663.792089] b43 ssb0:0: firmware: direct-loading firmware b43/ucode5.fw
>> [  663.801095] b43 ssb0:0: firmware: direct-loading firmware b43/pcm5.fw
>> [  663.802371] b43 ssb0:0: firmware: direct-loading firmware
>> b43/b0g0initvals5.fw
>> [  663.808001] b43 ssb0:0: firmware: direct-loading firmware
>> b43/b0g0bsinitvals5.fw
>> joaobatistafn@JoaoBatistaFN:~$ iwconfig
>> bash: iwconfig: comando não encontrado
>> joaobatistafn@JoaoBatistaFN:~$ su -
>> Senha:
>> root@JoaoBatistaFN:~# iwconfig
>> wlan0 IEEE 802.11bg  ESSID:off/any
>>   Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
>>   Retry short limit:7   RTS thr:off   Fragment thr:off
>>   Encryption key:off
>>   Power Management:on
>>
>> lono wireless extensions.
>>
>> eth0  no wireless extensions.
>>
>> root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
>> Lendo listas de pacotes... Pronto
>> Construindo árvore de dependências
>> Lendo informação de estado... Pronto
>> E: Impossível encontrar o pacote bcmwl-kernel-source
>> root@JoaoBatistaFN:~# grep 'blacklist b43' /etc/modprobe.d/*
>> /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43
>> /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43legacy
>> root@JoaoBatistaFN:~# sudo rm 
>> /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
>> b43
>> rm: não foi possível remover 
>> “/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
>> Arquivo ou diretório não encontrado
>> rm: não foi possível remover “b43”: Arquivo ou diretório não encontrado
>> root@JoaoBatistaFN:~# sudo rm 
>> /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
>> b43legacy
>> rm: não foi possível remover 
>> “/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
>> Arquivo ou diretório não encontrado
>> rm: não foi possível remover “b43legacy”: Arquivo ou diretório não
>> encontrado
>> root@JoaoBatistaFN:~# sudo modprobe -v b44
>> insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/mii.ko
>> i

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

Boa noite real bas.

Mais uma vez agradeço pela ajuda da comunidade.

Então... testei os passos do tópico compartilhado, e parece que ajudou um
pouco, mas ainda não solucionou o meu problema.

Aqui esta os resultados dos comandos:

joaobatistafn@JoaoBatistaFN:~$ sudo modprobe b43
[sudo] password for joaobatistafn:
joaobatistafn@JoaoBatistaFN:~$ lsmod | grep -e b43 -e wl
b43   362085  0
bcma   36446  1 b43
mac80211  425575  1 b43
ssb51408  1 b43
pcmcia 44245  2 b43,ssb
wl   6087369  0
cfg80211  350041  3 wl,b43,mac80211
rng_core   12645  1 b43
mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
joaobatistafn@JoaoBatistaFN:~$ dmesg | grep b43
[  663.728750] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[  663.760252] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8
[  663.760264] b43-phy0 warning: 5 GHz band is unsupported on this PHY
[  663.792089] b43 ssb0:0: firmware: direct-loading firmware b43/ucode5.fw
[  663.801095] b43 ssb0:0: firmware: direct-loading firmware b43/pcm5.fw
[  663.802371] b43 ssb0:0: firmware: direct-loading firmware
b43/b0g0initvals5.fw
[  663.808001] b43 ssb0:0: firmware: direct-loading firmware
b43/b0g0bsinitvals5.fw
joaobatistafn@JoaoBatistaFN:~$ iwconfig
bash: iwconfig: comando não encontrado
joaobatistafn@JoaoBatistaFN:~$ su -
Senha:
root@JoaoBatistaFN:~# iwconfig
wlan0 IEEE 802.11bg  ESSID:off/any
  Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:on

lono wireless extensions.

eth0  no wireless extensions.

root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote bcmwl-kernel-source
root@JoaoBatistaFN:~# grep 'blacklist b43' /etc/modprobe.d/*
/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43
/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist b43legacy
root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
b43
rm: não foi possível remover
“/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
Arquivo ou diretório não encontrado
rm: não foi possível remover “b43”: Arquivo ou diretório não encontrado
root@JoaoBatistaFN:~# sudo rm /etc/modprobe.d/broadcom-sta-dkms.conf:blacklist
b43legacy
rm: não foi possível remover
“/etc/modprobe.d/broadcom-sta-dkms.conf:blacklist”:
Arquivo ou diretório não encontrado
rm: não foi possível remover “b43legacy”: Arquivo ou diretório não
encontrado
root@JoaoBatistaFN:~# sudo modprobe -v b44
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/mii.ko
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/phy/libphy.ko
insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/net/ethernet/broadcom/b44.ko

root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# sudo apt-get install linux-firmware-nonfree
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-firmware-nonfree
root@JoaoBatistaFN:~# lspci -nn | grep -e 0200 -e 0280

03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
WLAN [14e4:4311] (rev 01)
05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8055
PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 11)
root@JoaoBatistaFN:~# lsmod | grep -e b43 -e wl
b43   362085  0
bcma   36446  1 b43
mac80211  425575  1 b43
ssb51408  2 b43,b44
pcmcia 44245  2 b43,ssb
wl   6087369  0
cfg80211  350041  3 wl,b43,mac80211
rng_core   12645  1 b43
mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci
root@JoaoBatistaFN:~# sudo apt-get purge bcmwl-kernel-source
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote bcmwl-kernel-source

Com isso verificamos que alguns comandos não funcionaram.

Thiago

Em dom, 14 de ago de 2016 às 12:51, real bas <realba...@gmail.com> escreveu:

> Veja esse tópico [1] leia ela inteira, o criador do tópico começa a ter
> resultados depois do post #23, parece ser o mesmo problema driver instalado
> mas wifi não funciona
>
> [1] broadcom bcm4311 802.11b/g wlan driver needed
> <https://ubuntuforums.org/showthread.php?t=2203312>
>
> Em 12 de agosto de 2016 10:39, Thiago Canuto <thiagocanuto...@gmail.com>
> escreveu:
>
>> Desde o Ubuntu, depois Xubuntu, Lubuntu e por fim Debian com LXDE.
>> Talvez se

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

>>
>>>>>>>> 2016-07-05 0:24 GMT-03:00 Thiago Canuto <thiagocanuto...@gmail.com>
>>>>>>>> :
>>>>>>>>
>>>>>>>>> Olá.
>>>>>>>>>
>>>>>>>>> Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>>>>>>>>>
>>>>>>>>>> No meu notebook anterior eu usava a Broadcom sem problemas e
>>>>>>>>>> dificuldades, mas antes tive que instalar esses pacotes:
>>>>>>>>>>
>>>>>>>>>> # apt-get install b43-fwcutter linux-firmware-nonfree
>>>>>>>>>>
>>>>>>>>>> Verifique se você tem eles instalado.
>>>>>>>>>>
>>>>>>>>>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <
>>>>>>>>>> thiagocanuto...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>>> Olá.
>>>>>>>>>>>
>>>>>>>>>>> Também estou com este problema atualmente. Estou usando um
>>>>>>>>>>> notebook STi IS-1451, e já tem mais de 1 semana que tento varias
>>>>>>>>>>> alternativas para solucionar, mas nada de resolver este problema. 
>>>>>>>>>>> Pesquisei
>>>>>>>>>>> em fóruns, sites, etc. e em ultimo caso decidi "incomodar" :-[ a
>>>>>>>>>>> comunidade e pedir ajuda aqui.
>>>>>>>>>>>
>>>>>>>>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>>>>>>>>
>>>>>>>>>>> *Atualizar a source.list com contrib non-free;*
>>>>>>>>>>>
>>>>>>>>>>> # Debian 8 "Jessie"
>>>>>>>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib
>>>>>>>>>>> non-free
>>>>>>>>>>>
>>>>>>>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * No link: https://wiki.debian.org/wl
>>>>>>>>>>> <https://wiki.debian.org/wl> , fiz os procedimentos:*
>>>>>>>>>>>
>>>>>>>>>>> Installation
>>>>>>>>>>>
>>>>>>>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>>>>>>>> Debian version, for example:
>>>>>>>>>>>
>>>>>>>>>>> *# Debian 8 "Jessie"*
>>>>>>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>>>>>>
>>>>>>>>>>> Update the list of available packages. Install the
>>>>>>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>>>>>>> packages:
>>>>>>>>>>>
>>>>>>>>>>> *# apt-get update*
>>>>>>>>>>> *# apt-get install linux-image-$(uname -r|sed
>>>>>>>>>>> 's,[^-]*-[^-]*-,,') linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>>>>>>> broadcom-sta-dkms*
>>>>>>>>>>>
>>>>>>>>>>> This will also install the recommended wireless-tools
>>>>>>>>>>> package. DKMS will build the wl module for your system.
>>>>>>>>>>>
>>>>>>>>>>> Unload conflicting modules:
>>>>>>>>>>>
>>>>>>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>>>>>>
>>>>>>>>>>> Load the wl module:
>>>>>>>>>>>
>>>>>>>>>>>

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

r linux-firmware-nonfree
>>>>>>>>>
>>>>>>>>> Verifique se você tem eles instalado.
>>>>>>>>>
>>>>>>>>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com
>>>>>>>>> >:
>>>>>>>>>
>>>>>>>>>> Olá.
>>>>>>>>>>
>>>>>>>>>> Também estou com este problema atualmente. Estou usando um
>>>>>>>>>> notebook STi IS-1451, e já tem mais de 1 semana que tento varias
>>>>>>>>>> alternativas para solucionar, mas nada de resolver este problema. 
>>>>>>>>>> Pesquisei
>>>>>>>>>> em fóruns, sites, etc. e em ultimo caso decidi "incomodar" :-[ a
>>>>>>>>>> comunidade e pedir ajuda aqui.
>>>>>>>>>>
>>>>>>>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>>>>>>>
>>>>>>>>>> *Atualizar a source.list com contrib non-free;*
>>>>>>>>>>
>>>>>>>>>> # Debian 8 "Jessie"
>>>>>>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib
>>>>>>>>>> non-free
>>>>>>>>>>
>>>>>>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * No link: https://wiki.debian.org/wl
>>>>>>>>>> <https://wiki.debian.org/wl> , fiz os procedimentos:*
>>>>>>>>>>
>>>>>>>>>> Installation
>>>>>>>>>>
>>>>>>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>>>>>>> Debian version, for example:
>>>>>>>>>>
>>>>>>>>>> *# Debian 8 "Jessie"*
>>>>>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>>>>>
>>>>>>>>>> Update the list of available packages. Install the
>>>>>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>>>>>> packages:
>>>>>>>>>>
>>>>>>>>>> *# apt-get update*
>>>>>>>>>> *# apt-get install linux-image-$(uname -r|sed
>>>>>>>>>> 's,[^-]*-[^-]*-,,') linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>>>>>> broadcom-sta-dkms*
>>>>>>>>>>
>>>>>>>>>> This will also install the recommended wireless-tools
>>>>>>>>>> package. DKMS will build the wl module for your system.
>>>>>>>>>>
>>>>>>>>>> Unload conflicting modules:
>>>>>>>>>>
>>>>>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>>>>>
>>>>>>>>>> Load the wl module:
>>>>>>>>>>
>>>>>>>>>> *# modprobe wl*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *Digitei o comando:*
>>>>>>>>>>
>>>>>>>>>> *# iwconfig wlan0*
>>>>>>>>>> *wlan0 No such device*
>>>>>>>>>>
>>>>>>>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>>>>>>>
>>>>>>>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>>>>>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>>>>>>>
>>>>>>>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de
>>>>>>>>>> fazer os comandos acima do site https://wiki.debian.org/wl eu
>>>>>>>>>> conseguia visualizar, porem sem ter acesso ao Wifi.
>>>>>>>>>>
&

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

t;>>>>>>>> alternativas para solucionar, mas nada de resolver este problema. 
>>>>>>>>> Pesquisei
>>>>>>>>> em fóruns, sites, etc. e em ultimo caso decidi "incomodar" :-[ a
>>>>>>>>> comunidade e pedir ajuda aqui.
>>>>>>>>>
>>>>>>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>>>>>>
>>>>>>>>> *Atualizar a source.list com contrib non-free;*
>>>>>>>>>
>>>>>>>>> # Debian 8 "Jessie"
>>>>>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib
>>>>>>>>> non-free
>>>>>>>>>
>>>>>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl>
>>>>>>>>> , fiz os procedimentos:*
>>>>>>>>>
>>>>>>>>> Installation
>>>>>>>>>
>>>>>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>>>>>> Debian version, for example:
>>>>>>>>>
>>>>>>>>> *# Debian 8 "Jessie"*
>>>>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>>>>
>>>>>>>>> Update the list of available packages. Install the
>>>>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>>>>> packages:
>>>>>>>>>
>>>>>>>>> *# apt-get update*
>>>>>>>>> *# apt-get install linux-image-$(uname -r|sed
>>>>>>>>> 's,[^-]*-[^-]*-,,') linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>>>>> broadcom-sta-dkms*
>>>>>>>>>
>>>>>>>>> This will also install the recommended wireless-tools package.
>>>>>>>>> DKMS will build the wl module for your system.
>>>>>>>>>
>>>>>>>>> Unload conflicting modules:
>>>>>>>>>
>>>>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>>>>
>>>>>>>>> Load the wl module:
>>>>>>>>>
>>>>>>>>> *# modprobe wl*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Digitei o comando:*
>>>>>>>>>
>>>>>>>>> *# iwconfig wlan0*
>>>>>>>>> *wlan0 No such device*
>>>>>>>>>
>>>>>>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>>>>>>
>>>>>>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>>>>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>>>>>>
>>>>>>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de
>>>>>>>>> fazer os comandos acima do site https://wiki.debian.org/wl eu
>>>>>>>>> conseguia visualizar, porem sem ter acesso ao Wifi.
>>>>>>>>>
>>>>>>>>> Depois pesquisando em alguns fóruns descobri alguns comandos que
>>>>>>>>> me mostra as informações sobre o wifi, que pode ser útil. Me apareceu 
>>>>>>>>> isto:
>>>>>>>>>
>>>>>>>>> *lspci -k |grep -A2 -i network*
>>>>>>>>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g
>>>>>>>>> WLAN (rev 01)
>>>>>>>>> Subsystem: Quanta Microsystems, Inc Device 1102
>>>>>>>>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
>>>>>>>>> PCI-E Gigabit Ethernet Controller (rev 11)
>>>>>>>>>
>>>>>>>>> *Drivers:*
>>>>>>>>>
>>>>>>>>>
&

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

;>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib
>>>>>>>> non-free
>>>>>>>>
>>>>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>>>>
>>>>>>>>
>>>>>>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl>
>>>>>>>> , fiz os procedimentos:*
>>>>>>>>
>>>>>>>> Installation
>>>>>>>>
>>>>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>>>>> Debian version, for example:
>>>>>>>>
>>>>>>>> *# Debian 8 "Jessie"*
>>>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>>>
>>>>>>>> Update the list of available packages. Install the
>>>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>>>> packages:
>>>>>>>>
>>>>>>>> *# apt-get update*
>>>>>>>> *# apt-get install linux-image-$(uname -r|sed
>>>>>>>> 's,[^-]*-[^-]*-,,') linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>>>> broadcom-sta-dkms*
>>>>>>>>
>>>>>>>> This will also install the recommended wireless-tools package.
>>>>>>>> DKMS will build the wl module for your system.
>>>>>>>>
>>>>>>>> Unload conflicting modules:
>>>>>>>>
>>>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>>>
>>>>>>>> Load the wl module:
>>>>>>>>
>>>>>>>> *# modprobe wl*
>>>>>>>>
>>>>>>>>
>>>>>>>> *Digitei o comando:*
>>>>>>>>
>>>>>>>> *# iwconfig wlan0*
>>>>>>>> *wlan0 No such device*
>>>>>>>>
>>>>>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>>>>>
>>>>>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>>>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>>>>>
>>>>>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de
>>>>>>>> fazer os comandos acima do site https://wiki.debian.org/wl eu
>>>>>>>> conseguia visualizar, porem sem ter acesso ao Wifi.
>>>>>>>>
>>>>>>>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>>>>>>>> mostra as informações sobre o wifi, que pode ser útil. Me apareceu 
>>>>>>>> isto:
>>>>>>>>
>>>>>>>> *lspci -k |grep -A2 -i network*
>>>>>>>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g
>>>>>>>> WLAN (rev 01)
>>>>>>>> Subsystem: Quanta Microsystems, Inc Device 1102
>>>>>>>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
>>>>>>>> PCI-E Gigabit Ethernet Controller (rev 11)
>>>>>>>>
>>>>>>>> *Drivers:*
>>>>>>>>
>>>>>>>>
>>>>>>>> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
>>>>>>>> *total 648*
>>>>>>>> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
>>>>>>>> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
>>>>>>>> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
>>>>>>>> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
>>>>>>>> drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
>>>>>>>> -rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
>>>>>>>> -rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
>>>>>>>> -rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
>>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
>>>>>>

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

t;>
>>>>>>> *# Debian 8 "Jessie"*
>>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>>
>>>>>>> Update the list of available packages. Install the
>>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>>> packages:
>>>>>>>
>>>>>>> *# apt-get update*
>>>>>>> *# apt-get install linux-image-$(uname -r|sed
>>>>>>> 's,[^-]*-[^-]*-,,') linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>>> broadcom-sta-dkms*
>>>>>>>
>>>>>>> This will also install the recommended wireless-tools package.
>>>>>>> DKMS will build the wl module for your system.
>>>>>>>
>>>>>>> Unload conflicting modules:
>>>>>>>
>>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>>
>>>>>>> Load the wl module:
>>>>>>>
>>>>>>> *# modprobe wl*
>>>>>>>
>>>>>>>
>>>>>>> *Digitei o comando:*
>>>>>>>
>>>>>>> *# iwconfig wlan0*
>>>>>>> *wlan0 No such device*
>>>>>>>
>>>>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>>>>
>>>>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>>>>
>>>>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer
>>>>>>> os comandos acima do site https://wiki.debian.org/wl eu conseguia
>>>>>>> visualizar, porem sem ter acesso ao Wifi.
>>>>>>>
>>>>>>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>>>>>>> mostra as informações sobre o wifi, que pode ser útil. Me apareceu isto:
>>>>>>>
>>>>>>> *lspci -k |grep -A2 -i network*
>>>>>>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g
>>>>>>> WLAN (rev 01)
>>>>>>> Subsystem: Quanta Microsystems, Inc Device 1102
>>>>>>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
>>>>>>> PCI-E Gigabit Ethernet Controller (rev 11)
>>>>>>>
>>>>>>> *Drivers:*
>>>>>>>
>>>>>>>
>>>>>>> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
>>>>>>> *total 648*
>>>>>>> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
>>>>>>> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
>>>>>>> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
>>>>>>> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
>>>>>>> drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
>>>>>>> -rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
>>>>>>> -rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
>>>>>>> -rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43legacy
>>>>>>> drwxr-xr-x  5 root root  4096 Jun 19 19:03 brcm80211
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 hostap
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 ipw2x00
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 iwlegacy
>>>>>>> drwxr-xr-x  4 root root  4096 Jun 19 19:03 iwlwifi
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas_tf
>>>>>>> -rw-r--r--  1 root root 49656 Abr  8 19:21 mac80211_hwsim.ko
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 mwifiex
>>>>>>> -rw-r--r--  1 root root 64476 Abr  8 19:21 mwl8k.ko
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 orinoco
>>>>>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 p54
>>>>>>> -

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

Primeiro, eu mandei uma mensagem hoje falando que eu tinha escrito o nome
do pacote errado, o certo é:

firmware-linux-nonfree

Segundo, você está executando como root ?

Por último, você não disse que já tinha instalado o b43-fwcutter ? como
assim você deseja saber se já tem instalado ? você já não sabia antes ?

O comando para ver pacotes instalados é:

dpkg -l

para filtrar para ver um pacote específico:

dpkg -l  | grep b43

ou dpkg -l | grep firmware

Abraços.

Em 5 de julho de 2016 17:43, Thiago Canuto <thiagocanuto...@gmail.com>
escreveu:

> Olá. Tentei o comando:
>  # apt-get install b43-fwcutter linux-firmware-nonfree
>
> Depois me apareceu a seguinte mensagem:
>
> # apt-get install b43-fwcutter linux-firmware-nonfree
> E: Não foi possível obter trava /var/lib/dpkg/lock - open (11: Recurso
> temporariamente indisponível)
> E: Não foi possível obter acesso exclusivo ao directório de administração
> (/var/lib/dpkg/), outro processo está a utilizá-lo?
>
> Aproveito e pergunto como saber se já tenho instalado, caso já tenha
> instalado? Pois não me lembro.
>
> 2016-07-05 16:20 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>
>> Oxi, agora que vi, escrevi errado, o certo é:
>>
>> firmware-linux-nonfree
>>
>> hehehe, desculpem, mas e como disse o Vinícius, instalou o
>> firmware-linux-nonfree ?
>>
>> Abraços.
>>
>> 2016-07-05 13:36 GMT-04:00 Vinícius RM <v...@cin.ufpe.br>:
>>
>>> E o linux-firmware-nonfree?
>>>
>>> 2016-07-05 0:24 GMT-03:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>>
>>>> Olá.
>>>>
>>>> Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.
>>>>
>>>>
>>>> 2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>>>>
>>>>> No meu notebook anterior eu usava a Broadcom sem problemas e
>>>>> dificuldades, mas antes tive que instalar esses pacotes:
>>>>>
>>>>> # apt-get install b43-fwcutter linux-firmware-nonfree
>>>>>
>>>>> Verifique se você tem eles instalado.
>>>>>
>>>>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>>>>
>>>>>> Olá.
>>>>>>
>>>>>> Também estou com este problema atualmente. Estou usando um notebook
>>>>>> STi IS-1451, e já tem mais de 1 semana que tento varias alternativas para
>>>>>> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, 
>>>>>> sites,
>>>>>> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir
>>>>>> ajuda aqui.
>>>>>>
>>>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>>>
>>>>>> *Atualizar a source.list com contrib non-free;*
>>>>>>
>>>>>> # Debian 8 "Jessie"
>>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>>>>>>
>>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>>
>>>>>>
>>>>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> ,
>>>>>> fiz os procedimentos:*
>>>>>>
>>>>>> Installation
>>>>>>
>>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>>> Debian version, for example:
>>>>>>
>>>>>> *# Debian 8 "Jessie"*
>>>>>> *deb http://httpredir.debian.org/debian/
>>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>>
>>>>>> Update the list of available packages. Install the
>>>>>> relevant/latest linux-image, linux-headers and broadcom-sta-dkms 
>>>>>> packages:
>>>>>>
>>>>>> *# apt-get update*
>>>>>> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>>> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>>>>>>
>>>>>> This will also install the recommended wireless-tools package.
>>>>>> DKMS will build the wl module for your system.
>>>>>>
>>>>>> Unload conflicting modules:
>>>>>>
>>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>>
>>>>&g

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

Olá. Tentei o comando:
 # apt-get install b43-fwcutter linux-firmware-nonfree

Depois me apareceu a seguinte mensagem:

# apt-get install b43-fwcutter linux-firmware-nonfree
E: Não foi possível obter trava /var/lib/dpkg/lock - open (11: Recurso
temporariamente indisponível)
E: Não foi possível obter acesso exclusivo ao directório de administração
(/var/lib/dpkg/), outro processo está a utilizá-lo?

Aproveito e pergunto como saber se já tenho instalado, caso já tenha
instalado? Pois não me lembro.

2016-07-05 16:20 GMT-04:00 Rodolfo <rof20...@gmail.com>:

> Oxi, agora que vi, escrevi errado, o certo é:
>
> firmware-linux-nonfree
>
> hehehe, desculpem, mas e como disse o Vinícius, instalou o
> firmware-linux-nonfree ?
>
> Abraços.
>
> 2016-07-05 13:36 GMT-04:00 Vinícius RM <v...@cin.ufpe.br>:
>
>> E o linux-firmware-nonfree?
>>
>> 2016-07-05 0:24 GMT-03:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>
>>> Olá.
>>>
>>> Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.
>>>
>>>
>>> 2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>>>
>>>> No meu notebook anterior eu usava a Broadcom sem problemas e
>>>> dificuldades, mas antes tive que instalar esses pacotes:
>>>>
>>>> # apt-get install b43-fwcutter linux-firmware-nonfree
>>>>
>>>> Verifique se você tem eles instalado.
>>>>
>>>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>>>
>>>>> Olá.
>>>>>
>>>>> Também estou com este problema atualmente. Estou usando um notebook
>>>>> STi IS-1451, e já tem mais de 1 semana que tento varias alternativas para
>>>>> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, 
>>>>> sites,
>>>>> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir
>>>>> ajuda aqui.
>>>>>
>>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>>
>>>>> *Atualizar a source.list com contrib non-free;*
>>>>>
>>>>> # Debian 8 "Jessie"
>>>>> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>>>>>
>>>>> Instalei o firmware b43 através do Synaptic;
>>>>>
>>>>>
>>>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> ,
>>>>> fiz os procedimentos:*
>>>>>
>>>>> Installation
>>>>>
>>>>> Add a "non-free" component to /etc/apt/sources.list for your
>>>>> Debian version, for example:
>>>>>
>>>>> *# Debian 8 "Jessie"*
>>>>> *deb http://httpredir.debian.org/debian/
>>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>>
>>>>> Update the list of available packages. Install the relevant/latest
>>>>> linux-image, linux-headers and broadcom-sta-dkms packages:
>>>>>
>>>>> *# apt-get update*
>>>>> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>>> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>>>>>
>>>>> This will also install the recommended wireless-tools package.
>>>>> DKMS will build the wl module for your system.
>>>>>
>>>>> Unload conflicting modules:
>>>>>
>>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>>
>>>>> Load the wl module:
>>>>>
>>>>> *# modprobe wl*
>>>>>
>>>>>
>>>>> *Digitei o comando:*
>>>>>
>>>>> *# iwconfig wlan0*
>>>>> *wlan0 No such device*
>>>>>
>>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>>
>>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>>
>>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer
>>>>> os comandos acima do site https://wiki.debian.org/wl eu conseguia
>>>>> visualizar, porem sem ter acesso ao Wifi.
>>>>>
>>>>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>>>>> mostra as informa

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

Oxi, agora que vi, escrevi errado, o certo é:

firmware-linux-nonfree

hehehe, desculpem, mas e como disse o Vinícius, instalou o
firmware-linux-nonfree ?

Abraços.

2016-07-05 13:36 GMT-04:00 Vinícius RM <v...@cin.ufpe.br>:

> E o linux-firmware-nonfree?
>
> 2016-07-05 0:24 GMT-03:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>
>> Olá.
>>
>> Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.
>>
>>
>> 2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>>
>>> No meu notebook anterior eu usava a Broadcom sem problemas e
>>> dificuldades, mas antes tive que instalar esses pacotes:
>>>
>>> # apt-get install b43-fwcutter linux-firmware-nonfree
>>>
>>> Verifique se você tem eles instalado.
>>>
>>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>>
>>>> Olá.
>>>>
>>>> Também estou com este problema atualmente. Estou usando um notebook STi
>>>> IS-1451, e já tem mais de 1 semana que tento varias alternativas para
>>>> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, sites,
>>>> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir
>>>> ajuda aqui.
>>>>
>>>> Fiz todos os passos iniciais depois de instalar como:
>>>>
>>>> *Atualizar a source.list com contrib non-free;*
>>>>
>>>> # Debian 8 "Jessie"
>>>> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>>>>
>>>> Instalei o firmware b43 através do Synaptic;
>>>>
>>>>
>>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> ,
>>>> fiz os procedimentos:*
>>>>
>>>> Installation
>>>>
>>>> Add a "non-free" component to /etc/apt/sources.list for your Debian
>>>> version, for example:
>>>>
>>>> *# Debian 8 "Jessie"*
>>>> *deb http://httpredir.debian.org/debian/
>>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>>
>>>> Update the list of available packages. Install the relevant/latest
>>>> linux-image, linux-headers and broadcom-sta-dkms packages:
>>>>
>>>> *# apt-get update*
>>>> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>>> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>>>>
>>>> This will also install the recommended wireless-tools package. DKMS
>>>> will build the wl module for your system.
>>>>
>>>> Unload conflicting modules:
>>>>
>>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>>
>>>> Load the wl module:
>>>>
>>>> *# modprobe wl*
>>>>
>>>>
>>>> *Digitei o comando:*
>>>>
>>>> *# iwconfig wlan0*
>>>> *wlan0 No such device*
>>>>
>>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>>
>>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>>
>>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer os
>>>> comandos acima do site https://wiki.debian.org/wl eu conseguia
>>>> visualizar, porem sem ter acesso ao Wifi.
>>>>
>>>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>>>> mostra as informações sobre o wifi, que pode ser útil. Me apareceu isto:
>>>>
>>>> *lspci -k |grep -A2 -i network*
>>>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN
>>>> (rev 01)
>>>> Subsystem: Quanta Microsystems, Inc Device 1102
>>>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
>>>> PCI-E Gigabit Ethernet Controller (rev 11)
>>>>
>>>> *Drivers:*
>>>>
>>>>
>>>> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
>>>> *total 648*
>>>> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
>>>> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
>>>> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
>>>> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
>>>> drwxr-xr-x  9 root root  4096 Jun 19 19:

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Vinícius RM]

E o linux-firmware-nonfree?

2016-07-05 0:24 GMT-03:00 Thiago Canuto <thiagocanuto...@gmail.com>:

> Olá.
>
> Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.
>
>
> 2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:
>
>> No meu notebook anterior eu usava a Broadcom sem problemas e
>> dificuldades, mas antes tive que instalar esses pacotes:
>>
>> # apt-get install b43-fwcutter linux-firmware-nonfree
>>
>> Verifique se você tem eles instalado.
>>
>> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>>
>>> Olá.
>>>
>>> Também estou com este problema atualmente. Estou usando um notebook STi
>>> IS-1451, e já tem mais de 1 semana que tento varias alternativas para
>>> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, sites,
>>> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir ajuda
>>> aqui.
>>>
>>> Fiz todos os passos iniciais depois de instalar como:
>>>
>>> *Atualizar a source.list com contrib non-free;*
>>>
>>> # Debian 8 "Jessie"
>>> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>>>
>>> Instalei o firmware b43 através do Synaptic;
>>>
>>>
>>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> , fiz
>>> os procedimentos:*
>>>
>>> Installation
>>>
>>> Add a "non-free" component to /etc/apt/sources.list for your Debian
>>> version, for example:
>>>
>>> *# Debian 8 "Jessie"*
>>> *deb http://httpredir.debian.org/debian/
>>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>>
>>> Update the list of available packages. Install the relevant/latest
>>> linux-image, linux-headers and broadcom-sta-dkms packages:
>>>
>>> *# apt-get update*
>>> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>>> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>>>
>>> This will also install the recommended wireless-tools package. DKMS
>>> will build the wl module for your system.
>>>
>>> Unload conflicting modules:
>>>
>>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>>
>>> Load the wl module:
>>>
>>> *# modprobe wl*
>>>
>>>
>>> *Digitei o comando:*
>>>
>>> *# iwconfig wlan0*
>>> *wlan0 No such device*
>>>
>>> Instalei o *laptop-mode-tools* através do Synaptic.
>>>
>>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>>
>>> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer os
>>> comandos acima do site https://wiki.debian.org/wl eu conseguia
>>> visualizar, porem sem ter acesso ao Wifi.
>>>
>>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>>> mostra as informações sobre o wifi, que pode ser útil. Me apareceu isto:
>>>
>>> *lspci -k |grep -A2 -i network*
>>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN
>>> (rev 01)
>>> Subsystem: Quanta Microsystems, Inc Device 1102
>>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E
>>> Gigabit Ethernet Controller (rev 11)
>>>
>>> *Drivers:*
>>>
>>>
>>> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
>>> *total 648*
>>> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
>>> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
>>> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
>>> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
>>> drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
>>> -rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
>>> -rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
>>> -rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43legacy
>>> drwxr-xr-x  5 root root  4096 Jun 19 19:03 brcm80211
>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 hostap
>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 ipw2x00
>>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 iwlegacy
>>> drwxr-xr-x  4 root root  4096 Jun 19 

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

Olá.

Sim. Já tenho instalado o b43-fwcutter. Instalei pelo Synaptic.

2016-07-04 7:16 GMT-04:00 Rodolfo <rof20...@gmail.com>:

> No meu notebook anterior eu usava a Broadcom sem problemas e dificuldades,
> mas antes tive que instalar esses pacotes:
>
> # apt-get install b43-fwcutter linux-firmware-nonfree
>
> Verifique se você tem eles instalado.
>
> 2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:
>
>> Olá.
>>
>> Também estou com este problema atualmente. Estou usando um notebook STi
>> IS-1451, e já tem mais de 1 semana que tento varias alternativas para
>> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, sites,
>> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir ajuda
>> aqui.
>>
>> Fiz todos os passos iniciais depois de instalar como:
>>
>> *Atualizar a source.list com contrib non-free;*
>>
>> # Debian 8 "Jessie"
>> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>>
>> Instalei o firmware b43 através do Synaptic;
>>
>>
>> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> , fiz
>> os procedimentos:*
>>
>> Installation
>>
>> Add a "non-free" component to /etc/apt/sources.list for your Debian
>> version, for example:
>>
>> *# Debian 8 "Jessie"*
>> *deb http://httpredir.debian.org/debian/
>> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>>
>> Update the list of available packages. Install the relevant/latest
>> linux-image, linux-headers and broadcom-sta-dkms packages:
>>
>> *# apt-get update*
>> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
>> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>>
>> This will also install the recommended wireless-tools package. DKMS
>> will build the wl module for your system.
>>
>> Unload conflicting modules:
>>
>> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>>
>> Load the wl module:
>>
>> *# modprobe wl*
>>
>>
>> *Digitei o comando:*
>>
>> *# iwconfig wlan0*
>> *wlan0 No such device*
>>
>> Instalei o *laptop-mode-tools* através do Synaptic.
>>
>> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
>> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>>
>> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer os
>> comandos acima do site https://wiki.debian.org/wl eu conseguia
>> visualizar, porem sem ter acesso ao Wifi.
>>
>> Depois pesquisando em alguns fóruns descobri alguns comandos que me
>> mostra as informações sobre o wifi, que pode ser útil. Me apareceu isto:
>>
>> *lspci -k |grep -A2 -i network*
>> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN
>> (rev 01)
>> Subsystem: Quanta Microsystems, Inc Device 1102
>> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E
>> Gigabit Ethernet Controller (rev 11)
>>
>> *Drivers:*
>>
>>
>> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
>> *total 648*
>> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
>> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
>> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
>> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
>> drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
>> -rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
>> -rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
>> -rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43legacy
>> drwxr-xr-x  5 root root  4096 Jun 19 19:03 brcm80211
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 hostap
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 ipw2x00
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 iwlegacy
>> drwxr-xr-x  4 root root  4096 Jun 19 19:03 iwlwifi
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas_tf
>> -rw-r--r--  1 root root 49656 Abr  8 19:21 mac80211_hwsim.ko
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 mwifiex
>> -rw-r--r--  1 root root 64476 Abr  8 19:21 mwl8k.ko
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 orinoco
>> drwxr-xr-x  2 root root  4096 Jun 19 19:03 p54
>> -rw-r--r--  1 root root 63056 Abr  8 19:21 ray_cs.ko
>> -rw-r--r--  1 root root 6

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

No meu notebook anterior eu usava a Broadcom sem problemas e dificuldades,
mas antes tive que instalar esses pacotes:

# apt-get install b43-fwcutter linux-firmware-nonfree

Verifique se você tem eles instalado.

2016-07-04 2:15 GMT-04:00 Thiago Canuto <thiagocanuto...@gmail.com>:

> Olá.
>
> Também estou com este problema atualmente. Estou usando um notebook STi
> IS-1451, e já tem mais de 1 semana que tento varias alternativas para
> solucionar, mas nada de resolver este problema. Pesquisei em fóruns, sites,
> etc. e em ultimo caso decidi "incomodar" :-[ a comunidade e pedir ajuda
> aqui.
>
> Fiz todos os passos iniciais depois de instalar como:
>
> *Atualizar a source.list com contrib non-free;*
>
> # Debian 8 "Jessie"
> deb http://httpredir.debian.org/debian/ jessie main contrib non-free
>
> Instalei o firmware b43 através do Synaptic;
>
>
> * No link: https://wiki.debian.org/wl <https://wiki.debian.org/wl> , fiz
> os procedimentos:*
>
> Installation
>
> Add a "non-free" component to /etc/apt/sources.list for your Debian
> version, for example:
>
> *# Debian 8 "Jessie"*
> *deb http://httpredir.debian.org/debian/
> <http://httpredir.debian.org/debian/> jessie main contrib non-free*
>
> Update the list of available packages. Install the relevant/latest
> linux-image, linux-headers and broadcom-sta-dkms packages:
>
> *# apt-get update*
> *# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,')
> linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms*
>
> This will also install the recommended wireless-tools package. DKMS
> will build the wl module for your system.
>
> Unload conflicting modules:
>
> *# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma*
>
> Load the wl module:
>
> *# modprobe wl*
>
>
> *Digitei o comando:*
>
> *# iwconfig wlan0*
> *wlan0 No such device*
>
> Instalei o *laptop-mode-tools* através do Synaptic.
>
> Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de
> /etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook
>
> Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer os
> comandos acima do site https://wiki.debian.org/wl eu conseguia
> visualizar, porem sem ter acesso ao Wifi.
>
> Depois pesquisando em alguns fóruns descobri alguns comandos que me mostra
> as informações sobre o wifi, que pode ser útil. Me apareceu isto:
>
> *lspci -k |grep -A2 -i network*
> 03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN
> (rev 01)
> Subsystem: Quanta Microsystems, Inc Device 1102
> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E
> Gigabit Ethernet Controller (rev 11)
>
> *Drivers:*
>
>
> *$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/*
> *total 648*
> -rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
> -rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
> -rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
> -rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
> drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
> -rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
> -rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
> -rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43legacy
> drwxr-xr-x  5 root root  4096 Jun 19 19:03 brcm80211
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 hostap
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 ipw2x00
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 iwlegacy
> drwxr-xr-x  4 root root  4096 Jun 19 19:03 iwlwifi
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas_tf
> -rw-r--r--  1 root root 49656 Abr  8 19:21 mac80211_hwsim.ko
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 mwifiex
> -rw-r--r--  1 root root 64476 Abr  8 19:21 mwl8k.ko
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 orinoco
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 p54
> -rw-r--r--  1 root root 63056 Abr  8 19:21 ray_cs.ko
> -rw-r--r--  1 root root 62060 Abr  8 19:21 rndis_wlan.ko
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 rsi
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 rt2x00
> drwxr-xr-x  4 root root  4096 Jun 19 19:03 rtl818x
> drwxr-xr-x 12 root root  4096 Jun 19 19:03 rtlwifi
> -rw-r--r--  1 root root 29420 Abr  8 19:21 wl3501_cs.ko
> -rw-r--r--  1 root root 29176 Abr  8 19:21 zd1201.ko
> drwxr-xr-x  2 root root  4096 Jun 19 19:03 zd1211rw
>
>
> *# lspci -nn -d 14e4:*
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
> WLAN [14e4:4311] (rev 01)
>

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Thiago Canuto]

Olá.

Também estou com este problema atualmente. Estou usando um notebook STi 
IS-1451, e já tem mais de 1 semana que tento varias alternativas para 
solucionar, mas nada de resolver este problema. Pesquisei em fóruns, 
sites, etc. e em ultimo caso decidi "incomodar":-[ a comunidade e pedir 
ajuda aqui.


Fiz todos os passos iniciais depois de instalar como:

*Atualizar a source.list com contrib non-free;*

# Debian 8 "Jessie"
deb http://httpredir.debian.org/debian/ jessie main contrib non-free

Instalei o firmware b43 através do Synaptic;

*
No link: https://wiki.debian.org/wl , fiz os procedimentos:*

Installation

Add a "non-free" component to /etc/apt/sources.list for your Debian 
version, for example:


/# Debian 8 "Jessie"//
//deb http://httpredir.debian.org/debian/ jessie main contrib non-free/

Update the list of available packages. Install the relevant/latest 
linux-image, linux-headers and broadcom-sta-dkms packages:


/# apt-get update//
//# apt-get install linux-image-$(uname -r|sed 's,[^-]*-[^-]*-,,') 
linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') broadcom-sta-dkms/


This will also install the recommended wireless-tools package. DKMS 
will build the wl module for your system.


Unload conflicting modules:

/# modprobe -r b44 b43 b43legacy ssb brcmsmac bcma/

Load the wl module:

/# modprobe wl//
/

*Digitei o comando:**
*
/# iwconfig wlan0//
//wlan0 No such device//
/
Instalei o *laptop-mode-tools* através do Synaptic.

Alterei o *WIRELESS_BATT_POWER_SAVING=0* dentro de 
/etc/laptop-mode/conf.d/wireless-power.conf e reinicie o notebook


Depois disso não consegui mais visualizar o *wlan0*. Antes de fazer os 
comandos acima do site https://wiki.debian.org/wl eu conseguia 
visualizar, porem sem ter acesso ao Wifi.


Depois pesquisando em alguns fóruns descobri alguns comandos que me 
mostra as informações sobre o wifi, que pode ser útil. Me apareceu isto:


*lspci -k |grep -A2 -i network*
03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN 
(rev 01)

Subsystem: Quanta Microsystems, Inc Device 1102
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E 
Gigabit Ethernet Controller (rev 11)

*
**Drivers:*


*$ ls -l /lib/modules/`uname -r`/kernel/drivers/net/wireless/**
**total 648*
-rw-r--r--  1 root root 37160 Abr  8 19:21 adm8211.ko
-rw-r--r--  1 root root  7284 Abr  8 19:21 airo_cs.ko
-rw-r--r--  1 root root 96676 Abr  8 19:21 airo.ko
-rw-r--r--  1 root root 53388 Abr  8 19:21 at76c50x-usb.ko
drwxr-xr-x  9 root root  4096 Jun 19 19:03 ath
-rw-r--r--  1 root root 10688 Abr  8 19:21 atmel_cs.ko
-rw-r--r--  1 root root 48124 Abr  8 19:21 atmel.ko
-rw-r--r--  1 root root  4196 Abr  8 19:21 atmel_pci.ko
drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43
drwxr-xr-x  2 root root  4096 Jun 19 19:03 b43legacy
drwxr-xr-x  5 root root  4096 Jun 19 19:03 brcm80211
drwxr-xr-x  2 root root  4096 Jun 19 19:03 hostap
drwxr-xr-x  2 root root  4096 Jun 19 19:03 ipw2x00
drwxr-xr-x  2 root root  4096 Jun 19 19:03 iwlegacy
drwxr-xr-x  4 root root  4096 Jun 19 19:03 iwlwifi
drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas
drwxr-xr-x  2 root root  4096 Jun 19 19:03 libertas_tf
-rw-r--r--  1 root root 49656 Abr  8 19:21 mac80211_hwsim.ko
drwxr-xr-x  2 root root  4096 Jun 19 19:03 mwifiex
-rw-r--r--  1 root root 64476 Abr  8 19:21 mwl8k.ko
drwxr-xr-x  2 root root  4096 Jun 19 19:03 orinoco
drwxr-xr-x  2 root root  4096 Jun 19 19:03 p54
-rw-r--r--  1 root root 63056 Abr  8 19:21 ray_cs.ko
-rw-r--r--  1 root root 62060 Abr  8 19:21 rndis_wlan.ko
drwxr-xr-x  2 root root  4096 Jun 19 19:03 rsi
drwxr-xr-x  2 root root  4096 Jun 19 19:03 rt2x00
drwxr-xr-x  4 root root  4096 Jun 19 19:03 rtl818x
drwxr-xr-x 12 root root  4096 Jun 19 19:03 rtlwifi
-rw-r--r--  1 root root 29420 Abr  8 19:21 wl3501_cs.ko
-rw-r--r--  1 root root 29176 Abr  8 19:21 zd1201.ko
drwxr-xr-x  2 root root  4096 Jun 19 19:03 zd1211rw

*
**# lspci -nn -d 14e4:*
03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 
802.11b/g WLAN [14e4:4311] (rev 01)

*
**Driver carregado:**
**
**~$ lspci -k |grep -A2 -i network*
03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN 
(rev 01)

Subsystem: Quanta Microsystems, Inc Device 1102
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E 
Gigabit Ethernet Controller (rev 11)


*
**$ lspci*
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML 
and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 (rev 02)
00:1c.1

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rafael Henrique da Silva Correia]

Rogério, eu particularmente toda distribuição que uso a primeira coisa 
que eu faço é remover o Network Manager (Gnome)... eu particularmente 
ODEIO ele.


Sem o Network Manager as coisas sempre funcionam.

Abraço

Em 25-06-2011 20:29, Rogerio R. Silva escreveu:

Rafael,

Obrigado pela mensagem. Já tenho esses pacotes instalados. Minha
interface está confusa. Wireless aparece desconectada (veja no fim da
mensagem).

Abs. - rogério

# nm-tool

NetworkManager Tool

State: connected

- Device: eth1 -
   Type:  802.11 WiFi
   Driver:wl
   State: disconnected
   Default:   no
   HW Address:00:17:C4:03:9E:EF

   Capabilities:

   Wireless Properties
 WEP Encryption:  yes
 WPA Encryption:  yes
 WPA2 Encryption: yes


Em 25 de junho de 2011 14:49, Rafael Henrique da Silva Correia
raf...@abraseucodigo.com.br  escreveu:
   

Caro Rogério eu tenho uma placa idêntica a sua, porém não segui a Wiki,
apenas instalei dois pacotes diretamente do aptitude...

b43-fwcutter
firmware-b43-installer

Apenas instalando os dois minha placa nunca deu problemas, conecto em
qualquer rede wireless.
Testa ai! Abraço

OBS: Quando eu utilizava o comando

# ifconfig wlan0 up

Não era apresentado nenhum erro em um terminar virtual, porém quando eu
executava

# ifconfig wlan0 up

Diretamente no tty1 ou tty2 ele apresentava erros e mostrava uma página
dando mais informações sobre o b43-fwcutter... segui as orientações
apenas... é importante ressaltar que estou usando o Debian Squeeze.
 



--
Rafael Henrique da Silva Correia
http://abraseucodigo.blogspot.com

Administrador de Sistemas Linux
Certificado pela LPIC - 101
ID: LPI000160699


--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e123d00.7000...@gmail.com

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rogerio R. Silva]

Rafael,

Obrigado pela sugestão. Infelizmente, tive que viajar e não consegui
resolver o problema da wireless. Mas, excluindo o NetworkManager, como fica
o seu arquivo interfaces?

Abraço,

Rogério

Em 4 de julho de 2011 19:21, Rafael Henrique da Silva Correia 
raf...@abraseucodigo.com.br escreveu:

 Rogério, eu particularmente toda distribuição que uso a primeira coisa que
 eu faço é remover o Network Manager (Gnome)... eu particularmente ODEIO ele.

 Sem o Network Manager as coisas sempre funcionam.

 Abraço

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rafael Henrique da Silva Correia]

Somente isso...

/auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.0.10
netmask 255.255.255.0
gateway 192.168.0.1
network 192.168.0.0
broadcast 255.255.255.0
/
Porém caso você necessite poderá acrescentar a wlan0 também... da última 
vez que fiz isso (usando Lenny ainda) fiz desta forma abaixo...


auto wlan0
iface wlan0 inet dhcp
#iface wlan0 inet static
# address x.x.x.x
# netmask x.x.x.x
# gateway x.x.x.x
# broadcast x.x.x.x
# network x.x.x.x

pre-up wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -wB -D wext
post-down killall wpa_supplicant

Coloquei mais detalhes em meu blog neste link... 
http://abraseucodigo.blogspot.com/2008/04/configurando-cliente-na-rede-wireless.html


Espero que ajude!

Abraço!


Em 04-07-2011 20:26, Rogerio R. Silva escreveu:

Rafael,

Obrigado pela sugestão. Infelizmente, tive que viajar e não consegui 
resolver o problema da wireless. Mas, excluindo o NetworkManager, como 
fica o seu arquivo interfaces?


Abraço,

Rogério

Em 4 de julho de 2011 19:21, Rafael Henrique da Silva Correia 
raf...@abraseucodigo.com.br mailto:raf...@abraseucodigo.com.br 
escreveu:


Rogério, eu particularmente toda distribuição que uso a primeira
coisa que eu faço é remover o Network Manager (Gnome)... eu
particularmente ODEIO ele.

Sem o Network Manager as coisas sempre funcionam.

Abraço




--
Rafael Henrique da Silva Correia
http://abraseucodigo.blogspot.com

Administrador de Sistemas Linux
Certificado pela LPIC - 101
ID: LPI000160699

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Fabricio Cannini]

Em segunda-feira 04 julho 2011, às 20:26:34, Rogerio R. Silva escreveu:
 Rafael,
 
 Obrigado pela sugestão. Infelizmente, tive que viajar e não consegui
 resolver o problema da wireless. Mas, excluindo o NetworkManager, como fica
 o seu arquivo interfaces?

Eu exclui o network-manager e atualmente estou usando o wicd. Tem interfaces 
pra gnome, kde, e console. Desde então, sem problemas. A única coisa que falta 
na interface do kde é integração com o kwallet pra salvar/ler as senhas. Fora 
isso, não tenho do que reclamar.


--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107050010.07634.fcann...@gmail.com

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

Só para ter certeza, mas após vc associar sua placa ao Access Point, você
digitou:  dhclient ? porque se o IP for fornecido via DHCP é necessário este
passo antes do uso funcional da rede.




Abraços.

Em 25 de junho de 2011 19:29, Rogerio R. Silva rogerioro...@gmail.comescreveu:

 Rafael,

 Obrigado pela mensagem. Já tenho esses pacotes instalados. Minha
 interface está confusa. Wireless aparece desconectada (veja no fim da
 mensagem).

 Abs. - rogério

 # nm-tool

 NetworkManager Tool

 State: connected

 - Device: eth1
 -
  Type:  802.11 WiFi
  Driver:wl
  State: disconnected
  Default:   no
  HW Address:00:17:C4:03:9E:EF

  Capabilities:

  Wireless Properties
WEP Encryption:  yes
WPA Encryption:  yes
WPA2 Encryption: yes


 Em 25 de junho de 2011 14:49, Rafael Henrique da Silva Correia
 raf...@abraseucodigo.com.br escreveu:
  Caro Rogério eu tenho uma placa idêntica a sua, porém não segui a Wiki,
  apenas instalei dois pacotes diretamente do aptitude...
 
  b43-fwcutter
  firmware-b43-installer
 
  Apenas instalando os dois minha placa nunca deu problemas, conecto em
  qualquer rede wireless.
  Testa ai! Abraço
 
  OBS: Quando eu utilizava o comando
 
  # ifconfig wlan0 up
 
  Não era apresentado nenhum erro em um terminar virtual, porém quando eu
  executava
 
  # ifconfig wlan0 up
 
  Diretamente no tty1 ou tty2 ele apresentava erros e mostrava uma página
  dando mais informações sobre o b43-fwcutter... segui as orientações
  apenas... é importante ressaltar que estou usando o Debian Squeeze.


 --
 To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/banlktikwl4thy6v-d6h_zpysivgm5v...@mail.gmail.com

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[André Luiz Fraga Moreira]

Eu tenho uma placa Broadcom BCM4312 802.11b/g na minha máquina e apenas tive 
que habilitar o módulo b43 do kernel e instalar o pacote 
firmware-b43-lpphy-installer para fazer o wireless funcionar.

On Fri, 24 Jun 2011 12:56:29 -0300
Bruno Schmidt Marques cont...@brunomarques.com.br wrote:

 Tente desabilitar o gerenciamento de energia da placa com o comando 
 (execute como root):
 iwconfig eth1 power off
 ou
 iwconfig wlan0 power off
 
 Não esqueça de colocar os outros drivers na blacklist, como indicado no 
 tutorial.
 Obs.: O comando para desabilitar o gerenciamento de energia precisa ser 
 feito sempre que a máquina foi reiniciada. Coloque o comando no script 
 /etc/rc.local.
 
 Abraços!
 
 
 On 06/24/2011 12:51 PM, Rogerio R. Silva wrote:
  Caros,
 
  Usei o tutorial para configurar drive wl seguindo a dica do Bruno
  (http://wiki.debian.org/wl). Minha placa é Broadcom Corporation
  BCM4311 802.11b/g. A placa foi reconhecida e as redes sem fio são
  identificadas, mas ainda assim não consigo conexão. A autenticação
  sempre falha.
 
  Alguém sabe que detalhe de configuração está faltando para finalmente
  conseguir me conectar a redes sem fio do Debian Squeeze.
 
  Abs. - rogério
 
 
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/4e04b3ad.3050...@brunomarques.com.br
 


-- 
André Luiz Fraga Moreira andre4deb...@gmail.com
Matriculado no curso de Tecnologia em Redes de Computadores
Linux Professional Institute Certified - LPIC 1
twitter e identi.ca: @andreluizfm
linkedin: http://www.linkedin.com/pub/andre-luiz-fraga-moreira/11/3b8/b00


pgpURIOqixeEF.pgp
Description: PGP signature

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rafael Henrique da Silva Correia]

Caro Rogério eu tenho uma placa idêntica a sua, porém não segui a Wiki, 
apenas instalei dois pacotes diretamente do aptitude...


*b43-fwcutter
firmware-b43-installer
*
Apenas instalando os dois minha placa nunca deu problemas, conecto em 
qualquer rede wireless.

Testa ai! Abraço

*OBS: Quando eu utilizava o comando

# ifconfig wlan0 up

Não era apresentado nenhum erro em um terminar virtual, porém quando eu 
executava


# ifconfig wlan0 up

Diretamente no tty1 ou tty2 ele apresentava erros e mostrava uma página 
dando mais informações sobre o b43-fwcutter... segui as orientações 
apenas... é importante ressaltar que estou usando o Debian Squeeze.

*
Em 24-06-2011 12:51, Rogerio R. Silva escreveu:

Caros,

Usei o tutorial para configurar drive wl seguindo a dica do Bruno
(http://wiki.debian.org/wl). Minha placa é Broadcom Corporation
BCM4311 802.11b/g. A placa foi reconhecida e as redes sem fio são
identificadas, mas ainda assim não consigo conexão. A autenticação
sempre falha.

Alguém sabe que detalhe de configuração está faltando para finalmente
conseguir me conectar a redes sem fio do Debian Squeeze.

Abs. - rogério


   



--
Rafael Henrique da Silva Correia
http://abraseucodigo.blogspot.com

Administrador de Sistemas Linux
Certificado pela LPIC - 101
ID: LPI000160699

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rogerio R. Silva]

Rafael,

Obrigado pela mensagem. Já tenho esses pacotes instalados. Minha
interface está confusa. Wireless aparece desconectada (veja no fim da
mensagem).

Abs. - rogério

# nm-tool

NetworkManager Tool

State: connected

- Device: eth1 -
  Type:  802.11 WiFi
  Driver:wl
  State: disconnected
  Default:   no
  HW Address:00:17:C4:03:9E:EF

  Capabilities:

  Wireless Properties
WEP Encryption:  yes
WPA Encryption:  yes
WPA2 Encryption: yes


Em 25 de junho de 2011 14:49, Rafael Henrique da Silva Correia
raf...@abraseucodigo.com.br escreveu:
 Caro Rogério eu tenho uma placa idêntica a sua, porém não segui a Wiki,
 apenas instalei dois pacotes diretamente do aptitude...

 b43-fwcutter
 firmware-b43-installer

 Apenas instalando os dois minha placa nunca deu problemas, conecto em
 qualquer rede wireless.
 Testa ai! Abraço

 OBS: Quando eu utilizava o comando

 # ifconfig wlan0 up

 Não era apresentado nenhum erro em um terminar virtual, porém quando eu
 executava

 # ifconfig wlan0 up

 Diretamente no tty1 ou tty2 ele apresentava erros e mostrava uma página
 dando mais informações sobre o b43-fwcutter... segui as orientações
 apenas... é importante ressaltar que estou usando o Debian Squeeze.


--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTikWL4THY6V-D6h_=zpysivgm5v...@mail.gmail.com

Wireless - BCM 4311 802.11b/g/n não conecta

[Rogerio R. Silva]

Caros,

Usei o tutorial para configurar drive wl seguindo a dica do Bruno
(http://wiki.debian.org/wl). Minha placa é Broadcom Corporation
BCM4311 802.11b/g. A placa foi reconhecida e as redes sem fio são
identificadas, mas ainda assim não consigo conexão. A autenticação
sempre falha.

Alguém sabe que detalhe de configuração está faltando para finalmente
conseguir me conectar a redes sem fio do Debian Squeeze.

Abs. - rogério


--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=4tcU_hkq_d6Ri1Zr-2_SM=tc...@mail.gmail.com

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Bruno Schmidt Marques]

Tente desabilitar o gerenciamento de energia da placa com o comando 
(execute como root):

iwconfig eth1 power off
ou
iwconfig wlan0 power off

Não esqueça de colocar os outros drivers na blacklist, como indicado no 
tutorial.
Obs.: O comando para desabilitar o gerenciamento de energia precisa ser 
feito sempre que a máquina foi reiniciada. Coloque o comando no script 
/etc/rc.local.


Abraços!


On 06/24/2011 12:51 PM, Rogerio R. Silva wrote:

Caros,

Usei o tutorial para configurar drive wl seguindo a dica do Bruno
(http://wiki.debian.org/wl). Minha placa é Broadcom Corporation
BCM4311 802.11b/g. A placa foi reconhecida e as redes sem fio são
identificadas, mas ainda assim não consigo conexão. A autenticação
sempre falha.

Alguém sabe que detalhe de configuração está faltando para finalmente
conseguir me conectar a redes sem fio do Debian Squeeze.

Abs. - rogério





--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e04b3ad.3050...@brunomarques.com.br

Re: Wireless - BCM 4311 802.11b/g/n não conecta

[Rodolfo]

Você está colocando a chave correta ?

É a autenticação WEP ? WPA ? tem que verificar, eu só conseguía fazer a
conexão em WPA pelo pacote wpa-supplicant (nem lembro mais).




Abraços

Em 24 de junho de 2011 11:51, Rogerio R. Silva rogerioro...@gmail.comescreveu:

 Caros,

 Usei o tutorial para configurar drive wl seguindo a dica do Bruno
 (http://wiki.debian.org/wl). Minha placa é Broadcom Corporation
 BCM4311 802.11b/g. A placa foi reconhecida e as redes sem fio são
 identificadas, mas ainda assim não consigo conexão. A autenticação
 sempre falha.

 Alguém sabe que detalhe de configuração está faltando para finalmente
 conseguir me conectar a redes sem fio do Debian Squeeze.

 Abs. - rogério


 --
 To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/banlkti4tcu_hkq_d6ri1zr-2_smtc...@mail.gmail.com

Wireless - BCM 4313 802.11b/g/n

[Rogerio R. Silva]

Pessoal,

Desde ontem estou usando debian (estável) em um HP mini. Não consigo usar
wireless. Alguém tem experiência recente com ativar placas wireless no
debian com chip da broadcom? Já li algumas dicas, mas ainda não consegui.
Note que a BCM 4313 não é suportada (unsupported chip) e a alternativa é
Linux STA driver da Broadcom.

Abs. - rogério

Re: Wireless - BCM 4313 802.11b/g/n

[Bruno Schmidt Marques]

Siga exatamente esse tutorial que vai funcionar: http://wiki.debian.org/wl

PS.: Coloque o comando iwconfig eth1 power off no arquivo rc.local 
para ele ser executado sempre que ligar o notebook.


Abraços.

On 06/14/2011 09:33 PM, Rogerio R. Silva wrote:

Pessoal,

Desde ontem estou usando debian (estável) em um HP mini. Não consigo 
usar wireless. Alguém tem experiência recente com ativar placas 
wireless no debian com chip da broadcom? Já li algumas dicas, mas 
ainda não consegui. Note que a BCM 4313 não é suportada (unsupported 
chip) e a alternativa é Linux STA driver da Broadcom.


Abs. - rogério



--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4df7fe88.2000...@brunomarques.com.br

Re: Wireless - BCM 4313 802.11b/g/n

[Rogerio R. Silva]

Bruno,

Obrigado pela dica. Simples de executar e wireless funcionando.

Abs. - rogério

Em 14 de junho de 2011 21:36, Bruno Schmidt Marques 
cont...@brunomarques.com.br escreveu:

 Siga exatamente esse tutorial que vai funcionar: http://wiki.debian.org/wl

 PS.: Coloque o comando iwconfig eth1 power off no arquivo rc.local para
 ele ser executado sempre que ligar o notebook.

 Abraços.


 On 06/14/2011 09:33 PM, Rogerio R. Silva wrote:

 Pessoal,

 Desde ontem estou usando debian (estável) em um HP mini. Não consigo usar
 wireless. Alguém tem experiência recente com ativar placas wireless no
 debian com chip da broadcom? Já li algumas dicas, mas ainda não consegui.
 Note que a BCM 4313 não é suportada (unsupported chip) e a alternativa é
 Linux STA driver da Broadcom.

 Abs. - rogério

  http://lists.debian.org/4df7fe88.2000...@brunomarques.com.br

Re: Wireless - BCM 4313 802.11b/g/n

[Bruno Schmidt Marques]

Sim, é esse arquivo mesmo. Eu precisei utilizar esse comando com a minha 
placa, que também é Broadcom, mas é um modelo diferente.


O comando serve pra corrigir alguns bugs (não conecta a determinadas 
redes, ou fica instável, ou fica lento, mesmo com sinal alto). Como o 
modelo da placa é um pouco diferente, talvez para você não seja 
necessário. O ideal é que você teste o desempenho dela e só coloque o 
comando caso sinta necessidade. Essa issue está descrita na mesma 
página da Wiki que eu lhe enviei.


Abraços;

On 06/14/2011 11:03 PM, Rogerio R. Silva wrote:

Bruno,

Obrigado pela dica. Uma dúvida: o arquivo rc.local é o arquivo 
executável que está em /etc?


Abs. -rogério

Em 14 de junho de 2011 21:36, Bruno Schmidt Marques 
cont...@brunomarques.com.br mailto:cont...@brunomarques.com.br 
escreveu:


Siga exatamente esse tutorial que vai funcionar:
http://wiki.debian.org/wl

PS.: Coloque o comando iwconfig eth1 power off no arquivo
rc.local para ele ser executado sempre que ligar o notebook.

Abraços.


On 06/14/2011 09:33 PM, Rogerio R. Silva wrote:

Pessoal,

Desde ontem estou usando debian (estável) em um HP mini. Não
consigo usar wireless. Alguém tem experiência recente com
ativar placas wireless no debian com chip da broadcom? Já li
algumas dicas, mas ainda não consegui. Note que a BCM 4313 não
é suportada (unsupported chip) e a alternativa é Linux STA
driver da Broadcom.

Abs. - rogério



-- 
To UNSUBSCRIBE, email to

debian-user-portuguese-requ...@lists.debian.org
mailto:debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org mailto:listmas...@lists.debian.org
Archive: http://lists.debian.org/4df7fe88.2000...@brunomarques.com.br

Re: Recommendations for Mini PCIe 802.11b/g card?

[Andrei Popescu]

On Thu,21.May.09, 23:55:56, Mark Shroyer wrote:
 My laptop's Intel 3945BG card won't connect to half of the APs that I
 want it to--and even when it does work, I can only squeeze about 9 Mbps
 out of it in 802.11g mode.  So I'd like to replace it with something
 that works better with Debian Lenny.  Can anyone recommend a really
 rock-solid 802.11b/g Mini PCI Express card that has an equally solid
 driver in Lenny?
 
How can you tell another card would do better?

 (I've read the compatibility lists, but there's nothing like first-hand
 experience to say what works and what doesn't.  E.g., on paper my 3945BG
 should have been fine, but in practice it turned out to be problematic.)

I'm happy with my 4965 (AGN), but don't move a lot with my laptop.

 My wish list:
 
   * 802.11b/g support
 
   * WPA2
 
   * Compatibility with Lenny's 2.6.26 kernel
 
with additional firmware

   * Non-wholesale availability in the United States
 
   * 802.11n support a plus, but not required

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Recommendations for Mini PCIe 802.11b/g card?

[Mark Shroyer]

My laptop's Intel 3945BG card won't connect to half of the APs that I
want it to--and even when it does work, I can only squeeze about 9 Mbps
out of it in 802.11g mode.  So I'd like to replace it with something
that works better with Debian Lenny.  Can anyone recommend a really
rock-solid 802.11b/g Mini PCI Express card that has an equally solid
driver in Lenny?

(I've read the compatibility lists, but there's nothing like first-hand
experience to say what works and what doesn't.  E.g., on paper my 3945BG
should have been fine, but in practice it turned out to be problematic.)

My wish list:

  * 802.11b/g support

  * WPA2

  * Compatibility with Lenny's 2.6.26 kernel

  * Non-wholesale availability in the United States

  * 802.11n support a plus, but not required

Thanks for any advice!

-- 
Mark Shroyer
http://markshroyer.com/contact/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

cambiar tarjeta Atheros a 802.11b

[Marc Aymerich]

Saludos !
Estoy tratando de poner mis tarjetas Atheros a 11b, me interesa
hacerlo porque según las especificaciones con este estandar tienen más
sensibilidad. Entonces según la documentación de iwconfig la forma de
hacerlo seria:

# iwconfig ath0 modu 11b
Error for wireless request Set Modulation (8B2F) :
SET failed on device ath0 ; Operation not supported.


Pero como veis parece que el dispositivo no lo soporta. Por otro lado
como ya sabréis, iwconfig tampoco deja poner las tarjetas atheros (con
el controlador madwifi-ng) en modo monitor, para ello hay que usar
wlanconfig para crear un dispositivo en esa modalidad. Es por esto que
me pregunto si funcionaria usando wlanconfig (el man no dice nada) o
algo similar, me extraña mucho que el dispositivo no lo soporte.

Saludos y muchas gracias!!
Marc


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Problems with Atheros® 802.11b/g wire less-LAN in Debian Etch

[Chris Lale]

Fernando C. Estrada wrote:
 Hi!
 
 I'm new in Debian O.S., I used Ubuntu Feisty first in my Toshiba
 Satellite M100 SP1022 Laptop, and Ubuntu detect automatically my
 wireless, but in Debian Etch this not function. I used the madwifi
 directions and the situation is the same. Can anyone give me a tip to
 solve that?
 


Have a look at the NewbieDOC wiki [1]. The package you need is madwifi-source.

[1]
http://newbiedoc.berlios.de/wiki/How_to_set_up_a_wireless_network_card_using_drivers_from_Debian_packages

-- 
Chris.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Problems with Atheros® 802.11b/g wireless-LAN in Debian Etch

[Fernando C. Estrada]

I solved with the module-assistant instructions in
http://madwifi.org/wiki/UserDocs/Distro/Debian/MadWifi

Thanks for Your help!

 Have a look at the NewbieDOC wiki [1]. The package you need is 
 madwifi-source.
 
 [1]
 http://newbiedoc.berlios.de/wiki/How_to_set_up_a_wireless_network_card_using_drivers_from_Debian_packages
 
 -- 
 Chris.

 Have a look here:
 http://www.burghardt.pl/wiki/articles/installing_and_using_debian_on_acer_aspire_5102wlmi
 hth

-- 
Fernando C. Estrada - [EMAIL PROTECTED]
http://www.grupoesco.com.mx/fcestrada
PGP-Key: UID: 1024D/087C43F8 2007-06-04
Fingerprint: C67C F75B 42FF 7D5E 5E2B  7F16 3C20 C9C5 087C 43F8


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente

Problems with Atheros® 802.11b/g wireless-LAN in Debian Etch

[Fernando C. Estrada]

Hi!

I'm new in Debian O.S., I used Ubuntu Feisty first in my Toshiba
Satellite M100 SP1022 Laptop, and Ubuntu detect automatically my
wireless, but in Debian Etch this not function. I used the madwifi
directions and the situation is the same. Can anyone give me a tip to
solve that?

At the bottom, I paste the lspci -vvv exit.

Thanks!

02:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device
001c (rev 01)
Subsystem: Askey Computer Corp. Unknown device 7106
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d010 (64-bit, non-prefetchable)
[size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
Address:   Data: 
Capabilities: [60] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
ExtTag-
Device: Latency L0s 128ns, L1 2us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal-
Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1,
Port 0
Link: Latency L0s 512ns, L1 64us
Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
Vector table: BAR=0 offset=
PBA: BAR=0 offset=
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel

-- 
Fernando C. Estrada [EMAIL PROTECTED]
=
Don't speak unless your words are better than silence


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente

Re: Problems with Atheros ® 802.11b/g wireless-LAN in Debian Etch

[Gerard Robin]

On Mon, Jun 04, 2007 at 06:27:30PM -0500, Fernando C. Estrada wrote:

From: Fernando C. Estrada [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: Problems with Atheros® 802.11b/g wireless-LAN  in
Debian Etch
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on murphy.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 required=4.0 tests=FORGED_RCVD_HELO,

LDOSUBSCRIBER autolearn=ham version=3.1.4
Organization: Grupo ESCO
X-Mailer: Evolution 2.6.3

Hi!

I'm new in Debian O.S., I used Ubuntu Feisty first in my Toshiba
Satellite M100 SP1022 Laptop, and Ubuntu detect automatically my
wireless, but in Debian Etch this not function. I used the madwifi
directions and the situation is the same. Can anyone give me a tip to
solve that?



02:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device
001c (rev 01)

Have a look here:
http://www.burghardt.pl/wiki/articles/installing_and_using_debian_on_acer_aspire_5102wlmi
hth
--
Gérard

Re: wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[boube]

On Mon, Aug 21, 2006 at 08:23:53PM +0200, [EMAIL PROTECTED] wrote:
 Hola.
 
 Resulta que tengo el portatil (Compaq Presario R3000)  de un amigo que quiere
 que le instale una distribucion de linux, y olvidarse de sistemas operativos 
 de
 pago.

Me alegro :)

 Bueno, pues le he instalado Debian GNU/Linux (etch) todo funciona muy bien, 
 pero
 tengo una duda y un problema.
 
 La duda es:
 
 El touchpad funciona muy bien pero el desplazamiento del raton lo hace muy
 lento, si embargo si le conecto un raton usb este funciona perfectamente, y
 touchpad sigue funcionando igual de lento.
 ¿esto es normal?¿en caso de no serlo como puedo solucionarlo?¿se solucionaria 
 si
 quitase la configuracion del raton usb en el fichero xorg.conf?
 

Section InputDevice
Identifier Synaptics Touchpad
Driver synaptics
Option Protocol event
Option Device /dev/input/event0
Option Emulate3Buttons true
Option ZAxisMapping 4 5
Option SHMConfig on
Option HorizScrollDelta 100
Option VertScrollDelta 100
EndSection

A mi me funcion�o asi ;)

-- 
Coleccion de trucos y recetas sobre Debian -- trucosdebian.cjb.net

Por el bien de todos respetemos las normas de la lista:
http://wiki.debian.org/NormasLista


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[baloncesto]

Hola.

todavia estoy liao con el tema del wifi, como me aconsejasteis instale el kernel
2.6.17-2-686 el cual trae el driver para la tarjeta Broadcom.

me reconoce la tarjeta wifi como eth1, la configuro e intento levantala para
usarla, pero se cae en menos de un segundo.

me indicasteis que tenia que poner el firmware de la tarjeta, ¿pero donde lo
pongo?¿como lo configuro?

llevo todos estos dias buscando en google pero la verdad actualmente no me
aclaro y lo peor de todo es que le tengo que devolver el portatil a mi amigo
dentro de dos dias y si no consigo hacerle funcionar el wifi no usara linux y
eso que el chaval tiene muchas ganas, pero con las prisas ya no me aclaro busco
y busco y lo unico que me pasas es que me lio mas. 

Si me pudieseis ayudar configurar el wifi os lo agradeceria muchisimo y ademas
ganariamos varios usuarios mas (mi amigo, su hermano y los compañeros del 
trabajo)

Saludos y gracias



-
Este correo ha sido enviado via MarcaMail - http://www.marca.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[EMAIL PROTECTED] escribió:
 Hola.
 
 todavia estoy liao con el tema del wifi, como me aconsejasteis instale el 
 kernel
 2.6.17-2-686 el cual trae el driver para la tarjeta Broadcom.
 
 me reconoce la tarjeta wifi como eth1, la configuro e intento levantala para
 usarla, pero se cae en menos de un segundo.
 
 me indicasteis que tenia que poner el firmware de la tarjeta, ¿pero donde lo
 pongo?¿como lo configuro?
 
 llevo todos estos dias buscando en google pero la verdad actualmente no me
 aclaro y lo peor de todo es que le tengo que devolver el portatil a mi amigo
 dentro de dos dias y si no consigo hacerle funcionar el wifi no usara linux y
 eso que el chaval tiene muchas ganas, pero con las prisas ya no me aclaro 
 busco
 y busco y lo unico que me pasas es que me lio mas. 
 
 Si me pudieseis ayudar configurar el wifi os lo agradeceria muchisimo y ademas
 ganariamos varios usuarios mas (mi amigo, su hermano y los compañeros del 
 trabajo)
 
 Saludos y gracias

Disculpa, leíste esto [1] que te envíe en un correo anterior? Allí te
muestra todos los pasos necesarios, lo único que tienes que hacer es
cambiar los números del kernel del paquete que instalar por el que
necesitas.

[1] http://walter.unplug.org.ve/?p=8

- --

~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE7JeLOKCtW8rKsRgRAuDBAKDU6T7zTFQ2P3RH82VG1xo7TbnlwACgjkuq
lbmCRQfPRLnZAfCakYlL2aY=
=iTaC
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[baloncesto]

Hola.

Resulta que tengo el portatil (Compaq Presario R3000)  de un amigo que quiere
que le instale una distribucion de linux, y olvidarse de sistemas operativos de
pago.

Bueno, pues le he instalado Debian GNU/Linux (etch) todo funciona muy bien, pero
tengo una duda y un problema.

La duda es:

El touchpad funciona muy bien pero el desplazamiento del raton lo hace muy
lento, si embargo si le conecto un raton usb este funciona perfectamente, y
touchpad sigue funcionando igual de lento.
¿esto es normal?¿en caso de no serlo como puedo solucionarlo?¿se solucionaria si
quitase la configuracion del raton usb en el fichero xorg.conf?

El problema es:

Estoy intentado configurarle el wifi (Broadcam Corporation BCM4303  802.11b 
wireless LAN Controller)  pero no lo consigo, despues de buscar por google 
encontre esto y segui los pasos pero no consigo hacerlo funcionar.

Esto es lo que hago:

1- Lo primero que hago es tener localizados los drivers de Windows de la tarjeta
wireless. Lo tengo en el CD  de windwos bajo los nombres bcmwl5.inf y bcmwl5.sys
y los copio al disco duro.
2- instalo ndiswrapper-utils-1.1 – ndiswrapper-source - ndiswrapper-common
3- ahora instalo: ndiswrapper -i bcmwl5.inf
4- Luego ndiswrapper –l  y me dice : driver installed, hardware present
5- todo correcto, y hago: ndiswrapper –m
6- ahora reinicio, miro que la wireless existe iwconfig
7- y no me aparece y ademas pierdo la conexión a internet con la tarjeta de red.

¿como lo puedo solucionar? ¿como hago para tener configurado la tarjeta de red y
el wifi al mismo tiempo?

Saludos y perdon por la parrafada.

-
Este correo ha sido enviado via MarcaMail - http://www.marca.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[EMAIL PROTECTED] escribió:
 Hola.
 
 Resulta que tengo el portatil (Compaq Presario R3000)  de un amigo que quiere
 que le instale una distribucion de linux, y olvidarse de sistemas operativos 
 de
 pago.
 
 Bueno, pues le he instalado Debian GNU/Linux (etch) todo funciona muy bien, 
 pero
 tengo una duda y un problema.
 
 La duda es:
 
 El touchpad funciona muy bien pero el desplazamiento del raton lo hace muy
 lento, si embargo si le conecto un raton usb este funciona perfectamente, y
 touchpad sigue funcionando igual de lento.
 ¿esto es normal?¿en caso de no serlo como puedo solucionarlo?¿se solucionaria 
 si
 quitase la configuracion del raton usb en el fichero xorg.conf?
 
 El problema es:
 
 Estoy intentado configurarle el wifi (Broadcam Corporation BCM4303  802.11b 
 wireless LAN Controller)  pero no lo consigo, despues de buscar por google 
 encontre esto y segui los pasos pero no consigo hacerlo funcionar.
 
 Esto es lo que hago:
 
 1- Lo primero que hago es tener localizados los drivers de Windows de la 
 tarjeta
 wireless. Lo tengo en el CD  de windwos bajo los nombres bcmwl5.inf y 
 bcmwl5.sys
 y los copio al disco duro.
 2- instalo ndiswrapper-utils-1.1 ? ndiswrapper-source - ndiswrapper-common
 3- ahora instalo: ndiswrapper -i bcmwl5.inf
 4- Luego ndiswrapper ?l  y me dice : driver installed, hardware present
 5- todo correcto, y hago: ndiswrapper ?m
 6- ahora reinicio, miro que la wireless existe iwconfig
 7- y no me aparece y ademas pierdo la conexión a internet con la tarjeta de 
 red.
 
 ¿como lo puedo solucionar? ¿como hago para tener configurado la tarjeta de 
 red y
 el wifi al mismo tiempo?
 
 Saludos y perdon por la parrafada.
 
 -
 Este correo ha sido enviado via MarcaMail - http://www.marca.net/
 
 

No es necesario hacer eso. Léete esto para saber como instalar el driver
en Debian ;-)

- --

~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE6k+7OKCtW8rKsRgRAj9NAKC6yvMhJ2E+cbLWhuf0T/rerdjaCwCcDTe6
6wV9M5rBp057+pvvGCdZRgA=
=4WsF
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[Jose Arcangel Salazar Delgado]

El 21/08/06, [EMAIL PROTECTED][EMAIL PROTECTED] escribió:

Hola.

Resulta que tengo el portatil (Compaq Presario R3000)  de un amigo que quiere
que le instale una distribucion de linux, y olvidarse de sistemas operativos de
pago.

Bueno, pues le he instalado Debian GNU/Linux (etch) todo funciona muy bien, pero
tengo una duda y un problema.

La duda es:

El touchpad funciona muy bien pero el desplazamiento del raton lo hace muy
lento, si embargo si le conecto un raton usb este funciona perfectamente, y
touchpad sigue funcionando igual de lento.
¿esto es normal?¿en caso de no serlo como puedo solucionarlo?¿se solucionaria si
quitase la configuracion del raton usb en el fichero xorg.conf?

El problema es:

Estoy intentado configurarle el wifi (Broadcam Corporation BCM4303  802.11b
wireless LAN Controller)  pero no lo consigo, despues de buscar por google
encontre esto y segui los pasos pero no consigo hacerlo funcionar.

Esto es lo que hago:

1- Lo primero que hago es tener localizados los drivers de Windows de la tarjeta
wireless. Lo tengo en el CD  de windwos bajo los nombres bcmwl5.inf y bcmwl5.sys
y los copio al disco duro.
2- instalo ndiswrapper-utils-1.1 – ndiswrapper-source - ndiswrapper-common
3- ahora instalo: ndiswrapper -i bcmwl5.inf
4- Luego ndiswrapper –l  y me dice : driver installed, hardware present
5- todo correcto, y hago: ndiswrapper –m
6- ahora reinicio, miro que la wireless existe iwconfig
7- y no me aparece y ademas pierdo la conexión a internet con la tarjeta de red.

¿como lo puedo solucionar? ¿como hago para tener configurado la tarjeta de red y
el wifi al mismo tiempo?


Por internet hay varios manuales de como hacer andar esta tarjeta de
red. Lo mas facil es conseguir el nucleo 2.6 mas nuevo de kernel.org.
Ese kernel ya tiene soporte para la tarjeta broadcom, sin necesidad
ndiswrapper. El problema es que necesita el firmware que se puede
extraer del driver para windows de la broadcom.

En cuanto al touchpad, yo tambien he tenido problemas, a veces
responde y a veces no. Parece que el driver todavia no esta
completamente terminado. Así que tendras que esperar.

Si tu amigo no quiere complicarse mas la existencia, te recomendaria
que le echaras un vistaso a linspire/freespire. Me a sorprendido
mucho, ya que configuro todo el hardware de mi laptop sin problemas,
incluyendo la wireless broadcom (el touchpad sige dando lata). El
unico problema es que freespire es solo en ingles. Si quieres el
sistema en español te recomiendo que compres el linspire, total, esta
bastante económico y que evitas tantas broncas (espero que no se me
echen al cuello por hacer esta recomendación).


Saludos y perdon por la parrafada.

-
Este correo ha sido enviado via MarcaMail - http://www.marca.net/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wifi (Broadcam Corporation BCM4303 802.11b wireless LAN Controller)

[Jose Arcangel Salazar Delgado]

2006/8/21, Jose Arcangel Salazar Delgado [EMAIL PROTECTED]:

El 21/08/06, [EMAIL PROTECTED][EMAIL PROTECTED] escribió:
 Hola.

 Resulta que tengo el portatil (Compaq Presario R3000)  de un amigo que quiere
 que le instale una distribucion de linux, y olvidarse de sistemas operativos 
de
 pago.

 Bueno, pues le he instalado Debian GNU/Linux (etch) todo funciona muy bien, 
pero
 tengo una duda y un problema.

 La duda es:

 El touchpad funciona muy bien pero el desplazamiento del raton lo hace muy
 lento, si embargo si le conecto un raton usb este funciona perfectamente, y
 touchpad sigue funcionando igual de lento.
 ¿esto es normal?¿en caso de no serlo como puedo solucionarlo?¿se solucionaria 
si
 quitase la configuracion del raton usb en el fichero xorg.conf?

 El problema es:

 Estoy intentado configurarle el wifi (Broadcam Corporation BCM4303  802.11b
 wireless LAN Controller)  pero no lo consigo, despues de buscar por google
 encontre esto y segui los pasos pero no consigo hacerlo funcionar.

 Esto es lo que hago:

 1- Lo primero que hago es tener localizados los drivers de Windows de la 
tarjeta
 wireless. Lo tengo en el CD  de windwos bajo los nombres bcmwl5.inf y 
bcmwl5.sys
 y los copio al disco duro.
 2- instalo ndiswrapper-utils-1.1 – ndiswrapper-source - ndiswrapper-common
 3- ahora instalo: ndiswrapper -i bcmwl5.inf
 4- Luego ndiswrapper –l  y me dice : driver installed, hardware present
 5- todo correcto, y hago: ndiswrapper –m
 6- ahora reinicio, miro que la wireless existe iwconfig
 7- y no me aparece y ademas pierdo la conexión a internet con la tarjeta de 
red.

 ¿como lo puedo solucionar? ¿como hago para tener configurado la tarjeta de 
red y
 el wifi al mismo tiempo?

Por internet hay varios manuales de como hacer andar esta tarjeta de
red. Lo mas facil es conseguir el nucleo 2.6 mas nuevo de kernel.org.
Ese kernel ya tiene soporte para la tarjeta broadcom, sin necesidad
ndiswrapper. El problema es que necesita el firmware que se puede
extraer del driver para windows de la broadcom.

En cuanto al touchpad, yo tambien he tenido problemas, a veces
responde y a veces no. Parece que el driver todavia no esta
completamente terminado. Así que tendras que esperar.

Si tu amigo no quiere complicarse mas la existencia, te recomendaria
que le echaras un vistaso a linspire/freespire. Me a sorprendido
mucho, ya que configuro todo el hardware de mi laptop sin problemas,
incluyendo la wireless broadcom (el touchpad sige dando lata). El
unico problema es que freespire es solo en ingles. Si quieres el
sistema en español te recomiendo que compres el linspire, total, esta
bastante económico y que evitas tantas broncas (espero que no se me
echen al cuello por hacer esta recomendación).


Se me olvidaba, la dirección de la documentación del driver de
broadcom para linux es esta: http://bcm43xx.berlios.de/

 Saludos y perdon por la parrafada.

 -
 Este correo ha sido enviado via MarcaMail - http://www.marca.net/


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Orinoco 802.11b Weirdness!

[Gnu-Raiz]

I ran into a rather weird problem with my network card, this is a 
pcmcia card plugged into an old laptop. For some reason when I 
start, and stop the pcmcia service my card is no longer recognized. 
It seems that it is trying to connect, but I get no green light.

I even reboot and it is still the same problem, except I get 
a /lib/modules/sony module error that mentions the module is not 
loaded.  Before this the laptop had an uptime of 58 days, which I 
use to crunch RC5-72. Even before I had to reboot, the green led on 
the card was green buy no network activity.

I even did a fsck of the harddrive to see if something was not 
right. Everything came up clean.  It seems that I am having a 
gremlin, which might be hardware related. It seems that the card 
wants to come up I see activity on the card but for some reason 
it's not doing the job. The behavior is he same regardless of which 
pcmcia slot I use.

Has anyone had this sort of problem, it acts like a software problem 
but the fsck comes up clean. I did an apt-get update about a week 
ago everything was working fine. I am expecting a hardware failure 
on this notebook, as it getting around 5 years old, and is on 24/7 
but it works.  So if I have a component failure, like a harddrive I 
probably will not fix it as it would cost more for the component 
then the worth of the notebook.

Gnu_Raiz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Orinoco 802.11b Weirdness!

[Michael Marsh]

On 6/1/06, Gnu-Raiz [EMAIL PROTECTED] wrote:

I ran into a rather weird problem with my network card, this is a
pcmcia card plugged into an old laptop. For some reason when I
start, and stop the pcmcia service my card is no longer recognized.
It seems that it is trying to connect, but I get no green light.


Which release, kernel, and pcmcia modules package are you using?
There was a bug in the kernel-pcmcia-modules for 2.4.27 in sid back in
December (which has yet to be fixed, as far as I've seen).  That seems
to have made its way into etch.  My solution was to use pcmcia-modules
instead, but that started exhibiting flakiness similar to what you
describe (though not exactly the same).  The temporary solution (as
in, about a day later I'd see the same behavior again) was to stop the
pcmcia service and restart it.  Sometimes repeatedly.  The permanent
solution was to upgrade to 2.6.

--
Michael A. Marsh
http://www.umiacs.umd.edu/~mmarsh
http://mamarsh.blogspot.com


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Orinoco 802.11b Weirdness!

[Gnu-Raiz]

After a little more research, and trying a debian etch netinstall 
iso, which gave me the same results. I have concluded that my 
Orinoco 802.11b silver card has given up the ghost.

I had that card for over 5 years, got it in 2000, or 2001 when 
Wireless networking first started to get going. That card was a 
great little card, lasted all these years and various systems. 

Before giving up totally I tried it in a Windows notebook, which 
could not detect my network either. I was using a 2.6.12 kernel, 
like I said it was up for 58 days without any problems.

So I took apart the card, and I did smell a little ic burnt smell, 
after looking at the card some more everything looked good except 
that little ic.  I guess the heat finally killed it, since the card 
is so close to the cpu when it's inserted.  It was also used in a 
pvr, with poor air flow, along with a desktop for a few years also 
poor air flow out of the case.

sniff, sniff I will miss ya, nice little card!

I guess it will have to be ethernet only laptop. But that duron 800 
is doing good, I am surprised it lasted this long. On my wife's 
600m Dell it's on its third motherboard, I do not dare run RC5-72 
on it, because I believe that is what caused the other board 
failures.

Gnu_Raiz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

carte pci wifi peabird 802.11b/g

[Hervé T]

bonjour
il y a-t-il un module pour un noyau 2.4.6.x compatible avec un chipset
marvell libertas 88w8335
merci


-- 
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

PCMCIA Proxim Orinoco 802.11b PC Card Gold Wlan

[Sandro Frenzel]

hey leute!
hatte schonma dazu eine frage gestellt! 
als antwort kam
man iwconfig
jedoch wird die karte erst gar nicht erkannt!
KDE's Infocenter sagt unsupported card!
pcmcia tools sind installiert
modprobe oricono und modprobe oricoco_cs funktioniert auch, aber bringt
keine veränderung...immer noch unsupported card! mir wurde aber
versichert, dass die karte unter Linux laufen MUSS!

hier mal meine kernel-config
http://home.arcor.de/theskum/config-2.6.8

danke und tschüss
sandro


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: PCMCIA Proxim Orinoco 802.11b PC Card Gold Wlan

[Sandro Frenzel]

Am Mo, den 14.03.2005 schrieb Goran Ristic um 19:06:
 Hallo, Sandro! 
 
 | jedoch wird die karte erst gar nicht erkannt!
 | KDE's Infocenter sagt unsupported card!
 
 Mach mal cardinfo - ist die Karte aufgeführt?

da steht nur unsupported card 
markiert (oder schwarz hinterlegt) ist Ready
außerdem markiert sind cd, vcc und vpp, aber kA was das heißt!


 | pcmcia tools sind installiert
 
 Wireless-tools auch?

ja

 
 | modprobe oricono und modprobe oricoco_cs funktioniert auch, aber bringt
 | keine veränderung...immer noch unsupported card! mir wurde aber
 | versichert, dass die karte unter Linux laufen MUSS!
 
 Tut sie auch. Prima sogar.
 

naja hoffentlich auch irgendwann bei mir!


 | hier mal meine kernel-config
 | http://home.arcor.de/theskum/config-2.6.8
 
 Ich kann nix besonderes erkennen. - Hast Du testweise mal einen
 Debian-Kernel genommen? Oder ne Knoppix?
 Vielleicht ist Deine Karte auch kaputt?

karte funktioniert ohne probleme unter windumpf! LEDs und alles gehen
an!
Knoppix hab ich noch nicht getestet!
was meinst du mit debian kernel?

danke schonma!

gruß
sandro




-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: PCMCIA Proxim Orinoco 802.11b PC Card Gold Wlan

[Sandro Frenzel]

Am Mo, den 14.03.2005 schrieb Goran Ristic um 19:37:
 Hallo, Sandro! 
 
 Monday, der 14. March 2005
 
 |  Mach mal cardinfo - ist die Karte aufgeführt?
 | 
 | da steht nur unsupported card 
 | markiert (oder schwarz hinterlegt) ist Ready
 | außerdem markiert sind cd, vcc und vpp, aber kA was das heißt!
 
 Komisch...
 
 | naja hoffentlich auch irgendwann bei mir!
 
 Wir arbeiten dran. ;)
 
 | karte funktioniert ohne probleme unter windumpf! LEDs und alles gehen
 | an!
 | Knoppix hab ich noch nicht getestet!
 
 Versuch mal. Wenns damit klappt, kannst Du /etc/pcmcia vergleichen und evtl
 Unterschiede feststellen

und wenns damit net klappt? habs auch schonma mit fedora core und suse
9.1 versucht! immer erfolglos! jetzt bin ich bei debian! werde aber
aufgrund des komforts dabei bleiben ;)!
knoppix? ohje...ich hab doch nur isdn...naja werd ich morgen mal an der
uni ne saugsession machen ;)!

 
 | was meinst du mit debian kernel?
 
 apt-cache search kernel-image ;)

jah nix tolles für mich dabei. bin froh, dass ich gerade wieda
speedstepping zum laufen gebracht habe :)!

sonst noch irgendwelche ideen? ist doch zum heulen eh! kann es sein,
dass der card-slot nicht erkannt wird?


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

tarjeta wireless BCM4306 802.11b/g

[Daniel Gil]

alguien me pude ayudar a configurar la tarjeta
inalambrica BCM4306 802.11b/g (Broadcom), he tratado
con el ndiswrapper, me detecta la tarjeta en wlan0
pero no he podido escanear AP, no detecta el ESSID no
lo deja poner manualmente.

Gracias.

=
Daniel Felipe Gil Tobón
Coordinador Grupo GnuUCOnix
(Grupo de Investigaciones de Aplicaciones Gnu y Sistemas Unix)
Ingenieria de Sistemas - Universidad Católica de Oriente
Tel: 057+4+5312128
Web: http://danielgil.active.ws
e-mail: [EMAIL PROTECTED]





__
Yahoo! lanza su nueva tecnología de búsquedas
¿te atreves a comparar?
http://busquedas.yahoo.es

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Frederik Dannemare]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 08 July 2004 15:46, Frederik Dannemare wrote:
On Wednesday 07 July 2004 05:40, Rodney D. Myers wrote:
 I know this card is supported under Linux, and debian, but...

 What is involved in getting this card found/configured under Sarge?
 Specifically under the new net install cdrom?

 A lady friend is seriously considering letting me move her off of
 windos and onto debian. The hangup is this wifi card. I don't ant to
 spend all day trying to get this piece of hardware working, unless I
 absolutely have to.

 Don't know how the new installer handles wifi, but this is more or
 less what you should do to get the netgear ma311 working:

 apt-get install hostap-utils hostap-source wireless-tools hotplug
 echo alias wlan0 hostap_cs /etc/modutils/hostap 

Should have said _pci, not _cs. Thus:
echo alias wlan0 hostap_pci /etc/modutils/hostap

 update-modules

 Ensure that you have a wlan0 section in /etc/network/interfaces...

 iwconfig wlan0 essid foobar
 iwconfig wlan0 mode managed

Did you get it to work, btw?
- -- 
Frederik Dannemare | mailto:[EMAIL PROTECTED]
GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu
Key fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E B5A8
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+PqmLSX61ZxOtagRAtyTAJ4mPTDCKNtJlDRYTnEokhyuGw0/oACfe9pz
VekRbCpIvFxhTcGDMRRnJTk=
=HQg0
-END PGP SIGNATURE-

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Rodney D. Myers]

On Sat, 17 Jul 2004 12:08:35 +0200
Frederik Dannemare [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On Thursday 08 July 2004 15:46, Frederik Dannemare wrote:
 On Wednesday 07 July 2004 05:40, Rodney D. Myers wrote:
  I know this card is supported under Linux, and debian, but...
 
  What is involved in getting this card found/configured under Sarge?
  Specifically under the new net install cdrom?
 
  A lady friend is seriously considering letting me move her off of
  windos and onto debian. The hangup is this wifi card. I don't ant
 to spend all day trying to get this piece of hardware working,
 unless I absolutely have to.
 
  Don't know how the new installer handles wifi, but this is more or
  less what you should do to get the netgear ma311 working:
 
  apt-get install hostap-utils hostap-source wireless-tools hotplug
  echo alias wlan0 hostap_cs /etc/modutils/hostap 
 
 Should have said _pci, not _cs. Thus:
 echo alias wlan0 hostap_pci /etc/modutils/hostap
 
  update-modules
 
  Ensure that you have a wlan0 section in /etc/network/interfaces...
 
  iwconfig wlan0 essid foobar
  iwconfig wlan0 mode managed
 
 Did you get it to work, btw?
 - -- 
 Frederik Dannemare | mailto:[EMAIL PROTECTED]

Actually I missed the first reply to this message, not sure how or why..
I know have this email printed out so I can try.

Thanks

-- 
Rodney D. Myers [EMAIL PROTECTED] 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgplDS6SOMDVL.pgp
Description: PGP signature

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Frederik Dannemare]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Saturday 17 July 2004 16:40, Rodney D. Myers wrote:
 On Sat, 17 Jul 2004 12:08:35 +0200

 Frederik Dannemare [EMAIL PROTECTED] wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  On Thursday 08 July 2004 15:46, Frederik Dannemare wrote:
 
  On Wednesday 07 July 2004 05:40, Rodney D. Myers wrote:
   I know this card is supported under Linux, and debian, but...
  
   What is involved in getting this card found/configured under
   Sarge? Specifically under the new net install cdrom?
  
   A lady friend is seriously considering letting me move her off
   of windos and onto debian. The hangup is this wifi card. I don't
   ant
  
  to spend all day trying to get this piece of hardware working,
  unless I absolutely have to.
  
   Don't know how the new installer handles wifi, but this is more
   or less what you should do to get the netgear ma311 working:
  
   apt-get install hostap-utils hostap-source wireless-tools hotplug
   echo alias wlan0 hostap_cs /etc/modutils/hostap
 
  Should have said _pci, not _cs. Thus:
  echo alias wlan0 hostap_pci /etc/modutils/hostap
 
   update-modules
  
   Ensure that you have a wlan0 section in
   /etc/network/interfaces...
  
   iwconfig wlan0 essid foobar
   iwconfig wlan0 mode managed
 
  Did you get it to work, btw?
  - --
  Frederik Dannemare | mailto:[EMAIL PROTECTED]

 Actually I missed the first reply to this message, not sure how or
 why.. I know have this email printed out so I can try.

Oh, I also forgot to mention that you should, of course, compile the 
hostap kernel module. This can be done like this (after having 
apt-get'ed hostap-source and assuming that you compile your own kernels 
with kernel sources located in /usr/src/linux):

cd /usr/src
tar zxvf hostap-source.tar.gz
cd linux
fakeroot make-kpkg --append-to-version -foobar modules_image
sudo dpkg -i ../hostap-modules-2.6.5-foobar_0.1.2-2_i386.deb
depmod -a

Should you ever want to use the MA311 as an access point, have a look at 
my notes: http://sentinel.dk/cookbook/?Linux_wireless_access_point
- -- 
Frederik Dannemare | mailto:[EMAIL PROTECTED]
GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu
Key fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E B5A8
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+XJrLSX61ZxOtagRAiedAKCFK+fFW+MOH9IZ10MGJazHCjLqGACdGDWW
Hcv0EXB8Hm/PCXVmTW1kdpw=
=F1Df
-END PGP SIGNATURE-

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Rodney D. Myers]

On Sat, 17 Jul 2004 20:39:36 +0200
Frederik Dannemare [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On Saturday 17 July 2004 16:40, Rodney D. Myers wrote:
  On Sat, 17 Jul 2004 12:08:35 +0200
 
  Frederik Dannemare [EMAIL PROTECTED] wrote:
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
  
   On Thursday 08 July 2004 15:46, Frederik Dannemare wrote:
  
   On Wednesday 07 July 2004 05:40, Rodney D. Myers wrote:
I know this card is supported under Linux, and debian, but...
   
What is involved in getting this card found/configured under
Sarge? Specifically under the new net install cdrom?
   
A lady friend is seriously considering letting me move her off
of windos and onto debian. The hangup is this wifi card. I
   don't ant
   
   to spend all day trying to get this piece of hardware working,
   unless I absolutely have to.
   
Don't know how the new installer handles wifi, but this is more
or less what you should do to get the netgear ma311 working:
   
apt-get install hostap-utils hostap-source wireless-tools
hotplug echo alias wlan0 hostap_cs /etc/modutils/hostap
  
   Should have said _pci, not _cs. Thus:
   echo alias wlan0 hostap_pci /etc/modutils/hostap
  
update-modules
   
Ensure that you have a wlan0 section in
/etc/network/interfaces...
   
iwconfig wlan0 essid foobar
iwconfig wlan0 mode managed
  
   Did you get it to work, btw?
   - --
   Frederik Dannemare | mailto:[EMAIL PROTECTED]
 
  Actually I missed the first reply to this message, not sure how or
  why.. I know have this email printed out so I can try.
 
 Oh, I also forgot to mention that you should, of course, compile the 
 hostap kernel module. This can be done like this (after having 
 apt-get'ed hostap-source and assuming that you compile your own
 kernels with kernel sources located in /usr/src/linux):
 
 cd /usr/src
 tar zxvf hostap-source.tar.gz
 cd linux
 fakeroot make-kpkg --append-to-version -foobar modules_image
 sudo dpkg -i ../hostap-modules-2.6.5-foobar_0.1.2-2_i386.deb
 depmod -a
 
 Should you ever want to use the MA311 as an access point, have a look
 at my notes: http://sentinel.dk/cookbook/?Linux_wireless_access_point
 - -- 
 Frederik Dannemare | mailto:[EMAIL PROTECTED]

many thanks.. I have the kernel-source, and everything you mentioned
above.. Now to try and compile the source code, and get a functioning
kernel  wifi card.

-- 
Rodney D. Myers [EMAIL PROTECTED] 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgpcY3ED0naXq.pgp
Description: PGP signature

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Frederik Dannemare]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 07 July 2004 05:40, Rodney D. Myers wrote:
 I know this card is supported under Linux, and debian, but...

 What is involved in getting this card found/configured under Sarge?
 Specifically under the new net install cdrom?

 A lady friend is seriously considering letting me move her off of
 windos and onto debian. The hangup is this wifi card. I don't ant to
 spend all day trying to get this piece of hardware working, unless I
 absolutely have to.

Don't know how the new installer handles wifi, but this is more or less 
what you should do to get the netgear ma311 working:

apt-get install hostap-utils hostap-source wireless-tools hotplug
echo alias wlan0 hostap_cs /etc/modutils/hostap
update-modules

Ensure that you have a wlan0 section in /etc/network/interfaces...

iwconfig wlan0 essid foobar
iwconfig wlan0 mode managed
- -- 
Frederik Dannemare | mailto:[EMAIL PROTECTED]
GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu
Key fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E B5A8
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA7VBJLSX61ZxOtagRAjnKAKCGTWtKls6N/064IR1y2bwJguHRVQCfRNV0
h2tP7ENv9RCbVPKKwFwOLjY=
=Rhi7
-END PGP SIGNATURE-

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Rodney D. Myers]

On Tue, 6 Jul 2004 20:40:55 -0700
Rodney D. Myers [EMAIL PROTECTED] wrote:

 I know this card is supported under Linux, and debian, but...

Thanks to all.. I have all responses compiled into one document when the
card arrives.

-- 
Rodney D. Myers [EMAIL PROTECTED] 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgp1MwYgtrYPx.pgp
Description: PGP signature

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Derrick 'dman' Hudson]

On Tue, Jul 06, 2004 at 08:40:55PM -0700, Rodney D. Myers wrote:
| I know this card is supported under Linux, and debian, but...
| 
| What is involved in getting this card found/configured under Sarge?
| Specifically under the new net install cdrom?
| 
| A lady friend is seriously considering letting me move her off of windos
| and onto debian. The hangup is this wifi card. I don't ant to spend all
| day trying to get this piece of hardware working, unless I absolutely
| have to.

http://www.linux-wlan.org/docs/wlan_adapters.html.gz

That card is a prism2-based card.  That means you need either the
hostap or linux-wlan-ng drivers.  I don't know as much about hostap
because it doesn't support USB, which is the type of prism2 device I
have.  As for linux-wlan-ng, you either need a 2.4 kernel or you need
to build a 0.2.1 prelease version of the drivers.  Binary packages for
the 2.4 kernels are available in debian, and Vineet Kumar has created
an unofficial binary package for some 2.6 kernels (URL in the list
archives).

After loading the driver (module prism2_pci for linux-wlan-ng) you
need to configure the interface with the parameters for associating
with the access point.  This could be as simple as putting the
following in /etc/network/interfaces :
iface wlan0 inet dhcp
wireless_mode   managed
wireless_essid  foo
wireless_enc on
wlan_ng_key0 xx:xx:xx:xx:xx

I don't know if the net install cd will have that driver and the user
tools available.  The installation may just be easier with a cabled
network card and then set up the wireless afterwards.  Or you may find
it helpful to put the card in your machine first so you can figure out
how to make it work before doing the install in her machine.

HTH,
-D

-- 
...In the UNIX world, people tend to interpret `non-technical user' as
meaning someone who's only ever written one device driver.
--Daniel Pead
 
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Bijan Soleymani]

Rodney D. Myers [EMAIL PROTECTED] writes:

 I am finding enough sites, to think it should be fairly straight
 forward, though not sure about the net install portion.

For net install simply find the right module and load it (by
switching to another virtual terminal (usually alt-f2 and alt-f1 to
get back) or by choosing the go to shell option in the menu if there
is one), then proceed to the part where you configure the network
settings and the setup program should then have no problems. Note that
if the net install cdrom doesn't include the right module, you're kind
of out of luck :)

Bijan
-- 
Bijan Soleymani [EMAIL PROTECTED]
http://www.crasseux.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Rodney D. Myers]

I know this card is supported under Linux, and debian, but...

What is involved in getting this card found/configured under Sarge?
Specifically under the new net install cdrom?

A lady friend is seriously considering letting me move her off of windos
and onto debian. The hangup is this wifi card. I don't ant to spend all
day trying to get this piece of hardware working, unless I absolutely
have to.

Thanks

-- 
Rodney D. Myers [EMAIL PROTECTED] 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgpy2cW0akuTL.pgp
Description: PGP signature

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Bijan Soleymani]

Rodney D. Myers [EMAIL PROTECTED] writes:

 I know this card is supported under Linux, and debian, but...

 What is involved in getting this card found/configured under Sarge?
 Specifically under the new net install cdrom?

Basically use google or whatever to find out what module (driver) is
required and simply try out that module with:

$ modprobe modulename

if that works add modulename to /etc/modules

if not, remove it with:
$ modprobe -r modulename

and try again.

Bijan
-- 
Bijan Soleymani [EMAIL PROTECTED]
http://www.crasseux.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card

[Rodney D. Myers]

On Tue, 06 Jul 2004 23:51:04 -0400
Bijan Soleymani [EMAIL PROTECTED] wrote:

 Rodney D. Myers [EMAIL PROTECTED] writes:
 
  I know this card is supported under Linux, and debian, but...
 
  What is involved in getting this card found/configured under Sarge?
  Specifically under the new net install cdrom?
 
 Basically use google or whatever to find out what module (driver) is
 required and simply try out that module with:
 
 $ modprobe modulename
 
 if that works add modulename to /etc/modules
 
 if not, remove it with:
 $ modprobe -r modulename
 
 and try again.
 
 Bijan

Thanks.. I have been doing that.. The first wifi card I bought was not
found, couldn't get it working, which is why I was asking.

I am finding enough sites, to think it should be fairly straight
forward, though not sure about the net install portion.

-- 
Rodney D. Myers [EMAIL PROTECTED] 
Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgp5vrNW5rskF.pgp
Description: PGP signature

Re[2]: 802.11b ralink 2460 ?

[Marek]

Hello Marcin,

uruchomilem! :)

Saturday, June 19, 2004, 10:48:41 AM, you wrote:

MMB Karta wymaga PCI 2.2 (czy jakoś tak) - np. na PII na BX-ie - nie zadziała.

u mnie cweleron na 443BX (ecs p6bxt-a+) - dziala

MMB U mnie działa: sarge, 2.4.26 (nie z dystrybucji), ze sterownikiem: 
rt2400-1.1.1-b1.tar.gz z http://rt2400.sourceforge.net/ .

sarge, 2.4.26 z debianowego kernel-source-2.4.26

MMB Zauważyłem, że karta przyjmuje parametry iwconfig przez chwilę po 
załadowaniu modułu. Pomogło przeniesienie  
/etc/network/if-pre-up.d/wireless-tools do /etc/network/if-up.d/ lub można 
napisać
MMB odpowiedni skrypt.

driver odpalilem, z reki skonfigurowalem i dziala, zaraz bede ustawial
configi.

Dziekuje za pomoc i pozdrawiam - na liste - bo moze ktos tez zwatpil w
uruchomienie tej karty ;)

-- 
Best regards,
 Marekmailto:[EMAIL PROTECTED]

Re: 802.11b ralink 2460 ?

[Marcin M. Bis]

On Sat, 19 Jun 2004 02:38:30 +0200
Marek [EMAIL PROTECTED] wrote:

 Hello debian-user-polish,
 
   chce toto uruchomic, ale ono nie chce ;) znalazlem pakiety driverow
   rt2400-source_1.1.0-4_all.deb i rt2400-utility_1.1.0-4_i386.deb i
   inne, podobne w zawartosci, ale wszystkie zachowuja sie tak samo -
   kompilacja ok, ale przy ladowaniu modulu zachowuja sie tak, jakby
   karty nie bylo w systemie

Karta wymaga PCI 2.2 (czy jakoś tak) - np. na PII na BX-ie - nie zadziała.

U mnie działa: sarge, 2.4.26 (nie z dystrybucji), ze sterownikiem: 
rt2400-1.1.1-b1.tar.gz z http://rt2400.sourceforge.net/ .
Zauważyłem, że karta przyjmuje parametry iwconfig przez chwilę po załadowaniu 
modułu. Pomogło przeniesienie  /etc/network/if-pre-up.d/wireless-tools do 
/etc/network/if-up.d/ lub można napisać odpowiedni skrypt.

Mój plik interfaces wygląda mniej więcej tak (z pamięci):
auto ra0
iface ra0 inet static
(...)
wireless_essid moja_siec
wireless_rate 11M
wireless_mode Ad-Hoc
wireless_nick komp1
wireless_channel 6

Nie mam w tej chwili dostępu do tego komputera, jeśli będziesz potrzebował 
dokładniejszych informacji - zgłoś się za tydzień na priv.

Powodzenia!

-- 
 Marcin Bis [jabber:[EMAIL PROTECTED]


-- 
 Marcin Bis [jabber:[EMAIL PROTECTED] [GG:1774976]

802.11b ralink 2460 ?

[Marek]

Hello debian-user-polish,

  chce toto uruchomic, ale ono nie chce ;) znalazlem pakiety driverow
  rt2400-source_1.1.0-4_all.deb i rt2400-utility_1.1.0-4_i386.deb i
  inne, podobne w zawartosci, ale wszystkie zachowuja sie tak samo -
  kompilacja ok, ale przy ladowaniu modulu zachowuja sie tak, jakby
  karty nie bylo w systemie

  we windzie 98 karta spisuje sie bardzo ladnie po sciagnieciu
  sterownika v.2.0, ale winda nie nadaj sie na router
  
  jesli komus udalo sie ta karte uruchomic prosze o wskazowki..

-- 
Best regards,
 Marek  mailto:[EMAIL PROTECTED]

Re: Troubleshooting 802.11b wireless

[Jeffrey L. Taylor]

Quoting Jonathan Brandmeyer [EMAIL PROTECTED]:
 On Wed, 2004-03-10 at 00:48, Joe Carey wrote:
  It's the wrong driver.  You're using the driver for an 
  Agere/Proxim/Orinoco card, i.e. Hermes on a card built with the 
  Prism2.5 chipset.  You probably want the linux-wlan-ng drivers.
  
  Check these links:
  http://packages.debian.org/testing/admin/linux-wlan-ng
  http://www.linux-wlan.com/linux-wlan/
  
  Have fun!
  
  joe
 
 That doesn't quite make sense to me.  If the driver is wrong than why
 does it report that it detected an Orinoco/Prism2 PCI device and then
 gets information from it like the MAC address and firmware revision? 
 This fellow http://members.iinet.net.au/~mtriggs/wireless.html got his
 card to work with the orinoco_pci driver.
 
 Unfortunately, the latest release of linux-wlan-ng doesn't work with
 2.6, although that support is coming down the pipe in the next release
 according to the CHANGELOG at linux-wlan.com.  I attempted to build the
 module from their source tree for 0.2.1-pre20, but it expects a file
 [kernel-source-root]/.tmp_versions to be present, which is not shipped
 with kernel-headers-2.6.3-1-686 (or its dependency).  So, without
 actually building my own kernel, what would it take to get a kernel
 source tree that matched the one used to build the stock Debian kernel
 verbatim?
 

Generally you have to do at least copy the .config file and do a make
dep after installing the kernel sources before you have anything
usable by other packages.

HTH,
  Jeffrey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Troubleshooting 802.11b wireless

[Jonathan Brandmeyer]

On Wed, 2004-03-10 at 03:59, Jeffrey L. Taylor wrote:
 Quoting Jonathan Brandmeyer [EMAIL PROTECTED]:
  On Wed, 2004-03-10 at 00:48, Joe Carey wrote:
   It's the wrong driver.  You're using the driver for an 
   Agere/Proxim/Orinoco card, i.e. Hermes on a card built with the 
   Prism2.5 chipset.  You probably want the linux-wlan-ng drivers.
   
   Check these links:
   http://packages.debian.org/testing/admin/linux-wlan-ng
   http://www.linux-wlan.com/linux-wlan/
   
   Have fun!
   
   joe
  
  That doesn't quite make sense to me.  If the driver is wrong than why
  does it report that it detected an Orinoco/Prism2 PCI device and then
  gets information from it like the MAC address and firmware revision? 
  This fellow http://members.iinet.net.au/~mtriggs/wireless.html got his
  card to work with the orinoco_pci driver.
  
  Unfortunately, the latest release of linux-wlan-ng doesn't work with
  2.6, although that support is coming down the pipe in the next release
  according to the CHANGELOG at linux-wlan.com.  I attempted to build the
  module from their source tree for 0.2.1-pre20, but it expects a file
  [kernel-source-root]/.tmp_versions to be present, which is not shipped
  with kernel-headers-2.6.3-1-686 (or its dependency).  So, without
  actually building my own kernel, what would it take to get a kernel
  source tree that matched the one used to build the stock Debian kernel
  verbatim?
  
 
 Generally you have to do at least copy the .config file and do a make
 dep after installing the kernel sources before you have anything
 usable by other packages.
 
 HTH,
   Jeffrey

Well, I still needed to manually create the .tmp_versions directory,
since building an additional kernel didn't create it.  However,
linux-wlan-ng is giving me fits as well.  modprobing the driver worked
OK, but nothing after that works.  I attempted to follow the directions
in the README file for the source, but it borked up my system so badly
that I had to reboot in order for my existing wired lan interface to
work again.   

First, I tried to use the Debian ifup/ifdown method of configuring the
thing.  Adding alias wlan0 prism2_pci to /etc/modules/linux-wlan-ng
doesn't lead to on-demand module loading, instead I had to add it to
/etc/modutils.d/linux-wlan-ng and rerun update-modules.  That wasn't
enough to get ifup to work, here is the relevant stanza from
/etc/network/interfaces:

iface wlan0 inet dhcp
wireless_essid 203cfr
wireless_mode managed
wireless_enc on
wlan_ng_key0 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx

ifup wlan0 reports this:
Error for wireless request Set ESSID (8B1A) :
SET failed on device wlan0 ; Operation not supported.
Error for wireless request Set Encode (8B2A) :
SET failed on device wlan0 ; Operation not supported.
Error for wireless request Set Mode (8B06) :
SET failed on device wlan0 ; Operation not supported.
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
 
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
 
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/wlan0/00:09:5b:67:95:0d
Sending on   LPF/wlan0/00:09:5b:67:95:0d
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database.
 
Sleeping.
 
So, next I tried to make the upstream method of using an init script
to do the job.  After editing /etc/wlan/wlan.conf (attached) and
creating an /etc/wlan/wlancfg-203cfr (attached) file from
wlancfg-DEFAULT and running the supplied `rc.wlan start`, This is all
that happens:
Starting WLAN Devices:

And nothing else.

So, any help is still appreciated.

-Jonathan

#===USER MIB SETTINGS=
# You can add the assignments for various MIB items
#  of your choosing to this variable, separated by 
#  whitespace.  The wlan-ng script will then set each one.
# Just uncomment the variable and set the assignments 
#  the way you want them.

#USER_MIBS=p2CnfRoamingMode=1 p2CnfShortPreamble=mixed

#===WEP===
# [Dis/En]able WEP.  Settings only matter if PrivacyInvoked is true
lnxreq_hostWEPEncrypt=true  # true|false
lnxreq_hostWEPDecrypt=true  # true|false
dot11PrivacyInvoked=true# true|false
dot11WEPDefaultKeyID=0  # 

Re: Troubleshooting 802.11b wireless

[Jeffrey L. Taylor]

Quoting Jonathan Brandmeyer [EMAIL PROTECTED]:
[snip]
 ifup wlan0 reports this:
 Error for wireless request Set ESSID (8B1A) :
 SET failed on device wlan0 ; Operation not supported.
 Error for wireless request Set Encode (8B2A) :
 SET failed on device wlan0 ; Operation not supported.
 Error for wireless request Set Mode (8B06) :
 SET failed on device wlan0 ; Operation not supported.

It sounds like you have a driver that does not support the wireless
tools extensions.  Sigh.  Unfortunately, the Debian way requires them.

You should be able to pass the parameters thru the module interface,
e.g.,

modprobe prism2 essid=ESSID mode=Managed

Note, I said SHOULD.  I have not actually made this work.  I had a
laptop that ran Slackware and it took downloading and building the
drivers, but I did get it working.  When I switched to Debian, I ran
into the problem you are seeing.  I decided it was easier to but a
PCMCIA Ethernet NIC.  (This was plain 802.11, not 802.11a/b/g and was
only useful with the same brand on all computers.  It saved pulling
Cat5 cable, but eventually was too slow, ~1Mbps real thruput.)

I suspect that you can find another driver that does support the
wireless extensions.

Jeffrey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Troubleshooting 802.11b wireless

[Jonathan Brandmeyer]

I'm trying to get a brand new Prism 2.5 based 802.11b wireless ethernet
card to work with Linux 2.6.3 (Netgear MA311) on Sid.

The wireless-tools package installed.

When I insert the required drivers into the kernel (orinoco_pci,
orinoco, and hermes), I get these messages:

orinoco.c 0.13e (David Gibson [EMAIL PROTECTED] and others)
orinoco_pci.c 0.13e (David Gibson [EMAIL PROTECTED]  Jean
Tourrilhes [EMAIL PROTECTED])
PCI: Found IRQ 11 for device :02:0b.0
Detected Orinoco/Prism2 PCI device at :02:0b.0, mem:0xF47FF000 to
0xF47F - 0xe080d000, irq:11
Reset done..7orinoco_lock() called with hw_unavailable (dev=d2f03800)
.7orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 17 more times)

Clear Reset.7orinoco_lock() called with hw_unavailable
(dev=d2f03800)
.7orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 20-something more times)
.;
pci_cor : reg = 0x0 - 75286D9 - 75284E5
orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 13 more times)

eth1: Station identity 001f:0006:0001:0003
eth1: Looks like an Intersil firmware version 1.3.6
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:09:5B:67:95:0D
eth1: Station name Prism  I
orinoco_lock() called with hw_unavailable (dev=d2f03800)
eth1: ready


With /etc/network/interfaces set up thus:
iface eth1 inet dhcp
name Wireless Ethernet LAN Card
wireless_essid 203cfr
wireless_mode managed
wireless_channel 6
wireless_ap auto

ifup eth1 gives me this output:
Error for wireless request Set Frequency (8B04) :
SET failed on device eth1 ; Operation not supported.
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth1/00:09:5b:67:95:0d
Sending on   LPF/eth1/00:09:5b:67:95:0d
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database.

Sleeping.

After rebooting and trying again, I got several of this error instead:
hermes @ MEM 0xe090a000: Error -16 issuing command.
hermes @ MEM 0xe090a000: Error -16 issuing command.
hermes @ MEM 0xe090a000: Error -16 issuing command.
which repeated until I ran `modprobe -r orinoco_pci`

So, can anyone help me debug this problem?  The card works fine under
Windows XP on the same machine.

Thanks,
Jonathan Brandmeyer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Troubleshooting 802.11b wireless

[Joe Carey]

It's the wrong driver.  You're using the driver for an 
Agere/Proxim/Orinoco card, i.e. Hermes on a card built with the 
Prism2.5 chipset.  You probably want the linux-wlan-ng drivers.

Check these links:
http://packages.debian.org/testing/admin/linux-wlan-ng
http://www.linux-wlan.com/linux-wlan/
Have fun!

joe

Jonathan Brandmeyer wrote:

I'm trying to get a brand new Prism 2.5 based 802.11b wireless ethernet
card to work with Linux 2.6.3 (Netgear MA311) on Sid.
The wireless-tools package installed.

When I insert the required drivers into the kernel (orinoco_pci,
orinoco, and hermes), I get these messages:
orinoco.c 0.13e (David Gibson [EMAIL PROTECTED] and others)
orinoco_pci.c 0.13e (David Gibson [EMAIL PROTECTED]  Jean
Tourrilhes [EMAIL PROTECTED])
PCI: Found IRQ 11 for device :02:0b.0
Detected Orinoco/Prism2 PCI device at :02:0b.0, mem:0xF47FF000 to
0xF47F - 0xe080d000, irq:11
Reset done..7orinoco_lock() called with hw_unavailable (dev=d2f03800)
.7orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 17 more times)
Clear Reset.7orinoco_lock() called with hw_unavailable
(dev=d2f03800)
.7orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 20-something more times)
.;
pci_cor : reg = 0x0 - 75286D9 - 75284E5
orinoco_lock() called with hw_unavailable (dev=d2f03800)
(repeated 13 more times)
eth1: Station identity 001f:0006:0001:0003
eth1: Looks like an Intersil firmware version 1.3.6
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:09:5B:67:95:0D
eth1: Station name Prism  I
orinoco_lock() called with hw_unavailable (dev=d2f03800)
eth1: ready
With /etc/network/interfaces set up thus:
iface eth1 inet dhcp
name Wireless Ethernet LAN Card
   wireless_essid 203cfr
   wireless_mode managed
   wireless_channel 6
   wireless_ap auto
ifup eth1 gives me this output:
Error for wireless request Set Frequency (8B04) :
   SET failed on device eth1 ; Operation not supported.
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth1/00:09:5b:67:95:0d
Sending on   LPF/eth1/00:09:5b:67:95:0d
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database.
Sleeping.

After rebooting and trying again, I got several of this error instead:
hermes @ MEM 0xe090a000: Error -16 issuing command.
hermes @ MEM 0xe090a000: Error -16 issuing command.
hermes @ MEM 0xe090a000: Error -16 issuing command.
which repeated until I ran `modprobe -r orinoco_pci`
So, can anyone help me debug this problem?  The card works fine under
Windows XP on the same machine.
Thanks,
Jonathan Brandmeyer
 



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Troubleshooting 802.11b wireless

[Jonathan Brandmeyer]

On Wed, 2004-03-10 at 00:48, Joe Carey wrote:
 It's the wrong driver.  You're using the driver for an 
 Agere/Proxim/Orinoco card, i.e. Hermes on a card built with the 
 Prism2.5 chipset.  You probably want the linux-wlan-ng drivers.
 
 Check these links:
 http://packages.debian.org/testing/admin/linux-wlan-ng
 http://www.linux-wlan.com/linux-wlan/
 
 Have fun!
 
 joe

That doesn't quite make sense to me.  If the driver is wrong than why
does it report that it detected an Orinoco/Prism2 PCI device and then
gets information from it like the MAC address and firmware revision? 
This fellow http://members.iinet.net.au/~mtriggs/wireless.html got his
card to work with the orinoco_pci driver.

Unfortunately, the latest release of linux-wlan-ng doesn't work with
2.6, although that support is coming down the pipe in the next release
according to the CHANGELOG at linux-wlan.com.  I attempted to build the
module from their source tree for 0.2.1-pre20, but it expects a file
[kernel-source-root]/.tmp_versions to be present, which is not shipped
with kernel-headers-2.6.3-1-686 (or its dependency).  So, without
actually building my own kernel, what would it take to get a kernel
source tree that matched the one used to build the stock Debian kernel
verbatim?

Thanks,
Jonathan Brandmeyer

 Jonathan Brandmeyer wrote:
 
 I'm trying to get a brand new Prism 2.5 based 802.11b wireless ethernet
 card to work with Linux 2.6.3 (Netgear MA311) on Sid.
 
 The wireless-tools package installed.
 
 When I insert the required drivers into the kernel (orinoco_pci,
 orinoco, and hermes), I get these messages:
 
 orinoco.c 0.13e (David Gibson [EMAIL PROTECTED] and others)
 orinoco_pci.c 0.13e (David Gibson [EMAIL PROTECTED]  Jean
 Tourrilhes [EMAIL PROTECTED])
 PCI: Found IRQ 11 for device :02:0b.0
 Detected Orinoco/Prism2 PCI device at :02:0b.0, mem:0xF47FF000 to
 0xF47F - 0xe080d000, irq:11
 Reset done..7orinoco_lock() called with hw_unavailable (dev=d2f03800)
 .7orinoco_lock() called with hw_unavailable (dev=d2f03800)
 (repeated 17 more times)
 
 Clear Reset.7orinoco_lock() called with hw_unavailable
 (dev=d2f03800)
 .7orinoco_lock() called with hw_unavailable (dev=d2f03800)
 (repeated 20-something more times)
 .;
 pci_cor : reg = 0x0 - 75286D9 - 75284E5
 orinoco_lock() called with hw_unavailable (dev=d2f03800)
 (repeated 13 more times)
 
 eth1: Station identity 001f:0006:0001:0003
 eth1: Looks like an Intersil firmware version 1.3.6
 eth1: Ad-hoc demo mode supported
 eth1: IEEE standard IBSS ad-hoc mode supported
 eth1: WEP supported, 104-bit key
 eth1: MAC address 00:09:5B:67:95:0D
 eth1: Station name Prism  I
 orinoco_lock() called with hw_unavailable (dev=d2f03800)
 eth1: ready
 
 
 With /etc/network/interfaces set up thus:
 iface eth1 inet dhcp
 name Wireless Ethernet LAN Card
 wireless_essid 203cfr
 wireless_mode managed
 wireless_channel 6
 wireless_ap auto
 
 ifup eth1 gives me this output:
 Error for wireless request Set Frequency (8B04) :
 SET failed on device eth1 ; Operation not supported.
 Internet Software Consortium DHCP Client 2.0pl5
 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
 All rights reserved.
 
 Please contribute if you find this software useful.
 For info, please visit http://www.isc.org/dhcp-contrib.html
 
 sit0: unknown hardware address type 776
 sit0: unknown hardware address type 776
 Listening on LPF/eth1/00:09:5b:67:95:0d
 Sending on   LPF/eth1/00:09:5b:67:95:0d
 Sending on   Socket/fallback/fallback-net
 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
 
 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
 No DHCPOFFERS received.
 No working leases in persistent database.
 
 Sleeping.
 
 After rebooting and trying again, I got several of this error instead:
 hermes @ MEM 0xe090a000: Error -16 issuing command.
 hermes @ MEM 0xe090a000: Error -16 issuing command.
 hermes @ MEM 0xe090a000: Error -16 issuing command.
 which repeated until I ran `modprobe -r orinoco_pci`
 
 So, can anyone help me debug this problem?  The card works fine under
 Windows XP on the same machine.
 
 Thanks,
 Jonathan Brandmeyer
 
 
   
 
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Wireless Laptop 802.11b - SUCCESS! (finally)

[M. Kirchhoff]

I am absolutely stunned that I finally got this working.  Honestly, I've
been hacking here and there, trying to get my laptop to work with my
3COM AirConnect 3CRWE737A 802.11b PCMCIA card for about a month and a
half, with no luck and lots of frustration.  I know the
chipsets/firmware in these cards changes sometimes without the name of
the product changing, which can cause problems when referencing various
Howtos.  

The solution that finally worked was the simplest.  By using the stock
orinoco_cs driver in the bf24 Debian kernel, I'm now able to get an ip
address from my WAP, albeit without WEP.  The orinoco_cs driver
apparently comes from turning on support for HERMES chipset/pcmcia cards
during Debian installion (or in kernel recompiling, I imagine). Many of
the howtos for this particular NIC suggested recompiling the kernel,
using third-party drivers, and all kinds of .conf file hacking.  All of
those might very well lead to a better connection and better security
support, but I'm relatively new to *nix and it was all a bit over my head.

After turning on the HERMES/orinoco_cs stuff, it was simply a matter of
apt-getting the wireless-tools package and running iwconfig eth0--it
found my WAP automatically and assigned an ip.  

At any rate, I'm overjoyed to have it working.  If anyone has a similar
card and similar frustrations, feel free to shoot me an email with
questions. Further, if anyone with this model got things working
*better*, let me know!  I know WEP is easily cracked, but I would still
like that false sense of security!

Thanks much to the debian-user archives for many bits of knowledge!!!

Sincerely,
M. Kirchhoff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Ad-hoc 802.11b internet access

[Mark Roach]

On Sun, 2003-06-08 at 22:36, Bret Comstock Waldow wrote:
[...]
 I want to get access to the internet from the PDA.  I've been reading
 some on the net - but the sources are mixed, of mixed antiquity, and I
 don't know enough to discern what to listen to, whose configuration file
 surgery to attempt, etc.  I don't just want to thrash around, but
 there's too much out there I don't know the relevance of to want to try
 to chew through it all.  Some talk about distros and boot-up sequences I
 don't have, and there are other differences I can't evaluate.
 
 Has anyone done something like this?  It's called Internet Connection
 Sharing on Windows.  Some sources call it NAT, some invoke ipmasq, or
 masquerading.

Lots of people do this (including me :)). The one thing you will have to
do no matter what is set the laptop's address as the PDA's default
gateway.

Here's a quick-n-dirty way to get it working:

(as root)
modprobe ipchains
ipchains -P forward DENY
ipchains -A forward -i eth0 -j MASQ
echo 1  /proc/sys/net/ipv4/ip_forward

and then, when you are ready to set up a real firewall, I would
recommend shorewall, it has lots of good documentation and is very
flexible but simple.

-Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]