hi all. i have searched the annals of this forum, and have found some good help for the ver2.5 and ver3 cards, but have not found anything ov the wpc11 ver4 card.

i installed suse 8.2 on my laptop, but would be more than happy switch, if need be (dont get me wrong about suse, i like it, but still learning it).

does anyone have the ver4 card? if so, is it just like the ver3 card?

any help would be greatlt appreciated.

thanks,

dan

Ohh fark, there's a version 4?!?!

What's the output of:

/sbin/cardctl ident

Hopefully they haven't broadcom'ed the pcmcia flavor of the card.

Cheers,

Finegan

Just to let you know, i have switched distros. First, it was Suse, then Mandrake 9.1, now it is RH 9. Anything to get the card working, i am happy for.

Here is the output:

Socket 0:
no product info available
Socket 1:
product info: "Realtek", "Rtl8139"
manfid: 0x0000, 0x024c
function: 6 (network)

Here is what i get when i restart network:

#service network restart
blah
blah
blah
Bringing up interface eth0: 8139too device eth0 does not seem to be present, delaying initialization

ok, so i remove the realtek 8139 drivers (even tho they r not wireless, that is what the OS thinks i have), and i put in the orinoco set. this time, i get no entry when restarting the network, but do get this when starting the pcmcia (with any drivers):

service pcmcia restart
Shutting down down PCMCIA services: cardmgr modulesds: Device or resource busy
yenta_socket: Device or resource busy
pcmcia_core: Device or resource busy
.
Starting PCMCIA services: cardmgr


finegan, any ideas?

anything else i could try??

/sbin/cardctl ident

Gives you that entry when there's a wireless NIC in there?!?! That's the ident line for a Realtek 10/100, its kinda near impossible to get that unless RH did something odd to /etc/pcmcia/config, which doesn't quite make sense...

Also, the distro dance isn't worth it, everything you mentioned had the exact same pcmcia-cs (more or less), and the exact same kernel. Slight changes in either might have a new entry for this new card, but since this thing is brand-spanking new, if its a new chipset, it may be unsupported or supported by an entirely different driver then the prism2/2.5/3 series cards.

Cheers,

Finegan

i will go thru the config 2morrow, and post here, that way you can see if there is anything out-of-the-ordinary.

I can always take it back and switch, i guess.

i will sleep on it.

thanks for the help.

well, i did not see anything in the pcmcia/config file that caught my eye, except for one thing. at the very end, it has a entry for the Linksys card v3 under "Red Hat Additions". i copied that, pasted it underneath, cahnged "v3" to "v4", and changed teh manfid items from what they were for the v3 to what they are when i run cardctl ident. so, my entry is now:

card "Linksys Instant Wireless Network PC Card WPC11 v4"
manfid 0x0000, 0x024c
bind "orinoco_cs"

i even changed "orinoco" to "wvlan" and "wavelan", but still nothing. It keeps telling me that eth0 is not present.

anything else you can think of, aside from returning it or waiting until it is "supported"?

thanks for all the help.

dan

So, have you found a resolution to this? I now have one of these, and am eager to get it working.

Not really, its a matter of finding out what the exact ident of the chipset is, if you have the exact same ident line from the above, that just says, ver 4, then that's probably not going to help much. Linksys has started dealing with ADMtek recently, as well as Broadcom and Atmel, the first and third of those are good, Broadcom is bad... but without knowing what the chipset is, the only method to figuring out is a lot of just nosing through /proc and trying a lot of different modules, most of which aren't in the kernel, so its tracking a lot of source.

What have you got off of /sbin/cardctl ident?

Cheers,

Finegan

Yup, hereit is:
Socket 0:
product info: "Realtek", "Rtl8139"
manfid: 0x0000, 0x024c
function: 6 (network)

and the dmesg output from starting pcmcia services:

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 02:06.0
Yenta IRQ list 0298, PCI irq11
Socket status: 30000020
cs: cb_alloc(bus 3): vendor 0x10ec, device 0x8180
PCI: Enabling device 03:00.0 (0000 -> 0003)
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.

Finegan: is there anyplace i could look for any more info that you might need for the chipset? if there are any commands i could put in to give u more info, i would be happy to do them.

otherwise, i did find out one item: when doing a search on 0x024c, i found that it also belongs to a edimax card/driver. I have not tried to install this, tho (prolly wont work anyway). i will keep you informed of what i try, what works, and what doesn't.

Thanks for all the help, everyone.

output of lspci:

03:00.0 Ethernet Controller: Realtek Semiconductor Co., Ltd.: Unknown device 8180 (rev 20)

Holy Crap, solved... damn, excellent! Its an RTL8180, that's why ident didn't work, this is a cardbus card, so it really doesn't get handled by the pcmcia subsystem... at least not entirely. Here's the link to the driver:

http://www.realtek.com.tw/downloads/...model=RTL8180L

They give you pre-compiled modules for stock RH kernels, but they give you the source code too, gotta have your kernel source onboard and you have to hand edit the make ffile to point to the kernel version right, but aside from that you can make it with a simple: "make" "make install" "depmod -a"

The entirety of handling it works through a funky set of "iwpriv" commands, that's a tool that comes with the rest of the wireless tools package, its a kin to "iwconfig". Read the README in the package, its brilliantly put together.

Cheers,

Finegan

More on the Makefile (for posterity's sake), this should be fixed with a simple config script of some sort or simply sorted from the makefile with a call to uname, but hey... they'll probably straighten that out later:

This is prepped for a RH 7.3 stock kernel. Say you were running... oh: 2.4.21-rc2-xfs, change it to read:


VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 21
EXTRAVERSION = -rc2-xfs

If you don't have an extraversion, just running stock, leave it blank.

Cheers,

Finegan

I will work on this 2nite after work. Thank you VERY much, finegan. If i need any help, i will post here. Otherwise, i will let u know how it goes.