on linux? nah.
try using windows on a machine that old if you want to know the true meaning of slow. it will always be updating something meaningless like edge in the background on top of it.
Hint: :q!
Community rules (click to expand)
sudo
in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
on linux? nah.
try using windows on a machine that old if you want to know the true meaning of slow. it will always be updating something meaningless like edge in the background on top of it.
Me, who still daily drives an Intel Skylake laptop from 2015: π€‘
The boot time isn't actually that bad, it's like 6 seconds with Win10 and an SSD.
Your Skylake laptop from 2015 boots faster than my Zen 4 desktop from 2022 (with a PCIe Gen 4 NVME SSD!)
This thing takes 25 seconds just to POST. The fucked up thing is that it used to be even worse, but has slowly been improving with BIOS updates. The good news is that once it's up and running, this machine is ready to fuck. Programs open the second I click the icon and loading screens don't exist in games anymore. But it's still disappointing that AMD can't figure out how to make their shit boot faster.
Itβs an issue with ddr5 memory checks. You can disable the checks but you might get instability.
Edit I misread that, I thought you had a Zenbook not the AMD desktop lol π
That's actually insane because mine is also an Asus Zenbook. It's the UX501 that I got at a liquidation sale, and I refuse to give this thing up because they really don't make them like this anymore.
I'll probably eventually move onto a Framework once this thing gives up the ghost, but I'm hoping for at least a few more years of use.
I still have my old laptop from college for whenever my PC is dead and I need a backup device. It's from 2008 and still has an HDD. There's Windows 7 installed and last time i booted it up the boot up time said 316 seconds. It's ridiculous.
I love having it idle at 100% for 30 mins, fan at max, just to update some windows nonsense. Updating 500 packages on linux is done in 5 mins including the download. Like how do you even manage to make the update process THAT bad if not on purpose? I am baffled by that. It's a thinkpad dual core i7 with an SSD. It only runs Debian now thankfully.
Have you tried swapping in a 21$ SSD?
I've on more than one occasion saved an old laptop from being replaced simply by slapping a cheap SATA SSD into them. The owners are almost always convinced that they needed a new PC, when all they do with it is browse Facebook and watch TikTok all day.
Just turn it off right after it shuts down before the OS starts booting again. (Or just turn it off whenever, it's not like there's much chance of filesystem corruption these days. Although there is a chance of registry corruption if you're using windows and it's updating, which is honestly worse to fix)
Modern Windows (and Linux) is very hard to kill. You can unplug it all day without issue. Registry corruption and similar issues have not been an issue in decades.
I had to recover a W10 box from a family members work after windows had slowly given itself cancer of file corruption. I've dealt with this shit before and it's not a big deal... usually...
This fucker took 3 days of babysitting to bring back to life. In-place upgrades, it required multiple (why, no fucking idea), dism, sfc just chipping away bit by bit. And no, this is a work machine, so wipe and start fresh was reserved for actual "cannot be saved" situations. It has a backup plan, and I am the unofficial/unpaid IT guy for that location, but I don't have license keys or installers for the software used (inherited situation), and it would add lots of friction to get running again. Absolutely not jumping on that grenade unless I must, it's untested if a restore causes license validation errors (time checks and other bullshit).
After that fiasco I applied a universal scheded task of dism followed by sfc, on a monthly basis, and every six months a few automated checks but also I pop my head in for a minute (remotely) just to validate that those automated tasks are running successfully.
It's been about... 4 years now? And it's been working as-expected. But windows obliterating itself with no user input isn't what I'd call 'a thing of the past'.
(also it wasn't a hardware fault)
My 10 year old laptop (which has been running Linux for 9.5 years now) has an SSD, so it'll restart in a normal amount of time. Even old laptops no longer have HDDs only
~~51 years~~ 8 seconds
$ systemd-analyze
Startup finished in 2.277s (firmware) + 1.145s (loader) + 1.644s (kernel) + 3.211s (userspace) = 8.279s
graphical.target reached after 3.211s in userspace.
$ lscpu | awk -F ' +' '/^ *M.* n/ {print $1, $2}'
Model name: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
$ vmstat -s | awk -F '^ +' '/[0-9]* K t.* m/ {print $2}'
3901984 K total memory
I've never experienced major slowdowns when running Linux on old laptops. It helps that OS fragmentation appears to be a problem exclusive to Windows
Fragmentation is only an issue if you run a HDD.
Whaaat my laptop is 13yo, It is faster than new, just because I added ram and ssd 4 years ago
Same, I have a 2012 laptop, just added RAM recently, with ssd replaced few years back. Boots in seconds.
It is actually amazing how much difference ssd made to my 6 year old laptop
SSD
HDD too, with Linux. IME it's just Windows chugging storage devices for entire minutes after booting, for no reason.
(arch with gdm3 and gnome takes around 1:30-2 minutes to boot from an hdd on my old craptop)
I don't understand why many desktop environments don't have a confirmation when you click one of those. Only ones I know that do it are GNOME and KDE
The confirmation is annoying for many GNU+Linux users. It's like asking are you sure you want to power off even though you had to use three or four keys or mouse clicks just to get to the poweroff menu.
It's not the total number of clicks that matters. It's the fact that several options (sleep, reboot, shut down) are the same final click and often a pixel or two away from each other.
When running a somewhat descent Linux distro even on a potato rebooting usually takes like ~15s. With windows even on recent hardware probably 5+ min
not if Arch LInux is installed on it
Sometimes I wait to enter the bios so I can press the power off button while there.
Even worse if you clicked "Update and restart"