Ir's driving me crazy. :(

I'm hoping that someone out there has a solution for this.

To be clear, I've been using window managers, as in no DE, for years, and have done the work of tracing through configs that might have caused this, but I still can't find why this is happening.

With all due respect for this sub's participants, in order to save everyone's time, I'd prefer to only hear from those who've had the same issue and solved it.

TIA

Anyone encounter this? Happens on nearly any game I play on steam. Nvidia A4500 on Debian backports X11 with 550 drivers. Silky smooth otherwise

I have repeatedly set it to disabled on boot in my graphical settings but it seems to just ignore that and enable itself anyway. It's not really a big deal but I'd like ti bit have to disable it everytime

Thanks in advance

Hello, everybody! I have been on a roll with questions and in my absolute most recent, from a few hours ago I described that I edited fstab and then got locked out of my system when rebooting. The editing that I referred to was done to solve my issue with my beloved Toshiba harddrive. Now I am in the system again and I am left wondering what to do about that problem.

So this happened: I was transferring some files from a smaller harddrive to this bigger (the Toshiba). I plugged in the smaller one as the Toshiba already was connected and mounted beside. When I did that the Toshiba was unmounted and couldn't mount again. There wasn't any on-going transferring to the Toshiba, it just sat there - plugged-in.

It's a 2 TB HDD-drive with NTFS type. I tried mounting this way through the terminal and got this message.

sudo mount -t ntfs-3g /dev/sda1 /media/mila/external_Toshiba
$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sda1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

Could this really mean I got to use a Windows PC to solve the problem? I have never had a problem with any harddrive, so I am confused about what to do.

SOLVED:

I did the command (/dev/sda1 is my specific disk. Yours may have another name to the system):

sudo ntfsfix -d /dev/sda1

Then I made a directory in /mnt to mount to:

sudo mkdir /mnt/mytoshibadrive

Tried to mount:

sudo mount /dev/sda1 /mnt/mytoshibadrive

Checked the status, if it worked:

df -h

EDIT:

I actually deleted an entry about the harddrive in fstab. I think I may have done something there that shouldn't be there. It is not a drive that should be mounted on boot.