Alpine Linux - User contributions [en]

https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&feedformat=atom&user=Legale Alpine Linux - User contributions [en] 2026-05-02T06:17:40Z User contributions MediaWiki 1.40.0 https://wiki.alpinelinux.org/w/index.php?title=Finding_the_fastest_mirror&diff=31385 Finding the fastest mirror 2025-11-04T10:39:25Z

<p>Legale: update mirrors url</p> <hr /> <div>After you install Alpine, you may be wondering how do I figure out the fastest mirror again?<br /> <br /> You could run <code>setup-apkrepos</code> again.<br /> <br /> The following script shows the closest mirror for a single ping, which might not be accurate:<br /> <br /> {{Cat|/home/user/fastestmirror|<nowiki><br /> data=""<br /> for s in $(wget -qO- https://mirrors.alpinelinux.org/mirrors.txt); do<br /> t=$(time -f "%E" wget -q $s/MIRRORS.txt -O /dev/null 2>&1)<br /> echo "$s was $t"<br /> data="$data$t $s\n"<br /> done<br /> <br /> echo "===RESULTS==="<br /> <br /> echo -e $data | sort<br /> </nowiki>}}<br /> <br /> == See also ==<br /> <br /> * [[How to setup a Alpine Linux mirror]]<br /> <br /> [[Category:Package Manager]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Setting_up_a_Samba_server&diff=21592 Setting up a Samba server 2022-02-09T12:57:44Z

<p>Legale: /* Create smb.conf */</p> <hr /> <div>= Installation =<br /> Install packages:<br /> {{Cmd|# apk add samba}}<br /> <br /> = Create a share directory =<br /> This will be the directory that's shared to clients. You can create as many of these as you wish.<br /> {{Cmd|# mkdir /media/storage}}<br /> {{Cmd|# chmod 0777 /media/storage}}<br /> <br /> = Create smb.conf =<br /> Alpine provides an example configuration file located at /etc/samba/smb.conf. The following is a simple example to get you up and running.<br /> {{cat|/etc/samba/smb.conf|# /etc/samba/smb.conf<br /> <nowiki><br /> [global]<br /> #to allow symlinks from everywhere<br /> allow insecure wide links = yes <br /> workgroup = WORKGROUP<br /> dos charset = cp866<br /> unix charset = utf-8<br /> force user = username<br /> <br /> [storage]<br /> # to follow symlinks<br /> follow symlinks = yes <br /> # to allow symlinks from outside<br /> wide links = yes <br /> browseable = yes<br /> writeable = yes<br /> path = /media/storage<br /> </nowiki><br /> }}<br /> {{note|For each directory share, you'll need to add a subsection to '''smb.conf'''}}<br /> <br /> = Create a system user and Samba user =<br /> Create a user on the system. Create a Samba user. Give both users the same password.<br /> {{Cmd|# adduser username}}<br /> {{Cmd|# smbpasswd -a username}}<br /> <br /> = Configure the Samba service =<br /> Run these two commands to start the service on boot and to start the service right now.<br /> {{Cmd|# rc-update add samba}}<br /> {{Cmd|# rc-service samba start}}<br /> <br /> [[Category:Server]]<br /> [[Category:Printers]]<br /> [[Category:Authentication]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Setting_up_a_Samba_server&diff=21591 Setting up a Samba server 2022-02-09T12:56:35Z

<p>Legale: /* Create smb.conf */</p> <hr /> <div>= Installation =<br /> Install packages:<br /> {{Cmd|# apk add samba}}<br /> <br /> = Create a share directory =<br /> This will be the directory that's shared to clients. You can create as many of these as you wish.<br /> {{Cmd|# mkdir /media/storage}}<br /> {{Cmd|# chmod 0777 /media/storage}}<br /> <br /> = Create smb.conf =<br /> Alpine provides an example configuration file located at /etc/samba/smb.conf. The following is a simple example to get you up and running.<br /> {{cat|/etc/samba/smb.conf|# /etc/samba/smb.conf<br /> <nowiki><br /> [global]<br /> #to allow symlinks from everywhere<br /> allow insecure wide links = yes <br /> workgroup = WORKGROUP<br /> dos charset = cp850<br /> unix charset = ISO-8859-1<br /> force user = username<br /> <br /> [storage]<br /> # to follow symlinks<br /> follow symlinks = yes <br /> # to allow symlinks from outside<br /> wide links = yes <br /> browseable = yes<br /> writeable = yes<br /> path = /media/storage<br /> </nowiki><br /> }}<br /> {{note|For each directory share, you'll need to add a subsection to '''smb.conf'''}}<br /> <br /> = Create a system user and Samba user =<br /> Create a user on the system. Create a Samba user. Give both users the same password.<br /> {{Cmd|# adduser username}}<br /> {{Cmd|# smbpasswd -a username}}<br /> <br /> = Configure the Samba service =<br /> Run these two commands to start the service on boot and to start the service right now.<br /> {{Cmd|# rc-update add samba}}<br /> {{Cmd|# rc-service samba start}}<br /> <br /> [[Category:Server]]<br /> [[Category:Printers]]<br /> [[Category:Authentication]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Setting_up_a_Samba_server&diff=21590 Setting up a Samba server 2022-02-09T12:51:08Z

<p>Legale: /* Create smb.conf */</p> <hr /> <div>= Installation =<br /> Install packages:<br /> {{Cmd|# apk add samba}}<br /> <br /> = Create a share directory =<br /> This will be the directory that's shared to clients. You can create as many of these as you wish.<br /> {{Cmd|# mkdir /media/storage}}<br /> {{Cmd|# chmod 0777 /media/storage}}<br /> <br /> = Create smb.conf =<br /> Alpine provides an example configuration file located at /etc/samba/smb.conf. The following is a simple example to get you up and running.<br /> {{cat|/etc/samba/smb.conf|# /etc/samba/smb.conf<br /> <nowiki><br /> [global]<br /> allow insecure wide links = yes #to allow symlinks from everywhere<br /> workgroup = WORKGROUP<br /> dos charset = cp850<br /> unix charset = ISO-8859-1<br /> force user = username<br /> <br /> [storage]<br /> follow symlinks = yes # to follow symlinks<br /> wide links = yes # to allow symlinks from outside<br /> browseable = yes<br /> writeable = yes<br /> path = /media/storage<br /> </nowiki><br /> }}<br /> {{note|For each directory share, you'll need to add a subsection to '''smb.conf'''}}<br /> <br /> = Create a system user and Samba user =<br /> Create a user on the system. Create a Samba user. Give both users the same password.<br /> {{Cmd|# adduser username}}<br /> {{Cmd|# smbpasswd -a username}}<br /> <br /> = Configure the Samba service =<br /> Run these two commands to start the service on boot and to start the service right now.<br /> {{Cmd|# rc-update add samba}}<br /> {{Cmd|# rc-service samba start}}<br /> <br /> [[Category:Server]]<br /> [[Category:Printers]]<br /> [[Category:Authentication]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Openbox&diff=20389 Openbox 2021-11-26T20:38:30Z

<p>Legale: </p> <hr /> <div>= Initial setup =<br /> Start by booting Alpine (see [[Installation|these]] instructions on how to do that)<BR><br /> <br /> = Enable Community Repository =<br /> We need the Community Repository available for access to the OpenBox packages. Instructions are available on the [[Enable_Community_Repository|Enable Community Repository]] page.<br /> <br /> = Install packages =<br /> Install openbox, xterm, and terminus font.<BR><br /> <br /> {{Cmd|# apk add openbox xterm terminus-font}}<br /> <br /> xterm is needed so you have a way to access the terminal in X. There are alternatives but this is the classic.<br /> Terminus is needed because without any fonts, you will not be able to see any text in OpenBox.<br /> <br /> = Configure xorg-server =<br /> On most systems, xorg should be able to autodetect all devices. However, you can still configure xorg-server manually by launching:<br /> {{Cmd|# setup-xorg-base}}<br /> <br /> = Configure user =<br /> To make Xorg work as normal user you need to add user to these groups: video, input.<br /> {{Cmd|# addgroup <username> input}}<br /> {{Cmd|# addgroup <username> video}}<br /> <br /> == acpid ==<br /> If you installed your Alpine Linux as a VirtualBox or VMWare guest, you might find it handy to be able execute an ACPI shutdown.<BR><br /> {{Cmd|# rc-update add acpid}}<br /> <br /> = Set openbox as the default WM =<br /> {{Cmd|$ echo 'exec openbox-session' >> ~/.xinitrc}}<br /> <br /> = Copy the config files to your home folder = <br /> {{Cmd|$ mkdir /home/<newuser>/.config}}<br /> {{Cmd|$ cp -r /etc/xdg/openbox ~/.config}}<br /> <br /> '''Note:''' The default configuration is minimal and most menu options won't work unless you customize and/or install additional packages. More information is available in the [http://openbox.org/wiki/Help:Configuration OpenBox configuration documentation].<br /> <br /> = Edit openbox settings =<br /> You can now edit the openbox settings for your user by editing the files located in<br /> {{Cmd|~/.config/openbox}}<br /> <br /> The OpenBox configuration details can he studied on the [http://openbox.org/wiki/Help:Contents#Configuration OpenBox wiki]. <br /> <br /> = Start your X! =<br /> {{Cmd|$ startx}}<br /> <br /> '''Note:''' The default OpenBox menu (right click on desktop) will have a lot of options that won't work because we didnt install anything else! Luckily XTerm will work if you added the package in the first step, and you can use that to add additional packages.<br /> <br /> The default configuration is minimal and most menu options won't work unless you customize and/or install additional packages. More information is available in the [http://openbox.org/wiki/Help:Configuration OpenBox configuration documentation].</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Openbox&diff=20388 Openbox 2021-11-26T20:21:06Z

<p>Legale: /* Set openbox as the default WM */</p> <hr /> <div>= Initial setup =<br /> Start by booting Alpine (see [[Installation|these]] instructions on how to do that)<BR><br /> <br /> = Enable Community Repository =<br /> We need the Community Repository available for access to the OpenBox packages. Instructions are available on the [[Enable_Community_Repository|Enable Community Repository]] page.<br /> <br /> = Install packages =<br /> Install openbox, xterm, and terminus font.<BR><br /> <br /> {{Cmd|# apk add openbox xterm terminus-font}}<br /> <br /> xterm is needed so you have a way to access the terminal in X. There are alternatives but this is the classic.<br /> Terminus is needed because without any fonts, you will not be able to see any text in OpenBox.<br /> <br /> = Configure xorg-server =<br /> On most systems, xorg should be able to autodetect all devices. However, you can still configure xorg-server manually by launching:<br /> {{Cmd|# setup-xorg-base}}<br /> <br /> == acpid ==<br /> If you installed your Alpine Linux as a VirtualBox or VMWare guest, you might find it handy to be able execute an ACPI shutdown.<BR><br /> {{Cmd|# rc-update add acpid}}<br /> <br /> = Set openbox as the default WM =<br /> {{Cmd|$ echo 'exec openbox-session' >> ~/.xinitrc}}<br /> <br /> = Copy the config files to your home folder = <br /> {{Cmd|$ mkdir /home/<newuser>/.config}}<br /> {{Cmd|$ cp -r /etc/xdg/openbox ~/.config}}<br /> <br /> '''Note:''' The default configuration is minimal and most menu options won't work unless you customize and/or install additional packages. More information is available in the [http://openbox.org/wiki/Help:Configuration OpenBox configuration documentation].<br /> <br /> = Edit openbox settings =<br /> You can now edit the openbox settings for your user by editing the files located in<br /> {{Cmd|~/.config/openbox}}<br /> <br /> The OpenBox configuration details can he studied on the [http://openbox.org/wiki/Help:Contents#Configuration OpenBox wiki]. <br /> <br /> = Start your X! =<br /> {{Cmd|$ startx}}<br /> <br /> '''Note:''' The default OpenBox menu (right click on desktop) will have a lot of options that won't work because we didnt install anything else! Luckily XTerm will work if you added the package in the first step, and you can use that to add additional packages.<br /> <br /> The default configuration is minimal and most menu options won't work unless you customize and/or install additional packages. More information is available in the [http://openbox.org/wiki/Help:Configuration OpenBox configuration documentation].</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Raspberry_Pi&diff=20180 Raspberry Pi 2021-10-07T18:51:58Z

<p>Legale: /* Loopback image with overlayfs */</p> <hr /> <div>{{warning | 11 Feb 2021 - There is currently a known bug upstream <br />[https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label] }}<br /> <br /> {{TOC right}}<br /> <br /> This tutorial will help you install Alpine Linux on your Raspberry Pi.<br /> <br /> == Preparation ==<br /> <br /> # [http://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. You should be safe using the '''armhf''' build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The '''armv7''' build is compatible with Raspberry Pi 2 Model B. The '''aarch64''' build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.<br /> # [[Create a Bootable USB#Format USB stick|Create a bootable FAT32 partition on your SD card.]] The partition type should be <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.) You can use a partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks] or [http://linux.die.net/man/8/fdisk fdisk].<br /> # Create a filesystem on the partition with <code>mkdosfs -F 32 /dev/sdX1</code> (Replace sdX1 with the correct reference to the partition you just created.)<br /> # Mount the partition and extract the tarball contents onto it.<br /> <br /> Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:<br /> * To enable audio: <code>dtparam=audio=on</code><br /> * If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code><br /> <br /> Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].<br /> <br /> == Installation ==<br /> <br /> Alpine Linux will be installed in [[Installation#Installation_Handbook|diskless mode]], hence you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots.<br /> <br /> For users who will be using their Raspberry Pi in scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. <br /> <br /> However, if you:<br /> * Expect there will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)<br /> * Need logs to persist after reboot<br /> * Plan to install packages which consume more space than can be loaded into RAM<br /> * Want to install kernel modules (such as ZFS or Wireguard)<br /> <br /> Then you may be better served by a [[Classic install or sys mode on Raspberry Pi|sys-mode installation]]. <br /> <br /> Follow these steps to install Alpine Linux in Diskless Mode:<br /> <br /> # Insert the SD card into the Raspberry Pi and power it on<br /> # Login into the Alpine system as root. Leave the password empty.<br /> # Type <code>setup-alpine</code><br /> # Once the installation is complete, commit the changes by typing <code>lbu commit -d</code><br /> <br /> Type <code>reboot</code> to verify that the installation was indeed successful.<br /> <br /> == Post Installation ==<br /> <br /> === Update the System ===<br /> <br /> After installation, make sure your system is up-to-date:<br /> <br /> {{cmd|apk update<br /> apk upgrade}}<br /> <br /> Don't forget to save the changes:<br /> <br /> {{cmd|lbu commit -d}}<br /> <br /> Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].<br /> <br /> === Clock-related error messages ===<br /> <br /> During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have<br /> a hardware clock, thus you need to disable the hwclock daemon and enable swclock:<br /> <br /> {{cmd|rc-update add swclock boot # enable the software clock<br /> rc-update del hwclock boot # disable the hardware clock}}<br /> <br /> Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a<br /> [https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a<br /> NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following<br /> command:<br /> <br /> {{cmd|setup-ntp}}<br /> <br /> The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is<br /> installed and running:<br /> <br /> {{cmd|lbu commit -d<br /> reboot}}<br /> <br /> After reboot, make sure the <code>date</code> command outputs the correct date and time.<br /> <br /> === WiFi on boot ===<br /> If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.<br /> You will need to start up a service to automatically connect to the wireless access point.<br /> # Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.<br /> # Run it manually with <code>/etc/init.d/wpa_supplicant start</code>.<br /> <br /> === Enable OpenGL (Raspberry Pi 3/4) ===<br /> Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):<br /> <br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount}}<br /> <br /> Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:<br /> <br /> gpu_mem=128<br /> # Raspberry Pi 3:<br /> dtoverlay=vc4-kms-v3d<br /> # Raspberry Pi 4:<br /> dtoverlay=vc4-fkms-v3d<br /> <br /> 256MB (and more on the Raspberry Pi 4) <code>gpu_mem</code> is also possible.<br /> <br /> Install the Mesa drivers:<br /> <br /> {{cmd|<nowiki># Raspberry Pi 3:<br /> apk add mesa-dri-vc4<br /> # Raspberry Pi 4:<br /> apk add mesa-dri-gallium</nowiki>}}<br /> <br /> Then reboot:<br /> <br /> {{cmd|lbu_commit -d; reboot}}<br /> <br /> === WiFi drivers ===<br /> As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.<br /> Use the ethernet interface to download the required packages:<br /> <br /> {{cmd|apk add linux-firmware-cypress}}<br /> <br /> And reboot.<br /> <br /> == Persistent storage ==<br /> === Loopback image with overlayfs ===<br /> <br /> When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.<br /> <br /> First, make the SD card writable again and change fstab to always do so:<br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount<br /> sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}<br /> <br /> Create the loop-back file, this example is 1 GB:<br /> <br /> {{cmd|dd if&#61;/dev/zero of&#61;/media/mmcblk0p1/persist.img bs&#61;1024 count&#61;0 seek&#61;1048576}}<br /> <br /> Install the ext utilities:<br /> <br /> {{cmd|apk add e2fsprogs}}<br /> <br /> Format the loop-back file:<br /> <br /> {{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}<br /> <br /> Mount the storage: <br /> <br /> {{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0" >> /etc/fstab<br /> mkdir /media/persist <br /> mount -a}}<br /> <br /> Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else. <br /> {{Warning|Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay must use its own workdir.}}<br /> <br /> <br /> {{cmd|mkdir /media/persist/usr <br /> mkdir /media/persist/.work_usr <br /> echo "overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0" >> /etc/fstab <br /> mount -a}}<br /> <br /> Your /etc/fstab should look something like this:<br /> {{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0<br /> /dev/usbdisk /media/usb vfat noauto,ro 0 0<br /> /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask&#61;0022,dmask&#61;0022,errors&#61;remount-ro 0 0<br /> /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0<br /> overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0}}<br /> <br /> Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)<br /> {{cmd|lbu_commit -d}}<br /> <br /> Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.<br /> <br /> If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`.<br /> <br /> If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent.<br /> <br /> === Traditional disk-based (sys) installation ===<br /> {{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}<br /> <br /> It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.<br /> <br /> Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:<br /> <br /> {{cmd|apk add e2fsprogs<br /> mkfs.ext4 /dev/mmcblk0p2}}<br /> <br /> Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.<br /> The Raspberry Pi doesn't need them to boot.<br /> <br /> {{cmd|<nowiki>mkdir /stage<br /> mount /dev/mmcblk0p2 /stage<br /> setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage<br /> # (ignore errors about syslinux/extlinux)</nowiki>}}<br /> <br /> Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:<br /> <br /> {{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}<br /> <br /> Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:<br /> <br /> {{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1<br /> sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}<br /> <br /> You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.<br /> <br /> N.B. <b>the contents of /boot will be ignored when the Pi boots</b>. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,<br /> copying the files to boot partition manually, is not needed.<br /> <br /> {{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}<br /> <br /> === Persistent Installation on Raspberry Pi 3 ===<br /> See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084<br /> <br /> === Persistent Installation on Raspberry Pi 4 ===<br /> As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.<br /> <br /> == Troubleshooting ==<br /> <br /> === Long boot time when running headless ===<br /> <br /> If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.<br /> <br /> If this is the case, simply plugging in any USB device should work around this issue.<br /> <br /> '''Alternatively''', installing haveged, the random numbers generator, would speed up the process: <br /> <br /> apk update <br /> apk add haveged<br /> rc-update add haveged boot<br /> lbu commit -d<br /> service haveged start<br /> <br /> (Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3)<br /> <br /> === apk indicating 'No space left on device' ===<br /> <br /> Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.<br /> <br /> === Wireless support with older Alpine images ===<br /> <br /> If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.<br /> (Replace /mnt/sdcard with the correct mount point.)<br /> <br /> git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git<br /> cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm<br /> <br /> == See Also ==<br /> <br /> * [[Classic install or sys mode on Raspberry Pi]] - a variant.<br /> * [[Raspberry Pi - Headless Installation]]<br /> * [[Raspberry Pi 3 - Setting Up Bluetooth]]<br /> * [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]<br /> * [[Raspberry Pi 3 - Browser Client]]<br /> * [[Linux Router with VPN on a Raspberry Pi]]<br /> * [[Create a bootable SDHC from a Mac]]<br /> * Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]<br /> * [[Tutorials and Howtos#Raspberry Pi]]<br /> <br /> [[Category:Installation]]<br /> [[Category: Raspberry]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Raspberry_Pi&diff=20179 Raspberry Pi 2021-10-07T18:51:27Z

<p>Legale: /* Loopback image with overlayfs */</p> <hr /> <div>{{warning | 11 Feb 2021 - There is currently a known bug upstream <br />[https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label] }}<br /> <br /> {{TOC right}}<br /> <br /> This tutorial will help you install Alpine Linux on your Raspberry Pi.<br /> <br /> == Preparation ==<br /> <br /> # [http://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. You should be safe using the '''armhf''' build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The '''armv7''' build is compatible with Raspberry Pi 2 Model B. The '''aarch64''' build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.<br /> # [[Create a Bootable USB#Format USB stick|Create a bootable FAT32 partition on your SD card.]] The partition type should be <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.) You can use a partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks] or [http://linux.die.net/man/8/fdisk fdisk].<br /> # Create a filesystem on the partition with <code>mkdosfs -F 32 /dev/sdX1</code> (Replace sdX1 with the correct reference to the partition you just created.)<br /> # Mount the partition and extract the tarball contents onto it.<br /> <br /> Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:<br /> * To enable audio: <code>dtparam=audio=on</code><br /> * If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code><br /> <br /> Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].<br /> <br /> == Installation ==<br /> <br /> Alpine Linux will be installed in [[Installation#Installation_Handbook|diskless mode]], hence you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots.<br /> <br /> For users who will be using their Raspberry Pi in scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. <br /> <br /> However, if you:<br /> * Expect there will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)<br /> * Need logs to persist after reboot<br /> * Plan to install packages which consume more space than can be loaded into RAM<br /> * Want to install kernel modules (such as ZFS or Wireguard)<br /> <br /> Then you may be better served by a [[Classic install or sys mode on Raspberry Pi|sys-mode installation]]. <br /> <br /> Follow these steps to install Alpine Linux in Diskless Mode:<br /> <br /> # Insert the SD card into the Raspberry Pi and power it on<br /> # Login into the Alpine system as root. Leave the password empty.<br /> # Type <code>setup-alpine</code><br /> # Once the installation is complete, commit the changes by typing <code>lbu commit -d</code><br /> <br /> Type <code>reboot</code> to verify that the installation was indeed successful.<br /> <br /> == Post Installation ==<br /> <br /> === Update the System ===<br /> <br /> After installation, make sure your system is up-to-date:<br /> <br /> {{cmd|apk update<br /> apk upgrade}}<br /> <br /> Don't forget to save the changes:<br /> <br /> {{cmd|lbu commit -d}}<br /> <br /> Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].<br /> <br /> === Clock-related error messages ===<br /> <br /> During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have<br /> a hardware clock, thus you need to disable the hwclock daemon and enable swclock:<br /> <br /> {{cmd|rc-update add swclock boot # enable the software clock<br /> rc-update del hwclock boot # disable the hardware clock}}<br /> <br /> Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a<br /> [https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a<br /> NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following<br /> command:<br /> <br /> {{cmd|setup-ntp}}<br /> <br /> The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is<br /> installed and running:<br /> <br /> {{cmd|lbu commit -d<br /> reboot}}<br /> <br /> After reboot, make sure the <code>date</code> command outputs the correct date and time.<br /> <br /> === WiFi on boot ===<br /> If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.<br /> You will need to start up a service to automatically connect to the wireless access point.<br /> # Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.<br /> # Run it manually with <code>/etc/init.d/wpa_supplicant start</code>.<br /> <br /> === Enable OpenGL (Raspberry Pi 3/4) ===<br /> Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):<br /> <br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount}}<br /> <br /> Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:<br /> <br /> gpu_mem=128<br /> # Raspberry Pi 3:<br /> dtoverlay=vc4-kms-v3d<br /> # Raspberry Pi 4:<br /> dtoverlay=vc4-fkms-v3d<br /> <br /> 256MB (and more on the Raspberry Pi 4) <code>gpu_mem</code> is also possible.<br /> <br /> Install the Mesa drivers:<br /> <br /> {{cmd|<nowiki># Raspberry Pi 3:<br /> apk add mesa-dri-vc4<br /> # Raspberry Pi 4:<br /> apk add mesa-dri-gallium</nowiki>}}<br /> <br /> Then reboot:<br /> <br /> {{cmd|lbu_commit -d; reboot}}<br /> <br /> === WiFi drivers ===<br /> As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.<br /> Use the ethernet interface to download the required packages:<br /> <br /> {{cmd|apk add linux-firmware-cypress}}<br /> <br /> And reboot.<br /> <br /> == Persistent storage ==<br /> === Loopback image with overlayfs ===<br /> <br /> When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.<br /> <br /> First, make the SD card writable again and change fstab to always do so:<br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount<br /> sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}<br /> <br /> Create the loop-back file, this example is 1 GB:<br /> <br /> {{cmd|dd if&#61;/dev/zero of&#61;/media/mmcblk0p1/persist.img bs&#61;1024 count&#61;0 seek&#61;1048576}}<br /> <br /> Install the ext utilities:<br /> <br /> {{cmd|apk add e2fsprogs}}<br /> <br /> Format the loop-back file:<br /> <br /> {{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}<br /> <br /> Mount the storage: <br /> <br /> {{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0" >> /etc/fstab<br /> mkdir /media/persist <br /> mount -a}}<br /> <br /> Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else. <br /> {{Warning|Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay must use its own workdir}}<br /> <br /> <br /> {{cmd|mkdir /media/persist/usr <br /> mkdir /media/persist/.work_usr <br /> echo "overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0" >> /etc/fstab <br /> mount -a}}<br /> <br /> Your /etc/fstab should look something like this:<br /> {{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0<br /> /dev/usbdisk /media/usb vfat noauto,ro 0 0<br /> /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask&#61;0022,dmask&#61;0022,errors&#61;remount-ro 0 0<br /> /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0<br /> overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0}}<br /> <br /> Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)<br /> {{cmd|lbu_commit -d}}<br /> <br /> Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.<br /> <br /> If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`.<br /> <br /> If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent.<br /> <br /> === Traditional disk-based (sys) installation ===<br /> {{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}<br /> <br /> It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.<br /> <br /> Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:<br /> <br /> {{cmd|apk add e2fsprogs<br /> mkfs.ext4 /dev/mmcblk0p2}}<br /> <br /> Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.<br /> The Raspberry Pi doesn't need them to boot.<br /> <br /> {{cmd|<nowiki>mkdir /stage<br /> mount /dev/mmcblk0p2 /stage<br /> setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage<br /> # (ignore errors about syslinux/extlinux)</nowiki>}}<br /> <br /> Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:<br /> <br /> {{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}<br /> <br /> Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:<br /> <br /> {{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1<br /> sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}<br /> <br /> You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.<br /> <br /> N.B. <b>the contents of /boot will be ignored when the Pi boots</b>. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,<br /> copying the files to boot partition manually, is not needed.<br /> <br /> {{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}<br /> <br /> === Persistent Installation on Raspberry Pi 3 ===<br /> See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084<br /> <br /> === Persistent Installation on Raspberry Pi 4 ===<br /> As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.<br /> <br /> == Troubleshooting ==<br /> <br /> === Long boot time when running headless ===<br /> <br /> If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.<br /> <br /> If this is the case, simply plugging in any USB device should work around this issue.<br /> <br /> '''Alternatively''', installing haveged, the random numbers generator, would speed up the process: <br /> <br /> apk update <br /> apk add haveged<br /> rc-update add haveged boot<br /> lbu commit -d<br /> service haveged start<br /> <br /> (Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3)<br /> <br /> === apk indicating 'No space left on device' ===<br /> <br /> Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.<br /> <br /> === Wireless support with older Alpine images ===<br /> <br /> If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.<br /> (Replace /mnt/sdcard with the correct mount point.)<br /> <br /> git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git<br /> cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm<br /> <br /> == See Also ==<br /> <br /> * [[Classic install or sys mode on Raspberry Pi]] - a variant.<br /> * [[Raspberry Pi - Headless Installation]]<br /> * [[Raspberry Pi 3 - Setting Up Bluetooth]]<br /> * [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]<br /> * [[Raspberry Pi 3 - Browser Client]]<br /> * [[Linux Router with VPN on a Raspberry Pi]]<br /> * [[Create a bootable SDHC from a Mac]]<br /> * Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]<br /> * [[Tutorials and Howtos#Raspberry Pi]]<br /> <br /> [[Category:Installation]]<br /> [[Category: Raspberry]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Raspberry_Pi&diff=20178 Raspberry Pi 2021-10-07T18:50:18Z

<p>Legale: /* Loopback image with overlayfs */</p> <hr /> <div>{{warning | 11 Feb 2021 - There is currently a known bug upstream <br />[https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label] }}<br /> <br /> {{TOC right}}<br /> <br /> This tutorial will help you install Alpine Linux on your Raspberry Pi.<br /> <br /> == Preparation ==<br /> <br /> # [http://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. You should be safe using the '''armhf''' build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The '''armv7''' build is compatible with Raspberry Pi 2 Model B. The '''aarch64''' build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.<br /> # [[Create a Bootable USB#Format USB stick|Create a bootable FAT32 partition on your SD card.]] The partition type should be <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.) You can use a partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks] or [http://linux.die.net/man/8/fdisk fdisk].<br /> # Create a filesystem on the partition with <code>mkdosfs -F 32 /dev/sdX1</code> (Replace sdX1 with the correct reference to the partition you just created.)<br /> # Mount the partition and extract the tarball contents onto it.<br /> <br /> Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:<br /> * To enable audio: <code>dtparam=audio=on</code><br /> * If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code><br /> <br /> Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].<br /> <br /> == Installation ==<br /> <br /> Alpine Linux will be installed in [[Installation#Installation_Handbook|diskless mode]], hence you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots.<br /> <br /> For users who will be using their Raspberry Pi in scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. <br /> <br /> However, if you:<br /> * Expect there will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)<br /> * Need logs to persist after reboot<br /> * Plan to install packages which consume more space than can be loaded into RAM<br /> * Want to install kernel modules (such as ZFS or Wireguard)<br /> <br /> Then you may be better served by a [[Classic install or sys mode on Raspberry Pi|sys-mode installation]]. <br /> <br /> Follow these steps to install Alpine Linux in Diskless Mode:<br /> <br /> # Insert the SD card into the Raspberry Pi and power it on<br /> # Login into the Alpine system as root. Leave the password empty.<br /> # Type <code>setup-alpine</code><br /> # Once the installation is complete, commit the changes by typing <code>lbu commit -d</code><br /> <br /> Type <code>reboot</code> to verify that the installation was indeed successful.<br /> <br /> == Post Installation ==<br /> <br /> === Update the System ===<br /> <br /> After installation, make sure your system is up-to-date:<br /> <br /> {{cmd|apk update<br /> apk upgrade}}<br /> <br /> Don't forget to save the changes:<br /> <br /> {{cmd|lbu commit -d}}<br /> <br /> Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].<br /> <br /> === Clock-related error messages ===<br /> <br /> During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have<br /> a hardware clock, thus you need to disable the hwclock daemon and enable swclock:<br /> <br /> {{cmd|rc-update add swclock boot # enable the software clock<br /> rc-update del hwclock boot # disable the hardware clock}}<br /> <br /> Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a<br /> [https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a<br /> NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following<br /> command:<br /> <br /> {{cmd|setup-ntp}}<br /> <br /> The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is<br /> installed and running:<br /> <br /> {{cmd|lbu commit -d<br /> reboot}}<br /> <br /> After reboot, make sure the <code>date</code> command outputs the correct date and time.<br /> <br /> === WiFi on boot ===<br /> If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.<br /> You will need to start up a service to automatically connect to the wireless access point.<br /> # Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.<br /> # Run it manually with <code>/etc/init.d/wpa_supplicant start</code>.<br /> <br /> === Enable OpenGL (Raspberry Pi 3/4) ===<br /> Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):<br /> <br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount}}<br /> <br /> Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:<br /> <br /> gpu_mem=128<br /> # Raspberry Pi 3:<br /> dtoverlay=vc4-kms-v3d<br /> # Raspberry Pi 4:<br /> dtoverlay=vc4-fkms-v3d<br /> <br /> 256MB (and more on the Raspberry Pi 4) <code>gpu_mem</code> is also possible.<br /> <br /> Install the Mesa drivers:<br /> <br /> {{cmd|<nowiki># Raspberry Pi 3:<br /> apk add mesa-dri-vc4<br /> # Raspberry Pi 4:<br /> apk add mesa-dri-gallium</nowiki>}}<br /> <br /> Then reboot:<br /> <br /> {{cmd|lbu_commit -d; reboot}}<br /> <br /> === WiFi drivers ===<br /> As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.<br /> Use the ethernet interface to download the required packages:<br /> <br /> {{cmd|apk add linux-firmware-cypress}}<br /> <br /> And reboot.<br /> <br /> == Persistent storage ==<br /> === Loopback image with overlayfs ===<br /> <br /> When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.<br /> <br /> First, make the SD card writable again and change fstab to always do so:<br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount<br /> sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}<br /> <br /> Create the loop-back file, this example is 1 GB:<br /> <br /> {{cmd|dd if&#61;/dev/zero of&#61;/media/mmcblk0p1/persist.img bs&#61;1024 count&#61;0 seek&#61;1048576}}<br /> <br /> Install the ext utilities:<br /> <br /> {{cmd|apk add e2fsprogs}}<br /> <br /> Format the loop-back file:<br /> <br /> {{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}<br /> <br /> Mount the storage: <br /> <br /> {{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0" >> /etc/fstab<br /> mkdir /media/persist <br /> mount -a}}<br /> <br /> Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else. <br /> {{Note|Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay should use its own workdir}}<br /> <br /> <br /> {{cmd|mkdir /media/persist/usr <br /> mkdir /media/persist/.work_usr <br /> echo "overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0" >> /etc/fstab <br /> mount -a}}<br /> <br /> Your /etc/fstab should look something like this:<br /> {{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0<br /> /dev/usbdisk /media/usb vfat noauto,ro 0 0<br /> /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask&#61;0022,dmask&#61;0022,errors&#61;remount-ro 0 0<br /> /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0<br /> overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0}}<br /> <br /> Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)<br /> {{cmd|lbu_commit -d}}<br /> <br /> Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.<br /> <br /> If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`.<br /> <br /> If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent.<br /> <br /> === Traditional disk-based (sys) installation ===<br /> {{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}<br /> <br /> It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.<br /> <br /> Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:<br /> <br /> {{cmd|apk add e2fsprogs<br /> mkfs.ext4 /dev/mmcblk0p2}}<br /> <br /> Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.<br /> The Raspberry Pi doesn't need them to boot.<br /> <br /> {{cmd|<nowiki>mkdir /stage<br /> mount /dev/mmcblk0p2 /stage<br /> setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage<br /> # (ignore errors about syslinux/extlinux)</nowiki>}}<br /> <br /> Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:<br /> <br /> {{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}<br /> <br /> Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:<br /> <br /> {{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1<br /> sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}<br /> <br /> You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.<br /> <br /> N.B. <b>the contents of /boot will be ignored when the Pi boots</b>. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,<br /> copying the files to boot partition manually, is not needed.<br /> <br /> {{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}<br /> <br /> === Persistent Installation on Raspberry Pi 3 ===<br /> See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084<br /> <br /> === Persistent Installation on Raspberry Pi 4 ===<br /> As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.<br /> <br /> == Troubleshooting ==<br /> <br /> === Long boot time when running headless ===<br /> <br /> If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.<br /> <br /> If this is the case, simply plugging in any USB device should work around this issue.<br /> <br /> '''Alternatively''', installing haveged, the random numbers generator, would speed up the process: <br /> <br /> apk update <br /> apk add haveged<br /> rc-update add haveged boot<br /> lbu commit -d<br /> service haveged start<br /> <br /> (Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3)<br /> <br /> === apk indicating 'No space left on device' ===<br /> <br /> Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.<br /> <br /> === Wireless support with older Alpine images ===<br /> <br /> If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.<br /> (Replace /mnt/sdcard with the correct mount point.)<br /> <br /> git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git<br /> cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm<br /> <br /> == See Also ==<br /> <br /> * [[Classic install or sys mode on Raspberry Pi]] - a variant.<br /> * [[Raspberry Pi - Headless Installation]]<br /> * [[Raspberry Pi 3 - Setting Up Bluetooth]]<br /> * [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]<br /> * [[Raspberry Pi 3 - Browser Client]]<br /> * [[Linux Router with VPN on a Raspberry Pi]]<br /> * [[Create a bootable SDHC from a Mac]]<br /> * Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]<br /> * [[Tutorials and Howtos#Raspberry Pi]]<br /> <br /> [[Category:Installation]]<br /> [[Category: Raspberry]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Raspberry_Pi&diff=20177 Raspberry Pi 2021-10-07T18:48:59Z

<p>Legale: /* Loopback image with overlayfs */</p> <hr /> <div>{{warning | 11 Feb 2021 - There is currently a known bug upstream <br />[https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label] }}<br /> <br /> {{TOC right}}<br /> <br /> This tutorial will help you install Alpine Linux on your Raspberry Pi.<br /> <br /> == Preparation ==<br /> <br /> # [http://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. You should be safe using the '''armhf''' build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The '''armv7''' build is compatible with Raspberry Pi 2 Model B. The '''aarch64''' build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.<br /> # [[Create a Bootable USB#Format USB stick|Create a bootable FAT32 partition on your SD card.]] The partition type should be <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.) You can use a partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks] or [http://linux.die.net/man/8/fdisk fdisk].<br /> # Create a filesystem on the partition with <code>mkdosfs -F 32 /dev/sdX1</code> (Replace sdX1 with the correct reference to the partition you just created.)<br /> # Mount the partition and extract the tarball contents onto it.<br /> <br /> Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:<br /> * To enable audio: <code>dtparam=audio=on</code><br /> * If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code><br /> <br /> Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].<br /> <br /> == Installation ==<br /> <br /> Alpine Linux will be installed in [[Installation#Installation_Handbook|diskless mode]], hence you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots.<br /> <br /> For users who will be using their Raspberry Pi in scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. <br /> <br /> However, if you:<br /> * Expect there will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)<br /> * Need logs to persist after reboot<br /> * Plan to install packages which consume more space than can be loaded into RAM<br /> * Want to install kernel modules (such as ZFS or Wireguard)<br /> <br /> Then you may be better served by a [[Classic install or sys mode on Raspberry Pi|sys-mode installation]]. <br /> <br /> Follow these steps to install Alpine Linux in Diskless Mode:<br /> <br /> # Insert the SD card into the Raspberry Pi and power it on<br /> # Login into the Alpine system as root. Leave the password empty.<br /> # Type <code>setup-alpine</code><br /> # Once the installation is complete, commit the changes by typing <code>lbu commit -d</code><br /> <br /> Type <code>reboot</code> to verify that the installation was indeed successful.<br /> <br /> == Post Installation ==<br /> <br /> === Update the System ===<br /> <br /> After installation, make sure your system is up-to-date:<br /> <br /> {{cmd|apk update<br /> apk upgrade}}<br /> <br /> Don't forget to save the changes:<br /> <br /> {{cmd|lbu commit -d}}<br /> <br /> Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].<br /> <br /> === Clock-related error messages ===<br /> <br /> During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have<br /> a hardware clock, thus you need to disable the hwclock daemon and enable swclock:<br /> <br /> {{cmd|rc-update add swclock boot # enable the software clock<br /> rc-update del hwclock boot # disable the hardware clock}}<br /> <br /> Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a<br /> [https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a<br /> NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following<br /> command:<br /> <br /> {{cmd|setup-ntp}}<br /> <br /> The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is<br /> installed and running:<br /> <br /> {{cmd|lbu commit -d<br /> reboot}}<br /> <br /> After reboot, make sure the <code>date</code> command outputs the correct date and time.<br /> <br /> === WiFi on boot ===<br /> If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.<br /> You will need to start up a service to automatically connect to the wireless access point.<br /> # Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.<br /> # Run it manually with <code>/etc/init.d/wpa_supplicant start</code>.<br /> <br /> === Enable OpenGL (Raspberry Pi 3/4) ===<br /> Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):<br /> <br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount}}<br /> <br /> Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:<br /> <br /> gpu_mem=128<br /> # Raspberry Pi 3:<br /> dtoverlay=vc4-kms-v3d<br /> # Raspberry Pi 4:<br /> dtoverlay=vc4-fkms-v3d<br /> <br /> 256MB (and more on the Raspberry Pi 4) <code>gpu_mem</code> is also possible.<br /> <br /> Install the Mesa drivers:<br /> <br /> {{cmd|<nowiki># Raspberry Pi 3:<br /> apk add mesa-dri-vc4<br /> # Raspberry Pi 4:<br /> apk add mesa-dri-gallium</nowiki>}}<br /> <br /> Then reboot:<br /> <br /> {{cmd|lbu_commit -d; reboot}}<br /> <br /> === WiFi drivers ===<br /> As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.<br /> Use the ethernet interface to download the required packages:<br /> <br /> {{cmd|apk add linux-firmware-cypress}}<br /> <br /> And reboot.<br /> <br /> == Persistent storage ==<br /> === Loopback image with overlayfs ===<br /> <br /> When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.<br /> <br /> First, make the SD card writable again and change fstab to always do so:<br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount<br /> sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}<br /> <br /> Create the loop-back file, this example is 1 GB:<br /> <br /> {{cmd|dd if&#61;/dev/zero of&#61;/media/mmcblk0p1/persist.img bs&#61;1024 count&#61;0 seek&#61;1048576}}<br /> <br /> Install the ext utilities:<br /> <br /> {{cmd|apk add e2fsprogs}}<br /> <br /> Format the loop-back file:<br /> <br /> {{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}<br /> <br /> Mount the storage: <br /> <br /> {{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0" >> /etc/fstab<br /> mkdir /media/persist <br /> mount -a}}<br /> <br /> Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else. <br /> {{Note|Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay should use its own workdir}}<br /> <br /> <br /> {{cmd|mkdir /media/persist/usr <br /> mkdir /media/persist/.work_usr <br /> echo "overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work 0 0" >> /etc/fstab <br /> mount -a}}<br /> <br /> Your /etc/fstab should look something like this:<br /> {{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0<br /> /dev/usbdisk /media/usb vfat noauto,ro 0 0<br /> /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask&#61;0022,dmask&#61;0022,errors&#61;remount-ro 0 0<br /> /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0<br /> overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0}}<br /> <br /> Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)<br /> {{cmd|lbu_commit -d}}<br /> <br /> Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.<br /> <br /> If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`.<br /> <br /> If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent.<br /> <br /> === Traditional disk-based (sys) installation ===<br /> {{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}<br /> <br /> It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.<br /> <br /> Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:<br /> <br /> {{cmd|apk add e2fsprogs<br /> mkfs.ext4 /dev/mmcblk0p2}}<br /> <br /> Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.<br /> The Raspberry Pi doesn't need them to boot.<br /> <br /> {{cmd|<nowiki>mkdir /stage<br /> mount /dev/mmcblk0p2 /stage<br /> setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage<br /> # (ignore errors about syslinux/extlinux)</nowiki>}}<br /> <br /> Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:<br /> <br /> {{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}<br /> <br /> Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:<br /> <br /> {{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1<br /> sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}<br /> <br /> You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.<br /> <br /> N.B. <b>the contents of /boot will be ignored when the Pi boots</b>. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,<br /> copying the files to boot partition manually, is not needed.<br /> <br /> {{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}<br /> <br /> === Persistent Installation on Raspberry Pi 3 ===<br /> See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084<br /> <br /> === Persistent Installation on Raspberry Pi 4 ===<br /> As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.<br /> <br /> == Troubleshooting ==<br /> <br /> === Long boot time when running headless ===<br /> <br /> If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.<br /> <br /> If this is the case, simply plugging in any USB device should work around this issue.<br /> <br /> '''Alternatively''', installing haveged, the random numbers generator, would speed up the process: <br /> <br /> apk update <br /> apk add haveged<br /> rc-update add haveged boot<br /> lbu commit -d<br /> service haveged start<br /> <br /> (Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3)<br /> <br /> === apk indicating 'No space left on device' ===<br /> <br /> Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.<br /> <br /> === Wireless support with older Alpine images ===<br /> <br /> If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.<br /> (Replace /mnt/sdcard with the correct mount point.)<br /> <br /> git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git<br /> cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm<br /> <br /> == See Also ==<br /> <br /> * [[Classic install or sys mode on Raspberry Pi]] - a variant.<br /> * [[Raspberry Pi - Headless Installation]]<br /> * [[Raspberry Pi 3 - Setting Up Bluetooth]]<br /> * [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]<br /> * [[Raspberry Pi 3 - Browser Client]]<br /> * [[Linux Router with VPN on a Raspberry Pi]]<br /> * [[Create a bootable SDHC from a Mac]]<br /> * Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]<br /> * [[Tutorials and Howtos#Raspberry Pi]]<br /> <br /> [[Category:Installation]]<br /> [[Category: Raspberry]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Raspberry_Pi&diff=20176 Raspberry Pi 2021-10-07T18:41:09Z

<p>Legale: /* Loopback image with overlayfs */</p> <hr /> <div>{{warning | 11 Feb 2021 - There is currently a known bug upstream <br />[https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label] }}<br /> <br /> {{TOC right}}<br /> <br /> This tutorial will help you install Alpine Linux on your Raspberry Pi.<br /> <br /> == Preparation ==<br /> <br /> # [http://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. You should be safe using the '''armhf''' build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The '''armv7''' build is compatible with Raspberry Pi 2 Model B. The '''aarch64''' build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.<br /> # [[Create a Bootable USB#Format USB stick|Create a bootable FAT32 partition on your SD card.]] The partition type should be <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.) You can use a partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks] or [http://linux.die.net/man/8/fdisk fdisk].<br /> # Create a filesystem on the partition with <code>mkdosfs -F 32 /dev/sdX1</code> (Replace sdX1 with the correct reference to the partition you just created.)<br /> # Mount the partition and extract the tarball contents onto it.<br /> <br /> Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:<br /> * To enable audio: <code>dtparam=audio=on</code><br /> * If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code><br /> <br /> Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].<br /> <br /> == Installation ==<br /> <br /> Alpine Linux will be installed in [[Installation#Installation_Handbook|diskless mode]], hence you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots.<br /> <br /> For users who will be using their Raspberry Pi in scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. <br /> <br /> However, if you:<br /> * Expect there will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)<br /> * Need logs to persist after reboot<br /> * Plan to install packages which consume more space than can be loaded into RAM<br /> * Want to install kernel modules (such as ZFS or Wireguard)<br /> <br /> Then you may be better served by a [[Classic install or sys mode on Raspberry Pi|sys-mode installation]]. <br /> <br /> Follow these steps to install Alpine Linux in Diskless Mode:<br /> <br /> # Insert the SD card into the Raspberry Pi and power it on<br /> # Login into the Alpine system as root. Leave the password empty.<br /> # Type <code>setup-alpine</code><br /> # Once the installation is complete, commit the changes by typing <code>lbu commit -d</code><br /> <br /> Type <code>reboot</code> to verify that the installation was indeed successful.<br /> <br /> == Post Installation ==<br /> <br /> === Update the System ===<br /> <br /> After installation, make sure your system is up-to-date:<br /> <br /> {{cmd|apk update<br /> apk upgrade}}<br /> <br /> Don't forget to save the changes:<br /> <br /> {{cmd|lbu commit -d}}<br /> <br /> Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].<br /> <br /> === Clock-related error messages ===<br /> <br /> During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have<br /> a hardware clock, thus you need to disable the hwclock daemon and enable swclock:<br /> <br /> {{cmd|rc-update add swclock boot # enable the software clock<br /> rc-update del hwclock boot # disable the hardware clock}}<br /> <br /> Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a<br /> [https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a<br /> NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following<br /> command:<br /> <br /> {{cmd|setup-ntp}}<br /> <br /> The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is<br /> installed and running:<br /> <br /> {{cmd|lbu commit -d<br /> reboot}}<br /> <br /> After reboot, make sure the <code>date</code> command outputs the correct date and time.<br /> <br /> === WiFi on boot ===<br /> If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.<br /> You will need to start up a service to automatically connect to the wireless access point.<br /> # Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.<br /> # Run it manually with <code>/etc/init.d/wpa_supplicant start</code>.<br /> <br /> === Enable OpenGL (Raspberry Pi 3/4) ===<br /> Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):<br /> <br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount}}<br /> <br /> Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:<br /> <br /> gpu_mem=128<br /> # Raspberry Pi 3:<br /> dtoverlay=vc4-kms-v3d<br /> # Raspberry Pi 4:<br /> dtoverlay=vc4-fkms-v3d<br /> <br /> 256MB (and more on the Raspberry Pi 4) <code>gpu_mem</code> is also possible.<br /> <br /> Install the Mesa drivers:<br /> <br /> {{cmd|<nowiki># Raspberry Pi 3:<br /> apk add mesa-dri-vc4<br /> # Raspberry Pi 4:<br /> apk add mesa-dri-gallium</nowiki>}}<br /> <br /> Then reboot:<br /> <br /> {{cmd|lbu_commit -d; reboot}}<br /> <br /> === WiFi drivers ===<br /> As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.<br /> Use the ethernet interface to download the required packages:<br /> <br /> {{cmd|apk add linux-firmware-cypress}}<br /> <br /> And reboot.<br /> <br /> == Persistent storage ==<br /> === Loopback image with overlayfs ===<br /> <br /> When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.<br /> <br /> First, make the SD card writable again and change fstab to always do so:<br /> {{cmd|mount /media/mmcblk0p1 -o rw,remount<br /> sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}<br /> <br /> Create the loop-back file, this example is 1 GB:<br /> <br /> {{cmd|dd if&#61;/dev/zero of&#61;/media/mmcblk0p1/persist.img bs&#61;1024 count&#61;0 seek&#61;1048576}}<br /> <br /> Install the ext utilities:<br /> <br /> {{cmd|apk add e2fsprogs}}<br /> <br /> Format the loop-back file:<br /> <br /> {{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}<br /> <br /> Mount the storage: <br /> <br /> {{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0" >> /etc/fstab<br /> mkdir /media/persist <br /> mount -a}}<br /> <br /> Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else:<br /> <br /> {{cmd|mkdir /media/persist/usr <br /> mkdir /media/persist/.work_usr <br /> echo "overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work 0 0" >> /etc/fstab <br /> mount -a}}<br /> <br /> Your /etc/fstab should look something like this:<br /> {{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0<br /> /dev/usbdisk /media/usb vfat noauto,ro 0 0<br /> /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask&#61;0022,dmask&#61;0022,errors&#61;remount-ro 0 0<br /> /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors&#61;remount-ro 0 0<br /> overlay /usr overlay lowerdir&#61;/usr,upperdir&#61;/media/persist/usr,workdir&#61;/media/persist/.work_usr 0 0}}<br /> <br /> Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)<br /> {{cmd|lbu_commit -d}}<br /> <br /> Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.<br /> <br /> If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`.<br /> <br /> If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent.<br /> <br /> === Traditional disk-based (sys) installation ===<br /> {{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}<br /> <br /> It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.<br /> <br /> Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:<br /> <br /> {{cmd|apk add e2fsprogs<br /> mkfs.ext4 /dev/mmcblk0p2}}<br /> <br /> Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.<br /> The Raspberry Pi doesn't need them to boot.<br /> <br /> {{cmd|<nowiki>mkdir /stage<br /> mount /dev/mmcblk0p2 /stage<br /> setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage<br /> # (ignore errors about syslinux/extlinux)</nowiki>}}<br /> <br /> Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:<br /> <br /> {{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}<br /> <br /> Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:<br /> <br /> {{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1<br /> sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}<br /> <br /> You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.<br /> <br /> N.B. <b>the contents of /boot will be ignored when the Pi boots</b>. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,<br /> copying the files to boot partition manually, is not needed.<br /> <br /> {{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}<br /> <br /> === Persistent Installation on Raspberry Pi 3 ===<br /> See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084<br /> <br /> === Persistent Installation on Raspberry Pi 4 ===<br /> As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.<br /> <br /> == Troubleshooting ==<br /> <br /> === Long boot time when running headless ===<br /> <br /> If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.<br /> <br /> If this is the case, simply plugging in any USB device should work around this issue.<br /> <br /> '''Alternatively''', installing haveged, the random numbers generator, would speed up the process: <br /> <br /> apk update <br /> apk add haveged<br /> rc-update add haveged boot<br /> lbu commit -d<br /> service haveged start<br /> <br /> (Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3)<br /> <br /> === apk indicating 'No space left on device' ===<br /> <br /> Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.<br /> <br /> === Wireless support with older Alpine images ===<br /> <br /> If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.<br /> (Replace /mnt/sdcard with the correct mount point.)<br /> <br /> git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git<br /> cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm<br /> <br /> == See Also ==<br /> <br /> * [[Classic install or sys mode on Raspberry Pi]] - a variant.<br /> * [[Raspberry Pi - Headless Installation]]<br /> * [[Raspberry Pi 3 - Setting Up Bluetooth]]<br /> * [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]<br /> * [[Raspberry Pi 3 - Browser Client]]<br /> * [[Linux Router with VPN on a Raspberry Pi]]<br /> * [[Create a bootable SDHC from a Mac]]<br /> * Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]<br /> * [[Tutorials and Howtos#Raspberry Pi]]<br /> <br /> [[Category:Installation]]<br /> [[Category: Raspberry]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Wi-Fi&diff=20173 Wi-Fi 2021-10-06T15:11:03Z

<p>Legale: </p> <hr /> <div>This document describes how to set up a wireless network connection with WPA encryption.<br /> <br /> == Install necessary drivers and software ==<br /> <br /> First make sure your wireless drivers are loaded properly. (if you are using a '''Broadcom chipset''', see the [[#Broadcom_Wi-Fi_Chipset_Users|section at the bottom of this post]].)<br /> <br /> Install {{Pkg|wireless-tools}} and {{Pkg|wpa_supplicant}}, which are probably available to be installed in the base setup.<br /> {{Cmd|apk add wireless-tools wpa_supplicant}}<br /> <br /> == Manual Configuration ==<br /> <br /> List your available network interfaces. If you don't see any wireless interfaces (e.g. {{Path|wlan0}}), you probably need to load and/or install drivers/firmware.<br /> {{Cmd|ip link}}<br /> <br /> Bring up the desired interface.<br /> {{Cmd|ip link set wlan0 up}}<br /> <br /> {{Note|If this errors with <code>ioctl 0x8914 failed: No error information</code>, that's <code>busybox ip</code>'s way of saying your wireless radio is rfkill'd. See [https://wiki.archlinux.org/index.php/Wireless_network_configuration#Rfkill_caveat here] for information on how to unblock your wireless radio.<br /> The base installation should have <code>busybox rfkill</code> available.}}<br /> <br /> <br /> Use the interface to scan for wireless access points. Make sure the ESSID you want to connect to appears here.<br /> {{Cmd|iwlist wlan0 scanning}}<br /> <br /> Associate the interface with desired ESSID.<br /> {{Cmd|iwconfig wlan0 essid ExampleWifi}}<br /> <br /> Sanity check: the interface should be configured with {{Path|ESSID:"ExampleWifi"}}.<br /> {{Cmd|iwconfig wlan0}}<br /> <br /> Create a wpa_supplicant configuration stanza for the wireless access point.<br /> {{Cmd|wpa_passphrase 'ExampleWifi' 'ExampleWifiPassword' > /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> ''(Access point not broadcasting its SSID requires additional line <code>scan_ssid=1</code> in the file <code>wpa_supplicant.conf</code>)''<br /> <br /> <br /> Start wpa_supplicant in the foreground to make sure the connection succeeds.<br /> {{Cmd|wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> <br /> If all is well, run it as a daemon in the background by setting the {{Path|-B}} option.<br /> {{Cmd|wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> <br /> Configure the interface with an IP address.<br /> {{Cmd|udhcpc -i wlan0}}<br /> <br /> Sanity check: the interface should have an {{Path|inet}} address.<br /> {{Cmd|ip addr show wlan0}}<br /> <br /> == Automatic Configuration on System Boot ==<br /> <br /> Add a stanza for the desired interface (e.g. {{Path|wlan0}}) to {{Path|/etc/network/interfaces}}:<br /> <br /> <pre><br /> auto wlan0<br /> iface wlan0 inet dhcp<br /> </pre><br /> <br /> Make sure {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}} is the correct configuration for the wireless access point you want to connect to.<br /> <br /> Bring the interface down.<br /> <br /> {{Cmd|ifconfig wlan0 down}}<br /> <br /> Manually start wpa_supplicant.<br /> <br /> {{Cmd|/etc/init.d/wpa_supplicant start}}<br /> <br /> If all is well (confirm with the sanity checks in [[#Manual_Configuration|Manual Configuration]]), configure wpa_supplicant to start automatically on boot.<br /> <br /> {{Cmd|rc-update add wpa_supplicant boot}}<br /> <br /> <br /> === Launching udhcpc through wpa_cli actions ===<br /> <br /> With the above configuration, udhcpc will only run once at boot.<br /> If the Wifi isn't available then, or the network changes in between, it needs to be notified.<br /> This is done through the wpa_cli action script in /etc/wpa_supplicant/wpa_cli.sh<br /> <br /> == Automatic Reconnection when WIFI signal is lost ==<br /> To enable automatic reconnection when wifi signal is lost add these to config:<br /> <br /> {{Cat|/etc/wpa_supplicant/wpa_supplicant.conf|<br /> <nowiki><br /> ap_scan=1<br /> autoscan=periodic:10<br /> disable_scan_offload=1<br /> </nowiki><br /> }}<br /> <br /> <br /> {{Cmd|rc-update add wpa_cli boot}}<br /> <br /> == Broadcom Wi-Fi Chipset Users ==<br /> <br /> The Broadcom chipset is quite popular among older computers. You will need to compile the firmware manually for this chipset as it is not included. <br /> <br /> You can check if you have a Broadcom chipset by using dmesg:<br /> <br /> {{Cmd|dmesg {{!}} grep Broadcom}}<br /> <br /> First install the SDK and Git:<br /> {{Cmd|apk add alpine-sdk git}}<br /> <br /> Then git clone aports from git.alpinelinux.org.<br /> <br /> <br /> {{Cmd|git clone git://git.alpinelinux.org/aports}}<br /> <br /> Change your directory to '''aports/non-free/b43-firmware''', then build it.<br /> <br /> {{Tip|You can't be root and must be a user of the group abuild (use groupadd f.e. '''addgroup $(whoami) abuild''')}}<br /> {{Tip|If this is your first time building a package you will need to generate a key for use in signing packages (use '''abuild-keygen -a -i''')}}<br /> <br /> {{Cmd|abuild -r}}<br /> <br /> Install the generated packge file (it will be in ~/packages/) - make sure to pass '''--allow-untrusted'''<br /> <br /> {{Cmd|apk add --allow-untrusted ~/packages/...pkg}}<br /> <br /> Now we need fwcutter, which is executed from the firmware package:<br /> <br /> {{Cmd|apk add b43-fwcutter b43-firmware}}<br /> <br /> Now you need to use modprobe so the device will show up:<br /> <br /> {{Cmd|modprobe b43}}<br /> <br /> To automate this on startup add it to /etc/modules:<br /> <br /> {{Cmd|echo b43 >> /etc/modules}}<br /> <br /> Now continue with the normal instructions. <br /> <br /> [[Category:Networking]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Wi-Fi&diff=20172 Wi-Fi 2021-10-06T15:01:17Z

<p>Legale: </p> <hr /> <div>This document describes how to set up a wireless network connection with WPA encryption.<br /> <br /> == Install necessary drivers and software ==<br /> <br /> First make sure your wireless drivers are loaded properly. (if you are using a '''Broadcom chipset''', see the [[#Broadcom_Wi-Fi_Chipset_Users|section at the bottom of this post]].)<br /> <br /> Install {{Pkg|wireless-tools}} and {{Pkg|wpa_supplicant}}, which are probably available to be installed in the base setup.<br /> {{Cmd|apk add wireless-tools wpa_supplicant}}<br /> <br /> == Manual Configuration ==<br /> <br /> List your available network interfaces. If you don't see any wireless interfaces (e.g. {{Path|wlan0}}), you probably need to load and/or install drivers/firmware.<br /> {{Cmd|ip link}}<br /> <br /> Bring up the desired interface.<br /> {{Cmd|ip link set wlan0 up}}<br /> <br /> {{Note|If this errors with <code>ioctl 0x8914 failed: No error information</code>, that's <code>busybox ip</code>'s way of saying your wireless radio is rfkill'd. See [https://wiki.archlinux.org/index.php/Wireless_network_configuration#Rfkill_caveat here] for information on how to unblock your wireless radio.<br /> The base installation should have <code>busybox rfkill</code> available.}}<br /> <br /> <br /> Use the interface to scan for wireless access points. Make sure the ESSID you want to connect to appears here.<br /> {{Cmd|iwlist wlan0 scanning}}<br /> <br /> Associate the interface with desired ESSID.<br /> {{Cmd|iwconfig wlan0 essid ExampleWifi}}<br /> <br /> Sanity check: the interface should be configured with {{Path|ESSID:"ExampleWifi"}}.<br /> {{Cmd|iwconfig wlan0}}<br /> <br /> Create a wpa_supplicant configuration stanza for the wireless access point.<br /> {{Cmd|wpa_passphrase 'ExampleWifi' 'ExampleWifiPassword' > /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> ''(Access point not broadcasting its SSID requires additional line <code>scan_ssid=1</code> in the file <code>wpa_supplicant.conf</code>)''<br /> <br /> <br /> Start wpa_supplicant in the foreground to make sure the connection succeeds.<br /> {{Cmd|wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> <br /> If all is well, run it as a daemon in the background by setting the {{Path|-B}} option.<br /> {{Cmd|wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}<br /> <br /> Configure the interface with an IP address.<br /> {{Cmd|udhcpc -i wlan0}}<br /> <br /> Sanity check: the interface should have an {{Path|inet}} address.<br /> {{Cmd|ip addr show wlan0}}<br /> <br /> == Automatic Configuration on System Boot ==<br /> <br /> Add a stanza for the desired interface (e.g. {{Path|wlan0}}) to {{Path|/etc/network/interfaces}}:<br /> <br /> <pre><br /> auto wlan0<br /> iface wlan0 inet dhcp<br /> </pre><br /> <br /> Make sure {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}} is the correct configuration for the wireless access point you want to connect to.<br /> <br /> Bring the interface down.<br /> <br /> {{Cmd|ifconfig wlan0 down}}<br /> <br /> Manually start wpa_supplicant.<br /> <br /> {{Cmd|/etc/init.d/wpa_supplicant start}}<br /> <br /> If all is well (confirm with the sanity checks in [[#Manual_Configuration|Manual Configuration]]), configure wpa_supplicant to start automatically on boot.<br /> <br /> {{Cmd|rc-update add wpa_supplicant boot}}<br /> <br /> <br /> === Launching udhcpc through wpa_cli actions ===<br /> <br /> With the above configuration, udhcpc will only run once at boot.<br /> If the Wifi isn't available then, or the network changes in between, it needs to be notified.<br /> This is done through the wpa_cli action script in /etc/wpa_supplicant/wpa_cli.sh<br /> <br /> == Automatic Reconnection when WIFI signal is lost ==<br /> `/etc/wpa_supplicant/wpa_supplicant.conf`<br /> <br /> To enable automatic reconnection when wifi signal is lost add these to config:<br /> ```<br /> ap_scan=1<br /> disable_scan_offload=1<br /> ```<br /> <br /> <br /> {{Cmd|rc-update add wpa_cli boot}}<br /> <br /> == Broadcom Wi-Fi Chipset Users ==<br /> <br /> The Broadcom chipset is quite popular among older computers. You will need to compile the firmware manually for this chipset as it is not included. <br /> <br /> You can check if you have a Broadcom chipset by using dmesg:<br /> <br /> {{Cmd|dmesg {{!}} grep Broadcom}}<br /> <br /> First install the SDK and Git:<br /> {{Cmd|apk add alpine-sdk git}}<br /> <br /> Then git clone aports from git.alpinelinux.org.<br /> <br /> <br /> {{Cmd|git clone git://git.alpinelinux.org/aports}}<br /> <br /> Change your directory to '''aports/non-free/b43-firmware''', then build it.<br /> <br /> {{Tip|You can't be root and must be a user of the group abuild (use groupadd f.e. '''addgroup $(whoami) abuild''')}}<br /> {{Tip|If this is your first time building a package you will need to generate a key for use in signing packages (use '''abuild-keygen -a -i''')}}<br /> <br /> {{Cmd|abuild -r}}<br /> <br /> Install the generated packge file (it will be in ~/packages/) - make sure to pass '''--allow-untrusted'''<br /> <br /> {{Cmd|apk add --allow-untrusted ~/packages/...pkg}}<br /> <br /> Now we need fwcutter, which is executed from the firmware package:<br /> <br /> {{Cmd|apk add b43-fwcutter b43-firmware}}<br /> <br /> Now you need to use modprobe so the device will show up:<br /> <br /> {{Cmd|modprobe b43}}<br /> <br /> To automate this on startup add it to /etc/modules:<br /> <br /> {{Cmd|echo b43 >> /etc/modules}}<br /> <br /> Now continue with the normal instructions. <br /> <br /> [[Category:Networking]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Finding_the_fastest_mirror&diff=20145 Finding the fastest mirror 2021-09-27T08:28:23Z

<p>Legale: </p> <hr /> <div>After you install Alpine, you may be wondering how do I figure out the fastest mirror again?<br /> <br /> {{Cat|/home/user/fastestmirror|<nowiki><br /> data=""<br /> for s in $(wget -qO- http://rsync.alpinelinux.org/alpine/MIRRORS.txt); do<br /> t=$(time -f "%E" wget -q $s/MIRRORS.txt -O /dev/null 2>&1)<br /> echo "$s was $t"<br /> data="$data$t $s\n"<br /> done<br /> <br /> echo "===RESULTS==="<br /> <br /> echo -e $data | sort<br /> </nowiki>}}<br /> <br /> <br /> <br /> This is more advanced implementation.<br /> {{Cat|/etc/apk/fastest-mirror|<nowiki><br /> #!/bin/sh<br /> get_hostname_url() {<br /> local n=${1#*://}<br /> echo ${n%%/*}<br /> }<br /> <br /> time_cmd() {<br /> local proc=$(cut -d ' ' -f1 /proc/uptime)<br /> local start="$(echo $proc | cut -d . -f1)$(echo $proc | cut -d . -f2)"<br /> $@ >/dev/null 2>&1 || return<br /> proc=$(cut -d ' ' -f1 /proc/uptime)<br /> local end="$(echo $proc | cut -d . -f1)$(echo $proc | cut -d . -f2)" <br /> echo $(( $end - $start ))<br /> }<br /> <br /> DATA=""<br /> MIRRORS=$(wget -qO- "http://rsync.alpinelinux.org/alpine/MIRRORS.txt")<br /> DST=/etc/apk/mirrors.txt<br /> <br /> #find best<br /> for URL in $MIRRORS; do<br /> TIME=$(time_cmd wget -T 1 -q ${URL%/} -O /dev/null)<br /> if [ -n "$TIME" ]; then <br /> echo "$(get_hostname_url $URL) was $TIME"<br /> DATA="$DATA$TIME $URL\n"<br /> fi<br /> done<br /> <br /> <br /> echo -e $DATA | sort -n | tail -n +2 > $DST<br /> [ $? = 0 ] && echo file $DST created<br /> <br /> BEST=$(head -n1 $DST | cut -d ' ' -f2)<br /> echo "Best mirror is: $BEST"<br /> <br /> sed -i -r 's#^http.+/(.+/main)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> sed -i -r 's#^http.+/(.+/community)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> sed -i -r 's#^http.+/(.+/testing)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> <br /> <br /> </nowiki>}}<br /> <br /> <br /> [[Category:Package Manager]]<br /> <br /> <br /> <br /> [[Category:Package Manager]]</div>

Legale https://wiki.alpinelinux.org/w/index.php?title=Finding_the_fastest_mirror&diff=20144 Finding the fastest mirror 2021-09-26T22:14:09Z

<p>Legale: </p> <hr /> <div>After you install Alpine, you may be wondering how do I figure out the fastest mirror again?<br /> <br /> {{Cat|/home/user/fastestmirror|<nowiki><br /> data=""<br /> for s in $(wget -qO- http://rsync.alpinelinux.org/alpine/MIRRORS.txt); do<br /> t=$(time -f "%E" wget -q $s/MIRRORS.txt -O /dev/null 2>&1)<br /> echo "$s was $t"<br /> data="$data$t $s\n"<br /> done<br /> <br /> echo "===RESULTS==="<br /> <br /> echo -e $data | sort<br /> </nowiki>}}<br /> <br /> <br /> <br /> This is more advanced implementation.<br /> {{Cat|/etc/apk/fastest-mirror|<nowiki><br /> #!/bin/sh<br /> get_hostname_url() {<br /> local n=${1#*://}<br /> echo ${n%%/*}<br /> }<br /> <br /> time_cmd() {<br /> local proc=$(cut -d ' ' -f1 /proc/uptime)<br /> local start="$(echo $proc | cut -d . -f1)$(echo $proc | cut -d . -f2)"<br /> $@ >/dev/null 2>&1 || return<br /> proc=$(cut -d ' ' -f1 /proc/uptime)<br /> local end="$(echo $proc | cut -d . -f1)$(echo $proc | cut -d . -f2)" <br /> echo $(( $end - $start ))<br /> }<br /> <br /> DATA=""<br /> MIRRORS=$(wget -qO- "http://rsync.alpinelinux.org/alpine/MIRRORS.txt")<br /> DST=/etc/apk/mirrors.txt<br /> <br /> #find best<br /> for URL in $MIRRORS; do<br /> TIME=$(time_cmd wget -T 1 -q ${URL%/} -O /dev/null)<br /> if [ -n "$TIME" ]; then <br /> echo "$(get_hostname_url $URL) was $TIME"<br /> DATA="$DATA$TIME $URL\n"<br /> fi<br /> done<br /> <br /> <br /> echo -e $DATA | sort -n | tail -n +2 > $DST<br /> $? && echo file $DST created<br /> <br /> BEST=$(head -n1 $DST | cut -d ' ' -f2)<br /> echo "Best mirror is: $BEST"<br /> <br /> sed -i -r 's#^http.+/(.+/main)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> sed -i -r 's#^http.+/(.+/community)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> sed -i -r 's#^http.+/(.+/testing)#'${BEST%/}'/\1#' /etc/apk/repositories<br /> <br /> <br /> </nowiki>}}<br /> <br /> <br /> [[Category:Package Manager]]<br /> <br /> <br /> <br /> [[Category:Package Manager]]</div>

Legale