Thanks for the tip! I will have to check those out as well. I believe I did have the non free when I setup to ensure Wi-Fi support. I don't know if the miscellaneous non free was included with that build.
I used an unofficial build from here using the netinst.iso writtento a USB. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/ Here are my apt sources. Anything you think I should add? # deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST with firmware 20191116-09:56]/ buster contrib main non-free # deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST with firmware 20191116-09:56]/ buster contrib main non-free deb http://deb.debian.org/debian/ buster main non-free contrib deb-src http://deb.debian.org/debian/ buster main non-free contrib deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. deb [arch=amd64] https://download.docker.com/linux/debian buster stable # deb-src [arch=amd64] https://download.docker.com/linux/debian buster stable # deb-src [arch=amd64] https://download.docker.com/linux/debian buster stable On Sun, Sep 6, 2020, 9:50 AM Andrew Cater <[email protected]> wrote: > Also - check carefully what firmware it might require. You have, for > example, installed firmware-linux-nonfree, firmware-misc-nonfree to enable > non-free firmware possibly? > > On Sat, Sep 5, 2020 at 10:12 PM riveravaldez <[email protected]> > wrote: > >> On 9/5/20, [email protected] <[email protected]> wrote: >> > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote: >> >> Well, I don't think it's a hardware issue. The computer is less than a >> >> year old and it's been used sporadically over the last year. Any >> >> thoughts >> >> on how to rule hardware out as an issue? >> > >> > Oh, maybe one idea, did it come with Windows and is it still there (I >> mean, can you boot into Windows?) -- if so, do that, and try a similar app >> in Windows. >> > >> > In Linux, does the problem happen in only one application, or in other >> > applications as well? >> >> Basic thought: grab any-distro LiveUSB and boot from there and check >> if the issue persist. >> >> If any other OS makes the hardware works fine then at least that cause >> could be ruled out. >> >> Hope this help, best regards. >> >>
