AmigaOS 3.2 + A600 + Furia + Indivision ECS v2 = black screen - Page 2

mja65 · 14 September 2021, 05:30

It only worked for me with a CF card of either 512MB or 1GB. Anything larger than that I get the issues listed above. It definitely appears to be related to 3.2 as the same cards that fail works fine when booting from a floppy with an older ROM (I was using maprom to load the 3.2 ROM) as well as when loaded with 3.1.4. I have tried both CF and SD with the same outcome - and despite the reputation of the Furia being picky with the media all work fine with 3.14.

It's also unlikely to be the media, as the cards that work happen to be some random cards from an old camera I had lying around which are close to 20 years old.

joedredd · 14 September 2021, 17:15

Quote:

Originally Posted by CCRider

Has anyone succeeded on getting ROM 3.2 to work on a Furia EC020 equipped A600? Or we’ll have to wait for an eventual firmware update for this accelerator?

Works fine on mine after following this advice:

https://eab.abime.net/showthread.php?t=107157
“please try deleting V47 scsi.device from devs: (it would possibly sit in a subfolder A500/A600/A2000 or something) or move it to another directory outside of devs:.”

mja65 · 15 September 2021, 03:05

Quote:

Originally Posted by joedredd

Works fine on mine after following this advice:

https://eab.abime.net/showthread.php?t=107157
“please try deleting V47 scsi.device from devs: (it would possibly sit in a subfolder A500/A600/A2000 or something) or move it to another directory outside of devs:.”

Yes that does work for me - but only if using an older Kickstart. As soon as I map kickstart 3.2 using the maprom command I get the same error. I'm assuming this relates to the scsi.device included in the rom.

joedredd · 16 September 2021, 09:47

Quote:

Originally Posted by mja65

Yes that does work for me - but only if using an older Kickstart. As soon as I map kickstart 3.2 using the maprom command I get the same error. I'm assuming this relates to the scsi.device included in the rom.

I can't *quite* remember or check right now due to everything being packed up....but I'm pretty sure I had that issue when mapping too - but it worked when I got my physical 3.2 roms. Which doesn't make a whole load of sense to me, but there you go.
I might get chance to set it up this weekend.

mja65 · 17 September 2021, 11:32

Quote:

Originally Posted by joedredd

I can't *quite* remember or check right now due to everything being packed up....but I'm pretty sure I had that issue when mapping too - but it worked when I got my physical 3.2 roms. Which doesn't make a whole load of sense to me, but there you go.
I might get chance to set it up this weekend.

Will be interested in what your setup is - if indeed it works as it might be worth ordering the physical ROM.

What i've found so far (all these work under 3.1.4 via maprom with a 3.x ROM):
512Mb CF Card - works under map rom 3.2
1GB CF Card - works under map rom 3.2
8GB CF Card - does not work under maprom 3.2 - works with 3.X ROM, OS 3.2 installed, SCSI.device file removed from DEVS
32GB SD Card - does not work under maprom 3.2 - works with 3.X ROM, OS 3.2 installed, SCSI.device removed from DEVS

ugrnm · 20 October 2021, 01:07

Quote:

Originally Posted by CCRider

Has anyone succeeded on getting ROM 3.2 to work on a Furia EC020 equipped A600? Or we’ll have to wait for an eventual firmware update for this accelerator?

Not that I know of. I saw that v13.1 was published there https://lotharek.pl/productdetail.php?id=322#files but no Changelog. Would be great to hear back from Boboo_SK

With that said, I've been using 3.2 on Furia v13 and 3.1.4 kickstart with the file modification documented in this thread without an issue.

astuermer · 01 November 2021, 21:48

Whats the latest physical Kickstart ROM the Furia is compatible with on the A600?
I had 2.0 installed but ordered 3.2 last week… now I read this thread about incompatibility with AmigaOS 3.2?
I have the same hardware setup - except the Indivision ECS v3 coming soon.

Update - Ok Lotarek answered me a few mins ago that only 3.1.4 is the last compatible official ROM in certain hardware constellations like this.

Update 2 - Ok it doesn't need a Indivision for this error. Rev 2 Furia here and only booting with Kick 3.2 with floppy, but NOT SD.

Thanks

01 November 2021, 21:48	#27
astuermer Registered User Join Date: May 2005 Location: Austria Age: 45 Posts: 117	Whats the latest physical Kickstart ROM the Furia is compatible with on the A600? I had 2.0 installed but ordered 3.2 last week… now I read this thread about incompatibility with AmigaOS 3.2? I have the same hardware setup - except the Indivision ECS v3 coming soon. Update - Ok Lotarek answered me a few mins ago that only 3.1.4 is the last compatible official ROM in certain hardware constellations like this. Update 2 - Ok it doesn't need a Indivision for this error. Rev 2 Furia here and only booting with Kick 3.2 with floppy, but NOT SD. Thanks Last edited by astuermer; 03 November 2021 at 19:19.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
FS-UAE 2.83 + AmigaOS 4.1 = Black Screen	D1mch	support.FS-UAE	12	16 September 2020 19:49
Indivision ECS A1000 Adapter in a A600 with A603: Does this work?	crazyegg	support.Hardware	3	23 March 2016 14:49
Indivision ECS Flashes Through Screen Under WB1.3, Fine Under 3.1	Loedown	support.Hardware	3	02 September 2013 15:34
Building an Adapter for ECS indivision in A600 to allow floppy usage	kipper2k	Hardware mods	1	25 February 2011 20:33
Creating a flexi cable for the A600 ECS Indivision	kipper2k	Hardware mods	38	22 February 2011 16:59

14 September 2021, 05:30	#21
mja65 Registered User Join Date: Sep 2019 Location: Spotswood, Australia Posts: 31	It only worked for me with a CF card of either 512MB or 1GB. Anything larger than that I get the issues listed above. It definitely appears to be related to 3.2 as the same cards that fail works fine when booting from a floppy with an older ROM (I was using maprom to load the 3.2 ROM) as well as when loaded with 3.1.4. I have tried both CF and SD with the same outcome - and despite the reputation of the Furia being picky with the media all work fine with 3.14. It's also unlikely to be the media, as the cards that work happen to be some random cards from an old camera I had lying around which are close to 20 years old.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)