6:15 p.m.
i've been searching everwhere and can't find if FC4 (or 5) supports this card.
has anyone any experience with this?
thank you so much
--
jack wallen, jr.
get those pantz off
www.monkeypantz.net
7 p.m.
jack wallen wrote:
i've been searching everwhere and can't find if FC4 (or 5)
supports this card.
has anyone any experience with this?
What does lspci show?
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
7:59 p.m.
On Sunday January 22 2006 1:00 am, John Summerfied wrote:
jack wallen wrote:
> i've been searching everwhere and can't find if FC4 (or 5) supports this
> card. has anyone any experience with this?
What does lspci show?
not sure yet. this is for an install on my girlfriend's daughter's computer.
she wants to use linux but her computer has to use a wireless network card
(the one i'm asking about). can't afford to buy a new card so i was hoping to
find out if this card would work in FC4. i've searched but haven't found
anything saying yeah or nay yet.
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
--
jack wallen, jr.
get those pantz off
www.monkeypantz.net
9:21 p.m.
jack wallen wrote:
On Sunday January 22 2006 1:00 am, John Summerfied wrote:
>jack wallen wrote:
>
>>i've been searching everwhere and can't find if FC4 (or 5) supports this
>>card. has anyone any experience with this?
>
>What does lspci show?
not sure yet. this is for an install on my girlfriend's daughter's computer.
she wants to use linux but her computer has to use a wireless network card
(the one i'm asking about). can't afford to buy a new card so i was hoping to
find out if this card would work in FC4. i've searched but haven't found
anything saying yeah or nay yet.
We can't tell you until we know what's in the card. You could boot
Knoppix to find out, or in Windows:
Start/Settings/Network Connections
Choose the wireless card, right-click, properties
Choose General/Configure
It well tell you stuff about the card. Windows says of my card,
"Orinocco" (the brand) and "Agere Systems" (the chipset manufacturer,
way more important then the brand) abd Driver/Driver details says "Lucent."
The printing on the outside of the card says "Wavelan," more recent ones
say "Orinocco."
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
10:48 a.m.
had to go into the driver settings to find anything out. looks like the driver
was made by broadcom - so i'm assuming it's a broadcom chip. of course that
means there's no support with linux right?
On Sunday January 22 2006 3:21 am, John Summerfied wrote:
jack wallen wrote:
> On Sunday January 22 2006 1:00 am, John Summerfied wrote:
>>jack wallen wrote:
>>>i've been searching everwhere and can't find if FC4 (or 5) supports
this
>>>card. has anyone any experience with this?
>>
>>What does lspci show?
>
> not sure yet. this is for an install on my girlfriend's daughter's
> computer. she wants to use linux but her computer has to use a wireless
> network card (the one i'm asking about). can't afford to buy a new card
> so i was hoping to find out if this card would work in FC4. i've searched
> but haven't found anything saying yeah or nay yet.
We can't tell you until we know what's in the card. You could boot
Knoppix to find out, or in Windows:
Start/Settings/Network Connections
Choose the wireless card, right-click, properties
Choose General/Configure
It well tell you stuff about the card. Windows says of my card,
"Orinocco" (the brand) and "Agere Systems" (the chipset
manufacturer,
way more important then the brand) abd Driver/Driver details says "Lucent."
The printing on the outside of the card says "Wavelan," more recent ones
say "Orinocco."
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
--
jack wallen, jr.
get those pantz off
www.monkeypantz.net
11:16 a.m.
On 1/22/06, jack wallen <jlwallen(a)monkeypantz.net> wrote:
had to go into the driver settings to find anything out. looks like
the driver
was made by broadcom - so i'm assuming it's a broadcom chip. of course that
means there's no support with linux right?
Well, there is a open source project that may help you:
http://bcm43xx.berlios.de/
You may try and see if it works for you.
Regards,
Fabio
On 1/22/06, jack wallen <jlwallen(a)monkeypantz.net> wrote:
had to go into the driver settings to find anything out. looks like
the driver
was made by broadcom - so i'm assuming it's a broadcom chip. of course that
means there's no support with linux right?
>
> On Sunday January 22 2006 3:21 am, John Summerfied wrote:
>
> > jack wallen wrote:
> > > On Sunday January 22 2006 1:00 am, John Summerfied wrote:
> > >>jack wallen wrote:
> > >>>i've been searching everwhere and can't find if FC4 (or 5)
supports this
> > >>>card. has anyone any experience with this?
> > >>
> > >>What does lspci show?
> > >
> > > not sure yet. this is for an install on my girlfriend's daughter's
> > > computer. she wants to use linux but her computer has to use a wireless
> > > network card (the one i'm asking about). can't afford to buy a new
card
> > > so i was hoping to find out if this card would work in FC4. i've
searched
> > > but haven't found anything saying yeah or nay yet.
> >
> > We can't tell you until we know what's in the card. You could boot
> > Knoppix to find out, or in Windows:
> > Start/Settings/Network Connections
> > Choose the wireless card, right-click, properties
> > Choose General/Configure
> > It well tell you stuff about the card. Windows says of my card,
> > "Orinocco" (the brand) and "Agere Systems" (the chipset
manufacturer,
> > way more important then the brand) abd Driver/Driver details says
"Lucent."
> >
> > The printing on the outside of the card says "Wavelan," more recent
ones
> > say "Orinocco."
> >
> >
> >
> >
> >
> >
> > --
> >
> > Cheers
> > John
> >
> > -- spambait
> > 1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
> > Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
> >
> > do not reply off-list
>
> --
> jack wallen, jr.
> get those pantz off
> www.monkeypantz.net
>
>
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
>
>
11:42 a.m.
You may be able to get it working with ndiswrapper as well.
If you have linux already installed on that laptop do:
lspci -v; that should give output that will help identify the device.
I get:
05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Hewlett-Packard Company: Unknown device 1355
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
That device is working quite happily on FC 4 using ndiswrapper from livna.org.
There is a how to at
http://ndiswrapper.sourceforge.net/mediawiki/index.php/Main_Page.
Bests
Jon
11:44 a.m.
On Sunday January 22 2006 5:42 pm, Jon Savage wrote:
You may be able to get it working with ndiswrapper as well.
If you have linux already installed on that laptop do:
lspci -v; that should give output that will help identify the device.
I get:
05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Hewlett-Packard Company: Unknown device 1355
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at c0204000 (32-bit, non-prefetchable) [size=8K]
That device is working quite happily on FC 4 using ndiswrapper from
livna.org. There is a how to at
http://ndiswrapper.sourceforge.net/mediawiki/index.php/Main_Page.
Bests
Jon
thanks for the help. never did get it to work. i was able to install
ndiswrapper and the driver but even with it installed the hardware was never
recognized. i tried it with both FC4 and Suse 10. I used the driver the Wiki
suggested for the card. nothing. i might have to break down and try to find
another card.
unless someone has a suggestion.
--
jack wallen, jr.
get those pantz off
www.monkeypantz.net
5:19 p.m.
Fabio Comolli wrote:
On 1/22/06, jack wallen <jlwallen(a)monkeypantz.net> wrote:
>had to go into the driver settings to find anything out. looks like the driver
>was made by broadcom - so i'm assuming it's a broadcom chip. of course that
>means there's no support with linux right?
Well, there is a open source project that may help you:
http://bcm43xx.berlios.de/
You may try and see if it works for you.
Regards,
Fabio
On 1/22/06, jack wallen <jlwallen(a)monkeypantz.net> wrote:
>had to go into the driver settings to find anything out. looks like the driver
>was made by broadcom - so i'm assuming it's a broadcom chip. of course that
>means there's no support with linux right?
broadcom is a great brand to avoid. Last Great Step Forward I head from
the broadcom reverse-engineers that they had fully documented the
interfaces and were ready to begin the Next Great Step. I got the
impression usable code was some way off.
ndiswrapper is the most likely option, from my reading but it does limit
what you can do with the card.
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
5:23 p.m.
jack wallen wrote:
thanks for the help. never did get it to work. i was able to install
ndiswrapper and the driver but even with it installed the hardware was never
recognized. i tried it with both FC4 and Suse 10. I used the driver the Wiki
suggested for the card. nothing. i might have to break down and try to find
another card.
I note vendors are starting to see benefit to mentioning the chipset on
the packaging: d-link often does and I think Netgear does too now.
I'm pretty happy atm buying anything with Atheros in it _but_ you will
still need to build the driver for Fedora. It should just work in SUSE 10.
unless someone has a suggestion.
I'm a bit surprised SUSE didn't handle that one; it looked to me like it
would. Mandriva might too.
Ubuntu also is a good bet.
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
9:20 a.m.
On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
broadcom is a great brand to avoid. Last Great Step Forward I head
from the broadcom reverse-engineers that they had fully documented
the interfaces and were ready to begin the Next Great Step. I got the
impression usable code was some way off.
My Acer laptop has a Broadcom wireless connection, using ipw2200. It
works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
but I see no reason why not.
Anne
9:59 a.m.
Anne Wilson wrote:
On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
> broadcom is a great brand to avoid. Last Great Step Forward I head
> from the broadcom reverse-engineers that they had fully documented
> the interfaces and were ready to begin the Next Great Step. I got the
> impression usable code was some way off.
>
My Acer laptop has a Broadcom wireless connection, using ipw2200. It
works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
but I see no reason why not.
If your using the ipw2200 then you've got an Intel mini-PCI card
in your Acer. My laptop has a broadcom chip (can't use the ipw2200
care because it's an AMD, grr) and I have to use ndiswrapper. I may
try the reverse engineered driver later when I have more time.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
10:17 a.m.
There is an open source project for Broadcom wireless cards. The URL is:
http://bcm43xx.berlios.de
You should try it and help developers.
Cheers,
Fabio
On 1/29/06, Neil Cherry <ncherry(a)comcast.net> wrote:
Anne Wilson wrote:
> On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
>
>> broadcom is a great brand to avoid. Last Great Step Forward I head
>> from the broadcom reverse-engineers that they had fully documented
>> the interfaces and were ready to begin the Next Great Step. I got the
>> impression usable code was some way off.
>>
> My Acer laptop has a Broadcom wireless connection, using ipw2200. It
> works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
> but I see no reason why not.
If your using the ipw2200 then you've got an Intel mini-PCI card
in your Acer. My laptop has a broadcom chip (can't use the ipw2200
care because it's an AMD, grr) and I have to use ndiswrapper. I may
try the reverse engineered driver later when I have more time.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12:05 p.m.
On Sun, 2006-01-29 at 15:20 +0000, Anne Wilson wrote:
On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
>
> broadcom is a great brand to avoid. Last Great Step Forward I head
> from the broadcom reverse-engineers that they had fully documented
> the interfaces and were ready to begin the Next Great Step. I got the
> impression usable code was some way off.
>
My Acer laptop has a Broadcom wireless connection, using ipw2200. It
works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
but I see no reason why not.
Anne
I've not seen the original poster show the output from lspci
(type /sbin/lspci -v at the prompt in a Terminal from the
Applications/System Tools menu) here...perhaps I've not been following
closely enough...but my Belkin "Wireless G Desktop Card" (ver.5000 per
the box label) has a Atheros 5212 chip on it and hence I use the madwifi
kernel module from Livna with it. At least one version of a commonly
available D-Link card also uses the 5212 so just dumping one card for
another may not help at all. And yes, this driver gets snippy when
passed parameters from iwconfig that it doesn't understand (like mode
auto) but it works well here even when parameter problems aren't fixed
in ifcfg-ath0.
If you are picky about the ethics of using ndiswrapper and a Windoze
driver, Madwifi isn't quite as bad as those fully proprietary drivers,
but the HAL is closed so it isn't completely open...but I can't see it
as being appreciably worse that loading firmware on certain other
implementations. At least Atheros seems to be trying to provide a
solution that both works for linux users and keeps the FCC off their
backs. Until the cleanroom reverse engineering projects on other
chipsets is much further along, non-hacker Linux users have limited
choices...but the whole tangled mess is being organized under the
watchful eye of John Linville so there is hope. :)
It ought to be clearly stated that a wireless card just ain't gonna play
unless you are loading the correct driver...trying to get the wrong
driver to work is less fun than beating yourself about the head and
shoulders with a ballpeen hammer...so guessing at the card's chipset
just won't cut it. OEMs seem to have a penchant for changing chips on a
whim so that V1 of a card sold under a certain branding may be one thing
and V2 may be something entirely different...thus you need to run lspci
to see what was actually in the box.
As convenient as GUIs are, sometimes you can't get there from here
without running command line tools so getting a little comfortable with
Gnome Terminal (or the KDE equivalent) is going to save a lot of pain in
the long run.
HTH,
Karen
1:02 p.m.
On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
If your using the ipw2200 then you've got an Intel mini-PCI card
in your Acer.
Apologies - you're right. The wireless connection is Intel, the cabled
connection is Broadcom.
My laptop has a broadcom chip (can't use the ipw2200
care because it's an AMD, grr)
Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
Anne
1:21 p.m.
On Sun, 2006-01-29 at 19:02 +0000, Anne Wilson wrote:
On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
>
> If your using the ipw2200 then you've got an Intel mini-PCI card
> in your Acer.
Apologies - you're right. The wireless connection is Intel, the cabled
connection is Broadcom.
> My laptop has a broadcom chip (can't use the ipw2200
> care because it's an AMD, grr)
Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
Anne
----
very confused discussion.
ip2100/2200 is Intel Centrino chipset. Can't possibly get it or use it
on AMD chipsets.
Broadcom makes everything difficult for Linux users since they
absolutely provide no help for open source drivers.
Their ethernet hardware is usable with later 2.4 and most all the 2.6
kernels but their wireless is still not incorporated into the kernel.
Best to stay away from laptops with built-in Broadcom wireless.
Craig
1:53 p.m.
On Sunday 29 Jan 2006 19:21, Craig White wrote:
ip2100/2200 is Intel Centrino chipset. Can't possibly get it or use
it on AMD chipsets.
Broadcom makes everything difficult for Linux users since they
absolutely provide no help for open source drivers.
Their ethernet hardware is usable with later 2.4 and most all the 2.6
kernels but their wireless is still not incorporated into the kernel.
Best to stay away from laptops with built-in Broadcom wireless.
Thanks for the clarification. I wasn't aware that that particular
driver was built for Centrinos.
Anne
2:08 p.m.
Anne Wilson wrote:
On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
> If your using the ipw2200 then you've got an Intel mini-PCI card
> in your Acer.
Apologies - you're right. The wireless connection is Intel, the cabled
connection is Broadcom.
> My laptop has a broadcom chip (can't use the ipw2200
> care because it's an AMD, grr)
Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
I thought it was weird also. The laptop is a Compaq Presario. It
has an Athlon chipset. If you put the ipw2200 in it won't get
past the BIOS check. It comes back with an unrecognized wireless
card and requests it be removed.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
2:09 p.m.
Craig White wrote:
On Sun, 2006-01-29 at 19:02 +0000, Anne Wilson wrote:
> On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
>> If your using the ipw2200 then you've got an Intel mini-PCI card
>> in your Acer.
> Apologies - you're right. The wireless connection is Intel, the cabled
> connection is Broadcom.
>
>> My laptop has a broadcom chip (can't use the ipw2200
>> care because it's an AMD, grr)
> Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
>
> Anne
----
very confused discussion.
ip2100/2200 is Intel Centrino chipset. Can't possibly get it or use it
on AMD chipsets.
Oops, mines a 2100 (the B card) it's a mini-PCI. I thought the
mini-PCI was a standard like the PCI but I guess not.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
4:14 p.m.
On Sunday January 29 2006 3:59 pm, Neil Cherry wrote:
Anne Wilson wrote:
> On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
>> broadcom is a great brand to avoid. Last Great Step Forward I head
>> from the broadcom reverse-engineers that they had fully documented
>> the interfaces and were ready to begin the Next Great Step. I got the
>> impression usable code was some way off.
>
> My Acer laptop has a Broadcom wireless connection, using ipw2200. It
> works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
> but I see no reason why not.
If your using the ipw2200 then you've got an Intel mini-PCI card
in your Acer. My laptop has a broadcom chip (can't use the ipw2200
care because it's an AMD, grr) and I have to use ndiswrapper. I may
try the reverse engineered driver later when I have more time.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
the machine i'm working on is a desktop - not a laptop. so this seems to limit
the number of cards that are supported.
--
jack wallen, jr.
get those pantz off
www.monkeypantz.net
5:40 p.m.
jack wallen wrote:
On Sunday January 29 2006 3:59 pm, Neil Cherry wrote:
> Anne Wilson wrote:
>> On Saturday 28 Jan 2006 23:19, John Summerfied wrote:
>>> broadcom is a great brand to avoid. Last Great Step Forward I head
>>> from the broadcom reverse-engineers that they had fully documented
>>> the interfaces and were ready to begin the Next Great Step. I got the
>>> impression usable code was some way off.
>> My Acer laptop has a Broadcom wireless connection, using ipw2200. It
>> works out-of-the-box with Mandriva. I haven't tried it with FC4 yet,
>> but I see no reason why not.
> If your using the ipw2200 then you've got an Intel mini-PCI card
> in your Acer. My laptop has a broadcom chip (can't use the ipw2200
> care because it's an AMD, grr) and I have to use ndiswrapper. I may
> try the reverse engineered driver later when I have more time.
>
> --
> Linux Home Automation Neil Cherry ncherry(a)linuxha.com
> http://www.linuxha.com/ Main site
> http://linuxha.blogspot.com/ My HA Blog
> http://home.comcast.net/~ncherry/ Backup site
the machine i'm working on is a desktop - not a laptop. so this seems to limit
the number of cards that are supported.
Check out this site, which may be useful:
http://linux-wless.passys.nl/
Don't expect 802.11n or pre-n stuff, but it may give you and idea
of what is available. Wireless is the one area that hits Linux
(and I guess any of the OSS) pretty hard. It has to do with the
fact that the consumer wireless stuff doesn't need a license
at least up to certain power level. Once you surpass that power
level licenses are required. Most chips have software controlled
power levels and the the FCC has mandated that no consumer can
have control of a software controlled power. That could let them
use the consumer product where a license is required. I would
guess the the EU has the same problem.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
6:53 p.m.
On Sun, 2006-01-29 at 19:02 +0000, Anne Wilson wrote:
On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
>
> If your using the ipw2200 then you've got an Intel mini-PCI card
> in your Acer.
Apologies - you're right. The wireless connection is Intel, the cabled
connection is Broadcom.
> My laptop has a broadcom chip (can't use the ipw2200
> care because it's an AMD, grr)
Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
Anne
I thought the ipw2200 driver was for intel chipsets, not broadcom.
7:03 p.m.
Jeff Vian wrote:
On Sun, 2006-01-29 at 19:02 +0000, Anne Wilson wrote:
> On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
> Apologies - you're right. The wireless connection is Intel,
the cabled
> connection is Broadcom.
>
>> My laptop has a broadcom chip (can't use the ipw2200
>> care because it's an AMD, grr)
> Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
I thought the ipw2200 driver was for intel chipsets, not broadcom.
The ipw2200 is an Intel chip set. I tried to use the ipw2100 with
the ipw2100 driver under Linux on a laptop with an AMD processor.
The bios wouldn't let it boot. The OS never got involved, the
bios determined that it didn't like the mini-PCI card.
Sorry about mixing ipw2200 and ipw2100.
--
Linux Home Automation Neil Cherry ncherry(a)linuxha.com
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
http://home.comcast.net/~ncherry/ Backup site
6:58 a.m.
On Sun, 2006-01-29 at 18:40 -0500, Neil Cherry wrote:
Wireless is the one area that hits Linux (and I guess any of the
OSS)
pretty hard. It has to do with the fact that the consumer wireless
stuff doesn't need a license at least up to certain power level. Once
you surpass that power level licenses are required. Most chips have
software controlled power levels and the the FCC has mandated that no
consumer can have control of a software controlled power. That could
let them use the consumer product where a license is required. I would
guess the the EU has the same problem.
I see you've mentioned something outside of the US (the EU), but I
wonder if buying an international product would be the answer? Although
most things here have their FCC information in the manual, the FCC has
no jurisdiction in my country, so different standards could apply.
I'd be surprised if most devices could generate enough power to be a
problem. And even if they couldn't, external amplifiers or better
antennas can increase their output beyond whatever software limits might
exist.
--
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
9:37 a.m.
On Mon, 2006-01-30 at 23:28 +1030, Tim wrote:
On Sun, 2006-01-29 at 18:40 -0500, Neil Cherry wrote:
> Wireless is the one area that hits Linux (and I guess any of the OSS)
> pretty hard. It has to do with the fact that the consumer wireless
> stuff doesn't need a license at least up to certain power level. Once
> you surpass that power level licenses are required. Most chips have
> software controlled power levels and the the FCC has mandated that no
> consumer can have control of a software controlled power. That could
> let them use the consumer product where a license is required. I would
> guess the the EU has the same problem.
I see you've mentioned something outside of the US (the EU), but
I
wonder if buying an international product would be the answer? Although
most things here have their FCC information in the manual, the FCC has
no jurisdiction in my country, so different standards could apply.
Different standards for power and frequency, maybe. But that doesn't
mean that a manufacturer is going to provide that information if he also
has the US as part of his market and he wants to maintain his product as
compliant with FCC standards. The FCC may not have jurisdiction in your
country over you but it may still have defacto jurisdiction over that
manufacturer if they (the manufacturer) wants certification in the US
for any of their products. Wouldn't even need to be the same product or
equipment. You don't want to go piss'n off the FCC on one hand while
trying to get a certification on something else.
I'd be surprised if most devices could generate enough power to
be a
problem. And even if they couldn't, external amplifiers or better
antennas can increase their output beyond whatever software limits might
exist.
I've heard it stated on one of the Linksys forums (might have been up
at Sveasoft or LinksysInfo) that, if you take the Linksys WRT54G{S,L}
and put the Sveasoft firmware (or one of its derivatives) on it and
boost the power output (I think you can go as high as a couple hundred
milliwatts) with the high gain antennas and add one of the range
extenders, you'll end up outside the FCC limits for a "Part 15"
unlicensed device. I haven't confirmed that myself.
But there is also the problem with frequencies. In the US, we've got
11 channels to play with (some of which overlap with licensed Amateur
channels). Other parts of the world have access to all 13 channels.
Some (Japan?) only a couple of channels. I've seen frequency control
cited more often than power limits as the reason. After all, you can
tack on an amplifier, range extenders (repeaters) or high gain antenna's
(for cards which accept external antenna) for more ERP (Effective
Radiated Power).
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
3:17 p.m.
Michael H. Warfield wrote:
Some (Japan?) only a couple of channels. I've seen frequency
control
cited more often than power limits as the reason. After all, you can
tack on an amplifier, range extenders (repeaters) or high gain antenna's
(for cards which accept external antenna) for more ERP (Effective
Radiated Power).
I had an interesting chat with Eric Blossom of the Gnu Radio project
over new year's. He had given an interesting talk about passive radar,
using FM radio stations as the illumination and trying to divine echos.
He seemed to believe the story that there were regulatory issues with
Open wireless drivers, specifically the frequency control stuff, but he
had an interesting take on why the Graphics cards manufacturers insist
on closed drivers, which may be the same reason for the dismal situation
for manufacturer-created Open drivers. He had heard that it was because
the various graphics card manufacturers are infringing each others'
patents left and right, and if they put the source out there it will
invite horrible things to happen to them.
-Andy
4:02 p.m.
On Tue, 2006-01-31 at 21:17 +0000, Andy Green wrote:
Michael H. Warfield wrote:
> Some (Japan?) only a couple of channels. I've seen frequency control
> cited more often than power limits as the reason. After all, you can
> tack on an amplifier, range extenders (repeaters) or high gain antenna's
> (for cards which accept external antenna) for more ERP (Effective
> Radiated Power).
I had an interesting chat with Eric Blossom of the Gnu Radio project
over new year's. He had given an interesting talk about passive radar,
using FM radio stations as the illumination and trying to divine echos.
He seemed to believe the story that there were regulatory issues with
Open wireless drivers, specifically the frequency control stuff, but he
had an interesting take on why the Graphics cards manufacturers insist
on closed drivers, which may be the same reason for the dismal situation
for manufacturer-created Open drivers. He had heard that it was because
the various graphics card manufacturers are infringing each others'
patents left and right, and if they put the source out there it will
invite horrible things to happen to them.
This is possible. This is where 3dfx lost to nVidia and went away. I
am not sure how much credence I would give to that theory though.
-Andy
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
7:43 p.m.
Neil Cherry wrote:
The ipw2200 is an Intel chip set. I tried to use the ipw2100 with
the ipw2100 driver under Linux on a laptop with an AMD processor.
The bios wouldn't let it boot. The OS never got involved, the
bios determined that it didn't like the mini-PCI card.
Sorry about mixing ipw2200 and ipw2100.
I thought both were for Intel (think Centrino).
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
10:04 p.m.
On 1/29/06, Neil Cherry <ncherry(a)comcast.net> wrote:
Anne Wilson wrote:
> On Sunday 29 Jan 2006 15:59, Neil Cherry wrote:
>> If your using the ipw2200 then you've got an Intel mini-PCI card
>> in your Acer.
>
> Apologies - you're right. The wireless connection is Intel, the cabled
> connection is Broadcom.
>
>> My laptop has a broadcom chip (can't use the ipw2200
>> care because it's an AMD, grr)
>
> Really? The ipw2200 driver doesn't work on AMD? I hadn't heard that.
I thought it was weird also. The laptop is a Compaq Presario. It
has an Athlon chipset. If you put the ipw2200 in it won't get
past the BIOS check. It comes back with an unrecognized wireless
card and requests it be removed.
FWI: The reason for this is there is a BIOS white list implemented by
HP/Compaq. They claim the FCC requires this since the original card
with that antenna is the one that passed all the FCC requirements for
RF emissions and such. Sounds like a convenient excuse (if they
really wanted, there might be some better way to comply with the FCC),
but is probably something they do have to do. This is not necessarily
an issue having to due with AMD.
Jonathan
6659
days inactive
6670
days old
28 comments
13 participants
participants (13)
-
Andy Green -
Anne Wilson -
Craig White -
Fabio Comolli -
Jack Wallen -
Jeff Vian -
John Summerfield -
Jon Savage -
Jonathan Berry -
Karen Spearel -
Michael H. Warfield -
Neil Cherry -
Tim