alpine-conf issueshttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues2024-01-24T21:52:21Zhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10573should setup-alpine add networking service to default, rather than boot runle...2024-01-24T21:52:21ZDermot Bradleyshould setup-alpine add networking service to default, rather than boot runlevel?Currently setup-alpine adds the networking init.d to the boot runlevel:
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-alpine.in?ref_type=heads#L229
Is there a specific reason why "boot" rather than "default"? Fo...Currently setup-alpine adds the networking init.d to the boot runlevel:
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-alpine.in?ref_type=heads#L229
Is there a specific reason why "boot" rather than "default"? For my own (non setup-alpine installed machines) I've always enabled networking in the default run-level.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10564setup-desktop: gnome fails to install if 'community' is not enabled yet2024-01-24T21:49:30Zdonobansetup-desktop: gnome fails to install if 'community' is not enabled yet```
setup-xorg-base ${BROWSER:-firefox} $(apk info --quiet --depends \ ...```
setup-xorg-base ${BROWSER:-firefox} $(apk info --quiet --depends \
gnome gnome-apps-core) "$@"
```
It wants to find gnome packages on apk info subshell but 'setup-xorg-base' will enable community repository later. So you need to run setup-desktop twice for gnome works.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10574gnome-apps-core didn't install2024-01-24T21:49:30ZDrSheppardgnome-apps-core didn't install1. Install alpine
2. ```setup-desktop gnome```
3. GDM and eudev didn't find and can't be adding in runlevels
I checked which packages should be installed after ```setup-desktop gnome``` and they included gnome-apps-core which contains g...1. Install alpine
2. ```setup-desktop gnome```
3. GDM and eudev didn't find and can't be adding in runlevels
I checked which packages should be installed after ```setup-desktop gnome``` and they included gnome-apps-core which contains gdm and gnome-console — most important packages for gnome desktop, that were nothttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10553`setup-interfaces -a` should setup all instead of last one2023-12-27T15:25:19Z杨文 陈`setup-interfaces -a` should setup all instead of last oneI expected
```bash
setup-interfaces -ar
```
to setup all interfaces, but only setup one.I expected
```bash
setup-interfaces -ar
```
to setup all interfaces, but only setup one.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10572setup-interfaces: use $iface with iw scan instead of wlan02023-12-27T07:43:11ZCarl Chavesetup-interfaces: use $iface with iw scan instead of wlan0I have a Dell/Wyse 3040 thin client with factory wifi card which shows up as interface `mlan0`. Setup-interfaces fails when trying to scan for wireless networks because `wlan0` is hard coded in the command:
https://gitlab.alpinelinux.or...I have a Dell/Wyse 3040 thin client with factory wifi card which shows up as interface `mlan0`. Setup-interfaces fails when trying to scan for wireless networks because `wlan0` is hard coded in the command:
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-interfaces.in?ref_type=heads#L125
I changed it to use the already defined `$iface` variable and was able to successfully connect and finish the setup:
```
(iw dev "$iface" scan; echo BSS) | awk -F": " '
```https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10532/root being created with group and world rx permissions (0755)2023-12-18T20:55:27ZDaniel F. Dickinson/root being created with group and world rx permissions (0755)At least with the 3.16.2 x86_64 virtual image (https://dl-cdn.alpinelinux.org/alpine/v3.16/releases/x86_64/alpine-virt-3.16.2-x86_64.iso), The root user's home directory (/root) is (at least after using `setup-alpine`) being created with...At least with the 3.16.2 x86_64 virtual image (https://dl-cdn.alpinelinux.org/alpine/v3.16/releases/x86_64/alpine-virt-3.16.2-x86_64.iso), The root user's home directory (/root) is (at least after using `setup-alpine`) being created with normal file permissions instead of restrictive.
That is 0755 (`drwxr-x-rx`) instead of 0700 (`drwx------`).
This was unexpected. (And not a fluke, three different VMs have done the same thing).
I don't know where the error is, that's why I'm submitting the report here instead of against a specific aports or alpine-conf or mkinit or other package.
I've marked it confidential since I consider it a security issue.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10563setup-user should prompt for password again if entered incorrectly2023-12-01T14:56:00ZJacksonsetup-user should prompt for password again if entered incorrectly`setup-alpine` asks for the password again when `passwd` fails (e.g. entered the password wrong on the second time) by invoking `passwd` again.
`setup-user` doesn't do that and continues even if a password is basically not set by `passw...`setup-alpine` asks for the password again when `passwd` fails (e.g. entered the password wrong on the second time) by invoking `passwd` again.
`setup-user` doesn't do that and continues even if a password is basically not set by `passwd`.
Allowing password setup retries means you don't have to setup the user password(s) after finishing `setup-alpine`.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10566setup-acf: Still install lua5.2 instead of lua5.4 package2023-12-01T13:43:10ZTony Bonninsetup-acf: Still install lua5.2 instead of lua5.4 packageHi,
On a fresh **Alpine 3.18.3** install, when `setup-acf` script call, it's installing lua5.2 package.
Don't understanding why since [Merge !48421](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/48421)
ThxHi,
On a fresh **Alpine 3.18.3** install, when `setup-acf` script call, it's installing lua5.2 package.
Don't understanding why since [Merge !48421](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/48421)
Thxhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10560update-kernel: pull-in latest wireless-regdb ?2023-11-29T17:47:34Zmacmpiupdate-kernel: pull-in latest wireless-regdb ?`update-kernel` takes care to install current `regulatory.db` into `modloop`:\
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/update-kernel.in#L321-326
However, it does not seem to pull-in latest `wireless-regdb` packag...`update-kernel` takes care to install current `regulatory.db` into `modloop`:\
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/update-kernel.in#L321-326
However, it does not seem to pull-in latest `wireless-regdb` package before, while it does for `linux-firmware` to get latest:\
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/update-kernel.in#L268 \
Shouldn't `wireless-regdb` be added in that install package list?
Thanks for consideration.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10570ethernet does not work anymore work for imx6(amrv7), start with alpine 3.152023-11-16T06:38:48ZGwen Lgethernet does not work anymore work for imx6(amrv7), start with alpine 3.15Hello,
I have tried to use alpine linux on my Wandboard Quad and Cubox-i (Both have a imx6 SOC).
The Ethernet connection worked well with Alpine 3.14.2, and no longer work since Alpine 3.15 (both with a new image, and after an update fr...Hello,
I have tried to use alpine linux on my Wandboard Quad and Cubox-i (Both have a imx6 SOC).
The Ethernet connection worked well with Alpine 3.14.2, and no longer work since Alpine 3.15 (both with a new image, and after an update from 3.14.2). And it still doesn't work with version 3.18.
The Ethernet hardware is correctly detected, the kernel driver (fec) seems to work correctly.
But, I am neither able to have an address by dhcp nor able to ping with a manually configured address.
While I'm able to have a working wifi connection with Alpine 3.18.4 on Wandboard, and able to have Ethernet connection with Armbian 23.08.1 with cubox-i.
I'm not expert, but I tried to :
- compare result of commands like lshw, ethtool and lsmod between alpine version, without seeing relevant information.
- look at dmesg output without seeing info about a problem.
Someone can help me to investigate more ?
Thank you.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10533update-kernel: fails with modinfo returning wildcarded firmware names2023-10-03T16:16:31Zmacmpiupdate-kernel: fails with modinfo returning wildcarded firmware namesSummarizing a long thread https://gitlab.alpinelinux.org/alpine/aports/-/issues/13302#note_259618, and landing resulting core issue where it should pertain, so that it does not fall aside.
While building modloop, firmware names extracte...Summarizing a long thread https://gitlab.alpinelinux.org/alpine/aports/-/issues/13302#note_259618, and landing resulting core issue where it should pertain, so that it does not fall aside.
While building modloop, firmware names extracted from `modinfo -F firmware` may contain `$FW` names with wildcards.\
`update-kernel` then does not process these as [`if [ -e "$ROOT/lib/firmware/$FW" ]`](https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/update-kernel.in#L298-306) statement fails with * wildcards.
An sample real-life consequence of this is Alpine failing to incorporate PiZero2W firmware file within Releases modloop.\
This may silently happen too for some other drivers...https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10567setup-apkrepos: wget: error getting response: Connection reset by peer2023-09-03T12:49:27ZThomas Anderson9rcevh0s@anonaddy.mesetup-apkrepos: wget: error getting response: Connection reset by peerPlease see below output on a Raspberry Pi 3 freshly installed with aarch64:
Different destinations on the internet can be pinged, however.
```shell
alpine-headless:~# setup-apkrepos
6030439C7F000000:error:0A000086:SSL routines:tls_pos...Please see below output on a Raspberry Pi 3 freshly installed with aarch64:
Different destinations on the internet can be pinged, however.
```shell
alpine-headless:~# setup-apkrepos
6030439C7F000000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889:
ssl_client: SSL_connect
wget: error getting response: Connection reset by peer
608042AD7F000000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889:
ssl_client: SSL_connect
wget: error getting response: Connection reset by peer
r) Add random from the above list
f) Detect and add fastest mirror from above list
e) Edit /etc/apk/repositories with text editor
Enter mirror number (1-0) or URL to add (or r/f/e/done) [1]
```
```shell
alpine-headless:~# uname -a
Linux alpine-headless 6.1.43-0-rpi #1-Alpine SMP PREEMPT Mon Aug 7 12:41:27 UTC 2023 aarch64 Linux
```
I haven't adjusted / moved the files into the proper partitions yet as described here: https://wiki.alpinelinux.org/wiki/Classic_install_or_sys_mode_on_Raspberry_Pi#Installation
However it should work nevertheless IMHO.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10554setup-repos sets wrong repositories2023-08-28T06:52:31ZHGpunktTsetup-repos sets wrong repositoriesWhen bootet via netboot from
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/vmlinuz-lts
with
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/initramfs-lts
`# setup-apkrepos`
inserts repositor...When bootet via netboot from
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/vmlinuz-lts
with
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/initramfs-lts
`# setup-apkrepos`
inserts repository names from **edge** and not from **v3.17** into `/etc/apk/repositories`Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10558setup-interfaces: when cannot install wpa_supplicant, mention extended images2023-08-23T00:51:46ZPatrycja Rosaalpine@ptrcnull.mesetup-interfaces: when cannot install wpa_supplicant, mention extended imagescurrently, when `apk add wpa_supplicant` fails, the script just returns from the function; if the user picked the standard image, it would be nice to mention that they can only use wired connections and if they need wifi, that's included...currently, when `apk add wpa_supplicant` fails, the script just returns from the function; if the user picked the standard image, it would be nice to mention that they can only use wired connections and if they need wifi, that's included in the extended onehttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10562`setup-alpine`: root passwords don't match2023-05-10T17:32:02ZIlya Petrov`setup-alpine`: root passwords don't matchAlpine version: 3.18.0 (Released May 09, 2023) for x86_64.
I run:
```sh-session
# setup-alpine
...
Changing password for root
# New password:
# Retype password:
Passwords don't match
```
The password I try to input is: `!5$1p!n#(&34+`.
...Alpine version: 3.18.0 (Released May 09, 2023) for x86_64.
I run:
```sh-session
# setup-alpine
...
Changing password for root
# New password:
# Retype password:
Passwords don't match
```
The password I try to input is: `!5$1p!n#(&34+`.
It never matches.
Simpler passwords (`12345`) match successfully.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10557setup-disk: fails when wanting to use two disks in raid1 with gpt partitionin...2023-05-02T16:27:46Zraspbeguysetup-disk: fails when wanting to use two disks in raid1 with gpt partitioning on legacy bios bootHello, I am trying to install alpine on a remote server which has two 3TB disks that are supposed to work in softraid array. The servers can only boot in legacy bios mode.
I ran:
```
export DISKLABEL=gpt
setup-alpine
```
At the `setup...Hello, I am trying to install alpine on a remote server which has two 3TB disks that are supposed to work in softraid array. The servers can only boot in legacy bios mode.
I ran:
```
export DISKLABEL=gpt
setup-alpine
```
At the `setup-disk` step I entered `sda sdb` and mode `sys`.
I always have this error:
```
mount: mounting /dev/sda on /mnt/boot failed: Resource busy
```https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10559Install fail as /boot is too big2023-04-22T13:48:41ZJean-RochInstall fail as /boot is too bigThis is for installation on local disk from alpine-virt-3.17 ISO\
The local disk is 500Mb
The setup-alpine is crashing complaining lack of free space, because the partition for /boot is set to 300Mb, using most of the disk\
In real life...This is for installation on local disk from alpine-virt-3.17 ISO\
The local disk is 500Mb
The setup-alpine is crashing complaining lack of free space, because the partition for /boot is set to 300Mb, using most of the disk\
In real life files on /boot only using 19Mb\
19 Mb / 100 Mb = 20% usage\
19 Mb / 300 Mb = 7% usage
Could the default size for /boot set back to 100M ?\
As it was for 3.16 ans earlier, which is 5x more than the real usage.
I tried with variable BOOT_SIZE, but it also fail saying the minimal must be 300Mhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10536Issue with boot partition sizing for UEFI installs2023-04-22T13:24:44ZDermot BradleyIssue with boot partition sizing for UEFI installssetup-disk sets the bootpartition to be 34MB in size when installing on a UEFI system with a 512byte sector size drive (HDD or SSD): https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L1602-1608
This appear to...setup-disk sets the bootpartition to be 34MB in size when installing on a UEFI system with a 512byte sector size drive (HDD or SSD): https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L1602-1608
This appear to be ok for a basic UEFI Sys-mode disk installation as the 34MB boot partition is actually the UEFI ESP partition, is mounted as /boot/efi and only holds the EFI related files (and so only uses approx 1MB of the 34MB).
However there is a problem with UEFI LUKS Sys-mode disk installations as the 34MB boot partition is used as *both* the ESP partition and also for holding the /boot files (kernel, initramfs, microcode, etc). Whilst such an installation may complete without filling the boot partition and then machine run fine whenever mkinitfs is triggered to build an updated initramfs file the boot partition runs out of space.
The same disk space issue may apply if UEFI is used via EFISTUB (rather than Grub) where a larger EFI file will be created (illustrated by !106), and may also apply if many of the linux-firmware-* packages are installed (and so initramfs grows in size accordingly)
I see the issue as being due to a 'confusion' between the purpose of a ESP partition, the purpose of a boot partition, and the use of a single partition for both purposes. The contents of a "pure" ESP partition are somewhat static (just Grub EFI in most cases, though a custom EFISTUB file in other, currently not supported by setup-disk, cases).
There are 2 solutions, either (a) have separate ESP and boot partitions and size them accordingly, or (b) have a single "boot" partition which is sufficiently larger than 34MB to ensure that there is adequate excessive space unused for kernel upgrades/firmware-in-initramfs/mkinitfs temporary usage/EFISTUB files).
Which ever solution is decided upon should be backported to Alpine 3.16.Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10555grub-efi install failed with 3.17-virt iso2023-03-24T14:52:02ZPikuZhenggrub-efi install failed with 3.17-virt isoI try to install alpine using the following command:
```
mkfs.ext4 /dev/sda3
mkswap /dev/sda2
mkdosfs /dev/sda1
mount -t ext4 /dev/sda3 /mnt
mkdir -p /mnt/boot/efi
mount -t msdos /dev/sda1 /mnt/boot/efi
swapon /dev/sda2
BOOTLOADER=grub...I try to install alpine using the following command:
```
mkfs.ext4 /dev/sda3
mkswap /dev/sda2
mkdosfs /dev/sda1
mount -t ext4 /dev/sda3 /mnt
mkdir -p /mnt/boot/efi
mount -t msdos /dev/sda1 /mnt/boot/efi
swapon /dev/sda2
BOOTLOADER=grub
USE_EFI=1
setup-disk -m sys /mnt
```
but it gives an error:
```
grub-install: error: failed to get canonical path of `'.
install: can't stat '/EFI/alpine/grubx64.efi': No such file or directory
```
This method is feasible in both alpine-virt-3.15.7-x86_64.iso and alpine-standard-3.17.2-x86_64.iso, but not alpine-virt-3.17.2-x86_64.iso.
anything I missed?Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10546setup-interfaces - parsing iw scan broken (alpine 3.17)2023-02-10T15:36:44Zph1ltersetup-interfaces - parsing iw scan broken (alpine 3.17)My WiFi SSID does not appear in the list given by **setup-interfaces**, and I am forbidden to enter a name which is not in that list.
## summary
The reason: A line `SSID List` in the `iw scan` output causes the awk pattern matching to f...My WiFi SSID does not appear in the list given by **setup-interfaces**, and I am forbidden to enter a name which is not in that list.
## summary
The reason: A line `SSID List` in the `iw scan` output causes the awk pattern matching to fail.
The awk pattern can be fixed to solve the problem (see below)
## Details
In the script `setup-interfaces` in the function **find_essids()** a call to `(iw dev wlan0 scan; echo BSS)` is passed to **awk -F ": "**.
This awk line causes the problem. Ideally it would match **SSID:** (with colon) but it cannot since $1 is split on colon `awk -F ": "`.
```
$1 ~ /SSID/ { ssid=$2 }
```
Instead we can match on $0 and add the colon to the pattern.
```
$0 ~ /SSID:/ { ssid=$2 }
```
This problematic scan output contains line `SSID List` which confuses the awk SSID check.
```
BSS xxxxx
...
SSID: NeverSeen
...
Extended capabilities:
* TFS
* WNM-Sleep Mode
* TIM Broadcast
* BSS Transition
* SSID List
* Operating Mode Notification
...
* Authentication suites: PSK
```