Bug 116367
Summary: | (PCMCIA)Yenta_socket not being automatically loaded | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian G. Anderson <bikehead> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | chris, emherman, leszek.cieplinski |
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: | 2006-02-21 19:01:29 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
Brian G. Anderson
2004-02-20 16:38:15 UTC
This cleared up when I updated to the latest development rpms But its back again after upgrading to 2.6.3-1.109 seems like the kernel? Possibly. I've upgraded to 2.6.3-1.116 and I notice that what is happening now is that the wireless interface on eth1 will come up about 2 out of three times. When it doesn't come up, whenever I do a ifup eth1 it gives me an error message 'eth1 no such interface'. Using cardctl to eject and reinsert the card doesn't clear it. If I reboot, then the wireless interface will come up. Next time it occurs I will try and rmmod the orinico_cs driver first, modprobe orinoco_cs, and see if that brings the interface back. I see whats going on. The pcmcia service isn't being started properly. When it first boots, pcmcia service says there are no sockets. When I manually do a "modprobe yenta_socket" and then do "service pcmcia restart" then the card appears and then I can start the wireless card. Shouldn't yenta_socket be automatically loaded by the init scripts? I am having much the same problem with Fedora Core 1, except that my TrueMobile 1150 is installed in a Latitude C610. What happens to me is that when I view the startup details, I see "Error initializing eth1; device does not seem to be present [FAILED]". The card does show up as a Wavelan on the Internet setup wizard, but when I try to go and activate the device, I get a message saying that the driver could not be queried or something (sorry, it's been a while since I last tried it) and then it stops with the "getting IP information... failed" message (even when I have the proper SSID and network key). I have the same problem with Dell Latitude CS with PCMCIA Ethernet card. The workaround from comment 6 works for me. *** Bug 111017 has been marked as a duplicate of this bug. *** "yenta_socket be automatically loaded by the init scripts".... Can you tell me how to edit these scripts so this will load on boot? I have KDS Valiant 671XH using the TI Yenta Socket. Step #6 also worked for me, but I would like it to load on boot. Same problem and solution as #6 Hardware: Fujitsu Siemens Amilo D 8820 and Compaq WL100 11 Mbps Wireless lan card To load at boot time, I adopted the ungraceful solution of adding the line: /sbin/modprobe yenta_socket near the top of the file /etc/rc.d/init.d/pcmcia Nice. Problem solved for me using solution from #12 Probably a dub, but it explanes the problem and a more proper solution https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121742 Couldn't get it to automatically start when booting up using step #12. Found bug ID from Comment #14 to be more thorough and the solution there worked. *** This bug has been marked as a duplicate of 121742 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |