I started looking at the Apple ID list again and it appears that
0x0453 was incorrect for this card type since it was the ID for the
miniPCIe card and not the miniPCI card I was using so I thought I'd
give it another shot and change the ID again.
I modified my ID's in a new file and copied it over to ssb_sprom.
I took a look at dmesg and I saw that ssb writing to the card so
without further action I rebooted into OSX and the ID's were now
correct for the specific card type.
I tested the card in Mac OS X 10.4.0, 10.4.8, 10.4.11, 10.5.0, 10.5.2
and 10.5.3 and the card was properly identified.
While the process has now become much simpler, I think it's extremely
dangerous if it doesn't perform some kind of verification on the data
that is being copied before it actually performs the firmware update.
I wish to thank Asheesh for his time in helping me get acclimated to
ubuntu-hardy and also the authors of b43 and ssb for simplifying the
sprom writing process and look forward to when the new cards like the
LinkSYS WMP300n and Buffalo Technology WLI-PCI-G300N are supported so
that the ID's can be corrected thus allowing the use of inexpensive
third-party cards without sacrificing functionality in other OS's.
Since this has turned out to be such a simple process, waiting for
the support of newer cards is a worthwhile wait provide that effort
is being applied.
I really wanna help, the cause is worthwhile.
What task can I perform? (no task to menial)
On Jun 09, 2008, at 04:46 AM, Dale Walsh wrote:
Well, I have a different card to modify as I prepare to familiarize
myself with the process so that when the bcm4321 chipset (0x4328 /
0x4329) is supported I will have great success.
I found a miniPCI card from a china made bcm4306 based card with
the 0x4320 ID that was not recognized as an Apple Airport card.
It look like it would be recognized by the b43 module based on
source examination so I figured I'd use a PCI to miniPCI adapter
and see if I can make the changes without bricking the card.
iwpriv doesn't seem to like the b43 module recognized card and
wouldn't allow me to perform any read/write functions and it was
hinted that this method is for the older bcm43xx module.
I located the ssb_sprom file for the card in question by
identification of lspci and copied out the ssb_sprom file to the
Desktop as original_sprom for easy identification (and so I know
which was the unmodified).
Time for step one:
I modified the firmware with the ID's I want using the ssb-sprom
application.
On to step two:
As suggested by Asheesh, I copied the modified firmware file onto
the ssb_sprom file in the original location and at first I couldn't
tell and wasn't sure if anything happened so I rmmod b43; modprobe
b43 and copied the ssb_sprom file back to the desktop as
new_original_sprom and then did ssb-sprom -i Desktop/
new_original_sprom -P and my new ID's were displayed so it was
time to test this so I started trying the card in various computers
and was elated with the success of things.
Results now in Mac OS X on a BW G3, a PowerPC Dual G5 Xserve and
an generic Intel x86 PC sporting a Core 2 Quad is that the card is
natively recognized and supported.
http://acm.pastebin.com/f5175a0a8
http://daleenterprise.com/download/airportclone.png
Now I have question regarding the process I performed.
Was the disabling and enabling of b43 required???
Is this the correct procedure for modification of the subsys ID's???
-- Dale
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
-- Dale
-- Dale
PGP.sig
Description: This is a digitally signed message part
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
