The release of current SDK for FE is great news indeed. I just wonder if anyone tried it with Cubic IDE - this is the environment I'm using on classic. I wish Cubic got updated as well to support AmigaOS 4.1 FE with latest SDK. Anyway before I will destroy my working environment by installing latest SDK I am curious of other Cubic IDE users experience.

This is great news indeed. Keeps our classic alive and for those who lacks PPC card not it is high time to finally get one.

Well, this is exactly what I did (clean hardware power on)and it still says that CopyStore is in use (failed to open for writing). It seems that using AutoInstall script always fails while manual copying with WorkBench did the job just right

I've have the same problem with CopyStore as already described. I've used AmiUpdate to download the archive to RAM: and than tried to install it manually but I sitll get the same error during write operation despite the fact that AmiUpdate is not running. Any tips how to solve this issue or should I wait for next AmiUpdate release?

I'm running AmigaOS 4.1 U2 on SAM440ep.

@Mrodfr

Haven't checked that yet but we need update to SDK anyway - looking at previous release history we didn't have to wait long for up to date SDK.

I have SAM440ep and use only passive cooling - this is why I resigned to install backplate. However I have a suspicion that after couple of hours the system becomes more unstable than usual. Never experienced self reset in such situation - only GreamRipper or crash.

Therefore I'd vote for PSU or temperature issue.

@corto

I keep my fingers crossed than .

@corto

No problem - I just wish it would work someday. I've thought that inclusion of the tool in official release from Hyperion makes it working on all supported architectures. Anyway I hope you will be able to identify the problem and find workaround for it - keep up good work.

@tonyw

Thanks for the info regarding labels. I've changed them accordingly just not to confuse others when I show them my system. Anyway I think this should be changed by the update itself. I know this is just a detail but still...

Anyway it's great to have another update so soon :)

@broadblues

I have the same issue - using AOS 4.1 U2 on SAM440 with latest SDK and Hieronymus is part of it. Can somebody confirm it works on SAM systems?

@gerograph

I tried Crux PPC 2.6 without any luck again. However I setup menu.lst file on my SFS (bootable) partition with Kicklayout too and this time Parthenope was able to read it however it hangs during loading. So I guess there is something wrong with how partitions are set up.

@jaokim

They must have it - at least SDK in some form because how they would compile the final version of OS? Would be interesting to hear from Hyperion what are they using for debugging.

@gerograph

Not yet - I plan to test 2.6 today and I'll let you know. Anyway this is not Crux related problem I belive - there must be something wrong with filesystem setup/layout on partition.

@Chris

I've tested both from Crux PPC 2.5 and ACube site versions of Parthenope and both boots AOS 4.1 U1 quickly as it used to be at least in my case.

@abalaban

I have most experience with Windows based debuggers (both userland and kernel) but I am using gdb under Linux/BSD systems often too and I agree that if one is coming from different tool it is a big change. Anyway from my perspective on AOS it was simply unstable. Not that I had a lot of experience with it and SDK. I've just recently started to play with it - found out it had problems and left it right there.

@kas1e

I confirm - I tried to use it and had a lot of problems with it. Good system debugger would be a nice add-on for next SDK release.

@Elwood

Thanks - as I wrote in another thread I still have the same problem even after changing to new SLB. The one thing that comes to my mind is Uboot settings... any special paramteres should be setup there?

I've assumed that the layout of partitions and their numbers are not important to SLB/Parthenope. My layout is as follows:

[os4.1u1 boot partition][swap][sfs][sfs][sfs][sfs][ext2 - lnx/00]

so in confing files I have root=/dev/sda7. Both menu.lst and a1boot.conf are world readable.

@Elwood

Well, I've installed the new SLB from Update CD and created /boot/a1boot.conf file on ext2 with proper line (in my case):

Crux /boot/uImage root=/dev/sda7 console=tty

and I'm still missing this option during boot selection screen. I'm really running out of ideas what can be wrong with my setup. It just seems that every second level bootloaders I try simply miss ext2 partition (lnx/00 automount bootable boot priority=-1).

@Elwood

I will check it out. Is there any documentation about it's new features and how it should be configured to boot Linux?

@Elwood

Thanks - I'll review my configuration. What else - besides bootable flag and boot priority - could result in missing my menu.lst from ext2 file system?

BTW: Crux 2.6 is out - time for some testing...