BCsven

Gravity Waves didn't exist according to my highschool science teacher

The wing experiment with hundreds of pressure sensors shows lower pressure on top and more on bottom.

I recently heard that they discovered hundreds of Pluto sizes "planets" beyond Pluto, so they had to decided do we add 100 more planets or just demote Pluto to planetoid and ignore the rest

Depends on your definition of successful

That Nissan SUV from factory is horrible, lights are up high and blinding.

Sometimes the underlying cause is you don't want to be bothered with the task. I am highly motivated to complete tasks, but sometimes I will let stuff slide because I can't be bothered.

Lazy exists. I am a fully capable person, but some times I just don't want to get up off the couch and wash the dishes, or finish painting the wall trim. Its not that I am sad, tired or depressed, it's just I'd rather be doing something else or nothing else.

I meant deb based as in those based on Debian OS...which feeds the other Debian based offshoots. I probably over simplified by original comment, I wasn't claiming deb package management was the issue, just the relation to Debian base OS being the issue. So whatever the base OS of fedora and SUSE is worked fine (those happen to be RPM packages) maybe Arch may have worked or failed also. The point of it all was , if one fails to install, try another distro, and I my case nothing based off of Debian could deal with the hardware issue

Its not the packages its that whatever Debian built and other derivatives of Debian, used as their base, did not work with that hardware. Trust me I distro hopped a ton to try and get a Debian to work. I didn't save the error, but however the NON Debian OS WORKED AND WOULD ACKNOWLEDGE THE ERROR ON SCREEN AND MOVE ON.

Sorry did not mean caps, caplock after OS lol.

Also an OS is not just the kernel, its your tools that boot the machine and recognize hardware, and what the OS it told to do with issues. So I assume Debian bug for specific hardware, and non deb distros didn't have the bug.

I deep dive issues as my job and nature, so trust me when I say a deb derived would not work I tried more than 10+ distros deb based. Only Fedora and SUSE ones worked (because non Debian build) not because of packaging

Yeah, it was some BIOS bug or hardware error that halted Debs, but RPM based would show that it worked around the issue and continued. As a Debian branch whatever was missing in main was probably missing throughout all the derivatives.

I tried every single* deb based distro on a Samsung laptop from 2010. Some installed but would freeze with error mid boot, some deb based refused to install and gave error upfront. I tried fedora and opensuse and they acknowledge the error and moved on.

Whatever hardware or bios bug or error handling problem tripped up the system , it was was prevrlant through all of the Debian Branch.

And No it wasn't secure boot. That was disabled.

Some hardware doesn't play well with deb based distros vs rpm based, it would be good to point out if your install is failing with errors that another distro may work