cconly
Group: Members
Posts: 10
Joined: June 2006 |
 |
Posted: Oct. 17 2006,00:51 |
 |
Thanks for answering.
When I type "sudo modprobe prism54" (and hit enter) there is no output. I think this means that the prism54 module is already loaded.
If I do "lsmod" I get this:
prism54 38716 0
firmware_class 3388 0 [prism54]
By comparison, I get this with Suse 10.1 (which, you remember, is on the same PC and works correctly):
prism54 47880 0
firmware_class 9856 2 pcmcia,prism54
The wifi card is not pcmcia, by the way, but is built in and on the pci bus.
As for the chipset, lspci -v gives me this:
0000:00:06.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)
Subsystem: AMBIT Microsystem Corp.: Unknown device 0210
Flags: bus master, medium devsel, latency 80, IRQ 4
Memory at e8000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [dc] Power Management version 1
(And lspci under Suse says the same.)
I'd like to be sure we're talking about the same thing. In order to make Suse work, I copied the firmware that I found on the Net into a specific directory: /lib/firmware. Before that Suse gave me the same message at boot that I now see with DSL, namely, "unable to load firmware" (or words to that effect).
What I wonder is whether with Debian (and DSL) there is not some comparable directory, or alternatively a parameter to use in a startup script to tell prism54 and firmware_class where to load the firmware from.
Thanks again for your help.
Chris
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
