Differences between revisions 4 and 5
Revision 4 as of 2008-03-05 00:31:20
Size: 14460
Editor: Baloo
Comment:
Revision 5 as of 2008-03-05 01:02:59
Size: 14558
Editor: Baloo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
Si decides ir por este camino, If you decide to go this route, te remito a las Páginas Man (del inglés manpage) acerca del module-assistant. You will need to run "m-a build ..." instead of "m-a auto-install ...". Note that if your Eee PC is running a different kernel version than your build machine, you will need to install the linux-headers and linux-kbuild packages corresponding to the Eee PC's kernel, and use the "-l" option to specify that version when you invoke module-assistant.

Once you have successfully built a module, copy the resulting .deb to the Eee PC and install it there with "dpkg -i ...".
Si decides ir por este camino, te remito a las páginas Man (del inglés manpage) acerca del module-assistant. Necesitarás usar "m-a build ..." en lugar de "m-a auto-install ...". Nótese que si tu Eee PC esta haciendo funcionar una versión diferente del kernel de tu la máquina que estes usando para la construcción, necesitarás instalar los paquetes linux-headers y linux-kbuild correspondientes al kernel del Eee PC, y usa la opción "-l" para especificar esta versión cuando invoques el module-assistant.

Una vez que finalizada la construcción de un módulo, copia el .deb resultante al Eee PC e instalalo en el con "dpkg -i ...".
Line 36: Line 36:
This just works now. The old version of our installer had a bug which required a manual install of atl2 after installation -- this is now no longer required. Esto ya funciona. La antigua versión de nuestro instalador tenía un bug que requería la instalación manual del atl2 después de la instalación -- esto ya no es necesario.
Line 38: Line 38:
Install and configure module-assistant:

Become root and invoke the following commands:
Instalar y configurar module-assistant:

Como root e invoque los siguientes comandos:
Line 45: Line 45:
Download and install this patched madwifi-source package:

Become root and invoke the following command:
Descarga e instala este paquete madwifi-source parcheado:

Como root e invoque los siguientes comandos:
Line 52: Line 52:
Be sure to have the contrib section in your {{{ /etc/apt/sources.list }}} because madwifi-source needs madwifi-tools. Now you can use module-assistant to build and install a .deb package for the driver:

Become root and invoke the following commands:
Asegúrate de que tienes la sección contrib en tu {{{ /etc/apt/sources.list }}} porque madwifi-source necesita madwifi-tools. Ahora ya puedes usar el module-assistant para construir e instalar un paquete .deb para el driver:

Como root e invoque los siguientes comandos:
Line 61: Line 61:
You may want to put the madwifi-source package on hold so that in any future upgrades it won't be overwritten. (See ["../../Todo#package_madwifi_source"]. A future release will solve this problem.) Puede que quieras marcar el paquete madwifi-source como 'mantener' para de esta forma evitar que en futuras actualizaciones sea sobreescrito. (Ver ["../../Todo#package_madwifi_source"]. Una futura revisión resolverá este problema.)

?TableOfContents

Traducciones: [:DebianEeePC/HowTo/Install:Inglés] [:DebianEeePCFrench/HowTo/Install:Francés] [:DebianEeePCGerman/HowTo/Install:Alemán] [:DebianEeePCItalian/HowTo/Install:Italiano]

Instalar Lenny usando el kernel y los módulos nativos de Debian

Este es el método recomendado para instalar Debian Lenny en un Eee PC. Si bien aún no está terminado, estamos trabajando a diario para mejorar cada uno de los pasos. El obgetivo es tener un instalador de Debian estándar que "simplemente funcione", así que estamos empleando el tiempo extra y nuestros esfuerzos para lograrlo en lugar de trabajar entorno al problema haciendo un montón de código personalizado específico del eee.

Preparación

Necesitarás un disco USB. Por favor, descarga estos ficheros:

Para preparar el disco USB, copia la imagen dentro de la unidad:

gunzip sid-usb.img.gz
dd if=sid-usb.img of=/dev/<YOUR-USB-DEVICE>

Nota: <YOUR-USB-DEVICE> = Todo el dispositivo, no una partición del dispositivo(ej. /dev/sdX NO /dev/sdX1)

Te habrás dado cuenta de que estas usando todo el dispositivo sin una tabla de particiones. Esto funciona porque la BIOS sabe cómo arrancar directamente desde particiones FAT. Este modo de arranque se llama modo "superfloppy" y esta soportado por la BIOS del Eee PC para dispositivos USB y tarjetas SD.

Instalación

Arranca el eee y presiona <ESC> en la pantalla de inicio. Esto te permite seleccionar desde que dispositivo arrancar.

La instalación actual es muy estándar; si estas leyendo esto, casi seguro que ya sabes cómo instalar Debian. :) Esta bien usar ext3 como sistema de ficheros, que es el valor por defecto. Ver http://wiki.eeeuser.com/ssd_write_limit para un argumento de peso que dice que no vas a matar tu unidad flash por el pequeño porcentaje de escrituras extras que añade un sistema de archivos con respaldo de transacciones o JFS (del inglés Journaling File System) al ciclo de vida de la unidad. Puede que quieras hacerlo sin swap simplemente porque ganarás espacio en la relativamente pequeña SSD del Eee. También ["DebianEeePC/TipsAndTricks"] enlaza a algunos consejos de ajuste si después de leer este artículo sigues preocupado en lo concerniente al ciclo de vida de escritura.

Módulos adicionales que todavía no están en los kernels de Debian

Introducción a la construcción de módulos externos-al-kernel

Las instrucciones que aparecen a continuación requieren que instales y compiles los fuentes de los módulos usando el module-assistant. Esto se puede hacer en tu Eee PC, pero se traducirá en la instalación de una gran cantidad de herramientas de desarrollo que puede ser que no necesites para nada mas.

Un método alternativo es hacer la instalación y la compilación de los módulos en otra máquina con Debian (una que sea mas rápida y tenga mas espacio en el disco), y entonces instalar los paquetes de los módulos resultantes en el Eee PC.

Si decides ir por este camino, te remito a las páginas Man (del inglés manpage) acerca del module-assistant. Necesitarás usar "m-a build ..." en lugar de "m-a auto-install ...". Nótese que si tu Eee PC esta haciendo funcionar una versión diferente del kernel de tu la máquina que estes usando para la construcción, necesitarás instalar los paquetes linux-headers y linux-kbuild correspondientes al kernel del Eee PC, y usa la opción "-l" para especificar esta versión cuando invoques el module-assistant.

Una vez que finalizada la construcción de un módulo, copia el .deb resultante al Eee PC e instalalo en el con "dpkg -i ...".

Ethernet (atl2)

Esto ya funciona. La antigua versión de nuestro instalador tenía un bug que requería la instalación manual del atl2 después de la instalación -- esto ya no es necesario.

Wireless (madwifi)

Instalar y configurar module-assistant:

Como root e invoque los siguientes comandos:

apt-get install module-assistant
m-a prepare

Descarga e instala este paquete madwifi-source parcheado:

Como root e invoque los siguientes comandos:

wget http://people.debian.org/~synrg/debian-eeepc/madwifi-source_0.9.3.2-2+eee_i386.deb
dpkg -i madwifi-source_0.9.3.2-2+eee_i386.deb

Asegúrate de que tienes la sección contrib en tu  /etc/apt/sources.list  porque madwifi-source necesita madwifi-tools. Ahora ya puedes usar el module-assistant para construir e instalar un paquete .deb para el driver:

Como root e invoque los siguientes comandos:

m-a build madwifi
m-a install madwifi
modprobe ath_pci

Puede que quieras marcar el paquete madwifi-source como 'mantener' para de esta forma evitar que en futuras actualizaciones sea sobreescrito. (Ver ["../../Todo#package_madwifi_source"]. Una futura revisión resolverá este problema.)

If you are using sid, (or the lenny version gets bumped, which it is likely to soon) then m-a a-i will first check for a newer source package. This is obviously bad as it wont have the binary patch applied. Use 'm-a build' as shown above to make the modules and then install the debs it makes in /usr/src.

See ["DebianEeePC/HowTo/Wifi"] to set up wifi with or without encryption.

Webcam (uvcvideo)

The module source in lenny should work with module-assistant:

Become root and invoke the following commands:

m-a a-i linux-uvc
modprobe uvcvideo

This won't work if you are using a 2.6.24 kernel. As noted in #[http://bugs.debian.org/463655 463655], the latest SVN revision of the driver works fine.

Then test it's working by executing:

Become root and invoke the following command:

apt-get install luvcview
As normal user you can now make use of your web cam tool
luvcview -f yuv

The camera is switched off by default after the installation. You can enable it in the BIOS, or by doing echo 1 > /proc/acpi/asus/camera. You should see messages about the camera being detected if you do dmesg | tail.

If you broke your webcam settings, use mplayer -fps 30 tv:// once to restore them.

Power management & hotkeys

Kernel module (eeepc-acpi)

The eeepc-acpi-source package is available in Debian unstable and testing. It builds an out-of-kernel module to support the Eee PC hotkeys. It was based on Asus's patched asus_acpi.c module, but doesn't conflict with standard Debian kernel packages.

First, set up a module-compilation environment as described in the Madwifi section above. Then build and install the eeepc-acpi module with module-assistant:

Become root and invoke the following commands:

m-a a-i eeepc-acpi
modprobe eeepc_acpi
/etc/init.d/acpid restart

Add eeepc_acpi to /etc/modules so that it will be loaded when you boot.

To respond properly to the acpi events, you will need the new eeepc-acpi-scripts package described in the next section, 'Scripts'.

Notes:

  • The battery info is not very precise (jumps from 10% to 100%, no rate information, etc...). Apparently, this is normal. It appears that the userspace battery utilities expect the battery to report mAh, but in fact it reports percentage. This is either a bug in the battery firmware or a bug in the BIOS. In either case, unless someone comes up with a patch to deal with batteries that report percentage, Asus needs to fix this.
  • [?DamyanIvanov] Hibernation mostly works for me on current Sid with 2.4.24 kernel once I've set up swap (and following the hints from ["DebianEeePC/TipsAndTricks"]). There is some problem with the madwifi driver that does not recover completely, but I think it is not hibernate-related as I see the same behaviour after suspend/resume.

Scripts (eeepc-acpi-scripts)

Special keys

Key

Function

Work, comment

Fn + F1

sleep

Yes

Fn + F2

wifi

Yes (read details below)

Fn + F3

- light screen

Yes

Fn + F4

+ light screen

Yes

Fn + F5

Change screen

No, nothing append

Fn + F6

Task manager

No, nothing append

Fn + F7

disabled Sound

Yes

Fn + F8

- sound

Yes

Fn + F9

+ sound

Yes

Install http://people.debian.org/~nion/debian-eeepc/eeepc-acpi-scripts_1.0_all.deb to get the described functionality. This just arrived in unstable and will be available in testing pretty soon. Please note that this package conflicts with acpi-support. You must purge acpi-support, not just remove it so that none of the acpi-support scripts that remain in /etc after removal are triggered by various acpi events.

Enabling/disabling the wifi works like plugging/unplugging the PCI Express wifi card. To ensure that it properly gets enabled when it is plugged, you need the pciehp kernel module. (And for some reason, it only works with the "pciehp_force=1" option.) Create a file /etc/modprobe.d/pciehp with 'options pciehp pciehp_force=1' in it and put 'pciehp' in /etc/modules. Then 'rmmod pciehp; modprobe pciehp'.

Read the doc in /usr/share/doc/eeepc-acpi-scripts/README.Debian and configure /etc/default/eeepc-acpi-scripts as needed.

Ethernet (atl2) upgrade

The version of atl2 binary module in Lenny is old and has bugs that are fixed in the new source package that exists in Lenny. Upgrade as follows:

Become root and invoke the following commands:

apt-get install module-assistant
m-a a-i atl2
modprobe atl2

For good measure this reloads the atl2 driver.

Xorg

Touchpad Scrolling

The default debian installer did not enable the touchpad scrolling for me. The following are bits that I had to add to xorg.conf to enable touchpad scrolling.

Section "InputDevice"
        Identifier      "Synaptics Touchpad"
        Driver          "synaptics"
        Option          "CorePointer"
        Option          "SendCoreEvents"        "true"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "auto-dev"
        Option          "HorizEdgeScroll"       "1"
EndSection
Section "Server Layout"
    Identifier          "Default Layout"
    Screen              "Default Screen"
    InputDevice         "Generic Keyboard"
    InputDevice         "Synaptics Touchpad"
EndSection

This will enable horizontal as well as vertical scrolling on the touchpad. By default, iceweasel will use the horizontal scrolling as <backwords/forwards> To disable this, go into about:config and change the following values.

mousewheel.horizscroll.withnokey.action   (change 2 to 0)
mousewheel.horizscroll.withnokey.numlines  (change -1 to 1)

Multiple displays

In /etc/X11/xorg.conf, make sure any "?HorizSync" and "?VertRefresh" lines are commented out or removed from the "Monitor" section and set "Virtual 2048 2048" in the "Display" subsection of your "Screen" section.

To enable an external display, positioning it above the Eee's own display, plug it in and type "xrandr --display VGA --above LVDS --auto". A future release of eeepc-acpi-scripts will add hotkey support for this.

Aiglx support for compiz

The following were needed to get [http://compiz.org/ Compiz] working. Compiz works for me with xfce, but its a bit choppy rotating the cube to a workspace that has opened programs on it. (If you have a good working xorg.conf thats different to this, please update)

Section "Device"
        Identifier      "Configured Video Device"
        Driver          "i810"
        Option          "XAANoOffscreenPixmaps"
        Option          "AddARGBGLXVisuals"     "true"
EndSection
Section "DRI"
    Mode 0666
Endsection
Section "Extensions"
    Option              "Composite"     "Enable"
Endsection

Hibernate

[?DamyanIvanov] Hibernate worked for me just fine after I've set up a 256M dedicated SWAP partition. Perhaps the same is possible using swap files too. The only glitch is that I have to quit memory-hungry programs like Iceweasel before attempting hibernate, as otherwise the swap space is not enough. To hibernate, run s2disk as root (from the uswsusp package). If you use gnome-power-manager you can just press the power button (but remember to disable the button action in /etc/acpi/actions/power.sh installed by debian-eeepc-scripts to avoid double prompts).

Troubleshooting

Ethernet does not come up

One problem you may come across is the ethernet not becoming active. This is a bug with the chipset for when you install. To fix this, temporarily enable PXE/netboot in the BIOS. You may not come across this problem, but you can enable it and disable it at any time without problem. The problem will be gone as soon as you have installed so you may disable PXE in the BIOS after that.


  • FixMe: Can someone please confirm this is still a problem sometimes? If there are no further reports of this, this should be removed from the wiki or at least moved out of this document. It is possible the updated atl2 fixes this.


  • I did not notice this when installing today. I am using unstable's 2.6.24 kernel, along with the matching atl2-modules package from unstable.


  • [BenArmstrong] So does the problem still exist in Lenny with 2.6.22?

Shutting down fails

There is an issue surrounding shutting down. The system halts, but the fan continues to run and the wifi light stays on. The reason is the sound module doesn't close correctly, but there is a fix!

  • Edit /etc/init.d/halt as root with your favourite text editor and add the line "rmmod snd_hda_intel"

Then it will poweroff correctly!

Microphone does not work

If the microphone does not work by default. The following fixes that.

  • Edit /etc/modprobe.d/alsa-base and add the line “options snd-hda-intel model=3stack-dig”


  • I did not experience this with unstable's 2.6.24 kernel--can anyone else confirm whether it has been fixed?

Screen resolution not large enough for some apps

Because the resolution screen is 800x480. Many applications exceed the screen. The best example is the Gnome application Evolution. See ["DebianEeePC/TipsAndTricks"]