I suppose you're over it now but I noticed your DVD drive came up as unit 0. I wonder if this might mess up the boot process? If it's setup to boot a HDD of unit 0? Usually that was the case.
The system does sound a bit flaky if it just crashes like that. Something is wrong there. I have noticed that sometimes if a system component is an incompatible or older version then something will crash. That doesn't look like well programmed software which would use a specific version and fail otherwise. That's what Amiga standard software is expected to do and I expected system software to set an example and hold to that standard tightly.
Just got in from a day out. So, yes, I’ve always felt that the system seems a bit flakey. It does seem like it’s easily crashed but unless there is a list of what all the correct latest or most compatible kickstart devices and libs for each system are then It’s not desperately easy to know what might be out of place. Especially when my system, like most now wasn’t built from scratch, but from a recovery stick.
It's possible that may affect it. Though if standard updates have been applied on top it should be fine. Would be good if there was an integrity check of all components above that of doing a simple AmiUpdate.
Is there any mileage in me giving a list of versions of all the kickstart files and system libs in my system? Would anyone actually know if one was out of place? Such a list doesn’t need to be posted here, could be anywhere.
I think you missed my point there a bit. I realise that AmiUpdate can tell me if any of the programs and libs that it knows about are up to date or whatever, and yeah, I run it quite often. But it didn't for example know that if I wanted to run an internal SATA CD drive on a 5040 board that actually, the 5020 data driver is what you want because the updated 5040 one doesn't appear to work properly*. And it can't know that "hey, you've got XYZ lib and ABC libs and they're known to cause issues together" etc.
*NB: No idea how stable or performant running the 5020 sata drive on a 5040 is, all I know is that it resolved the issues with the CD drive. I've switched back for now since I never intended to install the internal drive permanently anyway as my case doesn't have a 5.25" bay.
For what it's worth, I ran AmiUpdate just now. It found an update for GeekBench2D, installed it, I rescanned afterwards and AmiUpdate crashed with a DSI error. So that's nice and stable too
But when you mention the 5020 vs. 5040 sata driver, I suspect you are not really fully updated anyway, because the two drivers have (for several years) been unified into p50x0sata.device.kmod.
Are you sure you have configured AmiUpdate correctly? And did you install Update 2 and all further updates since.that?
When I referred to the 5040 driver, I actually mean the unified one, the one called "p50x0sata.device" I called it the 5040 one (wrongly) because the 5020 one is explicitly called p5020sata.device and well, there are only 2 boards that we use, 5020 and 5040. So, yeah, my bad there.
So, what I actually mean, is that the unified one, in my testing at the weekend over the coarse of this thread was terribly buggy with the internal CD drive and the (presumably older) 5020 specific one worked much better for me even though I have the 5040 board. Is it meant to be used on the 5040 board? I don't know. Presumably not, or things wouldn't have progressed to the unified driver. All I know is that the 5020 specific driver worked better in my 5040 than the 50x0 driver.
I probably wrote far more there than I needed!
So as for the other questions, AmiUpdate says it's v2.54 (18.2.2024). Is it configured correctly? Don't know. Both 'www.amiupdate.net' and 'update.amigaos.net' are defined and enabled. I don't see much else of relevance in the prefs. aminupdate.net is the default, bold, server.
For update 2 - no I didn't install that because my system came preconfigured with a USB "rescue" disk instead of actual install media and was installed (ny me) by restoring this to a new hard drive. The text in the top menu bar says Update 2 is installed, but that will have been by the supplier, not me, so I assume it is, but since I didn't do it, I can't be sure.
I mean, it doesn't really sound like much is up with the system in terms of drivers and libs. I think it's just pretty normal to get DSI errors and stuff. That's how it's been so far anyway.
When I referred to the 5040 driver, I actually mean the unified one, the one called "p50x0sata.device" I called it the 5040 one (wrongly) because the 5020 one is explicitly called p5020sata.device and well, there are only 2 boards that we use, 5020 and 5040. So, yeah, my bad there.
Ah, I see. In fact, now that I think back properly, I believe there was never released any driver named 5040 into public. The 50x0 name was born while the driver's support for the 040 was still in beta.
Quote:
All I know is that the 5020 specific driver worked better in my 5040 than the 50x0 driver.
Okay. In effect, what you are seeing is that an older version of the driver works better for you than a newer one - it's the same driver, it just got some support for the 040 built in.
Quote:
AmiUpdate says it's v2.54 (18.2.2024).
Sounds fine.
Quote:
Both 'www.amiupdate.net' and 'update.amigaos.net' are defined and enabled.
Also fine.
Quote:
I don't see much else of relevance in the prefs. aminupdate.net is the default, bold, server.
Okay.
Quote:
For update 2 - no I didn't install that because my system came preconfigured with a USB "rescue" disk instead of actual install media and was installed (ny me) by restoring this to a new hard drive. The text in the top menu bar says Update 2 is installed, but that will have been by the supplier, not me, so I assume it is, but since I didn't do it, I can't be sure.
Right. So it looks like the supplier has installed whatever was the latest at the time, fine. But have you registered your copy of OS4.1 FE at the Hyperion website, and have you entered your login credentials for that site into AmiUpdate when prompted? Otherwise you won't be able to make AmiUpdate download and install updates released after your installation was made.
Yes to both of those last two as well. So I think in terms of whether libs and drivers are the latest, I should be good.
So is any work still being done on drivers and the like? Does someone need to know that there were problems with SATA Optical drives and the 50x0 driver?
Sure, but it would help to have hidden tags, so it doesn't bloat up. This is from my volume without much extra clutter. It's recent but I didn't do an update check on it before building the list. It's from my X1000 so would differ to your X5000 but can provide a guide.
Hi, I just ordered an X5040 (to arrive in late August).
I'd like to know how wide the tower is so I can make room for it in my studio.
Where did you buy it? Different dealers may use different cases. The Fractal Design tower most are using is 19.5 (width) x 43.1 (height) x 45 cm (depth).
Also don't forget to leave room on both sides, especially the left one seen from the front - at least if it's the Fractal case, but probably most others - as it has fan openings on the side.
It has ventilation openings on the left, top, bottom and rear sides. Putting it with the right side next to something else should be no problem, but left, rear and top sides need space.
Only difference should be that for the X5000 usually a "Boing Ball" front plate is used, and mine has a "X5000" instead of the "Fractal" label at the front bottom.
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
Donate
