Bug 115732
Summary: | 3c59x device eth0 does not seem to be present | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hans Christian Studt <hc> |
Component: | pcmcia-cs | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | notting |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-02-16 19:17:50 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
Hans Christian Studt
2004-02-15 15:31:32 UTC
Does it work when the pcmcia service starts? Manually starting the pcmcia service helps. The problem still need to be fixed because the problem here is that the pcmcia service does not start at all when rebooting. Fthermore there is no SXXpcmcia script in any rcX.d direcory. After running the following command and rebooting the network seems to come up OK. chkconfig --add pcmcia What's your /etc/sysconfig/pcmcia look like? Should be fixed in pcmcia-cs-3.2.7-1.5. /etc/sysconfig/pcmcia PCMCIA=YES PCIC=yenya_socket PCIC_OPTS= CORE_OPTS At reboot I still get the UGLY error message (probably because pcmcia starts after the network starts), but after login to KDE the network must have been restarted (with pcmcia already running). So there is still a need to avoid that UGLY error message at boot. |