Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: bigpcman on May 14, 2010, 12:31:11 PM
-
Using wicd no wireless networks are found. It looks like the adapter has not been "turned on" - the leds never turn on. Any ideas?
tc@box:~$ lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:01.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
03:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
03:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
03:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
07:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
tc@box:~$ lsmod
Module Size Used by Not tainted
p54pci 4928 0
p54common 14056 1 p54pci
mac80211 82100 2 p54pci,p54common
cfg80211 21604 1 mac80211
prism54 35076 0
vfat 5652 1
fat 29692 1 vfat
squashfs 11732 40
scsi_wait_scan 260 0
pcmcia 13964 0
firmware_class 3188 3 p54pci,prism54,pcmcia
yenta_socket 13336 4
rsrc_nonstatic 5744 1 yenta_socket
pcmcia_core 16976 3 pcmcia,yenta_socket,rsrc_nonstatic
3c59x 24700 0
parport_pc 18352 0
parport 18768 1 parport_pc
battery 5976 0
ac 1732 0
-
I have wg511 v2 (made in china one...Marvel chipset) working but had to use ndiswrapper.
Looks like you have the other version 2...made in Tawain... prism54 chipset
Did you load required firmware...if not go here for info on getting it:
http://wireless.kernel.org/en/users/Drivers/p54#firmware
-
Please post relevant lines of dmesg, and the output of ifconfig.
-
Please post relevant lines of dmesg, and the output of ifconfig.
Here you go ...
tc@box:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:74:94:8D:7F
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:1 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4547 (4.4 KiB) TX bytes:1180 (1.1 KiB)
Interrupt:11 Base address:0x8c00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
dmesg ...
Loaded prism54 driver, version 1.2
prism54 0000:07:00.0: enabling device (0000 -> 0002)
prism54 0000:07:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
eth1 (prism54): not using net_device_ops yet
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
eth0: setting full-duplex.
eth1: resetting device...
eth1: uploading firmware...
prism54 0000:07:00.0: firmware: requesting isl3890
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
I think gwalther is right, the link he provided pretty much explains whats required. I'm now trying to get the wpc600n working first.
-
As stated earlier, you need the firmware installed.
You will either have to make an extension out of the firmware,
or include it in the backup.
-
Here's another link for the firmware that is supposed to have worked for someone else:
http://daemonizer.de/prism54/prism54-fw/fw-fullmac/1.0.4.3.arm
download file...rename it ..isl3890... and put it in ...../lib/firmware....
then try plugging in card again...check ...dmesg...to see if it recognized and retrived firmware.
-
Here's another link for the firmware that is supposed to have worked for someone else:
http://daemonizer.de/prism54/prism54-fw/fw-fullmac/1.0.4.3.arm
download file...rename it ..isl3890... and put it in ...../lib/firmware....
then try plugging in card again...check ...dmesg...to see if it recognized and retrived firmware.
I put the isl3890 file in /lib/firmware/.
Tried it with the following dmesg results ...
eth1: resetting device...
eth1: uploading firmware...
prism54 0000:07:00.0: firmware: requesting isl3890
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
So I guess the firmware goes somewhere else. Where is .../lib/firmware ?
-
You where correct...I meant .../lib/firmware/.....
which download link did you try...first or second one?...the first one has later version.....changing the name of the file is unusual..I know but I think the ...arm file contains multiple sets of firmware.
Also may need to check/change permissions and ownership of firmware file...isl3890
-
You where correct...I meant .../lib/firmware/.....
which download link did you try...first or second one?...the first one has later version.....changing the name of the file is unusual..I know but I think the ...arm file contains multiple sets of firmware.
Also may need to check/change permissions and ownership of firmware file...isl3890
I used the last link you gave me. The Driver files are on sda1 which is a fat disk so no permissions allowed.
-
The dir is /lib/firmware (in the TC ram filesystem), or if you make an extension, /usr/local/lib/firmware.
-
The dir is /lib/firmware (in the TC ram filesystem), or if you make an extension, /usr/local/lib/firmware.
My mistake I did put the driver in the tc file system /lib/firmware, it was the ndiswrapper driver that I put in the /mnt/sda1/driver. At this point I have given up on wireless using the hardware I have.