OS/2, eCS & ArcaOS - Technical > Setup & Installation
UEFI & SecureBoot?
Sigurd Fastenrath:
--- Quote from: jdeb on July 30, 2013, 10:25:31 pm ---
--- Quote from: Sigurd Fastenrath on July 30, 2013, 04:56:39 pm ---For the records:
I just got a new X230t from Lenovo with 8 GB Ram, i7 and so on. There is still the option to disable Secure Boot and UEFI in the BIOS, a least to emulate the "Legacy" BIOS.
While eCS 2.2 latest beta failed installation several times because of complaining about the HDD (where the eCS 2.2 demo while booting does not), it worked quite well once I installed it using the Clone method and DFSEE.
It may be worth a try for those trying to install eCS 2.2 on modern hardware if "usual" installation fails to create a clone of a working system and restore it on the new hardware. This will be shown in Cologne in November as mentioned. This is safe and time saving (takes about 5 to 10 minutes).
This allways worked for me.
--- End quote ---
Are their any license issue's doing it that way? Just curious. Additionally, what about those who can not attend Cologne? Is their any documentation on doing it, I thought I read it somewhere but it escapes me at the moment?
--- End quote ---
No, there will be no documentation, sorry. I might make a "How To" Video about it sometime but I am not sure. As long as you just install the clone on only one PC (or according to the number of license you own) I do not see any legal problem. I would like to advice to license and therefore support DFSEE as this is really a great peace of software.
I am thinking about making a bootable DFSEE USB Stick with the clone images of eCS 2.2. and Warp 4 on it....
Sigurd Fastenrath:
--- Quote from: Neil Waldhauer on July 30, 2013, 05:19:31 pm ---I struggled with a UEFI system (IBM X Series) server, and eCS 2.2 beta simply does not recognize the SATA hardware. It fails even in compatibility mode with
OS2AHCI driver version 1.29
Found AHCI device: Intel PCH AHCI (8086:3b22) class: 010601 bus: 0
devfunc 0xfa
OS2AHCI: couldn't register [MM]IO region: (rc = RMRC_RES_ALREADY_CLAIMED)
No adapters found.
--- End quote ---
I had the same problem with "my" OS/2 Warp 4 system - it did not occur with eCS 2.2.
Roderick Klein "oracled" he did know the reason for this but gave me no hint nor helped me with this - because of using Warp 4 instead of eCS 2.2 I guess. That slowed down my motivation in general to share my experiences, but at least I pointed them to the download source for a different OS2 Loader they may use to improve the eCS included one.
The solution for me was to add the switch to use only IRQ up to No. 15 (I guess it was /vw ). Therefore I have one clone "with" the /VW switch and one without, and one with OS4 Loader and one not.... :-)
Hope this helps.
What did help in some cases was to replace the eCS Loader with the OS/4 Loader - but you have to replace the kernel back to 104smp as well, that might cause new problems (in my case it turned out to be stable and worked - and the best of it - it does not have or show the "memory gap" at 512 MB - please see other of my threads for this)
walking_x:
--- Quote from: Sigurd Fastenrath on July 31, 2013, 07:49:58 am ---The solution for me was to add the switch to use only IRQ up to No. 15 (I guess it was /vw ). Therefore I have one clone "with" the /VW switch and one without, and one with OS4 Loader and one not.... :-)
--- End quote ---
You can remove at least one clone by using CFGEXT=EXT key of OS4 Loader ;)
It allow to load CONFIG.EXT instead of CONFIG.SYS and works with IBM kernels too.
Neil Waldhauer:
--- Quote from: Andy Willis on July 31, 2013, 02:50:10 am ---
--- Quote from: Neil Waldhauer on July 30, 2013, 05:19:31 pm ---I struggled with a UEFI system (IBM X Series) server, and eCS 2.2 beta simply does not recognize the SATA hardware. It fails even in compatibility mode with
--- End quote ---
Which model of X-series? I run one old one that has SCSI drives but another slightly newer one (still rather old) will not work with SAS drives. I haven't got one with actual SATA drives to test.
--- End quote ---
This is the x 3200 M3, so it has SAS. You can plug a SATA drive into the SAS slot. The machine is fine with it, and the drive appears in other OS. The SATA controller is the Intel PCH, which is supported, but support fails because of the above message. I know nothing about SAS, and I was surprised to see SATA connectors. Here is the PCI dump for the controller.
0000:01:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS (rev 08)
Subsystem: IBM Unknown device 03bb
Flags: bus master, fast devsel, latency 0, IRQ 16
I/O ports at 4000
Memory at 92210000 (64-bit, non-prefetchable)
Memory at 92200000 (64-bit, non-prefetchable)
Expansion ROM at ffe00000 [disabled]
Capabilities: [50] Power Management version 2
Capabilities: [68] Express Endpoint IRQ 0
Capabilities: [98] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
Andy Willis:
--- Quote from: Neil Waldhauer on July 31, 2013, 03:26:37 pm ---This is the x 3200 M3, so it has SAS. You can plug a SATA drive into the SAS slot. The machine is fine with it, and the drive appears in other OS. The SATA controller is the Intel PCH, which is supported, but support fails because of the above message. I know nothing about SAS, and I was surprised to see SATA connectors. Here is the PCI dump for the controller.
0000:01:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS (rev 08)
--- End quote ---
SAS controller... I've worked off and on with trying to get the SAS drives in an X3650 to work. My understanding is that SATA drives will work with a SAS controller because SATA is a subset of SAS. I have gotten to where the eCS installer's drive check utility will see a drive (though not everything that is defined in the RAID BIOS) but no partition/lvm information and it has been unsuccessful in fixing the problem when told to do so.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version