Ho appena installato Fedora 12 64 bit sul desktop di casa.

L’installazione è andata bene e a mio avviso è stata anche più rapida rispetto a quella di Fedora 11.

Aggiungo i repository Rpm Fusion , installo gli ultimi driver nvidia e riavvio.

Mi accorgo subito che il desktop risulta lento in alcune operazioni semplicissime come l’apertura del menu principale (Alt + F1) o di “Run Command” (Alt + F2). Dopo aver fatto alcune ricerche in google e aver provato varie configurazioni di  xorg.conf, l’unica soluzione valida è stata quella di fare un downgrade di xorg-x11-server-Xorg e xorg-x11-server-common alla versione 1.7.1.3 che potete trovare qui.

Per il resto funziona tutto bene e tutte le periferiche sono state riconosciute senze problemi o interventi manuali.

Comando : gft

gft 1024 768 60

Onde resolução seguido da frequência que o monitor usa…..

Zakładam, że masz zainstalowany sam system bazowy i nie korzystałeś jak do tej pory z innego menedżera okien, a więc nie masz zainstalowanego xorga. Jeśli jest inaczej, to możesz pominąć jego instalację.

Instalacja tego co konieczne, a bynajmniej przydatne

Wpierw instalujemy xorga:
# aptitude install xterm xserver-xorg xfonts-base xbase-clients

Teraz czas na fluxboxa:
# aptitude install fluxbox

Będziemy potrzebowali jeszcze menedżera logowania, ja polecam nodm:
# aptitude install nodm

Aby nodm uruchamiał się automatycznie należy nieco edytować jego plik konfiguracyjny /etc/default/nodm. Interesują nas linie:

NODM_ENABLED=false
NODM_USER=root

zamieniamy je na:

NODM_ENABLED=true
NODM_USER=trym

Oczywiście nic nie stoi na przeszkodzie aby zainstalować np. kdm, gdm, xdm, etc…

Teraz już możemy śmiało wykonać polecenie:
$ startx

No i jesteśmy w naszych okienkach (tzw. xach). Widok, który ujrzymy wygląda jak na zrzucie poniżej.

Niektórzy użytkownicy mogą być nieco zaskoczeni faktem, iż nie mamy ustawionego tła pulpitu (tapety) czy żadnych ikon. Na pociesznie jednak dodam, że w tym cały urok Fluxboxa. Konfigurujemy go wedle własnego uznania – nic nie jest z góry narzucane.

Dla wygody zainstalujemy sobie jeszcze menedżer plików i motyw ikon:
aptitude install pcmanfm lxappearance

Lxappearance jest w tym wypadku może nie niezbędny, ale wskazany. Uruchamiamy go i wybieramy motyw. Dzięki temu unikniemy komunikatu o błędzie przy uruchamianiu pcmanfm. Pamiętamy, iż należy motyw ustawić zarówno dla zwykłego użytkownika jak i root — poprzez uruchomienie programu z poziomu obydwu użytkowników.

Ustawienie tła pulpitu

Instalujemy aplikację feh:
# aptitude install feh

Tworzymy plik, który będzie odpowiadał nam za uruchamianie pewnych programów przy starcie i nadajemy odpowiednie uprawnienia:
$ touch /home/trym/.fluxbox/autostart
$ chmod +x /home/trym/.fluxbox/autostart

w nowo utworzonym pliku wpisujemy:

#!/bin/bash
fbsetbg -f /home/trym/download/tapety/aktualna_tap.jpg &

/home/trym/download/tapety/aktualna_tap.jpg – jest to ścieżka do pliku tła. Ponadto pamiętamy o znaku & na końcu wiersza.

W pliku /home/trym/.fluxbox/init odnajdujemy linię:

session.screen0.rootCommand:

i zamieniamy na:

session.screen0.rootCommand: /home/trym/.fluxbox/autostart

Restartujemy Fluxboxa (PPM -> Restart) i już mamy wybraną tapetę w trybie pełnoekranowym.

Ikony na pulpicie

Instalacja:
# aptitude install idesk

Tworzymy odpowiednie foldery i plik:
$ mkdir /home/trym/.idekstop
$ mkdir /home/trym/.idesktop/icons
$ vim /home/trym/.ideskrc

Utworzony plik wypełniamy treścią:

table Config
FontName: sans
FontSize: 8
FontColor: #aeb3bf
Locked: false
Transparency: 0
HighContrast: true
Shadow: true
ShadowColor: #000000
ShadowX: 1
ShadowY: 2
Bold: false
ClickDelay: 300
IconSnap: true
SnapWidth: 10
SnapHeight: 10
SnapOrigin: BottomRight
SnapShadow: true
SnapShadowTrans: 200
CaptionOnHover: false
end
table Actions
Lock: control right doubleClk
Reload: middle doubleClk
Drag: left hold
EndDrag: left singleClk
Execute[0]: left singleClk
Execute[1]: right singleClk
end

Umieszczamy interesującą nas ikonę z rozszerzeniem .png, .jpg lub .gif w katalogu /home/trym/.idesktop/icons. Dla tego przykładu niech zawiera ona nazwę home.png. Jeśli chcesz skorzystać z ikon typowych dla zainstalowanych programów to zajrzyj do katalogu /usr/share/applications, bardzo prawdopodobne, że znajdziesz tam właściwą ikonę.

Dla każdej ikony tworzymy odpowiedni plik konfiguracyjny:
$ vim /home/trym/.idesktop/home.lnk

Uzupełniamy:

table Icon
Caption: trym
Command: pcmanfm /home/trym
Icon: /home/trym/.idesktop/icons/home.png
Width: 48
Height: 48
X: 39
Y: 9
end

Na koniec dopisujemy do autostartu ideska, wydając polecenie:
$ echo 'idesk &'>>/home/trym/.fluxbox/autostart

Wygodne wyłączanie komputera

Instalujemy kolejne pakiety:
# aptitude install sudo gtkdialog

Następnie edytujemy plik /etc/sudoers/ wydając polecenie:
# visudo

I dopisujemy na końcu pliku:

User_Alias USERS=trym
Cmnd_Alias SHUTDOWN=/sbin/shutdown
Cmnd_Alias HALT=/sbin/halt
Cmnd_Alias REBOOT=/sbin/reboot

USERS ALL=NOPASSWD:SHUTDOWN
USERS ALL=NOPASSWD:HALT
USERS ALL=NOPASSWD:REBOOT

Tworzymy katalog, pobieramy odpowiedni plik:
$ mkdir ~/download
$ cd ~/download
$ wget http://hag-linux.eu.org/deb/pool/main/h/hag-exit-fluxbox/hag-exit-fluxbox_0.3-1_all.deb

Instalujemy pobrany pakiet:
# dpkg -i hag-exit-fluxbox_0.3-1_all.deb

Tworzymy ikonę zgodnie z opisem wyżej (Ikony na pulpicie) jako polecenie podając:

hag-exit-fluxbox

Po wywołaniu aktywatora (ikony) ukaże nam się taki widok:

Niektóre opcje mogą być niedostępne. Na przykład aby móc hibernować peceta zainstalujmy pakiet hibernate.

Ustawienie godziny i trybu wyświetlania zegara

Tryb wyświetlania 12h lub 24h ustawimy najeżdżając na zegar kursorem, klikając prawym przyciskiem myszy i wybierając odpowiednią opcję. Podobnie sprawa wygląda z tym jak szczegółowy czas chcemy by był pokazywany (HH:MM czy może HH:MM:SS).

Jeśli chodzi o ustawienie godziny to należy wydać odpowiednią komendę z konsoli, przykładowo:
# date -s 23:05

Skrót “pokaż pulpit”

Odczytujemy kombinację klawiszy za pomocą np. xbindkeys -k, gdzie otrzymamy przykładowo:

“(Scheme function)”
m:0×80 + c:40
Mod5 + d

Nas interesuje jedynie zapis Mod5 + d i należy go zapamiętać.

Edytujemy plik:
$ vim /home/trym/.fluxbox/keys

wpisując do niego (na końcu) między innymi wcześniej zapamiętany ciąg:

Mod5 d :ShowDesktop

Restart Fluxboxa i od tej pory pod kombinacją klawiszy prawy_Alt + d (lub inną, którą podaliśmy) mamy funkcję wyświetlającą “czysty” pulpit.

Section "Monitor"
Identifier "samsung-2243bw"
HorizSync 30-81
VertRefresh 50-85
Modeline "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync +Vsync
EndSection
Section "Screen"
Identifier "Screen 1"
Monitor "samsung-2243bw"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1680x1050" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1680x1050" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1"
EndSection
Section "InputDevice"
Identifier "VBoxMouse"
Driver "vboxmouse"
Option "CorePointer"
EndSection

Enjoy and share.

If you want to capture your desktop regularly for accounting or other purposes, here is how I implemented this on my Kubuntu desktop machine.

I found the following packages in my Karmic Kubuntu repository:

• scrot – easy batch mode, only console interface
• deskscribe – just records in some text log files, no image screenshots
• ksnapshot – dcop problems while trying to make it work in batch mode

The winner is scrot. The simple Bash scripts I developed do the following:

• Makes a snapshot, suitable for running automatically by crontab (make-snapshot.sh)
• Tests if there are recent snapshots in a specified folder; an error is issued otherwise (test-snapshot.sh)

Here is what I’ve put in my user’s crontab (“crontab -e”):

* * * * * ~/make-snapshot.sh :0 /no-backup/famzah/snapshots
* * * * * ~/test-snapshot.sh 5 /no-backup/famzah/snapshots

This way a snapshot is made every minute. Every five minutes a check is made if the snapshot utility works properly. In the case of an error, the output from the “test-snapshot.sh” script is sent via email by crontab. This is a standard feature of crontab.

The scripts have a help message, in case any of the parameters are not very clear. You need to install the “scrot” package by the following command:

sudo apt-get install scrot

A TODO note: Crontab script to clean up very old screenshots. A simple “find -mtime … | xargs rm …” should do the trick.

Portland, OR

I was so proud for the forth time be part of the X crew, this time in Portland. Really amazing the city. I had the opportunity to play tourist and visit some nice places.

My X conferences

BTW, I just collect the photos of all four X conferences that I’ve attended. It’s not much photos but there’s some funny things

X on embedded

The cool thing of the work that I’m doing at Nokia is that I can publish and discuss mostly all X fun with the open source communities. “Mostly” because, for the last device – the N-shiny-and-awesome-900 – for instance, the video driver is closed (provided by Imagination), so we cannot comment much regarding such driver stack C’est la vie.

So we’ve been using Xorg for our small devices (FWIW the development of kdrive based servers is dead! Period). Therefore, myself and Oliver brought to XDC some discussions that we had about X server for tiny systems. Xorg DDX is still too fat. There’s a lot of code that we can cut off and that was the whole idea of our talk, more concerned about Xorg’s memory footprint.

Life is beautiful

6 months living in Helsinki: hosted 4 visits of friends, 5 new European countries visited and an average of 2 pints per day Lot of fun and no time at all for opensource pet projects. Even so, I’m enjoying! Besides, I bought an skate board and I’m speaking the first Finnish words already. I’m happy also that I’m (finally) finding time again to appreciate a good music (but didn’t get a guitar yet for me here). Let’s see what will be my next musical project… Nähdään!

Bueno, acá les vengo a contar ésto que me pasó hoy mismo a la mañana.

Hace unos días, se publicó la versión 1.7 de Xorg, y como todos sabemos, Arch suele estar siempre al día, gracias a lo cual ya desde ayer teníamos dicha versión disponible en repositorios. Y ahí empezó la odisea, ya que, tras actualizarlos y reiniciar mi PC que quedé sin servidor gráfico. Y no había caso, no podía levantar las Xs de ninguna forma.

Tras luchar un poco, las levante usando vesa y ahi, buscando en el foro de Arch me enteré del problema, el cual no fue anunciando ni en el sitio de Arch (al menos hasta éste momento, sigue sin publicarse nada al respecto). La única mención que ví está en la lista de correo de desarrolladores.

Pero, ¿cuál es el problema?, muy sencillo que Xorg 1.7 es incompatible con todos los drivers legacy de Nvidia (las series 173xx y 96xx). O sea, que si tenés una placa de video Nvidia medio viejita olvídate de usar el nuevo Xorg, por lo menos, hasta que salgan nuevas versiones de los drivers solucionando ésto.

Pero bueno, ¿están ustedes en la misma que yo? les pasó lo mismo y ahora están sin entorno gráfico. La solución es relativamente sencilla. Es más, tenemos 3 opciones.

1_ Usar el driver NV

pacman -S xf86-video-nv

2_ Usar el divrer Nouveau

pacman -S nouveau-drm xf86-video-nouveau

Tanto para la opción 1 como para la 2, recuerden editar el xorg.conf y poner en la opción driver, el que corresponde en reemplazo del nvidia que tenían.

3_ Hacer un downgrade a la versión anterior de Xorg donde no había problemas.

El downgrade fue lo que yo hice. Y volví a la versión 1.6.3 que tenía antes. Existen 2 formas de hacerlo. La primera es buscar en var/cache/pacman/pkg el paquete deseado y luego, con un

pacman -U nombredelpaquete-versionvieja.pkg.tar.gz

Instalamos dicha versión, en nuestro caso, sería el paquete xorg-server-1.6.3.901-1-i686.pkg.tar.gz pero bueno obviamente yo no tengo tanta suerte y mi cache estaba vacía. Por lo que tomé el camino difícil.

Tal y como dice la wiki de Arch, fue a ver el estado de los mirrors de los repositorios y busqué alguno que todavía no se hubiese actualizado (hay algunos que tardan días o semanas en hacerlo). Entonces elegí uno de esos. Recuerden que a la web del mirror al final deben agregarle “$repo/os/i686” o el “$repo/os/x86_64” según su versión del sistema. Luego edité mi mirrorlist, en donde agregue dicho mirror y, temporalmente, comente todos los otros. Eso se hace, con un

sudo nano /etc/pacman.d/mirrorlist

Es lo mismo si usan nano, gedit, mousepad, kwrite o el que deseen. Yo pongo nano porque asumo que no tiene entorno gráfico para usar los otros. Entonces le agregan # a todos los mirrors y copian al comienzo el mirror elegido para que quede algo así:

Server = ftp://atviras.lt/archmirror/$repo/os/i686
#Server = http://www.las.ic.unicamp.br/pub/archlinux/$repo/os/i686
#Server = http://mirror.umoss.org/archlinux/$repo/os/i686

En donde el primero es, justamente, el mirror con paquetes viejos. Entonces, ya solo es cuestión de actualizar los repos y reinstalar Xorg. Aunque previamente, debemos hacer un downgrade a xf86-input-evdev debido a las dependencías. Entonces hacemos

sudo pacman -Syy
sudo pacman -S xf86-input-evdev
sudo pacman -S xorg

Durante el proceso, el mismo pacman les avisará que van a bajar de versión los programas y les pedirá la confirmación dicen que si, y listo. Ya tendrán el Xorg viejo instalado, ahora reinician el sistema y listo.

Si todo funcionó bien, ya pueden volver a editar el mirrorlist, quitando el repo que agregamos y volviendo a activar los que usan habitualmente. Ahora, para que en el próximo upgrade pacman no vuelva a actualizarles el Xorg, hay que editar el pacman.conf y decirler que ignore a xorg:

sudo kwrite /etc/pacman.conf

y lo editamos para que quede así

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = xf86-input-evdev
IgnoreGroup = xorg

Y listo. Solucionado todo el problema. Si algún día se actualizan los drivers Nvidia o cambian de placa, editan el pacman.conf borrando la referencia a ignorar xorg y listo, volverá a actualizare normalmente como cualquier otro paquete.

Y, ¿Cuál es la moraleja de todo ésto? es que siempre que se actualicen éstos paquetes importantes del sistema como Xorg, el kernel o cosas así, esperen unos días para actualizarse. Y antes de hacerlo, revisen el foro de Arch a ver si surgieron problemas con dicho update ya que puede pasarles a ustedes .

¡Hola!

Desde ayer 26/10/2009, ya contamos con la nueva versión del servidor gráfico más popular entre los sistemas unix (X.org), de este lanzamiento podemos destacar lo siguiente:

Características Agregadas/Mejoradas

• La compilación de Xserver ya no requiere enlace simbólico a las fuentes de Mesa.
• MPX: Multi-Pointer X.
• Soporte para E-EDID.
• Propiedades de los dispositivos de entrada.
• Predictable pointer acceleration.
• Xorg-server 1.7.0
• Añadido el módulo de seguridad de SELinux, que utiliza XACE.
• RandR 1.3

Entre otros que puedes ver desde aqui: http://www.x.org/wiki/Releases/7.5

Es muy seguro que pronto podremos disfrutar de estas mejoras en nuestra distro, si eres como yo, y no te gusta esperar, debajo está el enlace a todito el código fuente .

Enlaces de interés:

• http://www.x.org/releases/X11R7.5/src/ (Los tarball de código fuente).
• http://www.x.org/releases/X11R7.5/doc/RELNOTES.pdf (Notas de lanzamiento en PDF).
• http://www.x.org/releases/X11R7.5/doc/index.html (La documentación).
• http://www.x.org/releases/X11R7.5/changelog.html (El log de cambios).

y si aún tienes dudas de que se trata esto …

• http://es.wikipedia.org/wiki/XOrg (Artículo enciclopédico).

Hasta luego.

Sometimes you need standby for your Xorg server and sometimes not (surveillance applications don’t need it). I will try to show you in several lines how you can configure that.

To control standby for your monitor you need to see if you have enabled Display Power Management Signaling enabled.

For that try to run following command in a xterm

$xset q
DPMS (Energy Star):
Standby: 1200 Suspend: 1800 Off: 2400
DPMS is Enabled
Monitor is On

if is not enabled just run

$xset +dpms


To set standby, suspend and off parameters run
$xset dpms X Y Z
where X is standby time, Y is suspend time and Z is off time all in seconds.

To set that at every Xorg boot then you should add the following lines to your xorg.conf
Section “ServerFlags”
Option “blank time” “150″
Option “standby time” “300″
Option “suspend time” “600″
Option “off time” “1200″
Option “dpms” “true”
EndSection

If you want to disable DPMS standby then put this configuration in your xorg.conf

Section “ServerFlags”
Option “blank time” “0″
Option “standby time” “0″
Option “suspend time” “0″
Option “off time” “0″
Option “dpms” “false”
EndSection

Also read here http://www.randombugs.com/linux/disable-monitor-standby-xorg-xserver.html

OpenSolaris2009.06-GNOMEOriginally uploaded by Megaf

Olá todos, já faz um tempinho que não posto aqui.
Ainda estou vivo, só estou meio sem vontade de fazer muitas coisas.
Meu saco de vontade ta sendo tomado pela faculdade.
É, estou cursando Engenharia da Computação.

Aqui estou dando uma trégua de Linux e Mandriva.
Porque as versões 2009.x não estão muito boas, na minha opnião, decidi dar um tempo.

Resolvi agora voltar ao OpenSolaris, sistema que eu já testara a algum tempo atras.

Antes de tomar esta decisão radical de mudar de Linux pra OpenSolaris averiguei e matutei sobre alguns pontos, como os softwares que uso.

Muitos dos softwares que uso, como o NetBeans, VirtualBox, JAVA e VirtualBox, são, justamente da Sun, a empresa por tras do Solaris.

E praticamente todos outros softwares que uso, tem versão estável e recente tambem para o OpenSolaris, como:
Totem, XChat, Pidgin, Opera…

Então, por que não mudar?

Continuo agora testando outras distros, como o Debian/kFreeBSD e Haiku. E usando o Mandriva Cooker.
Rodando eles no VirtualBox.

Instalar o VirtualBox no OpenSolaris é ainda mais fácil que no Linux, são necessários apenas 2 comandos, não é preciso configurar nada, só instalar dois pacotes e pronto.
O dezempenho das máquinas virtuais rodando no VirtualBox com o OpenSolaris como host é simplismente fantástico.

Uma agradável surpresa que tive, foi assistir vídeos em tela cheia no YouTube com um tempo de resposta praticamente em tempo real. No Linux, ao mover o mouse sobre a barra de posição, ou pausar e dar o play, eu tinha que esperar alguns encomodos segundos, no Windows alguns milésimos, mas aqui, no OpenSolaris, é em tempo real.

Por enquanto não tenho muito o que reclamar deste sistema, muito pelo contrário, ele é extremamente rápido e responsivel, além da já conhecida estabilidade.

Algo que devo comentar, pela primeira vez, em toda minha história computacional, não tive vontade de alterar o tema de ícones, cursores ou estilo visual. A interface do OpenSolaris é brilhante. Limpa, bem dezenhada, bem trabalhada, agradavel de usar.

É isto, é um sistema que eu realmente recomendo testar, ainda mais para usuários que já tenham experiência com UNIX e/ou SunOS.

Aquele abraço!

One reason that I chose MythTV early on was for its ability to interface with other “satellite” frontend machines that I could place around the house in various locations where I have already installed hardwired Ethernet jacks.  Unless I wish to stream demanding high definition content, the frontend machines do not need to be equipped with expensive or modern hardware.

Here’s a case in point example.  I’ve had an old Dell Inspiron 8200 kicking around for a while that has a bad IDE controller.  It refuses to boot from the hard disk or the optical drive.  By most consequences, this machine is pretty much useless as is.  Enter PXE booting.  A BIOS setting in the 8200 allows for network booting.

I have experimented with linux and network booting in the past and have had joy using Diskless Remote Boot in Linux (DRBL) to network boot a DSL iso file from my Linux server to other computers around the house.  NFSRoot is a popular alternative and requires a dedicated box running a DHCP & TFTP servers and PXELINUX to boot a root filesystem over NFS.  My experience with this method has been frustrating and I never did get it working correctly using Debian.

I thought I would give it another shot and attempt to create a diskless frontend using the Inspiron.  I skipped all the manual configuration and opted to use a script available with the Knoppmyth distro to create a diskless frontend.  Basically the script sets up and configures the DHCP and TFTP servers on the myth backend and does all the hard work.  The Knoppmyth wiki has a good entry on how to get this going:

http://www.knoppmythwiki.org/index.php?page=DisklessFrontend

One thing that must be considered is that your frontend hardware will most likely be different from the backend hardware where the script was executed.  In my situation, from the backend, I had to reconfigure /nfsroot/dell8200/etc/X11/xorg.conf to get it play nicely with the Inspiron.  After a lot of googling and trial and error, I came up with a working xorg.conf that was compatible with the Inspiron’s 1600×1200 display.  Once changed, I had a diskless frontend working on the Inspiron with recorded programs available and live TV from the Motorola 6200 cable box.

Below is my xorg.conf for the Dell Inspiron 8200.  Note that I haven’t been successful getting an updated Nvidia driver installed for the older Nvidia graphics in the 8200.  One other issue involves navigating menus on the frontend.  When cycling through the menu using the arrow keys on the keyboard, it seems that two button clicks are being registered causing the menu to skip ahead one extra level – an annoying issue.  More time needed but it’s a good start…

# File generated by xorgconfig.

#

# Copyright 2004 The X.Org Foundation

#

# Permission is hereby granted, free of charge, to any person obtaining a

# copy of this software and associated documentation files (the “Software”),

# to deal in the Software without restriction, including without limitation

# the rights to use, copy, modify, merge, publish, distribute, sublicense,

# and/or sell copies of the Software, and to permit persons to whom the

# Software is furnished to do so, subject to the following conditions:

#

# The above copyright notice and this permission notice shall be included in

# all copies or substantial portions of the Software.

#

# THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL

# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF

# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

# SOFTWARE.

#

# Except as contained in this notice, the name of The X.Org Foundation shall

# not be used in advertising or otherwise to promote the sale, use or other

# dealings in this Software without prior written authorization from

# The X.Org Foundation.

#

# **********************************************************************

# Refer to the xorg.conf(5x) man page for details about the format of

# this file.

# **********************************************************************

# **********************************************************************

# Module section — this  section  is used to specify

# which dynamically loadable modules to load.

# **********************************************************************

#

Section “Module”

# Alps Touchpad

#    Load   “synaptics”

# This loads the DBE extension module.

Load        “dbe”  # Double buffer extension

# This loads the miscellaneous extensions module, and disables

# initialisation of the XFree86-DGA extension within that module.

SubSection  “extmod”

Option    “omit xfree86-dga”   # don’t initialise the DGA extension

EndSubSection

# This loads the font modules

#    Load        “type1″

Load        “speedo”

Load        “freetype”

#    Load        “xtt”

# This loads the GLX module

Load       “glx”

# This loads the DRI module

#    Load       “dri”

EndSection

# **********************************************************************

# Files section.  This allows default font and rgb paths to be set

# **********************************************************************

Section “Files”

# The location of the RGB database.  Note, this is the name of the

# file minus the extension (like “.txt” or “.db”).  There is normally

# no need to change the default.

RgbPath “/usr/X11R6/lib/X11/rgb”

# Multiple FontPath entries are allowed (which are concatenated together),

# as well as specifying multiple comma-separated entries in one FontPath

# command (or a combination of both methods)

#

#

FontPath   “/usr/share/fonts/misc/”

FontPath   “/usr/share/fonts/TTF/”

FontPath   “/usr/share/fonts/Type1/”

#    FontPath   “/usr/share/fonts/CID/”

FontPath   “/usr/share/fonts/75dpi/”

FontPath   “/usr/share/fonts/100dpi/”

FontPath   “/usr/share/fonts/local/”

#    FontPath   “/usr/share/fonts/Speedo/”

#    FontPath   “/usr/share/fonts/TrueType/”

#    FontPath   “/usr/share/fonts/freefont/”

# The module search path.  The default path is shown here.

#    ModulePath “/usr/X11R6/lib/modules”

EndSection

# **********************************************************************

# Input devices

# **********************************************************************

# **********************************************************************

# Core keyboard’s InputDevice section

# **********************************************************************

Section “InputDevice”

Identifier    “Keyboard1″

Driver  “kbd”

Option “AutoRepeat” “500 30″

Option “XkbRules”   “xorg”

Option “XkbModel”   “pc101″

Option “XkbLayout”  “us”

EndSection

# **********************************************************************

# Core Pointer’s InputDevice section

# **********************************************************************

Section “InputDevice”

Driver            “mouse”

Identifier  “USB-Mouse”

Option            “Device”    “/dev/input/mice”

Option            “Emulate3Buttons” “true”

Option            “ZAxisMapping”    “4 5″

EndSection

#Section “InputDevice”

#  Driver  “synaptics”

#  Identifier     “Alps”

#  Option   “Device”          “/dev/psaux”

#  Option   “Protocol”        “auto-dev”

#  Option   “LeftEdge”        “120″

#  Option   “RightEdge”       “830″

#  Option   “TopEdge”         “120″

#  Option   “BottomEdge”            “650″

#  Option   “FingerLow”       “14″

#  Option   “FingerHigh”            “15″

#  Option   “MaxTapTime”            “180″

#  Option   “MaxTapMove”            “110″

#  Option   “EmulateMidButtonTime”  “75″

#  Option   “VertScrollDelta” “20″

#  Option   “HorizScrollDelta”      “20″

#  Option   “MinSpeed”        “0.4″

#  Option   “MaxSpeed”        “0.8″

#  Option   “AccelFactor”           “0.02″

#  Option   “EdgeMotionMinSpeed”    “15″

#  Option   “EdgeMotionMaxSpeed”    “15″

#  Option   “UpDownScrolling” “1″

#  Option   “CircularScrolling”     “1″

#  Option   “CircScrollDelta” “0.1″

#  Option   “CircScrollTrigger”     “2″

#EndSection

#######################This is old touchpad

#Section “InputDevice”

#    Identifier   “Mouse1″

#    Driver “mouse”

#    Option “Protocol”    “GlidePointPS/2″

#    Option “Device”      “/dev/input/mouse0″

#    Option “Emulate3Buttons”

#EndSection

# **********************************************************************

# Monitor section

# **********************************************************************

# Any number of monitor sections may be present

Section “Monitor”

Identifier  “Monitor0″

# HorizSync is in kHz unless units are specified.

# HorizSync may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync   31.5 – 90.0

#    HorizSync    30-64         # multisync

#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies

#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.

# VertRefresh may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 59.0 – 85.0

EndSection

# **********************************************************************

# Graphics device section

# **********************************************************************

# Device configured by xorgconfig:

Section “Device”

Identifier  “Card0″

Driver      “nv”

# unsupported card

#VideoRam    65536

# Insert Clocks lines here if appropriate

EndSection

# **********************************************************************

# Screen sections

# **********************************************************************

# Any number of screen sections may be present.  Each describes

# the configuration of a single screen.  A single specific screen section

# may be specified from the X server command line with the “-screen”

# option.

Section “Screen”

Identifier  “Screen 1″

Device      “Card0″

Monitor     “Monitor0″

DefaultDepth 24

Subsection “Display”

Depth       8

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″

“640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       16

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       24

Modes       “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

EndSection

# **********************************************************************

# ServerLayout sections.

# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes

# the way multiple screens are organised.  A specific ServerLayout

# section may be specified from the X server command line with the

# “-layout” option.  In the absence of this, the first section is used.

# When now ServerLayout section is present, the first Screen section

# is used alone.

Section “ServerLayout”

# The Identifier line must be present

Identifier  “Simple Layout”

# Each Screen line specifies a Screen section name, and optionally

# the relative position of other screens.  The four names after

# primary screen name are the screens to the top, bottom, left and right

# of the primary screen.  In this example, screen 2 is located to the

# right of screen 1.

Screen “Screen 1″

# Each InputDevice line specifies an InputDevice section name and

# optionally some options to specify the way the device is to be

# used.  Those options include “CorePointer”, “CoreKeyboard” and

# “SendCoreEvents”.

#InputDevice “Mouse1″ “CorePointer”

#InputDevice “Alps” “CorePointer”

InputDevice “USB-Mouse” “AlwaysCore”

InputDevice “Keyboard1″ “CoreKeyboard”

EndSection

# Section “DRI”

#    Mode 0666

# EndSection

]]> http://pacoros.wordpress.com/2009/10/02/tips-to-make-acer-aspire-one-751h-ao751h-work-better-with-ubuntu/ Fri, 02 Oct 2009 20:47:00 +0000 Paco Ros http://pacoros.wordpress.com/2009/10/02/tips-to-make-acer-aspire-one-751h-ao751h-work-better-with-ubuntu/

The new toy from Acer is a affordable netbook featuring HT Intel Atom Z520 and a 1366×768 11.” LED LCD.

Almost all the hardwre included inside thie “piece of iron” is good and works out of the box with Ubuntu 9.04 (a.k.a. Jaunty) updated to 2.6.28-15 linux kernel version, but some manual configuration is needed to leave all the (at least for me) important things working:

Graphics Driver

I can’t stand without complaining about the stupid fact that Intel ordered another corp to develop the drivers for Intel GMA500 graphics chip. Somebody contracted Tungsten Graphics to build a driver that makes Dell mini family work with this piece of hell… and they did! So we now have a unmaintained old graphics driver with a binary privative piece inside it and we have to push it inside a free software system. I’d like to thank Lucazade at this point for the efforts made for this crap to work.

After complaining, let’s go for work. Remember this word, it’ll be your obsession th next hour afer you read this post: poulsbo. All GMA500 stuff is labeled with poulsbo or psk keyword, so, you know, you can begin by apt-cache searching for this term.

Begin by adding the following unofficial repositories to your /etc/apt/sources.list

deb http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu jaunty main

And authorize PPA packages to be installed

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C6598A30

If you arrived here, you’ll probably know what to do:

$ sudo apt-get update
$ sudo apt-get install poulsbo-driver-2d poulsbo-driver-3d psb-firmware

But, this is not enough, you must compile and install a kernel driver (let DKMS do the work):

$ sudo apt-get install psb-kernel-source

Time to reboot now, next time you login you’ll see a beautiful 1366×768 3D accelerated desktop. No need to edit /etc/X11/xorg.conf for me, but you can do to enable horitzontal scrolling for synaptics touchpad.

If you want to enable desktop effects, locate /usr/bin/compiz and add psb at the beggining of the list in the line “WHITELIST”

WHITELIST="psb nvidia intel ati radeon i810 fglrx"

Now you can activate compiz by selecting System -> Appearance -> Visual Effects and clicking in “Normal”

Remember, if you update the kernel you must reinstall psb kernel module and if compiz-wrapper gets updated, you should edit it again and add psb to whitelist. You can read the long thread about GMA500, poulsbo and ubuntu at ubuntu forums here.

Wireless

ath5k works out of the box. I tried to enable Atheros unsuccessfully, but there’s no need to enable it because ath5k seems to work fine, despite of some messages about jumbo packages being logged in syslog. I will try to make Madwifi work when I have some time, it’s useful if you need to inject frames in a signal.

Suspend to RAM

All the info above can be easily found in the internet, but there is no info about suspend. Suspend works out of the box, but it got broken when you installed psb video driver (Did i told this is a piece of shit?) and I can’t imagine a laptop that can’t be suspended. Fortunately Wander Boessenkool published a patch to hal mailing list. You must locate /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-acer.fdi and add the following at the end (before the last </match>):

<match key="system.hardware.product" string="AO751h">
   <merge key="power_management.quirk.dpms_on" type="bool">true</merge>
   <merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
   <merge key="power_management.quirk.vbestate_restore" type="bool">true</merge>
 </match>

This patch shouldn’t take too many time to be included in ubuntu hal packages. Remember to edit it it again if you update hal.

I couldn’t get suspend working by closing the lid. I’m working on ot and will update when it works.

Updated: It works fine by setting it in System -> Preferences -> Power Management

Enjoy the toy

Çok tuşlu fare ve klavyeleri seven bir yapıya sahip olduğum için Windows altında kullandığım multimedya özelliklerini Linux altında kullanmak istiyorum ben. Bilmiyorum haksız mıyım. Eğer sizin de 6-7 tuşlu fareniz var ve tuşları aktif değilse aşağıdaki yöntemi kullanabilirsiniz. (Anlatımın orjinali İtalyanca bir sitede. Girmek için buraya tıklayabilirsiniz. Türkçe’ye çeviren arkadaş için buraya tıklayabilirsiniz. Ben onun anlattığı yöntemi kendi uyguladığım şekliyle anlatacağım)

Öncelikle evdev adlı pakedi güncelliyoruz. Bunun için Uygulamalar -> Donatılar -> Uçbirim yolunu izleyerek terminal açıyoruz ve aşağıdaki kodları sırayla yapıştırıp entera basıyoruz:

sudo apt-get update
sudo apt-get install xserver-xorg-input-evdev

Ardından yine terminale aşağıdaki kodu yapıştırıp entera basıyoruz:

cat /proc/bus/input/devices

Bu komut ile sisteme takılı donanımların listesi terminalde görünecektir. Buradan farenizle ilgili kısmı bulun. Benimki şöyle:

Handlers yazan satırdaki event kısmına dikkat etmek gerekir. Ben kendiminki olan event4 olarak devam ettim işleme. Siz de kendinizkine göre devam edin.

Şimdi xorg.conf adlı dosyada birkaç değişiklik yapacağız.

Önce bir yedeğini alıyoruz:

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.yedek

Herhangi bir sorunda kurtarma modunda aşağıdaki kod yazılarak geri dönüş yapılabilir:

sudo cp /etc/X11/xorg.conf.yedek /etc/X11/xorg.conf

Sonra düzenlemek için xorg.conf dosyasını açıyoruz. Benimkinin fare ile ilgili kısmı şöyleydi:

Burada birkaç değişiklik yapmamız gerekiyor. Öncelikle ilk satıra yani Identifier yazan satıra dokunmuyoruz. Altındaki satırdaki “mouse”u “evdev” yapıyoruz. Onun altındaki satırın başına # koyuyoruz. Böylece o satır etkinsizleştirilir. Dilerseniz o satırı silebilirsiniz de. Bir alt satırdaki “/dev/input/mice” kısmını “dev/input/event4″ yapıyoruz. Tabi event4′ü herkes yukarıda event numarası kaç ise ona göre değiştirmelidir. Benimki event4 olduğu için öyle yaptım. Bir alttaki satırı ellemiyoruz. Onun altındaki satıra yukarıda terminalde faremiz ilgili kısımdaki Name’in karşısındaki değeri yazdım. Yani “A4Tech PS/2+USB Mouse” yazdım. İtalyanca sitedeki şahıs,  “A4Tech X7″ yazmış. Sonuç olarak

Option          "Name"	"A4Tech X7"

diye bir satır eklenmelidir buraya.

Daha sonra bir alttaki satırın başına da # konur. Böylece o satırda etkinsizleştirilir. Benim xorg.conf’umun fare ile ilgili kısmının son hali şöyle:

Kaydedip kapatıyoruz. Sistemi yeniden başlatıyoruz.

Şöyle bir kod daha var ama ben bunu çalıştıramadım hata verdi. Olmasa da olur sanırım. Eski sürümler için olabilir.(benim sürüm 9.04):

xmodmap -e "pointer=1 2 3 4 5 8 9 6 7"

Terminale şu kodu yazıyoruz şimdi de:

xev | grep button

Şöyle bir pencere açılacak:

Bu pencerede farenin tuşlarını basarak terminalde kaç numaralı tuşa denk geldiğini görebilirsiniz.

xmodmap’in varsayılan sırası şu şekilde: 1 2 3 4 5 8 9 6 7

Buradaki 8 ve 9′a dokunmuyoruz. Onlar farenin kendi ayarları ile ilgiliymiş.

Sıra Xmodmap’i kendimize göre düzenlemeye geldi. Bunun için terminale aşağıdaki kodu yazıyoruz:

gedit .Xmodmap

pointer=1 2 3 4 5 8 9 6 7

It works.  I don’t think that its very much optimized for speed, fonts, etc.  But for the time being its just peachy.

Touchpad scrolling should be working.  Going to try to deal with Mesa and freetype down the road a bit to make things look better.

Grab it here.

More to come..

This shortcut for zapping X11 server is now disabled by default. But it can be enabled.  Here are two solutions for this:

• Add this to .xinitrc file:

  setxkbmap -option terminate:ctrl_alt_bksp &

• Xorg.conf man page says that it can be done by adding this code to xorg.conf file. But this doesn’t work for me:

  Section "ServerFlags"
          Option "DontZap" "false"
  EndSection