PCMCIA 16 bits card with kernel 2.4.21 and 2.6.8 AMD64
Hello all
Are you ready to read this very detailed and technical mail :-) ?
0== my laptop, the PCMCIA cards and linux system :
Asus L5800DF Athlon64 socket 754
- modem PCMCIA Platinum Card MC227 v90 of ComOne (should work fine
according to tuxmobil.org)
- ethernet card Netgear FA411 (a 16 bits one)
SuSE Linux 9.1 AMD64 with the kernel of the SuSE 9.2 AMD64, a 2.6.8-24-3
(the previous one : a
2.6.5-7-111 one)
NB : the Netgear FA411 card, the Hayes modem card and the ComOne modem
card work fine under
WinXP on this Asus L5D laptop. No driver for the ComOne, a small driver
for the Hayes card for WinXP
(none for Win95 on a old laptop ...). I don't remember for the FA411.
1== what says linux during boot without PCMCIA card (dmesg) :
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9
Yenta: CardBus bridge found at 0000:02:01.0 [1043:1854]
Yenta: ISA IRQ mask 0x0098, PCI irq 9
Socket status: 30000006
ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:02:01.1 [1043:1854]
Yenta: ISA IRQ mask 0x0098, PCI irq 11
Socket status: 30000006
2== details about cardbus with "lspci -vv" :
0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab)
Subsystem: Asustek Computer, Inc.: Unknown device 1854
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Hello all
Are you ready to read this very detailed and technical mail :-) ?
Hi Pascal, first of all I can only help you from my experience with a 2.6 kernels, and not with 2.4 kernels. I did not bother to go back to a 2.4 kernel for my AMD64 notebook. I will go through your description more detailled later today, I have to leave now for a few hours. But in the meantime please confirm that the info you give below (configs etc.) are the ones used with the 2.6 kernels. Also I do see a dmesg output from *before* the card is plugged in ( during boot without PCMCIA card)", but I do not see it *after* the card is plugged in. This is however very useful to see how serial_cs or pcnet_cs accepted and configured your card, if recognized at all. From my experience this is the critical step. So please add the dmesg output *after* you inserted the card(s), if possible with a 2.6 kernel. Once that step was fine on my system, it simply worked, no further fiddling was necessary. HTH, Matt On Saturday 20 November 2004 05:02, patheve2 wrote:
0== my laptop, the PCMCIA cards and linux system :
Asus L5800DF Athlon64 socket 754 - modem PCMCIA Platinum Card MC227 v90 of ComOne (should work fine according to tuxmobil.org) - ethernet card Netgear FA411 (a 16 bits one) SuSE Linux 9.1 AMD64 with the kernel of the SuSE 9.2 AMD64, a 2.6.8-24-3 (the previous one : a 2.6.5-7-111 one)
NB : the Netgear FA411 card, the Hayes modem card and the ComOne modem card work fine under WinXP on this Asus L5D laptop. No driver for the ComOne, a small driver for the Hayes card for WinXP (none for Win95 on a old laptop ...). I don't remember for the FA411.
1== what says linux during boot without PCMCIA card (dmesg) :
Linux Kernel Card Services options: [pci] [cardbus] [pm] ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9 Yenta: CardBus bridge found at 0000:02:01.0 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 9 Socket status: 30000006 ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11 Yenta: CardBus bridge found at 0000:02:01.1 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 11 Socket status: 30000006
2== details about cardbus with "lspci -vv" :
0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) Subsystem: Asustek Computer, Inc.: Unknown device 1854 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 0000:02:01.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) Subsystem: Asustek Computer, Inc.: Unknown device 1854 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 3== the config.opts file in /etc/pcmcia (partial view before modifications)
# ====== # This are the official ports to use from pcmcia-cs, but ... # include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff # ... ports 0x810-0x81f hurt on some DELL machines and ... # ... ports 0x3b0-0x3df hurt on some FSC machines. #include port 0x100-0x4ff #include port 0x800-0x8ff #include port 0xc00-0xcff #include port 0x3000-0x7fff # according to lspci -vv for Cardbus include port 0x0000-0x1000 include port 0xb000-0xcfff # include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff include memory 0x60000000-0x60ffffff include memory 0xe0100000-0xe17fffff # according to lspci -vv for Cardbus include memory 0xf8a00000-0xfd1ff000 # # High port numbers do not always work... # include port 0x1000-0x17ff # Extra port range for IBM Token Ring #include port 0xa00-0xaff # Resources we should not use, even if they appear to be available # First built-in serial port exclude irq 4 # Second built-in serial port #exclude irq 3 # First built-in parallel port exclude irq 7 # ========
--- 1st step : to find the right range for the memory : kernel 2.4.21-243 or kernel 2.6.8-24-3
If I write in the /etc/pcmcia/config.opts this (instead of all the above data for memory) :
# 2 ranges : include memory 0xf8a00000-0xfa1ff000 include memory 0xfba00000-0xfd1ff000
or :
# 4 ranges : include memory 0xf8a00000-0xf95ff000 include memory 0xf9600000-0xfa1ff000 include memory 0xfba00000-0xfc5ff000 include memory 0xfc600000-0xfd1ff000
No card is recognized. But if I write this :
# 1 ranges : include memory 0xf8a00000-0xfd1ff000
===> good !!!! But I can't explain such a behaviour. Perharps you know ....
---- 2nd step : to find the right port address : kernel 2.4.21-243 or kernel 2.6.8-24-3
If I write in the /etc/pcmcia/config.opts this (instead of all the above data for port) :
include port 0xb000-0xbfff include port 0xc000-0xcfff
The cards are not available. I tried several address range before b000 : no succes. But, by adding this :
include port 0xd000-0xffff
===> good !!!! But not completely good ...
4a== case of the ethernet FA411 card with kernel 2.4.21
- cardctl ident : Socket 0: product info: "NETGEAR", "FA411", "Fast Ethernet" manfid: 0x0149, 0x0411 function: 6 (network) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardcrl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" function 0: config base 0x03c0 option 0x47 status 0x00 io 0xd000-0xd01f [auto] Socket 1: not configured
- in the file config, the entry for the FA411 is :
card "NetGear FA411 Fast Ethernet" version "NETGEAR", "FA411" bind "pcnet_cs"
- lsmod gives :
ds 9880 2 [pcnet_cs] yenta_socket 15520 2 pcmcia_core 57760 0 [pcnet_cs ds yenta_socket]
- and ifconfig gives (after yast for IP configuration) :
eth1 Link encap:Ethernet HWaddr 00:40:F4:44:19:A2 inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fe44:19a2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:2 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:288 (288.0 b) Base address:0xd000
===> better than before (on last summer)
4b== case of the ethernet FA411 card with kernel 2.6.8
- cardctl ident : Socket 0: product info: "NETGEAR", "FA411", "Fast Ethernet" manfid: 0x0149, 0x0411 function: 6 (network) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" irq 9 [exclusive] [level] function 0: config base 0x03c0 option 0x47 status 0x00 io 0xd000-0xd01f [auto] Socket 1: not configured
- in the file config, the entry for the FA411 is :
card "NetGear FA411 Fast Ethernet" version "NETGEAR", "FA411" bind "pcnet_cs"
- lsmod gives :
pcnet_cs 20152 1 8390 10752 1 pcnet_cs ds 21128 5 pcnet_cs yenta_socket 21248 1 pcmcia_core 66188 3 pcnet_cs,ds,yenta_socket
- and ifconfig gives (after yast for IP configuration) :
eth1 Link encap:Ethernet HWaddr 00:40:F4:44:19:A2 inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fe44:19a2/64 Scope:Link UP BROADCAST RUNNING 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:9 Base address:0xd000
===> like with 2.4.21-243 AMD64 !!! Good
5a== case of the Hayes modem card with kernel 2.4.21 :
- cardctl ident : Socket 0: product info: "HAYES", "OPT288", "YG01 GO", "V7.171;A" manfid: 0x010a, 0x0000 function: 2 (serial) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardcrl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" speaker output is enabled function 0: config base 0x0100 option 0x62 status 0x08 io 0xd000-0xd007 [8bit] Socket 1: not configured
- to force the loading of the right module, I added in the config file :
# insertion le 04-07-2004 card "Hayes Optima 288" version "HAYES", "OPT288", "YG01 GO" manfid 0x010a, 0x0000 bind "serial_cs" #
- lsmod gives :
serial_cs 6624 0 (unused) ds 9880 2 [serial_cs] yenta_socket 15520 2 pcmcia_core 57760 0 [serial_cs ds yenta_socket]
- in /dev/, the symbolic link /dev/modem -> /dev/ttyS2 is well created
- with setserial /dev/ttyS2, I get :
/dev/ttyS2, UART: 16450, Port: 0xd000, IRQ: 0
===> the problem seems to be this IRQ equal to 0, and probably the UART
- with a serial.opts file modified such as :
# Serial device configuration # # The address format is "scheme,socket,instance". # case "$ADDRESS" in *,*,*) INFO="Default modem setup" # Symbolic link to dialout device LINK="/dev/modem" # Options for 'setserial' SERIAL_OPTS="irq 4 autoconfig" # Should we create an inittab entry for this port? #INITTAB="/sbin/mgetty" # Extra stuff to do after setting up the device start_fn () { return; } # Extra stuff to do before shutting down the device stop_fn () { return; } # Card eject policy options NO_CHECK=n NO_FUSER=n ;; esac
I can fix an IRQ. The value 4 is given bye "man setserial". The UART is not modified (autoconfig)
- with wvdial :
--> WvDial: Internet dialer version 1.42 --> Initializing modem. --> Sending: ATZ --> Sending: ATQ0 --> Re-Sending: ATZ --> Modem not responding.
===> the modem card is not working, even with UART fixed to 16550A
5b== case of the Hayes modem card with kernel 2.6.8 :
- cardctl ident : Socket 0: product info: "HAYES", "OPT288", "YG01 GO", "V7.171;A" manfid: 0x010a, 0x0000 function: 2 (serial) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" irq 9 [exclusive] [level] speaker output is enabled function 0: config base 0x0100 option 0x62 status 0x08 io 0xd000-0xd007 [8bit]
- to force the loading of the right module, I added in the config file :
# insertion le 04-07-2004 card "Hayes Optima 288" version "HAYES", "OPT288", "YG01 GO" bind "serial_cs" #
- lsmod gives :
serial_cs 11176 1 ds 21128 5 serial_cs yenta_socket 21248 1 pcmcia_core 66188 3 serial_cs,ds,yenta_socket
- in /dev/, the symbolic link /dev/modem -> /dev/cua5 is created, instead of /dev/ttyS2
- with setserial /dev/cua5, I get :
/dev/cua5: No such device or address
===> why this device ????? I can't get information with "setserial /dev/cua5". When the system is halting (after init 0), the download process stops a the PCMCIA step
6a== case of the Com One modem card with kernel 2.4.21
- cardctl ident : Socket 0: product info: "PCMCIA CARD MEMBER", "FM56R-NCTV2", "021", "A" manfid: 0x0013, 0x0000 function: 2 (serial) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready], [wp], [bat low] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V Socket 1: not configured
- to force the loading of the right module, I added in the config file :
# ajout du 11/11/2004 card "Com One Platinum Card MC227" version "PCMCIA CARD MEMBER", "FM565-NCTV2" bind "serials_cs" #
- lsmod : serial_cs 6624 0 (unused) ds 9880 2 [serial_cs] yenta_socket 15520 2 pcmcia_core 57760 0 [serial_cs ds yenta_socket]
===> but no succes : I can't get the /dev/modem.
- with "setserial /dev/ttyS2" (if ttyS2 is for this card), I get :
/dev/ttyS2, UART: unknown, Port: 0xd3f8, IRQ: 0
===> IRQ 0 and UART unknown, even if SERIAL_OPTS="irq 4 autoconfig"
6b== case of the Com One modem card with kernel 2.6.8
- cardctl ident : Socket 0: product info: "PCMCIA CARD MEMBER", "FM56R-NCTV2", "021", "A" manfid: 0x0013, 0x0000 function: 2 (serial) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" irq 9 [exclusive] [level] speaker output is enabled function 0: config base 0x0420 option 0x45 status 0x08 pin 0x00 ext 0x00 io 0xd3f8-0xd3ff [8bit] Socket 1: not configured
- to force the loading of the right module, I added in the config file :
# ajout du 11/11/2004 card "Com One Platinum Card MC227" version "PCMCIA CARD MEMBER", "FM565-NCTV2" bind "serials_cs" #
- lsmod gives :
serial_cs 11176 1 ds 21128 5 serial_cs yenta_socket 21248 1 pcmcia_core 66188 3 serial_cs,ds,yenta_socket
- in /dev/, the symbolic link /dev/modem -> /dev/cua4
====> why cua4 ???? I can't information with "setserial /dev/cua4". When the system is halting (after init 0), the download process stops a the PCMCIA step
so, if all these details can help you to find the reason why the modem cards don't work with kernel 2.4.2& or 2.6.8, I would be happy to apply your recommandations.
Kind regards
Pascal
On Saturday 20 November 2004 05:02, patheve2 wrote:
Hello all
Are you ready to read this very detailed and technical mail :-) ?
Pascal, I see only now that you have posted replies in the older thread about this same subject. In the following I will comment on the post from you about the 2.6.8 kernel. I do also understand that the ethernet card works now, and it is only the modem card which does not work yet. Is that correct? On Sunday 21 November 2004 16:35, patheve2 wrote:
Hereafter the results about PCMCIA cards with the kernel 2.6.8-24.3 (see the previous mail for kernel 2.4.21)
---- 3rd step : case of the FA411 card with the kernel 2.6.8-24.3
[snip details, as this part seems to work]
---- 4th step : case of the Hayes modem card with the kernel 2.6.8-24.3
- cardctl ident : Socket 0: product info: "HAYES", "OPT288", "YG01 GO", "V7.171;A" manfid: 0x010a, 0x0000 function: 2 (serial)
good.
Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" irq 9 [exclusive] [level] speaker output is enabled function 0: config base 0x0100 option 0x62 status 0x08 io 0xd000-0xd007 [8bit]
- to force the loading of the right module, I added in the config file :
# insertion le 04-07-2004 card "Hayes Optima 288" version "HAYES", "OPT288", "YG01 GO" bind "serial_cs" #
This step is surely not wrong, however as the card had been recognized (see cardctl ident ) as "function: 2 (serial)" I assume that serial_cs would get loaded anyway. As you have done the configuration of ports and memory range already, now the next step is to see if serial_cs does indeed find your card and is able to configure it. This is easy, just do a dmesg right after you plugged tee card in. Then you see - if serial_cs did get loaded, and - how serial_cs did configure the card. Please do that dmesg after inserting the card, and post the output.
- lsmod gives :
serial_cs 11176 1 ds 21128 5 serial_cs yenta_socket 21248 1 pcmcia_core 66188 3 serial_cs,ds,yenta_socket
- in /dev/, the symbolic link /dev/modem -> /dev/cua5 is created, instead of /dev/ttyS2
The dmesg output ( see before) probably shows here that serial_cs did configure the card as /dev/cua5 As far as I remember this is bad, it did happen when I did work on that problem for me as long as I had a kernel < 2.6.7, and all efforts to communicate with that device failed. But lets see the dmesg output first, it might give us a hint. Same goes for the Com One modem card below. Regards, Matt
- with setserial /dev/cua5, I get :
/dev/cua5: No such device or address
===> why this device ?????
---- 5th step : case of the Com One modem card with the kernel 2.6.8-24.3
- cardctl ident : Socket 0: product info: "PCMCIA CARD MEMBER", "FM56R-NCTV2", "021", "A" manfid: 0x0013, 0x0000 function: 2 (serial) Socket 1: no product info available
- cardctl status : Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card
- cardctl config : Socket 0: Vcc 5.0V Vpp1 0.0V Vpp2 0.0V interface type is "memory and I/O" irq 9 [exclusive] [level] speaker output is enabled function 0: config base 0x0420 option 0x45 status 0x08 pin 0x00 ext 0x00 io 0xd3f8-0xd3ff [8bit] Socket 1: not configured
- to force the loading of the right module, I added in the config file :
# ajout du 11/11/2004 card "Com One Platinum Card MC227" version "PCMCIA CARD MEMBER", "FM565-NCTV2" bind "serials_cs" #
- lsmod gives :
serial_cs 11176 1 ds 21128 5 serial_cs yenta_socket 21248 1 pcmcia_core 66188 3 serial_cs,ds,yenta_socket
- in /dev/, the symbolic link /dev/modem -> /dev/cua4
====> why cua4 ????
So, it appears that there is a problem with modem card. The problem of the ethenet card seems to be solved. Who has an idea of how to solve this problem with modem card ?
Regards
Pascal
patheve2 wrote:
Hello Matt
I spent a lot of time on last Thursday to get the use of these PCMCIA cards with kernel 2.6.8 .... and kernel 2.4.21 AMD64 of SuSE. Before, a quick summerize : the Netgear FA411 card, the Hayes modem card and the ComOne modem card work fine under WinXP on this Asus L5D laptop. No driver for the ComOne, a small driver for the Hayes card for WinXP (none for Win95 on a old laptop ...). I don't remember for the FA411.
--- 1st step : to find the right range for the memory : kernel 2.4.21-243 or kernel 2.6.8-24-3
With lspci -vv, I get : [....] Memory window 0: fba00000-fc5ff000 (prefetchable) Memory window 1: fc600000-fd1ff000 [....] Memory window 0: f8a00000-f95ff000 (prefetchable) Memory window 1: f9600000-fa1ff000
If I write in the /etc/pcmcia/config.opts this :
# 2 ranges : include memory 0xf8a00000-0xfa1ff000 include memory 0xfba00000-0xfd1ff000
or :
# 4 ranges : include memory 0xf8a00000-0xf95ff000 include memory 0xf9600000-0xfa1ff000 include memory 0xfba00000-0xfc5ff000 include memory 0xfc600000-0xfd1ff000
No card is recognized. But if I write this :
# 1 ranges : include memory 0xf8a00000-0xfd1ff000
===> good :-) !!!! But I can't explain such a behaviour. Perharps you know ....
---- 2nd step : to find the right port address : kernel 2.4.21-243 or kernel 2.6.8-24-3
According to lspci -vv : [....] I/O window 0: 0000c000-0000c7ff I/O window 1: 0000c800-0000cfff [....] I/O window 0: 0000b000-0000b7ff I/O window 1: 0000b800-0000bfff
If I write in the /etc/pcmcia/config.opts this :
include port 0xb000-0xbfff include port 0xc000-0xcfff
The cards are not available. I tried several address range before b000
: no succes. But, by
adding this :
include port 0xd000-0xffff
===> good !!!! But not completely good .... :-(
---- 3rd step : case of the FA411 card with the kernel 2.4.21-243 (the kernel I am using for this mail)
[snip kernel 2.4 details]
#----------------------------------------------------------------------
======================
On Wednesday 10 November 2004 06:57, patheve2 wrote: /> Hello all / /> / /> My previous mails were sent during last August about this problem with / /> PCMCIA card and Linux 2.6.5. / /> I could hope that the kernel 2.6.8 should solve it, as it was written by / /> some users. /
As described at that time, the kernel >= 2.6.7 is helping, but it is just half of the solution. You also need to get the memory range and port range used by your system and configured in config.opts in sync.
A very quick check (sorry, not much time at the moment) seems to show that you didn't finish that part, see below.
/> Hereafter my proble / /> / /> 0== my laptop, the PCMCIA cards and linux system : / /> / /> Asus L5800DF Athlon64 socket 754 / /> - modem PCMCIA Platinum Card MC227 v90 of ComOne (should work fine / /> according to tuxmobil.org) / /> - ethernet card Netgear FA411 (a 16 bits one) / /> SuSE Linux 9.1 AMD64 with the kernel of the SuSE 9.2 AMD64, a 2.6.8-24-3 / /> (the previous one : a 2.6.5-7-111) / /> / /> / /> 1== what says linux during boot without PCMCIA card (dmesg) : / /> / /> Linux Kernel Card Services / /> options: [pci] [cardbus] [pm] / /> ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9 / /> Yenta: CardBus bridge found at 0000:02:01.0 [1043:1854] / /> Yenta: ISA IRQ mask 0x0098, PCI irq 9 / /> Socket status: 30000006 / /> ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11 / /> Yenta: CardBus bridge found at 0000:02:01.1 [1043:1854] / /> Yenta: ISA IRQ mask 0x0098, PCI irq 11 / /> Socket status: 30000006 / /> / /> / /> 2== details about cardbus with "lspci -vv" : / /> / /> 0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) / /> Subsystem: Asustek Computer, Inc.: Unknown device 1854 / /> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- / /> ParErr- Stepping- SERR- FastB2B- / /> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- / />
Latency: 168 / /> Interrupt: pin A routed to IRQ 9 / /> Region 0: Memory at fd200000 (32-bit, non-prefetchable) / /> Bus: primary=02, secondary=03, subordinate=06, sec-latency=176 / /> Memory window 0: fba00000-fc5ff000 (prefetchable) / /> Memory window 1: fc600000-fd1ff000 / here are the ports your system uses: /> I/O window 0: 0000c000-0000c7ff / /> I/O window 1: 0000c800-0000cfff /
/> BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ / /> PostWrite+ / /> 16-bit legacy interface ports at 0001 / /> / /> / /> 3== the config.opts file in /etc/pcmcia (partial view) / /> / /> # This are the official ports to use from pcmcia-cs, but ... / /> # include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff / /> # ... ports 0x810-0x81f hurt on some DELL machines and ... / /> # ... ports 0x3b0-0x3df hurt on some FSC machines. / /> #include port 0x100-0x4ff / /> #include port 0x800-0x8ff / /> #include port 0xc00-0xcff / /> #include port 0x3000-0x7fff /
and here is what you have configured: /> # according to lspci -vv for Cardbus / /> include port 0x0000-0x1000 / /> include port 0xb000-0xcfff /
i do not see where you got the values 0x0000-0x1000 and 0xb000 from. I do not see them in your "lspci -vv" output. Why don't you try just the port and memory ranges "lspci -vv" gave you, such as :
include port 0xc000-0xc7ff include port 0xc800-0xcfff
/> # / /> include memory 0xc0000-0xfffff / /> include memory 0xa0000000-0xa0ffffff / /> include memory 0x60000000-0x60ffffff / /> include memory 0xe0100000-0xe17fffff / /> # according to lspci -vv for Cardbus / /> include memory 0xf8a00000-0xfd1ff000 /
Also this is not the same as what your "lspci -vv" says, which is fba00000-fc5ff000 and fc600000-fd1ff000. Since 0xf8a00000 is smaller as fba00000 it might be OK though.
/> # / /> / /> # High port numbers do not always work... / /> # include port 0x1000-0x17ff / /> /
participants (2)
-
Matt T. -
patheve2