aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2021-01-18T08:40:55Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11153linux-lts: black screen after resume2021-01-18T08:40:55Zvoroskoilinux-lts: black screen after resumeHi,
I am running latest-stable. After upgrading linux-lts to 5.4.8 suspend/resume does not work as expected: screen remains black, i can only switch off my laptop and reboot.
I can confirm the same behavior with linux-lts-5.4.12.
Downg...Hi,
I am running latest-stable. After upgrading linux-lts to 5.4.8 suspend/resume does not work as expected: screen remains black, i can only switch off my laptop and reboot.
I can confirm the same behavior with linux-lts-5.4.12.
Downgrading to 5.4.6 and rebooting fixes the issue.
Video card:
```
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller])
DeviceName: 32
Subsystem: Hewlett-Packard Company Device [103c:172a]
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 5058 [size=8]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
```
Let me know if I can provide any useful additional info!
Thankshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12098targetcli missing kernel modules dependencies on alpine-virt2021-07-06T21:37:35ZNir Soffertargetcli missing kernel modules dependencies on alpine-virtI'm trying to build a minimal storage appliance for testing
purposes using alpine-virt. The use case is setting up a temporary
throwaway storage server vm for a test run, run tests, and delete
the vm and the storage created during the te...I'm trying to build a minimal storage appliance for testing
purposes using alpine-virt. The use case is setting up a temporary
throwaway storage server vm for a test run, run tests, and delete
the vm and the storage created during the test.
Steps to reproduce:
1. Install alpine-virt-3.12.1-x86_64.iso
2. Enable the http://dl-cdn.alpinelinux.org/alpine/v3.12/community repository
3. Install targetcli according to https://wiki.alpinelinux.org/wiki/Linux_iSCSI_Target_(TCM)
4. Start targetcli
```
# targetcli ls
b'modprobe: FATAL: Module iscsi_target_mod not found in directory /lib/modules/5.4.72-0-virt\n'
```
Looking in /lib/modules, we have only target_core module:
```
# ls /lib/modules/5.4.72-0-virt/kernel/drivers/target/
target_core_mod.ko
```
On another system installed from alpine-standard-3.12.1-x86_64.iso we have:
```
# ls /lib/modules/5.4.72-0-lts/kernel/drivers/target/
iscsi target_core_file.ko target_core_pscsi.ko
loopback target_core_iblock.ko target_core_user.ko
sbp target_core_mod.ko tcm_fc
```
Looking at /boot/config-virt
```
CONFIG_TARGET_CORE=m
# CONFIG_TCM_IBLOCK is not set
# CONFIG_TCM_FILEIO is not set
# CONFIG_TCM_PSCSI is not set
# CONFIG_LOOPBACK_TARGET is not set
# CONFIG_ISCSI_TARGET is not set
```
Looks like targetcli needs to depend on the linux-lts package,
or maybe the target modules should be part of another package?
After:
```
apk add linux-lts
apk del linux-virt
reboot
```
targetcli works, but it looks mostly like alpine-standard install.
In particular it seems to have additional 550 MiB in /lib/firmware
that I probably do not need in a vm.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12157When installing new kernel, please don't delete old modules2023-05-19T12:49:24ZjujuWhen installing new kernel, please don't delete old modulesWhen apk update installs a new kernel, old modules in /lib/modules got deleted.
This may make the system unbootable if:
* You want to boot with the old kernel
* You are not booting from /boot, ie with rEFInd from another place
Pleas...When apk update installs a new kernel, old modules in /lib/modules got deleted.
This may make the system unbootable if:
* You want to boot with the old kernel
* You are not booting from /boot, ie with rEFInd from another place
Please keep the old files in /lib/modules and warn user to clean it up instead.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12751Module request: snd-cs42362021-11-05T17:11:44ZBrian WhiteModule request: snd-cs4236I've recently installed Alpine on some old hardware that has some onboard audio. Unfortunately while Alpine has kernel modules for other Cirrus Logic chipsets, snd-cs4236 is not one of them and is what my motherboard uses. I know the aud...I've recently installed Alpine on some old hardware that has some onboard audio. Unfortunately while Alpine has kernel modules for other Cirrus Logic chipsets, snd-cs4236 is not one of them and is what my motherboard uses. I know the audio works well under Linux (using buildroot for example), so it'd be great to have this available in Alpine out of the box.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12971Kernel segfault when probing VIA VT6122 10/100/1000 driver2024-01-30T12:43:30ZJ RBKernel segfault when probing VIA VT6122 10/100/1000 driverAttempting to install Alpine-3.14.2 via USB always resulted in a kernel panic ( https://imgur.com/a/9vAaePD)
downloaded 3.12.8 and successfully booted, installed, rebooted.
change the repositories to use 3.14 and upgraded on-disk insta...Attempting to install Alpine-3.14.2 via USB always resulted in a kernel panic ( https://imgur.com/a/9vAaePD)
downloaded 3.12.8 and successfully booted, installed, rebooted.
change the repositories to use 3.14 and upgraded on-disk install, rebooted and again experienced a kernel panic.
edited boot parameters at grub to include init=/bin/ash and booted to edit /etc/rc.conf to enable interactive mode.
In doing so, aspects of networking, especially probing the associated driver, result in a kernel panic.
via-velocity is the module associated with the onboard VIA VT6122 Gigabit Ethernet controller.
Re-installing with 3.12.8 for nowNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13157Kernel: Add support for various RK3399 based devices2023-11-19T22:10:21ZLogan GKernel: Add support for various RK3399 based devicesI think it would be nice if you could boot vanilla Alpine on the large amount RK3399 based boards. The majority of these boards already have mainline support and can be booted from a mainline kernel with the default arm64 config. However...I think it would be nice if you could boot vanilla Alpine on the large amount RK3399 based boards. The majority of these boards already have mainline support and can be booted from a mainline kernel with the default arm64 config. However they do not seem to work with Alpine's kernel config, although the DTBs are there.
I messed around for a bit on my Rock Pi 4, and one of the issues on it seems to be that the RK808 related flags are not enabled. After enabling these, the kernel finally booted but the uSD slot did not work, nor did the HDMI video output. I'm not sure why though. After testing on mainline's default config, everything works as expected.
This would likely help vanilla Alpine run on:
- Radxa Rock Pi 4 (A/B/C)
- Orange Pi 4
- Pine64 RockPRO64
- Pine64 PinePhone Pro
- Pine64 PineBook Pro
- Firefly-RK3399
- ASUS Tinker Board 2
- NanoPC T4
- Others that I can't think of
Most of these boards from what I can gather have fairly similar hardware, so in theory supporting even one of these would likely accidentally make others work as well.Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13588linux-edge: enable Landlock2022-11-26T16:07:12ZMickaël Salaünlinux-edge: enable LandlockHi!
Could you please enable Landlock in the kernel? It enables to sandbox applications and is available since Linux 5.13. See https://landlock.io for presentations and useful links, linux-lts changes (https://gitlab.alpinelinux.org/alpi...Hi!
Could you please enable Landlock in the kernel? It enables to sandbox applications and is available since Linux 5.13. See https://landlock.io for presentations and useful links, linux-lts changes (https://gitlab.alpinelinux.org/alpine/aports/-/commit/b49410ac39b3c9ef46434b9d5daa79f2c845015e), related merge request (https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/31556) and related issue (https://gitlab.alpinelinux.org/alpine/aports/-/issues/13572).
Cc @mpsMilan P. StanićMilan P. Stanićhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13841linux-lts: Power off hangs in qemu-system-arm with the linux-virt armv7 kernel2023-05-12T12:01:00ZNatanael Copalinux-lts: Power off hangs in qemu-system-arm with the linux-virt armv7 kernelTo reproduce:
```
qemu-system-arm -M virt -m 512M -cpu cortex-a7 \
-drive if=pflash,format=raw,file=/usr/share/qemu/edk2-arm-code.fd,readonly=on \
-drive if=virtio,file=alpine-virt-3.16.0_rc5-armv7.iso \
-serial stdio
```
When pow...To reproduce:
```
qemu-system-arm -M virt -m 512M -cpu cortex-a7 \
-drive if=pflash,format=raw,file=/usr/share/qemu/edk2-arm-code.fd,readonly=on \
-drive if=virtio,file=alpine-virt-3.16.0_rc5-armv7.iso \
-serial stdio
```
When powering it off it hangs:
```
* Terminating remaining processes ...[ 49.127699] reboot: System halted
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/14306pkcs8_key_parser kernel module is missing2022-11-11T08:32:01ZMartin Ruskopkcs8_key_parser kernel module is missingHello,
would it be possible to set CONFIG_PKCS8_PRIVATE_KEY_PARSER for the future kernel builds, please? Without that IWD daemon is not able to read keys.
Thanks and Regards,
MartinHello,
would it be possible to set CONFIG_PKCS8_PRIVATE_KEY_PARSER for the future kernel builds, please? Without that IWD daemon is not able to read keys.
Thanks and Regards,
MartinNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14407Installer: installer not booting in Apple's Virtualization.framework virtual ...2023-03-26T04:23:32ZCatherine KellyInstaller: installer not booting in Apple's Virtualization.framework virtual machines## Description
The installer does not boot in virtual machines built with macOS Virtualization.framework.
## Version
3.17.0 Virt, 3.17.0 Standard
## Arch
Aarch64
## Host OS
macOS 13.0.1 (aarch64)
## Expected behavior
The installer bo...## Description
The installer does not boot in virtual machines built with macOS Virtualization.framework.
## Version
3.17.0 Virt, 3.17.0 Standard
## Arch
Aarch64
## Host OS
macOS 13.0.1 (aarch64)
## Expected behavior
The installer booted successfully.
## Actual behavior
After selecting "Linux virt" in GRUB, the screen freezes.
## Possibly related to
https://gitlab.alpinelinux.org/alpine/aports/-/issues/13120
## Additional information
RHEL / CentOS / Alma Linux, Fedora, Arch Linux ARM, Ubuntu installer boots.
The `virtio_console`, `virtio_gpu` kernel modules are not included in the installer.
`virtio_blk` and `virtio_dma_buf` are not loaded upon boot.
The CPU usage goes to 100%. (possibly the kernel panicked?)
A sample Virtualization.framework project can be found at [Running GUI Linux in a virtual machine on a Mac](https://developer.apple.com/documentation/virtualization/running_gui_linux_in_a_virtual_machine_on_a_mac).Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15173Enable CONFIG_DYNAMIC_DEBUG on linux-edge2023-08-07T17:08:43ZNico SchotteliusEnable CONFIG_DYNAMIC_DEBUG on linux-edgeI was wondering whether we can enable CONFIG_DYNAMIC_DEBUG on linux-edge?
linux-lts has it and its very valuable for debugging, -edge does not have it atmI was wondering whether we can enable CONFIG_DYNAMIC_DEBUG on linux-edge?
linux-lts has it and its very valuable for debugging, -edge does not have it atmMilan P. StanićMilan P. Stanićhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15351move linux-edge to testing2023-10-28T17:18:34ZMilan P. Stanićmove linux-edge to testingany objection?any objection?3.19.0Milan P. StanićMilan P. Stanićhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15706Release images does not boot from NVMe2024-01-22T18:01:41ZFilippo ValsordaRelease images does not boot from NVMeTo allow booting a diskless/data/setup-bootable setup from a NVMe drive, `CONFIG_BLK_DEV_NVME=y` needs to be set in the kernel config, as modules have to be loaded from the NVMe drive itself.
See for example the equivalent change in ras...To allow booting a diskless/data/setup-bootable setup from a NVMe drive, `CONFIG_BLK_DEV_NVME=y` needs to be set in the kernel config, as modules have to be loaded from the NVMe drive itself.
See for example the equivalent change in raspberrypi/linux: https://github.com/raspberrypi/linux/issues/4163Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15756Compress linux-firmware packages2024-03-10T10:49:54ZNewbyteCompress linux-firmware packagesCurrently, installing all linux-firmware packages results in a `/lib/firmware` directory which is around 1,0 GB in size. This could be significantly smaller if we started compressing firmware during packaging. The Linux kernel has suppor...Currently, installing all linux-firmware packages results in a `/lib/firmware` directory which is around 1,0 GB in size. This could be significantly smaller if we started compressing firmware during packaging. The Linux kernel has supported loading compressed firmware since version 5.3 and other distributions such as Fedora and Arch Linux have already implemented this successfully. In Fedora, for example, at the time of writing the entire `/lib/firmware` directory is a more modest 238 MB.
There are some problems however. Not all firmware can be compressed, so exceptions would have to be made on a per-file basis. In particular, firmware served to certain remote processors on Qualcomm devices cannot be compressed at the moment as the serving happens in userspace rather than kernelspace. There may also be other necessary exceptions, so this would require extensive testing to avoid breakage. As other distributions already have implemented this, we could investigate what files (if any) they exempt as a start. However, their lists may not be complete as it is unlikely that they've tested more obscure ARM hardware.Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15757rtl8723bs_nic.bin is missing from alpine-standard-3.19.0-x86_64.iso 's modloop.2024-03-01T00:48:53ZEric Toombsrtl8723bs_nic.bin is missing from alpine-standard-3.19.0-x86_64.iso 's modloop.It has meant that my computer's wifi wouldn't work on boot.
I had to add the firmware file to the modloop squashfs image myself.
I don't know how this happened.
The firmware file is in [the linux-firmware-rtlwifi package](https://pkgs.a...It has meant that my computer's wifi wouldn't work on boot.
I had to add the firmware file to the modloop squashfs image myself.
I don't know how this happened.
The firmware file is in [the linux-firmware-rtlwifi package](https://pkgs.alpinelinux.org/contents?file=&path=&name=linux-firmware-rtlwifi&branch=v3.19&repo=main&arch=x86_64).
(I would have installed linux-firmware-rtlwifi, but the /lib/firmware directory was read-only, so the apk add command failed.)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15772Enable UFSHCD and UFSHCD_PCI2024-02-23T15:22:01ZM HEnable UFSHCD and UFSHCD_PCII'm running Alpine LTS on a Microsoft Surface Go 4. SG4 uses Universal Flash Storage for storage and with the current kernel it is possible to install Alpine, but Alpine fails to boot after installation due to missing support for UFS. I ...I'm running Alpine LTS on a Microsoft Surface Go 4. SG4 uses Universal Flash Storage for storage and with the current kernel it is possible to install Alpine, but Alpine fails to boot after installation due to missing support for UFS. I complied a custom kernel with `UFSHCD` and `UFSHCD_PCI` enabled, and dependencies suggested by `menuconfig`. I was able to boot the installation with the custom kernel. Would it be possible to enable `UFSHCD` and `UFSHCD_PCI` for the x86_64 Alpine kernel?Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15867Differences between drbd utils and kernel module versions2024-03-14T10:30:46ZmikeisitDifferences between drbd utils and kernel module versionsI using v3.19.1
Differences between drbd utils and kernel module versions
The drbd kernel module version is 8.4.11, but drbd-utils is 9.26.0
These two versions are not compatible with each otherI using v3.19.1
Differences between drbd utils and kernel module versions
The drbd kernel module version is 8.4.11, but drbd-utils is 9.26.0
These two versions are not compatible with each otherNatanael CopaNatanael Copa