Bug 30167
Summary: | PCMCIA hang completely a Dell Latitude C800 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alfredo Ferrari <alfredo.maria.ferrari> |
Component: | kernel-pcmcia-cs | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | david_j_morse, msw |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-13 17:56:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alfredo Ferrari
2001-03-01 13:42:31 UTC
Can you try to detect if you are loading "yenta_socket.o" or "i82365.o" ? 2.4 kernels should use yenta_socket.o for cardbus controllers... Hi, yes of course I was using yenta_socket.o as reported in the log above (even though it is never written in a clear way, I knew from the various mailing list that this is the way pcmcia should work on 2.4). The /etc/sysconfig/pcmcia file was: PCMCIA=yes PCIC=yenta_socket PCIC_OPTS="" CORE_OPTS= CARDMGR_OPTS="-v -f" Please again note that there are clear indications that the most recent Dell Laptos are "misunderstood" by all pcmcia flavours, kernel (Linus) or external (D.HInds) ones, both with 2.2 or 2.4 kernels. The "external" drivers work if you tweak them setting on the "pnp" option. There are several consistent messages on the pcmcia forum at sourceforce.net and in the Dell laptop lists showing this behaviour. I am ready to supply all extra infos you may need. I am writing this message connected happily with kernel 2.2.17, pcmcia-cs-3.1.24 recompiled with "pnp" ... the only combination which fully works up to now. We have tested this on two such laptops here without being able to reproduce it, and Dell has also not been able to reproduce the bug. please attach your /etc/pcmcia/config.opts I am running bios a02, I had (and still have) kernel-2.2.17-4 together with the wolverine kernel. System hangs occurred with an Adaptec AP1480A and a 3Com 3C575 in the two sockets. Both are cardbus cards. I got a similar hang with the APA1480A and a Psion Gold card instead of the 3Com. However, latest news, interacting with other RH guys (Mike Harris and Bill Nottingham) in order to get hardware 3D acceleration working, I installed a further version of the kernel and pcmcia-cs from rawhide (with some extra patches for the graphic card they sent me). With this kernel I was just now able to get PCMCIA partially working if a) the APA1480A is NOT there b) a given memory range (0x800-0x8ff) which is apparently unused according to /proc/ioports and which was required in the past to get the two cardbus and/or Psion modem and the OSS/4Technology drivers working together is excluded from /etc/pcmcia/config.opts. This last remark is my fault, I left it because it was needed under kernels 2.2.16 in order to get all the above work, under 2.2.17 it doesn't hurt as well as under 2.4.1 with D.Hinds PCMCIA modules (same exact machine and system, the only difference being the kernel I boot from), it seems to be dangerous with 2.4.1 So the present status is (kernel 2.4.1-0.1.14 plus r128 patches, and kernel-pcmcia-cs-3.1.24-0.5) - the Psion Gold Card is recognized (I suppose it works, not yet tested) - The 3Com575 is recognized and works after I "ifup" manually the network (a bug reported in the realese notes of Wolverine) - The APA1480A still does not work. If I boot with that card inserted and with port 0x800-0x8ff excluded, the system does no longer hang, but the card does not work giving: Mar 2 21:19:32 pceet215 cardmgr[452]: initializing socket 1 Mar 2 21:19:32 pceet215 cardmgr[452]: initializing socket 1 Mar 2 21:19:32 pceet215 cardmgr[452]: socket 1: Adaptec APA-1480 SCSI Host Adap ter Mar 2 21:19:32 pceet215 cardmgr[452]: socket 1: Adaptec APA-1480 SCSI Host Adap ter Mar 2 21:19:33 pceet215 cardmgr[452]: product info: "Adaptec", "APA-1480 SCSI Host Adapter", "", "" Mar 2 21:19:33 pceet215 cardmgr[452]: product info: "Adaptec", "APA-1480 SCSI Host Adapter", "", "" Mar 2 21:19:33 pceet215 cardmgr[452]: manfid: 0x012f, 0xcb01 function: 8 (SC SI) Mar 2 21:19:33 pceet215 cardmgr[452]: manfid: 0x012f, 0xcb01 function: 8 (SC SI) Mar 2 21:19:33 pceet215 cardmgr[452]: executing: 'modprobe cb_enabler' Mar 2 21:19:33 pceet215 cardmgr[452]: executing: 'modprobe cb_enabler' Mar 2 21:19:33 pceet215 cardmgr[452]: executing: 'modprobe apa1480_cb' Mar 2 21:19:33 pceet215 cardmgr[452]: executing: 'modprobe apa1480_cb' Mar 2 21:19:33 pceet215 cardmgr[452]: + modprobe: Can't locate module apa1480_c b Mar 2 21:19:33 pceet215 cardmgr[452]: + modprobe: Can't locate module apa1480_c Mar 2 21:19:33 pceet215 cardmgr[452]: modprobe exited with status 255 Mar 2 21:19:33 pceet215 cardmgr[452]:modprobe exited with status 255 The 3Com card works, even though there are some intial complains in the logs: Mar 2 19:47:05 pceet215 kernel: Yenta IRQ list 0698, PCI irq11 Mar 2 19:47:05 pceet215 kernel: Socket status: 30000020 Mar 2 19:47:06 pceet215 kernel: cs: cb_alloc(bus 7): vendor 0x10b7, device 0x52 57 Mar 2 19:47:06 pceet215 kernel: got res[e800:e87f] for resource 0 of PCI devi ce 10b7:5257 Mar 2 19:47:06 pceet215 kernel: got res[f5000000:f500007f] for resource 1 of PCI device 10b7:5257 Mar 2 19:47:06 pceet215 kernel: got res[f5000080:f50000ff] for resource 2 of PCI device 10b7:5257 Mar 2 19:47:06 pceet215 kernel: got res[f4c00000:f4c1ffff] for resource 6 of PCI device 10b7:5257 Mar 2 19:47:06 pceet215 kernel: PCI: Enabling device 07:00.0 (0000 -> 0003) Mar 2 19:47:06 pceet215 kernel: PCI: No IRQ known for interrupt pin A of device 07:00.0. Please try using pci=biosirq. My present config.opts files is: # # Local PCMCIA Configuration File # #---------------------------------------------------------------------- # System resources available for PCMCIA devices include port 0x100-0x4ff # include port 0x800-0x8ff include port 0xc00-0xcff include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff # 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 # Resources we should not use, even if they appear to be available # ??? Why ttyS1 is taking 2 ??? # exclude irq 2 # First built-in serial port exclude irq 4 # Second built-in serial port #exclude irq 3 # First built-in parallel port exclude irq 7 # ??? Why something is taking 9 ??? # exclude irq 9 # PS/2 Mouse controller port, comment this out if you don't have a PS/2 # based mouse exclude irq 12 #---------------------------------------------------------------------- # Examples of options for loadable modules # To fix sluggish network with IBM ethernet adapter... #module "pcnet_cs" opts "mem_speed=600" # Options for IBM Token Ring adapters #module "ibmtr_cs" opts "mmiobase=0xd0000 srambase=0xd4000" # Options for Raylink/WebGear driver: uncomment only one line... # Generic ad-hoc network module "ray_cs" opts "essid=ADHOC_ESSID hop_dwell=128 beacon_period=256 translat e=1" # Infrastructure network for older cards #module "ray_cs" opts "net_type=1 essid=ESSID1" # Infrastructure network for WebGear #module "ray_cs" opts "net_type=1 essid=ESSID1 translate=1 hop_dwell=128 beacon_ period=256" # Options for WaveLAN/IEEE driver (AccessPoint mode)... #module "wvlan_cs" opts "station_name=MY_PC" # Options for WaveLAN/IEEE driver (ad-hoc mode)... #module "wvlan_cs" opts "port_type=3 channel=1 station_name=MY_PC" # Options for Xircom Netwave driver... #module "netwave_cs" opts "domain=0x100 scramble_key=0x0" # Try to get aha152x on the right interrupt module "aha152x_cs" opts "irq_list=10" # Try to get ttyS1 on the right interrupt module "serial_cs" opts "irq_list=3,9" The last lines are "historical" I was always crazy in avoiding interrupt conflicts on my previous Latitudes. This is the present status (muuuuch better than before). The APA1480A does indeed work flawlessly with the latest beta release of the "old" PCMCIA drivers from D. Hinds. All cards work correctly with kernel-2.2.17-14 and pcmcia-cs-3.1.24 if and only if the latter is compiled with the pnp option. Cheers Alfredo This appears to be closed as resolved in a newer release. Closing. |