4 ms·
I remember when even a cold start would drop me into a working desktop within a few seconds. Thus was in the early 90's with RISC OS running on the early days o
by kiwijamo 6y ago
I remember when even a cold start would drop me into a working desktop within a few seconds. Thus was in the early 90's with RISC OS running on the early days of ARM chips. Respectfully I would argue hibernation and suspend are just a band-aid for the sorry state of hardware and software today. What if we didn't need hibernation or suspend?
- wazoox 6y agoMy Pop_OS laptop cold boots from button press to login in 8s.
- arendtio 6y agoHow much time of these 8s is spend in EFI? When I look at my PC it is so painful to see, that it actually spends more time with EFI than with the OS: $ systemd-analyze Startup finished in 7.859s (firmware) + 1.203s (loader) + 1.683s (kernel) + 1.356s (initrd) + 1.431s (userspace) = 13.534s
- executesorder66 6y agoCoreboot is the solution here, but it's just a shame so many hardware manufactures are so protective over their shitty firmware. Why can't they just open-source whatever they crapped out, and have professional developers maintain it for them for free?
- pwdisswordfish8 6y agoPlanned obsolescence.
- kiwijamo 6y agoMine machine only shows kernel + userspace. Even that alone adds up to 15.648 seconds.
- wazoox 6y agoStartup finished in 2.680s (firmware) + 826ms (loader) + 2.977s (kernel) + 12.269s (userspace) = 18.753s I had to enter my password 3 times to login, that's most of time spent here :) (8 to 10 seconds to the login banner). I think you have an Intel machine. For some reason, Intel machines spend large amounts of time initializing their firmware. Xeon servers spend minutes at it, while Epyc ones spends only ten seconds or so. But even Intel laptops seems slower than Ryzen ones for some reason. Edit : I had an update and rebooted (password entered once this time :) Startup finished in 2.557s (firmware) + 799ms (loader) + 2.901s (kernel) + 5.103s (userspace) = 11.362s graphical.target reached after 5.093s in userspace Login banner appeared a little less than 8s after boot.
- BlueTemplar 6y agoThe point is to keep all your programs open and in the same state, which might take much longer to get back to than the boot itself.
- Too 6y agoIsn't this also treating the symptom rather than providing a cure? Keeping important state only in volatile memory and hoping user clicks Ctrl+S often enough? Just resume wherever the user left off regardless if its a cold boot or not. Androids Activity-model provides a more modern solution to this (putting its lack of multitasking aside). Did you ever think of what happens when you swap app and did you ever care about shutting off old apps? There is no need, it automatically hibernates individual apps that were not used recently but you don't notice, next time you open it magically continues exactly where you left off. Assuming developer of the app cared about state-management.