Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: freqmax on April 19, 2011, 02:35:35 AM
-
I tried AROS m68k in e-uae-0.8.29.w4_5 and uae-0.8.29_1 and it will only show a black screen with 2M chip + 1M fast. In all combinations of 68000/68060, ECS, AGA, A500, A1200 etc.. While both kickstart 1.3 (512k) and 3.5 (512k) works without any problems.
So what to do, to get AROS-m68k running?
Files:
http://aros.sourceforge.net/cgi-bin/nightly-download?20110417/Binaries/AROS-20110417-amiga-m68k-system.tar.bz2
http://www.amigaemulator.org/
-
Kickstart 1.3 should only be 256k.... and did you try inserting a Workbench disc? :lol:
-
I tried a KS1.3 from some site. Anyway it should show the "insert disc" image without a disc.
-
AROS 68k has two ROM files, a Kickstart and a Kickstart ext, you will need both (i forget the e-UAE options to load that). The emulator should be set up exactly as an A1200 with 4meg fast ram and if possible RTG. It should work then, IIRC AROS doesn't show a disk prompt you should ensure a bootable disk (hard or floppy) is available)
Note: re the 512k 1.3 ROM, I had to double up my ROM image to make DOS UAE work many years ago... I guess any that are floating around probably still are doubled up :)
-
68k AROS only works on actual Amigas and Winuae at the moment. Even Winuae needs to be at least 2.3.1b8 (although Id suggest using actual 2.3.1). None of the other UAE's are upto date enough to run it.
-
fishy_fiz, What is the magical difference in the WinUAE update that makes it work?
(or what makes the current ROM so troublesome?)
Seems the emulator (uae) get's stuck at this:
F812A0 MOVE.W $00DFF018 (http://en.wikipedia.org/wiki/Amiga_500#Memory_map),D0
F812A6 BTST.L #$000D,D0
F812AA BEQ.B #$FFFFFFF4 == 00F812A0 (TRUE)
F812A0 MOVE.W $00DFF018,D0
etc..
What's at $00DFF018 ?, SERDATR ?
I checked the kickstart 1.3 file. And it's duplicated 2x. :)
As for the AROS-68k it consists of two files rom + ext. And the emulator only loads one. So I assumed it has to be loaded in one contiguous file. Ie "cat rom.bin ext.bin > emu.rom".
-
fishy_fiz, What is the magical difference in the WinUAE update that makes it work?
More uptodate emulation :)
-
Seems $00DFF018 really is SERDATR (http://amigadev.elowar.com/read/ADCD_2.1/Hardware_Manual_guide/node003D.htm) and thus it waits for the serial receive buffer to become 0xD .. doh..
The UAE debugger also misses intuitive help text ...gah
-
If I put NOP (0x4E71) into fileposition 0x12AA (F812AA) then uae at least starts to show lightgrey. So it's not completly fucked ;)
-
I tried AROS m68k in e-uae-0.8.29.w4_5 and uae-0.8.29_1 and it will only show a black screen with 2M chip + 1M fast. In all combinations of 68000/68060, ECS, AGA, A500, A1200 etc.. While both kickstart 1.3 (512k) and 3.5 (512k) works without any problems.
While it won't work in EUAE, if you did find a combination that worked, the most likely ones would require graphics card emulation. It is that way because the AGA-specific drivers don't work very well since they are incomplete. Currently Toni Wilen, the WinUAE author and Kickstart bounty #2 programmer, is working on implementing automatic screen switching for the chipset modes and RTG modes to share a window.
-
Any news since last on the AROS-m68k front?
-
I was wondering how to get this running on an actual Amiga. Anyone have a breakdown or a web link that explains it step by step?
All this hullabaloo surrounding legacy OS is starting to frustrate me :)
-
TheBilgeRat:
download the current nightly. in the distfiles folder you will find an adf archive of a boot floppy. using f.i diskimage device (http://aminet.net/disk/misc/diskimage.m68k-aos.zip)
you will be able to decompress it to a real floppy. also the best is to prepare aros boot partition on a hard disk (just coppy the content of nightly to it and mark the partition as bootable).
now, boot from the prepared floppy drive, which will extract the aros kickstart to ram and boot from there. you can recognize aros kickstart booting by dirty-ocker-yellow color on screen (lol). if you have a bootable aros harddisk partition attached to the system (preferably via internal ide or accelerator scsi) chances are that your system will boot to wanderer. be sure to have it a highest priority hd.
i have tested and can confirm a4k 030/040/060 as working, except for csppc. also many configs of a1200 work, in particular blizzard 1260. there is problem wit elbox fastata so far i see.
anyways further testers would be very welcome.
-
Whats the requirements of aros68k on a REAL amiga?
-
i suspect aros might currently boot up on a1200 with 4mb fast ram. i will try to test it tomorrow since i have an exemplar in my studio. it should through definitely boot from ide on a1200/a4000 equipped with =>030 and 16mb ram. note that aros is still generally very slow, especially on aga.
-
TheBilgeRat:
download the current nightly. in the distfiles folder you will find an adf archive of a boot floppy. using f.i diskimage device (http://aminet.net/disk/misc/diskimage.m68k-aos.zip)
you will be able to decompress it to a real floppy. also the best is to prepare aros boot partition on a hard disk (just coppy the content of nightly to it and mark the partition as bootable).
now, boot from the prepared floppy drive, which will extract the aros kickstart to ram and boot from there. you can recognize aros kickstart booting by dirty-ocker-yellow color on screen (lol). if you have a bootable aros harddisk partition attached to the system (preferably via internal ide or accelerator scsi) chances are that your system will boot to wanderer. be sure to have it a highest priority hd.
i have tested and can confirm a4k 030/040/060 as working, except for csppc. also many configs of a1200 work, in particular blizzard 1260. there is problem wit elbox fastata so far i see.
anyways further testers would be very welcome.
Awesome, thanks wawrzon! I'll muck about with it soon. I have a 40Gb IDE drive laying about and an A4000/40 with 16M ram.
-
you welcome.
in my opinion best is to connect your hd to pc with running uae to copy the nightly files on it if your amiga has no internet access. also the secondary 3.x partition is useful for maintenance as decompressing the adf to floppy.
-
you welcome.
in my opinion best is to connect your hd to pc with running uae to copy the nightly files on it if your amiga has no internet access. also the secondary 3.x partition is useful for maintenance as decompressing the adf to floppy.
I don't run WinUae, but linux UAE. Will that be an issue?
-
most likely. first of all the kicksart file exceeds 512kb and is provided in form of two winuae specific files. you might try to boot it like a real hardware, that means first with regular 3.1 kick file from provided adf floppy, and then when aros kick has been succesfully loaded from the aros partition.
-
I don't run WinUae, but linux UAE. Will that be an issue?
Try winuae under wine... It worked well for me.
-
i suspect aros might currently boot up on a1200 with 4mb fast ram. i will try to test it tomorrow since i have an exemplar in my studio. it should through definitely boot from ide on a1200/a4000 equipped with =>030 and 16mb ram. note that aros is still generally very slow, especially on aga.
Then you need a gfx-card for normal usage, too bad.
-
I think the biggest problem isn't the chunky-to-planar support being required for all graphics, although that is a big problem. I think the biggest problem is that GCC 4.5.1 has a terrible 68k backend which makes the code run terribly slow.
-
amiga rtg support is not even implemented yet on aros except uae. in fact aros as system runs yet much, much too slow (on real hardware) in most respects, and i dont think it is a question of unoptimized compiler backend, in which case i would expect a factor 2 -3 speedup best case,
-
I tried AROS m68k in e-uae-0.8.29.w4_5 and uae-0.8.29_1 and it will only show a black screen with 2M chip + 1M fast. In all combinations of 68000/68060, ECS, AGA, A500, A1200 etc.. While both kickstart 1.3 (512k) and 3.5 (512k) works without any problems.
So what to do, to get AROS-m68k running?
Files:
http://aros.sourceforge.net/cgi-bin/nightly-download?20110417/Binaries/AROS-20110417-amiga-m68k-system.tar.bz2
http://www.amigaemulator.org/
Hi,
The way to get AROS to run is a hope, a prayer, and a lot of patience, which I don't have, it runs semi on my computer with no Internet. I just gave up, you needs this, then you needs that. It is sort of like an Amiga, the hardware just don't operate with everything (ever try to run a printer on the Amiga, unless you use the ones on their list forget it.
smerf
-
@smerf
And what have the troubles getting AROS to work with millions of different x86 configurations to do with achieving support for the extremely few 68k Amiga platforms available?
-
Is adf2disk adequate for making the AROS boot floppy?
-
yes, of course.
-
I'm copying over the 5-22 nightly build now to the AROS partition, soon to be making the kickstart floppy. It's kind of exciting!
-
make sure to cold boot. after the floppy boots alright, and toldyou it has successfulle decompressed aros kick to ram remove floppy from the drive. short dirty yellow screen flash will tel you aros kick is resident. wait now, it boots long. if nothing works try to reboot without startup sequence. in case of further trouble serial debugging might be necessary.
-
make sure to cold boot. after the floppy boots alright, and toldyou it has successfulle decompressed aros kick to ram remove floppy from the drive. short dirty yellow screen flash will tel you aros kick is resident. wait now, it boots long. if nothing works try to reboot without startup sequence. in case of further trouble serial debugging might be necessary.
OK, so procedure is...
1. Cold Boot with Kickstart floppy in drive
2. wait for it to say successful load into ROM.
3. Dirty Yellow Screen.
4. Remove kickstart disk.
5. Wait a while
?
I've done that, and the HD light stays on for a while, then we just have a blank screen. I'll give it a try with no startup sequence.
-
did the floppy loaded succesfully? if not choose it as boot device in early boot, holding both mouse buttons. same procedure to get into aros early boot to be able to boot without s-s.
-
did the floppy loaded succesfully? if not choose it as boot device in early boot, holding both mouse buttons. same procedure to get into aros early boot to be able to boot without s-s.
Boot floppy says successful. I had floppy as pri 5, AROS partition as pri 3 and normal partition as 0. Floppy says successful boot, screen flashes ochre, I remove disk, then black screen with disk activity, then black screen without disk activity. BAsic A4000 with full ram.