alpine-conf issueshttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues2023-03-30T01:43:12Zhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10556TUI with dialog2023-03-30T01:43:12ZDrSheppardTUI with dialogTerminal user interface help newbies install alpine in interactive mode. It will also help to attract new usersTerminal user interface help newbies install alpine in interactive mode. It will also help to attract new usershttps://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/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/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/10552issues with alpine on a micro sd card2023-05-02T16:35:30ZGhost Userissues with alpine on a micro sd cardI'm trying to install alpine linux to a micro sd card through an hp elitebook 810 revolve g3, but couldn't find my home network. Other networks were still available, and I was eventually able to get through setup-alpine once I connected ...I'm trying to install alpine linux to a micro sd card through an hp elitebook 810 revolve g3, but couldn't find my home network. Other networks were still available, and I was eventually able to get through setup-alpine once I connected to my campus's public network.
I couldn't however boot into it without using an adapter and usb reader, despite the laptop having a dedicated micro sd card slot and having enabled sd card boot in the bios. I didn't have any issue booting into the live iso through the laptop's dedicated slot.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10551Support gummiboot as EFI bootloader2023-02-09T16:50:10ZPatrycja Rosaalpine@ptrcnull.meSupport gummiboot as EFI bootloaderit's more lightweight than grub, is in main already and its config wouldn't be hard to implementit's more lightweight than grub, is in main already and its config wouldn't be hard to implementhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549Make ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILE2023-02-02T23:07:16ZRogério da Silva YokomizoMake ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILEOn `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab...On `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-disk.in#L866
It would be nice to be able to set `ERASE_DISK` via `USEANSERFILE`.
```
setup-alpine -f ANSWERS
# ANSWERS file
ERASE_DISK=/dev/sda # <---- Does not pass through from setup-alpine into setup-disk
DISKOPTS="-m sys /dev/sda"
```
Since it is possible to define `DISKOPTS` via `USEANSERFILE`, I see no reason why `ERASE_DISK` could not be exported/forwarded. I could send a patch for this.
relevant lines:
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L72
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L263https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10548setup-apkrepos: version detection for edge2023-01-26T09:31:38ZWilliam Wilhelmsetup-apkrepos: version detection for edge`setup-apkrepos` currently looks at `/etc/alpine-release` to determine the version to use when adding repositories. However the edge package of alpine-base will contain a "release" version sometimes, currently it is `3.17.0`. This causes...`setup-apkrepos` currently looks at `/etc/alpine-release` to determine the version to use when adding repositories. However the edge package of alpine-base will contain a "release" version sometimes, currently it is `3.17.0`. This causes `setup-apkrepos` to add `v3.17.0` repositories, even if the system is on edge. How can we improve the detection? Would checking the existing `/etc/apk/repositories` file for the `main` version be better?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10547setup-alpine: downloading answer file broken2023-01-25T14:46:20ZWilliam Wilhelmsetup-alpine: downloading answer file brokenSince 3114f2ed9b1cffe25a0d48d8ee8b64445e1688f4, specifying a http/https/ftp URL for the answer file doesn't work anymore.Since 3114f2ed9b1cffe25a0d48d8ee8b64445e1688f4, specifying a http/https/ftp URL for the answer file doesn't work anymore.https://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
```https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10545update-kernel: does not update successfully on Pi / diskless2022-12-09T09:20:59Zmacmpiupdate-kernel: does not update successfully on Pi / disklessJust tried to update kernel on a 3.17 PiZero in diskless setup (ref https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10470). \
(release is on kernel 5.15.79, linux-rpi 5.15.81 is available in main)\
All seems to work fine, unti...Just tried to update kernel on a 3.17 PiZero in diskless setup (ref https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10470). \
(release is on kernel 5.15.79, linux-rpi 5.15.81 is available in main)\
All seems to work fine, until:\
`umount: can't unmount /.modloop: Resource busy`\
no other errors reported.
In the end produced files **do not land** in `/media/mmcblk0p1/boot` which remains with original files: produced files are not copied-over...
No report of failing copies either.
Was executed as `root`, with `TMPDIR="/media/spare/SPARE" update-kernel`, and `/media/mmcblk0p1` was remounted `rw` before (just in case script under-looks it).
Thoughts?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10544setup-desktop: run automatically during setup-alpine2023-12-01T15:18:44ZPatrycja Rosaalpine@ptrcnull.mesetup-desktop: run automatically during setup-alpinecurrently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an ...currently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an option to not install any desktop at allhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10543setup-interfaces: allow for picking the wireless network by list index number2022-11-21T15:01:03ZPatrycja Rosaalpine@ptrcnull.mesetup-interfaces: allow for picking the wireless network by list index numbersometimes typing the full network name can be a bit annoying, it would be nice if users were presented with an indexed list, like in setup-apkrepos where you can just enter the number instead of the namesometimes typing the full network name can be a bit annoying, it would be nice if users were presented with an indexed list, like in setup-apkrepos where you can just enter the number instead of the namehttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10542setup-interfaces: do not touch existing setup if user chooses "done"2022-11-22T10:48:57Zmacmpisetup-interfaces: do not touch existing setup if user chooses "done"In interactive mode, user may not want to alter settings and will enter "done" on first question (typical on headless setup, with working network settings).\
Currently, hitting "done" overwrites eventually existing `/etc/network/interfac...In interactive mode, user may not want to alter settings and will enter "done" on first question (typical on headless setup, with working network settings).\
Currently, hitting "done" overwrites eventually existing `/etc/network/interfaces` with default loopback entry.\
Restarting interfaces then just kills the existing connection and abort all setup process.
Can we keep (pre)existing `/etc/network/interfaces` if user select `done` right-away on first question?\
Thanks for consideration.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10541linux-firmware-b43 (no such package)2022-11-14T09:29:00ZCarlo Corradinilinux-firmware-b43 (no such package)I'm trying to install alpine `base` (standard) on an old MacBook Pro.
However, it fails during `setup-disk` (after selecting `sda` and `SYS`):
```sh
Installing system on /dev/sda3:
Installing for x86_64-efi platform.
Installation finishe...I'm trying to install alpine `base` (standard) on an old MacBook Pro.
However, it fails during `setup-disk` (after selecting `sda` and `SYS`):
```sh
Installing system on /dev/sda3:
Installing for x86_64-efi platform.
Installation finished. No error reported.
ERROR: unable to select packages:
linux-firmware-b43 (no such package):
required by: world[linux-firmware-b43]
```
I've tried to solve it, but unsuccessfully.
Note that I need only Ethernet and not any Wi-Fi, so if possible, I can skip it.
Any help is appreciated. Thanks!https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10540Alpine 3.16.2 setup-disk fails to create config.txt and cmdline.txt on Raspbe...2022-11-11T15:06:49ZThomas ZemanAlpine 3.16.2 setup-disk fails to create config.txt and cmdline.txt on Raspberry PIWhen executing setup-disk on a Raspberry PI with a mount point as parameter (/mnt below), the script shows the following two error messages:
Installing system on /dev/mmcblk0p2:
/sbin/setup-disk: line 469: can't create /mnt/boot/config....When executing setup-disk on a Raspberry PI with a mount point as parameter (/mnt below), the script shows the following two error messages:
Installing system on /dev/mmcblk0p2:
/sbin/setup-disk: line 469: can't create /mnt/boot/config.txt: nonexistent directory
/sbin/setup-disk: line 470: can't create /mnt/boot/cmdline.txt: nonexistent directory
This happens because the function setup_raspberrypi_bootloader() in setup-disk assumes the mount point has a /boot directory which is not guaranteed to be there.
Proposed fix: The function needs to create the directory first.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10539Linux kernel file permission denied during install of 3.16.22022-11-08T17:09:30ZAaron MasonLinux kernel file permission denied during install of 3.16.2![image](/uploads/5179fcba0b128c3e71f20091ae941b27/image.png)
Nothing special was done during the install that I can think of that caused this. This occurred in a Hyper-V virtual machine, if that makes a difference.
/mnt/boot only has ...![image](/uploads/5179fcba0b128c3e71f20091ae941b27/image.png)
Nothing special was done during the install that I can think of that caused this. This occurred in a Hyper-V virtual machine, if that makes a difference.
/mnt/boot only has the extlinux files, no kernel files are there.
![image](/uploads/ebfa2f7ca1675408e97e8ae63751b6ca/image.png)https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10538ls displays an error if listing sub-timezones and user entered directory with...2022-11-08T17:06:34ZCarl Chavels displays an error if listing sub-timezones and user entered directory without trailing slashFor example:
```
Which timezone are you in? ('?' for list) [UTC] Europe
What sub-timezone of 'Europe' are you in? ('?' for list) ?
ls: Europe/: No such file or directory
Amsterdam Bratislava Dublin Kaliningrad Luxembourg N...For example:
```
Which timezone are you in? ('?' for list) [UTC] Europe
What sub-timezone of 'Europe' are you in? ('?' for list) ?
ls: Europe/: No such file or directory
Amsterdam Bratislava Dublin Kaliningrad Luxembourg Nicosia Samara Stockholm Vatican Zurich
Andorra Brussels Gibraltar Kiev Madrid Oslo San_Marino Tallinn Vienna
Astrakhan Bucharest Guernsey Kirov Malta Paris Sarajevo Tirane Vilnius
Athens Budapest Helsinki Kyiv Mariehamn Podgorica Saratov Tiraspol Volgograd
Belfast Busingen Isle_of_Man Lisbon Minsk Prague Simferopol Ulyanovsk Warsaw
Belgrade Chisinau Istanbul Ljubljana Monaco Riga Skopje Uzhgorod Zagreb
Berlin Copenhagen Jersey London Moscow Rome Sofia Vaduz Zaporozhye
```
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-timezone.in#L32
could be changed to add a slash after $path:
```
for i in $(find $path/ -maxdepth 1); do
```
Which fixes it in my testing.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10537soundcard not detected by kernel2022-10-05T06:15:25ZDocbrokesoundcard not detected by kernelThis issue is with my new MSI modern 14, (core i7 + nvidia geforce mx450) laptop. I am having dual boot setup, alpine and archlinux. In arch linux soundcard is detected and works but it is not detected by alpine kernel.
With alpine
```
...This issue is with my new MSI modern 14, (core i7 + nvidia geforce mx450) laptop. I am having dual boot setup, alpine and archlinux. In arch linux soundcard is detected and works but it is not detected by alpine kernel.
With alpine
```
[sharad@msi-end][~/Data]
[ins]$ cat sound.log
[sharad@sdalpine][~]
[ins]$ aplay -l
aplay: device_list:275: no soundcards found...
[sharad@sdalpine][~]
[ins]$ pinxi -A
Audio: Message: No PCI card data found. [/code]
```
with archlinux
```
[sharad@msi-end][~]
[ins]$ pinxi -A
Audio: Card-1: Intel Tiger Lake-LP Smart Sound Audio Controller
driver: sof-audio-pci-intel-tgl
Sound Server: ALSA v: k5.15.71-1-lts
[sharad@msi-end][~]
[ins]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 31: HDA Analog Deep Buffer (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
```https://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 Copa