Bill Davidsen <davidsen(a)tmr.com> writes:
Kevin Kofler wrote:
> Bill Davidsen wrote:
>> Jim, mine uses something called rt73.bin and I have no idea how it got in
>> /lib/firmware... But that's what it appears to use.
>
> rt73 is a Ralink firmware, it has nothing to do with the OP's Prism WLAN.
> It comes from the rt73usb-firmware package.
>
Let me state the facts and you can tell me why they don't mean the
obvious... when I plug in the WUSH54G device, the disk blinks, the
device blinks, and a wireless connection is made. On looking at the
files in /lib/firmware I see that the most recently accessed file is
rt73.bin. And that if I boot without plugging in the WUSH54G device
that firmware is not accessed.
I didn't pull that filename out of the sir, I looked to see what
firmware was accessed. Are you saying that the access when the device
is used is just a coincidence?
Does /var/log/messages say anything interesting? On my laptop's
embedded radio I see kernel-tagged syslog messages indicating which
firmware file is getting loaded. If that were present it would put an
end to any doubt.
Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
Jun 3 10:32:19 ancho kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
Jun 3 10:32:19 ancho kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
-wolfgang
--
Wolfgang S. Rupprecht Android 1.5 (Cupcake) and Fedora-11