@All
So replaced in X5000 HDD on SSD, and install OS4 FE + update1 + update2 on top of it. Now my boot time instead of 48 seconds, takes 37 seconds. Kickstart loading is take about 0.5-1 second now. Whole OS4 loading from amigaboot (white screen), till usable workbench : 12 seconds instead of previous 23 seconds.

With disabled KVM from machine USB scanning goes much faster, and so, i have with pure mouse and keyboard attached directly to X5000: 31 seconds from power off till full working wb !

So it's usb scanning take more time (and for Uboot, and for OS4's usb stack). The more devices you attached, the longer booting you have. It's like +1 usb device mean +1-2 second more to whole boot process.

@msteed
Quote:

So if we cut off this 5 seconds menu timeout, then it 44 seconds for for full reboot.. My one 55. But that with additional KVM and passive usb hub. For you it just pure keyboard+mouse ?

@TearsOfMe
That bad .. But at least we tried :)

@nbache
Quote:

I checked it out, and yeah, it does have an additional USB 2.0 port, just like the TESMART one. It appears that "normal" KVM developers frequently (?) add this additional port, so that when things go wrong with their EDIT-programmed keyboard and mouse ports, you have an additional USB2 port with no logic on top as a workaround.

Basically, for myself, having KVM with just the standard USB ports for input will suffice, eliminating the need for an additional (passive, at least) USB hub, but at least we found a way to make things work!

But... so far I have had no success with Pegasos 2's firmware, whereas when OS4 loads and the USB stack sends something to the USB bus (right at the beginning of OS loading), everything has worked since.

This TESMART KVM do have "online" leds, which activate only when hardware sends or receives some unknown data via USB, which Pegasos2's firmware did not. So, if the hardware fails to send something (I didn't know what at the moment), then KVM's led indicator for online dind't light up, and KVM believes there is no alive USB.

When OS4 on Pegasos2 starts loading, I can see that when my USB mouse is "lighted" (the mouse also has some leds), then the "online" indicator begins to show that there is an working connection, and everything works since.

So far, I'm considering two extreme solutions to the "firmware in Pegasos 2 does not work in KVM" problem:

1). Buy a hardware USB analyzer (the budget models cost around 200–300 dollars). Then I can sniff all the traffic and compare what Pegasos 2 sends to what other Amiga firmware sends.

2). Tinker with the firmware, i.e., hack it, in the usual way: unpack, disassemble, find out where USB routines start, and then try to send what KVM wants to be sent.

I also think that maybe there can be some kind of adapter that can be connected to the USB port of the Pegasos 2 and pretend to be a "working USB" so KVM will be cheated ?

In any case, the first step is probably to figure out what Pegasos2 didn't send and what KVM wants, and then cheat it (either in hardware or by hacking firmware).

@Trixie
I seems don't have ide_cd_timeout setup, but i also didn't have issues at begining of loading (there speed comparable), the most speed loss i get when actualy load os4, so probabaly for me it will matter to swap on SSD, which i doing now

@Spectre
Will go the most obvious route for now : will install new os4update2 on SSD with new sata cable. And will see..

@Spectre
AFter reinstalling OS4 on HDD, or after just attach HDD back with old OS4 install ?

@geennaam
Can it be you who can wrote Ethernet onboard driver for x1000 ?:) Your driver for audio cards is 100% stable and good (i use it on 3 different amigaos4 machines for now). If you will consider ethernet driver i can help with betatesting of course

Anyway, ppls who wrote drivers offten didn't wrote any documentation, so other ones need to do the same again and again. And once they do what they want, they then have no big interest or motivation to wrote documentation, and so other devs recreating the wheel again.

@smf
So it seems that at least you, eliyahu, and mufa do use some latest betas of uboot..

@rjd324
Did you have public uboot on your side from 2016 coming on x5000 ? Or also a beta one ?

@smf
You also as eliyhau and rjd324 use SFS and not NGFS ?

@all
Those of you who have x1000 instead of x5000, can meassure the full loading from power on to working workbench as well as meassuer just a time between white screen (when amigaboot starting load modules) and the working system ?

@Spectre
Yeah, same as for me. But for mufa, eliyhau, smf and rjd324 it takes only 11 seconds.

Did you use SSD or HDD ?

In meantime tried to delete from prefs AppCache dir - it didn't speed thing up. Removing running AmiDock and XDock and i have 21 seconds from white screen to workbench still. In the uboot all i have for os4_Commandline for now is "serial", and nothing else.
And i see how offten "hdd" blinks in this time. Probabaly worth to test with SSD, it looks like it..

And intersting, that those ones who do have 11 seconds for os4 loading all on SSH, while we both on HDD and have 23 seconds. Dunno if it related or not.

Maybe it also make a difference what filesystem is used for booting (sfs vs ngfs ?) and all those settings in mediatool box..

@rjd324
So as i suspect the initialization speed is the same, it's the loading of amigaos4 much faster on your video : 11 seconds from "white" screen till usable WB, for me it takes 26 seconds. So ...

That can be and because differences HDD vs SSD, and, which a think as well can be "big" appdir cashe, and maybe debug-level add something .. Also i have lot's more on startup to run : 2 amidock panels , 1 xdock panel, dopus4, shell, few dockies, etc.

Will check futher, thanks!

@rjd324
Thanks, but have the same question to you as to smf and eliyhau in previous post, can you plz meassure those steps ? (so i will know where i loose 15 seconds).

I do have disabled animation of course as well.

@eliyhau, smf

So i loose somewhere 15 seconds. Can you measure exact steps and which take what ?

I mean

1). how much you have from power up , till x5000 logo disapper
2). how much you have after logo disappear, till the amigaboot start loading
3). how much you have from amigaboot starting loading till the working system

@smf
Can you share your "printenv" there as well ? If you have serial cable of course, as typing all manually is unreal :) And probabaly you use latst public uboot from 2015, and not the beta one from 2021-2022 ?

@mufa
32 seconds for x5k after you hit poweron till fully loadef wb with amidocks and co ? Sounds strange.. i mean logo+busscaning take ~25 seconds alone..

If you indeed have 32 seconds for everything, can you answer plz on those questions:

- is it 020 or 040 version ?
- Did you use ssd or hdd ?
- what version of ngfs ?
- Beta uboot or public one ?
- fresh update2 or a long time working system (with big appdir cache, etc) ?
- Can you post there your whole "printenv" from uboot ?
- can you meassure plz those times:
1). How much for x5000 boot logo ? I.e. how many seconds from power on till logo disappear ?
2). How many seconds between disappeared logo and amigaboot loading ?
3). How many seconds after amigaboot starts till full working wb ?

Because 32 seconds sounds too good. X5000 logo alone take 10 seconds.. and 10-15 seconds for usb bus-scanning.

Thanks!

@Nostromo
Sadly no USB boot :( There is a bug in the CFE or amigaboot: cfe can see usb, cfe can load amigaboot from usb, but then amigaboot didnt see usb-installcd as boot device. I was told that this is a cfe bug, but it looks like amigaboot didnt attach boot device tree properly.

As for cf card: i didnt tried yet, but as you can read on previous pages of topic TiredOfLife back in years use ide2cf adapter, and attach this adapter to ide bus of x1000 (yeah, x1000 still have one ide port and not only sata ones) and was able to boot installation cd from. But that need proper checking. I hope to check this myself soon

@daveyw
Quote:
I am a bit correct first port, it was not "until logo showups", but "while logo showups". Or better "until logo disappear from the screen". I.e. ~10 seconds of logo like doing nothing on both x1000 and x5000

@LiverForIt
Yeah, when i see this "[HELO][DRAM]" thing i firstly think about a battery, and about memory sticks not being fit correctly. But seems for one it fixed by repluging sata cables, for other one by swapping memory sticks.. strange

@sailor
Quote:

Can you post plz exactly information about your memory modules (full chip info, etc), and how much of them and in which ports, etc ,etc with which you have no such issue ?

As it start to looks like that issue is with the memory modules then...

@ddni
Quote:

Basically you one time setup CFE as you need and not bother about anymore for years. So yeah, that not big deal, but still a little annoy.

@sailor
Quote:

Dunno about PCIe line connections, but what real life use you have with where it gives you better results in compare with x5000 ? I mean something showing why it better to have PCIe line connections like on x1000.

As for X1000 better suits for two card connection, probabaly it not very offten to have 2 cards in, but, i have another shortcoming found for x1000:

While with x1000 you do have needs for additinal network card (so minus 1 slot), you also have adapter for rs232 then minus one hole too. With x5000 you have them free, if you need it. But then again, that not really issue, because probably no one fill the whole slots ever be it x1000 or x5000.

I of course didn't say that x1000 much worse than x5000, but if i need to do a choose like a new user, then it should be x5000 , that for sure. At least for now with current situation.

Quote:

Are you saying that you never-ever have this "[HELO][DRAM]" stop booting after reset of x1000 ? I just have this issue, and Raziel too, and it sounds like everyone have it ?

@imagodespira
But probabaly if Hyperion do not use sources for years, then we can continue updating it ? I mean, it's the same can then go to the Hyperion's server, but at least version in between can be released with no problems ?

@abalaban
Check pm plz :)