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
I’m not saying that whatever happened to you didn’t happen. I’m saying that your assertion of “deb based distros not working with specific types of hardware” is 100% NOT a thing. Package managers DO NOT interact with hardware.
If you had issues, it was not because of deb packages or apt and your particular hardware, it was because of incompatibilities with the software versions being installed. Has absolutely nothing to do with deb packages.
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
I’m not saying that whatever happened to you didn’t happen. I’m saying that your assertion of “deb based distros not working with specific types of hardware” is 100% NOT a thing. Package managers DO NOT interact with hardware.
If you had issues, it was not because of deb packages or apt and your particular hardware, it was because of incompatibilities with the software versions being installed. Has absolutely nothing to do with deb packages.
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