Hi all,
The last few days I've been trying to get b43 to work on my WRT54GL
wlan-router. The reason I've been trying this is because I want to use the
device as a bridge between the local university wlan and my own local
network. However, because the network I'm trying to connect to is part of
Maurits Dijkstra wrote:
Hi all,
The last few days I've been trying to get b43 to work on my WRT54GL
wlan-router. The reason I've been trying this is because I want to use the
device as a bridge between the local university wlan and my own local
network. However, because the network I'm
Larry Finger wrote:
I think your system doesn't use PCI, so this probably won't work,
but you should be able to implement something similar. Once you
have a dump, you should be able to find the MAC addresses of the
wireless and ethernet interfaces.
IIRC the WRTs don't have a sprom, instead
I have a Linksys PCMCIA N card which IDs as a BCM43XG, but unfortunately
is model 0x4329 rev 01, which is not on the hardware list as a supported
device.
Is this something that requires RE effort... and am I tainted because
I've looked at the Linux driver (reverse tainted) or am I clear
Ehud Gavron wrote:
I have a Linksys PCMCIA N card which IDs as a BCM43XG, but unfortunately
is model 0x4329 rev 01, which is not on the hardware list as a supported
device.
Is this something that requires RE effort... and am I tainted because
I've looked at the Linux driver (reverse
On Monday 29 January 2007 04:18, Larry Finger wrote:
Although we have not made any progress on the transmit strength problem with
4318, 4311 and 4312
That's not true. We are doing progress, but we didn't solve the
issue completely, yet. It's a complicated issue. ;)
--
Greetings Michael.
Michael Buesch wrote:
On Monday 29 January 2007 04:18, Larry Finger wrote:
Although we have not made any progress on the transmit strength problem with
4318, 4311 and 4312
That's not true. We are doing progress, but we didn't solve the
issue completely, yet. It's a complicated issue. ;)
I
Hello. I am the owner of a card (a LinkSys Wireless-G WPC54GS (ver.2))
which has a 4318 chip:
kernel: bcm43xx: Chip ID 0x4318, rev 0x2kernel: bcm43xx: Number of cores: 4
kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243
Jim McCloskey wrote:
Hello. I am the owner of a card (a LinkSys Wireless-G WPC54GS (ver.2))
which has a 4318 chip:
kernel: bcm43xx: Chip ID 0x4318, rev 0x2kernel: bcm43xx: Number of cores: 4
kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
kernel: bcm43xx: Core 1: ID 0x812
Vincent Danjean wrote:
When building this system (with a cross compiler : WRT54G is mips),
we can choose to compile the bcm43xx module (the SoftMac one). The
sources for this module are not patched (ie they are the same as the
ones in 2.6.17 official linux kernel). However, I want to use my
Hi,
I have a linksys WRT54G on which I install OpenWRT (the development
version, ie Kamikaze). This linux system comes with a 2.6.17 kernel
(not the linus kernel but one patched to support some of the WRT54G
hardware).
When building this system (with a cross compiler : WRT54G is mips),
we
On Monday 13 November 2006 23:45, Vincent Danjean wrote:
Index: dscape-ieee80211/src/wireless-dev/ssb/ssb.c
===
--- dscape-ieee80211.orig/src/wireless-dev/ssb/ssb.c 2006-11-13
02:00:02.0 +0100
+++
On Thu, Aug 10, 2006 at 12:02:04AM +1000, Ben Klein wrote:
I have just bought a Linksys WPC54G adapter based on research indicating it
was a Broadcom chipset that works with ndiswrapper. I have not tried
ndiswrapper yet, as I found out about bcm43xx in the 2.6.17 kernel after
confirming
:04AM +1000, Ben Klein wrote: I have just bought a Linksys WPC54G adapter based on research indicating it
was a Broadcom chipset that works with ndiswrapper. I have not tried ndiswrapper yet, as I found out about bcm43xx in the 2.6.17 kernel after confirming it is a Broadcom. I'm sending this email
I have just bought a Linksys WPC54G adapter based on research indicating it was a Broadcom chipset that works with ndiswrapper. I have not tried ndiswrapper yet, as I found out about bcm43xx in the 2.6.17 kernel after confirming it is a Broadcom.
I'm sending this email to show the product/vendor
Ben Klein wrote:
I have just bought a Linksys WPC54G adapter based on research indicating
it was a Broadcom chipset that works with ndiswrapper. I have not tried
ndiswrapper yet, as I found out about bcm43xx in the 2.6.17 kernel after
confirming it is a Broadcom.
I'm sending this email
Hello.
I'm trying to get a LinkSys Wireless G WPC54GS card to work, using the bcm43xx
driver. This card has the Broadcom 4318 chipset.
The kernel here is a hand-compiled version of 2.6.17. I have version 28-1 of
wireless-tools from Debian unstable, and udev 0.093 also from Debian unstable
Hi,
I couldn't find the Linksys WPC54G-EU v3 in the list of bcm43xx devices
at http://openfacts.berlios.de/index-en.phtml?title=Bcm43xxDevices ,
but I'd like to report that it works just fine with linux-2.6.17-rc1.
Here's the output from lspci:
:02:00.0 Network controller: Broadcom
On Tue, 2006-02-28 at 19:52 +0100, Khiraly wrote:
The driver say nothing if you specify wrong essid (or the AP is not
present), there is no message in dmesg. If the associated was
successfull is a message in dmesg:
Actually, there are some things reported when you listen to the right
events
On Tue, 2006-02-28 at 19:52 +0100, Khiraly wrote:
The driver is perfect to normal usage, even kismet works fine, but its
not good for penetration testing.
Well. For that you really need a 'raw' sending mode which we haven't
written yet. Search the archives -- I've detailed that before.
Gregory Gulik wrote:
I was surprised (pleasantly at first) to find there was a bcm43xx driver
included in the Fedora Core 5 Test 3 release. Anyway, I found the
firmware and I think I installed it correctly.
However, when the device gets started up it seems to think the radio is
turned off
Ok, I tried that and still
nothing:
[EMAIL PROTECTED] ~]# ifconfig eth1 up
[EMAIL PROTECTED] ~]# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"Auto" Nickname:"dell8100"
Mode:Managed Frequency=2.437 GHz Access Point: Invalid
Bit Rate=54 Mb/s Tx-Power=2346 dBm
RTS thr:off Fragment thr:off
Here you go. I ejected and
re-inserted the card to get a full picture of what's happening.
Feb 28 12:07:54 dell8100 kernel: pccard: CardBus card inserted into
slot 1
Feb 28 12:07:54 dell8100 kernel: PCI: Enabling device :0d:00.0
( - 0002)
Feb 28 12:07:54 dell8100 kernel: ACPI: PCI
2006. 02. 28, kedd keltezéssel 11.46-kor Gregory Gulik ezt írta:
Ok, I tried that and still nothing:
Try first without dhclient (you can use dhclient after to
I tipically do the following:
ifconfig eth2 down; rmmod bcm43xx; modprobe bcm43xx; ifconfig eth2 up
192.168.1.15; iwconfig eth2 essid
Grrr, it worked to set the essid manually.
The static IP worked, then running the dhcp client after that also worked.
Why is that?
does this driver need the essid specified? I never had to do that with
other wifi drivers.
Khiraly wrote:
Try first without dhclient (you can use dhclient
Khiraly wrote:
Ok. Here is thoughts what I experienced (softmac version).
The driver says nothing if it was disassociated from the AP, so to
specify manually the essid its always a good idea.
The driver say nothing if you specify wrong essid (or the AP is not
present), there is no message in
Ok...apparently my previous wpa_supplicant config was interfering. Just
for kicks I decided to edit wpa_supplicant.conf, and simply
commented-out everything that I had in there to make ndiswrapper work
with my WPA-PSK settings (I thought I had tried this before with no
results). Voila (after
On Thu, 2006-02-09 at 23:40 -0500, Mike Leahy wrote:
Feb 9 23:29:35 localhost firmware_helper[3127]: Loading of
/lib/firmware/bcm43xx_microcode4.fw for bcm43xx driver failed: No such
file or directory
no comment.
johannes
signature.asc
Description: This is a digitally signed message
On Sat, 11 Feb 2006 06:02:25 -0500
Mike Leahy [EMAIL PROTECTED] wrote:
Any other suggestions?
Move closer to your AP. Note that this driver has still some issues with TX
power.
--
ciao
st3
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any obvious
effect either.
The set_xmitpower section is still a TODO. The interface accepts the input but
then throws it away.
Larry
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any obvious
effect either.
The set_xmitpower section is still a TODO.
On Saturday 11 February 2006 17:55, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any
On Saturday 11 February 2006 18:46, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:55, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem
turn to the
default linksys-brand drivers? I guess I'll give that a try next...
Here's what I get with ifconfig:
eth1 Link encap:Ethernet HWaddr 00:06:25:40:4C:53
inet6 addr: fe80::206:25ff:fe40:4c53/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
On Wed, Feb 08, 2006 at 03:18:24PM +0100, Michael Buesch wrote:
[...]
Well, I did not publish the URL on the homepage, because it is not
really needed for everyone to clone my repository.
Currently, there are all-in-one snapshots available.
I am going to setup a script for softmac standalone
On Wednesday 08 February 2006 17:47, you wrote:
On Wed, Feb 08, 2006 at 03:18:24PM +0100, Michael Buesch wrote:
[...]
Well, I did not publish the URL on the homepage, because it is not
really needed for everyone to clone my repository.
Currently, there are all-in-one snapshots available.
On Wednesday 08 February 2006 20:10, you wrote:
The new standalone isn't working for me. Compilation and syntax
errors all over the place - mostly near the error handling gotos.
Attached is the results of a compilation attempt.
I'm going to give a look at see if I can figure out the issue.
On Wed, Feb 08, 2006 at 08:16:30PM +0100, Michael Buesch wrote:
[...]
I am not sure what you are doing, but it compiles for me. ;)
Are you trying on a recent kernel with softmac installed?
Yes, my build setup is ok.
The issue was KBUILD_MODNAME is defined without quotes. I did a patch
Scott Robinson wrote:
On Tue, Feb 07, 2006 at 12:50:08PM -0600, Larry Finger wrote:
[...]
As you are obviously in the FC test program, could you inquire where they
are downloading softmac and bcm43xx code?
[...]
That's a good braod question. There have been a lot of patches flying
back on
On Tue, 2006-02-07 at 12:50 -0600, Larry Finger wrote:
I wonder where Fedora is getting their source. The iwconfig errors you
report were fixed about a month ago. On my system, WPA started working
on Jan. 12 and that didn't work until most of the IOCTL links used by
iwconfig were working.
On Tue, 2006-02-07 at 15:31 -0600, Larry Finger wrote:
I'm not quite sure where the patches are. The subversion tree is a lot
newer than the FC sources seem to be, but not current. Michael Buesch
has a private git tree, but I not comfortable giving you that URL. If
he is willing to publish it,
Michael Buesch wrote:
On Monday 06 February 2006 08:22, Mike Leahy wrote:
Thanks for the tip.
I eventually abandoned bcm43xx in favour of ndiswrapper. Maybe bcm43xx
driver works for some people...but never for me. I've been running
FC5T2 (and subsequent updates) - every kernel that gets
Larry,
Thanks for letting me know - I'll keep a lookout for it in the updates
with FC5. I'm well aware of how lucky I am to have this working - I did
notice that 4k stack issue, but I also hacked around with my
configuration quite a bit until at some point it just seemed to start
working with
Hello list,
I'm just wondering if anyone knows where I can find some instructions or
How-to documentation - I've got the same WPC54G pcmcia card on my
laptop, with FC5 test 2 fully updated. I can get as far as getting some
basic info on the card from iwconfig (which reported a Broadcom 4306
as
On Friday 27 January 2006 04:17, Mike Leahy wrote:
I'd be delighted to know how anyone else may have got this card working
(whether or not the LED works is secondary given my current problem)...
I use SWScanner http://swscanner.org/. It doesn't seem to support WPA
though.
Tim
On Sunday 05 February 2006 18:13, [EMAIL PROTECTED] wrote:
Do you also add support for linksys technology for improving signalstrenght
by using two or more antennas ?
I personally use a debian system with a Linksys WMP54G card.
Could you tell me if , and if yes , at what time
46 matches
Mail list logo
