Pheonix's questions

As the title says, I am booting from a Live USB. Releases 16.04 and 17.04. Booting in Legacy mode, because I like to have a multiboot flash drive and I can't find a UEFI compatible multiboot system.

When I attempt to boot from the live USB, I get an error from Nouveau saying gr: failed to load fecs_inst. This occurs for both Ubuntu Unity and Gnome.

I can hear the welcome chime while the graphics error is shown, so the system likely makes it through boot-up aside from the graphics.

My pc is running an AMD CPU, GTX 970 graphics with 16GB RAM. I know Nouveau is the graphics driver. I assume my card isn't outdated already.

Could the issue be that I'm booting in legacy mode? If so, does anyone know where I could find a UEFI Multiboot system? Or do I just have to deal with one OS at a time?

For a while now, I've been trying to think of a way to install some distro of Ubuntu on an old tower I have.

The tower is running dual Xeons, with a Quadros graphics card, 4GB RAM and SCSI type hard drives. It originally came with Windows XP installed, and might be 32 bit.

I attempted loading a Live image of Ubuntu 14.04, but it failed. I'm under the impression that 14.04 is too new for the machine.

Anyone have suggestions?

Edit: The machine in question is an IBM IntelliStation Z Pro, Type 6221-47U. Components: CPU: x2 Xeon 3.06 GHz RAM: 2 GB DDR (1? 2?) GRAPHICS: unspecified

It does have a DVD drive (two actually) so booting from a disc shouldn't be an issue. If I remember correctly, that's what I tried before.

A couple specific questions I have:

Does Ubuntu have any trouble handling multi-CPU systems, or should I expect it to work as normal?

Does Ubuntu natively support SCSI drives?

This machine will hopefully be used for a CNC mill control station, so it just needs basic functionality.

I'm using a chromebook Pixel 2, with a 2560x1700 (3:2) display. My goal is to use a smaller 3:2 resolution.

For a while now, I've been using a few commands to reset the resolution on my Chroot of Unity 14.04 (commands below). This works fine as a temporary fix, but it's a little bothersome to reset the resolution to stock settings whenever I log in or out of the chroot.

Here are the commands I use:

cvt 1680 1120 60
xrandr --newmode "1680x1120_60.00" 157.00 1680 1792 1968 2256  1120 1123 1133 1162 -hsync +vsync
xrandr --addmode eDP1 1680x1120_60.00

I attempted converting the commands to a bash file, but when run, xrandr gave many errors.

If I could simply add a 3:2 resolution (perhaps close to 1680x1120) to xrandr permanently, that would be perfect.

EDIT: I followed this article on dnschneid's crouton wiki to get my current results, which just need to be made persistent. It boils down to the three commands I posted before.

I did a few quick google searches, and it looks like the most recent discussion about this was back in 2012.

How might I go about disabling mouse acceleration in Ubuntu 15.10? I tried installing gpointing-device-settings but there were many errors.

I'm looking for a persistent setting.

I have a 32GB USB 3.0 Flash drive marked "Read Only". It is formatted FAT32. I don't know when it was formatted as such, and I need to reformat it.

I've attempted using Windows' Diskpart to mark it writeable, and removing the partition with Gparted, shred, and dosfsck.

The drive is roughly 2 years old and I've used it for a lot of Live USB boot disc creation, so it may be dying, although I thought flash drives were pretty resilient.

My next course of action will be to set up DBAN and try to nuke it.

Does anyone have any suggestions? Every attempt I've made ended in an error akin to "Cannot write to this partition".

EDIT: If I remember correctly, I was transferring files to it when it suddenly locked up. So it may very well be done-for.

I was able to get Teamviewer 10 installed in a chroot of Trusty with Unity (using sudo gdebi teamviewer_linux.deb), however when I attempt to start it it fails with

The TeamViewer daemon is not running! Please start the daemon (needs root permissions) before running.

I attempted to start it by running sudo teamviewer --daemon start and then launching TeamViewer from the dash, but after about 1 second it closes and the daemon seems to have stopped.

Why would the daemon stop in the middle of running TeamViewer?

I recently upgraded my desktop from an NVIDIA 560ti graphics card to a 970 SC. Before upgrading the card, I updated to Vivid Vervet with no issues. After upgrading the card, my login screen is blown up (maybe 720p) as opposed to 1080p on the old card, and login attempts result in some text flashing by and a return to the login.

I also tried booting into the LiveUSB version of 14.10, but this failed too.

I'm certain the problem lies in the new graphics card. Several other threads suggest installing new or experimental drivers, but I can't even access the terminal. Is there any official support for the new card, or am I out of luck for now?