HeresMyAccount: adamhm, so I can just install whatever drivers I want and it will only use them
if it needs them? Well that's convenient!
sanscript, but the thing is, if I can use this sort of pseudo-compatibility mode, or whatever it's doing when I type those words to use some default generic drivers instead of trying to use the Nvidia ones (I assume that's what it's doing), then shouldn't that work on all cards? I mean, mine seems to be one of the least compatible ones there is, so if I could get it to work on mine then it should work on all or
nearly all. And if whatever driver it's using now doesn't work on some card then probably
nothing will. Do you get what I'm saying, or is there a flaw in my logic?
Otherwise I guess I could just install tons of different drivers and it will automatically pick the most applicable one, right? But I rather not resort to doing it that way.
You can make the boot options permanent, but there's really no need to & I wouldn't recommend it as the "compatibility mode" is noticeably slower and more limited even just at the desktop - just keep the proprietary Nvidia drivers installed for Nvidia systems (updating them when necessary) and let it use the default open source drivers for Intel and AMD GPUs.
There's no need to install tons of drivers separately; most drivers are already provided with the kernel so you don't need to bother with installing them separately - just keep the system updated and you're set.
HeresMyAccount: Great... so basically, I shouldn't use any of those tools, right?
*sigh* ... something that really annoys me about some parts of the Linux community is when you get people who consider their choice of distro to be "the one true distro", their way of doing things the only "right" way, and spread FUD about others like Darvond did there. It's *really* counterproductive and serves only to confuse and drive away newcomers. The truth is every distro has its advantages and its flaws and everyone has their own requirements and preferences.
About the specific utilities you mentioned:
* Synaptic Package Manager: GUI tool for the package management system. In my experience it works fine, although you should rarely ever need to touch it.
* Software Manager: This is used for installing software from the system repositories, it's like an "app store" of sorts.
* Update Manager: Exactly what it says it is; if there are updates available for your system they are installed from here (an icon for this is shown in the system tray).
* Software Sources: Used for adding/removing/managing the repositories that provide software packages.
None of them are anywhere near as bad as Darvond claims (they're pretty user-friendly actually; Synaptic could use some improvements but it's mostly fine), and they are all detailed in my guide.
For archives like .zip/.rar/etc use the Archive Manager - this should be used to open them automatically if you double click them. You can also right-click on files and select "Open With" in the popup menu.
HeresMyAccount: I'm doing that very thing with Linux Mint. It can run in live mode (like a test mode for the installer without installing, so you can't save to it but you can save documents on other drives, but you can't change default configurations, I don't think), or you can actually install it directly onto another USB drive and then run it like the normal, full OS!
Anyway, I've hit a couple more snags:
First of all, I tried to run a Java program, and it said that it's not executable, and I'd have to change the permissions. I tried it two ways:
- First I opened the properties and checked the box to allow it to execute, and when I did that, it checked on for about half a second and then automatically unchecked again, and did that each time I tried!
- Then I used chmod to set the permissions to +rx, and it expected the sudo password, but then it didn't say anything (no error, so I thought it worked), but it still wasn't executable!
Are you saving them to a drive using a FAT or NTFS partition? If so, then that would be why - those filesystems are designed for Windows and don't have any way to store the permissions flags for Linux. The only way around this is to either use a drive formatted with a more Linux-friendly filesystem or you can work around this by running them from the terminal using a command like "java <file>".
HeresMyAccount: The other thing is that I've found the information from lsusb for my WiFi adapter, but I'm not sure how useful it actually is. First, here's what I got from inxi:
Network:
Device-2: TP-Link 802.11ac NIC type: USB driver: usb-network
And here's what I got from lsusb, but I don't see any specific model number other than 802.11ac, which I think is more of a generic internet protocol or something like that, if I'm not mistaken:
Bus 002 Device 002: ID 2357:012d TP-Link 802.11ac NIC
802.11ac is the supported protocol specification(s) -
https://en.wikipedia.org/wiki/IEEE_802.11 2357:012d is the vendor & device ID. Looking that up, it appears to be a TP-Link Archer T3U and uses a Realtek chip... which is bad news because Realtek's Linux support is quite bad in my experience - I usually had to compile drivers for those from third party sources rather than simply update the kernel or use the driver manager to install them as for other vendors.
Also the product page for this particular adapter only mentions Windows and Mac as supported operating systems:
https://www.tp-link.com/uk/home-networking/adapter/archer-t3u/