@AmigaOldskooler

Thank you so much!

@AmigaOldskooler

Thank you so much!

Trygve is super cute! :)

@Hitman

I use Kingston KC600 512GB 2,5" SATA III (SKC600/512G) connected through SiI3114 and never had any issues with it.

@afxgroup

That's totally fine! The driver in its current version is already good enough for me to consider freeing up a PCIe 1x slot if I'd need it.

@afxgroup

Testing on my Sam460LE with driver's version 2.3 and the CSL card you've suggested in your post #2.

So far so good, the device is recognized by the OS on the fly, I can select one of the new modes. Played some games (Quake 2, Starfall Defenders and UBEK) and had a proper sound in all of these. Watching videos with Emotion worked good as well.

What didn't work quite well was playing music with AmigaAMP. It gets sound glitches from time to time, and if there's a concurrent operation happening in the OS like resizing Filer's or MultiViewer's window, the sound gets terribly sliced while window keeps getting rerendered.

Two more observations, that are not problems by themselves, but probably worth mentioning:
* the test sound in Sound Prefs is rather weird
* there is also weird sound playing for a while in the exact moment the AmigaOS 4.1 splash screen appears during OS loading.

Once again thank you for your awesome work!

@smarkusg that's really cool stuff!

@afxgroup
Another fantastic work from you, thank you so much!

I've ordered this CSL card and will do some testing with my Sam460LE once it arrives :)

@sailor
Quote:
Exactly!

@smarkusg

Not a spam at all - quite the contrary, I appreciate your work and admire your passion a lot!

Btw, I really like this nice, truly oldshool feeling that Chocolate Quake has!

Thanks for sharing!

Thank you! As always, it's really nice to have these roundups!

As for the headlines idea, it works very well imho! Please keep this :)

@afxgroup

Absolutely AWESOME! Thank you!!!

@samo79

Quote:

I'd be delighted to have MK3 running natively on AmigaOS4. If such project starts, I'm more than happy to support it as well :)

@Skateman

Awesome! Thanks for sharing!

@daveyw

I was referring this part:

Quote:

So in our case, the solution to the USB problem was to go into U-Boot command line and run "usb reset" command.

@skynet

I don't have any evidence of Candi working after Update 3 (sorry if I made it unclear).

When we've tried to apply Update 3 for the first time, we had Candi up and running. Things went wrong and after trying to boot from USB stick, we've experienced some Grim Reaper errors, including the one related to Candi.

On the second attempt at installing Update 3, we had Candi switched off and didn't even try using it after the update.

@MazinKaesar

Thank you for the hint! It will certainly be very helpful at some point in future!

@smf

Quote:

As @smf mentioned in the quoted fragment, grey screen occurring between the U-Boot and AmigaOS splash screen indicates a problem with Kickstart. Obviously, grey screen is not very informative, and connecting through a serial cable may be a bit of a hassle for somebody who didn't do it before. Being a Sam owner, I have little experience with X5000, but still I have a small observation that I somehow hope could be helpful.

When supporting my colleague in restoring his X5000 back to life after Update 3, accidentally I've made a typo in the Kicklayout file in the bootable pendrive I've created. This resulted in a strange behaviour and also a grey screen - even after we've reinstalled AmigaOS from scratch. Of course the problem here was that because of that typo, one of the files from the Kickstart wouldn't load and at the same time it tried to load the mistyped file that did not exist at all.

How did I learn about it? I have entered the boot menu, selected Boot from Hard Disk option, and then triggered boot procedure by typing "boota" in the command line. This way I could see some useful information during Kickstart loading, in particular the message about the missing file. Much more helpful than simply a grey screen. Now I wish I knew that before we decided to format the SYS partition.

My point is, maybe someone who still hasn't resolved this issue, could try this approach and see if it brings anything to the table.

@daveyw

Looks like Update 3 can mess up with USB.

Feel free to look at my post in the other thread (which also is a follow up on this post). I described issue with USB after applying Update 3 on X5000 and how it was resolved.

Yesterday, together with my colleague, we took another attempt at solving the issue with his X5000/20 after failed Update 3 installation.

tl;dr
We have decided to reinstall AmigaOS from scratch, and eventually succeeded in installing Update 3 from the downloaded archive, but first we had to solve a problem with USB by doing "usb reset" in the U-Boot. For the detailed description, please continue reading.


1. Bootable USB preparation
Using my Sam460, we've created a bootable USB stick (this was the easy part, thanks to this tutorial with a great, screenshot illustrated guide attached).

2. USB problem
We've inserted newly created bootstick and launched X5000. Any hopes that we've had, faded away right after AmigaOS splash screen. Workbench greeted us with a grey screen with only a top bar with a Boing Ball visible, and some Grim Reaper errors popping up one over another. The errors were mentoning hid.usbfd and a keyboard. We've unplugged both mouse and keyboard right after launching a boot procedure, which left us with only single Grim Reaper error related to CANDI (I still don't understand why it was there despite booting from freshly created USB, but this makes me think that the original corrupted OS installation from internal SSD was still involved in the process).

Initially, I thought that I have made a mistake when preparing the bootable pendrive. We've carefully created another one, but still no luck.

We've also tried with replacing the ehci.usbhcd driver from Update 2 (despite it was X5000/20). Obviously, that didn't help as well.

We've ended up performing "usb reset" in the U-Boot. Only after that we've experienced a proper AmigaOS installation screen after booting from the pendrive.

3. AmigaOS fresh installation
At this point we were already short on time and decided not to spent another (possbily frustratingly fruitless) hours trying to repair existing installation.
Instead, we've just quick formatted the system partition and proceeded with fresh installation in the following order:
* AmigaOS 4.1 FE
* Update 2
* Enhancer Software 2.2
* Update 3

4. Final thoughts
I don't the know the precise details of the AmigaOS 4.1FE setup on which we originally failed to install Update 3, but certainly we had Update2 and ES 2.2 installed, and CANDI up and running during the Update 3 installation. Knowing that the CANDI doesn't play well with Update 3, on second attempt we haven't turned it on.

I want to emphasize, that prior to applying Update 3 for the first time (before all the things went off), we didn't have any problems with USB devices. Keyboard, mouse, pendrives... everything was working fine. This makes me think that the failed update messed with the USB on the U-Boot level, but I have no idea how that would even be possible.

This time we wanted to try installing Update 3 via AmiUpdate, but for some reason AmiUpdate didn't see the proper server and as such, we couldn't connect. Only after installing Update 3, AmiUpdate started working as expected, enabling future updates.

@AmigaSociety

Quote:

This is exactly the same behaviour we've experienced with my colleague when I was helping him out with Update 3 install on his X5000 (as described in this thread AmigaOS 4.1FE Update 3 - Bugs and Experience Report).


@cloverskull

Quote:

This is exactly the way we've proceed - downloaded the update package from Hyperion website, unpacked and run the install manually.

@Kyle

Quote:
Together with my colleague we've been unfortunate to share your experience when trying to apply Update3 on his AmigaOne X5000. The update seemed to be progressing well up to 100%. Then it stopped on 100% and several minutes passed, but nothing seemed to be happening. Eventually we've chosen to restart the machine, after which the grey screen welcomed us.

@smf

Quote:
It happens before AOS4.1 splash screen so it looks like a Kickstart problem, according to what you've mentioned. Do you possibly have any ideas on how we could narrow down the issue to find the problem?

Personally, I had more luck as on my Sam460LE the update (through AmiUpdate) went smooth. The only inconvenience was that after the first reboot I had AmigaDOS window opened instead of Workbench and I had to restart the OS again.