Hi,
The aforementioned kernel seems to have a minor bug on
(at least) my laptop -- it looks like a potential off-
by-one in the socket handling:
After a clean bootup:
# cardctl status 0
no card
# cardctl status 1
no card
Insert a card in socket 0
# cardctl status 0
no card
# cardctl status 1
5V 16-bit PC Card
function 0: [ready]
Eject card:
# cardctl status 0
no card
# cardctl status 1
no card
Insert card in socket 1:
# cardctl status 0
5V 16-bit PC Card
function 0: [ready]
# cardctl status 1
no card
With both cards:
# cardctl status 0
5V 16-bit PC Card
function 0: [ready]
# cardctl status 1
5V 16-bit PC Card
function 0: [ready]
I once managed to make it assign a socket 0 card to both sockets
and completely ignore socket 1, but can't reproduce this now.
Matthew.
# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (AGP disabled) (rev 03)
00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:04.0 VGA compatible controller: Trident Microsystems Cyber 9525 (rev 49)
00:05.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:05.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:05.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:05.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
00:0a.0 Communication controller: Toshiba America Info Systems FIR Port (rev 23)
00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
On Sat, 9 Dec 2000, Matthew Kirkwood wrote:
> I once managed to make it assign a socket 0 card to both sockets
> and completely ignore socket 1, but can't reproduce this now.
Did it again. It seems that if I boot with anything
in socket 0, socket 1 becomes useless.
Matthew.