Bug 81282
Summary: | No pcmcia devices found (HP OmniBook XT6050) after upgrade. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ivo Sarak <ivo> |
Component: | kernel-pcmcia-cs | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | jroyse, rpjday |
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-05-14 18:09:35 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
Ivo Sarak
2003-01-07 15:49:49 UTC
Does the rawhide kernel-pcmcia-cs solve this for you? No. Only difference is that all error messages are gone (only message is "pcmcia: started successfully"). Still no pcmcia_core.o, yenta-socket.o or ds.o module are loaded and no pcmcia devices are found. No changes with Phoebe Beta 8.0.93. No changes with kernel-pcmcia-cs-3.1.31-13.i386.rpm . Any news? It is strange that pcmcia is unable to start up at bootime, but fortunately I get the pcmcia working by running: modprobe pcmcia_core modprobe yenta_socket modprobe ds cardmgr As the release of RedHat Linux 9.0 is imminent, what is the status of this bug? Is this the reason?: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88054 An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2003-172.html *** Bug 88054 has been marked as a duplicate of this bug. *** |