OS2World OLD-STATIC-BACKUP Forum

OS/2 - Technical => Hardware => Topic started by: OriAl on 2010.11.18, 03:22:59

Title: major trouble after motherboard swap
Post by: OriAl on 2010.11.18, 03:22:59
My friend swapped out my 32 bit motherboard for a 64 bit Asus MA489GTD Pro motherboard.  Bios was set for native IDE for the controller.  After motherboard change, nothing would boot.  Boot Manager on drive 1came up, but when eCS (1.2) was selected, the computer immediately rebooted every time.  Not even a glimpse of the eComStation screen.  XP showed the Windows screen, then died.  Both are on disk 1.  Ubuntu 8.04, which I had on a small second drive and had looked at occasionally, showed the welcome screen, but died soon after.  

I'm currently on a reinstall of XP on a new drive.  My friend has my other drives, motherboard, and cards, and plans to build a test machine with them to see if the OS's will still boot with the old configuration.  I'd like to get at least my old eCS on old drive 1 working with the new motherboard.  Any ideas?

Thank you.
Title: Re: major trouble after motherboard swap
Post by: ivan on 2010.11.18, 10:02:52
You did update the Dani drivers to the latest before you tried to boot off the new system didn't you?  If not you will have boot from CD and add them.

ivan
Title: Re: major trouble after motherboard swap
Post by: Fahrvenugen on 2010.11.19, 06:50:36
In addition to the Danis driver(s), make sure you're on the latest kernel.  Try the 14.104a_uni kernel from

http://www.os2site.com/sw/upgrades/kernel/

I seem to recall eCS 1.2MR shipped with an earlier kernel that didn't have all the stuff to work on 64 bit processors.

And, depending on what video driver you were using, you'll possibly have to revert back to VGA mode to make it work.
Title: Re: major trouble after motherboard swap
Post by: Andi on 2010.11.19, 14:12:47
eCS2.0 is shipped with/will install SMP kernel and there are reasons for that I do not remember any more. Suggest you try the SMP kernel not the UNI.
Title: Re: major trouble after motherboard swap
Post by: Fahrvenugen on 2010.11.19, 17:16:20
The reasons that eCS 2.0 shipped with the SMP kernel is for multi-core / multi-processor support and ACPI.

It is true that the SMP kernel will work with a uni processor, *but*, to use the SMP kernel you'll need the SMP-enabled Doscall1.dll from WsEB, otherwise you'll probably get a trap error.  It is possible to find this file within the public WsEB fixpaks on IBM's ftp sites.

And even if it is a multi-core processor, the cores may not be recognized unless you have the os2apic.psd or the acpi driver (shipped with ecs 2.0)

On the other hand, the Uni processor should work.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.19, 19:46:10
I believe I had updated to the latest Dani driver when it was released, but with my memory, I could be wrong.  

The eCS version should be 1.2R.  I thought I had kept up with all fixes.  

Thanks for the ideas - I'll pass them on to my friend.

Assuming I get eCS booting, is there a driver for the Realtek 8111E LAN chipset?
Title: Re: major trouble after motherboard swap
Post by: DougB on 2010.11.19, 20:22:32
Quote
Assuming I get eCS booting, is there a driver for the Realtek 8111E LAN chipset?

You need to know the PCI identifier. Something like "10EC:8168". PCI.EXE will tell you that information.

Chances are good that GENMAC will support it (possibly in UNSUPPORTED mode), but there is probably a better chance that the new Realtek NIC driver, that Mensys is developing, will support it (when it is ready).

FWIW, the SMP kernel (with proper supporting software - DOSCALL1.DLL - which comes with the SMP kernel) should work for all Pentium, and up, systems. Sometimes, it is even a good idea to run a single processor machine in SMP mode (Add "/SMP /APIC" to the ACPI.PSD line in CONFIG.SYS). My ThinkPad (T43 1871-W8M) works better that way.
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.20, 22:34:49
And finally, keep in mind that multiple components may need to be upgraded at the same time to prevent other issues. JFS, SMP, DOSCALL1 and some networking stuff (sockets/stack related) should be replaced with the prerequisite versions each requires. Usually the readme files that accompany the downloadable versions of each component will tell you what other components need to be upgraded, and to what level they are needed. For instance, a great way of causing problems for oneself it to upgrade the original JFS without upgrading the original kernel.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.21, 02:08:48
Switching to the SMP kernel sounds complicated.  I'd rather get what I have booting.

 
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.21, 02:21:36
Switching to the SMP kernel sounds complicated.  I'd rather get what I have booting.

 

OS2MT/eCSMT and (someplace out there - Hobbes I think) make it pretty painless. Starting with the kernel and it's related files (which can be found in a package) and continuing from there is usually a safe bet.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.22, 21:28:02
Even if I (or my friend) get the needed files,  how would eCSMT be used if eCS won't boot?  IS eCSMT usable from the CD?

I admit to being totally lost.
Title: Re: major trouble after motherboard swap
Post by: Andi on 2010.11.23, 09:10:46
I vaguely remember I couldn't install one of the 2.0rc versions because of the UNI kernel. I think I filled a bug for that. Solution was - using SMP kernel. Your problem reminded me the troubles I had at that time and so I suggested SMP instead of UNI cause it was definitely the solution. On the other hand, if you've a working system with UNI kernel and don't want to benefit from the extra cores you already bought you can stick with UNI or W4 kernel if you like.
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.24, 18:16:44
Even if I (or my friend) get the needed files,  how would eCSMT be used if eCS won't boot?  IS eCSMT usable from the CD?

I admit to being totally lost.

Sorry... should have replied in more detail...

IF you have another eCS or OS/2 machine, you can use eCSMT/OS2MT to download the files you need and then extract them. Boot your non-working eCS install from the CD and go to commandline and add/replace the needed files, and modify the config.sys

Failing that, search Hobbes for the necessary files, read the readme files to ensure you have all the prerequisites, and install them onto the non-bootable system in the same fashion as above. They should mostly be packaged in zip files, so you can do this one on any machine that has a zip/unzip utility.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.28, 02:09:25
I can't find any kernel files on Hobbes when I search for SMP.

If we put the old drive with eCS back in my machine, maybe I can just install eCS 2.0?  If that succeeds, is there a way to get my desktop from the 1.2 boot partition?
Title: Re: major trouble after motherboard swap
Post by: IBManners on 2010.11.28, 09:08:06
Hi,

Kernels can be found here :-
http://www.os2site.com/sw/upgrades/kernel/index.html (http://www.os2site.com/sw/upgrades/kernel/index.html)

and several other websites.

I thought I had it some were but cant spot it at present, a file with a quick
walk thought of whats needed to change from a UNI to a SMP setup.

Cheers
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.28, 09:49:43
Hi,

Kernels can be found here :-
http://www.os2site.com/sw/upgrades/kernel/index.html (http://www.os2site.com/sw/upgrades/kernel/index.html)

and several other websites.

I thought I had it some were but cant spot it at present, a file with a quick
walk thought of whats needed to change from a UNI to a SMP setup.

Cheers

I too am looking for it. There's a kernel installer out there that actually will swap all the required files. I've used it before, so I know I have it someplace, but still cannot find it.

If I dig it up, or figure out where I found it, I will post here.

-R
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.28, 09:58:48
Instructions (ie: the commands to execute) are located in the latest kernel's readme file. Ensure you have zip support on the system.

(for SMP) If memory serves, you will need SMP version of DOSCALL1.DLL, and OS2APIC.PSD, and the files that come in the kernel pack.

Boot off CD, have the files handy and unzipped. Follow the instructions in the readme that comes with the kernel (that will replace all the necessary files in that respect).

Install OS2APIC.PSD, add it to the config.sys file thusly:
PSD=OS2APIC.PSD /p:1

Replace DOSCALL1.DLL

Doubt the SMP versions of DOSCALL1 comes with eCS... but you will need to find the most recent versions of those two files (DOSCALL1 and OS2APIC).



Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.28, 21:20:00
Would it be better to try to migrate eCS 2.0 onto the partition on the other drive that currently has my non-booting eCS 1.2 (I have a backup clone of that partition on the same drive?)  Being that I have the eCS 2.0 CDs, and was going to install it anyway, it seems that might be a way to go.  2.0 should boot on 64 bit motherboard, I would hope.
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.28, 22:12:33
Would it be better to try to migrate eCS 2.0 onto the partition on the other drive that currently has my non-booting eCS 1.2 (I have a backup clone of that partition on the same drive?)  Being that I have the eCS 2.0 CDs, and was going to install it anyway, it seems that might be a way to go.  2.0 should boot on 64 bit motherboard, I would hope.

Probably, as SMP will then be an option. And it should work with a decent number of 64bit motherboards.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.11.30, 04:19:04
Thank you.  Are there any installation tips I could use?  I will have the current drive with XP, as well as the drive with eCS.  There are several HPFS partitions on that drive - I would want to migrate 2.0 to the first partition.  My memory is so bad, I can't remember how I installed 1.2.
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2010.11.30, 04:28:04
Thank you.  Are there any installation tips I could use?  I will have the current drive with XP, as well as the drive with eCS.  There are several HPFS partitions on that drive - I would want to migrate 2.0 to the first partition.  My memory is so bad, I can't remember how I installed 1.2.

Please explain a little more about your setup:
(1) PHY drive setup (qty, location of XP, location for eCS)
(2) Partitioning information (how are you managing multi-OS boot? what partitions exist (or will) on each? what filesystems exist (or will) on each?)
(3) If you are not sure if you had to install additional drivers for the original eCS install, list some hardware specifics (chipsets, CPU, video, NIC, etc)

Best,
Rob
Title: Re: major trouble after motherboard swap
Post by: Fahrvenugen on 2010.11.30, 07:01:12
Instructions (ie: the commands to execute) are located in the latest kernel's readme file. Ensure you have zip support on the system.

(for SMP) If memory serves, you will need SMP version of DOSCALL1.DLL, and OS2APIC.PSD, and the files that come in the kernel pack.

Boot off CD, have the files handy and unzipped. Follow the instructions in the readme that comes with the kernel (that will replace all the necessary files in that respect).

Install OS2APIC.PSD, add it to the config.sys file thusly:
PSD=OS2APIC.PSD /p:1

Replace DOSCALL1.DLL

Doubt the SMP versions of DOSCALL1 comes with eCS... but you will need to find the most recent versions of those two files (DOSCALL1 and OS2APIC).


Hi,

For those files, you can find the SMP version of Doscall1.dll from the WsEB / Warp 4.5 fixpak xre_003, which is still available from IBM.  Of course, the license for this fixpak does require you to have a licensed copy of WsEB.  However it has been reported that these files also work on eCS, and it is available on anonymous FTP from IBM.

ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_e003/

You'll need disks 10, 13, and 14.

10:
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_e003/xr_e003a.zip

13:
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_e003/xr_e003d.zip

14:
ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_e003/xr_e003e.zip

From the readme file (on disk 1):
   OS2APIC.PSD   OS2APIC.PS_    14    02/13/2002  14:23    31232  CD86A06D
  DOSCALL1.DLL  DOSCALL1.SM_   10    02/13/2002  14:21   144387  E2D6BF8B
   DOSCALL1.DLL  DOSCALL1.UN_   10    02/13/2002  14:12   137445  44BCBD46
   DOSCALL1.SYM  DOSC1SYM.SM_   13    02/13/2002  14:21    43828  7FF7880A
   DOSCALL1.SYM  DOSC1SYM.UN_   13    02/13/2002  14:12    43476  BED7692E

You'll need to expand the .??_ files, obviously the .sm_ is for the smp kernel, the .un_ is for the uni processor kernel.  You'll need the DLL and the SYM files for Doscall1 and the PSD driver.


Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.12.01, 01:06:12
Thank you.  Are there any installation tips I could use?  I will have the current drive with XP, as well as the drive with eCS.  There are several HPFS partitions on that drive - I would want to migrate 2.0 to the first partition.  My memory is so bad, I can't remember how I installed 1.2.

Please explain a little more about your setup:
(1) PHY drive setup (qty, location of XP, location for eCS)
(2) Partitioning information (how are you managing multi-OS boot? what partitions exist (or will) on each? what filesystems exist (or will) on each?)
(3) If you are not sure if you had to install additional drivers for the original eCS install, list some hardware specifics (chipsets, CPU, video, NIC, etc)

Best,
Rob

It was two drives before.  eCS and XP were on the first, an old Ubuntu install I rarely looked at was on the second drive (I'm not worried about that.)  Boot Manager was used.  There are lots of HPFS partitions - C: - L:.  C: through I: are 2 G each, J: through L: are 20 G each.  Also two hidden 2 G partitions.  XP was on a 57 G NTFS partition at the end of the drive.  That's the drive I will get back and want to migrate eCS 2.0 onto C:.  

Both drives were IDE.  Current drive is IDE.  My friend is trying to copy my eCS drive onto a SATA drive.

The motherboard was an Abit KX7-333 with Athlon 2600 CPU, ATI Radeon Video Card, Intel NIC.  No sound - I had uninstalled SBLive driver. SNAP graphics.

Right now, I have one drive with XP on a 100 G NTFS partition.  We know boot.ini will need to be edited.

New motherboard is Asus MA489GTD Pro.  Chipsets are   North Bridge and AMD 890GX South Bridge AMD SB850.
Video is ATI Radeon HD 4290.  Audio is Realtek ALC892. NIC is Realtek 8111E.  CPU is AMD Athlon II X4 640.

This is the url of the new motherboard in the machine, if that helps.

http://www.newegg.com/Product/Product.aspx?Item=N82E16813131631&cm_re=m4a89gtd_pro-_-13-131-631-_-Product
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.12.08, 20:55:49
I haven't gotten my eCS drive back yet, so nothing has been tried.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2010.12.26, 23:20:20
If my friend builds a computer with my old drive, motherboard, and add-on card cards, will he be able to migrate 2.0 onto my 1.2 boot partition using the SMP kernel option?  If so, would that 2.0 install work with my new motherboard (it has ATI graphics, like my old video card, and I was using SNAP?)
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2011.01.20, 21:00:09
We're still stuck.  My friend hasn't had much chance to work on things.  I thought I could use DFSEE to create an HPFS partition on the IDE drive I currently have (100G NTFS XP install on it, and a good amount of free space), and try to install 2.0 clean to it, with Bootmanager.

Right now, Windows is not finding my external floppy drive.  Actually, it finds the drive (says TEAC USB drive), but doesn't operate it (no floppy drive under drives, can't access it from command prompt.)  I've uninstalled and reinstalled the drive, checked for updated drivers, scanned for new hardware, but no joy.  I need that just to try an install - my eCS key is on a floppy. 
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2011.01.27, 02:18:10
Well, the floppy shouldn't be a deal breaker for the install. You can manually type the key, or move the file to the CD (a copy of the CD) with an ISO editor.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2011.01.30, 20:36:13
Update - I got 2.0 to install on my current drive.  I can't do anything with it, however.

> I used Dfsee to delete both the 1992M and BM I had created w/ Dfsee,
> >booted the 2.0 CD, started install, used miniLVM to create BM first (at
> >beginning of Freespace), then a 1992M bootable partition.  No LVM error.

> >I continued installation, and it worked.  I have no network connection
> >or printer or sound, but eCS 2.0 does boot, and so does XP.  So, the 64
> >bit motherboard and multi-core CPU aren't the problem, apparently.

One minor problem - before Boot Manager appears, I get an error message "Drive 1 is not ready."  I only have one hard drive at the moment.  Hitting a key continues the boot to BM.

I told my friend this, and he's bringing back my old disk to see if we can find a way to get 2.0 to recognize the partitions on that drive, and allow me to migrate 2.0 over my old 1.2 setup.  We already know 1.2 won't boot on this motherboard and CPU.

I don't know if 2.0 doesn't recognize Dfsee-created partitions as installable, but Jan van Wilk says that has never been a problem.


Title: Re: major trouble after motherboard swap
Post by: DougB on 2011.01.30, 22:48:41
Quote
I don't know if 2.0 doesn't recognize Dfsee-created partitions as installable, but Jan van Wilk says that has never been a problem.

I have seen it. It happened on my Lenovo ThinkPad T510, with 500 GB disk. It seems to be the result of Win7 creating an incompatible geometry, that eCS simply refuses to (can't) use. From what I have seen, it is caused by 32 meg cylinders. I got around it by fooling windows into thinking that it was installing to a smaller disk (but my method probably won't work for your situation). See:
http://hobbes.nmsu.edu/download/pub/os2/doc/Taming_Win7_v0_1.zip (http://hobbes.nmsu.edu/download/pub/os2/doc/Taming_Win7_v0_1.zip)
which tells you what I did about it.

DFSEE was able to create partitions, and I could even use the eCS install CD to format them, as JFS, but MiniLVM complained about a partition table error, and refused to enable the install. I also cannot restore eCS data to such a geometry. It starts, but fails quickly, and the data that did get restored is scrambled. I did use DFSEE to wipe the whole disk, and then create new partitions, and then eCS would install, but I never found a way to make Win7 work with that setup. WinXP also had trouble.

Quote
"Drive 1 is not ready."

I have seen that too. In my case, it is caused by trying to boot with a USB disk, that doesn't have a boot system on it, attached at boot time. IMO, that is a flaw in the BIOS boot code. However, you may be seeing something different. One possible fix, is to disable Legacy USB mode, in the BIOS. That will disable the use of USB keyboard, and mouse, until the proper drivers get loaded though. A PS/2 keyboard will work.

Quote
booted the 2.0 CD, started install, used miniLVM to create BM first (at beginning of Freespace),

It has been my experience, that it is always MUCH better to put Boot Manager right at the very end of the disk. Doing that allows you to make the first partition a primary for windows, with enough room for a hibernation file (if you can get that to work). So far, I have never had any luck with hibernation, unless it can build a file on a FAT, FAT32, or NTFS, drive, that is FIRST on the disk. Even windows doesn't work if it can't find the room on the fist primary. If you put BM at the front of the disk, that is the first primary, and it certainly doesn't have either the room, or the file system, to allow a hibernation file to be created. Placing BM at the end of the disk keeps it out of the way, and it works, as long as you have the BM that supports the I13x extensions, AND, the disk is something less that about 500 GiB. BM does have problems with larger disks, no matter where you put it. It does work, but it doesn't get set up right.

Quote
We already know 1.2 won't boot on this motherboard and CPU.

It probably will, if you have every update, that is available, installed.

Quote
allow me to migrate 2.0 over my old 1.2 setup

Personally, I have never seen a migration install worked anywhere near correctly. On the surface, it seems to be a good idea, and it looks like it works, but under the covers, it leaves a terrible mess, that you will probably never be able to clean up. I also find that it is MUCH faster, and easier, to simply re-install all of the software, than to try to figure out what the migration install did, or didn't do, when it did the migration. You will need to re-install some of it anyway.

Quote
So, the 64 bit motherboard and multi-core CPU aren't the problem, apparently.

So far, all 64 bit CPUs can run in 32 bit mode, and OS/2 has had multi CPU support for a long time.

My bet is that your main problem is the geometry on the disk. You will probably have to wipe it clean, and recreate the partitions, preferably using either MiniLVM, or DFSEE. You will likely have problems with that, if the disk is larger than about 500 GB too.
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2011.02.27, 00:24:54
I now have my old drive back - it's the second drive on the controller.  The 2.0 install does see all the HPFS partitions on it, with proper drive letters.  However, I really need to migrate, as there are apps for which I no longer have install disks which are installed in 1.2 (I'd also like to find all the files folks have mentioned which are needed to get 1.2 to work on this motherboard - if I try to boot 1.2, the system immediately resets.)

So, assistance with migration is greatly needed.  I've tried it a couple of times, but I don't get internet connectivity (my Intel Pro 10/100 NIC is still connected) or printer access.  I do have a router attached.  I don't recall the names or ip addresses network install asks for (if I could get 1.2 working, I could see them.)  It does find the 10/100 as well as the built-in NIC, and installs Genmac for both.)

I have a Kensington Expert Mouse trackball (I'm disabled, so it's easier than a mouse), so I don't need the Amouse driver that's installed.  I also have a tape drive, and still used Fastback to back up eCS 1.2.  I was using SNAP graphics, but I understand Panorama is better for 2.0, so I went with that in the test migrations.  I also have an external tape drive, but Dfsee for OS/2 can't access it (DFseewin does, so I can save partition images of eCS on it.)

For some reason, I can only install or migrate 2.0 onto drive 1, the primary.

I'm not booting with a USB disk, so that shouldn't cause "Drive 1 is not ready, press a key" before Boot Manager appears.  I can move BM to the end of the disk using DFSEE, though XP is already the first partition on drive 1.
Title: Re: major trouble after motherboard swap
Post by: ivan on 2011.02.27, 02:00:58
Hi OriAl,

A couple of comments. 
The Kensington Expert Mouse trackball works with the Amouse driver with out any problems - I know because I use them both, been using a trackball from the days when we had massive units that had either 4" or 6" balls - in fact I hate mice.

Since you can see your old drive use a file manager like FM/2 or File Freedom to look at each of the directories of your old installed software.  Some of them may have cmd files for restoring the desktop objects.  If so you can then copy those dirs over to your new drive and create the objects - no migration needed.  If they don't have scripts for recreating the objects, all is not lost because you can create them manually.  The only possible problem you may encounter is if the install program has put some DLL in an odd place but even this can be checked by starting the program from a command prompt - it will tell you what it can't find if it does not run.

I assume your router is set up to be a DHCP server therefore you shouldn't require to know anything - just say it is DHCP and the network install should get the necessary address from the router.  If on the other hand your router is set up for fixed addresses then you need to look in IBMCOM and IBMLAN and MPTN\ETC for the necessary information.

I can't say much about the eCS install as we don't have it here but I have recently built an AMD Athlon II x4 box and shifteb over everything from the box it replaced via the NAS (saved having to mix IDE and SATA drives).  All I did was a fresh install of WSeB and then copied everything from the NAS  ran ROBO RESTORE  and had 99% of the desktop back as it was, a couple of manual object creations solved the remainder.

For you information I'm using SNAP graphics driver and a 28" 1920x1200 monitor - see pics of mboard and monitor.

Title: Re: major trouble after motherboard swap
Post by: OriAl on 2011.03.02, 02:01:19
Will Amouse allow me to set the top buttons as locked down?  I need that setting.  Kensingnton's driver has that setting.

What is NAS and Robo Restore?

I'm still going to play with migration, but should I use Easy or Advanced Install?
Title: Re: major trouble after motherboard swap
Post by: ivan on 2011.03.02, 13:43:35
Not sure if Amouse will specifically lock down buttons so I would suggest you install it first then you can install the kensingnton driver over it if necessary.

NAS - Network Attached Storage, in my case a D-Link 343 with 4 x 1.5 TB drives in double raid setup.

Robo restore is the restore part of Robosave an IBM Employee written software tool for backing up and restoring the desktop.  I've been using it from my OS/2 2.1 days.

I have never used the easy install path with OS/2, or any other operating system, because I want to know what is going on and have some control overs what is done.  I assume eCS will give options on what you can install using the advanced path therefore use that.

ivan
Title: Re: major trouble after motherboard swap
Post by: OriAl on 2011.03.10, 23:11:24
In addition to the Danis driver(s), make sure you're on the latest kernel.  Try the 14.104a_uni kernel from

http://www.os2site.com/sw/upgrades/kernel/

I seem to recall eCS 1.2MR shipped with an earlier kernel that didn't have all the stuff to work on 64 bit processors.

And, depending on what video driver you were using, you'll possibly have to revert back to VGA mode to make it work.


I'd like to get my 1.2 booting, on a separate partition, while I try to get 2.0 working (if I knew what I was doing, it would help, I admit.)  I've downloaded the 14.04a uni kernel, and danis506187 (though I thought I installed that already), as well as what I think is the latest SMP kernel and the Doscall and related files mentioned for it in the thread.  I don't need it to recognize multiple cores, if 1.2 would work without it.

When I tried to boot 1.2, the system immediately reset.  Does that immediacy hint at the exact cause of the problem?
Title: Re: major trouble after motherboard swap
Post by: Andi on 2011.03.11, 13:07:26
Quote
When I tried to boot 1.2, the system immediately reset.  Does that immediacy hint at the exact cause of the problem?
Not for me. Beside I miss what 'immediacy' mean, do the boot blob appear (white rectangle on the top left corner)? Is there a altf2on.$$$ file in the root dir and you still see no single driver loading? Does ALT-F1/F2 work?

But if I re-read your first post and see that neither Win nor Linux boots I would say you've a major hardware problem. RAM, power supply....?

Or did you succeed with Win or Linux in the meantime?

Maybe it's worth to summarize your findings till now and start a new thread with a short overview what you've tried. At least for me it's hard to follow all the posts in this thread till now.
Title: Re: major trouble after motherboard swap
Post by: RobertM on 2011.03.13, 20:31:03
In addition to the Danis driver(s), make sure you're on the latest kernel.  Try the 14.104a_uni kernel from

http://www.os2site.com/sw/upgrades/kernel/

I seem to recall eCS 1.2MR shipped with an earlier kernel that didn't have all the stuff to work on 64 bit processors.

And, depending on what video driver you were using, you'll possibly have to revert back to VGA mode to make it work.


I'd like to get my 1.2 booting, on a separate partition, while I try to get 2.0 working (if I knew what I was doing, it would help, I admit.)  I've downloaded the 14.04a uni kernel, and danis506187 (though I thought I installed that already), as well as what I think is the latest SMP kernel and the Doscall and related files mentioned for it in the thread.  I don't need it to recognize multiple cores, if 1.2 would work without it.

When I tried to boot 1.2, the system immediately reset.  Does that immediacy hint at the exact cause of the problem?


If this is a newer system, chances are you will need the ACPI drivers that come in eCS v2 for SMP support to work. The standard OS/2 method only supports SMP systems using the MP1.4 or earlier specifications (and even in those cases, certain systems that add extensions to that (ie: no longer MP1.4 compliant) will not work properly).