Sounds like you're making progress...
On Tue, 10 Dec 2002 23:31:22 GMT Samuel Abreu wrote:
> Hi again, i get more deep in Bering, and playing with /etc/init.d/pcmcia
> stops and starts, i find more things useful!
>
> Some how, when the /etc/init.d/pcmcia is started, it load the modules
> necessary to load ISA-PCMCIA card, and then try to load module for orinoco,
> but the module wavelan2_cs, then i rename the file
> /etc/pcmcia/wavelan2_cs.conf to something else (wavebackup), and started
> pcmcia,
wavelan2_cs.conf could definitely get in the way.
> and this time it try load orinoco_cs, but return some unresolved
> symbols, cos it don't load modules hermes and orinoco first, so i edit
> /etc/init.d/pcmcia and add the lines:
> /sbin/insmod hermes
> /sbin/insmod orinoco
You shouldn't need to modify /etc/init.d/pcmcia . Do you have
a /etc/pcmcia/hermes.conf file? You should, and it should have
a section something like this:
device "orinoco_cs"
class "network"
module "hermes", "orinoco", "orinoco_cs"
at the top. I think you can also use:
device "orinoco_cs"
class "network"
module "hermes", "orinoco" opts "pc_debug=3", "orinoco_cs"
^^^^^^^^^^^^^^^^^
to get extra debugging information. The "module" line reflects
the module dependencies and should cause hermes and orinoco to
be loaded before orinoco_cs.
> So, when i start pcmcia, it loads the module correct, but returns me the
> error:
> eth0: failed to reset hardware (err = -19)
> orinoco_cs: register_netdev() failed
>
> and then in /var/log/daemon.log, in the last line, say:
> cardmgr[nnnn]: get dev info on socket 0 failed: Operation not suported by
> device!
>
> And is not in one computer, is in two, with ISAPCMCIA cards diferent! =(
>
> Anyone have a idea of why is not working??
No, but I'm having a tough time following exactly how you are
initializing things and what state the PCMCIA subsystem is in
when the "failed to reset hardware" error occurs. Try the
hermes.conf fix and see if that helps. If not, repost the
details of how you currently have pcmcia setup. An effective
way to communicate the details is to include the output of:
ls -lt /etc/pcmcia/
for f in /etc/network/interfaces \
/etc/default/pcmcia \
/etc/pcmcia/*.opts; do
echo File: $f
echo -----------------------
grep -v ^# $f
done
lsmod
ip link show
iwconfig
lrpkg -l | grep -e pcmcia -e libm -e wireless
and any pcmcia related log entries in syslog or daemon.log.
Be sure to collect that data right after experiencing the
symptom you're asking for help with; that helps us understand
what state the system is in when the problem occurs.
--Brad
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
