Yesterday I upgraded Gnome on my ArchLinux Laptop to the version 2.28. There are quite some changes in this new version of Gnome. The first I recognized, was the different Background-Picture of the Login Screen. To change this Background just type in the following into the Terminal:
gksudo -u gdm dbus-launch gnome-appearance-properties
This calls the gnome-appearance application using the gdm session. Select a nice Background, and you are done. It is normal, that two accessability icons appear in your panel. To fix this, just log-off and they should be vanished. If you still have one, please go to the Keyboard Settings and turn off the accessabiliity feature.
One more problem, I do have right now, is the Keyboard Layout of the GDM Login Screen. This is by default set to the US design (qwerty) and not like expected to DE (qwertz). The normal Keyboard Layout for Gnome is already set to DE, but still the GDM Login Screen is set to US.
I found the this Forum entry, and will dig deeper. Hopefully I find an easy solution, then I will report back.
To make my system more secure (well, it is a client only and is probably insecure anyway, but…) I wanted to disable the root login via ssh on my machine. To do this, just change the line
For Arch, I needed an xorg.conf, which basically runs on my W500. The W500 has some specialties, in that it has two discinct graphic cards, one Intel and one AMD. I have found an XOrg on Stargazers Blog. Please find the Xorg.conf directly here. Thanks Stargazer.
To make a nice boot-process, I have had to install fbsplash. The install is pretty seemless and easy. To make the whole process really nice, my menu.lst is configured as follows:
title Arch Linux (boot logo)
kernel /vmlinuz26 root=/dev/disk/by-uuid/577947c2-06ad-4bce-825f-a882228f724d ro quiet console=tty1 vga=795 splash=silent,theme:arch-black,fadein,fadeout
Note, that I did not write a logo.nologo into the kernel-line, like suggested in the Arch Wiki.
For this, I installed beforehand the themes from the package
fbsplash-theme-arch-black. To make the whole process more streamlined, I also edited the /etc/conf.d/fbsplash file:
I wanted to make my laptop truely archified. Therefor I installed first of all the murrine engine for GTK and, to have some themes available the corresponding theme collection:
pacman -S gtk-engine-murrine
pacman -S murrine-themes-collection
After this, I downloaded the splashscreen from gnome-look.org (I later recognized, that this is not really needed anymore, since the splash ist just shown a very very short time). On the same page the GDM Greeter is already referred, and I downloaded it as well.
To install the splashscreen, I furthermore downloaded the package
gnome-splashscreen-manager from the AUR via yogurt. I just downloaded it, and recognized that some errors seem to be in the PKGBUILD-file, therefor I then removed the last „}“ from PKGBUILD and then did a makepkg -s in the same directory to make the package. Finally I installed it via
pacman -U gnome-splashscreen-manager and could then install the previously downloaded splashscreen.
The GDM Greeter is easily installed via „System -> Administration -> Login Window“, where the whole package can be referenced.
For the wallpaper, I have right now installed the package
archlinux-wallpaper and choose one of those. I have to admit, that I think these backgrounds are a little bit too dark for myself.
Now my system is „archified“ and I can show, that I own an Arch Linux system.
Since I am a long time Gnome user (well, I have used Ubuntu for almost 5 years), I thought, if I am going to install a new distro (Arch Linux in this case) I switch my Desktop Environment as well. Therefor I installed KDE.
Let me tell you, that I was not really happy with this decision, and that’s why I have chosen to de-install KDE (version 4.3) and install GNOME 2.6. I followed the instructions for de-installing on the ArchLinux Wiki (DE) and everything went smooth. Afterwards, I installed Gnome using once again the ArchLinux Wiki (DE) as a guide.
After re-starting my system, the GDM came up, but after logging in, I got an error message, telling me that the „System has no xclients file. starting up in xterm……“. Also I did not receive a nice Gnome Desktop, but only a small shell in the upper left corner. I found this page in the Arch Linux Forum, where somebody claimed that another user could login. Therefor I looked into my own homedirectory and found several X-related subdirectories (starting with a „.“, meaning to see them you have to do a
ls -al). I deleted all KDE and X related stuff and all directories, where I was pretty unsure for what reason they were created. After this, Gnome was running smoothly.
One more thing to add, do not start GDM via rc.conf (DEAMONS=) and via inittab. I put GDM inside both configuration files and GDM started, but showed an error, that another X-Server tried to start as well. After removing GDM from rc.conf, everything was fine.
I am writing this post now under Gnome using Firefox 🙂
The next step is now to install a nice Theme (ARCH specific) and probably even a bootsplash.
I have now successfully installed Arch Linux on my Thinkpad W500. Sound was a problem. I do have the following Soundcard in the Laptop:
[root@athene modprobe.d]# cat /proc/asound/card0/codec#* | grep Codec
Codec: Conexant CX20561 (Hermosa)
Codec: Conexant ID 2c06
To get this up and running I edited the file
/etc/modprobe.d/alsa-sound.conf (keep in mind, that there is probably already a file 50-alsa.conf or something like that, which is can be configured in the described way as well, I just renamed this file) with the following entries:
options snd-hda-intel model=laptop
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
and added my user to the group audio using the following command:
gpasswd -a USERNAME audio
You can then test your audio device with the following command:
The following link (in german) was really useful for me: http://wiki.archlinux.de/title/Alsa
Be aware, that you will find the Soundcard in the following list with the model name Conexant 5051
Hello, I do have quite some experiences with Linux Distos (in the last couple of years mainly Ubuntu). Now I have shifted to ARCH. I am going to write more about this choice in the future. Right now I would like to explain, how to get packages (in my case networkmanager-plasmoid-svn) from the AUR to my machine:
1) download a AUR-Helper, I am using yogurt (download the code on the bottom of the page.
2) Yogurt needs a
pacman -S sudo upfront, because otherwise it is not working correctly
3) as root call
visudo and add your user with the following line to the sudoers-file
username ALL=(ALL) ALL
4) change the line
sudo makepkg -s -i || error "Makepkg was unable to create or install the package." to
makepkg -s -i || error "Makepkg was unable to create or install the package."
After this „installation“ you can now install a new package using yogurt.sh (e.g. ./yogurt.sh networkmanager-plasmoid-svn). If the script asks you for a password, provide you own password.
I just upgraded (basically I installed totally from scratch) my machine to Ubuntu Feisty Fawn. I am working at home with NFS all the time. The process of mounting was pretty slow after the upgrade. Therefor I read a couple of articles on the web and figured, that you have to install portmap on your client machine as well. Now everthing is working.
Today I found a rather nice description from a guy having a similar Laptop then myself. He describes, what is working and what not, so, if you have a Sony VAIO GRX616MP/SP, take a look at this link.