OS/2, eCS & ArcaOS - Technical > Utilities
OS/2 arrows: 2.1: What components to include to OS?
Pete:
Hi Andi B
Yes, pointless having the monitor if we do not have a driver with the necessary capability :-)
So far I have not been told whether our current driver has the capability although I did not notice anything about hot swapping in the readme file.
My current arca noae os2ahci bug is system cannot boot with eSATA drive attached "OS/2 is unable to operate hard disk or diskette..." so I will probably ask about hot swap in that very related bug. The reason the drive was attached at boot was simply because hot swap does not work .
Regards
Pete
Andi B.:
--- Quote ---My current arca noae os2ahci bug is system cannot boot with eSATA drive attached "OS/2 is unable to operate hard disk or diskette..." so
--- End quote ---
To my understanding this are different things. "Unable to operate...." maybe solved rearranging controllers in BIOS. Guss your eSATA drive is numerated before your standard boot drive. Don't know by which OS/2 driver though.
Hot swapping is a new feature our OS does not support except for USB drives or optical medias. No clue which parts of the OS have to be changed to allow removable SATA devices.
Pete:
Hi Andi B.
The "cannot boot with eSATA drive attached" bug is specific to the os2ahci.add 1.32 released by Arca Noae. The problem does not exist with the slightly earlier, slightly smaller 1.32 supplied with the eCS2.2beta2 release.
That seems to indicate the drives are enumerated by the os2ahci driver.
I have no idea how hot swapping works on a technical level...
The possibly good news is that eSATA is simply SATA but with hot swap capability, ie there is not another set of drivers involved as there is with a USB drive.
I suspect that the system needs to poll the controller(s) to check if a drive has been newly attached to a port and on finding a new drive attached pass the drive data, size etc, on to the system . The job the Removable Device Monitor does for USB drives is probably a good example of what is needed and, if that code is available, may provide a starting point. Maybe eSATA support could be added to that code rather than developing a separate eSATA Device Monitor.
I also suspect the driver needs to be "hot swap" capable and have no idea if that is the case with the current/recent os2ahci.add releases.
Regards
Pete
Doug Bissett:
--- Quote ---so I will probably ask about hot swap in that very related bug. The reason the drive was attached at boot was simply because hot swap does not work
--- End quote ---
Don't report more than one problem per incident, or both problems may be ignored. Hot swap is completely different from your "unable to operate" problem. It is also not a deadly problem because a simple boot works around it.
--- Quote ---The problem does not exist with the slightly earlier, slightly smaller 1.32 supplied with the eCS2.2beta2 release.
--- End quote ---
The AHCI driver that comes with eCS 2.2 b2 does have some sort of problem, it is best not to use it, although my understanding is that it either works, or it doesn't. There is a later version, also called 1.32, that was made available after eCS 2.2 b2 was released. It fixes the problem, and it would be very interesting to see if it also has the problem that you see with the Arca Noae driver. If so, it was that change that messed it up. If not, it was whatever Arca Noae did to it. Unfortunately, the eCS betazone seems to be gone, and I think that was where the fixed 1.32 driver was.
--- Quote ---The possibly good news is that eSATA is simply SATA but with hot swap capability
--- End quote ---
The SATA hardware is hot swap capable. ESATA simply adds a defined cable to do it. I suspect that the only real difference is extra shielding, for longer distances, and possibly a tougher connector.
--- Quote ---I also suspect the driver needs to be "hot swap" capable and have no idea if that is the case with the current/recent os2ahci.add releases.
--- End quote ---
The "removable" feature needs to be added, otherwise it would work. The other thing that it needs, is a hook to allow an eject, which needs to close out the file system, before telling the user that they can disconnect it. I don't think that ACPI needs to get involved any more than it gets involved in ejecting a USB drive. There is no need to power off the drive before connecting/disconnecting it.
Pete:
Hi Doug
I would not mind trying this "post ecS2.2beta2 pre Arca Noae" driver to see if that also has the boot problem.
As you say the problem is finding a copy...
If anyone has a copy of os2ahci.add dated later than
[M:\OS2\BOOT]bldlevel os2ahci.add
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#D Azarewicz:1.32#@##1## 10 Nov 2013 07:58:57 DAZAR1 ::
::::@@AHCI Driver (c) 2013 D Azarewicz
and before
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#Arca Noae LLC:1.32#@##1## 16 Nov 2014 08:16:06 DAZAR1
::::::@@AHCI Driver (c) 2014 Arca Noae LLC
Please let me know.
Regards
Pete
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version