This is an old revision of the document!
Guía de instalación
La Guía de instalación del live-CD de Hyperbola (que también se puede ejecutar desde una unidad de memoria USB) está destinada a ayudar a los usuarios experimentados de GNU/Linux a instalar Hyperbola desde el sistema live iniciado con la imagen de instalación oficial. Esta página asume un alto nivel de experiencia con los sistemas y utilidades GNU/Linux, especialmente la línea de comandos. Si desea una guía más detallada, paso a paso a través del proceso de instalación, consulte la Guía para principiantes. Antes de comenzar, le recomendamos que consulte nuestras FAQ, Arch FAQ, y emplee el man command
para leer la página del manual de cualquier comando con el que no estén familiarizados. La wiki de Hyperbola (conocida como HyperWiki), así como la ArchWiki, debe ser la fuente principal de información y su primer recurso durante la resolución de problemas.
Descarga
Descargue la nueva imagen de Hyperbola ISO desde la página de descarga.
- En lugar de seis imágenes diferentes, solo proporcionamos una sola imagen que puede iniciarse en un sistema i686 y x86_64 para instalar Hyperbola GNU/Linux-libre a través de la red.
- Las imágenes de instalación están firmadas y se recomienda verificar su firma antes de usarlas. En Hyperbola, esto se puede hacer usando pacman-key -v <iso-file>.sig
- La imagen se puede grabar en un CD, se puede montar como un archivo ISO o se puede escribir directamente en un USB stick utilizando una utilidad como dd. Esto destinado solo para nuevas instalaciones; un sistema existente Hyperbola GNU/Linux-libre siempre se puede actualizar con pacman -Syu.
Usuarios de baja visión o deficientes visuales.
Existe una ISO llamada HyperTalking que es un CD de instalación derivado, basado en TalkingArch y una copia de la Hyperbola ISO modificada para incluir la salida de voz y braille.
Escribiendo una imagen ISO de Hyperbola en una unidad USB
# dd if=''[iso file]'' of=''[usb device file]'' bs=1M && sync
[iso file]
es la ruta del archivo ISO image.
[usb device file]
es la ruta del archivo dispositivo USB. dmesg o lsblk –fs puede usarse para saber la ruta. A menudo es similar a los nombres de los dispositivos de almacenamiento como discos duros y SSD, por ejemplo. /dev/sdb 'Es muy importante usar el valor correcto
' para evitar sobrescribir otros dispositivos de almacenamiento.
Instalación
Diseño del teclado
Para muchos países y tipos de teclado, ya están disponibles los mapas de teclas apropiados, y un comando como loadkeys uk puede hacer lo que desee. Puede encontrar más archivos de mapas de teclas disponibles en /usr/share/kbd/keymaps/ (puede omitir la ruta del mapa de teclado y la extensión de archivo usando loadkeys).
Soporte braille
HyperTalking incluye brltty, para aquellos que poseen pantallas braille. El paquete brltty disponible en el CD HyperTalking se compiló con la menor cantidad de dependencias posible. Si desea utilizar braille, deberá proporcionar el parámetro brltty en el indicador de inicio. Alternativamente, puede iniciar brltty desde el shell, una vez que el sistema se haya iniciado.
El parámetro brltty boot-time consta de tres campos separados por comas: driver, device y table. El primero es el controlador para su pantalla, el segundo es el nombre del archivo del dispositivo y el tercero es una ruta relativa a una tabla de traducción. Puede usar “auto” para especificar que el controlador debe detectarse automáticamente. Lo invito a leer la documentación de brltty para una explicación más completa del programa.
Por ejemplo, suponga que tiene un dispositivo conectado a /dev/ttyS0, el primer puerto serie. Usted desea utilizar la tabla de texto en inglés de EE.UU. y el controlador debe ser detectado automáticamente. Esto es lo que debe escribir en el indicador de arranque:
arch32 brltty=auto,ttyS0,en_US
Una vez que se esté ejecutando brltty, es posible que desee deshabilitar el habla. Puede hacerlo a través de la tecla “print screen”, también conocida como sysrq. En mi teclado qwerty, esa tecla está ubicada directamente sobre la tecla de inserción, entre F12 y el bloqueo de desplazamiento.
Particionado de discos
Consulte partitioning para obtener más información.
Recuerde crear cualquier dispositivo de bloque apilado como LVM, LUKS, o RAID.
Format the partitions
See File Systems for details.
If you are using (U)EFI you will most probably need another partition to host the UEFI System partition. Read Create an UEFI System Partition in GNU/Linux.
Mount the partitions
We now must mount the root partition on /mnt. You should also create directories for and mount any other partitions (/mnt/boot, /mnt/home, …) and mount your swap partition if you want them to be detected by genfstab.
Connect to the Internet
A DHCP service is already enabled for all available devices. If you need to setup a static IP or use management tools, you should stop this service first:
# rc-service dhcpcd stop
For more information read Configuring Network.
The dhcpcd network daemon starts automatically during boot and it will attempt to start a wired connection. Try to ping a server to see if a connection was established. For example, gnu.org:
# ping -c 3 gnu.org PING gnu.org (208.118.235.148) 56(84) bytes of data. 64 bytes from wildebeest.gnu.org (208.118.235.148): icmp_seq=1 ttl=47 time=183 ms 64 bytes from wildebeest.gnu.org (208.118.235.148): icmp_seq=2 ttl=47 time=168 ms 64 bytes from wildebeest.gnu.org (208.118.235.148): icmp_seq=3 ttl=47 time=183 ms --- gnu.org ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 168.131/178.357/183.914/7.248 ms
If you get a ping: unknown host error, first check if there is an issue with your cable or wireless signal strength. If not, you will need to set up the network manually, as explained below.
Wired
Follow this procedure if you need to set up a wired connection via a static IP address.
First, disable the dhcpcd service which was started automatically at boot:
# rc-service dhcpcd stop
Identify the name of your Ethernet interface.
# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 00:11:25:31:69:20 brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000 link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff
In this example, the Ethernet interface is enp2s0f0. If you are unsure, your Ethernet interface is likely to start with the letter “e”, and unlikely to be “lo” or start with the letter “w”. You can also use iwconfig and see which interfaces are not wireless:
# iwconfig enp2s0f0 no wireless extensions. wlp3s0 IEEE 802.11bgn ESSID:"NETGEAR97" Mode:Managed Frequency:2.427 GHz Access Point: 2C:B0:5D:9C:72:BF Bit Rate=65 Mb/s Tx-Power=16 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=61/70 Signal level=-49 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:430 Missed beacon:0 lo no wireless extensions.
In this example, neither enp2s0f0 nor the loopback device have wireless extensions, meaning enp2s0f0 is our Ethernet interface.
You also need to know these settings:
- Static IP address.
- Subnet mask.
- Gateway's IP address.
- Name servers' (DNS) IP addresses.
- Domain name (unless you are on a local LAN, in which case you can make it up).
Activate the connected Ethernet interface (e.g. enp2s0f0):
# ip link set enp2s0f0 up
Add the address:
# ip addr add ip_address/subnetmask dev interface_name
For example:
# ip addr add 192.168.1.2/24 dev enp2s0f0
For more options, run man ip.
Add your gateway like this, substituting your own gateway's IP address:
# ip route add default via ip_address
For example:
# ip route add default via 192.168.1.1
Edit resolv.conf, substituting your name servers' IP addresses and your local domain name:
# nano /etc/resolv.conf
nameserver 61.23.173.5
nameserver 61.95.849.8
search example.com
You should now have a working network connection. If you do not, check the detailed Network Configuration page.
Wireless
Follow this procedure if you need wireless connectivity (Wi-Fi) during the installation process.
First, identify the name of your wireless interface.
# iw dev phy#0 Interface wlp3s0 ifindex 3 wdev 0x1 addr 00:21:6a:5e:52:bc type managed
In this example, wlp3s0 is the available wireless interface. If you are unsure, your wireless interface is likely to start with the letter “w”, and unlikely to be “lo” or start with the letter “e”.
Bring the interface up with:
# ip link set wlp3s0 up
SIOCSIFFLAGS: No such file or directory
Then, your wireless chipset could need a non-free firmware to function. This is not supported on Hyperbola. Please see Wireless Setup if you are unsure if this is the true for your particular chipset.
Next, use iw dev wlp3s0 scan | grep SSID to scan for available networks, then connect to a network with:
# wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "ssid" "psk")
You need to replace ssid with the name of your network (e.g. “Linksys etc…”) and psk with your wireless password, leaving the quotes around the network name and password.
Finally, you have to give your interface an IP address. This can be set manually or using the dhcp:
# dhcpcd wlp3s0
If that does not work, issue the following commands:
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf
# wpa_passphrase <ssid> <passphrase> >> /etc/wpa_supplicant.conf
# ip link set <interface> up # May not be needed as dhcpcd should bring it up but may be needed for wpa_supplicant.
# wpa_supplicant -B -D nl80211 -c /foobar.conf -i <interface name>
# dhcpcd -A <interface name>
ADSL with PPPoE/PPPoA
Follow this procedure if you need ADSL with PPPoE/PPPoA during the installation process.
First, identify the name of your Ethernet interface.
# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 00:11:25:31:69:20 brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000 link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff
In this example, the Ethernet interface is enp2s0f0.
Second, create the PPP net script and the net script for the Ethernet interface to be used by PPP:
# ln -s /etc/init.d/net.lo /etc/init.d/net.ppp0
# ln -s /etc/init.d/net.lo /etc/init.d/net.enp2s0f0
Now we need to configure /etc/conf.d/net.
# nano /etc/conf.d/net config_eth0=null (Specify the ethernet interface) config_ppp0="ppp" link_ppp0="enp2s0f0" (Specify the ethernet interface) plugins_ppp0="pppoe" username_ppp0='user' password_ppp0='password' pppd_ppp0=" noauth defaultroute usepeerdns holdoff 3 child-timeout 60 lcp-echo-interval 15 lcp-echo-failure 3 noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp" rc_need_ppp0="net.enp2s0f0"
Now that the interface is configured, we can start it using the following commands:
rc-service net.ppp0 start
Behind a proxy server
If you are behind a proxy server, you will need to export the http_proxy and ftp_proxy environment variables. See Proxy settings for more information.
Verification of package signatures
New packager keys are necessary by default to install Hyperbola from current ISOs. Because changes in existing keys might happen since the ISO release, it is recommended, if not mandatory, to update the keys before attempting an install.
To check that your computer has the correct time, enter date in the terminal.
# date
If the date is incorrect, you will need to manually set the correct time.
# date MMDDhhmm[[CC]YY][.ss]
where MM is the month, DD the day, hh the hour, mm the minutes, CC the century, YY the year and .SS the seconds of current time, the seconds can be omitted (and then also the dot before them should be omitted), the year can also be submitted or just the century. for instance if the current time is 32 seconds and 44 minutes past 18 (6 pm) on the 13th November 2013. Then the command would be:
# date 111318442013.32
Once the date is correct, we need to initialize the gnupg directory and update pacman's keys.
# pacman-key --init
# mount -o remount,size=100M,noatime /etc/pacman.d/gnupg
# pacman-key --populate hyperbola arch
# pacman-key --refresh-keys
If you get GPG errors updating those packages, you can try running these commands to start over:
# rm -r /etc/pacman.d/gnupg/*
# pacman-key --init
# pacman-key --populate hyperbola arch
# pacman-key --refresh-keys
If you get an error related to dirmngr, you can get rid of it with:
# mkdir /root/.gnupg && chmod go-rx /root/.gnupg && touch /root/.gnupg/dirmngr_ldapservers.conf
For the time being, running the previous command might also be needed in the newly installed system.
Install the base system
Before installing, you may want to edit /etc/pacman.d/mirrorlist such that your preferred mirror is first. This copy of the mirrorlist will be installed on your new system by pacstrap as well, so it's worth getting it right.
Install the base system using pacstrap:
# pacstrap /mnt
You can install additional packages passing base and the names of these packages as arguments after the root directory of the new installation (all packages from the base group are installed if no package is specified).
If you have a btrfs root, you probably want to install also btrfs-progs.
# pacstrap /mnt
Then, you can try to fix them with:
# rm -r /etc/pacman.d/gnupg/*
# pacman-key --init
# pacman-key --populate hyperbola arch
# pacman-key --refresh-keys
Install and configure a bootloader
GRUB
- For BIOS and EFI:
# pacstrap /mnt grub
- Install GRUB after chrooting (refer to the Configure the system section).
See GRUB for further details.
Syslinux
# pacstrap /mnt syslinux
See Syslinux for further details.
Install wireless tools
If your wireless network is WPA protected, you'll need wpa_supplicant to connect to it:
# pacstrap /mnt wpa_supplicant
Configure the system
Generate a fstab with the following command (if you prefer to use UUIDs or labels, add the -U or -L option, respectively):
# genfstab -p /mnt >> /mnt/etc/fstab
Next we chroot into our newly installed system:
# arch-chroot /mnt
- Write your hostname to /etc/hostname
# echo myhostname > /etc/hostname
- Symlink /etc/localtime to /usr/share/zoneinfo/Zone/SubZone. Replace Zone and Subzone to your liking. For example:
# ln -s /usr/share/zoneinfo/Europe/Athens /etc/localtime
- Set locale preferences in /etc/locale.conf
- Add console keymap and font preferences in /etc/conf.d/keymaps
- Uncomment the selected locale in /etc/locale.gen and generate it with locale-gen
- Set a root password with passwd
- Add your user to the relevant group such as:
# gpasswd -a YourActualUserName video
- Configure /etc/mkinitcpio.conf as needed (see mkinitcpio) and create an initial RAM disk with:
# mkinitcpio -p linux-libre-lts
- If you want to install GRUB for the (U)EFI mode, you will need to make sure that:
- The computer booted in (U)EFI mode (if /sys/firmware/efi exist, then it booted in (U)EFI mode)
- The efivars module is loaded. (modprobe efivars will load it)
- To configure the bootloader, you have to install it and generate the file grub.cfg:
# grub-install /dev/sdX
grub-install --no-bootsector /dev/sdX
# grub-mkconfig -o /boot/grub/grub.cfg
- Configure the network again for newly installed environment. See Network Configuration and Wireless Setup.
Configure speech support (for blind and visually impaired users)
If you are using HyperTalking and need start speech support when you boot the system, you will need to do:
- Install espeakup and alsa-utils.
- Enable the espeakup service by executing:
# rc-update add espeakup default
- Save the state of the sound card, so that it will be retrieved on reboot:
# alsactl store
Unmount and reboot
If you are still in the chroot environment type exit or press Ctrl+D in order to exit. Earlier we mounted the partitions under /mnt. In this step we will unmount them:
# umount /mnt/{boot,home,}
Now reboot and then login into the new system with the root account.
Configure pacman
Edit /etc/pacman.conf and configure pacman's options, also enabling the repositories you need.
See Pacman and Repositories for details.
Update the system
At this point you should update your system.
See Upgrading packages for instructions.
Add an user
Finally, add a normal user as described in User management.
Service management
Since Hyperbola removed entire systemd support, we suggest you read about OpenRC which is our main default init system.
Conclusion
Your new Hyperbola GNU/Linux-libre base system is now a functional GNU/Linux environment.
Acknowledgement
This wiki article is based on ArchWiki, GentooWiki and ParabolaWiki. We may have removed non-FSDG bits from it.