Who's Online |
46 user(s) are online ( 36 user(s) are browsing Forums)
Members: 0
Guests: 46
more...
|
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 12:51
#61
|
Not too shy to talk 
|
@smarkusg so, firstly, the fact that sgit works for you there is highly likely down to the size of the repo you are checking out. 1.6MB will likely be fine. My repo is around 19MB and it fails at 98%. Like I said, I cut it down to a smaller repo which isn't a desperately sustainable solution and it did complete the checkout, but then it choked on a symlink.
But more importantly, it would be good to know how you built it. Because cloning simplegit to my Mac, then running the build inside the docker cross compiler didn't work. And I don't believe I'm alone in that. If it worked then we could look into things.
Maybe later today I can find some time to go back to it, have another go and post some of the problems.
[edit] I need to try the idea of cloning to the ram drive. That speedup could get round the SSL error on the larger repo. Only could because I think the speed issue comes from the network on OS4, not the disk.
Edited by MartinW on 2024/5/17 13:08:36
|
|
Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 12:42
#62
|
Not too shy to talk
|
@MartinW i don't use this tool, but i quickly recompiled it under openssl and something works there.... i haven't checked anything else but clone and chechout  you can definitely do it
|
|
|
|
|
|
Re: A1222+ issue with CD/DVD drives?
|
Posted on: 5/17 12:27
#63
|
Just popping in 
|
@thread
I've been following this thread with interest because I, too, have been building up my A1222+ and also have CD/DVD issues, although I think, in my case, it may be the particular CDs I'm trying to read.
I have a copy of Wordworth Office 6 and a copy of Vulcanology (the first 9 or so games by Vulcan Software - Bograts, etc), neither of which even show up on the desktop.
I have tried other CDs (mainly Amiga Future cover discs), which read OK.
The two particular ones I have problems with, I have tried in an iMac and a 2012 laptop, with no result, then in a 2015 laptop, where they do read.
The Amiga Future cover discs are professionally produced, whereas the Wordworth and Vulcanology are licensed copies, but produced by the vendor. I'm thinking that the professionally produced CDs were produced using a stronger laser, perhaps.
I seem to remember I used to have a CD/DVD writer and a CD writer in my old A1-XE, one of which was better at reading certain disks than the other.
The unit I have at present in my A1222+ is a new Asus CD/DVD/DL writer. I do have a slot loading CD/DVD writer which I'll try and see if that improves matters. I do also have an external drive which I'll try out.
|
|
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 11:57
#64
|
Not too shy to talk
|
Would be great if you could spare the time, even if it's just to see if we can work out why we can't build the existing sources so that we can dig into the issues. I'll have to go back and have a look at why the build was failing when trying to build simplegit source itself. It wasn't the easiest of things to track down though as it was downloading stuff and patching stuff and doing a lot of things beyond simply building.
|
|
Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 11:56
#65
|
Home away from home 
|
@MartinW Quote:
Apologies if my tone comes off as negative, but it's how I'm feeling about the platform in general at the moment and consequently it's not getting anything like as much of my attention as I would have liked.
That's ok :) You are not the first one and sadly not the last one who by some reasons at first think that obscure AmigaOS4 it is something which worth _that_ much. And that it have all the tools and languages available, and have a lot of developers and users. That of course was never and never will the case. Remaining of us trying to fix it in one or another way, but there are just not so many of us (and never will). Any obscure OS will have lack of tools, many strange things, lots of unfinished and unreleased stuff (and even released, but then removed), and lots of pure strange and unlogical things. Some of us tried as hard as possible to explain that for every newcomer about, that they not need to hold a lot of hope for, a lot of praise for, and there are no needs to make os4 looks as it didn't look like: in real is just obscure OS for the fanatics, hackers, low-level coders and all sort of ppls who in interest in “strange” things. But it will never be "usual OS where all available". The usage of the cross-compiler is simply better at current time because of above reasons : we have few developers, they all busy with everything else, so instead of spend their time on making native version of sgit , or awk, or whatever, they will be better use bug free, 100% times tested by 1000..xx users and developers around the world from compiler version to produce _native_ version of their tools. Not native building ? Yes, of course not native! Is it bad ? In current realm we should be happy that we even have cross-compilers , so we have a way to make work to be done with less issues, or to be done at all : for example, if not cross-compiler, there will be no Odyssye before, because even compilation of Odyssey few years ago for me on normal modern notebook take a hour. When we compile "only" gui parts on X1000 natively (8% of whole code), it take as much as it takes to build whole webkit (remain 92% of code). So you can imagine no one want to spend 2 days on building a thing, which can be build for a hour (and even faster today), only for "we can build it native" reasons :) Of course, that not mean we not need native development tools. Of course, we require them too and better to have them too. But if we should choose, then we have what we have and what developers find better, at least for now, in the current state of things. You shouldn't think that is issue with OS4 only : same happens with any obscure OS (And not only PPC and Amiga based ones). Even for ZX Spectrum all the games, all the art, all the coding done on PC tools and cross-compiler tools, and then adapted/polished natively. That just the reality of obscure and unpopular OSes and hardware. In other words, don't put OS4 where is not. In reality, it is an obscure OS with the developers-hackers and users who understand it issues, some of which, sadly, will never be fixed. And some will be even worse. If you can enjoy it as it, and accept — then there will be a fun for you. If you will “hope” for more and more and be it like you wanted it to be, or like you see it at first, then it will be just rage-quit, burn out, and all that stuff. Another practice can be applied to all this amigaos stuff: once you feel you are start to be annoyed, disappointed by anything , just take a rest for a month, or two, or a year, and then back when you will have motivation : at least that how some of us did :) @billyfish Btw, MightyMax taken over GDB porting, and few days ago were dealt with breakpoint/tracing stuff (he develops on qemu with peg2 emulation). So at least after few years there are progress in :)
|
|
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 11:47
#66
|
Just popping in
|
Hi all
Blimey it's been a while! I lost my dev set up on my old computer but I can take a look at rebuilding it again.
So my memory is like a sieve but I'm pretty sure that I had the option to build it so that it would use the amissl shared libraries rather than statically linking to openssl. The main issue was that at some point libgit2 moved over to using mmap () and munmap () and we didn't have support for those at the time.
Over the weekend I'll see if I can get it all set up again and see what I can do.
cheers
billy
|
|
|
|
|
|
Re: updating sgit
|
Posted on: 5/17 11:26
#67
|
Not too shy to talk
|
@Hans, yes, for me everything has been too big and it dies. It also lacks the options to be able to limit the size of the checkout. I found the source but it fails miserably to build just like a lot of other stuff. I even tried to create a smaller project by not including a whole section of the project and the checkout worked, then it failed because there’s a symlink in the repo and it died on that. At that point I gave up. Too many concessions having to be made to bother.
|
|
Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
|
|
|
|
Re: developing amiga 68000 clone
|
|
Not too shy to talk
|
@kerravonQuote:
Ok, and what about an OS (e.g. PDOS/386 and MSDOS) that relies on the IBM PC BIOS to do its work? And what about an OS (e.g. z/PDOS) that relies on intelligent hardware (ie mainframe hardware) such that there isn't a lot of work to do to create a CCW to obtain data from a device?
Generally that wouldn't be considered hosted as the OS would need to interface with any firmware. Unless there was a boot loader in between. But even then that usually acts as a middle man. Quote: Regardless of your answer to that, if you think using UEFI is "cheating", then there is no issue replacing the pseudo-bios layer that PDOS-generic relies on with direct access to hardware - ie partially (and pointlessly?) duplicating UEFI. I just haven't had a reason to do that (apparently?) pointless work. It hasn't been a priority. Right now my priority is to have a mini Amiga clone so that at long last I can actually test my Amiga executables without having to ask someone else to test them for me. I wouldn't say that's cheating. I would interpret hosted as running on a full OS and usually loaded by hand. But unless you have driver sources for all drivers you need you cannot be expected to fully take over the hardware. Modern UEFI is similar to Amiga ROM2.0+. With mouse and GUI. But in many ways surpassed a basic early startup menu. You can make use of WinUAE or any UAE to emulate an Amiga so you don't need a physical machine all the time. I can see what you mean by duplicating unnecessary work. A few years back I wrote a Linux chain loader for the newer AmigaOS4 machines that use a boot loader (called AmigaBoot) for menu between firmware and AmigaOS. Now I could have written a full boot loader that also presented submenus to chose from. But I would have need to write a ton more code and handle file loading myself as well the user needing to manually add it to the firmware menu as an option. I decided to make use of the existing menu loader, adding menu entries with a dedicated boot partition, and letting the boot loader load all the files in for me. I just needed to iterate through a list of files and it gave me freedom to support other compression formats. Quote: Ok, I was excited about this, as I don't like having to rely on registers at startup. However, I realized (incorrectly?) that in my case it doesn't matter. I need to get the number 4 (ExecBase) from somewhere (noting that the number will no longer be 4 when run under qemu-m68k Linux or Atari or whatever, so I can't see anything to be gained by switching to using ReadArgs. Note that I'm doing something similar for Linux itself - I don't get argc and argv from the stack - at least not as a first preference. I try /proc/pid/cmdline first instead - which normally always exists. That allows PDOS/386 to run certain Linux programs without needing to construct the odd stack. Ok so $4 is also known as ABSEXECBASE. It's the only consistent address in the whole Amiga OS. What I don't know iss why the OS just didn't pass it in a register and avoid using a 68000 vector. But the OS does use it on reboot. So you just need to read the pointer at $4 and store it as ExecBase. For arguments A0/D0 can be saved as well. But keep in mind it's just a string. Address and length. The C lib would read it and split it into an array of arg vectors. I've written ASM macros in the past that did this. You could also access it from the process CLI structure. That would avoid relying on registers. But again it's just a string that needs splitting. Unlike what I read about /proc/pid/cmdline containing null bytes. That looked like a bad idea when I read it at first. Using a null terminator as delimiter in a string.  Quote: I could put the (alternative to) the number 4 on the stack, which would allow standard C code to read it, but I would still need a flag of some sort to indicate that an alternative ExecBase has been provided. So the high bit in D0 seems to be as good as anything else, and I'm stuck with needing assembler code. Or does AmigaOS already put something on the stack that I could rely on and detect? Or any other technique? Do you need an alternative to ExecBase? Any program can read it from $4 (or 0x4) any time it likes. An alternative implies you are replacing it and I don't think you intend to rewrite an existing core kernel. You could save it or stack but it's always the same. Good idea to cache it as $4 is in chip RAM and incurs a slight penalty. So, AmigaOS or the AmigaDOS startup code doesn't stack anything for you. The AmigaOS ABI doesn't work that way. All OS functions take parameters in registers. In this respect it's somewhat like a RISC ABI. The 68000 provides 8 data and almost 8 address registers for use. The OS uses them. The only main exception is Intuition hooks where message data for lists is pushed to stack. And some other esoteric functions. Plus most C compilers would use stack based calling conventions. Quote: All those scenarios are possible depending on what user requirements are. However, the one that I am more likely to code personally is the one that uses AmigaDOS as a glorified BIOS. Because I may not be able to access the hard disks from PDOS otherwise, because the hard disks may require device drivers that are no longer supported and that there is no source code for. Replacing that for every bit of hardware is not really something I wish to do. Perhaps if there was a user requirement and a user willing to pay for development of that. But for me as a hobbyist - unlikely. Okay I can understand that. Well, the kernel is there to provide all that, so you might as well use it. So you have two basic ways about it. You could create a boot disk that has boot code to boot strap PDOS. That allows you to take over instantly. But also be able to use OS to read in disk blocks. From your own file system. Of course, though nice for testing, not very practical relying on floppy. The other way is for PDOS to be a shell. It simply runs as a command on startup and can take over that way. Cover disk menus also did this. The user can exit back DOS. Or run it independently. This would make use of Amiga filesystem and could be installed to a bootable partition at will. Either way this would be hosted but making use of core OS components. It is called PDOS and in this case AmigaPDOS so obviously a DOS interface and not entire OS replacement. It can customise a console to run inside a PDOS window. So drivers. This would be the easy bit. Device drivers for most hardware are added by the OS from the Zorro card ROMs. Plug and play so to speak. You just need to know the device driver name. There is Exec name and DOS name. Reverse name look ups from DOS name to Exec name are convoluted for some reason. Unless you need to write directly to disk blocks you don't need it. DOS is enough to read files from and SYS: is always assigned as boot volume. The only concern is 68040 and up need CPU libraries or it can crash. At this point, since you are still working on it, is how a PDOS binary will interface with PDOS. You could provide a PDOS library that all PDOS binaries open on startup. Standard Amiga binaries could be tested that way. But, the intention is for ELF binaries, so obviously this needs to executed by a PDOS shell. In that case you have full control over how PDOS passes itself. You will need an ELF loader as well. And I imagine a pass through for standard hunk binaries if that is supported. The user may be confused if running an Amiga binary doesn't work. But same user would be aware they are running in PDOS.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
|
Just popping in
|
@MamePPCA1
Can you launch a shell and type this:
"version SmartFuleSystem full" and give us the output?
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
|
Just popping in
|
@HypexQuote: Hypex wrote:@smf
Quote:If your partitions is SFS formated it's very important that your's usb boot media contains the "updated" sfs that supports the X5000.
I didn't think of this. Is the format changed? Most of my X1000 partitions are in SFS and would have been formatted before I installed Enhancer. So, would newer SFS be backwards compatible? But a newer SFS formatted volume be incompatible with an older SFS?
In this case if Enhancer has been applied to HDD but not recovery drive then that's simply a broken recovery and totally useless! This should have been tested before the machine was sent off from the dealer. The format has not changed, it's just that the "old" sfs does not support new machines like tabor and X5000 so for you it will be safe. But it's sure a little bit complicated for X5000 customers atm as they need to know how to prepare their own emergency boot pendrive if they want to run a better filesystem than what was offered when the latest os4.1 iso was shipped in case they run into problems. A-eon has created a great emergency boot iso for the tabor, they should do it for the X5000 too.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
|
Not too shy to talk
|
@MamePPCA1 I think smf is on the right track. By all accounts, from what you described, it looks like this recovery pendrive only has a basic OS4 system. It needs updating. While you could download an ISO from Hyperion if you could log in that wouldn't help. It lacks updated drivers. But make sure not to confuse the main site and forum logins as they are different. I've got stuck on that before. Make sure you log on from here with correct login: https://www.hyperion-entertainment.comDo you have an Enhancer CD as well as OS4.1 CD? If not do you have your AmiStore login? At this point I think the best course of action would be to update drivers on your recovery pendrive. Make a backup of your pendrive as a full drive image. It shouldn't be too large. Most USB imaging software can do this. 1. Now boot your pendrive to Workbench. 2.a If you have Enhancer CD then run the installer and select to only install Kickstart modules. Close all programs. Done. 2.b If not. You will need working internet. If not already set up and save. Download and install AmiStore. Run. Enter AmiSphere login. Select to download Enhancer. Once complete install Kickstart modules. You can also do so from Updater. Close all programs. Done. 4. Now updated fully reboot your X5000 and boot off recovery USB again. Just bear in mind Updater and AmiStore uses the AmiSphere login. Which is different to AmiUpdate. Info on Updater: https://wiki.amiga.org/index.php/UpdaterAmiStore: http://www.amistore.net/
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
|
Not too shy to talk
|
@smf Quote: This thread is a mess to follow so sorry if i'm pointing out something that's already been talked about or if i miss some information. You're right. It's become a mess. Unless it's obvious it's a bit hard trying to give advice remotely without seeing the machine in action. Quote: If your partitions is SFS formated it's very important that your's usb boot media contains the "updated" sfs that supports the X5000. I didn't think of this. Is the format changed? Most of my X1000 partitions are in SFS and would have been formatted before I installed Enhancer. So, would newer SFS be backwards compatible? But a newer SFS formatted volume be incompatible with an older SFS? In this case if Enhancer has been applied to HDD but not recovery drive then that's simply a broken recovery and totally useless! This should have been tested before the machine was sent off from the dealer.
|
|
|
|
|
|
Re: updating sgit
|
|
Home away from home
|
@MartinW Has sgit stopped working? I remember it working okay for smaller projects, although it took some getting used to. I did have trouble with sgit with larger projects (like ZitaFTP Server), which is a contributing factor to me reluctantly switching almost exclusively to cross-compiling. Like you, I'd rather work directly on AmigaOS, but I'm more productive when building on another machine. The sgit source code is here. I remember having trouble finding it because the repository is called "simplegit" instead of "sgit. Quote: Apologies if my tone comes off as negative, but it's how I'm feeling about the platform in general at the moment and consequently it's not getting anything like as much of my attention as I would have liked. The lack of tools, outdated libraries and other problems can be frustrating, and squash motivation. Hans
|
|
|
|
|
|
Re: Hello!
|
|
Quite a regular 
|
@dfstudios
Welcome to Amigans. I hope you enjoy your A1222 Plus.
---
redfox
|
|
|
|
|
|
A "tutorial" how to reply to negative comments
|
Posted on: 5/16 22:11
#75
|
Just can't stay away 
|
Here's a "tutorial" how to reply to negative comments in the Internet (90s style). (Contains bad language.) https://www.youtube.com/watch?v=x_QmvZRS85UIt's funny how that video reminds of some of the Amiga forums.
|
|
Rock lobster bit me - so I'm here forever
X1000 + AmigaOS 4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
|
|
|
|
Re: updating sgit
|
Posted on: 5/16 21:19
#76
|
Not too shy to talk
|
Currently there isn't a working git command for OS4. Yet another thing to add to the list of stuff that doesn't work unfortunately.
The problem (as far as I've seen anyhow) is that many people don't develop directly on OS4 and I've even had the comment (more than once) you would be mad to try. Personally I think you'd be mad to spend £2k on the hardware and NOT use it to develop on! But there appear to be few of us that think like that.
Anyway, I've been sat here trying to work out if I could get libgit2 to build against AmiSSL but I wouldn't have a clue how to even tell ligbit2 about AmiSSL. While AmiSSL says it's 100% OpenSSL compatible, at the end of the day it's not OpenSSL and without cmake find scripts and the like, it's probably beyond my skillset (again) to get it building.
I spent a day last weekend following along to one of the "build yourself a git client" articles, which happened to be in Python. It was fun. Everything looked do-able. Until you realise that everywhere they hit complicated bits, they skipped them (clone being one of the big ones, pack files being another - though I'm sure I could work that out). All the same it was fun and I thought I could take that approach instead.
Then I realised that OS4 has an ancient version of Python and I hit a very similar brick wall looking for a 3.x version of Python for OS4. There at least appeared to be a v3.8 but as is often the case, it's alpha and not been released, so may as well not exist.
Apologies if my tone comes off as negative, but it's how I'm feeling about the platform in general at the moment and consequently it's not getting anything like as much of my attention as I would have liked.
|
|
Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/16 19:14
#77
|
Quite a regular
|
@HypexQuote: Hypex wrote:@MamePPCA1
Quote:As I told before my AmigaOne X5000 resets after the splash screen.You can read it probably on my first posts.
Ah yes, it's on the second page. Forgot about that. Ok, so that proves the partitions are still there or at least the partition holding the Kickstart. Which should be on DH0.
Quote:
Using Media Toolbox. But I wouldn't recommend it without a backup. It will delete all records of your partitions.
Quote:And as I said before my HDD partitions shows on Media toolBox.3 in total.
I can't think of any reason for them go missing. Usually there would be some sign like an NDOS icon on Workbench for any corrupt partition. Is it the same in the CLI? So if you run Info in a shell window is there also no sign? Assign is another command that will give info.
Quote:Partition Wizard doesn't run.I tried before and no luck.
The pendrive should have a compatible version. It may just be a basic recovery Workbench without any Enhancer fixes or just Radeon driver. While it's usually all pre-installed by a dealer that only works if the system doesn't break. Which in reality a recovery system should be able to fix. However your problem is unusual.
These days an X5000 is offered with an SSD drive. Currently Amedia sells it with one. What isn't ruled out yet is the HDD going faulty. The problems you experienced could be a symptom of that. The first HDD on my XE played within a few short years. Yes the partitions are there,no doubt but I have mounted with Mounter on SYS:System I think.When they are mounted with this it appears a hand over it.All of this via pendrive that is the only way to see Workbench these recent days. Yeah I will not mount RDB on MediaToolBox.It could be dangerous. Yes my 3 partitions are not missing they are all shown inside my MediaToolBox utility. I don't know if the pendrive has an compatible version of Partition Wizard.Yeah I know my problem is unusual but for now is a gigantic or great problem. I don't need Amedia that they usually doesn't answer.I also have a pendrive.And yes I have an AmigaOne and is a very faulty
|
|
Amiga 500 1MB Chip RAM with ACA 500+ACA1232,CD32,Amiga 1300 030/50 Mhz,32MB (now on my hands at least)and Amiga One G3 XE PPC 800 Mhz,ATI Radeon 9250 128 MB,256 MB RAM,Seagate 200 GB HD,2 working DVD drives,X-Arcade double for MAME,Sil0680,4 USB ports,LG
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/16 18:57
#78
|
Quite a regular
|
@smf
OK but where is an recent/updated SFS to boot from for example my pendrive?
I really need to know,so please help me someone.
My AmigaOS 4.1 is very important
|
|
Amiga 500 1MB Chip RAM with ACA 500+ACA1232,CD32,Amiga 1300 030/50 Mhz,32MB (now on my hands at least)and Amiga One G3 XE PPC 800 Mhz,ATI Radeon 9250 128 MB,256 MB RAM,Seagate 200 GB HD,2 working DVD drives,X-Arcade double for MAME,Sil0680,4 USB ports,LG
|
|
|
|
Re: A1222+ issue with CD/DVD drives?
|
Posted on: 5/16 16:36
#80
|
Quite a regular
|
@graff @dfstudios
Ok, I understand, thanks for the advice. I have decided to use an external USB HUB with a separate power supply to make sure there is enough power available. I hope this solution works.
Also, yesterday I was able to buy an RX 570 ITX graphics card for the ITX tower with 8GB at auction, so I can test this card in addition to the RX 550 4GB ITX to see if there are any speed differences under AmigaOs4.1 with these cards. I will open a separate thread for this test later and whoever wants to can then participate and publish their results as well.
Which tool is best suited to perform graphics card tests under AmigaOs4.1 2d/3d accelerated?
The a1222plus supports DDR3 SODIMM 64 bit interface
400Mhz, but is it also possible to use SODIMM with 1333/1600 MHz, or will the system then become unstable? I have read that this board has been tested with the SODIMM 400MHz as standard configuration with AmigaOs4.1.
Edited by Maijestro on 2024/5/16 16:56:14
Edited by Maijestro on 2024/5/16 16:57:12
|
|
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
