Scott, On Fri, 17 Jan 2003 10:25:36 EST Scott Merrill wrote:
> On Friday 17 January 2003 10:16 am, you wrote: > > Never seen those error messages before. Something is defintely wrong, > > but I'm not sure what. You might get better help on the orinoco-user > > list: > > http://sourceforge.net/mailarchive/forum.php?forum=orinoco-users > > > > or in the samba wireless archives: > > http://lists.samba.org/pipermail/wireless/ > > That's my next stop. David Gibson, the orinoco_cs author, participates regularly on orinoco-users, so you're likely to get good help there. There is also a recent thread http://sf.net/mailarchive/forum.php?thread_id=1517538&forum_id=11432 that references the same error message you reported. > > > I switched cards, putting the LEAF/Bering card into my laptop, and vice > > > versa; but the problem remained -- a moderate period of inactivity caused > > > the system to think that the card was no longer there. > > > > Which version of orinoco_cs does the Bering system use? Does the > > notebook use orinoco_cs drivers? (Note: you could also try the > > wavelan2_cs binary driver from Lucent.) > > I'm not sure what module version LEAF/Bering uses in the pcmcia_orinoco.lrp > package. > The laptop is using orinoco_cs, from Debian's woody pcmcia-cs package. Look in /var/log/kern.log after a pcmcia restart. When the drivers are insmodded they spit out a bunch of debugging info, including the driver version. (If you post to orinoco-users you'll want to include those log messages.) Most likely you have 0.09b on Bering and 0.11b on woody. That is a combo that worked for me for several months with firmware 8.10 in the debian (sarge) card and 6.16 on the Bering card. > > > The laptop does not produce these error messages, so I'm fairly confident > > > that the problem is isolated to the LEAF/Bering box. This could mean > > > that I've got a screwy configuration somehow, or that I've got a hardware > > > problem (most likely a flakey ISA-to-PCMCIA adapter?). > > > > What make and model is the ISA-to-PCMCIA bridge? > > Vadem VG-469 ISA-to-PCMCIA, just like the one you report success with. Did you have to add PCIC_OPTS=i365_base=0x3e2 to /etc/default/pcmcia like I did? Since your setup is so similar to mine, I will send you copies of my config files and startup messages offlist so you can use them for reference. > > You may also want to try the 2.4.20 version of the kernel, > > pcmcia_orinoco.lrp, and modules.lrp since that will get you up > > to the 0.11b version of orinoco_cs. > > If that'll fix it, so be it. But Matt Schalit's recent explanation of the > hoops to jump through in order to enjoy 2.4.20 gives me the willies! =) IIRC, Matt built his from scratch, but that's not really necessary. Just grab the kernel (linux-2.4.20.upx), pcmcia_orinoco.lrp and modules.lrp from http://leaf.sourceforge.net/devel/jnilo/bering/latest/contrib/2.4.20/ and use them instead of the versions in the 1.0-stable image. You will need to rename "linux-2.4.20.upx" to "linux" and "pcmcia_orinoco.lrp" to "pcmcia.lrp". You _may_ also need the wireless.lrp and iptables.lrp packages from that directory, but I'm not positive. Then use modules from http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/2.4.20/ Just a thought...it's certainly easier than compiling your own kernel and pcmcia modules to upgrade orinoco_cs. :) And you'll probably get better support on orinoco-users if you're using a newer driver version. --Brad ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en ------------------------------------------------------------------------ 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
