Commit 9a6b5125 authored by Murukesh Mohanan's avatar Murukesh Mohanan

new notes on alienware

parent 1102298f
......@@ -43,7 +43,7 @@ pagestyle: posts
{% endif %}
</section>
<div id="fb-root"></div>
<!-- <div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
......@@ -58,6 +58,8 @@ pagestyle: posts
data-numposts="10"
data-colorscheme="dark">
</div>
<noscript>Please enable JavaScript to view the comments powered by Facebook.</noscript>
-->
<!--
<div id="disqus_thread"></div>
<script type="text/javascript">
......@@ -74,5 +76,4 @@ pagestyle: posts
})();
</script>
-->
<noscript>Please enable JavaScript to view the comments powered by Facebook.</noscript>
</section>
......@@ -5,7 +5,7 @@ tags: [tech, linux]
---
It's been [4½ years since I bought my System76 laptop][sys76], and it is showing its
age. Back in 2013, an NVidia GT670 MX was a pretty decent laptop graphics card
age. Back in 2013, an NVIDIA GT670 MX was a pretty decent laptop graphics card
(which meant it couldn't hold a candle to the desktop graphics cards). But I was
able to play *Hitman: Absolution*, the various *Mass Effect* games, *Tomb
Raider* and so on on it, and with OK graphics levels and resolutions. Fast
......@@ -79,7 +79,7 @@ and processed it a bit to get this:
But that's probably the best bit about the Alienware UEFI setup. The UEFI menu
itself is … disappointing. It didn't support widescreen monitors, and I have
seen a few UEFI systems that do, so there's that. Many UEFI systems also support
screenshots, but this doesn't.
screenshots, but this one doesn't.
I needed to disable Secure Boot to get Arch to boot, as expected. Disabling
Secure Boot enabled legacy boot as well, and the legacy boot splash is somewhat
......@@ -197,7 +197,7 @@ command is long-winded enough that I saved it to file in root's home directory,
which turned out to be pretty handy later.
Next step was to edit `/etc/mkinitcpio.d/linux` to get it to create the
initramfs files in the locationss listed above directly (using [the mkinitcpio(2)
initramfs files in the locations listed above directly (using [the mkinitcpio(2)
method from the Arch Wiki][hook]).
Timezone set, `fstab` created, hostname set … and reboot!
......@@ -216,7 +216,7 @@ efibootmgr --disk /dev/nvme0n1 --part 1 --create --gpt --label "Arch Linux" --lo
Reboot again, and I'm dropped into a TTY. :disappointed: I had installed `gnome`
after all. Of course, I forgot that Arch doesn't automatically enable services,
so logging in, and `systemctl enable gdm; systemctl start gdm` later,
so logging in, and `systemctl enabla --now gdm` later,
I had … GDM crashing in a loop. I had both my TV and my monitor connected, so I
tried disconnecting my TV, which stabilized GNOME and allowed me to login.
Turns out GDM itself runs in Wayland, and while Wayland didn't have problems on
......@@ -285,11 +285,10 @@ My gaming will no longer be as frustrating as it was before. :sunglasses:
Who knew an Alienware would be so comfortable for Linux? Besides goof-ups I made
because I hadn't installed Arch in ages and didn't pay attention to the Wiki, it
was a pretty easy install. It would hvae been easier still if I'd gone for
was a pretty easy install. It would have been easier still if I'd gone for
Ubuntu, I suspect. A far cry from some of the laptops I have installed Linux on
for friends, maybe the year of the Linux desktop is indeed at hand.
<!-- section -->
[^1]: Not because of battery issues, but because I burnt(!) the LVDS cable
......
This diff is collapsed.
......@@ -23,9 +23,9 @@
}
#main ul li {
padding: 0.5em 0;
padding: 0.2em 0;
margin-left: 0.5em;
list-style-image: url("../images/not_sign.png");
list-style-image: url('/images/out.png');
}
#main li.no-marker {
......
images/out.png

174 Bytes

......@@ -4,33 +4,34 @@ pagestyle: cann-table
permalink: /resources/
description: General stuff
---
# Vim: `vimrc` and plugins [![gitlab]](https://git.cse.iitb.ac.in/murukesh/vimrc){:.git} [![github]](https://github.com/murukeshm/vimrc){:.git} {#vim}
Currently contains a nifty `vimrc`, and some plugins:
- [vim-plug](https://github.com/junegunn/vim-plug)
- [ctrlp.vim](https://github.com/ctrlpvim/ctrlp.vim.git)
- [diffchar.vim](https://github.com/vim-scripts/diffchar.vim)
- [molokai](https://github.com/tomasr/molokai.git)
- [nerdtree](https://github.com/scrooloose/nerdtree.git)
- [supertab](https://github.com/ervandew/supertab)
- [syntastic](https://github.com/scrooloose/syntastic)
- [tabular](https://github.com/godlygeek/tabular.git)
- [tagbar](https://github.com/majutsushi/tagbar.git)
- [vim2hs](https://github.com/dag/vim2hs)
- [vim-airline](https://github.com/bling/vim-airline)
- [vim-fugitive](https://github.com/tpope/vim-fugitive.git)
- [vim-go](https://github.com/fatih/vim-go.git)
- [vim-markdown](https://github.com/gabrielelana/vim-markdown)
- [vim-surround](https://github.com/tpope/vim-surround.git)
- [vimtex](https://github.com/lervag/vimtex)
- [YouCompleteMe](https://github.com/Valloric/YouCompleteMe.git)
{: #plugins-list}
In addition, I'm writing my own plugin for using [Vim as a
`MANPAGER`](/2015/08/28/vim-for-man.html):
- [vim-manpager](https://github.com/murukesh/vim-manpager)
# Home: dotfiles, including `.vim` and plugins [![gitlab]](https://git.cse.iitb.ac.in/murukesh/home){:.git} [![github]](https://github.com/muru/home){:.git} {#vim}
Currently contains a nifty `.zshrc`, `vimrc`, and some plugins:
- zsh
- [fast-syntax-highlighting](https://github.com/dharma/fast-syntax-highlighting)
- vim
- [vim-plug](https://github.com/junegunn/vim-plug)
- [ctrlp.vim](https://github.com/ctrlpvim/ctrlp.vim.git)
- [diffchar.vim](https://github.com/vim-scripts/diffchar.vim)
- [molokai](https://github.com/tomasr/molokai.git)
- [nerdtree](https://github.com/scrooloose/nerdtree.git)
- [supertab](https://github.com/ervandew/supertab)
- [syntastic](https://github.com/scrooloose/syntastic)
- [tabular](https://github.com/godlygeek/tabular.git)
- [tagbar](https://github.com/majutsushi/tagbar.git)
- [vim2hs](https://github.com/dag/vim2hs)
- [vim-airline](https://github.com/bling/vim-airline)
- [vim-fugitive](https://github.com/tpope/vim-fugitive.git)
- [vim-go](https://github.com/fatih/vim-go.git)
- [vim-markdown](https://github.com/gabrielelana/vim-markdown)
- [vim-surround](https://github.com/tpope/vim-surround.git)
- [vimtex](https://github.com/lervag/vimtex)
- [YouCompleteMe](https://github.com/Valloric/YouCompleteMe.git)
{: #plugins-list}
In addition, I wrote my own plugin for using [Vim as a
`MANPAGER`](/2015/08/28/vim-for-man.html): [vim-manpager](https://github.com/muru/vim-manpager).
Old plugins:
......@@ -42,7 +43,13 @@ Old plugins:
- [ctrlp.vim](https://github.com/kien/ctrlp.vim): superseded by `ctrlp/ctrlp.vim`
- [LaTeX-Box](https://github.com/LaTeX-Box-Team/LaTeX-Box.git): superseded by `vimtex`
Once cloned to `~/.vim`, do:
Setting up usually goes:
1. Clone to a folder, say `~/home` (recursively, so that the zsh plugin is pulled in)
2. Copy files from there: `cp ~/home/. ~/ -ar`
Once done:
vim -c PlugUpdate
......@@ -50,20 +57,20 @@ And optionally:
vim -c PlugUpgrade
**Bonus**: My dotfiles repo [![gitlab]](https://git.cse.iitb.ac.in/murukesh/home){:.git}
The `.vim` used to be in a separate repo, then I merged it into home.
<!-- section -->
# Some scripts {#scripts}
- [`curlwc.sh`](https://github.com/murukeshm/scripts/blob/master/curlwc.sh):
- [`curlwc.sh`](https://github.com/muru/scripts/blob/master/curlwc.sh):
This script uses [curl(1)](http://manpages.ubuntu.com/curl.1) to download the
target file in parts. Not very robust.
- [`mtcd.sh`](https://github.com/murukeshm/scripts/blob/master/mtcd.sh):
- [`mtcd.sh`](https://github.com/muru/scripts/blob/master/mtcd.sh):
This script mounts all arguments in directories within `~/cdrom` (as ISO9660
images), and also handles unmounting.
These and more can be found on my scripts repo. [![github]](https://github.com/murukeshm/scripts){:.git}
These and more can be found on my scripts repo. [![github]](https://github.com/muru/scripts){:.git}
<!-- section -->
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment