http://qa.mandrakesoft.com/show_bug.cgi?id=2153

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Orinoco PCMCIA autodetection|9.1 RC1 & RC2 Orinoco PCMCIA
                   |                            |autodetection



------- Additional Comments From [EMAIL PROTECTED]  2003-03-08 21:59 -------
I've fixed the problem for me, but there are still some problems with detecting
and configuring Orinoco WLAN.

In 9.1 RC2 by default acpi=off in lilo.conf (in my case), I set the value to acpi=on
Afterwards the detection of the card was ok (two high beeps), in
/var/log/messages it looks now like that:

Mar  8 13:40:05 localhost kernel: Linux Kernel Card Services Kernel Version
Mar  8 13:40:05 localhost kernel:   options:  [pci] [cardbus] [pm]
Mar  8 13:40:05 localhost kernel: PCI: Enabling device 00:0a.0 (0000 -> 0002)
Mar  8 13:40:05 localhost kernel: Yenta IRQ list 0000, PCI irq17
Mar  8 13:40:05 localhost kernel: Socket status: 10000011
Mar  8 13:40:05 localhost kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Mar  8 13:40:05 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x290-0x297 0x378-0x37f 0x400-0x40f 0x4d0-0x4d7
Mar  8 13:40:05 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Mar  8 13:40:05 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.

I used drakconnect for configuring the Orinoco card (LAN - orinoco_cs), after
configuring a window rised (gmessage), but instead of asking for CD1, the window
was empty!
The configuration in /etc/sysconfig/network-scripts/ifcfg-eth0 wasn't also not
correct, so I had to do the configuration by hand, this was configured:

DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=10.0.1.2
NETMASK=255.255.255.0
NETWORK=10.0.1.0
BROADCAST=10.0.1.255
ONBOOT=yes

The correct configuration should look like that, this is, what I told
drakconnect to configure:

IPADDR=10.0.1.2
NETMASK=255.255.255.0
NETWORK=10.0.1.0
BROADCAST=10.0.1.255
ONBOOT=yes
WIRELESS_MODE=Managed
WIRELESS_ESSID=0fa1d6
WIRELESS_ENC_KEY=4ffe4ffeff


My specs:
AMD Athlon XP 2200+
512MB DDR RAM(333)
Motherboard MSI 6590 KT4 Ultra KT400/VT8235




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
I'm using an Orinoco Silver PCMCIA Card with an PCI Bridge in my Desktop PC.
The autodetection process brings an high and an low peep, and the following log
message:

Feb 22 14:34:04 localhost kernel: Linux Kernel Card Services Kernel Version
Feb 22 14:34:04 localhost kernel:   options:  [pci] [cardbus] [pm]
Feb 22 14:34:04 localhost kernel: PCI: Enabling device 00:0a.0 (0000 -> 0002)
Feb 22 14:34:04 localhost kernel: PCI: No IRQ known for interrupt pin A of
device 00:0a.0. Probably buggy MP table.
Feb 22 14:34:04 localhost kernel: Yenta IRQ list 0000, PCI irq0
Feb 22 14:34:04 localhost kernel: Socket status: 10000011
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x290-0x297 0x378-0x37f 0x400-0x40f 0x4d0-0x4d7
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 22 14:34:04 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Feb 22 14:34:04 localhost kernel: orinoco_cs: RequestIRQ: Resource in use

For testing purpose I changed /etc/sysconfig/pcmcia to:

PCMCIA=yes
PCIC=i82365    (instead of PCIC=yenta_socket)
PCIC_OPTS=irq_mode=0

This configuration change had no effect, system uses yenta_socket instead of
i82365. Why???

My Specs:
AMD XP 2200+
MSI KT4 Ultra KT400/VT8235
512 MB DDR (333) RAM

Reply via email to