Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Pete

Pages: 1 ... 53 54 [55] 56 57 ... 87
811
Setup & Installation / Re: ArcaOS - new install (and a few questions)
« on: June 05, 2017, 01:57:53 am »
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.html

At 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






812
Networking / Re: Intel 6205 Wireless, GenMAC, GenMU Test, and ArcaOS
« on: June 03, 2017, 04:51:06 am »
Hi Eric

Sorry to read it did not work for you.The lantran.log does indicate a probable reason: the MAC address is all 0's.

I suppose the big question is: Does loading the driver turn on whatever visible indicator is used to show WiFi is on?

If it does not then I would guess that is the reason for the MAC address being 0 and that you need a later driver - the problem there is, as Doug mentioned, genmac cannot cope with the later, bigger drivers.

Yes, installing ArcaOS to a laptop/notebook will, hopefully, become a little easier when the Arca Noae wireless drivers happen.


Regards

Pete

813
Setup & Installation / Re: Bad or missing command interpreter
« on: June 03, 2017, 04:27:35 am »
Hi Paul

Not having had DOS/Win16 support installed for many years I would guess that either \os2\mdos\command.com has gone missing or this line in the config.sys file is missing/incorrect - change M: for the boot drive involved
SHELL=M:\OS2\MDOS\COMMAND.COM M:\OS2\MDOS /P


Regards

Pete

814
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 03, 2017, 12:42:36 am »
Hi All

I have now managed to get a very basic ArcaoS installation up'n'running by the simple expedient of a Custom install   deselecting all software apart from CAD, NewView and IBM Tools and Games. The result was a very basic Warp4 desktop that is being rapidly modified.

After reading a few posts about people having problems with the Realtek 8168/8111/8169 nics I must admit that I was a little concerned as this system has 1 of those - but known to be working with the Arca Noae MMRE driver already. No problems here; tcpip, File and Print Client working fine - and I've just hooked up my already installed Seamonkey to get online.

And I thought this was going to be my first ever OS/2 install failure since picking up a copy of Warp3 in 1992...

Time to go get some more Desktop customisation and already installed applications hooked up  :-)


Regards

Pete

815
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 03, 2017, 12:28:49 am »
Hi Remy

I have not seen the problem with geometry changing, no problems accessing volumes from either ArcaOS installer or when booted from either eCS boot volume on the disk. The only thing I have noticed is that my D: volume, fat32, always gets a chkdsk when booting eCS after the ArcaOS installation attempts.

What driver is involved? - if os2ahci.add then the only thing that will help is a rewrite/update of the driver based on the experience I have had with it. During my last - and most successful - install attempt I opted for System Management at the end of phase1 of install, opened a command window and deleted the just installed os2ahci.add replacing it with the version from eCS2.2beta2 - and remembered to edit config.sys to remove the /!R parameter.

End of os2ahci.add problems  :-)


Regards

Pete


816
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 02, 2017, 06:03:40 pm »
Hi roberto

The install is to a volume on a hard drive that has eCS2.1 and 2.2b2 boot volumes on it and running without problems.

I think we can discount hard disk failure and having performed multiple installations to a laptop to get a working system that I was vaguely happy with I doubt there is a dvd problem - unless I have worn it out  :-)

I currently have a partial installation on my desktop system that boots and may be something to build onto...
From the logs it is possible that the problem happened during yum/rpm software installation, \var\log\lcu.l1 seems to be where events are stored and that ends with

[Fri Jun 02 14:31:48] RPM/YUM install is starting.

All other entries have a corresponding entry "... install was successful." except yum/rpm

Anyway, I have finally found some hardware that ArcaOS installs to without any problems at all - the BIN  ;-)

Must admit to being exceedingly underwhelmed by ArcaOS.


Regards

Pete

817
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 02, 2017, 02:22:29 am »
Hi All

Have now tried using the os2ahci.add parameter /!r during installation. This does allow the installer to "see" the connected hard disks, but only Port0  on Adapter1, and installation proceeds - but not very far. The installer gave a lot of beeps at 2% and further beeps until crapping out at 10%.

Just for fun I thought I'd reset the BIOS to use native IDE and install using the danis drivers - can always change back to os2ahci later.

I did not realise the installer played tunes - Oh, hang on, it is just a continual stream of beeps. Despite all the beeps it got to reboot into phase2 where the installer crapped out at 50%.

A quick look through a few of the log files that exist does not offer any clues. Any particular logs to look for that may indicate why installation crapped out?


Regards

Pete


818
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 02, 2017, 12:21:06 am »
Hi David

I had not really looked into parameters as the eCS version does not need them. I'll have to give /!r a try as it looks like it may help. Will report back later...


Regards

Pete

819
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 01, 2017, 08:51:59 pm »
Hi All

Out of interest I copied os2ahci.add from the ArcaOS installation on my laptop to the desktop that I cannot install on and rebooted to load the driver. Result: Booted to desktop.

Double checked the driver in use:-


[L:\OS2\BOOT]bldlevel os2ahci.add



Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Arca Noae LLC:2.01#@##1## 6 May 2017 11:25:04      DAZAR1
::::::@@AHCI Driver (c) 2017 Arca Noae LLC
Vendor:          Arca Noae LLC
Revision:        2.01
Date/Time:       6 May 2017 11:25:04
Build Machine:   DAZAR1
File Version:    2.1
Description:     AHCI Driver (c) 2017 Arca Noae LLC

[L:\OS2\BOOT]



So, the driver is definitely the ArcaOS version.


Copied loaded driver detail to text file:-

[L:\OS2\BOOT]copy os2ahci$ os2ahci.trc
        1 file(s) copied.

[L:\OS2\BOOT]


The generated file os2ahci.trc contains:-

Adapter 0: PCI=0:17:0 ID=1002:4391 AMD SB700/800 irq=19 addr=0xfeb0b000 version=10200
  Port 0:
    Drive 0: 9729 cylinders, 255 heads, 63 sectors per track (76316MB) (LVM)
             Model: SAMSUNG HD080HJ                       
  Port 1:
    Drive 0: 60321 cylinders, 255 heads, 127 sectors per track (953855MB) (LVM)
             Model: WDC WD10EZRX-00L4HB0                   
  Port 2:
    Drive 0: atapi removable
             Model: HL-DT-ST DVDRAM GH24NSC0               
  Port 3:
    Drive 0: atapi removable
             Model: HL-DT-ST DVDRAM GH24NSC0               
Adapter 1: PCI=3:0:0 ID=1b4b:9172 Generic Generic irq=47 addr=0xfe810000 version=10000
  Port 0:
    No drive present



So os2ahci.add will work on an already installed system as it recognises the disks - still "loses" Adapter1 Port1 though...

The above prompts the question: Anyone have any ideas why this driver does not recognise the hard disks attached to Adapter0 Ports0 and 1 during ArcaOS install as it almost works fine added in to a working system?



@Doug
I believe that David believes he is correct. However, the very different behaviour of the 2 1.32 builds tells a different story - the binary code must be different in some way otherwise the 2 drivers would behave the same on the same hardware.



Regards

Pete




820
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 01, 2017, 07:58:10 pm »
Hi Martin

The mainboard is a Gigabyte 990FXA-UD3 with AMDFX990/SB950 chipsets

No problem with the eCS2.2beta2 supplied os2ahci.add v1.32 - connected disks are displayed, system boots with eSATA drive connected.

Using Arca Noae os2ahci.add v1.32 results in boot failing when an eSATA drive is attached - the only way to use an eSATA drive currently.

Using Arca Noae os2ahci.add v2.01 results in no connected hard disks available and Adapter1 Port1 missing - by far the worst os2ahci.add performance to date.


Regards

Pete

821
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 01, 2017, 07:47:14 pm »
Hi Rick

I do not see any point in running an operating system to run an operating system. Either ArcaOS installs to real hardware  or it does not get installed.


Regards

Pete

822
Networking / Re: Intel 6205 Wireless, GenMAC, GenMU Test, and ArcaOS
« on: June 01, 2017, 07:44:19 pm »
Hi Doug

I see from using wpiview on GenMU_INTEL_WIFI-0-4-6.wpi that the 8086:0891 also uses the netw4x32.reg and netw4x32.sys files.

As these Intel files "grow" as a result of updated and new drivers being added to what seems to be a "multipack of drivers" - the same driver file has code for a range of wireless nics - there is a chance that the advice given to Eric could work for your 8086:0891; I have just modified that post.

GENMAC2.WPI from the eCS2.2beta2 dvd/iso will also need to be installed as v2.20 releases seem to fail to load drivers they do not "know" about.

On my Intel (Dell) 5100 laptop the wireless led comes on just after genmac reports the driver as loaded.

Hopefully the eagerly awaited wireless nic drivers from Arca Noae will enable us to move on from fiddling hopefully with genmac drivers in the near future.


Regards

Pete

823
Applications / Re: ArcaOS - Dell Inspiron 1300
« on: June 01, 2017, 06:35:37 pm »
Hi Jean-Yves

The ArcaOS dvd has the 8086:4220 driver included in the genmac package [dvd]:\CID\SERVER\ARCAPKG\GENMARCA.WPI

Before attempting any form of nic install with genmac Please read the brief Howto I included in a response to Eric here
http://www.os2world.com/forum/index.php?topic=1396.msg13470 - I could not get wireless nic connectivity with driver loaded if I did not install a wireless nic during installation.


Good luck  :-)

Pete

824
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 01, 2017, 06:20:19 pm »
Hi Rick

If I installed linux on this system I would not bother running any OS/2 based system in a vm/vpc. I'm sure it would run quickly enough but I simply would not have any use for it.


Regards

Pete

825
Setup & Installation / Re: ArcaOS: Impossible to install!
« on: June 01, 2017, 06:18:10 pm »
Hi Doug

Sounds like os2ahci.add worked as it should on your systems - lucky you  :-)

Yes, BIOS disk access is set to AHCI, no the danis506.add is not in use.

As you can see from comparing output of copy os2ahci$ of the ArcaOS supplied version (v2.01 I think) which does not "see" any hard drives and also fails to "see" Adapter1 Port1 to the output of os2ahci$ v1.32 included with eCS2.2beta2 which displays connected hard disks correctly and recognises both Ports on Adapter1 there is a problem with the ArcaOS os2ahci.add driver. To clarify: the output of both drivers is on the same hardware, these are not different systems providing the output.

I have no idea why the ArcaOS version should fail so badly - but the os2ahci.add included in the Arca Noae driver pack also has problems. If I remember correctly that fails to identify Adapter1 completely - but David states that the 2 releases of os2ahci.add v1.32 are identical apart from the bldlevel info. Sorry to say but he must be wrong - possibly a different compiler switch used or other minor setting that he has forgotten about - simply because the drivers behave so differently.

I think we were hoping that problem would be resolved by the ArcaOS version...


Regards

Pete

Pages: 1 ... 53 54 [55] 56 57 ... 87