[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cs: pcmcia_socket0: cardbus cards are not supported



Hi Geoff,
-------- Original-Nachricht --------
Von: Geoff Simmons <gsimmons@gsimmons.org>
An: Stefan Welte <post@stefan-welte.de>
Datum: 22.01.2010 14:49

Thanks for the detailed answer.

>> the cardbus/pcmcia-wlan-card (11ab:1faa) doesn't work on my laptop
>> with debian lenny, 2.6.26-2-486:
> 
> What laptop do you have?  Your provided lspci output appears to match
> against the "Mentor 620" model (Intel Pentium MMX 200) made by Rock
> Computers.
The laptop is labeled:
HIGHSCREEN, LeBook Advance
lspci
00:00.0 Host bridge: OPTi Inc. 82C557 [Viper-M] (rev 14)
00:01.0 ISA bridge: OPTi Inc. 82C558 [Viper-M ISA+IDE] (rev 02)
00:06.0 VGA compatible controller: Chips and Technologies F65550 (rev c6)
00:07.0 CardBus bridge: Texas Instruments PCI1130 (rev 04)
00:07.1 CardBus bridge: Texas Instruments PCI1130 (rev 04)
00:14.0 IDE interface: OPTi Inc. 82C621 [Viper-M/N+] (rev 12)
lspci -n
00:00.0 0600: 1045:c557 (rev 14)
00:01.0 0601: 1045:c558 (rev 02)
00:06.0 0300: 102c:00e0 (rev c6)
00:07.0 0607: 104c:ac12 (rev 04)
00:07.1 0607: 104c:ac12 (rev 04)
00:14.0 0101: 1045:c621 (rev 12)

It seems, the laptop is basically a rock one, and model is mentor (cause of picture and some
hardware data).
But i'm not sure, if it is the 620; cause there are no hardware details for it. [2]
It even could be the "Mentor"-only model [3], but the cardbus bridge is not matching exactly
(TI1030 vs TI1130).

> If this is correct, are you using BIOS version 1.38? [1]
boot screen:
systemsoft bios for opti viper 557/558n version 1.01.25 (3530-13)
v2.4e 10/29/97
systemsoft plug-n-play bios ver 1.17.00

aida16 (only) told me "systembiosdate 12/23/1994", but unfortunately it did not show any bios
version; the motherboard type is also unknown to aida16. :-(

So i think, i don't use 1.38, perhaps 1.17?
If you are familar with the mentor laptops, is there a difference in the bioses of the mentor
series or is there one bios for all mentor laptops?

>> dmesg shows:
>> cs: pcmcia_socket0: cardbus cards are not supported.
> [..]
>> another card is working in the pcmcia-slots, so the slot is ok.
> 
> Is your other card a 16-bit or 32-bit (CardBus) PCMCIA device?
Yes, the card is 16 bit and works well. But it doesn't support 802.11g.

>> possible, suggested solutions:
> [snip]
>> but with pci=assign-busses,pci=biosirq,pci=routeirq,irqpoll as
>> kernelparameters it don't work.
> 
> Did you try these parameters separately, or all together?  
I tried the pci= parameters separately and combined with the irqpoll parameter.

> Try pnpbios=off,pci=noacpi instead.
I tried (with "old" bios, version written above), but it did not solve the problem (cardbus
cards not supported).
I try to get latest bios [4] and then will flash it; afterwards i'll test with these parameters
again.

> CardBus devices continue to be supported by the Linux kernel, subject to
> driver availability (which you intend to workaround using NDISwrapper).
Yes, that's my intention.

Which part of debian outputs the "cs: pcmcia_socket0: cardbus cards are not supported"
information? Is it the kernel, a module or a debian-script,etc?
Why does it output the information?

Thanks,
Stefan



> [1] http://www.rockdirect.com/support/search_more.php?id=356
[2] http://www.rockdirect.com/support/prod.php?product_id=356&size=min
[3] http://www.rockdirect.com/support/prod.php?product_id=62&size=min
[4] http://www.rockdirect.com/support/rock_req.htm

begin:vcard
fn:Stefan Welte
n:Welte;Stefan
adr:Zimmer L103;;Klosterweg 28;Karlsruhe;Baden;76131;Europa
email;internet:post@stefan-welte.de
tel;work:07215604346 (sipgate.de)
tel;pager:SIP:1601472@sipgate.de(nursipgateintern) - JABBER:weltebu@jabber.org - ICQ:174271257
tel;home:077071362 (dtag.de)
tel;cell:07214519817 (sipgate.de)
note:Ich bin Thawte-Notar, siehe www.thawte.com/cgi/personal/wot/contents.exe
x-mozilla-html:FALSE
url:http://www.stefan-welte.de/
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


Reply to: