The Linux Questions Thread: a bunch of pitfalls, but technically it's possible

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Linux Questions Thread: a bunch of pitfalls, but technically it's possible

«‹›2 »

Xik: Mar 10, 2011; Dinosaur Gum

Tighclops posted:

I hope I'm in the right place for this, but I'm having problems getting the 304.64 Nvidia drivers to remember which of my two monitors I want to be the primary display. I'm running Mint 13 MATE with a GeForce G210 so far with few problems I haven't been able to stumble and google my way through, but I can't seem to lick this. Here is my x config file: http://pastebin.com/XMxL3y7X

I can't really make heads or tails of it but I suspect it's something in here I need to change.

This might be a bit too hackish for you, but my solution was to run a couple of xrandr commands when my window manager starts up.

My NVIDIA card has two DVI and one HDMI outputs, I leave them plugged in and I am constantly switching between the second DVI and the HDMI output. One of the startup entries in my window manager(i3wm) is a two line script to ensure the second DVI output is active and not the HDMI output:

code:

xrandr --output HDMI-0 --off
xrandr --output DVI-I-3 --auto --right-of DVI-I-2

As I said, I'm always switching between them so I have two functions in my .bashrc file:

code:

# turn off output on hdmi screen and turn on dvi                                                        
function xdv(){
    xrandr --output HDMI-0 --off
    xrandr --output DVI-I-3 --auto --right-of DVI-I-2
}

# turn off dvi output and turn on hdmi                                                                  
function xhd(){
    xrandr --output DVI-I-3 --off
    xrandr --output HDMI-0 --auto --right-of DVI-I-2
}

# ¿ Feb 2, 2013 18:15

Adbot: ADBOT LOVES YOU

# ¿ Apr 26, 2024 16:57

Xik: Mar 10, 2011; Dinosaur Gum

Tighclops posted:

I probably should have mentioned that I have a DVI and a VGA monitor (and that I'd like the DVI one to be the x screen) so it looks like something like this might be a solution, but I have no idea how to set something like that up.

xrandr may look daunting and complicated but it really isn't. The i3 user guide has a small section on xrandr which pretty clearly explains it's basic functionality, you should be able to figure it out for your particular use from there.

# ¿ Feb 3, 2013 04:20

Xik: Mar 10, 2011; Dinosaur Gum

code:

du * -hs | sort -h

Will get you a nice sorted summary in human readable form from the current directory.

# ¿ Feb 4, 2013 18:17

Xik: Mar 10, 2011; Dinosaur Gum

No no serious posted:

Dynamic tiling windows managers: I've been flitting back and forth between dwm, awesome, and XMonad. Dwm looks ugly to me and seems to lack really good taskbar customization, awesome is unstable and screen flickery, and xmonad - I am too old to learn a language like haskell.

Are there any others worth looking at that allow heavy customization, will make me feel like a l33t ha><0r, and don't require a masters in comp sci to configure?

E: or alternatively, any thoughts on turning openbox into a part time tiling wm using pytyle? Has anyone here done this, and is it any good?

I use i3wm and love it, but it's not "dynamic". When I was looking for a window manager, my only real requirements were that it had plain text config files and had good documentation. It turns out that if you don't want to configure your window manager in a programming language and don't want to have to tediously search through mailing lists or reask basic config questions in IRC, there isn't much of a selection.

The i3 user guide is awesome, if you leave it open for the first couple of days while you adapt and learn about it, you should have no problems.

# ¿ Mar 1, 2013 14:20

Xik: Mar 10, 2011; Dinosaur Gum

Megaman posted:

I use Debian, and I want to install testing or SID, what is the best way to do this? I've downloaded the mini.iso and installed SID, but the installer fails on installing GRUB into the MBR from a USB onto my SSD (I think because it thinks the SSD is /dev/sda when in fact it's /dev/sdb). Does anyone know why this is broken, or does anyone else have experience with this?

If you used GPT when you were creating your partitions, installation of GRUB will fail unless you created it's own boot partition. The GRUB Arch wiki page should help explain. If that isn't the issue, unplugging any unnecessary drives before you install is always a good idea, just make sure you use UUIDs in fstab.

Is this the correct thread for asking about an NFS issue I'm having? I'm running a debian file server and I just recently reinstalled Arch after an SSD failure and for the life of me I can't remember how I got my NFS shares to mount at startup.

Nothing has changed server side since it was working with my previous arch install, but obviously packages are updated crazy fast on Arch. It's probably a completely different system (kernel and relevant nfs packages) then before I had the drive failure.

I can see the shares:

code:

showmount -e fs
Export list for fs:
/mnt/backup 192.168.1.1/24
/mnt/data   192.168.1.1/24

I can manually mount the shares on my local system at any time.

Relevant fstab entries:

code:

fs:/mnt/data					/mnt/data	nfs             auto,intr,_netdev	        0 0
fs:/mnt/backup					/mnt/backup	nfs             auto,intr,_netdev       	0 0

And I can even

code:

sudo mount -a

after logging in and they both mount correctly as set out in fstab, but it just won't happen during boot. Am I missing something obvious?

code:

dmesg | grep -i rpc
[    1.982282] RPC: Registered named UNIX socket transport module.
[    1.982284] RPC: Registered udp transport module.
[    1.982285] RPC: Registered tcp transport module.
[    1.982286] RPC: Registered tcp NFSv4.1 backchannel transport module.

# ¿ Jan 20, 2014 07:27

Xik: Mar 10, 2011; Dinosaur Gum

code:

code:

code:

code:

code:

code:

code:

code:

code:

code:

code:

quote:

code:

code:

code:

quote:

code:

code:

code:

code:

code:

code:

code: