Hi All
Recently i posted that I had managed to get an ArcaOS install completed almost to my satisfaction and that the Realtek nic was working fine - see last post in this thread
http://www.os2world.com/forum/index.php/topic,1407.15.htmlAt that point I was using dhcp. A little later I switched to a static ip, rebooted and had no problems.
When I booted this morning there were no connectivity problems. A friend phoned with a Win7 question around midday so I rebooted into Win7 to check how to resolve his problem. That sorted I shutdown and went for lunch.
A couple of hours later I booted ArcaOS - and discovered I had no connectivity. Booting my laptop proved the router was working so I started looking into what was wrong with ArcaOS connectivity.
What I did notice is that the lantran.log looks very different to what I expect it to look like based on logs I have seen previously - and checking against my 2 eCS volumes on this system it is definitely different. Here is that lantran.log:-
IBM OS/2 LANMSGDD [05/21/04] 6.00 is loaded and operational.
MMRE NDIS device driver @#Arca Noae LLC:0.0.5#@##1## 4 Dec 2016 21:33:03 DAZAR1 ::::5::SVN63@@RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E P
MMRE Hardware detected: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
MMRE PHY: driver=rlphy OUI=e04c MODEL=11 FAIL
MMRE PHY: driver=rlphy OUI=e04c MODEL=11 FAIL
MMRE PHY: driver=rgephy OUI=e04c MODEL=11 SUCCESS
MMRE Mac address: fc:aa:14:2f:a1:23
MMRE Setup filter interrupt 16
IBM LANPDD is loaded and operational.
IBM OS/2 TCPBEUI 6.00.0
TCPBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( May 25, 2005)
IBM OS/2 NETBIOS 4.0
Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications.
NETBIOS 4.0 is loaded and operational.
IBM OS/2 LAN Netbind
TCPBEUI: Logical adapter 0 is bound to TCP/IP interface lan0.
For comparison here is lantran.log from this boot with working connectivity:-
IBM OS/2 LANMSGDD [05/21/04] 6.00 is loaded and operational.
IBM OS/2 TCPBEUI 6.00.0
TCPBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( May 25, 2005)
IBM OS/2 NETBIOS 4.0
Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications.
NETBIOS 4.0 is loaded and operational.
MMRE NDIS device driver @#Arca Noae LLC:0.0.5#@##1## 4 Dec 2016 21:33:03 DAZAR1 ::::5::SVN63@@RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E P
MMRE Hardware detected: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
MMRE PHY: driver=rlphy OUI=e04c MODEL=11 FAIL
MMRE PHY: driver=rlphy OUI=e04c MODEL=11 FAIL
MMRE PHY: driver=rgephy OUI=e04c MODEL=11 SUCCESS
MMRE Mac address: fc:aa:14:2f:a1:23
MMRE Setup filter interrupt 16
IBM OS/2 LAN Netbind
TCPBEUI: Logical adapter 0 is bound to TCP/IP interface lan0.
This successful log is the same as those stored from last boots of eCS2.1 and eCS2.2 on this system - and connectivity works. I suspect the failed log(top) possibly indicates nic related items in the config.sys file loading in the wrong order.
Before I tried sorting out the ArcaOS connectivity problem I booted eCS2.2b2 and discovered that was also having a connectivity problem. Very strange as I had not been using eCS for a few days and had definitely not made any configuration changes during last use.
Well, I had been running Win7 when I last connected to anything so I rebooted into Win7. No problems with Win7 connectivity although it seemed to take a little longer than usual for the nic icon on the taskbar to show as connected.
Having proven the nic working I rebooted into eCS2.1 - the only OS/2 installation not tested so far. That booted fine, no problems with connectivity.
I then rebooted into eCS2.2 and connectivity had been restored.
This looks suspiciously like a windows related problem; maybe something had glitched during Win7 shutdown affecting the nic and causing the connectivity problem. I have had hardware in the past that struggled to work with OS/2 based systems and the problems had (mainly) gone away after using the hardware in windows. I can only guess that the windows driver does some sort of initialisation or reset of the hardware.
So, I can only suggest that those people struggling with Realtek nics boot into windows, if possible, to check whether the nic works with that system. If it does it may then work with OS/2 based systems.
I must admit that I did not boot into ArcaOS until I had spent a few hours rearranging the ArcaOS config.sys file to closely resemble my eCS2.2 config.sys file especially the order of nic/networking related lines. It may not have been necessary but the lantran.log now looks like I expect it to and connectivity works - although I suspect that may be more to do with having run Win7 to check that the nic works.
I hope this is of some help to other Realtek users having connectivity problems despite all drivers loading OK.
Regards
Pete