inflexion Posted April 1, 2005 Report Share Posted April 1, 2005 (edited) Set up 10.1 to run my card at boot but now i finally set up my wireless network and have some use for it, the card wont run. Everything works fine in winblows. At boot it says that its not present and then when i try to config it through MCC it just flashes up some error messages far to quickly for anyone to see The card is a linksys wpc11 v3 Edited April 1, 2005 by inflexion Quote Link to comment Share on other sites More sharing options...
Gowator Posted April 1, 2005 Report Share Posted April 1, 2005 If its not lighting up then chances are that PCMCIA is not started or is failing... check your /etc/init.d/pcmcia ? i.e at the CLI as root /etc/init.d/pcmcia stop /etc/init.d/pcmcia start any error messages? Quote Link to comment Share on other sites More sharing options...
inflexion Posted April 1, 2005 Author Report Share Posted April 1, 2005 [root@localhost matt]# /etc/init.d/pcmcia stop Shutting down PCMCIA services: ERROR: Module ds is in use by orinoco_cs ERROR: Module pcmcia_core is in use by orinoco_cs,ds done. [root@localhost matt]# /etc/init.d/pcmcia start Starting PCMCIA services: cardmgr[6295]: no sockets found! done. [root@localhost matt]# Quote Link to comment Share on other sites More sharing options...
Gowator Posted April 1, 2005 Report Share Posted April 1, 2005 well, its half working then :D presuming the orinoco is the correct driver then it looks like you just need it configuring. If you have 'other' internet access then Kwifi is a good way for KDE users. Quote Link to comment Share on other sites More sharing options...
inflexion Posted April 1, 2005 Author Report Share Posted April 1, 2005 hmmm thats what i though, yea i do have other net access cause its still all on my table in a mess of wires lol Quote Link to comment Share on other sites More sharing options...
inflexion Posted April 1, 2005 Author Report Share Posted April 1, 2005 that doesnt do squat! How can i remove it from starting at boot then i can try to config it again Quote Link to comment Share on other sites More sharing options...
Gowator Posted April 1, 2005 Report Share Posted April 1, 2005 that doesnt do squat! How can i remove it from starting at boot then i can try to config it again <{POST_SNAPBACK}> You can remove it from starting a boot with chkconfig pcmcia off This will leave the init script so you can trouble shoot. My suggestions are playing with the iwconfig tool etc. and use KWifi as a way to see when it works... first time i tried I actualy had it working and didn't realise for half a day! I found for instance setting the rate=54M etc. actually got it working... but it was largely trial and error. The newer KWifi in KDE 3.4 has a scanning option too. You seem to be loading the module so it probably either isn't finding the firmware or its a setting... ifconfig <wlan0> down ifconfig <wlan0> up (wlan being the name of the interface... ) ifconfig by itself should show you the state of all the interfaces and the names. Quote Link to comment Share on other sites More sharing options...
inflexion Posted April 1, 2005 Author Report Share Posted April 1, 2005 nothing works, doing ifconfig eth0 down ifconfig eth0 up brought it up in ifconfig but it wasnt the wifi card :( Im guessing that its the PCMCIA slot rather than the card because in system>config>kde>info>pcmcia it says that there is no controller detected oh and /etc/init.d/network start gives Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth1: [ OK ] Bringing up interface eth2: orinoco_cs device eth2 does not seem to be present, delaying initialization. [FAILED] Quote Link to comment Share on other sites More sharing options...
adamw Posted April 1, 2005 Report Share Posted April 1, 2005 does: modprobe yenta_socket help? Quote Link to comment Share on other sites More sharing options...
Gowator Posted April 2, 2005 Report Share Posted April 2, 2005 does: modprobe yenta_socket help? <{POST_SNAPBACK}> After you try this you should be assigned a name for your PCMCIA card. in your case it seems to be assigned eth2 So you seem to have eth0 (working and OK) eth1 (??) eth2 (??) One of these might be firewire ? which would be eth1 hence ifconfig eth2 down ifconfig eth2 up should give you a bit more detail with the yenta socket loaded this should be OK but if not the error messages will be helpful. Quote Link to comment Share on other sites More sharing options...
inflexion Posted April 3, 2005 Author Report Share Posted April 3, 2005 eth1 is my NIC which is what im connected with now eth0 could be firewire im not sure eth2 should be the card as thats what it assigns at boot but iwconfig gives eth0, eth1 and sit0 doing ifconfig sit0 down ifconfig sit0 up gives me the info on it has it been IPv6 in IPv4 so i think that this is the firewaire socket as thats one of the connection options in MCC. also the info for eth0 gives me a massive MAC address so im more than confused by this Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.