I was happy to see the releaes of 3.2. This means it's about time to get a G5 tower, though in the mean time I figured I'd update my Efika. Strangest thing though, I can boot off the EfikaInstall.img, and it tells me my system resources at the bottom with butterfly boot logo at the top, but that is as far as it gets and my drive keeps flashing like it's still loading, though it's been a good 30 minutes.
So I am wondering, was this release tested and varified on the Efika board, and if so, what should I do to get this to install?

Thanks in advance!

Update, I rebooted and after 15 minutes (about) I arrived and am still sitting at a screen with great and white bars across it.

For the note, I am installing off the same USB stick that I used to install 3.1 from previously.

EDIT: Since then I went down stairs to get some coffee, I came back up and the butterfly logo was present again, though now it just went back to the white and grey screen.

[ Edited by XDelusion 28.05.2013 - 16:06 ]

My second attempt was also fruitless, so I re-downloaded the Efika Boot image, this time from Germany, and so far I'm still getting the same exact results.

Installed MOS3.2 on my EFIKA without any problems - runs great! Did net-boot (install.img) from TFTP-Server and put MOS then on internal HD.....
I did this manually - be sure that you have installed the right boot.img for the EFIKA (found as bootefika.img in the MOS-iso) on your boot-partition.....

Installation of 3.2 to Efika is currently in progress. Copied the efikaboot.img manually to the boot partitition, and rebooted with the 3.2 boot.img - worked so far. Then copied the iso to a stick, mounted that iso, launched teh iWizzard and assigned teh iso as source and sarted teh update process. Copy process is still in progress.
IIRC I did most if not all updates that way. The usb boot takes too long.

Update finished, everything went fine. Now three 3.2 machines in the house. Nice!


[ Editiert durch Zylesea 28.05.2013 - 23:48 ]

Amigaharry2: I've not tried the TFTP-Server method. Does that require a secondary MorphOS machine?

What I did was download the morphos-3.2-efikainstall.img (twice) off the MorphOS page.

Put that on the same USB drive that I had used for the 3.1 install.

Since I read your response, I tried the boot.img from the 3.2 Install ISO, but that failed to boot.

Are you sure you've taken the right boot.img (bootefika.img) and put it to the right destination and renamed it correctly (or adjusted the boot comand accordingly)?
The only variable hardware (except usb things) on Efika is the gfx card, what gfx card do you have. I have a 9250 SE/128 MB/AGP.

It can be done even with the offical install iso, when there is already a MorphOS installation.

Download the full ISO (2xx MB) for Peg2, Mac etc.
Put it on your system/boot.img partition name it boot.iso <- iso!!!
Double click it and grab the bootefika.img and copy it to system/boot image partition, where you change the name to "boot.img"
Open a shell and type "info" to get the device name of the partition were you copied the full iso. e.g. "Dh0:"
Reset and enter open firmware
type "boot boot.img bi Dh0:boot.iso"

Now it should boot the CD within seconds and you simply install like on peg2 or mac after inserting the CD.

Geit

I'm positive. Neither the IMG off the ISO or the one off the web site works.
I have installed 3.1 succesfully using my Radeon 7000.

When you installed, did your screen present the kind of garbage that mine did during the load time for the installer?

No joy installing 3.2 on my Efika as yet. This is the first time I've had it connected via dvi (samsung syncmaster 2494hs) and the previous 2.7 install & 3.2 efikainstall.img don't offer any resolution beyond 1280x1024. I might try the vga connector later...

(Edit) ok, scratch that. I gave up too soon on the morphos-3.2-efikainstall.img - it booted successfully and even got the right resolution this time. It does seem to pause in the smart firmware screen a bit longer than usual and outputs different text than I've seen before but it's been a while since I've spent any time using the Efika.

(2nd Edit) 3.2 installed successfully - the only minor issue here is that, once again, 1280x1024 is the highest available resolution. Really need to try the vga connector now...

[ Edited by ausPPC 29.05.2013 - 09:45 ]

I heard another user having trouble with his ATI 7000 gfx card (not on Efika though, but Pegasos). That may be at least a hint.
http://www.pegasosforum.de/viewtopic.php?f=1&t=4843

>>When you installed, did your screen present the kind of
>>garbage that mine did during the load time for the installer?

No garbage at all.


[ Editiert durch Zylesea 29.05.2013 - 00:37 ]

I just tested the 3.2 , 2.7 & 2.6 morphos-x.x-efikainstall.img files with a vga and dvi connection and they all detect the native resolution for my display. Regardless of vga or dvi, 2.7 and 3.2 boot into 1280x1024 and I can't choose any higher resolution. My previous display was an asus vh222 (vga only) and MorphOS never had an auto detect issue with it.

Jugding by that thread above and the fact that I can still boot the 3.1 Install, I'd say the 7000 drivers got thrashed in the upgrade. Could be wrong, but that seems to be the deal.

For the sake of completeness, I setup my former asus vh222 & samsung syncmaster 740n displays to test with the Efika. As expected, no problem detecting the native resolutions (1920x1080 & 1280x1024 respectively) on 2.7 or 3.2 installs.

Just to reiterate, the morphos-x.x-efikainstall.img files correctly detect the native 1920x1080 resolution of my newly acquired samsung syncmaster 2494hs but, once installed, MorphOS 3.2 and 2.7 are limited to a maximum resolution of 1280x1024.

Fingers crossed my mac mini won't have this issue when it arrives.

You probably forced the system to use your old monitor settings file and disabled DDC (display detection stuff).

Check if the file "ENVARC:CyberGraphX/RadeonMonitor" exists. It contains the name of the detected monitor and if the file exists, no DDC takes place.

So if it does exist, delete it and reboot. This will reenable autodetection.

Geit

[ Edited by geit 30.05.2013 - 02:00 ]

Thank you for this info, Geit. I don't think I actually managed to boot into 3.2 on my Efika yet... I've forgotten how to tell the boot.img which partition to boot from.

Also, the sys:prefs/env-archive RadeonMonitor file was still identifying my asus monitor but the Ram:ENV RadeonMonitor file showed the name of my current monitor. I deleted the RadeonMonitor file in sys:prefs/... and rebooted but still don't have a native resolution display.

Anyway... I'm going to go look for the parameters that can be passed to boot.img

(Edit) For me, on my Efika, I needed to enter:

> boot hd:2 boot.img bd=dh2

to properly boot into 3.2 - and it auto-detects as expected. The problem I was having was making an incorrect assumption about which partition was being booted from.

Thanks for bearing with me!

[ Edited by ausPPC 30.05.2013 - 12:40 ]

My previous 2.7 install is displaying at the native resolution now. I must have had my Efika connected to my smaller samsung display some time ago. I found a file for it in sys:prefs/presets/monitors and deleted it, rebooted and then autodetect did its magic.

Now I'm having a different display related problem in 3.2 I'm not sure if I noticed this previously but after checking out a few screen blankers and simply canceling out of that preference selection, intermittently, sometimes every few minutes, the screen goes blank for a second or two. This behaviour has persisted after a reboot...

I'm still stuck on 3.1 my self.

XDelusion,
Quote:

Can't you just download the 3.2 iso onto your Efika's hard drive and copy the MORPHOS folder to your System partition (rename the System:MORPHOS folder first) and copy the Efika boot.img from the iso to your boot: partition? (Rename boot:boot.img first too)

That seems to me to be the simplest method, have you tried to do it that way?

@XDelusion: Sorry, was'nt online the last days...... TFTP_servers are also available on Windows or MAC. In my case I use it on a second MOS-PC (Pegasos2) with TFTP-Server from Aminet....you need only the Efika "install.img" in the same directory as your TFTP-server. Please notice: install.img ist not the same as "efikaboot.img"! Install.img contains a rudimentary "mini-boot-system", which is only usefull for a following main-installation.....
After starting TFTP-Server type in OF-Console of EFIKA: "boot eth:<Net-adress>, install.img". Net-Adress is the adress from your TFTP-Server (eg: 192.168.0.xxx). Don't forget the blank(!) before the word "install.img"!!
Then Efika will load the image and boot......Once Efika has boot, you can install MOS3.2 from a stick .....

Amigaharry2: Thanks, I'll probbably try the second solution you mentioned, though I'm really thinking that 3.2 has issues with the 7000 where as 3.1 did not. Also, I put a CF card onto an IDE adaptor and tried installing 3.1 onto that as well. Again the installation went flawless from the same USB drive. So given that, I would think 3.2 should install from it fine as well.

I'd love to see someone on here with a 7000, try to do an install with the 7000 plugged in, just to see if they get the same graphical garbage and boot resets that I'm experiencing.

I tried it for test now in EFIKA with a 7000 GraKa ---- you are right! After showing MOS-Bootscreen the system hangs up! I can't boot wether from net, nor from internal HD - always same behaviour under MOS3.2! With Radeon 9250 no problem!

Agh ha! Thank you for that, so it does seem as though support for the 7000 has been damaged. You and I are not the only ones to experience this.

> I'd love to see someone on here with a 7000, try to do an install with the 7000 plugged in,
> just to see if they get the same graphical garbage and boot resets that I'm experiencing.

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=9252&forum=11&start=1

XDelusion

I have the same problems you have on Two Efika and a Pegasos 2. All three have Radeon 7000 cards. Like you said boot screen with white bar in the corner then garbage and resets.