[Prism54-users] Problems with a 3COM 3CRWE154G72
Allen Winter
winterz@verizon.net
Mon, 5 Jan 2004 12:41:16 -0500
On Monday 05 January 2004 11:59 am, Peter Leinen wrote:
> Dear all,
>
> I try to connect my notebook running under Fedore Core, 2.4.22-1.2115.nptl
?? To my knowledge, the driver only works for kernel 2.4.23 and above.
You should try upgrading your kernel.
> via a Office Connect Wireless PC Card (3CWE154G72) to a wireless lan with
> no success. Yes, I know the card should work as already seen on the list.
>
> I'm not sure where the problem is. The link light blinks and also the
> activity light blink from time to time but I cant see a connection on the
> access point.
>
> I wonder if the module is correct loaded. Should the pcmcia_core and/or the
> ds module not be used by prism54. See the output of lsmod below.
>
> Any other pcmcia card works fine in the slot; for example a ne2000
> compatible network adapter and some SDCards from the digital camera.
>
> Any help welcome.
> Peter
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>++++++++ I installed the version prism54-cvs20040104 as the README tells me
> (alternative 2).
>
> firmware_class is enabled and
> ksyms -a | egrep "request_firmware|release_firmware|register_firmware"
> give the following output.
> c68f0960 release_firmware_R33934162 [firmware_class]
> c68f0830 request_firmware_R38ce5074 [firmware_class]
> c68f0a20 request_firmware_nowait_R5d6ba2b0 [firmware_class]
> c68f09a0 register_firmware_R711cccd3 [firmware_class]
>
> /proc/sys/kernel/hotplug show /sbin/hotplug which is present
> and gives the list of agents as follows
> AgentName values on this system: firmware ieee1394 net pci scsi usb
>
> The firmware file "isl3890" is in /usr/lib/hotplug/firmware.
>
> Finally the card is visible to the pci subsystem as lspci shows
> 02:00.0 Network controller: 3Com Corporation: Unknown device 6001 (rev 01)
> Subsystem: 3Com Corporation: Unknown device 6001
> Flags: bus master, medium devsel, latency 80, IRQ 11
> Memory at 10800000 (32-bit, non-prefetchable) [size=8K]
> Capabilities: [dc] Power Management version 1
>
> ifconfig shows:
> eth1 Link encap:Ethernet HWaddr 00:0D:54:9F:48:C6
> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:168 (168.0 b)
> Interrupt:11
>
> and iwconfig tells me:
> eth1 3COM 3CRWE154G72 Mode:Managed Channel:11
> Access Point: 00:00:00:00:00:00 Bit Rate:0kb/s
> Sensitivity=20/200 Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> where the Channel change from time to time
>
> the list of modules related to this topic:
> Module Size Used by Not tainted
> prism54 40524 1
> firmware_class 6060 0 [prism54]
> ds 8680 1
> yenta_socket 13664 1
> pcmcia_core 57216 0 [ds yenta_socket]
>
> and finally some lines from syslog
> pe kernel: Linux Kernel Card Services 3.1.22
> pe kernel: options: [pci] [cardbus] [pm]
> pe kernel: PCI: Found IRQ 11 for device 00:0a.0
> pe kernel: PCI: Sharing IRQ 11 with 00:02.0
> pe kernel: Yenta IRQ list 0698, PCI irq11
> pe kernel: Socket status: 30000820
> pe kernel: cs: cb_alloc(bus 2): vendor 0x10b7, device 0x6001
> pe kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
> pe pci.agent[5517]: /lib/modules/2.4.22-1.2115.nptl/modules.pcimap
> pe cardmgr[5519]: starting, version is 3.1.31
> pe cardmgr[5519]: watching 1 sockets
> pe cardmgr[5519]: Card Services release does not match
> pe kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> pe kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x398-0x39f 0x4d0-0x
> pe kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> pe cardmgr[5519]: socket 0: CardBus hotplug device
> pe pci.agent[5517]: PCI slot 02:00.0
> pe kernel: Loaded prism54 driver, version 1.0.2.2
> pe kernel: divert: allocating divert_blk for eth1
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x17000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x17000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
> pe kernel: _mgt_get_request(): data length (1!=34) mismatch for oid=0x1200
> pe kernel: _mgt_get_request(): data length (1!=34) mismatch for oid=0x1000
> pe kernel: _mgt_get_request(): data length (1!=6) mismatch for oid=0x10000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
> pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
> pe kernel: eth1: islpci_open()
> pe devlabel: devlabel service started/restarted
> pe kernel: eth1: resetting device...
> pe kernel: eth1: uploading firmware...
> pe kernel: firmware_class.c:call_helper: firmware: /sbin/hotplug firmware
> pe kernel: eth1: firmware uploaded done, now triggering reset...
> pe kernel: eth1: prism54_mib_init()
> pe kernel: eth1: done with prism54_mib_init()! -- Client Managed mode
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users