7:30 p.m.
I'm trying to get the built-in wireless working on a new Compag
v5000z. lspci claims the following:
06:02.0 Network controller: Broadcom Corporation Dell Wireless 1470 DualBand WLAN (rev
02)
Subsystem: Hewlett-Packard Company Unknown device 1358
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
I'd first assumed it was a BCM43xx card and followed the instructions
on bcm43xx-fwcutter to get the card going. I never see an eth1 (or
other new network device) show up under "ifconfig -a".
Short of ripping the laptop apart and putting the wireless chips under
a magnifying glass, how do I find out what chip this really is? (Or
is "1470" the chip number? I had assumed it was a the mini-pci card's
model number.)
-wolfgang
7:40 p.m.
I assume the computer has a working cable NIC...so why not ditch the hassle
of configuring your wireless card and just buy a wireless bridge? They're
very affordable and much more easy to setup. ;-) :-)
On 3/30/06, Wolfgang S. Rupprecht <
wolfgang+gnus200603(a)dailyplanet.dontspam.wsrcc.com> wrote:
I'm trying to get the built-in wireless working on a new Compag
v5000z. lspci claims the following:
06:02.0 Network controller: Broadcom Corporation Dell Wireless 1470
DualBand WLAN (rev 02)
Subsystem: Hewlett-Packard Company Unknown device 1358
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
I'd first assumed it was a BCM43xx card and followed the instructions
on bcm43xx-fwcutter to get the card going. I never see an eth1 (or
other new network device) show up under "ifconfig -a".
Short of ripping the laptop apart and putting the wireless chips under
a magnifying glass, how do I find out what chip this really is? (Or
is "1470" the chip number? I had assumed it was a the mini-pci card's
model number.)
-wolfgang
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
2:50 p.m.
"Hex Star" <hexstar(a)gmail.com> writes:
I assume the computer has a working cable NIC...so why not ditch
the
hassle of configuring your wireless card and just buy a wireless
bridge? They're very affordable and much more easy to setup. ;-) :-)
That is an interesting idea. I've seen it done in hotels where they
want to offer wired connections but are too cheap to run real cat-5.
In my case, I was really thinking more of the wireless from when I'm
not at home (like in a coffee shop, or on a trip). (I already have
cat-5 runs to all the rooms in the house, so getting a connection when
at home isn't a problem.)
-wolfgang
7:40 p.m.
On Thu, 30 Mar 2006, Wolfgang S. Rupprecht wrote:
I'm trying to get the built-in wireless working on a new Compag
v5000z. lspci claims the following:
06:02.0 Network controller: Broadcom Corporation Dell Wireless 1470 DualBand WLAN (rev
02)
Subsystem: Hewlett-Packard Company Unknown device 1358
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
I'd first assumed it was a BCM43xx card and followed the instructions
on bcm43xx-fwcutter to get the card going. I never see an eth1 (or
other new network device) show up under "ifconfig -a".
Short of ripping the laptop apart and putting the wireless chips under
a magnifying glass, how do I find out what chip this really is? (Or
is "1470" the chip number? I had assumed it was a the mini-pci card's
model number.)
It's probably a broadcom 4318...
joelja
-wolfgang
--
--------------------------------------------------------------------------
Joel Jaeggli Unix Consulting joelja(a)darkwing.uoregon.edu
GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
2:14 p.m.
Joel Jaeggli <joelja(a)darkwing.uoregon.edu> writes:
On Thu, 30 Mar 2006, Wolfgang S. Rupprecht wrote:
>
> 06:02.0 Network controller: Broadcom Corporation Dell Wireless 1470 DualBand WLAN
(rev 02)
> Subsystem: Hewlett-Packard Company Unknown device 1358
> Flags: bus master, fast devsel, latency 64, IRQ 10
> Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
It's probably a broadcom 4318...
Yup. I just opened up the laptop and the chip says:
BCM4318EKFBG
HS0601P20
766529N1
I guess I have to wait till the code for the 4318 gets sorted out.
-wolfgang
2:47 p.m.
--- "Wolfgang S. Rupprecht"
<wolfgang+gnus200603(a)dailyplanet.dontspam.wsrcc.com>
wrote:
Joel Jaeggli <joelja(a)darkwing.uoregon.edu> writes:
> On Thu, 30 Mar 2006, Wolfgang S. Rupprecht wrote:
>>
>> 06:02.0 Network controller: Broadcom
Corporation Dell Wireless 1470 DualBand WLAN (rev
02)
>> Subsystem: Hewlett-Packard Company
Unknown device 1358
>> Flags: bus master, fast devsel,
latency 64, IRQ 10
>> Memory at c0204000 (32-bit,
non-prefetchable) [size=8K]
>
> It's probably a broadcom 4318...
Yup. I just opened up the laptop and the chip says:
BCM4318EKFBG
HS0601P20
766529N1
I guess I have to wait till the code for the 4318
gets sorted out.
-wolfgang
This was recently posted on the bcm43xx list:
----------------------------------------
Hi...
ehm... i use 4318 with 2.6.16, and absolutly no real
problem
(sometimes i must bring eth down, up, down to put in
monitor mode, but
hey it's work!).
I read this ml to stay updated to release and news,
but if i can help
ask without problem.
The card works for Florian and me, so seem like the
drivers is good,
but some config broken it....
Luca
----------------------------------------
You may need to build the bcm43xx driver from more
recent source. maybe even use their fwcutter util to
pull the softmac info out of the windows driver.
╔══╗
║ j≈
╚══╝
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
3:06 p.m.
Josh Coffman <josh_coffman(a)yahoo.com> writes:
ehm... i use 4318 with 2.6.16, and absolutly no real
problem
(sometimes i must bring eth down, up, down to put in
monitor mode, but
hey it's work!).
I read this ml to stay updated to release and news,
but if i can help
ask without problem.
The card works for Florian and me, so seem like the
drivers is good,
but some config broken it....
In my case I don't see any eth1 show up, so I can't even
ifconfig down/up the interface.
You may need to build the bcm43xx driver from more
recent source. maybe even use their fwcutter util to
pull the softmac info out of the windows driver.
While the laptop came with all the ms-windows stuff (and the wireless
works under ms-windows), I don't know enough to even find the broadcom
firmware. Heck, I dont' even know what they call their find(1)
utility (or if they even have one). Any hints what the pathname of
the firmware file would be or how I go about finding it? The
bcm43xx-fwcutter README files assume the reader understands more about
ms-windows than I do.
To the firmware I used the url's at the bottom of the one README.
fwcutter didn't like some of the files claiming they were too old and
it couldn't extract some firmware element. The firmware from
http://openwrt.inf.fh-brs.de/~nbd/wl_apsta.o seemed new enough that
fwcutter got all it needed, but perhaps that firmware wasn't quite
right either.
-wolfgang
4:14 p.m.
--- "Wolfgang S. Rupprecht"
<wolfgang+gnus200603(a)dailyplanet.dontspam.wsrcc.com>
wrote:
Josh Coffman <josh_coffman(a)yahoo.com> writes:
> ehm... i use 4318 with 2.6.16, and absolutly no
real
> problem
> (sometimes i must bring eth down, up, down to put
in
> monitor mode, but
> hey it's work!).
> I read this ml to stay updated to release and
news,
> but if i can help
> ask without problem.
> The card works for Florian and me, so seem like
the
> drivers is good,
> but some config broken it....
In my case I don't see any eth1 show up, so I can't
even
ifconfig down/up the interface.
I tried the bcm43xx driver last night. The device name
I saw was wlan0.
> You may need to build the bcm43xx driver from more
> recent source. maybe even use their fwcutter util
to
> pull the softmac info out of the windows driver.
While the laptop came with all the ms-windows stuff
(and the wireless
works under ms-windows), I don't know enough to even
find the broadcom
firmware. Heck, I dont' even know what they call
their find(1)
utility (or if they even have one). Any hints what
the pathname of
the firmware file would be or how I go about finding
it?
Under windows, use the windows key + f and it should
bring up the file search util. In case you don't know
which key is the "windows", it is usually just to the
right of the left CTRL on a typical 101 keyboard.
It's been a while since I messed with it but the files
your looking for should be in the %windows%\system32
path (assuming it not win64) That path usually is
c:\windows\system32 or c:\winnt\system32
For my broadcom, the file starts with bcmwl5. You'll
want the .inf and the .sys(? .dll) files. I had them
on a driver cd.
You may want to look here:
http://www.linuxant.com/driverloader/drivers.php
In scanning it wuickly, I didn't see the bcm4318
driver. But you can probably google it.
The
bcm43xx-fwcutter README files assume the reader
understands more about
ms-windows than I do.
To the firmware I used the url's at the bottom of
the one README.
fwcutter didn't like some of the files claiming they
were too old and
it couldn't extract some firmware element. The
firmware from
http://openwrt.inf.fh-brs.de/~nbd/wl_apsta.o seemed
new enough that
fwcutter got all it needed, but perhaps that
firmware wasn't quite
right either.
-wolfgang
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
╔══╗
║ j≈
╚══╝
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
6662
days inactive
6662
days old
7 comments
4 participants
participants (4)
-
Hex Star -
Joel Jaeggli -
Josh Coffman -
Wolfgang S. Rupprecht