Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (Hypex)

Bottom

« 1 (2) 3 4 5 ... 21 »

Hypex

Re: Sam460LE - linux Debian / Ubuntu instalation questions

Posted on: 2024/11/29 11:22 #21

Not too shy to talk

@joerg

Quote:

My AmiDVD tool (Enhancer Software, old versions are available for free on os4depot and AmiNet) supports adding the slb_v2 to ISO 9660 images, setting the required flags, etc., and burning them to CDs and DVDs.

That's good to know it can modify existing images. I used to do it on the fly when building an A1 OS4 boot image. Are the older AmiDVD restricted to pre-FE? I recall reading about some issue. I have the Enhancer version so not so not so concerned about it.

But for my specific purpose I need to inject data into the system area at the first 32KB of the ISO9660 image. It relies on UBoot method of scanning for boot block which is usually after RDB on HDD but it scans for BOOT blocks within a small space for SLB so my chain loader is found instead on USB which then loads in the real boot code from the El Torino boot block. Since UBoot doesn't directly support booting ISO9660 off CD, this transparently works around it and unlike some ISO/USB Linux installers, my method works without needing FAT DOS BOOT CD image hackers.

Quote:

I never tested it with AROS/MorphOS/Linux-only 2nd level bootloaders like ub2lb/Parthenope, which can't boot AmigaOS 4.x (at least not from AmigaOS SFS partitions), but since it shouldn't make any difference for U-Boot those should work as well, if you only want to boot AROS, MorphOS and/or Linux with them but not AmigaOS 4.x.

That's what the issue was. I recall it had some quirk when a friend installed Linux but needed to boot OS4 Kickstart from FFS when his Workbench was on SFS. Provided SFS format was public SFS support could have been added. Parthenope already knew some secrets about booting OS4. It knew what was in the module nodes.

Topic | Forum

Hypex

Re: Sam460LE - linux Debian / Ubuntu instalation questions

Posted on: 2024/11/28 4:10 #22

Not too shy to talk

@smarkusg

I wonder if genisoimage or similar can inject data into the reserved system area? Most CD image builders, likely due to using a limited GUI, didn't let you select a file to inject in there I could see. I modified some Amiga program that overwrote the system area of a CD image with a file to get the job done once.

A number of of years ago I wrote a small boot code stub I called UBL. Universal Boot Loader. It was to allow USB/ISO CD hybrid images to be created. You could write the image to CD or USB. And it would autoboot off either.

It needed to be in the system area so UBoot would pick it up as an RDB boot block for USB booting. IIRC it didn't need to have an actual RDB. It then scanned the USB disk for the boot block, loaded it and launched it. UBL would then check the disk blocks (from USB) for a CD boot block and chain load it in. That then took over and would boot the rest of the USB as if it was on CD.

Topic | Forum

Hypex

Re: Sam460LE - linux Debian / Ubuntu instalation questions

Posted on: 2024/11/28 3:37 #23

Not too shy to talk

@Spectre660

I'm surprised the kernels wouldn't boot. Because one kernel there is only a 5MB image. Geri's A1 kernels were about 13MB in size. The A1 kernels are older format so were not compressed which is likely why but did combine raw kernel with compressed ramdisk inside a raw UBoot image.

Suppose if they cannot be embedded in a multi packed image then possibly a multi raw image should have worked. The kernels were 3.x which matches the last version for A1 Linux. Above that into 4.x and 5.x may introduce too much bloat.

AFAIR both slb and ub2lb use UBoot for booting. So would send it a diskboot command to load image. Then do a bootm to boot it. They would usually do a load to 500000. I think the issue here is GZ breaking it as it doesn't allow enough space and using absolute addresses was bound to break. Did you even try to create a raw image or was the kernel binary too large?

Topic | Forum

Hypex

Re: Sam460LE - linux Debian / Ubuntu instalation questions

Posted on: 2024/11/28 2:49 #24

Not too shy to talk

@sailor

You got a bit further than I did. I tried to install on friends Sam440. But I kept getting stuck on finding a repo since all the installers are net only. I didn't understand why apart from taking more server space as the internet goes out of date quickly. I spent 2 hours looking for a working PPC repo before giving up. All just ended up in error.

At one point I ended up converting to CD image to USB. Forget why apart from slower CD speed and faster USB speed. But it kept going faulty over USB for some reason.

It is strange only one install menu showed up. I used a modified Parthenope for the A1 Linux installer and I don't recall any missing menu issue. The earlier Sam installers must have given a working system. It installed Parthenope with a menu so that part worked. But the kernel crashed and that only used to happen when a different kernel was booted. I don't see any other OS4 volumes on there.

Not being able to boot from SLB is strange as Geri's kernels for the A1 are large and around 13MB. SLB is used to boot kernel after Debian is installed. Never seen a problem booting a large kernel.

So the dtb is a device tree blob which is really an OpenFirmware object. Whatever firmware is used to boot Linux, it needs this blob to describe the hardware. On UBoot this doesn't exist so it is passed in an extra file. The UBoot on Sam is more modern and accepts multi image kernels as well as DTB to boot.

Topic | Forum

Hypex

Re: USB keyboards and Uboot - on a Sam460ex

Posted on: 2024/11/27 12:21 #25

Not too shy to talk

@sailor

Quote:

For me works best TeraTerm on windows. Putty not bad, is powerful ( excellent for ssh ) but quite complex for serial. TeraTerm is mainly for serial connection ( and partially ssh ), is very easy to setup can send special characters like break easily. With AmigaOS / MorphOS I am using 68k Term

Thanks. I'll look that up. Where I have found Windows better is for serial to BT adapters for wireless serial. That works well when testing. Some apps are quirky and don't seem well thought out. But BT is broken on Linux and doesn't work well with the GUI. That was back when I was trying to replace the cable with air. But the devices are expensive industrial units or cheap and buggy PCB boards.

Quote:

I agree, than USB-serial adapters sometimes picky. For me works only one from two. Allways better pure serial. My workstation has one on motherboard. But today is simplest to buy PCIe serial card, or use cheap old notebook with serial.

I must have got lucky. I bought one at swap meet decades ago as it looked useful. Got a long null modem cable. And it worked on OSX without needing to track down drivers. I've since been given some more from a friend but am yet to test them.

Topic | Forum

Hypex

Re: USB keyboards and Uboot - on a Sam460ex

Posted on: 2024/11/23 6:32 #26

Not too shy to talk

@NinjaCyborg

I take it you never got serial working? Does the Sam have two serial ports and you got nothing out of both? I did set up a terminal in Windows but forgot about Putty so looked for a terminal on the MS store and was shocked how bad they were. The Amiga blessed us with good free software but in Windows, the most popular OS in the world, free software is crap!

I also set it up in Linux but it's a pain as it won't work without root. So you need to stuff around. Better software than I found on Windows but won't work out of the box.

However, my main terminal is an old PowerBook G4 with a serial to USB adapter. Running ZTerm as terminal which works fine for my usage. But, because of the adapter, it is quirky. If I leave it all plugged in and shut the lid it will lose connection on wake. So I need to quit ZTerm and reload. I can leave adapter plugged in. But I find I need to the adapter plugged in first and then load in the driver from terminal software. I don't recall if Windows is just as quirky with these adapters.

Topic | Forum

Hypex

Re: USB keyboards and Uboot - on a Sam460ex

Posted on: 2024/11/23 6:13 #27

Not too shy to talk

@LiveForIt

In this case there is some issue with interrupts and compositing. I haven't truly got over the Update 2 notfix which introduced the rare but common on my system bug. It's a known issue with Sam 460 and R7 250 as well as RX driver. But my X1000 and R7 250 is apparently uncommon configuration. I've read about some issue with a write back function so could be an OLAND chipset glitch that rears its head.

I ended up testing WaitTOF() with a patch to print calls to serial. On a freeze compose.task is left hanging on WaitTOF(). So there is some interrupt signal missed somewhere. In my case the system is locked up but was still functional internally. Background tasks pinging out to serial still work. So the freeze looks like a graphics lock and not full hardware lock up.

Topic | Forum

Hypex

Re: Quake 2 reduced price during time of AmiWest 2024

Posted on: 2024/10/26 14:52 #28

Not too shy to talk

@TheMagicSN

Thanks. But there is something wrong with their site. Logged and try to buy on PayPal. Get to Confirmation page and it says click a "Buy" button. There is no Buy button any where.

Edit: Okay somehow managed to fix glitch by going to contact page and then back to cart to try again.

Topic | Forum

Hypex

Re: AmiUpdate Update 2.55 (11.10.2024)

Posted on: 2024/10/22 2:49 #29

Not too shy to talk

So I noticed a few discrepancies.

- The latest release is 2.55 but the latest download package is only 2.54.

- The latest download is claimed to be 2.52 on site.

- The latest 2.55 needs to be installed by AmiUpdate updating itself from 2.54 version.

So I grabbed the latest off the website. Installed and it went ok. Reboot. Ran it again and it found a new version. Installed that and reboot again. Now my AmiUpdate is the latest 2.55.

There could be a recurring issue. I didn't see AmiUpdate detect the latest itself. Need to check what I had but it wasn't until I installed the latest available 2.54 manually that AmiUpdate found a newer version.

Also, sometimes I find AmiUpdate checking servers for way too long. Usually finding nothing when there should be some update. I wonder if latest changes cause a slow down in server detection?

Update: (Excusing the pun.)

I updated another volume with the latest AmiUpdate. It had been running 2.49 which is a few releases behind. This confirms my suspicion the issue with AmiUpdate not finding an update to itself is unresolved or has come back. I was stuck on that a few years back.

So I installed 2.54. Reboot and run it. AmiUpdate took a while looking but did not see an update to itself. I then ran a scan and it found an update to itself in the update list. That was strange. Could be a slight bug with latest changes. Well it updated itself fine regardless.

Edited by Hypex on 2024/10/23 0:32:58

Topic | Forum

Hypex

Re: CMake 3.29 Native (OS4)

Posted on: 2024/10/12 3:16 #30

Not too shy to talk

@elfpipe

Okay got it working. It didn't need to be told where compiler is. But it did need to be told where "make" is. So it was able to complete the build. The make ran without problems.

However, I managed to crash it again. I don't know how. I tested CMaking the tinf project from the RAM Disk. It crashed CMake. Does it matter if I CMake direct to list file without a build folder?

Looks like it drank a bad coffee from a bad cafe:


Register dump:

GPR (General Purpose Registers):

   0: 7E2D52E8 4F2EFDD0 ABADCAFE 00000100 502BD8D0 0200B030 02A8824C 02A8826C 

   8: 00000000 2F53444B 2F432F6D 0201FBF8 39955959 51033DD8 5EDE09B4 53A4FEC0 

  16: 02B30000 DFB74240 5958F028 6FFFE300 5101F4A0 5101F020 7D0E9600 00000023 

  24: 59506760 5101F024 595BA038 7D0E9600 5139AB2C 5139AB2C 4F2F0BA4 4F2EFDD0 





Symbol info:

Instruction pointer 0x7E2D53BC belongs to module "cmake" (PowerPC) 

Symbol: uv__signal_event + 0x130 in section 1 offset 0x011F6398



Stack trace:

    cmake:uv__signal_event()+0x130 (section 1 @ 0x11F6398)

    cmake:uv__signal_event()+0x5c (section 1 @ 0x11F62C4)

    cmake:uv_run()+0xf4 (section 1 @ 0x11E61D8)

    cmake:_Z23cmExecuteProcessCommandRKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EER17cmExecutionStatus()+0x1b3c (section 1 @ 0x476AD8)

   



PPC disassembly:

 7e2d53b4: 81490004   lwz               r10,4(r9)

 7e2d53b8: 813f001c   lwz               r9,28(r31)

*7e2d53bc: 81290034   lwz               r9,52(r9)

 7e2d53c0: 7c0a4800   cmpw              r10,r9

 7e2d53c4: 40820050   bne-              0x7E2D5414

Topic | Forum

Hypex

Re: GreaseWeazle help needed

Posted on: 2024/10/12 3:02 #31

Not too shy to talk

@Greenslade

It sounds like you have it all setup correctly. If you have a light on one drive and off on another I wonder if it's getting enough power? A USB2 port is good enough for a USB floppy drive but I'm wondering if an older floppy drive needs more power?

Have you tried to run the GW command in a standard CMD line? PowerShell may be too powerful, though it shouldn't matter. By the sounds of it the shell cannot find the path. Are you dragging the exe into the shell window? What if you just run it from the explorer icon?

Funny that Windows software doesn't open any windows and needs DOS. Thought we had moved on from this. Might as well stick with the retro PC if you wanted DOS!

Topic | Forum

Hypex

Re: CMake 3.29 Native (OS4)

Posted on: 2024/10/11 14:56 #32

Not too shy to talk

@Raziel

Thanks. That looks like an obvious route. I'm not sure how I did it a few years back. I managed to configure it with the older CMake but it doesn't work now as it relies on older so objects so I can't run it. But the new one complains about the old build files. Suppose I need to treat it like a cross compiler as on AmigaOS you need to hold it's hand when configuring a build, since it doesn't pick up things automatically like on other systems.

Topic | Forum

Hypex

Re: CMake 3.29 Native (OS4)

Posted on: 2024/10/11 14:43 #33

Not too shy to talk

@elfpipe

Actually, it is on an SFS partition. My Development volume is SFS. On that is installed the SDK and CMake folders.

Topic | Forum

Hypex

Re: CMake 3.29 Native (OS4)

Posted on: 2024/10/11 3:21 #34

Not too shy to talk

@elfpipe

Quote:

What do you mean "always ends up"? As in : You can start cmake, and it does some work, but then it crashes? At what point does it crash, and of course : What does the crash look like?

So I enter a build folder and run a "cmake .." like so:


4.RAM Disk:tinf-1.2.1/build> cmake ..

CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):

  Compatibility with CMake < 3.5 will be removed from a future version of

  CMake.



  Update the VERSION argument <min> value or use a ...<max> suffix to tell

  CMake that the project does not need compatibility with older versions.

After printing all that to CLI I get a reaper. I'll post a cut down of it:


GPR (General Purpose Registers):

   0: FFFF3BB0 61EE8630 ABADCAFE 580F4930 00000000 00000000 580F49E8 00000001 

   8: 00000004 580F4930 00000003 61EE8630 61EE8630 588E6DD8 61EB39B4 59241DA0 

  16: 02B30000 DFB75480 613EC028 6FFFE300 588D24A0 588D2020 7E4EE600 00000003 

  24: 5A48EC40 588D2024 5EB90038 7E4EE600 580F01D4 580F01D4 61EE8FE4 61EE8630 



Symbol info:

Instruction pointer 0x7F27DBD4 belongs to module "cmake" (PowerPC) 

Symbol: _Z25cmCommandArgument_yyparsePv + 0xC in section 1 offset 0x00D99BB0



Stack trace:

    cmake:_Z25cmCommandArgument_yyparsePv()+0xc (section 1 @ 0xD99BB0)

    cmake:_ZN29cmCommandArgumentParserHelper11ParseStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi()+0xd8 (section 1 @ 0x87FE24)

    cmake:_ZNK10cmMakefile23ExpandVariablesInStringERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEbbbPKclbb()+0x2f4 (section 1 @ 0x160140)

    cmake:_ZNK10cmMakefile15ExpandArgumentsERKSt6vectorI18cmListFileArgumentSaIS1_EERS0_INSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISB_EE()+0x224 (section 1 @ 0x1656C0)

    cmake:_ZL20InvokeBuiltinCommandPFbRKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EER17cmExecutionStatusERKS_I18cmListFileArgumentSaISE_EESB_()+0x12c (section 1 @ 0x26B080)

    cmake:_ZZN7cmState17AddBuiltinCommandERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFbRKSt6vectorIS5_SaIS5_EER17cmExecutionStatusEENKUlRKS8_I18cmListFileArgumentSaISH_EESE_E_clESL_SE_()+0x38 (section 1 @ 0x26B208)



PPC disassembly:

 7f27dbcc: 3c00ffff   lis               r0,-1

 7f27dbd0: 60003bb0   ori               r0,r0,15280

*7f27dbd4: 7c21016e   stwux             r1,r1,r0

 7f27dbd8: 7c0802a6   mflr              r0

 7f27dbdc: 900c0004   stw               r0,4(r12)

Quote:

If it is another stack issue, then it is easy to fix. AMOF I don't quite remember, if the online version contains a stack cookie.

You could be right. I checked and my shell has a paltry stack that's barely over 64KB. I changed it to 1MB and CMake didn't crash! Thanks for the hint. The shell needs a bugzilla if the default is really that small.

Ok so that's a lot better. But then I got stuck again. Like happened recently after reading back a few pages CMake cannot find my make command or compiler either:


-- CMAKE_HOST_SYSTEM_VERSION : 53.18

CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

I saved a Snoopy fail log but don't see where it's looking for a make or compiler:


00016 : cmake           : FAIL = GetVar("ELF.debug",0x56B13A90,19,0x00000000) [62uS]

00017 : cmake           : FAIL = ExamineObject([SN] "PROGDIR:.unix") [10uS]

00018 : cmake           : FAIL = GetVar("EXEC_IMPORT_LOCAL",0x56B13E8C,8,0x00000200) [8uS]

00019 : cmake           : FAIL = Lock("/tmp",SHARED) [32uS]

00020 : cmake           : FAIL = Lock("/tmp",SHARED) [10uS]

00021 : cmake           : FAIL = GetVar("PWD",0x5892DFE8,256,0x00000000) [96uS]

00022 : cmake           : FAIL = Lock("Development:cmake-amiga/bin/cmake-gui",SHARED) [17uS]

00023 : cmake           : FAIL = Lock("Development:cmake-amiga/bin/ccmake",SHARED) [16uS]

00024 : cmake           : FAIL = Lock("Development:cmake-amiga/bin/cmcldeps",SHARED) [15uS]

00025 : cmake           : FAIL = Lock("Development:cmake-amiga/doc/cmake-3.29/html/index.html",SHARED) [18uS]

00026 : cmake           : FAIL = GetVar("CMAKE_GENERATOR",0x5892DFE8,256,0x00000000) [83uS]

00027 : cmake           : FAIL = GetVar("CMAKE_GENERATOR_INSTANCE",0x5892DFE8,256,0x00000000) [61uS]

00028 : cmake           : FAIL = GetVar("CMAKE_GENERATOR_PLATFORM",0x5892DFE8,256,0x00000000) [62uS]

00029 : cmake           : FAIL = GetVar("CMAKE_GENERATOR_TOOLSET",0x5892DFE8,256,0x00000000) [60uS]

00030 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/CMakeCache.txt",SHARED) [18uS]

00031 : cmake           : FAIL = GetVar("MAKEFLAGS",0x5892DFE8,256,0x00000000) [68uS]

00032 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/PreLoad.cmake",SHARED) [16uS]

00033 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/PreLoad.cmake",SHARED) [16uS]

00034 : cmake           : FAIL = GetVar("VERBOSE",0x5892DFE8,256,0x00000000) [59uS]

00035 : cmake           : FAIL = GetVar("HOSTNAME",0x5D679B6C,255,0x00000000) [63uS]

00036 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CMakeFiles/CMakeScratch",SHARED) [23uS]

00037 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CMakeFiles/CMakeScratch",SHARED) [18uS]

00038 : cmake           : FAIL = Delete("Development:CMake/tinf-1.2.1/build/CMakeFiles/pkgRedirects") [240257uS]

00039 : cmake           : FAIL = GetVar("CMAKE_TEST_LAUNCHER",0x5892DFE8,256,0x00000000) [94uS]

00040 : cmake           : FAIL = GetVar("CMAKE_CROSSCOMPILING_EMULATOR",0x5892DFE8,256,0x00000000) [64uS]

00041 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/.cmake/api/v1/query",SHARED) [21uS]

00042 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CMakeConfigureLog.yaml",SHARED) [17uS]

00043 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [79uS]

00044 : cmake           : FAIL = GetVar("CLICOLOR_FORCE",0x5892DFE8,256,0x00000000) [68uS]

00045 : cmake           : FAIL = GetVar("CLICOLOR",0x5892DFE8,256,0x00000000) [59uS]

00046 : cmake           : FAIL = GetVar("MAKE_TERMOUT",0x5892DFE8,256,0x00000000) [58uS]

00047 : cmake           : FAIL = GetVar("EMACS",0x5892DFE8,256,0x00000000) [58uS]

00048 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [101uS]

00049 : cmake           : FAIL = GetVar("CMAKE_BUILD_TYPE",0x5892DFE8,256,0x00000000) [76uS]

00050 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [71uS]

00051 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [67uS]

00052 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00053 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00054 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00055 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00056 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [65uS]

00057 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00058 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [65uS]

00059 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00060 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [70uS]

00061 : cmake           : FAIL = GetVar("CMAKE_PREFIX_PATH",0x5892DFE8,256,0x00000000) [69uS]

00062 : cmake           : FAIL = GetVar("CMAKE_PROGRAM_PATH",0x5892DFE8,256,0x00000000) [61uS]

00063 : cmake           : FAIL = GetVar("CMAKE_APPBUNDLE_PATH",0x5892DFE8,256,0x00000000) [62uS]

00064 : cmake           : FAIL = GetVar("PATH",0x5892DFE8,256,0x00000000) [63uS]

00065 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [67uS]

00066 : cmake           : FAIL = GetVar("CMAKE_MAXIMUM_RECURSION_DEPTH",0x5892DFE8,256,0x00000000) [66uS]

00067 : cmake           : FAIL = GetVar("CLICOLOR_FORCE",0x5892DFE8,256,0x00000000) [67uS]

00068 : cmake           : FAIL = GetVar("CLICOLOR",0x5892DFE8,256,0x00000000) [58uS]

00069 : cmake           : FAIL = GetVar("MAKE_TERMOUT",0x5892DFE8,256,0x00000000) [59uS]

00070 : cmake           : FAIL = GetVar("EMACS",0x5892DFE8,256,0x00000000) [58uS]

00071 : cmake           : FAIL = GetVar("CLICOLOR_FORCE",0x5892DFE8,256,0x00000000) [99uS]

00072 : cmake           : FAIL = GetVar("CLICOLOR",0x5892DFE8,256,0x00000000) [60uS]

00073 : cmake           : FAIL = GetVar("MAKE_TERMOUT",0x5892DFE8,256,0x00000000) [59uS]

00074 : cmake           : FAIL = GetVar("EMACS",0x5892DFE8,256,0x00000000) [58uS]

00075 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CPackConfig.cmake",SHARED) [36uS]

00076 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CPackSourceConfig.cmake",SHARED) [18uS]

00077 : cmake           : FAIL = Lock("RANDOM:",SHARED) [5363uS]

00078 : cmake           : ROOT = ParentOfFH(0x18C25962) "RANDOM:" [145uS]

00079 : cmake           : FAIL = Delete("Development:CMake/tinf-1.2.1/build/CMakeCache.txt.tmpae9ee") [33uS]

00080 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CMakeCache.txt.tmpae9ee",SHARED) [20uS]

00081 : cmake           : FAIL = Lock("Development:CMake/tinf-1.2.1/build/CMakeCache.txt.tmpae9ee",SHARED) [21uS]

00082 : cmake           : FAIL = Rename("Development:CMake/tinf-1.2.1/build/CMakeCache.txt.tmpae9ee" -> "Development:CMake/tinf-1.2.1/build/CMakeCache.txt") [26uS]

00083 : cmake           : FAIL = Delete("Development:CMake/tinf-1.2.1/build/CMakeCache.txt.tmpae9ee") [17uS]

00084 : cmake           : FAIL = Lock("PIPE:0144/32768/0",SHARED) [4157uS]

00085 : cmake           : FAIL = Lock("PIPE:1144/32768/0",SHARED) [23736uS]

00086 : cmake           : FAIL = Lock("PIPE:2144/32768/0",SHARED) [13311uS]

00087 : cmake           : ROOT = ParentOfFH(0x18C25962) "RANDOM:" [38uS]

00088 : cmake           : ROOT = ParentOfFH(0x18C25962) "RANDOM:" [1086uS]

00089 : cmake           : <----- RunCommand(0x15F2C675 "cmake",,"..",3) = 1 [0x00000001] [1229759uS]

I'm trying to build this project:
https://github.com/jibsen/tinf

Topic | Forum

Hypex

Re: CMake 3.29 Native (OS4)

Posted on: 2024/10/10 2:28 #35

Not too shy to talk

Has anyone experienced any crashes? I've got the alpha CMake up and running and it starts to work. But it always always ends up in a crash. I'll collect some crash logs. Right now trying to update some code using the newer CMake.

Topic | Forum

Hypex

Re: Why not use the second core for chipset emulation?

Posted on: 2024/10/7 15:02 #36

Not too shy to talk

@NinjaCyborg

The custom did also share bus cycles with CPU in Amiga chipset.

Before getting into the emulation itself, there's the first obstacle to move out the way, managing the other core. Ideally this would be managed by the OS itself. So for this case OS4 needs to technically support multi-core. However, itself and apps would still run on single core, but it would still need to manage two cores running and possibly isolate memory for other core.

To be practical only OS friendly apps can be supported. Because otherwise a 68k game or program could just take down the host system. That's another obstacle. Even without any chipset emulation most software that hits the hardware or even use it to open a screen will want to freeze the system until it's finished

UAE could be used on other core. Since audio can be simulated but graphics is harder and combining with CPU in one dedicated program like UAE can be better. But then UAE would need to run in parallel somehow while not interfering with the other core single running OS4.

Just my thoughts.

Topic | Forum

Hypex

Re: AmigaOS 4.1 Final Edition or Odyssey?

Posted on: 2024/10/7 14:43 #37

Not too shy to talk

@Tuvok

Worth a look just in case. Can cancel that out then. In that case the Grim Reaper is the next best clue. Which can save a log. Full of lots of info but in most cases the stack trace usually is all that's needed to pin point an issue.

Edited by Hypex on 2024/10/8 13:43:24

Topic | Forum

Hypex

Re: AmiStore purchases and downloads

Posted on: 2024/10/6 14:53 #38

Not too shy to talk

@Maijestro

Looks like AmiStore GS is a medium through which you can purchase both OS3 and OS4 software. With more emphasis on OS4 since it has more products. In some ways the A600GS could be a hardware dongle through which OS4 products can be purchased.

Edited by Hypex on 2024/10/7 13:38:14

Topic | Forum

Hypex

Re: AmiStore purchases and downloads

Posted on: 2024/10/5 15:15 #39

Not too shy to talk

@Hans

Quote:

So we'd need an embeddable browser engine for this.

Might as well require an app while we are at it. Given the world is going to 2FA and 3FA before long. I can't login to Yahoo on my phone without it wanting to send a code to my phone but it works normally from desktop email client.

There's a 3rd party AmiStore buyer Java app. So the method of payment is known. Though, writing it in Java doesn't help again, as the Amiga Java port must be 20 and almost 30 years late by now, so it won't help to have one Amiga application.

Topic | Forum

Hypex

Re: IntuitionBase.com updates

Posted on: 2024/10/2 15:53 #40

Not too shy to talk

@walkero

When I read the first line I thought it was about one of my programs.

When it comes to info on setting up a graphic card and what configurations works on what hardware Sailor is the bomb.

I should consider checking if I have any articles that may be useful, though they may be old.

Topic | Forum

Top

« 1 (2) 3 4 5 ... 21 »