Mailing List os2-wireless_users@2rosenthals.com Archived Message #6596

From: "Andy Willis" <os2-wireless_users@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [OS2Wireless] Driver Problem
Date: Wed, 17 Feb 2010 09:16:37 -0700
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>

Thomas Dennis wrote:
Andy Willis wrote:
Lewis G Rosenthal wrote:
Hi, Thomas...

On 02/10/10 03:42 pm, Thomas Dennis thus wrote :
Hi:
I'm trying to get my Laptop to work with eCS 2.0 rc7.
Since my Laptop is an older model I'm using a PCMCIA
plug-in card. A D-Link DWA 645. The chipset is suppose
to an Atheros but I haven't been able to establish it
as a fact.
I did download two s/w packages from Netlabs that are
for the Atheros chipset but I have not been able to
install them. The problem may be due to one of the files being
saddled with the DOS name regulation 8:3. I have
renamed it correctly as it is on the Internet, but
one of the eCS 2.0 rc7 widgets keeps showing the
DOS file name.
Like: GENMAC220_ATHEROS.WPI
GENMAC~1.WPI
Where it's getting this data from I don't know.
WarpIN, which came with eCS 2.0, gives me an error
message saying that:
"GenMac could not find any network interface card in
the system!"
Can anybody tell me what the problem is?
Am I doing something wrong or left something out that
needs to be included?
You need to install Veit's cbenable driver to get GenMAC to see the card
and turn it on. Please see my other post of 2/3 @ 8:25pm EST. Without
cbenable, there's no "glue" to bind the card slots to the PCI bus
(insofar as GenMAC is concerned), so it doesn't see the card.

Also, in that same message, I asked you to provide the PCI ID string of
the card, so that we could be certain of the chipset. If you need
assistance with this step of the process, please advise.

You should probably review
http://article.gmane.org/gmane.org.netlabs.genmac.user/1187 , et seq.

One thing to note: cbenable does not work with ACPI.
I've had success with the following:

REM [PCCARD section
DEVICE=D:\UTILS\THINKPAD\VPCMCIA.SYS
DEVICE=D:\UTILS\THINKPAD\PCMSSDIF.SYS
REM DEVICE=D:\UTILS\THINKPAD\PCM2SRAM.SYS
REM DEVICE=D:\UTILS\THINKPAD\FLSH2MTD.SYS
REM DEVICE=D:\UTILS\THINKPAD\PCM2FLSH.SYS
BASEDEV=PCMCIA.SYS /R:500
BASEDEV=IBM2SS14.SYS
rem BASEDEV=sspcic.sys /VS:auto /E /AP:on
BASEDEV=AUTODRV2.SYS
REM BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP
BASEDEV=PCM2ATA.ADD /S:2 /NOBEEP
REM BASEDEV=OS2PCARD.DMD
BASEDEV=CBENABLE.SYS * * 0 0 PCIIRQ
BASEDEV=OEMHLP2.SYS
DEVICE=D:\OS2\$ICPMOS2.SYS /G

sspcic - Apsoft driver does not work for this configuration either.
eCS 2.0 rc7 should have the proper pccard support level, previous
releases did not.
Until cbenable is in place, the pccard will not show with pci.exe.
Not much more involved really other than, if once you have all drivers
in place and if it hangs on boot at or around netbind then wait for a
short while but if it doesn't continue then you can pull the pccard
and the boot will continue but the card will not function.
Andy
Andy:
I seem to be a bit confused.
It's about this: BASEDEV=CBENABLE.SYS * * 0 0 PCIIRQ
I thought that CBENABLE.SYS had only three switches and in the
past switches started with " / " but that doesn't seem to be the case
here. There appear to be more than three. Can you explain?

Not all switches/parameters require a "/".  By convention it is not unusual to require it but that is largely because it is a way to make parsing for the switches easier.  I believe that despite the number of objects seen, it technically is only 3 switches.  If the "/" were used I think it would be like so:
basedev=cbenable.sys /* * 0 /0 /PCIIRQ
where the "* * 0" represent the first parameter.  Its just that the first parameter requires 3 objects to represent the desired information.
From cbenable.txt (which is where I copied the above from initially):
     Examples:

       BaseDev=CBENABLE.SYS * * 0 0 10,11,12
       BaseDev=CBENABLE.SYS * * 0 0    NOIRQ
       BaseDev=CBENABLE.SYS * * 0 0   PCIIRQ
                            ^^^^^ ^      ^^^
                           Bridge Socket IRQ

<from second email>
Another question that has come up is about this statement:
"1.  First install Card Service version 5.0.
      cbenable.sys checks for version 5.00 (8.00 is broken)"

This is the first step in "Usage" for cbenable.sys.
Do you have any idea what "Card Service" is meant?
Maybe then I can find a version 5.00.
Ignore the message about 8.00, that is the version I had to install to get it to work and is the version in eCS 2.0 rc 7(and is the reason it is in eCS 2.0 rc7).
As long as you have:
BASEDEV=PCMCIA.SYS /R:500
then you should be fine in this regard... in fact, the fact that you can see the pccard via pci.exe suggests that it is fine.
Andy




Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster