OS/2, eCS & ArcaOS - Technical > Setup & Installation
Final Request for Help for the Final Warp 4 Image Clone
walking_x:
This problem has ages, actually :) But now it occurs much often.
Some years ago I saw report about old HP notebook with 64 + 96 Mb onboard with a small hole between of them... And the user was very grateful to OS/4 loader ;)
Doug Bissett:
--- Quote ---- ACPI - I have to use the /VW switch on the Samsung Slate, otherwise the boot process stops with "Can not load OS2AHCI.ADD because IRQ 19 allready claimed" -> so obvious for me tha the handling of hig IRQ is not working as it should as eCS 2.1 with ACPI 3.21.07 does not have this problem (but some more I do not have with Warp 4). I only have the ACPI32107.wpi file installed, no more ACPI related files. Do I need something else to handle the high IRQ in the right way?
--- End quote ---
ACPI32107 seems to work very well. Your problem is probably one of the system drivers causing problems, or it may be something in the BIOS that is claiming IRQ 19 before ACPI gets started. Either you aren't starting ACPI properly (at the right time), or you need to figure out what is holding IRQ 19, and do something about it. On the other hand, is there really any reason to not use /VW?
--- Quote ---- Atheros WLAN - I still try to figure out to run the Atheros WLAN 9285 chipset. I already opened the Slate and could change the MiniPCIE Option GM67 card, and put an Intel inside, but I would loose Bluetooth or 3G,a s there is no Intel chipset Mini PCIE card around with Bluetooth, Wlan and 3G - I do use and need all three for windows. And I am not sure if the WLAN Multimac for Intel will see the light of the day (hopefully it will). Someone posted to me a mail with some hints for this card (I already got the driver loading in UNSUPPORTED mode but the boot process stops - I guess because of netbind.exe or an IRQ conflict) - but unfortunately I lost this mail. May be thsi person is reading here and can send it to me once again?
--- End quote ---
If you want to use an UNSUPPORTED wireless LAN device (any of them), you need to patch \IBMCOM\macs\GENM32W.OS2. Apparently, GENMAC does not enable the piece of code that XWLAN needs to interface with the windows driver, if you use UNSUPPORTED mode. See the GENMU_TEST_README.TXT file at ftp://genmac@ftp.os2voice.org/ (use the word "unsupported", lower case, and no quotes, as a password if asked), for more information. Also check that for the presence of an already prepared driver. I don't know what the PCI ID for that device is, and it may already be included. If not, supply the parts, and I will add it to the TEST version. The instructions are in the README. I can't guarantee that it will actually work, but it should get installed properly that way (including the required patch).
--- Quote ---- Memory management - the Installation "only" sees 512MB of the internal 4GB of RAM - according to the xworkplace program "OS/2 kernel" - as it is an Intel Core i5 second generation cpu the same problems occur with eCS 2.2 beta. Is there a program that can show me the amount of space OS/2 "really" uses or sees?
--- End quote ---
It seems that all UEFI machines are going to have this problem, to some extent. Somebody decided to allow more than one memory hole, and OS2LDR can't handle that. It also seems that 512 meg seems to be a popular spot to put the second hole. That means that OS/2 (eCS) can't assign memory above that address. OS2LDR needs to be fixed, somehow. From what I can tell, OS/2 "sees" 512 meg, and no more. Since OS/2 can actually operate reasonably well with that amount of memory, you will probably find that the machine will work okay, and hope they can fix the problem, eventually. Changing video cards is not a viable work around for most machines (especially laptops). I expect that what Roderick describes simply moved the memory hole to another spot. In my case, on my Lenovo ThinkPad L530, I think it is one of the NICs that sets up shop at 512 meg, not the video card.
--- Quote ---The user continues make damage to eComStation (and eComStation.RU)
--- End quote ---
eComStation.RU does their own damage. They don't need any help from Sigurd.
--- Quote ---The problem is simple - IBM (eCS) OS2LDR gets only 1st block of memory from system, but EFI BIOS split memory on 2-3 huge blocks...
--- End quote ---
Apparently, it is not always "huge" blocks, and it can be more than 2-3. It depends on the specific system, and what I/O they have installed.
--- Quote ---Because if this would be an EFI issue and you insert a different video card and the memory hole then goes away!?
--- End quote ---
It is definitely a UEFI problem. The UEFI specs allow for I/O devices (not just video cards) to put holes in memory, and it seems that those holes can be put anywhere they please. Logically, they should be at the end of memory, but that is not in the specs. It also seems that Microsoft defined the specs, and saw an opportunity to mess up other operating systems, again. Linux has, apparently, found a work around, but it is not that easy in OS/2 since they do not have the source for OS2LDR (or, if they do, it is not common knowledge).
I have yet to see any way to "insert a different video card" in a laptop. It can also be difficult in a desktop, sometimes. Not to mention it is an extra expense that many people aren't willing to pay (eCS is not cheap to start with). The problem needs to be fixed, soon, because UEFI seems to be the way that all new hardware is going.
Roderick Klein:
--- Quote from: Doug Bissett on April 05, 2013, 06:19:01 pm ---
It is definitely a UEFI problem. The UEFI specs allow for I/O devices (not just video cards) to put holes in memory, and it seems that those holes can be put anywhere they please. Logically, they should be at the end of memory, but that is not in the specs. It also seems that Microsoft defined the specs, and saw an opportunity to mess up other operating systems, again. Linux has, apparently, found a work around, but it is not that easy in OS/2 since they do not have the source for OS2LDR (or, if they do, it is not common knowledge).
I have yet to see any way to "insert a different video card" in a laptop. It can also be difficult in a desktop, sometimes. Not to mention it is an extra expense that many people aren't willing to pay (eCS is not cheap to start with). The problem needs to be fixed, soon, because UEFI seems to be the way that all new hardware is going.
--- End quote ---
Well I don't think this is specific for the UEFI standard. Remember the old ISA cards video boards. They also had a memory hole!
So I still don't see why this is specificly related to the UEFI standard.
And I know sticking in a video card in a laptop is not possible.
And certainly network cards do not require a memory hole...
Roderick
walking_x:
--- Quote from: Doug Bissett on April 05, 2013, 06:19:01 pm ---Apparently, it is not always "huge" blocks, and it can be more than 2-3. It depends on the specific system, and what I/O they have installed.
--- End quote ---
Yes, but there is no reason to use tiny blocks... Whole list can hold up to 20 entries and most of them - small in size. OS/4 loader just ignore blocks smaller 64k, as I know.
And - OS2LDR still can be rewritten from scratch ;) This is possible if you know how organized kernel loading process.
Sigurd Fastenrath:
First I would like to thank for answering and , to avoid double messages, I would like to point to the similar thread at the yahoo group, for those not already monotoring both forums:
http://tech.groups.yahoo.com/group/eComStation/message/88015
--- Quote from: Doug Bissett on April 05, 2013, 06:19:01 pm ---
If you want to use an UNSUPPORTED wireless LAN device (any of them), you need to patch \IBMCOM\macs\GENM32W.OS2. Apparently, GENMAC does not enable the piece of code that XWLAN needs to interface with the windows driver, if you use UNSUPPORTED mode. See the GENMU_TEST_README.TXT file at ftp://genmac@ftp.os2voice.org/ (use the word "unsupported", lower case, and no quotes, as a password if asked), for more information. Also check that for the presence of an already prepared driver. I don't know what the PCI ID for that device is, and it may already be included. If not, supply the parts, and I will add it to the TEST version. The instructions are in the README. I can't guarantee that it will actually work, but it should get installed properly that way (including the required patch).
--- End quote ---
Yes, I already used your genmac files from the genmac list ;). And I already have the XP drivers for the Atheros and I changed the protocol.ini and some more. I will come back to this once Finger support is finished. Wim just handed a one finger driver and this is working great!! He may have the chance not only to support two but also FIVE finger support ;D But we have to see and all credits to Wim!
By the way, for me one can not top using Warp 4 (or ecomstation if you like) with this tablet and finger + stylus support.....
8)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version