|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
| Hello, I try to activate a Nic (PCMCIA PCcard and/or Cardbus) on a portable with a chipset : Bus 6 (PCI), Device Number 1, Device Function 0 Vendor 1180h Ricoh Co Ltd Device 0476h RL5c476 CardBus Controller Command 0007h (I/O Access, Memory Access, BusMaster) Status 0210h (Has Capabilities List, Medium Timing) Revision 8Bh, Header Type 82h, Bus Latency 40h Self test 00h (Self test not supported) PCI Class Bridge, type PCI to Cardbus Subsystem ID 833810F7h Unknown Subsystem Vendor 10F7h Matsushita Electric Industrial Corp Ltd Address 0 is a Memory Address : FFF00000h, limit : 000FF000h Address 2 is an I/O Port : FFFFF000h, limit : 00000FFCh System IRQ 9, INT# A PCI bus number 6, CardBus bus number 7, Subordinate bus number 7 CardBus latency 20h New Capabilities List Present: Power Management Capability Supports power state D1 Current Power State : D0 (Device operational, no power saving) I have several nic's : Xircom Realport 2 PC Card (driver CE3NDIS.OS2 v2.9) Xircom Cardbus (driver CBENDIS v3.10) 3 com 3C589C/D Pc Card (driver ELPC3.OS2 v1.6) I can not get any nic to work. Is there someone who has such a nic working? Where can I find information what version of drivers are wright? (version of PCMCIA.SYS and IBM2SS14.SYS) Version of my warp = V4 (without any fixpack installed) Revision 9.023 On http://www.os2warp.be/index2.php?name=pcmciaentry I see that this chipset is supported in "base OS (0): Whether or not IBM OS/2 Warp 4 GA (Merlin) natively supports these chipsets" Who can give me some hints? I can not get it to work. I think basic installation is : BASEDEV = PCMCIA /R:500 BASEDEV = IBM2SS14.SYS DEVICE = C:\IBMLAN\MACS\nicdriver Do I need other lines ? regards, PHE |
| Date: 08 Apr, 2007 on 20:22 |
|
|
Premium member in user
       posts: 113 since: 04 Oct, 2006
 |
|
2. Re:PCMCIA Warp4 Ethernet |
|
|
| Date: 08 Apr, 2007 on 22:19 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
3. Re:PCMCIA Warp4 Ethernet |
|
|
I will try to apply fix 15 and DD2. I will come back when I have don this.I hope with good results. regards, |
| Date: 10 Apr, 2007 on 10:46 |
|
|
Normal member in user
     posts: 9 since: 28 Feb, 2007 |
|
4. Re:PCMCIA Warp4 Ethernet |
|
|
| I do have a Xircom and a 3C589 working on my thinkpad with Warp3 without fixpack. If you're interessted, I can post my config.sys entries when I'm back home. |
| Date: 10 Apr, 2007 on 12:29 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
5. Re:PCMCIA Warp4 Ethernet |
|
|
El Vato (08 Apr, 2007 22:19): You may want to apply fixpak 15 (< ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us >) and the Device Driver fixpak (< ftp://service.boulder.ibm.com/ps/products/os2/fixes/ddpak/xr_d002/ >) BEFORE attempting to diagnose the cause of your failures.
Applying Fix 15 : Ok. But when I try to apply fix XR_D002 : I get the message "No products where found on target system to service" Even when I copied the SYSLEVEL.OS2 from disk2 of the OS/2 install CD. What can be wrong ? regards, phe Syslevel after applying fix 15 : C:\OS2\INSTALL\SYSLEVEL.OS2 IBM OS/2 Base Operating System Version 4.00 Component ID 5639A6100 Type 0C Current CSD level: XR0M015 Prior CSD level: XR04000 C:\OS2\INSTALL\SYSLEVEL.SDS Distributed SOM Framework Version 2.01.5 Component ID 562222700 Current CSD level: SM20012 Prior CSD level: NONE C:\OS2\INSTALL\SYSLEVEL.SEM SOM Event Management Framework Version 2.01.5 Component ID 562222700 Current CSD level: SM20012 Prior CSD level: NONE C:\OS2\INSTALL\SYSLEVEL.SUT SOMobjects Utility Classes Version 2.01.5 Component ID 562222700 Current CSD level: SM20012 Prior CSD level: NONE C:\OS2\INSTALL\SYSLEVEL.SIR SOMobjects Interface Repository Framework Version 2.01.5 Component ID 562222700 Current CSD level: SM20012 Prior CSD level: NONE C:\OS2\INSTALL\SYSLEVEL.SRK SOM Run-time Kernel Version 2.01.5 Component ID 562222700 Current CSD level: SM20012 Prior CSD level: NONE C:\OS2\INSTALL\SYSLEVEL.GRE IBM OS/2 32-bit Graphics Engine Version 4.00 Component ID 5639A6100 Type 0C Current CSD level: XR04000 Prior CSD level: XR04000 C:\OS2\INSTALL\SYSLEVEL.FPK OS/2 Warp 4 Service Level Version 1.00 Component ID 566933010 Type Fixpak Current CSD level: XR0M015 Prior CSD level: XR0M015 C:\IBMLAN\SYSLEVEL.REQ IBM OS/2 LAN Requester Version 5.04 Component ID 5639A6000 Current CSD level: IP08400 Prior CSD level: IP08000 C:\IBMLAN\SYSLEVEL.PER IBM Peer for OS/2 Version 4.00 Component ID 5639A6000 Current CSD level: IP08400 Prior CSD level: IP02001 C:\MUGLIB\SYSLEVEL.UPE IBM OS/2 User Profile Management - Extended Version 5.04 Component ID 5639a6000 Current CSD level: IP08400 Prior CSD level: IP08000 C:\MUGLIB\SYSLEVEL.MUG IBM OS/2 User Profile Management Version 5.04 Component ID 5639A6000 Current CSD level: WR08400 Prior CSD level: WR08000 C:\IBMINST\SYSLEVEL.WCB OS/2 Warp Networking Services Installation Version 4.00 Component ID 5939a9200 Current CSD level: IP08400 Prior CSD level: IP08400 C:\DMISL\SYSLEVEL.DMI IBM OS/2 DMTF Service Layer Version 1.10 Component ID 576562200 Current CSD level: CA00000 Prior CSD level: CA00000 C:\JAVAOS2\BIN\SYSLEVEL.JAV Java Runtime Version 4.00 Component ID 5639B3300 Current CSD level: XR04000 Prior CSD level: XR04000 C:\JAVAOS2\DLL\SYSLEVEL.JEP JEmpower Version 4.00 Component ID 5639B3300 Current CSD level: XR04000 Prior CSD level: XR04000 C:\CID\LOCINSTU\SYSLEVEL.LCU IBM LAN CID Utility Version 5.10 Component ID 5639A5700 Current CSD level: WR08400 Prior CSD level: WR08210 C:\IBMCOM\SYSLEVEL.TRP IBM OS/2 LAN Adapter and Protocol Support Version 5.10 Component ID 5639A5700 Current CSD level: WR08400 Prior CSD level: WR08210 C:\MPTN\SYSLEVEL.DHC IBM OS/2 Dynamic Host Configuration Protocol Services Version 4.00 Component ID 562290901 Current CSD level: WR08400 Prior CSD level: WR08210 C:\MPTN\SYSLEVEL.MPT IBM OS/2 TCP/IP Stack Version 5.10 Component ID 5639B1700 Current CSD level: WR08400 Prior CSD level: WR08210 C:\IBMI18N\SYSLEVEL.I18 IBM I18N Toolkit Version 1.05 Component ID 5639A5700 Current CSD level: WR08400 Prior CSD level: WR08210 |
| Date: 10 Apr, 2007 on 19:08 |
|
|
Premium member in user
       posts: 113 since: 04 Oct, 2006
 |
|
6. Re:PCMCIA Warp4 Ethernet |
|
|
PHE (10 Apr, 2007 19:0 :
El Vato (08 Apr, 2007 22:19): You may want to apply fixpak 15 (< ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us >) and the Device Driver fixpak (< ftp://service.boulder.ibm.com/ps/products/os2/fixes/ddpak/xr_d002/ >) BEFORE attempting to diagnose the cause of your failures.
Applying Fix 15 : Ok. But when I try to apply fix XR_D002 : I get the message "No products where found on target system to service" Even when I copied the SYSLEVEL.OS2 from disk2 of the OS/2 install CD. What can be wrong ? [...]
I think you mean: " 3.0.6 CSF0208 NO PRODUCTS WERE FOUND This means no SYSLEVEL files was found that had a CSD Level, COMPID, Version and Type that matched any of the SYSLEVEL files supported by this FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2 in the OS2/INSTALL directory on your boot drive. Compare this data with the data contained in the README.1ST file on FixPak disk 1. To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2 and copy SYSLEVEL.OS2 from your Warp 4 installation DISK 1." (taken from the readme.1st of the xr_dd02 fixpak) Consequently, you have renamed <your OS/2 drive>:\OS2\INSTALL\SYSLEVEL.OS2 to (say) SYSL.OS2 and copied over to the <your OS/2 drive>:\OS2\INSTALL directory the file SYSLEVEL.OS2 from your OS/2 installation diskette 2 (I did not find it in diskette 1 either, by the way). ...correct  |
| Date: 11 Apr, 2007 on 06:12 |
|
|
Premium member in user
       posts: 113 since: 04 Oct, 2006
 |
|
7. Re:PCMCIA Warp4 Ethernet |
|
|
last updated at 11 Apr, 2007 08:10 (1 times)
PHE (08 Apr, 2007 20:22): [...]On http://www.os2warp.be/index2.php?name=pcmciaentry I see that this chipset is supported in "base OS (0): Whether or not IBM OS/2 Warp 4 GA (Merlin) natively supports these chipsets" Who can give me some hints? I can not get it to work. I think basic installation is : BASEDEV = PCMCIA /R:500 BASEDEV = IBM2SS14.SYS DEVICE = C:\IBMLAN\MACS\nicdriver Do I need other lines ? regards, PHE
Generally, you are advised to remove the built in PCMCIA support that is includded with the original installation of your OS/2 Warp 4. You can do so from the utility in your OS/2. Reboot your machine after you remove the old built-in support. After reboot make a backup of your CONFIG.SYS. Subsequently, you will reinstall support (read: newer drivers than those with the original built-in PCMCIA support) with PcCard Director 5 whose link at hobbes is given in prior post. After you explode the file in a temporary directory, read the instructions in the readme files and browse the EN directory. There is an executable file PCMINST2.EXE that will install CardBus support, etc. and will modify your CONFIG.SYS for you. Below is a portion of a previous eMachines laptop OS/2 CONFIG.SYS that I used to have (note that this is only part of the full modification on my root drive F:): BASEDEV=PCMCIA.SYS REM El Vato removed this IBM PcCard Director driver: BASEDEV=IBM2SS14.SYS in favour of Daniela's hack from www.OS/2WARP.be: (below): BASEDEV=SS2TICB.SYS BASEDEV=AUTODRV2.SYS DEVICE=F:\THINKPAD\VPCMCIA.SYS DEVICE=F:\THINKPAD\PCMSSDIF.SYS DEVICE=F:\THINKPAD\PCM2SRAM.SYS DEVICE=F:\THINKPAD\FLSH2MTD.SYS DEVICE=F:\THINKPAD\PCM2FLSH.SYS rem El Vato's modification: BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP BASEDEV=PCM2ATA.ADD /S:1 /!DM /NOBEEP You simply have to make sure (by opening your CONFIG.SYS in a text editor subsequently) that your PCMCIA.SYS is read BEFORE DEVICE=F:\OS2\BOOT\COM.SYS
Sometimes (especially if you encounter errors upon a subsequent reboot after reinstallation of your PcCard support) you must verify that the modifications to your OS/2 CONFIG.SYS have been done properly. For instance, DEVICE paths are not reflected appropriately in certain cases and make sure that your newly installed BASEDEV drivers are in your <your OS/2 root drive>:\OS2 or <your OS/2 root drive>:\OS2\BOOT directories so that the OS/2 bootstrap routine will find them. (read the documentation) In short, if your PCMCIA support does not work with the IBM ThinkPad driver (highlighted in red above, in the portion of the CONFIG.SYS) and you find a driver hacked for your specific chipset in your machine, REMming out the IBM ThinkPad driver and inserting your alternative one will solve your problem (hopefully . Best of luck ! P.S. Accept Andi's offer to show you his appropriate portion of his working CONFIG.SYS He is got one of the drivers that you are interested --even if your respective machine chipsets (consequently ThinkPad versus other brand drivers) are different, the NIC portions in the OS/2 CONFIG.SYS will be similar. |
| Date: 11 Apr, 2007 on 07:22 |
|
|
Normal member in user
     posts: 9 since: 28 Feb, 2007 |
|
8. Re:PCMCIA Warp4 Ethernet |
|
|
| Sorry, it tooks a while, but here's what I think are the relevant config.sys entries - BASEDEV=PCMCIA.SYS DEVICE=E:\OS2\MDOS\VPCMCIA.SYS .. DEVICE=E:\OS2\BOOT\AUTODRV2.SYS E:\OS2\AUTODRV2.INI BASEDEV=IBM2SS01.SYS /s0=2 /IG0=2 .. DEVICE=e:\IBMCOM\MACS\XPSNDIS.OS2 DEVICE=E:\IBMCOM\MACS\ELPC3.OS2 I've the 3Com 3C589D Combo and a Xircom 'CreditCard Ethernet+Modem' (never tested the modem part) installed and tcpip works on both. |
| Date: 11 Apr, 2007 on 21:17 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
9. Re:PCMCIA Warp4 Ethernet |
|
|
last updated at 12 Apr, 2007 11:38 (2 times)
Andi (10 Apr, 2007 12:29): I do have a Xircom and a 3C589 working on my thinkpad with Warp3 without fixpack. If you're interessted, I can post my config.sys entries when I'm back home. BASEDEV=PCMCIA.SYS DEVICE=E:\OS2\MDOS\VPCMCIA.SYS .. DEVICE=E:\OS2\BOOT\AUTODRV2.SYS E:\OS2\AUTODRV2.INI BASEDEV=IBM2SS01.SYS /s0=2 /IG0=2 .. DEVICE=e:\IBMCOM\MACS\XPSNDIS.OS2 DEVICE=E:\IBMCOM\MACS\ELPC3.OS2
Hello Andi, When you post your config.sys, protocol.ini and IBMLAN.ini. I can compare it with mine. What is the version of your PCMCIA.SYS ? What is the PCMCIA-chipset ? What is the version of IBM2SS01.sys you use? BASEDEV=IBM2SS01.SYS /s0=2 /IG0=2
How many PCMCIA-slots do you have? Your Xircom-card : in what slot is it inserted? /IG0=2 : Does this not mean : no Socket Service support from adapter 2? So from adapter 2 you can use drivers with Point Enablers (as Xircom-drivers are)? regards,
|
| Date: 12 Apr, 2007 on 11:25 |
|
|
Normal member in user
     posts: 5 since: 15 Nov, 2006 |
|
10. Re:PCMCIA Warp4 Ethernet |
|
|
| I remember older xircom modem/network cards would only work if they were point enabled. You will need to modify IBM2SS14.SYS (BASEDEV=IBM2SS14.SYS /IG0=1) to keep card services from trying to mess with it. Point enabled means you are not using card services to manage the card. David |
| Date: 12 Apr, 2007 on 12:30 |
|
|
Normal member in user
     posts: 9 since: 28 Feb, 2007 |
|
11. Re:PCMCIA Warp4 Ethernet |
|
|
PHE (12 Apr, 2007 11:3 : When you post your config.sys, protocol.ini and IBMLAN.ini. I can compare it with mine.
I can post it if you like. But as I stated above, it's Warp3, no fixpack, but LanServer5.0 on top of that. I try to respond this or next evening when I'm at home.
What is the version of your PCMCIA.SYS ? What is the PCMCIA-chipset ? What is the version of IBM2SS01.sys you use?
It's an old Thinkpad TP365. Honestly I do not know very much about all this PCMCIA stuff and I've no clue which chipset is used there. But will post what buildlevel will show.
BASEDEV=IBM2SS01.SYS /s0=2 /IG0=2How many PCMCIA-slots do you have? Your Xircom-card : in what slot is it inserted? /IG0=2 : Does this not mean : no Socket Service support from adapter 2? So from adapter 2 you can use drivers with Point Enablers (as Xircom-drivers are)?
2 slots. I think the 3Com is in the first slot, it's the top one, and the Xircom is in the second below the 3Com. I think I've added /IG0 because I read it in the Xircom Manual. Yes, this old card manual do have a chapter dealing with OS/2. As I remember correct, I use the original Xircom driver which comes with the disk. I can nothing say about 'Socket Service' or 'Point Enablers' cause lack of knowlegde. Although I use pcs for more than 20 years, I hardly deal with notebooks. |
| Date: 13 Apr, 2007 on 09:00 |
|
|
Normal member in user
     posts: 9 since: 28 Feb, 2007 |
|
12. Re:PCMCIA Warp4 Ethernet |
|
|
| Date: 13 Apr, 2007 on 22:21 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
13. Re:PCMCIA Warp4 Ethernet |
|
|
last updated at 18 Apr, 2007 08:01 (1 times) Hi Andi,Sorry for the late reply. I was searching trying, searching, trying, and so on. I all of a sudden got succes. It was with a portable with 512 Meg with Warp 4 fix 15 installed and with O2Micro chipset OZ711M3. There are 2 PCMCIA slots. Xircomcard is in the bottom slot. (is this 0? or 1 or 2 ? ? I do not know how I can find this out) I was using PCMCIA bldlevel 10.056 ! ! and CBENDIS version 3.10 I entered only BASEDEV=PCMCIA.SYS /R:500 I tried with IBM2SS14.SYS version 10.148 also (but this with the parameter /IG0:1 I do not get success) IBM2SS14.SYS line must be remmed out !
Protocol.ini had only the protman section and the [Xir_nif] section. In the [Xir_nif] section there is only one line : Drivername = Xircom$.
IBMLAN.ini is empty. (for the moment) I will try to redo my actions to confirm that my experiance is wright.
I did the same actions on an other PC with OS2 warp 4 (with and with fix 15) with a Ricoh R/RL/5C476 (II) chipset, but here I do not have success ! ! Even with PCMCIA.SYS 10.148. When I use SSPCIC.SYS driver, I get some more information about my slots. But I still get the message back from CBENDIS.OS2 driver "A card was not detected in the selected slot" I think the parameters of SSPCIC are not exact. But how can I find out what the right parameters are? I used /E /MS0:1 /vs:auto /ap:on Any suggestion? regards, |
| Date: 17 Apr, 2007 on 19:59 |
|
|
Normal member in user
     posts: 9 since: 28 Feb, 2007 |
|
14. Re:PCMCIA Warp4 Ethernet |
|
|
| One of the PCMCIA tools in my warp3 installation detects card 1 (3Com) but says 'no card detected' for the second slot. But the xircom beeing in there works. |
| Date: 18 Apr, 2007 on 13:32 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
15. Re:PCMCIA Warp4 Ethernet |
|
|
Andi (18 Apr, 2007 13:32): One of the PCMCIA tools in my warp3 installation detects card 1 (3Com) but says 'no card detected' for the second slot. But the xircom beeing in there works.
That is because of Xircom cards (networkcards) work with point enabler driver. Notmaly they do no need any card- and service socket drivers. I have the same experiance with and older machine (Digital Highnote). Here my Xircom card works with only the Xircom-driver loaded (no card- and/or socket services !). I guess it is because of the chipset used in the PC. (in the Highnote is an old one and this is probably compatible with the point enabler of the xircom-driver) With newer machines I get problems. Compaq HP nc 6000 : chipset OZ711M3 I found out that PCMCIA.SYS /r:500 is needed. No socket driver is needed here. Regards, |
| Date: 19 Apr, 2007 on 07:10 |
|
|
Premium member in user
       posts: 145 since: 20 Jan, 2003 |
|
16. Re:PCMCIA Warp4 Ethernet |
|
|
PHE (19 Apr, 2007 07:10): That is because of Xircom cards (networkcards) work with point enabler driver. Notmaly they do no need any card- and service socket drivers.I have the same experiance with and older machine (Digital Highnote). Here my Xircom card works with only the Xircom-driver loaded (no card- and/or socket services !).
I have used three or four different Xircom RealPort or RealPort2 cards (don't trip over a network cable plugged into one). None needed all of the PCMCIA drivers for the network to run. And at least one wouldn't finish booting when it was installed. The worst was a combo network & modem that needed all PCMCIA drivers installed for the modem to work, but crashed during the boot when loading the network drivers. Luckily, when I had this one I rarely needed to use the modem.
---
David
|
| Date: 20 Apr, 2007 on 02:26 |
|
|
Normal member in user
     posts: 42 since: 07 Aug, 2003 |
|
17. Re:PCMCIA Warp4 Ethernet |
|
|
last updated at 21 Apr, 2007 18:51 (1 times)
davidfor (20 Apr, 2007 02:26): I have used three or four different Xircom RealPort or RealPort2 cards (don't trip over a network cable plugged into one). None needed all of the PCMCIA drivers for the network to run. And at least one wouldn't finish booting when it was installed. The worst was a combo network & modem that needed all PCMCIA drivers installed for the modem to work, but crashed during the boot when loading the network drivers. Luckily, when I had this one I rarely needed to use the modem.
I thingkit is releated to the chipset in the PC. Can you figure out what chipset is used? regards, |
| Date: 21 Apr, 2007 on 12:03 |
|
|
Premium member in user
       posts: 145 since: 20 Jan, 2003 |
|
18. Re:PCMCIA Warp4 Ethernet |
|
|
last updated at 24 Apr, 2007 01:42 (1 times)
PHE (21 Apr, 2007 18:51):I thingkit is releated to the chipset in the PC. Can you figure out what chipset is used?
I don't believe the crashes I have seen are directly related to the PCMCIA chipset. As someone mentioned, XIRCOM network cards have tended to use "point enabled" drivers. With these drivers, not all of the OS/2 PCMCIA drivers are needed. I think the important difference is that the cards that worked with the full driver set are CardBus cards (the current one I am using is). It may be as simple as the XIRCOM drivers for these cards were better than the older ones. And the obvious question is which part of the drivers are not needed. Working from memory, the driver IBM2SS14.SYS (or equivalent for the PCMCIA chipset) is needed. The driver PCMCIA.SYS can be removed. Or, the parameters can be changed so that it ignores the slot the XIRCOM card is using. I always commented the driver out as the XIRCOM cards I have used block both slots. Later on: I had my laptop in Win2000 when I wrote the above. I later rebooted to OS/2 and looked at the config.sys. Much to my surprise, all the PCMCIA related drivers were commented out. So, these XIRCOM cards run without any OS/2 PCMCIA support. I uncommented the PCCMIA.SYS, IBM2SS14.SYS and VPCCMIA.SYS statements and rebooted and the network keeps running. The only problem is that when I opened "Card Director", it shows the card as a memory device.
David
|
| Date: 23 Apr, 2007 on 04:43 |
|
|
|
|
| All times are CET+1. |
< Prev. | P. 1 | Next > |
|