|
Home > Archive > alt.os.linux > July 2002 > Wireless PCMCIA funniness
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Wireless PCMCIA funniness
|
|
|
| Hmmmm.
Linksys WPC11 tried with:
RedHat 7.2 with default modules that come with the OS's kernel
RedHat 7.2 with a built kernel with modules for the card
RedHat 7.3 with default modules
RedHat 7.3 with built kernel
Both of those also without PCMCIA built into the kernel and
pcmcia_cs-3.1.34
pcmcia_cs-3.1.29
built as add-on.
None of these work. I blew away the entire OS and tried each clean.
Same errors. I thought it may be the card, it may have an older
revision number or something so I bought a D-Link DWL-650+ and tried it.
I've heard good things about the dlink.
The D-Link did not work either. I published the errors with the Linksys
in another thread, so here is what a xircom 10/100/56K card looks like
(the xircom works well):
Jul 24 14:40:49 computer kernel: cs: cb_alloc(bus 9): vendor 0x115d,
device 0x0003
Jul 24 14:40:49 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
Jul 24 14:40:49 computer kernel: PCI: Enabling device 09:00.1 (0000 -> 0003)
Jul 24 14:40:49 computer kernel: ttyS04 at port 0xd080 (irq = 10) is a
16550A
Jul 24 14:40:49 computer cardmgr[782]: initializing socket 0
Jul 24 14:40:49 computer cardmgr[782]: socket 0: Xircom CBEM56G-100
CardBus 10/100 Ethernet + 56K Modem
Jul 24 14:40:49 computer /etc/hotplug/pci.agent: Setup xircom_cb for PCI
slot 09:00.0
Jul 24 14:40:49 computer /etc/hotplug/pci.agent: ... no modules for PCI
slot 09:00.1
Jul 24 14:40:49 computer kernel: PCI: Setting latency timer of device
09:00.0 to 64
Jul 24 14:40:49 computer kernel: eth1: Xircom cardbus revision 3 at irq 10
Jul 24 14:40:49 computer /etc/hotplug/net.agent: invoke ifup eth1
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++
Now we throw in the D-Link:
Jul 24 21:41:30 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
device 0x8400
Jul 24 21:41:30 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
Jul 24 21:41:30 computer cardmgr[778]: initializing socket 0
Jul 24 21:41:30 computer cardmgr[778]: unsupported card in socket 0
Jul 24 21:41:30 computer cardmgr[778]: product info: "Wireless Network
CardBus PC Card", "Global", "", ""
Jul 24 21:41:30 computer cardmgr[778]: manfid: 0x0097, 0x8402
Jul 24 21:41:30 computer cardmgr[778]: PCI id: 0x104c, 0x8400
Jul 24 21:41:31 computer /etc/hotplug/pci.agent: ... no modules for PCI
slot 09:00.0
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
++++
Okay, so we work on that and use the PCMCIA HOW-TO:
Jul 24 21:46:46 computer cardmgr[7568]: watching 2 sockets
Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0100-0x04ff:
excluding 0x4d0-0x4d7
Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 24 21:46:53 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
device 0x8400
Jul 24 21:46:53 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
Jul 24 21:46:53 computer cardmgr[7568]: initializing socket 0
Jul 24 21:46:53 computer cardmgr[7568]: socket 0: Wireless Network
CardBus PC Card
Jul 24 21:46:53 computer cardmgr[7568]: executing: 'modprobe wvlan_cs'
Jul 24 21:46:53 computer /etc/hotplug/pci.agent: ... no modules for PCI
slot 09:00.0
Jul 24 21:46:53 computer kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
Jul 24 21:46:53 computer kernel: wvlan_cs: (c) Andreas Neuhaus
<andy@fasta.fh-dortmund.de>
Jul 24 21:46:53 computer kernel: wvlan_cs: GetFirstTuple: No more items
Jul 24 21:46:54 computer cardmgr[7568]: get dev info on socket 0 failed:
Resource temporarily unavailable
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
+++
Well, wvlan_cs didn't work that well, orinoco was supposed to take over
for that anyway so let's try that one:
Jul 24 21:47:24 computer cardmgr[7669]: watching 2 sockets
Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0100-0x04ff:
excluding 0x4d0-0x4d7
Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 24 21:47:29 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
device 0x8400
Jul 24 21:47:29 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
Jul 24 21:47:29 computer cardmgr[7669]: initializing socket 0
Jul 24 21:47:29 computer cardmgr[7669]: socket 0: Wireless Network
CardBus PC Card
Jul 24 21:47:29 computer cardmgr[7669]: executing: 'modprobe orinoco_cs'
Jul 24 21:47:29 computer kernel: orinoco_cs: GetFirstTuple: No more items
Jul 24 21:47:29 computer /etc/hotplug/pci.agent: ... no modules for PCI
slot 09:00.0
Jul 24 21:47:30 computer cardmgr[7669]: get dev info on socket 0 failed:
Resource temporarily unavailable
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
++++++
The 64 dollar question...
What resource is unavailable? How do I fix this? If the resource is
unavailable, why does the xircom work? It's only the wireless cards
that do not.
Thank you for your time
DanH
--
UNIX - Not just for Vestal Virgins anymore
Linux - Choice of a GNU generation
| |
| dhinds 2002-07-24, 9:25 pm |
| In comp.os.linux.portable DanH <danh@ankylosaur.com> wrote:
> Now we throw in the D-Link:
> Jul 24 21:41:30 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
> device 0x8400
> Jul 24 21:41:30 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> Jul 24 21:41:30 computer cardmgr[778]: initializing socket 0
> Jul 24 21:41:30 computer cardmgr[778]: unsupported card in socket 0
> Jul 24 21:41:30 computer cardmgr[778]: product info: "Wireless Network
> CardBus PC Card", "Global", "", ""
This card is not supported. To my knowledge, all supported PCMCIA
wireless adapters are 16-bit cards; none are CardBus. None of the
existing 16-bit wireless drivers will work with a CardBus adapter.
-- Dave
| |
|
| dhinds wrote:
> In comp.os.linux.portable DanH <danh@ankylosaur.com> wrote:
>
>
>>Now we throw in the D-Link:
>>Jul 24 21:41:30 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
>>device 0x8400
>>Jul 24 21:41:30 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
>>Jul 24 21:41:30 computer cardmgr[778]: initializing socket 0
>>Jul 24 21:41:30 computer cardmgr[778]: unsupported card in socket 0
>>Jul 24 21:41:30 computer cardmgr[778]: product info: "Wireless Network
>>CardBus PC Card", "Global", "", ""
>>
>
> This card is not supported. To my knowledge, all supported PCMCIA
> wireless adapters are 16-bit cards; none are CardBus. None of the
> existing 16-bit wireless drivers will work with a CardBus adapter.
>
> -- Dave
>
Well, that does explain that.
I'll take the card back and see what else the store has in for wireless
cards.
Thank you
DanH
--
UNIX - Not just for Vestal Virgins anymore
Linux - Choice of a GNU generation
| |
| Jeff Small 2002-07-25, 10:25 am |
| Should your card be using wavelan_cs?
I am using a Linksys card and got mine working on RH7.3 quite
quickly. Now, granted, you are using RH7.1, but I found this very
useful from another post.
I added this to my /etc/pcmcia/config file
card "Linksys WPC11 Instant Wireless PCCard"
manfid 0x0274, 0x1612
bind "orinoco_cs"
Double check the manfid to make sure yours is the same. (xterm then
cardctrl ident). When I rebooted everything worked wonderfully.
DanH <danh@ankylosaur.com> wrote in message news:<3D3FB6FE.8020504@ankylosaur.com>...
> dhinds wrote:
>
> > In comp.os.linux.portable DanH <danh@ankylosaur.com> wrote:
> >
> >
> >>Now we throw in the D-Link:
> >>Jul 24 21:41:30 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
> >>device 0x8400
> >>Jul 24 21:41:30 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> >>Jul 24 21:41:30 computer cardmgr[778]: initializing socket 0
> >>Jul 24 21:41:30 computer cardmgr[778]: unsupported card in socket 0
> >>Jul 24 21:41:30 computer cardmgr[778]: product info: "Wireless Network
> >>CardBus PC Card", "Global", "", ""
> >>
> >
> > This card is not supported. To my knowledge, all supported PCMCIA
> > wireless adapters are 16-bit cards; none are CardBus. None of the
> > existing 16-bit wireless drivers will work with a CardBus adapter.
> >
> > -- Dave
> >
>
> Well, that does explain that.
>
> I'll take the card back and see what else the store has in for wireless
> cards.
>
> Thank you
> DanH
| |
| B. Joshua Rosen 2002-07-26, 7:25 am |
| In <76694860.0207250815.1d98085a@posting.google.com>, Jeff Small wrote:
> Should your card be using wavelan_cs?
>
> I am using a Linksys card and got mine working on RH7.3 quite quickly.
> Now, granted, you are using RH7.1, but I found this very useful from
> another post.
>
> I added this to my /etc/pcmcia/config file
>
> card "Linksys WPC11 Instant Wireless PCCard"
> manfid 0x0274, 0x1612
> bind "orinoco_cs"
Which version of the card do you have? I have the WPC11 version 3 and I
haven't been able to get it to work in Redhat 7.2 or 7.3. I'll try your
suggestion this weekend and see if that works.
| |
|
| B. Joshua Rosen wrote:
> In <76694860.0207250815.1d98085a@posting.google.com>, Jeff Small wrote:
>
>
>>Should your card be using wavelan_cs?
>>
>>I am using a Linksys card and got mine working on RH7.3 quite quickly.
>>Now, granted, you are using RH7.1, but I found this very useful from
>>another post.
>>
>>I added this to my /etc/pcmcia/config file
>>
>>card "Linksys WPC11 Instant Wireless PCCard"
>> manfid 0x0274, 0x1612
>> bind "orinoco_cs"
>>
>
> Which version of the card do you have? I have the WPC11 version 3 and I
> haven't been able to get it to work in Redhat 7.2 or 7.3. I'll try your
> suggestion this weekend and see if that works.
>
I gave it a shot. orinoco_cs and wvlan_cs.
Here is what I got before I tried it:
Jul 25 22:03:39 computer kernel: Linux Kernel Card Services 3.1.22
Jul 25 22:03:39 computer kernel: options: [pci] [cardbus] [pm]
Jul 25 22:03:39 computer kernel: PCI: Found IRQ 10 for device 02:0f.0
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 00:1f.2
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 02:0f.1
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 02:0f.2
Jul 25 22:03:39 computer kernel: PCI: Found IRQ 10 for device 02:0f.1
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 00:1f.2
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 02:0f.0
Jul 25 22:03:39 computer kernel: PCI: Sharing IRQ 10 with 02:0f.2
Jul 25 22:03:39 computer kernel: Yenta IRQ list 0288, PCI irq10
Jul 25 22:03:39 computer kernel: Socket status: 30000006
Jul 25 22:03:39 computer kernel: Yenta IRQ list 0288, PCI irq10
Jul 25 22:03:39 computer kernel: Socket status: 30000006
Jul 25 22:03:40 computer cardmgr[3871]: starting, version is 3.1.22
Jul 25 22:03:40 computer cardmgr[3871]: config error, file 'config' line
984: syntax error
Jul 25 22:03:40 computer cardmgr[3871]: config error, file
'./config.opts' line 9: no function bindings
Jul 25 22:03:40 computer cardmgr[3871]: watching 2 sockets
Jul 25 22:03:40 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 25 22:03:44 computer cardmgr[3871]: initializing socket 0
Jul 25 22:03:44 computer cardmgr[3871]: unsupported card in socket 0
Jul 25 22:03:44 computer kernel: cs: memory probe 0xa0000000-0xa0ffffff:
clean.
Jul 25 22:03:44 computer cardmgr[3871]: product info: "Instant
Wireless ", " Network PC CARD", "Version 01.02", ""
Jul 25 22:03:44 computer cardmgr[3871]: manfid: 0x0156, 0x0002
function: 6 (network)
Jul 25 22:04:20 computer cardmgr[3871]: exiting
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
+++
So, I put this into the config file:
card "Instant Wireless Network PC CARD Version 01.02"
manfid 0x0156, 0x0002
bind "wavelan_cs"
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
+++
and this came out when I put the card in:
Jul 25 22:06:03 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Jul 25 22:06:07 computer cardmgr[4056]: initializing socket 0
Jul 25 22:06:07 computer cardmgr[4056]: socket 0: Instant Wireless
Network PC CARD Version 01.02
Jul 25 22:06:07 computer kernel: cs: memory probe 0xa0000000-0xa0ffffff:
clean.
Jul 25 22:06:07 computer cardmgr[4056]: executing: 'modprobe wavelan_cs'
Jul 25 22:06:08 computer cardmgr[4056]: executing: './network start eth2'
Jul 25 22:06:08 computer kernel: eth2: wv_hw_config(): modem not
connected or not a wavelan card
Jul 25 22:06:08 computer /etc/hotplug/net.agent: invoke ifup eth2
Jul 25 22:06:08 computer kernel: wv_82593_cmd: wv_82593_config():
configure timeout, status 0x00
Jul 25 22:06:08 computer kernel: wv_82593_cmd: wv_82593_config():
ia-setup timeout, status 0x00
Jul 25 22:06:13 computer kernel: NETDEV WATCHDOG: eth2: transmit timed out
Jul 25 22:06:13 computer kernel: eth2: wavelan_watchdog: watchdog timer
expired
Jul 25 22:06:13 computer kernel: wv_82593_cmd: wavelan_watchdog(): abort
timeout, status 0x30
Jul 25 22:06:13 computer kernel: eth2: wavelan_watchdog: abort failed,
trying reset
Jul 25 22:06:13 computer kernel: eth2: wv_mmc_init(): Invalid MAC
address: FF:FF:FF:...
Jul 25 22:06:13 computer kernel: eth2: wv_hw_config(): Can't configure
the modem
Jul 25 22:06:13 computer kernel: wv_82593_cmd: wv_82593_config():
configure timeout (previous command), status 0xff
Jul 25 22:06:13 computer kernel: wv_82593_cmd: wv_82593_config():
ia-setup timeout (previous command), status 0xff
Jul 25 22:06:13 computer kernel: wv_82593_cmd: wv_82593_config():
mc-setup timeout (previous command), status 0xff
Jul 25 22:06:13 computer kernel: wv_82593_cmd: wv_packet_write():
transmit timeout (previous command), status 0xff
Jul 25 22:06:16 computer kernel: NETDEV WATCHDOG: eth2: transmit timed out
Jul 25 22:06:16 computer kernel: eth2: wavelan_watchdog: watchdog timer
expired
Jul 25 22:06:16 computer kernel: wv_82593_cmd: wavelan_watchdog(): abort
timeout, status 0x00
Jul 25 22:06:16 computer kernel: eth2: wavelan_watchdog: abort failed,
trying reset
Jul 25 22:06:16 computer kernel: eth2: wv_mmc_init(): Invalid MAC
address: FF:FF:FF:...
Jul 25 22:06:16 computer kernel: eth2: wv_hw_config(): Can't configure
the modem
Jul 25 22:06:16 computer kernel: wv_82593_cmd: wv_packet_write():
transmit timeout (previous command), status 0xff
Jul 25 22:06:18 computer kernel: NETDEV WATCHDOG: eth2: transmit timed out
Jul 25 22:06:18 computer kernel: eth2: wavelan_watchdog: watchdog timer
expired
Jul 25 22:06:18 computer kernel: wv_82593_cmd: wavelan_watchdog(): abort
timeout, status 0x00
Jul 25 22:06:18 computer kernel: eth2: wavelan_watchdog: abort failed,
trying reset
Jul 25 22:06:18 computer kernel: eth2: wv_mmc_init(): Invalid MAC
address: FF:FF:FF:...
Jul 25 22:06:18 computer kernel: eth2: wv_hw_config(): Can't configure
the modem
Jul 25 22:06:18 computer kernel: wv_82593_cmd: wv_packet_write():
transmit timeout (previous command), status 0xff
Jul 25 22:06:21 computer kernel: NETDEV WATCHDOG: eth2: transmit timed out
Jul 25 22:06:21 computer kernel: eth2: wavelan_watchdog: watchdog timer
expired
Jul 25 22:06:21 computer kernel: wv_82593_cmd: wavelan_watchdog(): abort
timeout, status 0x00
Jul 25 22:06:21 computer kernel: eth2: wavelan_watchdog: abort failed,
trying reset
Jul 25 22:06:21 computer kernel: eth2: wv_mmc_init(): Invalid MAC
address: FF:FF:FF:...
Jul 25 22:06:21 computer kernel: eth2: wv_hw_config(): Can't configure
the modem
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
++++++
The whole computer froze after I took the card out. Interesting.
DanH
--
UNIX - Not just for Vestal Virgins anymore
Linux - Choice of a GNU generation
| |
| Colin G. 2002-07-26, 1:25 pm |
| I would recommend looking into the linux-wlan project. I've my wireless
cards working using this driver. I have a Linksys WPC11 (version 1),
Linksys WPC11 (version 3), and a D-Link DWL-650. I also have a Cisco
Aironet 352 which works using Cisco's drivers on their site.
linux-wlan site: http://www.linux-wlan.org/
Good luck,
Colin G.
On Wed, 24 Jul 2002 14:50:45 -0700, DanH wrote:
> Hmmmm.
>
> Linksys WPC11 tried with:
> RedHat 7.2 with default modules that come with the OS's kernel
> RedHat 7.2 with a built kernel with modules for the card
>
> RedHat 7.3 with default modules
> RedHat 7.3 with built kernel
>
> Both of those also without PCMCIA built into the kernel and
> pcmcia_cs-3.1.34
> pcmcia_cs-3.1.29
>
> built as add-on.
>
> None of these work. I blew away the entire OS and tried each clean.
> Same errors. I thought it may be the card, it may have an older
> revision number or something so I bought a D-Link DWL-650+ and tried it.
> I've heard good things about the dlink.
>
> The D-Link did not work either. I published the errors with the Linksys
> in another thread, so here is what a xircom 10/100/56K card looks like
> (the xircom works well):
>
> Jul 24 14:40:49 computer kernel: cs: cb_alloc(bus 9): vendor 0x115d,
> device 0x0003
> Jul 24 14:40:49 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> Jul 24 14:40:49 computer kernel: PCI: Enabling device 09:00.1 (0000 -> 0003)
> Jul 24 14:40:49 computer kernel: ttyS04 at port 0xd080 (irq = 10) is a
> 16550A
> Jul 24 14:40:49 computer cardmgr[782]: initializing socket 0
> Jul 24 14:40:49 computer cardmgr[782]: socket 0: Xircom CBEM56G-100
> CardBus 10/100 Ethernet + 56K Modem
> Jul 24 14:40:49 computer /etc/hotplug/pci.agent: Setup xircom_cb for PCI
> slot 09:00.0
> Jul 24 14:40:49 computer /etc/hotplug/pci.agent: ... no modules for PCI
> slot 09:00.1
> Jul 24 14:40:49 computer kernel: PCI: Setting latency timer of device
> 09:00.0 to 64
> Jul 24 14:40:49 computer kernel: eth1: Xircom cardbus revision 3 at irq 10
> Jul 24 14:40:49 computer /etc/hotplug/net.agent: invoke ifup eth1
> ++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++
> Now we throw in the D-Link:
> Jul 24 21:41:30 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
> device 0x8400
> Jul 24 21:41:30 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> Jul 24 21:41:30 computer cardmgr[778]: initializing socket 0
> Jul 24 21:41:30 computer cardmgr[778]: unsupported card in socket 0
> Jul 24 21:41:30 computer cardmgr[778]: product info: "Wireless Network
> CardBus PC Card", "Global", "", ""
> Jul 24 21:41:30 computer cardmgr[778]: manfid: 0x0097, 0x8402
> Jul 24 21:41:30 computer cardmgr[778]: PCI id: 0x104c, 0x8400
> Jul 24 21:41:31 computer /etc/hotplug/pci.agent: ... no modules for PCI
> slot 09:00.0
>
> ++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
++++
> Okay, so we work on that and use the PCMCIA HOW-TO:
> Jul 24 21:46:46 computer cardmgr[7568]: watching 2 sockets
> Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0100-0x04ff:
> excluding 0x4d0-0x4d7
> Jul 24 21:46:46 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> Jul 24 21:46:53 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
> device 0x8400
> Jul 24 21:46:53 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> Jul 24 21:46:53 computer cardmgr[7568]: initializing socket 0
> Jul 24 21:46:53 computer cardmgr[7568]: socket 0: Wireless Network
> CardBus PC Card
> Jul 24 21:46:53 computer cardmgr[7568]: executing: 'modprobe wvlan_cs'
> Jul 24 21:46:53 computer /etc/hotplug/pci.agent: ... no modules for PCI
> slot 09:00.0
> Jul 24 21:46:53 computer kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
> Jul 24 21:46:53 computer kernel: wvlan_cs: (c) Andreas Neuhaus
> <andy@fasta.fh-dortmund.de>
> Jul 24 21:46:53 computer kernel: wvlan_cs: GetFirstTuple: No more items
> Jul 24 21:46:54 computer cardmgr[7568]: get dev info on socket 0 failed:
> Resource temporarily unavailable
>
> ++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
+++
> Well, wvlan_cs didn't work that well, orinoco was supposed to take over
> for that anyway so let's try that one:
> Jul 24 21:47:24 computer cardmgr[7669]: watching 2 sockets
> Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0100-0x04ff:
> excluding 0x4d0-0x4d7
> Jul 24 21:47:24 computer kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> Jul 24 21:47:29 computer kernel: cs: cb_alloc(bus 9): vendor 0x104c,
> device 0x8400
> Jul 24 21:47:29 computer kernel: PCI: Enabling device 09:00.0 (0000 -> 0003)
> Jul 24 21:47:29 computer cardmgr[7669]: initializing socket 0
> Jul 24 21:47:29 computer cardmgr[7669]: socket 0: Wireless Network
> CardBus PC Card
> Jul 24 21:47:29 computer cardmgr[7669]: executing: 'modprobe orinoco_cs'
> Jul 24 21:47:29 computer kernel: orinoco_cs: GetFirstTuple: No more items
> Jul 24 21:47:29 computer /etc/hotplug/pci.agent: ... no modules for PCI
> slot 09:00.0
> Jul 24 21:47:30 computer cardmgr[7669]: get dev info on socket 0 failed:
> Resource temporarily unavailable
>
> ++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
++++++
>
> The 64 dollar question...
>
> What resource is unavailable? How do I fix this? If the resource is
> unavailable, why does the xircom work? It's only the wireless cards
> that do not.
>
> Thank you for your time
> DanH
| |
| dhinds 2002-07-26, 10:25 pm |
| In comp.os.linux.portable DanH <danh@ankylosaur.com> wrote:
> I gave it a shot. orinoco_cs and wvlan_cs.
....
> card "Instant Wireless Network PC CARD Version 01.02"
> manfid 0x0156, 0x0002
> bind "wavelan_cs"
wavelan_cs is absolutely the wrong driver. It is for old pre-IEEE
Wavelan cards. What happens with orinoco_cs or wvlan_cs?
-- Dave
|
|
|
|
|