Help getting Senao/intersil/prism PCMCIA WiFi wlan0 card working again
Ken Caruso
ken at ipl31.net
Fri Dec 22 18:13:09 PST 2006
On Fri, 2006-12-22 at 14:05 -0800, Daevid Vincent wrote:
> > On Thu, 2006-12-21 at 22:45 -0800, Daevid Vincent wrote:
> > > Thanks for taking the time to help, but that doesn't seem to work.
> > >
> > > I'm very frustrated as I've not had wireless working for
> > days now -- and it
> > > did work for years before this. :( To make things worse, I
> > can't find a
> > > single _current_ "howto" on using the kernel hostap and
> > prism card (via
> > > pcmcia adapter). The old hostap/d is depricated and their
> > site specifically
> > > says to use the 2.6.x kernel version instead, yet they have
> > no instructions
> > > that I can find either. GRRRR.
> >
> > Have you looked at the documentation for linux wireless tools:
> > http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
>
> I keep seeing that page, but nothing useful on there that I can tell.
> Eric Johanson (you know him?) set this up for me years ago, and it's been
> working well since then until time took it's toll and has now effectively
> forced me to upgrade.
>
> > Is the senao card supposed to be a access point or a client to another AP?
>
> Yes. It's supposed to be the WAP for my home network.
>
> > What is the source for your init script?
>
> In gentoo, each interface is just a symlink to net.lo which is very long and
> there isn't anything user configurable about it.
>
> daevid init.d # ll /etc/init.d/net.*
> lrwxrwxrwx 1 root root 6 Nov 19 13:37 /etc/init.d/net.eth0 -> net.lo
> lrwxrwxrwx 1 root root 6 Feb 5 2006 /etc/init.d/net.eth1 -> net.lo
> -rwxr-xr-x 1 root root 30341 Nov 19 13:37 /etc/init.d/net.lo
> lrwxrwxrwx 1 root root 6 Feb 5 2006 /etc/init.d/net.wlan0 -> net.lo
>
> > When you say it doesn't work, what do you mean? Can you not see the
> > wireless ap from another laptop? Have you done any scans? Have you
> > checked the pigtail to make sure its not damaged? I doubt this is a
> > driver issue as the driver appears to see your card and the interfaces
> > are created.
>
> Well, the short version is that trying to start the wlan0 interface (or
> various renamed versions thereof [wifi0, wlan0ap, etc]) won't start. Mostly
> resulting in "network interface wlan0 does not exist" as shown below in
> previous emails.
Yes I have seen all that. But you pasted a iwconfig which showed the
card is Master/AP mode with an SSID of "test" you never said if you
could see the AP from a laptop but not associate etc... If the card is
up and running, in master mode with an SSID and you can't see it, its
quite possible that the problem is somewhere else.
Have you tried configuring by hand without using the init scripts?
>
> I haven't moved anything about the computer. It's a server in my home
> office. It's possible it was dammaged during the power outage, but I really
> don't think that's the case, or I should be seeing errors I'd suspect, or no
> card at all.
>
> I used to use the hostap packages and linux-wlan packages (ebuilds), then
> recently tried to switch since the hostap packages are depricated in favor
> of the kernel versions as per their website. http://hostap.epitest.fi/
> "Note! Host AP driver was added into the main kernel tree in Linux v2.6.14.
> The version in the kernel tree should be used instead of this external
> hostap-driver package. The external releases are only for older kernel
> versions and all the future development will be in the main kernel tree." I
> have no linux-wlan packages installed anymore either -- should I? That seems
> old too... http://www.linux-wlan.org/ the page is all kinds of broken.
>
> Perhaps I am missing something obvious like I don't have the equivallent of
> the linux-wlan-ng drivers? I stopped using them at the same time b/c I
> thought hostap did that task too. Am I wrong?
Hostap is what you want.
>
> Last night, I compiled all the remotely related "prism" drivers as modules.
> And now I see some peculiar things:
>
> daevid init.d # lsmod
> Module Size Used by
> hostap_cs 61080 0
> hostap 112260 1 hostap_cs
> orinoco_cs 15368 1
> orinoco 41108 1 orinoco_cs
> hermes 6656 2 orinoco_cs,orinoco
>
> Why are those orinoco modules being loaded now too?
If I am not mistaken orinoco_cs also supports prism2 as well so it maybe
detecting the card and loading those modules. You may want to black list
the orinoco drivers.
>
> And in dmesg I see this:
>
> Yenta: CardBus bridge found at 0000:00:08.0 [133f:3000]
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:08.0, mfunc 0x00001d92, devctl 0x02
> Yenta: ISA IRQ mask 0x0000, PCI irq 5
> Socket status: 10000051
> ...
> eth2: Hardware identity 800c:0000:0001:0000
> eth2: Station identity 001f:0009:0001:0004
> eth2: Firmware determined as Intersil 1.4.9
> eth2: Ad-hoc demo mode supported
> eth2: IEEE standard IBSS ad-hoc mode supported
> eth2: WEP supported, 104-bit key
> eth2: MAC address 00:02:6F:09:B2:B4
> eth2: Station name "Prism I"
> eth2: ready
> eth2: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
> hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
> ...
> wlan0ap: New link status: Disconnected (0002)
> wlan0ap: New link status: Connected (0001)
> wlan0ap: New link status: Disconnected (0002)
> wlan0ap: New link status: Association Failed (0006)
> wlan0ap: New link status: Disconnected (0002)
> wlan0ap: New link status: Connected (0001)
> cdrom: open failed.
> ipt_owner: pid, sid and command matching not supported anymore
> pccard: card ejected from slot 0
> hostap_cs: Driver unloaded
> pccard: PCMCIA card inserted into slot 0
> pcmcia: registering new device pcmcia0.0
> orinoco 0.15rc3 (David Gibson <hermes at gibson.dropbear.id.au>, Pavel Roskin
> <proski at gnu.org>, et al)
> orinoco_cs 0.15rc3 (David Gibson <hermes at gibson.dropbear.id.au>, Pavel
> Roskin <proski at gnu.org>, et al)
> eth2: Hardware identity 800c:0000:0001:0000
> eth2: Station identity 001f:0009:0001:0004
> eth2: Firmware determined as Intersil 1.4.9
> eth2: Ad-hoc demo mode supported
> eth2: IEEE standard IBSS ad-hoc mode supported
> eth2: WEP supported, 104-bit key
> eth2: MAC address 00:02:6F:09:B2:B4
> eth2: Station name "Prism I"
> eth2: ready
> eth2: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
> hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
>
> So it's strange that NOW eth2 shows up (which would then explain why the
> UDEV rule looks for "eth*"). Is that because of the orinoco driver now? And
> if that is the case, then does that give credence to my theory that I just
> don't have a driver for my senao card in the kernel (or didn't)
Blacklist the orinoco driver so it doesn't load. It looks like its
loading them both.
>
> daevid init.d # ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:03:47:3B:65:87
> inet addr:24.17.255.202 Bcast:255.255.255.255 Mask:255.255.252.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3484575 errors:0 dropped:0 overruns:0 frame:0
> TX packets:95969 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:224322717 (213.9 Mb) TX bytes:70296500 (67.0 Mb)
>
> eth1 Link encap:Ethernet HWaddr 00:03:47:3B:65:88
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4762 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7619 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:551274 (538.3 Kb) TX bytes:4527348 (4.3 Mb)
>
> 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:2905 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2905 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:261093 (254.9 Kb) TX bytes:261093 (254.9 Kb)
>
> wlan0ap Link encap:Ethernet HWaddr 00:02:6F:09:B2:B4
> BROADCAST MULTICAST MTU:1500 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:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:5 Base address:0x100
>
>
> daevid init.d # iwconfig
> ...
> wlan0ap IEEE 802.11b ESSID:"" Nickname:"Prism I"
> Mode:Managed Access Point: Not-Associated Bit Rate:11 Mb/s
> Sensitivity:1/3
> Retry min limit:8 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=0/92 Signal level=-68 dBm Noise level=-122 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Notice also that my wifi0 is gone now?! Again, did the orinoco driver cause
> that?
I don't know.
>
> I think the core of the problem is that I can't get a wlan0 -- once that
> happens, I think the rest of the hostapd (WAP) stuff should just work as it
> has done for years...
The driver has changed alot. In the old driver there was no "wifi0" and
wlan0ap etc... Just wlan0. Wireless in Linux has changed a lot in 2.6
and its constantly changing. Do not assume anything works the same way
it did before.
My suggestion. Rmmod all the wireless modules. modprobe for hostap.
When the wlan0ap interface is created make sure to "ifconfig up" the
interface and set an ssid on it. Then tell me if you see the access
point on your laptop (windows? mac? linux?). If you can see the AP then
you know the card is at least functional and can move on from there.
At this point your box has changed so much I would not rely on the init
scripts for trouble shooting. You will have to do it by hand to figure
out whats going on.
>
> :(
>
> Again, I appreciate you're willingness to help me...
>
> d
>
> > >
> > > daevid rules.d # ifconfig wlan0ap up
> > >
> > > daevid rules.d # /etc/init.d/net.wlan0ap start
> > > * Starting wlan0ap
> > > * Configuring wireless network for wlan0ap
> > > * no access points found
> > > * Couldn't find any access points on wlan0ap
> > > * Failed to configure wireless for wlan0ap
See it appears here the init script thinks this interface is a wireless
client and not a wireless ap, APs should not be looking for access
points.
> > >
> > >
> > > daevid rules.d # ifconfig wlan0 up
> > > wlan0: unknown interface: No such device
> > >
> > > daevid rules.d # ifconfig wifi0 up
> > >
> > > daevid rules.d # /etc/init.d/net.wlan0 start
> > > * Starting wlan0
> > > * Bringing up wlan0
> > > * 10.10.10.1/24
> > > * network interface wlan0 does not exist
> > > * Please verify hardware or kernel module (driver)
> > >
> > >
> > > daevid rules.d # /etc/init.d/net.wlan0ap start
> > > * Starting wlan0ap
> > > * Configuring wireless network for wlan0ap
> > > * no access points found
> > > * Couldn't find any access points on wlan0ap
> > > * Failed to configure wireless for wlan0ap
> > >
> > >
> > > daevid rules.d # ifconfig -a
> > > eth0 Link encap:Ethernet HWaddr 00:03:47:3B:65:87
> > > inet addr:24.17.255.202 Bcast:255.255.255.255
> > Mask:255.255.252.0
> > > UP BROADCAST NOTRAILERS RUNNING MULTICAST
> > MTU:1500 Metric:1
> > > RX packets:5173730 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:86841 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:1000
> > > RX bytes:336080007 (320.5 Mb) TX bytes:61058844 (58.2 Mb)
> > >
> > > eth1 Link encap:Ethernet HWaddr 00:03:47:3B:65:88
> > > inet addr:192.168.1.1 Bcast:192.168.1.255
> > Mask:255.255.255.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:20544 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:26792 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:1000
> > > RX bytes:2378811 (2.2 Mb) TX bytes:13997634 (13.3 Mb)
> > >
> > > 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:3398 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:3398 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:300608 (293.5 Kb) TX bytes:300608 (293.5 Kb)
> > >
> > > wifi0 Link encap:UNSPEC HWaddr
> > > 00-02-6F-09-B2-B4-00-00-00-00-00-00-00-00-00-00
> > > BROADCAST MULTICAST MTU:1500 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:1000
> > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > > Interrupt:5 Base address:0x100
> > >
> > > wlan0ap Link encap:Ethernet HWaddr 00:02:6F:09:B2:B4
> > > BROADCAST MULTICAST MTU:1500 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)
> > > Interrupt:5 Base address:0x100
> > >
> > > So that's another thing I just don't understand about udev,
> > I have two NICs
> > > ports that I use, eth0 from the cable modem to linux and
> > eth1 to a switch.
> > > Then also my wifi.
> > >
> > > Why is the UDEV rule set to be "eth*" in all the examples I
> > see. I've also
> > > tried the other two commented out ones with no difference really.
> > >
> > > daevid rules.d # cat 10-wireless.rules
> > > KERNEL=="eth*", SYSFS{address}=="00:02:6F:09:B2:B4", NAME="wlan0"
> > > #KERNEL=="wifi*", SYSFS{address}=="00:02:6F:09:B2:B4", NAME="wlan0"
> > > #KERNEL=="wlan*", SYSFS{address}=="00:02:6F:09:B2:B4", NAME="wlan0"
> > >
> > > daevid rules.d # ll /sys/class/net
> > > total 0
> > > drwxr-xr-x 7 root root 0 Dec 21 22:23 .
> > > drwxr-xr-x 28 root root 0 Dec 20 17:51 ..
> > > drwxr-xr-x 3 root root 0 Dec 21 21:34 eth0
> > > drwxr-xr-x 3 root root 0 Dec 21 21:34 eth1
> > > drwxr-xr-x 3 root root 0 Dec 20 17:51 lo
> > > drwxr-xr-x 4 root root 0 Dec 21 22:28 wifi0
> > > drwxr-xr-x 4 root root 0 Dec 21 22:23 wlan0ap
> > >
> > >
> > > > -----Original Message-----
> > > > From: talk-bounces at seattlewireless.net
> > > > [mailto:talk-bounces at seattlewireless.net] On Behalf Of Ken Caruso
> > > > Sent: Thursday, December 21, 2006 2:25 AM
> > > > To: SeattleWireless Talk List
> > > > Subject: Re: Help getting PCMCIA WiFi card working again
> > > >
> > > > On Thu, 2006-12-21 at 02:12 -0800, Daevid Vincent wrote:
> > > > > My Senao/EnGenius 200mW WiFi card was working fine for a
> > > > few years, and now,
> > > > > after some upgrade and a power-outage that caused a reboot,
> > > > it's not. I
> > > > > cannot figure out for the life of me what is wrong now.
> > > > It's been two days
> > > > > of constant debugging and I'm out of ideas. I'm trying to
> > > > use the kernel
> > > > > 2.6.15-gentoo-r1 hostap and pcmcia drivers as per the
> > > > suggestions I've read
> > > > > that have depricated the alternatives. It's frustrating,
> > > > because the card
> > > > > appears to be recognized and I don't see any errors
> > > > anywhere to debug
> > > > > further.
> > > >
> > > >
> > > > Your net.wlan0 script is trying to bring up net.wlan0.
> > The drivers you
> > > > are using created an interface of "wlan0ap".
> > > >
> > > > I think "ifconfig wlan0ap up" will probably get it going. You
> > > > will want
> > > > to change your init script to reflect the change in
> > interface names. I
> > > > suspect the hostap drivers got updated a long a time ago
> > and you just
> > > > never noticed without a reboot.
> > > >
> > > > -Ken
> > > >
> > > > >
> > > > > daevid ~ # /etc/init.d/net.wlan0 start
> > > > > * Starting wlan0
> > > > > * Bringing up wlan0
> > > > > * 10.10.10.1/24
> > > > > * network interface wlan0 does not exist
> > > > > * Please verify hardware or kernel module (driver)
> > > > >
> > > > >
> > > > > daevid ~ # ifconfig
> > > > > eth0 Link encap:Ethernet HWaddr 00:03:47:3B:65:87
> > > > > inet addr:24.17.255.202 Bcast:255.255.255.255
> > > > Mask:255.255.252.0
> > > > > UP BROADCAST NOTRAILERS RUNNING MULTICAST
> > > > MTU:1500 Metric:1
> > > > > RX packets:5739 errors:0 dropped:0 overruns:0 frame:0
> > > > > TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
> > > > > collisions:0 txqueuelen:1000
> > > > > RX bytes:363967 (355.4 Kb) TX bytes:35779 (34.9 Kb)
> > > > >
> > > > > eth1 Link encap:Ethernet HWaddr 00:03:47:3B:65:88
> > > > > inet addr:192.168.1.1 Bcast:192.168.1.255
> > > > Mask:255.255.255.0
> > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > > > RX packets:27 errors:0 dropped:0 overruns:0 frame:0
> > > > > TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
> > > > > collisions:0 txqueuelen:1000
> > > > > RX bytes:4112 (4.0 Kb) TX bytes:7001 (6.8 Kb)
> > > > >
> > > > > 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:12 errors:0 dropped:0 overruns:0 frame:0
> > > > > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> > > > > collisions:0 txqueuelen:0
> > > > > RX bytes:1096 (1.0 Kb) TX bytes:1096 (1.0 Kb)
> > > > >
> > > > >
> > > > > daevid ~ # iwconfig
> > > > > eth0 no wireless extensions.
> > > > >
> > > > > eth1 no wireless extensions.
> > > > >
> > > > > lo no wireless extensions.
> > > > >
> > > > > wifi0 IEEE 802.11b ESSID:"test"
> > > > > Mode:Master Access Point: Not-Associated Bit
> > > > Rate:11 Mb/s
> > > > > Sensitivity=1/3
> > > > > Retry min limit:8 RTS thr:off Fragment thr:off
> > > > > Encryption key:off
> > > > > Power Management:off
> > > > >
> > > > > wlan0ap IEEE 802.11b ESSID:"test"
> > > > > Mode:Master Access Point: Not-Associated Bit
> > > > Rate:11 Mb/s
> > > > > Sensitivity=1/3
> > > > > Retry min limit:8 RTS thr:off Fragment thr:off
> > > > > Encryption key:off
> > > > > Power Management: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
> > > > >
> > > > >
> > > > >
> > > > > daevid ~ # lsmod
> > > > > Module Size Used by
> > > > > hostap_cs 61080 1
> > > > > hostap 112260 1 hostap_cs
> > > > > tuner 43556 0
> > > > > tvaudio 22300 0
> > > > > bttv 157264 0
> > > > > video_buf 17412 1 bttv
> > > > > v4l2_common 4992 1 bttv
> > > > > btcx_risc 4232 1 bttv
> > > > > tveeprom 14096 1 bttv
> > > > > videodev 7424 1 bttv
> > > > > nvidia 4547284 0
> > > > >
> > > > >
> > > > > daevid ~ # cat /etc/udev/rules.d/10-wireless.rules
> > > > > KERNEL=="eth*", SYSFS{address}=="00:02:6f:09:b2:b4",
> > NAME="wlan0"
> > > > >
> > > > > daevid ~ # dmesg
> > > > > hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
> > > > > hostap_cs: setting Vcc=33 (constant)
> > > > > hostap_cs: CS_EVENT_CARD_INSERTION
> > > > > hostap_cs: setting Vcc=33 (from config)
> > > > > Checking CFTABLE_ENTRY 0x01 (default 0x01)
> > > > > IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
> > > > > io->flags = 0x0046, io.base=0x0000, len=64
> > > > > hostap_cs: Registered netdevice wifi0
> > > > > hostap_cs: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
> > > > > prism2_hw_init: initialized in 376 ms
> > > > > wifi0: NIC: id=0x800c v1.0.0
> > > > > wifi0: PRI: id=0x15 v1.1.0
> > > > > wifi0: STA: id=0x1f v1.4.9
> > > > > wifi0: defaulting to bogus WDS frame as a workaround for
> > > > firmware bug in
> > > > > Host AP mode WDS
> > > > > wifi0: registered netdevice wlan0
> > > > >
> > > > >
> > > > > daevid ~ # esearch pcmcia
> > > > > * sys-apps/pcmcia-cs
> > > > > Latest version available: 3.2.8-r2
> > > > > Latest version installed: 3.2.8-r2
> > > > >
> > > > > * sys-apps/pcmcia-cs-cis
> > > > > Latest version available: 3.2.8-r1
> > > > > Latest version installed: [ Not Installed ]
> > > > >
> > > > > * sys-apps/pcmcia-cs-modules
> > > > > Latest version available: 3.2.8
> > > > > Latest version installed: [ Not Installed ]
> > > > >
> > > > > * sys-apps/pcmcia-cs-pnptools
> > > > > Latest version available: 3.2.8
> > > > > Latest version installed: [ Not Installed ]
> > > > >
> > > > > * sys-apps/pcmciautils
> > > > > Latest version available: 013
> > > > > Latest version installed: 013
> > > > >
> > > > > * virtual/pcmcia
> > > > > Latest version available: 2.6.13
> > > > > Latest version installed: 3.2.8-r2
> > > > >
> > > > > daevid ~ # esearch udev
> > > > > * sys-fs/udev
> > > > > Latest version available: 103
> > > > > Latest version installed: 103
> > > > >
> > > > > daevid ~ # pccardctl info
> > > > > PRODID_1="INTERSIL"
> > > > > PRODID_2="HFA384x/IEEE"
> > > > > PRODID_3="Version 01.02"
> > > > > PRODID_4=""
> > > > > MANFID=0156,0002
> > > > > FUNCID=6
> > > > >
> > > > > daevid ~ # pccardctl ls
> > > > > Socket 0 Bridge: [yenta_cardbus] (bus ID:
> > > > 0000:00:08.0)
> > > > > Socket 0 Device 0: [hostap_cs] (bus ID: 0.0)
> > > > >
> > > > > daevid ~ # pccardctl status
> > > > > Socket 0:
> > > > > 3.3V 16-bit PC Card
> > > > > Subdevice 0 (function 0) bound to driver "hostap_cs"
> > > > >
> > > > > _______________________________________________
> > > > > Talk mailing list
> > > > > Talk at seattlewireless.net
> > > > > http://seattlewireless.net/mailman/listinfo/talk
> > > >
> > > > _______________________________________________
> > > > Talk mailing list
> > > > Talk at seattlewireless.net
> > > > http://seattlewireless.net/mailman/listinfo/talk
> > > >
> > >
> > > _______________________________________________
> > > Talk mailing list
> > > Talk at seattlewireless.net
> > > http://seattlewireless.net/mailman/listinfo/talk
> >
> > _______________________________________________
> > Talk mailing list
> > Talk at seattlewireless.net
> > http://seattlewireless.net/mailman/listinfo/talk
> >
>
> _______________________________________________
> Talk mailing list
> Talk at seattlewireless.net
> http://seattlewireless.net/mailman/listinfo/talk
More information about the Talk
mailing list