aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2019-07-12T14:22:55Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/87include cciss driver in initramfs2019-07-12T14:22:55ZNatanael Copainclude cciss driver in initramfswe add it to /etc/mkinitfs/modules.d/raid
*(from redmine: issue id 87, created on 2009-07-24, closed on 2009-07-30)*we add it to /etc/mkinitfs/modules.d/raid
*(from redmine: issue id 87, created on 2009-07-24, closed on 2009-07-30)*Alpine 1.9 betaNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/93we need store root_size in apkovl2019-07-12T14:22:58ZNatanael Copawe need store root_size in apkovlwould be nice to be able to set the root\_size in apkovl.
Ideas on how to implement it?
Possible alternative:
lbu mountopts - save the mount options for root in apkovl
*(from redmine: issue id 93, created on 2009-07-28, closed on 20...would be nice to be able to set the root\_size in apkovl.
Ideas on how to implement it?
Possible alternative:
lbu mountopts - save the mount options for root in apkovl
*(from redmine: issue id 93, created on 2009-07-28, closed on 2009-08-19)*
* Changesets:
* Revision b36359dbd01c71a5b10cc9c95efaff4cc1db57ef on 2009-07-30T11:50:01Z:
```
main/mkinitfs: upgrade to 1.9
fixes #93
```Alpine 1.9https://gitlab.alpinelinux.org/alpine/aports/-/issues/120dnscache doesn't work on startup (1.9.0beta2)2019-07-12T14:23:14ZNathan Angelacosdnscache doesn't work on startup (1.9.0beta2)Weird problem with dnscache; it is running on 127.0.0.1; and is set to
send requests out the default gateway (standard)
1. echo “nameserver 127.0.0.1” >/etc/resolv.conf
2. echo “RESOLV\_CONF=‘no’” >/etc/udhcpc/udhcp.conf
3. rc-...Weird problem with dnscache; it is running on 127.0.0.1; and is set to
send requests out the default gateway (standard)
1. echo “nameserver 127.0.0.1” >/etc/resolv.conf
2. echo “RESOLV\_CONF=‘no’” >/etc/udhcpc/udhcp.conf
3. rc-update add dnscache
4. ping -c 1 www.google.com
(works fine)
<reboot>
\#ping -c 1 www.google.com
— fails after a very long time; no DNS resolution is possible
\#apk add djbdns
\#dnsq A \[any address\] 127.0.0.1
— will fail
doing a tcpdump on 127.0.0.1 shows the request going to 127.0.0.1; but
no response.
**however**, after logging into the server, doing a:
1. /etc/init.d/dnscache restart
— makes all DNS requests work.
Tried adding a delay in the /etc/init.d/dnscache start script; tried
changing the internet facing interface from dhcp to static; no effect.
DNSCACHE does not work until it is restarted.
Any ideas?
*(from redmine: issue id 120, created on 2009-08-08, closed on 2009-08-19)*
* Changesets:
* Revision 0b2149a1ec7b4881ed69cbc8206e3be153b28e39 on 2009-08-08T16:46:53Z:
```
main/djbdns: added net dependency in initd scripts
fixes #120
```
* Revision 6740d61d3640a7e253d6772364ca83dd82a78a57 on 2009-08-09T13:25:04Z:
```
main/djbdns: provide random seed to dnscache
fixes #120
Thanks to Nathan for solving this.
```Alpine 1.9 betaNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/148mdadm-raid does not start before lvm2019-07-12T14:23:24Zaa latchmmdadm-raid does not start before lvmUsing alpine 1.9.0\_beta4, I set up LVM on a RAID array created with
mdadm (/dev/md0) according to the document
http://wiki.alpinelinux.org/w/index.php?title=Setting\_up\_Logical\_Volumes\_with\_LVM.
I replaced every \`rc\_add\` command ...Using alpine 1.9.0\_beta4, I set up LVM on a RAID array created with
mdadm (/dev/md0) according to the document
http://wiki.alpinelinux.org/w/index.php?title=Setting\_up\_Logical\_Volumes\_with\_LVM.
I replaced every \`rc\_add\` command with \`rc-update SERVICE default\`.
All the services were sequenced correctly except for mdadm-raid. As a
result, the lvm partitions were unavailable after rebooting. Here are
the services as installed:
~# rc-status -a
* Caching service dependencies... [ok]
Runlevel: default
lvm [ started ]
localmount [ started ]
chronyd [ started ]
sshd [ started ]
cron [ started ]
crpd [ started ]
mdadm-raid [ started ]
swap [ started ]
Runlevel: boot
modules [ started ]
hwclock [ started ]
hostname [ started ]
sysctl [ started ]
bootmisc [ started ]
syslog [ started ]
networking [ started ]
I was able to work around this problem by creating /etc/conf.d/lvm as
follows:
~# cat /etc/conf.d/lvm
rc_need="mdadm-raid"
This results in the correct sequence for \`mdadm-raid\`:
~# rc-status default
Runlevel: default
mdadm-raid [ started ]
lvm [ started ]
localmount [ started ]
chronyd [ started ]
sshd [ started ]
cron [ started ]
crpd [ started ]
swap [ started ]
Perhaps /etc/init.d/mdadm-raid should be modified as follows:
--- mdadm-raid-orig Fri Aug 28 14:59:38 2009
+++ /etc/init.d/mdadm-raid Fri Aug 28 14:59:24 2009
@@ -2,6 +2,10 @@
# script to start raid devices described in /etc/mdadm.conf.
+depend() {
+ before lvm
+}
+
start() {
[ -f /proc/mdstat ] || modprobe -k md > /dev/null 2>&1
ebegin "Starting RAID devices"
*(from redmine: issue id 148, created on 2009-08-28, closed on 2009-10-09)*
* Changesets:
* Revision 386db07f3ed3f3e7dec969389f22472d44d7946c on 2009-08-31T11:22:07Z:
```
main/lvm2: init.d dependency fixes
make sure we start after fsck and after hwdrivers and modules.
provide default config that starts lvm after mdadm-raid.
fixes #148
```Alpine 1.9Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/169solve the hda/sda swapping2019-07-12T14:23:35ZNatanael Copasolve the hda/sda swappingProblem When booting from cd or usb disk shows up as sdX. after run setup-disk the disk shows up as hdX and boot fails.
---------------------------------------------------------------------------------------------------------------------...Problem When booting from cd or usb disk shows up as sdX. after run setup-disk the disk shows up as hdX and boot fails.
-----------------------------------------------------------------------------------------------------------------------
Reason The ide drivers gets loaded first. Which is loaded first seems to depend on how/when depmod was run and is completetly unpredictable.
--------------------------------------------------------------------------------------------------------------------------------------------
### Solution 1. Use UUID=… instead of devices in fstab and exlinux.conf 2. disable the IDE drivers and use scsi emulation only. (/dev/hdX will dissapear) This is what debian, ubuntu and fedora does.
*(from redmine: issue id 169, created on 2009-09-18, closed on 2009-10-02)*
* Changesets:
* Revision 529426cca93f7466eda8392b82e9dd4bc97b54ea on 2009-09-18T09:53:02Z:
```
main/alpine-conf: use uuid in setup-disk
fixes #169
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/172/etc/rc.local is not migrated to 1.92022-07-25T07:00:29Zaa latchm/etc/rc.local is not migrated to 1.9After upgrade from 1.8 to 1.9, /etc/rc.local is not migrated as a
startup script. Instead, /etc/init.d/rc.local (which may or may not
exist) is added to runlevel default.
Tested on 1.9.0\_rc5.
Some possible options:
- mv /etc/rc.loc...After upgrade from 1.8 to 1.9, /etc/rc.local is not migrated as a
startup script. Instead, /etc/init.d/rc.local (which may or may not
exist) is added to runlevel default.
Tested on 1.9.0\_rc5.
Some possible options:
- mv /etc/rc.local /etc/init.d/rc.local
- ln -s /etc/rc.local /etc/init.d/rc.local
- rc-update del rc.local && ln -s /etc/conf.d/local.start && rc-update
add local
- Write default /etc/init.d/rc.local which sources /etc/rc.local
*(from redmine: issue id 172, created on 2009-09-25, closed on 2009-10-02)*
* Changesets:
* Revision bd325689a38ce40e1e7fe6357c87c9cb07fdb9f6 on 2009-09-25T14:25:32Z:
```
main/openrc: migrate rc.local from 1.8
fixes #172
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/178/etc/init.d/localmount stop umounts modloop2019-07-12T14:23:39Zaa latchm/etc/init.d/localmount stop umounts modloopI think /etc/init.d/localmount stop should not umount modloop.
/etc/init.d/modloop stop is already designed to do this.
Since /etc/init.d/localmount stop umounts modloop, a
/etc/init.d/localmount restart will fail to mount any device wh...I think /etc/init.d/localmount stop should not umount modloop.
/etc/init.d/modloop stop is already designed to do this.
Since /etc/init.d/localmount stop umounts modloop, a
/etc/init.d/localmount restart will fail to mount any device which
requires new modules to be loaded.
For example, in the document
[http://wiki.alpinelinux.org/w/index.php?title=Setting\_up\_Logical\_Volumes\_with\_LVM](http://wiki.alpinelinux.org/w/index.php?title=Setting\_up\_Logical\_Volumes\_with\_LVM),
the instructions include running /etc/init.d/localmount start in order
to mount a new xfs partition. This requires loading the xfs module. Here
is what happens:
1. localmount is already started in 1.9 upon bootup, since it is a
‘need’ dependency of /etc/init.d/bootmisc, and bootmisc is in the
boot runlevel
1. Therefore the only option is to do /etc/init.d/localmount
restart (rc will not allow starting of a service that is
“already started”)
2. /etc/init.d/localmount restart first stops localmount, which umounts
modloop.
3. /etc/init.d/localmount restart then tries to mount the new xfs
partition, but cannot load the xfs module, so that it fails.
I think the following change should fix the problem:
--- localmount.orig Thu Oct 8 18:24:03 2009
+++ localmount Thu Oct 8 18:24:58 2009
@@ -32,7 +32,7 @@
{
# We never unmount / or /dev or $RC_SVCDIR
local x= no_umounts_r="/|/dev|/dev/.*|${RC_SVCDIR}"
- no_umounts_r="${no_umounts_r}|/bin|/sbin|/lib|/libexec"
+ no_umounts_r="${no_umounts_r}|/bin|/sbin|/lib|/libexec|/.modloop"
# RC_NO_UMOUNTS is an env var that can be set by plugins
OIFS=$IFS SIFS=${IFS-y}
IFS=$IFS:
*(from redmine: issue id 178, created on 2009-10-08, closed on 2009-12-23)*
* Changesets:
* Revision 52e59e902232fa150e2e8ced9e66bbd5d4140023 on 2009-10-12T13:00:05Z:
```
main/openrc: localmount: don't umount .modloop
fixes #178
```
* Revision 880a404a6daca5e4b606bab8d0b67dd581dd242c on 2009-10-12T14:24:28Z:
```
main/openrc: localmount: don't umount .modloop
fixes #178
(cherry picked from commit 52e59e902232fa150e2e8ced9e66bbd5d4140023)
```
* Revision a4cc593132e169168d5b701da879998f91f3744c on 2010-12-21T10:37:20Z:
```
main/openrc: apply patch from upstream. force root to be remounted as rw
also remove the .modloop hack. Basically, everytying in 'boot' runlevel
is for bootstrapping the system. Dont expect things work if restart
any of those services.
ref #178
```
* Revision 60204f874164b38247e0d52e589dbe52c4daa178 on 2011-01-07T12:39:48Z:
```
main/openrc: apply patch from upstream. force root to be remounted as rw
also remove the .modloop hack. Basically, everytying in 'boot' runlevel
is for bootstrapping the system. Dont expect things work if restart
any of those services.
ref #178
(cherry picked from commit a4cc593132e169168d5b701da879998f91f3744c)
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/209Alpine 1.9.1 on Soekris 48012019-07-12T14:23:57ZalgitbotAlpine 1.9.1 on Soekris 4801Hello,
I’m trying to use the lastest stable Alpine on a Soekris 4801 machine.
This worked perfectly with Alpine 1.8 or 1.6 .
I used the documentation to make the Compact Flash , making the serial
active .
My problem is at boot i get...Hello,
I’m trying to use the lastest stable Alpine on a Soekris 4801 machine.
This worked perfectly with Alpine 1.8 or 1.6 .
I used the documentation to make the Compact Flash , making the serial
active .
My problem is at boot i get the following message (file attached for all
logs) :
\_Freeing unused kernel memory: 7144k freed
Alpine Init 2.0\_rc6
\* Starting mdev: ok.
\* Loading boot drivers: PAX: suspicious general protection fault: 0000
\[\#1\] SMP
last sysfs file:
/sys/devices/pci0000:00/0000:00:13.0/usb1/1-0:1.0/modalias
Modules linked in: pata\_sc1200(+) ata\_generic libata ohci\_hcd ssb
pcmcia pcmcia\_core crc32 firmware\_class usb\_storage usb\_libusual
usbcore sd\_mod scsi\_mod cramfs loop
Pid: 305, comm: modprobe Not tainted (2.6.30.8-grsec \#1)
EIP: 0060:\[<002e296d>\] EFLAGS: 00010246 CPU: 0
EAX: c746c13c EBX: c746c05c ECX: 73627653 EDX: 73627573
ESI: c746c13c EDI: aa55006d EBP: c6eb9e34 ESP: c6eb9e28
DS: 0068 ES: 0068 FS: 00d8 GS: 0000 SS: 0068
Process modprobe (pid: 305, ti=c6eb8000 task=c7423900
task.ti=c6eb8000)
Stack:
c645f40c 00000001 00000000 c6eb9e50 002e29d7 c6444000 00000040
c645f40c
00000000 c6eb9ea8 c6eb9e7c 002ee15f c895a06c 00000040 002eff1f
c0b04354
c746c05c c6eb9ea8 c746c000 00000000 c6eb9ea8 c6eb9e9c 002ee6bc
c895a06c
Call Trace:
\_
So it seems the kernel crashes just after mdev .
Can someone help me ?
Thanks in advance
Nicolas SCHMERBER
*(from redmine: issue id 209, created on 2009-11-18, closed on 2010-02-19)*Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/220Feature request: lbu pre and post package scripts2021-07-31T22:46:10ZNathan AngelacosFeature request: lbu pre and post package scriptsWhen creating a package, it would be helpful to have a directory of
scripts that are run before and after the apkovl is created.
For example, the correct way to backup a sql database is to do a
database dump; a script could be part of l...When creating a package, it would be helpful to have a directory of
scripts that are run before and after the apkovl is created.
For example, the correct way to backup a sql database is to do a
database dump; a script could be part of lbu to create the database dump
before the apkovl is created, and then a script could delete the dump
file after the apkovl is created.
That allows flexibility in including “special” things in the lbu
archive.
Perhaps
/etc/lbu/pre-package.d/\*
and
/etc/lbu/post-package.d/\*
with run-scripts rules (like cron)
*(from redmine: issue id 220, created on 2009-12-17, closed on 2010-01-20)*
* Changesets:
* Revision 63f898c17a41acd7d22657209fed005ae3c55fcd by Natanael Copa on 2009-12-17T11:12:24Z:
```
lbu: implement support for lbu package pre/post hooks
scripts in /etc/lbu/pre-package.d/ will be executed prior creating the
tar ball and scripts in /etc/lbu/post-package.d/ will be executed after.
if pre-scripts fails, then will package not be created.
ref #220
```
* Revision b25b80ea9b361aef18289e51433ef275a50a0fea on 2009-12-17T14:59:05Z:
```
main/alpine-conf: upgrade to 2.0
fixes #91
fixes #220
```
* Revision 92dd4f0a0a7118c285cbc6f873677dbc427778a3 on 2009-12-17T15:02:14Z:
```
main/alpine-conf: upgrade to 2.0
fixes #91
fixes #220
(cherry picked from commit b25b80ea9b361aef18289e51433ef275a50a0fea)
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/228Alpine 1.9.3 won't boot on HP ML350 G62019-07-12T14:24:11ZJeff Bilykjbilyk@gmail.comAlpine 1.9.3 won't boot on HP ML350 G6On either 1.9.3 or the minimal 2.0 alpha 4 created in \#209, boot halts
with a PAX error: “suspicious general protection fault: 0000 \[\#1}
SMP”. Details follow below. It appears that the boot halts when trying
to load the hpwdt module, ...On either 1.9.3 or the minimal 2.0 alpha 4 created in \#209, boot halts
with a PAX error: “suspicious general protection fault: 0000 \[\#1}
SMP”. Details follow below. It appears that the boot halts when trying
to load the hpwdt module, used for the iLO card in the system. To test,
I disabled the iLO card, but the module still loads. I also tried the
nmi\_watchdog=0 boot option and the module still loads and crashes. What
would be the best way to blacklist the module when booting from the
LiveCD?
Additional error output:
Last sysfs file: /sys/devices/virtual/misc/psaux/dev
Modules: hpdwt(+) mousedev evdev rtc\_cmos rtc\_core rtc\_lib container
thermal button processor vfat fat nls\_iso8859 isofs nls\_base usbmouse
usbhid hid usbkbd sr\_mod cdrom ehci\_hcd pata\_acpi ata\_generic
ata\_piix libata uhci\_hcd cciss usb\_storage usb\_libusual usbcore
sd\_mod scsi\_mod cramfs loop
*(from redmine: issue id 228, created on 2009-12-24, closed on 2009-12-29)*
* Changesets:
* Revision ce9c551ded7784c6967df896afedb68946974451 on 2009-12-24T14:56:28Z:
```
main/linux-grsec: disable hpwtd
ref #228
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/258Upgrading kernel to latest edge does not allow boot2019-07-12T14:24:27ZJeff Bilykjbilyk@gmail.comUpgrading kernel to latest edge does not allow bootUpgrading from 2.6.32.6 to 2.6.32.7 in edge has multiple issues. First,
the soft link in /boot vmlinuz-grsec does not get recreated to
vmlinuz-2.6.32.7-grsec, but stays at the old version. Recreating the
soft by booting from liveCD bring...Upgrading from 2.6.32.6 to 2.6.32.7 in edge has multiple issues. First,
the soft link in /boot vmlinuz-grsec does not get recreated to
vmlinuz-2.6.32.7-grsec, but stays at the old version. Recreating the
soft by booting from liveCD brings up another issue. When trying to
mount drive via UUID string to sysroot, the mounting fails.
*(from redmine: issue id 258, created on 2010-02-04, closed on 2010-02-11)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/259Unable to create a Alpine linux virtal machine using vmware player 32019-07-12T14:24:28ZalgitbotUnable to create a Alpine linux virtal machine using vmware player 3Hi,
I wanted to create an Alpine Linux VM for using in my class project, EEL
5718 in university of florida (taken by Dr. Haniph Latchman).
I followed the steps mentioned at
http://wiki.alpinelinux.org/w/index.php?title=Installing\_Al...Hi,
I wanted to create an Alpine Linux VM for using in my class project, EEL
5718 in university of florida (taken by Dr. Haniph Latchman).
I followed the steps mentioned at
http://wiki.alpinelinux.org/w/index.php?title=Installing\_Alpine\_on\_a\_virtual\_machine.
The VM boots up from the CD (which is the .iso file downloaded), but
gets hanged. The screen shows “boot:” and then does’nt move forward with
the booting process. I am using the latest version (1.9.3 for x86). I
tried this on a windows vista host and ubuntu 9.10 host and got the same
result.
*(from redmine: issue id 259, created on 2010-02-04, closed on 2010-02-08)*Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/260/etc/init.d/chronyd should 'provide ntp'2019-07-12T14:24:29Zaa latchm/etc/init.d/chronyd should 'provide ntp'Currently some packages should have a ‘use’ dependency for NTP
synchronization. In order to avoid tying these services the chrony NTP
implementation, chronyd should ‘provide ntp’.
—- /etc/init.d/chronyd Tue Sep 15 13:25:08 2009
<span ...Currently some packages should have a ‘use’ dependency for NTP
synchronization. In order to avoid tying these services the chrony NTP
implementation, chronyd should ‘provide ntp’.
—- /etc/init.d/chronyd Tue Sep 15 13:25:08 2009
<span class="underline"></span>+ chronyd Sat Feb 6 00:01:56 2010
@@ –7,6 +7,7 @@
need net
after firewall
use dns
+ provide ntp
}
checkconfig() {
*(from redmine: issue id 260, created on 2010-02-06, closed on 2010-02-13)*
* Changesets:
* Revision 580b1e991fe7b5c58be1c045379bae23e190fc7d on 2010-02-08T13:10:53Z:
```
main/chrony: provide ntp-client and ntp-server
fixes #260
```
* Revision 8548d6c936344a59341c1c4362172407bf2149c2 on 2010-02-08T13:35:12Z:
```
main/chrony: provide ntp-client and ntp-server
fixes #260
(cherry picked from commit 580b1e991fe7b5c58be1c045379bae23e190fc7d)
```Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/261ipsec-tools: racoon should start after NTP service2019-07-12T14:24:29Zaa latchmipsec-tools: racoon should start after NTP serviceTested in alpine-1.9.3 with latest repository packages for 1.9.
racoon currently does not have any dependencies for NTP. Since correct
time may be necessary for Security Associations, it would be appropriate
to have a ‘use’ dependency f...Tested in alpine-1.9.3 with latest repository packages for 1.9.
racoon currently does not have any dependencies for NTP. Since correct
time may be necessary for Security Associations, it would be appropriate
to have a ‘use’ dependency for NTP. According to
http://redmine.alpinelinux.org/issues/show/260 chronyd should ‘provide
ntp’. So the racoon initscript should look like:
—- etc/init.d/racoon Thu Dec 10 15:19:10 2009
<span class="underline"></span>+ /root/racoon Sat Feb 6 00:04:23 2010
@@ –4,7 +4,7 @@
depend() {
before netmount
- use net
+ use net ntp
after firewall
provide ipsec
}
*(from redmine: issue id 261, created on 2010-02-06, closed on 2010-02-13)*
* Changesets:
* Revision b9df3004d7d87e527523028a02f0133e66029b52 on 2010-02-08T13:16:43Z:
```
main/ipsec-tools: start after ntp-client
fixes #261
```
* Revision a09d19aec0e9f05f5158bc7db885cb8465480c15 on 2010-02-08T13:35:27Z:
```
main/ipsec-tools: start after ntp-client
fixes #261
(cherry picked from commit b9df3004d7d87e527523028a02f0133e66029b52)
```Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/262opennhrp should start before zebra2019-07-12T14:24:30Zaa latchmopennhrp should start before zebraTested on 1.9.3 with latest packages in 1.9 repo:
Although in an upgrade from 1.8.x the number sequencing for startup of
opennhtp seems to be preserved, no dependencies are set up for opennhrp
to start before Zebra and BGP. This setup i...Tested on 1.9.3 with latest packages in 1.9 repo:
Although in an upgrade from 1.8.x the number sequencing for startup of
opennhtp seems to be preserved, no dependencies are set up for opennhrp
to start before Zebra and BGP. This setup is necessary for BGP over NHRP
tunnels. This change will provide a usable default:
--- etc/init.d/opennhrp Thu Nov 5 14:11:53 2009
+++ /root/opennhrp Sat Feb 6 00:09:20 2010
@@ -6,6 +6,7 @@
PIDFILE=/var/run/opennhrp.pid
depend() {
+ before zebra
use logger dns
need net
after firewall ipsec
*(from redmine: issue id 262, created on 2010-02-06, closed on 2010-02-13)*
* Changesets:
* Revision 48c7f07294786a39cbb7ad396f4f4669cfe7d447 on 2010-02-08T13:30:16Z:
```
main/quagga: have zebra start after opennhrp
fixes #262
```
* Revision bb328568465eb4144c70829a6eecb636b705df82 on 2010-02-08T13:35:42Z:
```
main/quagga: have zebra start after opennhrp
fixes #262
(cherry picked from commit 48c7f07294786a39cbb7ad396f4f4669cfe7d447)
```Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/273Alpine Linux on Asus 1000he netbook2019-07-12T14:24:36ZalgitbotAlpine Linux on Asus 1000he netbookAlpine 1.9.3-x86 will not run directly by booting from a CD connected to
USB port. It also will not run in a virtual machine using VirtualBox. I
have several other versions of Linux running as virtual machines without
problems. But Alpin...Alpine 1.9.3-x86 will not run directly by booting from a CD connected to
USB port. It also will not run in a virtual machine using VirtualBox. I
have several other versions of Linux running as virtual machines without
problems. But Alpine will not boot on my netbook. I have a desktop
running on a Celeron processor with Ubuntu 9.04 and VirtualBox. Alpine
runs on it just fine as a virtual machine.
Any ideas?
*(from redmine: issue id 273, created on 2010-02-12, closed on 2010-02-19)*Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/275mdadm-3.1.1 /etc/init.d/mdadm-raid fails to start2019-07-12T14:24:38ZNatanael Copamdadm-3.1.1 /etc/init.d/mdadm-raid fails to startnew behaviour in mdadm. if raid devices are already running it will exit
with error. Since we start our raid in initramfs our init.d script will
fail to start.
Best would be if upstream could provide an
—only-start-not-already-running o...new behaviour in mdadm. if raid devices are already running it will exit
with error. Since we start our raid in initramfs our init.d script will
fail to start.
Best would be if upstream could provide an
—only-start-not-already-running option or similar, but meanwhile we need
to fix our init.d script.
*(from redmine: issue id 275, created on 2010-02-13, closed on 2010-02-24)*
* Changesets:
* Revision 5e3b66ce08317c39c9689ec73ae774feae62e542 on 2010-02-13T17:03:49Z:
```
main/mdadm: fix init.d script
fixes #275
fixes #276
```
* Revision 5ffd9b46d64ad0c31abf77cba2e9a4e1dcd76067 on 2010-02-13T18:05:51Z:
```
main/mdadm: fix init.d script
fixes #275
fixes #276
```
* Revision e47172d6a82ba03449f131e8329f349f254662bb on 2010-02-16T14:35:56Z:
```
main/mdadm: do no exit with error if all raids are already
ref #275
```
* Revision 697b99fd2eb775ae86b698377284cf219f29ddb2 on 2010-02-16T14:37:52Z:
```
main/mdadm: do no exit with error if all raids are already
ref #275
(cherry picked from commit e47172d6a82ba03449f131e8329f349f254662bb)
```Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/276mdadm-raid fails to stop during shutdown2019-07-12T14:24:39ZNatanael Copamdadm-raid fails to stop during shutdownmdadm exits with error because / (root) is mounted and in use.
We need to have the script stop all raid devices except any that is
mounted as /
*(from redmine: issue id 276, created on 2010-02-13, closed on 2010-02-24)*
* Changesets:...mdadm exits with error because / (root) is mounted and in use.
We need to have the script stop all raid devices except any that is
mounted as /
*(from redmine: issue id 276, created on 2010-02-13, closed on 2010-02-24)*
* Changesets:
* Revision 5e3b66ce08317c39c9689ec73ae774feae62e542 on 2010-02-13T17:03:49Z:
```
main/mdadm: fix init.d script
fixes #275
fixes #276
```
* Revision 5ffd9b46d64ad0c31abf77cba2e9a4e1dcd76067 on 2010-02-13T18:05:51Z:
```
main/mdadm: fix init.d script
fixes #275
fixes #276
```Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/293alpine-mini-1.10_rc3 does not include openssl2019-07-12T14:24:51ZNatanael Copaalpine-mini-1.10_rc3 does not include opensslapkovls does not work
*(from redmine: issue id 293, created on 2010-02-24, closed on 2010-03-06)*apkovls does not work
*(from redmine: issue id 293, created on 2010-02-24, closed on 2010-03-06)*Alpine 1.10.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/297initramfs init should apk add --best-effort2019-07-12T14:24:54ZNatanael Copainitramfs init should apk add --best-effortIf you upgrade alpine and a package that used to be on the cdrom is no
longer there, it will break and launch an emergency shell.
We could probably add —force to apk add, but then it will continue even
if it gets signing key errors etc....If you upgrade alpine and a package that used to be on the cdrom is no
longer there, it will break and launch an emergency shell.
We could probably add —force to apk add, but then it will continue even
if it gets signing key errors etc.
Other option could be to test if each requested package is available
before apk add is called and warn about those who are not.
*(from redmine: issue id 297, created on 2010-02-26, closed on 2010-02-26)*Alpine 1.10.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/318alpine 1.10 upgrade problem2019-07-12T14:25:06ZNatanael Copaalpine 1.10 upgrade problemIf upgrading from 1.9.x and there are http repostiroies and cache
enabled and some packages are missing in 1.10 (for example sfic and
beep), then will Alpine not boot and give an error message.
*(from redmine: issue id 318, created on ...If upgrading from 1.9.x and there are http repostiroies and cache
enabled and some packages are missing in 1.10 (for example sfic and
beep), then will Alpine not boot and give an error message.
*(from redmine: issue id 318, created on 2010-03-10, closed on 2010-03-18)*Alpine 1.10.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/339Screen contents are not cleared after syslinux loads2019-07-12T14:25:19ZJeff Bilykjbilyk@gmail.comScreen contents are not cleared after syslinux loadsAfter selecting a kernel + options with syslinux, the screen contents
are not cleared. For example, the BIOS hardware summary remains in while
the services + daemons are started up, which makes the contents of the
screen difficult to rea...After selecting a kernel + options with syslinux, the screen contents
are not cleared. For example, the BIOS hardware summary remains in while
the services + daemons are started up, which makes the contents of the
screen difficult to read. In the past this was done, and I can’t
remember when this changed. Is there just a kernel option to make the
screen contents disappear or is there a change needed in Alpine?
*(from redmine: issue id 339, created on 2010-03-30, closed on 2010-06-16)*
* Changesets:
* Revision 2214577d304e6e0099a902315981d0b908b1b818 on 2010-06-08T13:41:51Z:
```
main/linux-grsec: fix clearing of screen at boot
fixes #339
```
* Revision 54f50864ba74d0c4c63fdc7167f9ff8aac0510f9 on 2010-06-08T14:36:56Z:
```
main/linux-grsec: fix clearing of screen at boot
fixes #339
(cherry picked from commit 2214577d304e6e0099a902315981d0b908b1b818)
```
* Revision 3a138c7fc3c38433f75cf3d44a4a78d80a6da705 on 2010-08-06T08:58:36Z:
```
main/linux-vserver: add fix for screen output on boot
was never applied to linux-vserver kernel.
ref #339
```Alpine 1.10.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/344When upgrading from 1.9.3 to 1.10.1, nrpe does not stay in the "default" set ...2022-07-25T21:32:26ZJeff Bilykjbilyk@gmail.comWhen upgrading from 1.9.3 to 1.10.1, nrpe does not stay in the "default" set of services to startTonight I upgraded one of our Alpine Linux boxes which runs several
services including mail relaying and web proxying. We use the nrpe
daemon to monitor the box via our central nagios server. The server has
been setup to run from disk, a...Tonight I upgraded one of our Alpine Linux boxes which runs several
services including mail relaying and web proxying. We use the nrpe
daemon to monitor the box via our central nagios server. The server has
been setup to run from disk, and was running 1.9.3 with the latest
updates from the 1.9 Main repo. We upgraded to 1.10.1 by switching to
the Main 1.10 repo and running apk upgrade. The update went without any
issues and we rebooted the server. After the reboot, the nrpe service
failed to start. I checked the “default” boot services and nrpe had been
removed. I added it back manually, which isn’t a big issue, but any
ideas why it didn’t stick around.
Only other detail that may or may not be important is that nrpe had been
originally installed from the edge repo, which isn’t in our
/etc/apk/repositories anymore.
*(from redmine: issue id 344, created on 2010-04-24, closed on 2010-07-20)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/429run-from-RAM install: Remember if certain package files have been deleted2019-07-12T14:26:17Zaa latchmrun-from-RAM install: Remember if certain package files have been deletedA couple of users have had an interesting case where certain undesired
configuration files included in the package APK would be deleted.
However, if other files in the package APK are still needed, this raises
a question of how to mainta...A couple of users have had an interesting case where certain undesired
configuration files included in the package APK would be deleted.
However, if other files in the package APK are still needed, this raises
a question of how to maintain the change over reboots.
Not sure what might be the best solution.
*(from redmine: issue id 429, created on 2010-09-09, closed on 2010-10-01)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/453support for alpine_dev=UUID=... boot parameter2019-07-12T14:26:28ZNatanael Copasupport for alpine_dev=UUID=... boot parameterWe might not know how kernel enumarates the disks so when looing for the
device with apks we want be able to use UUID from blkid.
*(from redmine: issue id 453, created on 2010-10-25, closed on 2010-10-27)*We might not know how kernel enumarates the disks so when looing for the
device with apks we want be able to use UUID from blkid.
*(from redmine: issue id 453, created on 2010-10-25, closed on 2010-10-27)*Alpine 2.1.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/457Alpine ISO: Attempts to load boot media from last detected CD-ROM device?2019-07-12T14:26:31ZMatt SmithAlpine ISO: Attempts to load boot media from last detected CD-ROM device?I haven’t looked into this in depth, but attempting to load an Alpine
2.0.x ISO onto a KVM virtual machine with two CD-ROM devices (this could
be a ‘bad’ KVM configuration), the ISO attempts to load the boot media
from the second CD-ROM ...I haven’t looked into this in depth, but attempting to load an Alpine
2.0.x ISO onto a KVM virtual machine with two CD-ROM devices (this could
be a ‘bad’ KVM configuration), the ISO attempts to load the boot media
from the second CD-ROM device, even though the ISO is loaded into the
first CD-ROM device.
In order to get the Alpine ISO to boot properly, I have to enter the
following at the ‘boot:’ prompt:
/boot/grsec initrd=/boot/grsec.gz alpine_dev=sr0:iso9660 modules=loop,cramfs,sd-mod,usb-storage,floppy,sr-mod quiet
From there, it boots up and I can proceed with installation.
*(from redmine: issue id 457, created on 2010-10-31, closed on 2011-04-27)*
* Changesets:
* Revision 2d116ff62c2f3bc5e25fafaadde1eb750c1b8096 on 2011-04-13T06:53:55Z:
```
mdev.conf: only symlink first cdrom to /dev/cdrom
fixes #457
```Alpine 2.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/458Should swap be started in an earlier runlevel?2019-07-12T14:26:31ZMatt SmithShould swap be started in an earlier runlevel?As it is now, swap activates in boot runlevel, and this occurs
practically after everything else has loaded on boot and prior to
arriving at the login prompt. It seems to me that swap should be
activated earlier on in the boot process.
...As it is now, swap activates in boot runlevel, and this occurs
practically after everything else has loaded on boot and prior to
arriving at the login prompt. It seems to me that swap should be
activated earlier on in the boot process.
I tried at one point, to move swap to the sysinit runlevel, but it seems
that its the first thing to go when doing a halt or reboot.. so I’m not
sure how to go about ‘fixing’ this.
Keep in mind that if we do move swap to another runlevel, setup-disk
needs to reflect this as well.
*(from redmine: issue id 458, created on 2010-10-31, closed on 2011-07-20)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/477Option to mount boot media read-only2019-07-12T14:26:42ZTimo TeräsOption to mount boot media read-onlyWhen having CF or USB install, it would be nice to have an option to
mount /media/usb or /media/sda1 as read-only. This would also need
support from lbu to remount the media as read-write when committing
config changes (and remount back ...When having CF or USB install, it would be nice to have an option to
mount /media/usb or /media/sda1 as read-only. This would also need
support from lbu to remount the media as read-write when committing
config changes (and remount back to ro).
This adds a bit of security (action needed to make things writable), and
also hard reboot tolerance (the media is ro, so someone cutting powers
off unexpectedly will have zero possibility to corrupt media).
*(from redmine: issue id 477, created on 2010-11-18, closed on 2011-03-24)*
* Changesets:
* Revision d98fee839dff01a68747a69df124660ff774a2f6 on 2010-12-03T09:32:55Z:
```
main/alpine-conf: add support for read-only lbu media
ref #477
```
* Revision 5b1639fe510db42372468d07f5eefc3aede744bd on 2010-12-03T09:39:02Z:
```
main/mkinitfs: upgrade to 2.1.3
fixes #477
```
* Revision 4e7ab7455206ec157a72d07c40c07f1a299529f1 by Natanael Copa on 2010-12-03T09:55:04Z:
```
lbu: remount LBU_MEDIA as read-write if it was read-only
ref #477
```Alpine 2.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/486booting from encrypted lvm is not supported.2019-07-12T14:28:33ZMarcin Kowalskibooting from encrypted lvm is not supported.When using the live media, i have no problem accessing the encrypted lvm
(after adding a few packages), and installing it there.
the issue at hand is that the initrd does not support encrypted lvm
booting, and initrd created with dracut...When using the live media, i have no problem accessing the encrypted lvm
(after adding a few packages), and installing it there.
the issue at hand is that the initrd does not support encrypted lvm
booting, and initrd created with dracut initrd generator fails to locate
the init. the system is otherwise operational (when chrooting into it).
please consider extending initrd with encrypted lvm support.
i might try doing it myself, if nobody is up to the task.
*(from redmine: issue id 486, created on 2010-12-07, closed on 2011-10-27)*
* Relations:
* relates #669
* Changesets:
* Revision cd089916834f1a0fa77a93ecb028e3582497ac41 on 2010-12-23T17:09:04Z:
```
main/mkinitfs: upgrade to 2.2.0
ref #486
```Alpine 2.3.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/538after upgrade to openrc-0.7.x vserver guests does not boot up2019-07-12T14:27:23ZNatanael Copaafter upgrade to openrc-0.7.x vserver guests does not boot upThe /etc/rc.sys file has this info:
# If unset, the old automagic detection code will be triggered. Said old code
# is deprecated and be removed not later than 2010/03/01.
rc_sys=""
Apparently this change comes from gentoo ...The /etc/rc.sys file has this info:
# If unset, the old automagic detection code will be triggered. Said old code
# is deprecated and be removed not later than 2010/03/01.
rc_sys=""
Apparently this change comes from gentoo due to LXC is not beeing able
to detected reliable.
This causes networing service be pulled in which fails, naturally. As a
result sshd fails and all other network services fails.
*(from redmine: issue id 538, created on 2011-03-03, closed on 2011-03-11)*Alpine 2.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/613ugly progressbar during boot when not quiet2019-07-12T14:27:59Ziilluzion _ugly progressbar during boot when not quietIf ‘quiet’ directive is removed from syslinux.cfg then setting of system
root directory looks exactly as decribed here:
http://bugs.alpinelinux.org/issues/591
*(from redmine: issue id 613, created on 2011-04-28, closed on 2011-04-29)*
...If ‘quiet’ directive is removed from syslinux.cfg then setting of system
root directory looks exactly as decribed here:
http://bugs.alpinelinux.org/issues/591
*(from redmine: issue id 613, created on 2011-04-28, closed on 2011-04-29)*
* Changesets:
* Revision 89285d731d09a4f898f5781ba1a52df1a4e25294 on 2011-04-28T15:52:35Z:
```
main/mkinitfs: fix progressbar
fixes #613
```Alpine 2.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/616RAM based system may loose some packages after upgrade2019-07-12T14:28:01Ziilluzion _RAM based system may loose some packages after upgradeThis is related to RAM based systems. During upgrade process some
packages installed previously but missing in new cache may not be
installed after first reboot of upgraded system. Consequently after
changes have been committed with out ...This is related to RAM based systems. During upgrade process some
packages installed previously but missing in new cache may not be
installed after first reboot of upgraded system. Consequently after
changes have been committed with out noticing of missing packages
/etc/apk/world will be rewritten and list of packages will be cut.
Perhaps we need some algorithm to force update from new repositories
before first reboot after upgrade.
*(from redmine: issue id 616, created on 2011-04-28, closed on 2011-10-06)*Alpine 2.3.0Jeff Bilykjbilyk@gmail.comJeff Bilykjbilyk@gmail.comhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/622Loosing console at boot on Alpine 2.22019-07-12T14:28:04ZMika HavelaLoosing console at boot on Alpine 2.2Booting up a fresh Alpine 2.2.0 (from CD) on a box with a AGP graphic
card makes the console go blank after some seconds after booting.
I don’t seem to get the console through /dev/ttyS0 either, so I’m really
‘blind’.
Logging on “with...Booting up a fresh Alpine 2.2.0 (from CD) on a box with a AGP graphic
card makes the console go blank after some seconds after booting.
I don’t seem to get the console through /dev/ttyS0 either, so I’m really
‘blind’.
Logging on “with my eyes shut” like this solves it:
root [Enter]
modprobe fbcon [Enter]
This gives me screen on my AGP card and now I can start using the box
*<span class="ncopa from suggestion to thanks"></span>*.
I need to remember to ‘echo fbcon >>/etc/modules’ so I get
console at next reboot *<span
class="apkovl a create to me requires which"></span>*.
If not having console on /dev/ttyS0 and/or no graphic on AGP-cards might
make Alpine seem to “fail” to boot on many hardware types.
Would it be wise to enable console on /dev/ttyS0 as default?
Would it be possible to have fbcon included as default?
*(from redmine: issue id 622, created on 2011-05-05, closed on 2011-06-03)*
* Changesets:
* Revision f1f9a3a857cccd09b42ac4e29cf0aa9782b7de76 on 2011-05-24T13:45:28Z:
```
main/busybox-initscripts: load fbcon with framebuffer dev
When a frambuffer device shows up we want a framebuffer console
ref #622
```
* Revision 7945f609e9ae56b62164aac68519a2b148bd43f3 on 2011-05-25T06:05:30Z:
```
main/busybox-initscripts: load fbcon with framebuffer dev
When a frambuffer device shows up we want a framebuffer console
fixes #622
(cherry picked from commit f1f9a3a857cccd09b42ac4e29cf0aa9782b7de76)
```Alpine 2.2.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/652mdadm-raid init script fails with default /etc/mdadm.conf file2022-06-16T15:25:50Ziilluzion _mdadm-raid init script fails with default /etc/mdadm.conf fileThe default /etc/mdadm.conf file has just lines started with ‘\#’ symbol
and has no ARRAY… like strings by default.
$(awk ‘{print $2}’ /etc/mdadm.conf) parses the default /etc/mdadm.conf
file incorrectly and so init script fails.
*(f...The default /etc/mdadm.conf file has just lines started with ‘\#’ symbol
and has no ARRAY… like strings by default.
$(awk ‘{print $2}’ /etc/mdadm.conf) parses the default /etc/mdadm.conf
file incorrectly and so init script fails.
*(from redmine: issue id 652, created on 2011-05-20, closed on 2011-05-27)*
* Changesets:
* Revision da2ac01c0ce27f102ee58913eb257aaabf592614 on 2011-05-23T13:13:04Z:
```
main/mdadm: init.d script ignore comments in mdadm.conf
ref #652
```
* Revision 5bbd39ada7b3872cef665283c7acba70675c1847 on 2011-05-24T13:33:26Z:
```
main/mdadm: init.d script ignore comments in mdadm.conf
fixes #652
(cherry picked from commit da2ac01c0ce27f102ee58913eb257aaabf592614)
```Alpine 2.2.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/695extlinux.conf generated by syslinux trigger does not detect and load root fil...2019-07-12T14:28:45ZNatanael Copaextlinux.conf generated by syslinux trigger does not detect and load root filesystem kernel modulewhich makes boot fail if your root is anything but ext3.
*(from redmine: issue id 695, created on 2011-06-23, closed on 2011-09-15)*which makes boot fail if your root is anything but ext3.
*(from redmine: issue id 695, created on 2011-06-23, closed on 2011-09-15)*Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/755Errors before/in init when running from ram on sda12019-07-12T14:29:13ZCarlo LandmeterErrors before/in init when running from ram on sda1When booting current edge the following will be displayed just before
init (boot is OK):
mkdir: can’t create directory ’’: no such file or directory
mount: can’t find /media/sda1 in fstab
I am using grub:
title ISCSI SCST
root (hd...When booting current edge the following will be displayed just before
init (boot is OK):
mkdir: can’t create directory ’’: no such file or directory
mount: can’t find /media/sda1 in fstab
I am using grub:
title ISCSI SCST
root (hd0,0)
kernel /boot/scst alpine\_dev=sda1:ext3
modloop=/boot/scst.modloop.squashfs
modules=loop,squashfs,sd-mod,usb-storage
initrd /boot/scst.gz
title ISCSI SCST UUID
root (hd0,0)
kernel /boot/scst
alpine\_dev=UUID=0b149c29-d3bf-41ed-90e6-b88a92d334e5:ext3
modloop=/boot/scst.modloop.squashfs
modules=loop,squashfs,sd-mod,usb-storage
initrd /boot/scst.gz
Both entries have similar issues.
*(from redmine: issue id 755, created on 2011-10-06, closed on 2013-10-18)*Alpine 2.7.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/784Upgrading to Alpine 2.3_rc2 fails on loading modules2019-07-12T14:29:31ZDuane HughesUpgrading to Alpine 2.3_rc2 fails on loading modulesUpgrading using setup-bootable from Alpine 2.2.0 to 2.3\_rc2 using
modules=…cramfs in syslinux.cfg and rebooting fails with:
Mounting modloop /media/sda1/boot/grsec.modloop.squashfs
mount: mounting /dev/loop0 on /.modloop failed...Upgrading using setup-bootable from Alpine 2.2.0 to 2.3\_rc2 using
modules=…cramfs in syslinux.cfg and rebooting fails with:
Mounting modloop /media/sda1/boot/grsec.modloop.squashfs
mount: mounting /dev/loop0 on /.modloop failed: Invalid argument
Modules then fail to load:
Loading modules ...
modprobe: chdir(/lib/modules): No such file or directory
Following boot process, running lsmod | grep squashfs shows squashfs is
not loaded.
*(from redmine: issue id 784, created on 2011-10-26, closed on 2011-10-28)*
* Changesets:
* Revision 2983d59b5ed04b9ee3d3b5ef08d78b28180ca7f6 by Natanael Copa on 2011-10-26T14:49:01Z:
```
main/mkinitfs: upgrade to 2.4.1
fixes #784
```Alpine 2.3.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/791Alpine Linux 2.3.0_rc5 running under VMWare requires pax_nouderef kernel opti...2019-07-12T14:29:35ZJeff Bilykjbilyk@gmail.comAlpine Linux 2.3.0_rc5 running under VMWare requires pax_nouderef kernel option to bootIt was my understanding that at one point, some VMWare detection code
was put into syslinux (or another part of the bootloader/initial kernel
loading) so that the pax\_nouderef option was passed to the kernel
whenever Alpine is running u...It was my understanding that at one point, some VMWare detection code
was put into syslinux (or another part of the bootloader/initial kernel
loading) so that the pax\_nouderef option was passed to the kernel
whenever Alpine is running under VMWare. It’s possible that since uderef
was disabled for a bit then re-enabled in
http://git.alpinelinux.org/cgit/aports/commit/?id=f6f718575335c86eb6d93dcc8df345eab3da460b
that re-enabling it caused this behaviour. If it’s worth fixing before
2.3.0, that’s fine, but otherwise can probably wait for 2.3.1 or 2.4.0.
*(from redmine: issue id 791, created on 2011-10-29, closed on 2012-01-02)*Alpine 2.4.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/891broken /etc/apk/repositories when booting a clean/new USB2019-07-12T14:30:23ZNatanael Copabroken /etc/apk/repositories when booting a clean/new USBTo reproduce: create a bootable USB that uses UUID in syslinux.cfg
Boot it up and run setup-alpine
It will complain about not finding packages etc.
What happens is that it will use /media/$UUID when installing the
packages. This is us...To reproduce: create a bootable USB that uses UUID in syslinux.cfg
Boot it up and run setup-alpine
It will complain about not finding packages etc.
What happens is that it will use /media/$UUID when installing the
packages. This is used to generate the /etc/apk/repositories.
Later will that be relocated to /media/usb and the /media/$UUID
repository no longer works.
*(from redmine: issue id 891, created on 2012-01-04, closed on 2012-01-05)*
* Changesets:
* Revision 1b581690423ac11ecd853d8be9abe8a15a0ff146 by Natanael Copa on 2012-01-04T14:58:41Z:
```
main/mkinitfs: fix for init
we need generate the /etc/apk/repositories after we have relocated
/media/$UUID to /media/usb
ref #891
```
* Revision fda7e3a8891679e7c6bc732f9db82f3fec61661a by Natanael Copa on 2012-01-05T14:23:54Z:
```
main/mkinitfs: fix for init
we need generate the /etc/apk/repositories after we have relocated
/media/$UUID to /media/usb
fixes #891
(cherry picked from commit 1b581690423ac11ecd853d8be9abe8a15a0ff146)
```Alpine 2.3.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/967If root cannot be remounted "rw" due to an issue, the status is falsely repor...2020-01-18T20:12:53ZFlorian HeiglIf root cannot be remounted "rw" due to an issue, the status is falsely reported as "OK"Seems the remount handler cannot fully identify the status from mount -o
remount.
I had a small world of pain until I identified this issue, it would be
good to verify if it applies to other mount issues as well.
The setup-alpine creat...Seems the remount handler cannot fully identify the status from mount -o
remount.
I had a small world of pain until I identified this issue, it would be
good to verify if it applies to other mount issues as well.
The setup-alpine creates a ext4 filesystem with the “barrier=1” option.
When testing Alpine VMs on a older Xen host that still had a 2.6.18….
RHEL-based kernel there’s the issue that the devmapper/LVM cannot
correctly handle barriers.
Ext4 denies the remount to RW under this condition\[\*\]. Nonetheless
the boot script that remounts root does report an OK state. There’s a
lot of ext errors if I manually try this.
I think the most important part in this is to identify holes in the
return code handling.
The bug in itself is only a small nuisance for me so far.
I can re-test or provide a test vm for this.
\[\*\](and it doesn’t matter if you set “nobarrier” in your fstab, for
some reason. mount bug actually, can verify that manually if you do
mount <s>o remount,nobarrier and cat /proc/mounts</s> the arguments are
stacked. If you do a tune2fs and set nobarrier that way, it’ll work)
*(from redmine: issue id 967, created on 2012-01-30)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1171Will not find and use /var/lib/apk/world when upgrading2019-07-23T14:33:51ZNatanael CopaWill not find and use /var/lib/apk/world when upgradingWhen upgrading an empty /etc/apk/world created by apk add —initdb will
be used instead of a /var/lib/apk/world when upgrading.
Bug introduced with commit:“8981ccbf5b2636c7d2e06b08ffdf87be80fe19c8”.
*(from redmine: issue id 1171, creat...When upgrading an empty /etc/apk/world created by apk add —initdb will
be used instead of a /var/lib/apk/world when upgrading.
Bug introduced with commit:“8981ccbf5b2636c7d2e06b08ffdf87be80fe19c8”.
*(from redmine: issue id 1171, created on 2012-05-17, closed on 2012-05-18)*
* Changesets:
* Revision 1e6eacb33245c79f9cfd1515b76849a9079c6240 by Natanael Copa on 2012-05-17T15:16:09Z:
```
main/mkinitfs: fix apk world when upgrading
ref #1171
```
* Revision d4509104527c6c3f69c713406d4aff091f8c7952 by Natanael Copa on 2012-05-17T15:16:57Z:
```
main/mkinitfs: fix apk world when upgrading
fixes #1171
(cherry picked from commit 1e6eacb33245c79f9cfd1515b76849a9079c6240)
```
* Revision 63772febffe791258a084468049d35305a30a376 by Natanael Copa on 2012-05-25T12:20:57Z:
```
main/mkinitfs: fix apk world when upgrading
ref #1171
```Alpine 2.4.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1337setup-bootable, and boot media mounting improvements2019-07-23T14:18:35ZTimo Terässetup-bootable, and boot media mounting improvementsThe new setup-bootable unconditionally overwrites the alpine\_dev boot
option with UUID=xxx style line.
This has following implications:
- apk repositories, and lbu media need to be updated if UUID changes
- setup-bootable help tex...The new setup-bootable unconditionally overwrites the alpine\_dev boot
option with UUID=xxx style line.
This has following implications:
- apk repositories, and lbu media need to be updated if UUID changes
- setup-bootable help text is misleading (-u says “Keep existing
syslinux.cfg” which is not true without -k)
- it also overwrites LABEL=xxx things
Suggestions:
- do not touch alpine\_dev if it is LABEL=xxx style
- maybe plain or UUID style alpine\_dev should be mounted as
/media/boot, so we get consistent mount point for other config
files?
- could we drop UUID= from the mount point name? /media/UUID=xxx is
inconvenient
- additionally we might need to pass initial mount options when
mounting boot media, an ability to do that would be nice (e.g. -o
barrier=0 is useful in certain cases)
*(from redmine: issue id 1337, created on 2012-08-23, closed on 2013-11-06)*
* Relations:
* duplicates #2258Alpine 2.7.0Natanael CopaNatanael Copa2012-10-01https://gitlab.alpinelinux.org/alpine/aports/-/issues/1340Software raid startup broken2019-07-23T14:31:28ZCarlo LandmeterSoftware raid startup brokenWhen using software raid on Alpine 2.4 and having udev installed, im
unable to make it start properly by init.
First of all udev has a script which will try to start it
/lib/udev/rules.d/64-md-raid.rules, because udev is run before my ...When using software raid on Alpine 2.4 and having udev installed, im
unable to make it start properly by init.
First of all udev has a script which will try to start it
/lib/udev/rules.d/64-md-raid.rules, because udev is run before my raid
module is loaded, the raid will be started as inactive.
I can prevent this behavior by adding an empty file
/etc/udev/rules.d/64-md-raid.rules which prevents udev to start the
array and have the default scripts jump in.
After doing the above I still run into another issue. The new way of
handling raid devices are based on names. Linux raid will auto number md
devices (starting from 127 and down) and should create a symlink to
/dev/md/devicename to be access. After trying a few options, I am not
able to have this symlink although mdadm outputs it has started it.
mdadm.conf I used was
ARRAY /dev/md/stripe metadata=1.2
UUID=9dbff4d2:b343c7fe:4bca5b42:d2053de1 name=xen:stripe
I had to switch back the old naming like:
ARRAY /dev/md0 UUID=9dbff4d2:b343c7fe:4bca5b42:d2053de1
This starts the array as md0 again and init script work again.
*(from redmine: issue id 1340, created on 2012-08-24, closed on 2013-11-06)*Alpine 2.7.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1469Lockup on boot from CD at clocksource message.2019-07-23T14:29:43ZRyan FarnhamLockup on boot from CD at clocksource message.I got this distro as I figured it was perfect for my needs but it
doesn’t even boot from the CD fully!
It locks up at a message stating setting new clocksource (that part
having to do with CPU I suspect) I see a bunch of
ATA errors b...I got this distro as I figured it was perfect for my needs but it
doesn’t even boot from the CD fully!
It locks up at a message stating setting new clocksource (that part
having to do with CPU I suspect) I see a bunch of
ATA errors before hand, not sure if it doesn’t like my CD-ROM (nothing
else has issues with it or the computer), this is as much information I
can really provide, sorry.
The computer specs are:
IBM NetVista
Pentium 4 2.0Ghz
768MB RAM
30GB PATA Hard Disk
LiteOn CD-RW Drive
Intel everything chipsets
Sorry to say I can not afford to wait to solve the issue before moving
on, need this machine back up in running with something more secure than
Ubuntu for server use but I now can’t as that was my last CD now gone so
unless I find a network bootable distro and can figure out how to do
that.. oi
*(from redmine: issue id 1469, created on 2012-11-15, closed on 2017-04-07)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1530gendepends.sh segfault when checking depends2019-07-23T14:28:53ZCarlo Landmetergendepends.sh segfault when checking dependsgendepends.sh\[1196\]: segfault at 7f1bb302dff8 ip 00000714b5b27f68 sp
00007f1bb302e000 error 6 in busybox\[714b5ad8000+e6000\]
This happends in current edge repo.
*(from redmine: issue id 1530, created on 2013-01-03, closed on 2013-0...gendepends.sh\[1196\]: segfault at 7f1bb302dff8 ip 00000714b5b27f68 sp
00007f1bb302e000 error 6 in busybox\[714b5ad8000+e6000\]
This happends in current edge repo.
*(from redmine: issue id 1530, created on 2013-01-03, closed on 2013-01-18)*
* Relations:
* duplicates #1539
* Changesets:
* Revision 0e89f5bbc2edaea3803b3b389c877c3f15de8eae by Carlo Landmeter on 2013-01-03T11:58:20Z:
```
main/openrc: dont depend but need in networking.initd
fixes #1530
```
* Revision dadf6d7f5d66c399568e8be3d1e57f5837993d3f by Carlo Landmeter on 2013-01-07T20:21:12Z:
```
main/openrc: dont depend but need in networking.initd
fixes #1530
```Alpine 2.5.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1539openrc-0.10.5-r6 and/or busybox-1.20.2-r3 failure2019-07-23T14:28:49ZTimo Teräsopenrc-0.10.5-r6 and/or busybox-1.20.2-r3 failureAfter upgrading to alpine-2.5.1, openrc/busybox failed during the first
boot.
The dmesg contains:
\[ 16.066159\] grsec: denied resource overstep by requesting 8392704 for
RLIMIT\_STACK against limit 8388608 for /lib/rc/sh/
gendepend...After upgrading to alpine-2.5.1, openrc/busybox failed during the first
boot.
The dmesg contains:
\[ 16.066159\] grsec: denied resource overstep by requesting 8392704 for
RLIMIT\_STACK against limit 8388608 for /lib/rc/sh/
gendepends.sh\[gendepends.sh:627\] uid/euid:0/0 gid/egid:0/0, parent
/lib/rc/sh/gendepends.sh\[gendepends.sh:554\] uid/euid:0/0
gid/egid:0/0
\[ 16.066192\] gendepends.sh\[627\]: segfault at 5c4f7f20 ip 13b36ba8 sp
5c4f7f24 error 6 in busybox\[13ae9000+e8000\]
\[ 16.066275\] grsec: Segmentation fault occurred at 5c4f7f20 in
/lib/rc/sh/gendepends.sh\[gendepends.sh:627\] uid/euid:0/0 g
id/egid:0/0, parent /lib/rc/sh/gendepends.sh\[gendepends.sh:554\]
uid/euid:0/0 gid/egid:0/0
\[ 16.066359\] grsec: denied resource overstep by requesting 4096 for
RLIMIT\_CORE against limit 0 for /lib/rc/sh/gendepends
.sh\[gendepends.sh:627\] uid/euid:0/0 gid/egid:0/0, parent
/lib/rc/sh/gendepends.sh\[gendepends.sh:554\] uid/euid:0/0 gid/egid:
0/0
\[ 17.299774\] grsec: denied resource overstep by requesting 8392704 for
RLIMIT\_STACK against limit 8388608 for /lib/rc/sh/
gendepends.sh\[gendepends.sh:739\] uid/euid:0/0 gid/egid:0/0, parent
/lib/rc/sh/gendepends.sh\[gendepends.sh:666\] uid/euid:0/0
gid/egid:0/0
\[ 17.299806\] gendepends.sh\[739\]: segfault at 59b4dffc ip 146074be sp
59b4e000 error 6 in busybox\[145be000+e8000\]
\[ 17.299891\] grsec: Segmentation fault occurred at 59b4dffc in
/lib/rc/sh/gendepends.sh\[gendepends.sh:739\] uid/euid:0/0 g
id/egid:0/0, parent /lib/rc/sh/gendepends.sh\[gendepends.sh:666\]
uid/euid:0/0 gid/egid:0/0
The system does not have BIOS battery, so clock skew during bootup is
guaranteed. However, this should not result in gendepends.sh crashing
busybox.
As result not all system services were started.
*(from redmine: issue id 1539, created on 2013-01-16, closed on 2013-01-18)*
* Relations:
* duplicates #1530Alpine 2.5.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1754DHCP at initrd time broken (ip=dhcp)2019-07-23T14:25:41ZHugo LandauDHCP at initrd time broken (ip=dhcp)The Alpine kernel is built with CONFIG\_IP\_PNP=y and
CONFIG\_IP\_PNP\_DHCP=y, which means that it should obtain an IP address
if booted with ip=dhcp. However, this appears to require that the
relevant network drivers are built into the ...The Alpine kernel is built with CONFIG\_IP\_PNP=y and
CONFIG\_IP\_PNP\_DHCP=y, which means that it should obtain an IP address
if booted with ip=dhcp. However, this appears to require that the
relevant network drivers are built into the kernel itself rather than as
modules.
We should therefore disable CONFIG\_IP\_PNP and call udhcpc at initrd
time if ip=dhcp is spotted in the command line. This will require
modification to the initrd init script and inclusion of an appropriate
udhcpc handler in the initrd.
This is a blocker for allowing Alpine to boot usefully with PXE (i.e.,
with a NFS or HTTP server as alpine\_dev.)
*(from redmine: issue id 1754, created on 2013-04-04, closed on 2013-04-26)*
* Changesets:
* Revision 7dc60785b198f0c4909c4e1d087614b844d05a95 by Natanael Copa on 2013-04-09T10:29:18Z:
```
main/linux-grsec: disable CONFIG_IP_PNP
fixes #1754
```Alpine 2.6.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1789Boot failure on ALIX during LED registration2019-07-23T14:25:07ZCarlo LandmeterBoot failure on ALIX during LED registrationOpenRC 0.11.8.f045407 is starting up Linux 3.8.7-0-grsec (i586)
* /proc is already mounted
* Mounting /run ... * /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Ca...OpenRC 0.11.8.f045407 is starting up Linux 3.8.7-0-grsec (i586)
* /proc is already mounted
* Mounting /run ... * /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ... [ ok ]
* Mounting security filesystem ... [ ok ]
* Mounting debug filesystem ... [ ok ]
* Mounting cgroup filesystem ... [ ok ]
* Starting busybox mdev ... [ ok ]
* Mounting modloop /media/sda1/boot/grsec.modloop.squashfs ... [ ok ]
* Loading hardware drivers ...[ 15.709955] general protection fault: 0000 [#1] SMP
[ 15.712287] Modules linked in: leds_gpio(+) via_rhine mii cs5535_mfd mfd_core geode_rng rng_core geode_aes isofs nls_utf8 nls_cp437 vfat fat pata_acpi pata_cs5536 pata_amd ata_generic libata ehci_pci ehci_hcd ohci_hcd usbcore usb_common sd_mod scsi_mod squashfs loop
[ 15.712287] Pid: 782, comm: modprobe Not tainted 3.8.7-0-grsec #1-Alpine
[ 15.712287] EIP: 0060:[<c1141043>] EFLAGS: 00010212 CPU: 0
[ 15.712287] EIP is at __gpio_cansleep+0xd/0x14
[ 15.712287] EAX: 00000000 EBX: ce3c2818 ECX: c1379bf0 EDX: 00000000
[ 15.712287] ESI: c142f7a4 EDI: c142f770 EBP: cdd67ddc ESP: cdd67dbc
[ 15.712287] DS: 0068 ES: 0068 FS: 00d8 GS: 007b SS: 0068
[ 15.712287] CR0: 8005003b CR2: aaa409b0 CR3: 0dd16000 CR4: 00000090
[ 15.712287] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 15.712287] DR6: ffff0ff0 DR7: 00000400
[ 15.712287] Process modprobe (pid: 782, ti=ce6d6a90 task=ce6d6700 task.ti=ce6d6a90)
[ 15.712287] Stack:
[ 15.712287] d0aa91cb 00000000 c142f660 ce3c2814 00000000 c142f660 c142f654 d0aa7014
[ 15.712287] cdd67df0 c11a5efd c142f660 d0aa7014 d0aa7014 cdd67e04 c11a4bf2 c142f660
[ 15.712287] d0aa7014 c142f694 cdd67e18 c11a4d2b cdd67e20 d0aa7014 00000000 cdd67e34
[ 15.712287] Call Trace:
[ 15.712287] [<d0aa91cb>] ? gpio_led_probe+0xba/0x203 [leds_gpio]
[ 15.712287] [<c11a5efd>] platform_drv_probe+0x26/0x48
[ 15.712287] [<c11a4bf2>] driver_probe_device+0x80/0x172
[ 15.712287] [<c11a4d2b>] __driver_attach+0x47/0x63
[ 15.712287] [<c11a38db>] bus_for_each_dev+0x3c/0x66
[ 15.712287] [<c11a4899>] driver_attach+0x14/0x16
[ 15.712287] [<c11a4ce4>] ? driver_probe_device+0x172/0x172
[ 15.712287] [<c11a4577>] bus_add_driver+0xbd/0x1bc
[ 15.712287] [<d0aab000>] ? 0xd0aaafff
[ 15.712287] [<d0aab000>] ? 0xd0aaafff
[ 15.712287] [<c11a51a0>] driver_register+0x74/0xec
[ 15.712287] [<c12784c8>] ? notifier_call_chain+0x25/0x46
[ 15.712287] [<d0aab000>] ? 0xd0aaafff
[ 15.712287] [<c11a5a8c>] platform_driver_register+0x38/0x3a
[ 15.712287] [<d0aab00d>] gpio_led_driver_init+0xd/0x5b5 [leds_gpio]
[ 15.712287] [<c1001173>] do_one_initcall+0x6a/0xff
[ 15.712287] [<c1063d30>] load_module+0x15b2/0x18de
[ 15.712287] [<c109f731>] ? insert_vmalloc_vmlist+0x14/0x52
[ 15.712287] [<c10a0eee>] ? __vmalloc_node_range+0x13e/0x15f
[ 15.712287] [<c106416f>] sys_init_module+0x113/0x129
[ 15.712287] [<c12758cf>] syscall_call+0x7/0xb
[ 15.712287] Code: 00 5c 50 c1 75 14 8b 82 04 5c 50 c1 a8 01 74 0a 8b 8a 08 5c 50 c1 eb 02 31 c9 89 c8 5d c3 6b c0 0c 55 89 e5 5d 8b 80 00 5c 50 c1 <8a> 40 40 83 e0 01 c3 6b d0 0c 55 89 e5 53 8b 8a 00 5c 50 c1 8b
[ 15.712287] EIP: [<c1141043>] __gpio_cansleep+0xd/0x14 SS:ESP 0068:cdd67dbc
[ 15.714343] ---[ end trace d6fdd52620ab8376 ]---
[ 16.491213] cs5535-gpio cs5535-gpio: reserved resource region [io 0x6100-0x61ff]
[ 16.604968] cs5535-mfgpt cs5535-mfgpt: reserved resource region [io 0x6200-0x623f]
[ 16.606766] cs5535-mfgpt cs5535-mfgpt: 8 MFGPT timers available
*(from redmine: issue id 1789, created on 2013-04-17, closed on 2013-05-17)*
* Changesets:
* Revision 38b0da640df3b549dea1106199baeddda85057cd by Natanael Copa on 2013-05-17T10:30:49Z:
```
main/linux-grsec: upgrade to 2.9.1-3.9.2-201305162327 and fix boot on alix
fixes #1789
```Alpine 2.6.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/1850startscript /etc/init.d/xendomains ignores XENDOMAINS_CREATE_USLEEP defined i...2019-07-23T14:24:26ZDieter Blomsstartscript /etc/init.d/xendomains ignores XENDOMAINS_CREATE_USLEEP defined in /etc/default/xendomainsHi,
in the configfile /etc/default/xendomains is a parameter
XENDOMAINS\_CREATE\_USLEEP=5000000.
For me it looks like this parameter is ignored by the start script and
the domains are started without
waiting this defined time after ...Hi,
in the configfile /etc/default/xendomains is a parameter
XENDOMAINS\_CREATE\_USLEEP=5000000.
For me it looks like this parameter is ignored by the start script and
the domains are started without
waiting this defined time after each domain start.
If attached a little patch which fixes this problem for me.
Maybe you will accept and include it for the final release.
*(from redmine: issue id 1850, created on 2013-05-08, closed on 2013-05-17)*
* Changesets:
* Revision ef80eb1f042d2bfe8d0588e6d248b42cb1b33552 by Natanael Copa on 2013-05-16T16:54:57Z:
```
main/xen: sleep a bit when starting up xen domains
fixes #1850
```
* Revision 939441c1cc213c7cee15ff9af002c1fba512a6e0 by Natanael Copa on 2013-05-21T11:55:47Z:
```
main/xen: sleep a bit when starting up xen domains
fixes #1850
(cherry picked from commit ef80eb1f042d2bfe8d0588e6d248b42cb1b33552)
```
* Uploads:
* [xendomains.diff](/uploads/82ea808568f60ec9d02b3966542371a4/xendomains.diff) my little patch which add a usleep to each start of a domUAlpine 2.6.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2071usb keyboard does not work in emergency console2019-07-23T14:21:14ZCarlo Landmeterusb keyboard does not work in emergency consoleI made a diff of lsmod when plugging in the keyboard. dmesg also
included.
PS this install has udev running.
@@ -1,4 +1,8 @@
Module Size Used by Not tainted
+hid_generic 1188 0
+usbhi...I made a diff of lsmod when plugging in the keyboard. dmesg also
included.
PS this install has udev running.
@@ -1,4 +1,8 @@
Module Size Used by Not tainted
+hid_generic 1188 0
+usbhid 29506 0
+hid 84338 2 hid_generic,usbhid
+usbkbd 4460 0
ipv6 290957 20
af_packet 26467 0
fbcon 34076 70
@@ -94,7 +98,7 @@
pata_acpi 3286 0
libata 180626 3 ata_generic,ata_piix,pata_acpi
usb_storage 48293 2 ums_realtek
-usbcore 161029 7 btusb,ums_realtek,uvcvideo,ehci_pci,ehci_hcd,uhci_hcd,usb_storage
+usbcore 161029 9 usbhid,usbkbd,btusb,ums_realtek,uvcvideo,ehci_pci,ehci_hcd,uhci_hcd,usb_storage
usb_common 1037 1 usbcore
sd_mod 26613 2
scsi_mod 108736 4 sr_mod,libata,usb_storage,sd_mod
[ 1.232354] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 1.303355] tsc: Refined TSC clocksource calibration: 1995.224 MHz
[ 1.303363] Switching to clocksource tsc
[ 1.453349] usb 7-1: new high-speed USB device number 2 using ehci-pci
[ 1.827375] usb 7-1: New USB device found, idVendor=0bda, idProduct=0158
[ 1.827379] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.827381] usb 7-1: Product: USB2.0-CRW
[ 1.827384] usb 7-1: Manufacturer: Generic
[ 1.827387] usb 7-1: SerialNumber: 20071114173400000
[ 2.193348] usb 7-4: new high-speed USB device number 4 using ehci-pci
[ 2.337627] usb 7-4: New USB device found, idVendor=0408, idProduct=20ba
[ 2.337632] usb 7-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 2.337635] usb 7-4: Product: USB Webcam
[ 2.337638] usb 7-4: Manufacturer: SN001
[ 2.446682] usb 8-2: new high-speed USB device number 2 using ehci-pci
[ 2.505782] ehci-pci 0000:00:1d.7: port 2 reset error -110
[ 2.506676] ehci-pci 0000:00:1d.7: port 2 reset error -110
[ 2.510664] ehci-pci 0000:00:1d.7: port 2 reset error -110
[ 2.513108] ehci-pci 0000:00:1d.7: port 2 reset error -110
[ 2.514002] ehci-pci 0000:00:1d.7: port 2 reset error -110
[ 2.515554] hub 8-0:1.0: hub_port_status failed (err = -32)
[ 2.716694] hub 8-0:1.0: unable to enumerate USB device on port 2
[ 3.073345] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[ 3.235660] usb 2-1: New USB device found, idVendor=18e8, idProduct=6252
[ 3.235664] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.235667] usb 2-1: Product: Broadcom Bluetooth USB
[ 3.235670] usb 2-1: Manufacturer: Broadcom Corp
[ 3.586679] usb 3-2: new full-speed USB device number 2 using uhci_hcd
[ 3.720702] usb 3-2: not running at top speed; connect to a high speed hub
[ 3.748700] usb 3-2: New USB device found, idVendor=14cd, idProduct=121c
[ 3.748704] usb 3-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 3.748707] usb 3-2: Product: Mass Storage Device
[ 3.748709] usb 3-2: Manufacturer: Generic
[ 3.748712] usb 3-2: SerialNumber: 812320100708
[ 3.753368] scsi4 : usb-storage 3-2:1.0
[ 4.838733] scsi 4:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 4.850742] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 4.984743] sd 4:0:0:0: [sdb] 7716864 512-byte logical blocks: (3.95 GB/3.67 GiB)
[ 4.990716] sd 4:0:0:0: [sdb] No Caching mode page present
[ 4.990721] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 5.006711] sd 4:0:0:0: [sdb] No Caching mode page present
[ 5.006714] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 5.012717] sdb: sdb1
[ 5.260729] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 193.869329] udevd[1102]: starting version 175
[ 195.423372] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 195.423686] ACPI: AC Adapter [ACAD] (on-line)
[ 195.543435] ACPI: Requesting acpi_cpufreq
[ 195.543747] Monitor-Mwait will be used to enter C-1 state
[ 195.543755] Monitor-Mwait will be used to enter C-2 state
[ 195.543760] Monitor-Mwait will be used to enter C-3 state
[ 195.543764] tsc: Marking TSC unstable due to TSC halts in idle
[ 195.543778] ACPI: acpi_idle registered with cpuidle
[ 195.544182] Switching to clocksource hpet
[ 195.622150] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 195.622159] ACPI: Power Button [PWRB]
[ 195.622220] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
[ 195.630054] ACPI: Lid Switch [LID0]
[ 195.630138] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
[ 195.630145] ACPI: Sleep Button [SLPB]
[ 195.630231] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 195.630234] ACPI: Power Button [PWRF]
[ 195.694996] thermal LNXTHERM:00: registered as thermal_zone0
[ 195.695000] ACPI: Thermal Zone [TZ01] (76 C)
[ 195.935928] acpi device:07: registered as cooling_device2
[ 195.935959] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[ 195.936016] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/LNXVIDEO:01/input/input5
[ 195.974162] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 195.974172] ACPI: Battery Slot [BAT0] (battery present)
[ 196.438951] wmi: Mapper loaded
[ 196.749704] Linux agpgart interface v0.103
[ 196.868938] [drm] Initialized drm 1.1.0 20060810
[ 197.464399] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x298480a2
[ 197.464405] nouveau [ DEVICE][0000:01:00.0] Chipset: G98 (NV98)
[ 197.464407] nouveau [ DEVICE][0000:01:00.0] Family : NV50
[ 197.465960] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
[ 197.557284] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
[ 197.557288] nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN
[ 197.557543] nouveau [ VBIOS][0000:01:00.0] BIT signature found
[ 197.557546] nouveau [ VBIOS][0000:01:00.0] version 62.98.4e.00.33
[ 197.577827] nouveau [ PFB][0000:01:00.0] RAM type: DDR2
[ 197.577831] nouveau [ PFB][0000:01:00.0] RAM size: 256 MiB
[ 197.577834] nouveau [ PFB][0000:01:00.0] ZCOMP: 960 tags
[ 197.603765] nouveau [ PTHERM][0000:01:00.0] FAN control: none / external
[ 197.603776] nouveau [ PTHERM][0000:01:00.0] fan management: disabled
[ 197.603787] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes
[ 197.603792] nouveau [ PTHERM][0000:01:00.0] Programmed thresholds [ 90(3), 95(3), 105(2), 110(5) ]
[ 197.604010] [TTM] Zone kernel: Available graphics memory: 1025786 kiB
[ 197.604012] [TTM] Initializing pool allocator
[ 197.604020] [TTM] Initializing DMA pool allocator
[ 197.604717] nouveau [ DRM] VRAM: 256 MiB
[ 197.604722] nouveau [ DRM] GART: 512 MiB
[ 197.604728] nouveau [ DRM] TMDS table version 2.0
[ 197.604731] nouveau [ DRM] DCB version 4.0
[ 197.604734] nouveau [ DRM] DCB outp 00: 01000323 00010034
[ 197.604737] nouveau [ DRM] DCB outp 01: 02014300 00000028
[ 197.604740] nouveau [ DRM] DCB outp 02: 02021332 00020010
[ 197.604742] nouveau [ DRM] DCB conn 00: 00000340
[ 197.604745] nouveau [ DRM] DCB conn 01: 00001061
[ 197.604748] nouveau [ DRM] DCB conn 02: 00000147
[ 197.604750] nouveau [ DRM] DCB conn 03: 00002131
[ 197.604753] nouveau [ DRM] DCB conn 04: 00000400
[ 197.604755] nouveau [ DRM] DCB conn 05: 00000210
[ 197.604757] nouveau [ DRM] DCB conn 06: 00000211
[ 197.604760] nouveau [ DRM] DCB conn 07: 00000213
[ 197.623400] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 197.623403] [drm] No driver support for vblank timestamp query.
[ 197.623407] nouveau [ DRM] ACPI backlight interface available, not registering our own
[ 197.623555] nouveau [ DRM] 4 available performance level(s)
[ 197.623560] nouveau [ DRM] 0: core 169MHz shader 338MHz memory 100MHz voltage 900mV fanspeed 100%
[ 197.623564] nouveau [ DRM] 1: core 275MHz shader 550MHz memory 250MHz voltage 900mV fanspeed 100%
[ 197.623569] nouveau [ DRM] 2: core 500MHz shader 1000MHz memory 400MHz voltage 1090mV fanspeed 100%
[ 197.623573] nouveau [ DRM] 3: core 580MHz shader 1450MHz memory 400MHz voltage 1170mV fanspeed 100%
[ 197.623578] nouveau [ DRM] c: core 275MHz shader 550MHz memory 249MHz voltage 1090mV
[ 197.648999] nouveau [ DRM] MM: using M2MF for buffer copies
[ 197.695109] nouveau [ DRM] allocated 1280x800 fb: 0x60000, bo ffff88007b876800
[ 197.695212] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[ 197.695215] nouveau 0000:01:00.0: registered panic notifier
[ 197.695220] [drm] Initialized nouveau 1.1.0 20120801 for 0000:01:00.0 on minor 0
[ 197.882352] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 197.882721] r8169 0000:05:00.0: irq 44 for MSI/MSI-X
[ 197.882881] r8169 0000:05:00.0 eth0: RTL8102e at 0xffffc9000463a000, 00:1e:68:f2:c9:67, XID 14a00000 IRQ 44
[ 197.970997] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMBA 1 (20130117/utaddress-251)
[ 197.971005] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 197.971009] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251)
[ 197.971014] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 197.971016] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20130117/utaddress-251)
[ 197.971021] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 197.971023] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 197.976788] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
[ 198.492325] iTCO_vendor_support: vendor-support=0
[ 198.492655] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 198.492695] iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0460)
[ 198.492826] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 199.036382] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[ 199.286243] input: HDA Intel HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[ 199.286397] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 199.286471] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 199.361386] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 199.426856] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 199.691853] cfg80211: Calling CRDA to update world regulatory domain
[ 199.878065] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 199.878070] Copyright(c) 2003-2013 Intel Corporation
[ 199.878375] iwlwifi 0000:02:00.0: irq 46 for MSI/MSI-X
[ 199.884544] input: PC Speaker as /devices/platform/pcspkr/input/input9
[ 200.190782] iwlwifi 0000:02:00.0: loaded firmware version 8.83.5.1 build 33692
[ 200.754376] media: Linux media interface: v0.10
[ 201.018292] Linux video capture interface: v2.00
[ 201.142146] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 201.142151] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 201.142154] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[ 201.142157] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[ 201.142160] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_P2P disabled
[ 201.142163] iwlwifi 0000:02:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[ 201.142193] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
[ 201.148025] uvcvideo: Found UVC 1.00 device USB Webcam (0408:20ba)
[ 201.148075] psmouse serio1: synaptics: Touchpad model: 1, fw: 6.5, id: 0x1c0b1, caps: 0xa04751/0xa00000/0x0, board id: 3655, fw id: 428212
[ 201.154215] input: USB Webcam as /devices/pci0000:00/0000:00:1a.7/usb7/7-4/7-4:1.0/input/input10
[ 201.160705] usbcore: registered new interface driver uvcvideo
[ 201.160709] USB Video Class driver (1.1.1)
[ 201.220615] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input11
[ 201.275663] scsi5 : usb-storage 7-1:1.0
[ 201.275748] usbcore: registered new interface driver ums-realtek
[ 201.418892] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 201.588411] mousedev: PS/2 mouse device common for all mice
[ 201.876219] Bluetooth: Core ver 2.16
[ 201.876248] NET: Registered protocol family 31
[ 201.876250] Bluetooth: HCI device and connection manager initialized
[ 201.876261] Bluetooth: HCI socket layer initialized
[ 201.876265] Bluetooth: L2CAP socket layer initialized
[ 201.876273] Bluetooth: SCO socket layer initialized
[ 201.939287] usbcore: registered new interface driver btusb
[ 202.278929] scsi 5:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
[ 202.284427] sd 5:0:0:0: [sdc] Attached SCSI removable disk
[ 203.481130] Console: switching to colour frame buffer device 160x50
[ 203.575354] NET: Registered protocol family 17
[ 203.592794] grsec: time set by /bin/busybox[hwclock:1396] uid/euid:0/0 gid/egid:0/0, parent /lib/rc/sh/runscript.sh[runscript.sh:1387] uid/euid:0/0 gid/egid:0/0
[ 203.781198] r8169 0000:05:00.0 eth0: link down
[ 203.781235] r8169 0000:05:00.0 eth0: link down
[ 205.373816] r8169 0000:05:00.0 eth0: link up
[ 211.162428] NET: Registered protocol family 10
[ 239.573346] usb 3-1: new low-speed USB device number 3 using uhci_hcd
[ 239.839828] usb 3-1: New USB device found, idVendor=046e, idProduct=52c1
[ 239.839832] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 239.839835] usb 3-1: Product: USB Multimedia Keyboard
[ 239.839838] usb 3-1: Manufacturer: BTC
[ 240.015216] input: BTC USB Multimedia Keyboard as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1:1.0/input/input12
[ 240.015328] usbcore: registered new interface driver usbkbd
[ 240.017378] hidraw: raw HID events driver (C) Jiri Kosina
[ 240.134903] usbcore: registered new interface driver usbhid
[ 240.134906] usbhid: USB HID core driver
[ 240.207904] input: BTC USB Multimedia Keyboard as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1:1.1/input/input13
[ 240.208037] hid-generic 0003:046E:52C1.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [BTC USB Multimedia Keyboard] on usb-0000:00:1d.0-1/input1
*(from redmine: issue id 2071, created on 2013-06-06, closed on 2013-08-07)*
* Changesets:
* Revision 79fd28fa96d12a25831ef7761d58c633ab9cb727 by Natanael Copa on 2013-08-07T08:40:02Z:
```
main/busybox-initscripts: fix module autoloading
ref #2071
```
* Revision 1747953569f36106c1f30207067c466154ede6d4 by Natanael Copa on 2013-08-07T08:40:49Z:
```
main/mkinitfs: add hid-generic driver to fix usb keyboards
ref #2071
```
* Revision 28da60a05e96fa74584fbff529639bab30833353 by Natanael Copa on 2013-08-07T13:36:38Z:
```
main/busybox-initscripts: fix module autoloading
ref #2071
(cherry picked from commit 79fd28fa96d12a25831ef7761d58c633ab9cb727)
```
* Revision f0b476449f4f3d020cd0217348604352264c9d6c by Natanael Copa on 2013-08-07T13:37:00Z:
```
main/mkinitfs: upgrade to 2.5.0
fixes #2071
```Alpine 2.6.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2269apkovl not loaded from usb when booting from CD unless ovl_dev is set on boot...2019-07-23T14:18:30ZHernan Scarnichiaapkovl not loaded from usb when booting from CD unless ovl_dev is set on boot parametersWhen booting from CD the apkovl saved on usb is not loaded on boot.
steps to reproduce:
1. boot from cd
2. setup-alpine (disk none and lbu usb, etc.)
3. lbu ci -e
4. verify the apkovl file is on the usb
5. reboot from cd
6. ...When booting from CD the apkovl saved on usb is not loaded on boot.
steps to reproduce:
1. boot from cd
2. setup-alpine (disk none and lbu usb, etc.)
3. lbu ci -e
4. verify the apkovl file is on the usb
5. reboot from cd
6. the opkovl is not loaded.
WORKAROUND: add ovl\_dev=usbdisk:vfat to the boot parameters, or alter
isolinux.cfg and make new .iso
tested on versions 2.6.5 and 2.6.4
*(from redmine: issue id 2269, created on 2013-10-07, closed on 2017-04-08)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2360LUKS encrypted root does not mount (Alpine 2.7.0)2019-07-23T14:17:14ZStuart CardallLUKS encrypted root does not mount (Alpine 2.7.0)LUKS encrypted root fails to mount on booting.
**/etc/mkinitfs/files.d/cryptsetup** appears to be missing:
/lib/libdl.so.\* (just before libz.so)
This does not seem to fix root not being mounted - the emergency initram
shell still has...LUKS encrypted root fails to mount on booting.
**/etc/mkinitfs/files.d/cryptsetup** appears to be missing:
/lib/libdl.so.\* (just before libz.so)
This does not seem to fix root not being mounted - the emergency initram
shell still has no option for cryptsetup
*(from redmine: issue id 2360, created on 2013-11-18, closed on 2013-11-19)*
* Changesets:
* Revision a66095b9d8d8bb9e10f9978c746710ed0fce75d9 by Natanael Copa on 2013-11-18T16:09:08Z:
```
main/mkinitfs: add missing dependency for cryptsetup
ref #2360
```
* Revision 8cbcfd63d0193e3bb35e386123a5e31be77dec02 by Natanael Copa on 2013-11-18T16:10:17Z:
```
main/mkinitfs: add missing dependency for cryptsetup
fixes #2360
```Alpine 2.7.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/2445LUKS encrypted root does not mount2019-07-23T14:16:12ZDubiousjim .LUKS encrypted root does not mountLUKS encrypted root fails to mount on booting.
**/etc/mkinitfs/files.d/cryptsetup** appears to be missing:
/lib/libpthread**.so**
This problem is similar to http://bugs.alpinelinux.org/issues/2360, but
involves a different missing dep...LUKS encrypted root fails to mount on booting.
**/etc/mkinitfs/files.d/cryptsetup** appears to be missing:
/lib/libpthread**.so**
This problem is similar to http://bugs.alpinelinux.org/issues/2360, but
involves a different missing dependency. Alternatively, perhaps
cryptsetup should be built without relying on the threads library?
*(from redmine: issue id 2445, created on 2013-12-01, closed on 2013-12-09)*
* Changesets:
* Revision 944e4b6299ecbd45a3472a8e129fc85ea67d576f by Natanael Copa on 2013-12-02T14:15:47Z:
```
main/mkinitfs: add missing libpthread dep for cryptsetup
ref #2445
```
* Revision 65a01bc959382a5ef376022a4f29866e292f38dd by Natanael Copa on 2013-12-02T14:16:55Z:
```
main/mkinitfs: add missing libpthread dep for cryptsetup
fixes #2445
```Alpine 2.7.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2527Issue with booting Alpine on Syslinux 5.02-pre32019-07-23T14:11:35ZMicah JohnsonIssue with booting Alpine on Syslinux 5.02-pre3I have an interesting problem when booting Alpine 2.6.4 with syslinux
5.02-pre3. When I boot the system, the “boot:” prompt is displayed and
never boots. If I hit the enter key, the system will begin booting
normally. Here is a copy of m...I have an interesting problem when booting Alpine 2.6.4 with syslinux
5.02-pre3. When I boot the system, the “boot:” prompt is displayed and
never boots. If I hit the enter key, the system will begin booting
normally. Here is a copy of my syslinux.cfg:
serial 0 9600
timeout 20
prompt 1
default grsec
label grsec
kernel /boot/graces
append initrd=/boot/grsec.gz alpine_dev=usbdisk:vfat modules=loop,squashfs,sd-mod,usb-storage console=tty1,38400 console=ttyS0,9600
If I remove the “prompt 1” line, the system doesn’t display the “boot:”
prompt but the system boots with no issue. However, on other Alpine
boxes (with different syslinux versions), I have the above configuration
and the “boot:” prompt is displayed for 2 seconds and then the system
boots normally. We have used this prompt feature in the past to assist
with password recovery and we would like to have this feature available
if possible.
Thanks for looking into this issue!!
Micah Johnson
*(from redmine: issue id 2527, created on 2013-12-23, closed on 2015-12-09)*
* Relations:
* duplicates #2748
* Changesets:
* Revision 67ca8d827f7c656d50a7104f779b060263a2759a by Natanael Copa on 2013-12-30T11:13:29Z:
```
main/syslinux: upgrade to 5.10
fixes #2527
(cherry picked from commit fbdf208c06a960a3b768309c96d0d112ea41fda5)
```Alpine 2.6.7Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2529booting x86_64 with apkvol generated from x86 fails2019-07-23T14:14:57ZNatanael Copabooting x86_64 with apkvol generated from x86 failsbooting ends with:
/sbin/init not found in new root. Launching emergency recovery shell
Type exit to continue boot.
I believe it happens because /etc/apk/arch has ‘x86’.
We should try detect and fixup this from initramfs init ...booting ends with:
/sbin/init not found in new root. Launching emergency recovery shell
Type exit to continue boot.
I believe it happens because /etc/apk/arch has ‘x86’.
We should try detect and fixup this from initramfs init script.
*(from redmine: issue id 2529, created on 2013-12-25, closed on 2014-01-07)*
* Changesets:
* Revision 60c0c254f011816eb7354794dcb5a04967b98ef4 by Natanael Copa on 2014-01-07T10:51:54Z:
```
main/mkinitfs: upgrade to 2.5.3
fixes #2529
```Alpine 2.7.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2616Alpine 2.7 fails to boot on Tyan S52112019-07-15T14:12:05ZDave SandersonAlpine 2.7 fails to boot on Tyan S5211Booting Alpine 2.7 hangs at Loading Hardware Drivers, adding noquiet to
the boot string does not provide any useful data.
I have tried but x86 and x86\_64 builds as well as the 2.6 build.
The screen flashes once then hangs, a ctr-alt-d...Booting Alpine 2.7 hangs at Loading Hardware Drivers, adding noquiet to
the boot string does not provide any useful data.
I have tried but x86 and x86\_64 builds as well as the 2.6 build.
The screen flashes once then hangs, a ctr-alt-del will restart the
system, but otherwise it remains unresponsive.
*(from redmine: issue id 2616, created on 2014-01-31)*
* Uploads:
* ![alpine-hang](/uploads/b3ce31da00da3ab955db7db3a93f338b/alpine-hang.png)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/2880udhcpc default.script (busybox-initscripts) fails to set broadcast address2019-07-23T14:09:39ZA. Wilcoxudhcpc default.script (busybox-initscripts) fails to set broadcast addressThe default.script file included in the busybox-initscripts package does
not use the ‘broadcast’ variable, and therefore when setting the IP
address the machines have broadcast IP set to 0.0.0.0.
My shell-fu is not very good, or I would...The default.script file included in the busybox-initscripts package does
not use the ‘broadcast’ variable, and therefore when setting the IP
address the machines have broadcast IP set to 0.0.0.0.
My shell-fu is not very good, or I would submit a patch; needless to
say, if the broadcast variable is set, it should be used as such:
88: ip addr add $ip/$mask broadcast $broadcast dev $interface
97: ip addr add $ip/$mask broadcast $broadcast dev $interface
I have just added this to my own custom package because I know that
broadcast will always be provided by our DHCP server. But it is not
always, so it should probably be determined if it is set before blindly
using it as I have above. This is just the syntax to use if it is set.
Thank you for your consideration.
*(from redmine: issue id 2880, created on 2014-05-05, closed on 2014-05-06)*
* Changesets:
* Revision 692420e9abb5049050b09d1385ad98befba1ecfc by Natanael Copa on 2014-05-06T10:35:20Z:
```
main/busybox-initscripts: add support for broadcast from dhcp
ref #2880
```
* Revision ba260652227f85da4d7b0acf7fcc80f3e7e57521 by Natanael Copa on 2014-05-06T10:57:15Z:
```
main/busybox-initscripts: add support for broadcast from dhcp
fixes #2880
(cherry picked from commit 692420e9abb5049050b09d1385ad98befba1ecfc)
```Alpine 2.7.7Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3265wrong path name in /etc/mkinitfs/features.d/gfs2.modules and ocfs2.modules2019-07-23T14:03:54ZIgor Falcomatawrong path name in /etc/mkinitfs/features.d/gfs2.modules and ocfs2.moduleskvaio64:/etc/mkinitfs/features.d# grep -F "kerne/" *
gfs2.modules:kerne/fs/gfs2
ocfs2.modules:kerne/fs/ocfs2
^^^^^
*(from redmine: issue id 3265, created on 2014-07-29, closed on 2014-08-11)*
* Changesets:
...kvaio64:/etc/mkinitfs/features.d# grep -F "kerne/" *
gfs2.modules:kerne/fs/gfs2
ocfs2.modules:kerne/fs/ocfs2
^^^^^
*(from redmine: issue id 3265, created on 2014-07-29, closed on 2014-08-11)*
* Changesets:
* Revision 7c015fedaa64a1800751771deadc85a0be12f2d1 by Natanael Copa on 2014-07-31T09:12:31Z:
```
main/mkinitfs: fix typo for gfs2 and ocfs2 modules
ref #3265
```
* Revision 05395d8e45071116e6fdbe5f93788448e16fdc5c by Natanael Copa on 2014-07-31T09:16:44Z:
```
main/mkinitfs: fix typo for gfs2 and ocfs2 modules
fixes #3265
(cherry picked from commit 7c015fedaa64a1800751771deadc85a0be12f2d1)
```3.0.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3273Boot hangs on ISOLINUX2019-07-23T14:03:49ZNick HovakerBoot hangs on ISOLINUXWhen booting Alpine Linux 3.0.2 or 3.0.1, the installer just hangs on
“ISOLINUX 6.02 2013-10-13 ETCD”. This happens on both x86 and x86-64
standard ISO images.
*(from redmine: issue id 3273, created on 2014-07-30, closed on 2014-08-11)...When booting Alpine Linux 3.0.2 or 3.0.1, the installer just hangs on
“ISOLINUX 6.02 2013-10-13 ETCD”. This happens on both x86 and x86-64
standard ISO images.
*(from redmine: issue id 3273, created on 2014-07-30, closed on 2014-08-11)*
* Changesets:
* Revision d62b3ba99a840efefaefe12e64f673ef9457f828 by Natanael Copa on 2014-08-01T10:09:17Z:
```
main/syslinux: upgrade to 6.03_pre19
ref #3273
```
* Revision 2aeefcde7d385dbd1b74eb4218dbcceb11907a5a by Natanael Copa on 2014-08-06T14:21:09Z:
```
main/syslinux: upgrade to 6.03_pre19
fixes #3273
(cherry picked from commit d62b3ba99a840efefaefe12e64f673ef9457f828)
```3.0.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3420initfs won't boot encrypted rootfs from LVM2019-07-23T14:01:37ZJohannes Matheisinitfs won't boot encrypted rootfs from LVM/usr/share/mkinitfs/initramfs-init first calls start\_cryptsetup and
then start\_lvm.
On a system with encrypted logical volumes the order has to be reversed.
*(from redmine: issue id 3420, created on 2014-10-08, closed on 2017-04-07.../usr/share/mkinitfs/initramfs-init first calls start\_cryptsetup and
then start\_lvm.
On a system with encrypted logical volumes the order has to be reversed.
*(from redmine: issue id 3420, created on 2014-10-08, closed on 2017-04-07)*
* Changesets:
* Revision 4c42c322adc76ab8c6991cb697b1076dea7c8a91 by Natanael Copa on 2014-11-10T13:52:57Z:
```
main/mkinitfs: upgrade to 2.7.0
fixes #3240
fixes #3420
```Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3506bridge autocreation in /etc/init.d/networking seems to be broken2019-07-23T14:00:36ZThomas Zelchbridge autocreation in /etc/init.d/networking seems to be brokenHi,
It seems that the /etc/init.d/networking script is currently not able to
create configured Bridges automatically.
If i do a default Configuration like stated in the Wiki:
auto eth0
iface eth0 inet manual
auto br0
iface br0 in...Hi,
It seems that the /etc/init.d/networking script is currently not able to
create configured Bridges automatically.
If i do a default Configuration like stated in the Wiki:
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.0.253
netmask 255.255.255.0
gateway 192.168.0.254
bridge\_ports eth0
bridge\_stp 0
I get the following Error during boot:
ip: can’t find device ‘br0’
ip: ioctl 0x8913 failed: no such device
ip: can’t find device ‘br0’
Only if i do something ugly like:
auto br0
iface br0 inet static
pre-up brctl addbr br0
address 192.168.0.253
netmask 255.255.255.0
gateway 192.168.0.254
auto eth0
iface eth0 inet manual
up brctl addif br0 eth0
Then it will work.
This happend in the current Alpine Version 3.0.6
*(from redmine: issue id 3506, created on 2014-11-12, closed on 2019-06-11)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3555switching graphical mode in boot process and KVM install in CLI2019-07-23T14:00:07ZJean-Charles de Longuevilleswitching graphical mode in boot process and KVM install in CLIWhen following http://wiki.alpinelinux.org/wiki/Qemu to install a brand
new KVM based on alpine…
I’m doing it in a gnome terminal on a awesome desktop connected trhough
ssh to a screen on the remote machine running the KVMs from comman...When following http://wiki.alpinelinux.org/wiki/Qemu to install a brand
new KVM based on alpine…
I’m doing it in a gnome terminal on a awesome desktop connected trhough
ssh to a screen on the remote machine running the KVMs from command
line.
Launching the KVM for the first time from the freshly downloaded ISO
starts well but then proceed to switch to **“1024 x 768 Graphic mode”**
which I cannot follow anymore in my terminal window :(
My command to launch the KVM is
qemu-system-x86_64 -enable-kvm -smp 1 -m 256 -cdrom alpine-mini-3.0.6-x86_64.iso -hda kvm-alpine.qcow2 -boot d -net nic -net user -nographic -localtime -display curses
*(from redmine: issue id 3555, created on 2014-11-25, closed on 2014-12-09)*
* Changesets:
* Revision 545977c1fde1dadc99987aedc2912d93243c28a9 by Natanael Copa on 2014-12-03T12:00:17Z:
```
main/alpine-conf: pass nomodeset boot option to installed disk
fixes #3555
```3.1.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3609kernel panic when using xen-pciback Module2019-07-23T13:59:40ZThomas Zelchkernel panic when using xen-pciback ModuleHi,
When configuring the xen-pciback Module in the kernel Options, the
Kernel Panics.
the kernel panics with message /init: /eval: line 1: syntax error
unexpected “(”
/etc/update-extlinux.conf looks like this:
default\_kernel\_opts=...Hi,
When configuring the xen-pciback Module in the kernel Options, the
Kernel Panics.
the kernel panics with message /init: /eval: line 1: syntax error
unexpected “(”
/etc/update-extlinux.conf looks like this:
default\_kernel\_opts=“quiet cryptroot=/dev/sda2 cryptdm=root
xen-pciback.hide=(01:00.0)”
*(from redmine: issue id 3609, created on 2014-12-10, closed on 2015-05-26)*3.2.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/3636GnuTLS initialization: Failed to acquire random data2019-07-23T13:59:17ZDennis PrzytarskiGnuTLS initialization: Failed to acquire random dataBoot continues normally.
*(from redmine: issue id 3636, created on 2014-12-14, closed on 2015-05-14)*
* Uploads:
* ![gnutls](/uploads/a58b4617b26ac21ec8ff7a8b8ad59787/gnutls.png)Boot continues normally.
*(from redmine: issue id 3636, created on 2014-12-14, closed on 2015-05-14)*
* Uploads:
* ![gnutls](/uploads/a58b4617b26ac21ec8ff7a8b8ad59787/gnutls.png)3.1.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3741Request: make isos grub2 detectable2019-07-12T14:53:54ZV KrishnRequest: make isos grub2 detectableBuild iso in way that it can be detected via grub2
or booted/loaded directly via grub2.
*(from redmine: issue id 3741, created on 2015-01-23, closed on 2015-05-26)*Build iso in way that it can be detected via grub2
or booted/loaded directly via grub2.
*(from redmine: issue id 3741, created on 2015-01-23, closed on 2015-05-26)*3.2.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/3846init.d/modloop fails for virt-grsec2019-07-23T13:57:41ZTimo Teräsinit.d/modloop fails for virt-grsecinit.d/modloop now searches modloop based on the uname.
It seems ${kver\#\#\*<s>} is used, but that will return ’grsec’ for my
’3.14.30-1-virt-grsec’ kernel. It works only for flavors that do not
have ’</s>’ in them.
*(from redmine: i...init.d/modloop now searches modloop based on the uname.
It seems ${kver\#\#\*<s>} is used, but that will return ’grsec’ for my
’3.14.30-1-virt-grsec’ kernel. It works only for flavors that do not
have ’</s>’ in them.
*(from redmine: issue id 3846, created on 2015-01-31, closed on 2015-03-20)*
* Changesets:
* Revision 8eee05cbbaca2f797bbeee6bcebf03c6642fe332 on 2015-02-03T10:38:50Z:
```
main/linux-virt-grsec: rename into linux-virtgrsec. Fixes #3846
```3.1.3Leonardo ArenaLeonardo Arenahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4015issue with modloop start/stop when PXEboot2019-07-23T13:55:27ZJean-Charles de Longuevilleissue with modloop start/stop when PXEbootHi,
when using PXE to boot AL in ram mode, there is an issue with modloop at
boot time and another one at shutdown.
### boot
At boot time, the modloop squashfs doesn’t load nor from the NFS share
nor from the http offering because th...Hi,
when using PXE to boot AL in ram mode, there is an issue with modloop at
boot time and another one at shutdown.
### boot
At boot time, the modloop squashfs doesn’t load nor from the NFS share
nor from the http offering because the /etc/init.d/modloop script is
looking after /dev/nfs but the right path to look after is /dev/alpine.
This means no modules available…
This patch fix this issue
localhost:~# diff /etc/init.d/modloop modloop.new
--- /etc/init.d/modloop
+++ modloop.new
@@ -32,7 +32,7 @@
local search_dev="$1" fstab="$2"
local dev mnt fs mntopts chk
case "$search_dev" in
- UUID=*|LABEL=*|/dev/*);;
+ UUID=*|LABEL=*|/dev/*|nfs);;
*) search_dev=/dev/$search_dev;;
esac
local search_real_dev=$(resolve_dev $search_dev)
@@ -49,6 +49,10 @@
fi
done
done
+ if [ "$fs" = "$search_dev" ]; then
+ echo "$mnt"
+ return
+ fi
done < $fstab 2>/dev/null
}
For the time being, a quick hack is to add the modified
/etc/init.d/modloop script in some apkovl to be served as default one
trough http.
### shutdown
At shutdown time (poweroff or reboot), the system just hangs (but not
always) because it is trying to unmount the nfs share (from
/etc/init.d/modloop script) but the network is already down.
1750 root 0:00 /sbin/rc shutdown
2131 root 0:00 {mdev} /sbin/runscript /etc/init.d/mdev --lockfd 20 stop
2132 root 0:00 {modloop} /sbin/runscript /etc/init.d/modloop --lockfd 3 stop
2133 root 0:00 {runscript.sh} /bin/sh /lib/rc/sh/runscript.sh /etc/init.d/modloop stop
2161 root 0:00 mountinfo --quiet /media/alpine
The fix is to manually kill the hanging mountinfo process when hanging
or to manually issue “/etc/init.d/modloop stop” before issuing the
poweroff (or reboot). Then the shutdown sequence completes properly.
*(from redmine: issue id 4015, created on 2015-03-22, closed on 2015-05-14)*
* Changesets:
* Revision d211f6a58f8a130b0ab7aefbf0ae9317c480d200 by Natanael Copa on 2015-04-23T07:32:27Z:
```
openrc: modloop: fix finding nfs in /proc/mounts
Also fix finding UUID=... in fstab while at it
ref #4015
```
* Revision 858ecc1fec192dd11b25d9e3220cd3f287807a85 by Natanael Copa on 2015-04-23T08:34:55Z:
```
openrc: modloop: fix finding nfs in /proc/mounts
Also fix finding UUID=... in fstab while at it
fixes #4015
(cherry picked from commit d211f6a58f8a130b0ab7aefbf0ae9317c480d200)
```3.1.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4424no x86_64 uefi support enable image2019-07-23T13:50:46Zalgitbotno x86_64 uefi support enable imagehi
the subject tell all
if one of you have a image or howto for boot on uefi x86\_64 usb key
it
will be fine
edge is welcome
thanks
*(from redmine: issue id 4424, created on 2015-07-02, closed on 2016-06-24)*hi
the subject tell all
if one of you have a image or howto for boot on uefi x86\_64 usb key
it
will be fine
edge is welcome
thanks
*(from redmine: issue id 4424, created on 2015-07-02, closed on 2016-06-24)*3.4.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/4510eudev from edge breaks diskless mode2019-07-15T14:23:01ZAugust Kleineudev from edge breaks diskless modeSteps to reproduce:
1. Upgrade to edge in /etc/apk/repositories
2. apk del udev
3. apk add eudev
4. Run setup-udev. It says:
>“Udev requires /dev to be a mounted devtmpfs.
>Please reconfigure your system.
>ERROR: u...Steps to reproduce:
1. Upgrade to edge in /etc/apk/repositories
2. apk del udev
3. apk add eudev
4. Run setup-udev. It says:
>“Udev requires /dev to be a mounted devtmpfs.
>Please reconfigure your system.
>ERROR: udev failed to start”
If you do *“mount -n -t devtmpfs dev /dev”* udev is able to start but
when reboot
it fails again (I am previously running *“lbu ci”* , of course).
Also the trick: *“ln -s /dev/null
/etc/udev/rules.d/80-net-name-slot.rules”* does not work
on diskless mode (it works in a traditional hard-disk install) because
it does not survive
across reboots. (again using *“lbu ci”*)
*(from redmine: issue id 4510, created on 2015-08-04)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4617LXC container with Edge (3.2.3+) networking fails to start2019-07-23T13:48:22ZDavid FavorLXC container with Edge (3.2.3+) networking fails to start1) Create container + fix it up so it will actually run
lxc-create -t alpine-latest -n dev-alpine -- --release edge
printf "\n# allow container to start\nlxc.aa_allow_incomplete = 1" >> /var/lib/lxc/dev-alpine/config
printf "...1) Create container + fix it up so it will actually run
lxc-create -t alpine-latest -n dev-alpine -- --release edge
printf "\n# allow container to start\nlxc.aa_allow_incomplete = 1" >> /var/lib/lxc/dev-alpine/config
printf "nameserver 127.0.0.1\nnameserver 8.8.8.8\nnameserver 8.8.4.4\n" > /var/lib/lxc/dev-alpine/rootfs/etc/resolv.conf
chroot /var/lib/lxc/dev-alpine/rootfs passwd
2) lxc-start -n dev-alpine -F
OpenRC 0.17.c3aa146 is starting up Linux 3.19.8-031908-generic (x86_64) [LXC]
* /proc is already mounted
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ... [ ok ]
* Migrating /var/lock to /run/lock ... [ ok ]
* Migrating /var/run to /run ... [ ok ]
* Creating user login records ... [ ok ]
* Wiping /tmp directory ... [ ok ]
* Starting busybox syslog ... [ ok ]
Welcome to Alpine Linux 3.2
Kernel 3.19.8-031908-generic on an x86_64 (/dev/console)
dev-alpine login:
3) No networking appears to start by default. Test networking to make sure it never started.
lxc-attach -n dev-alpine ping google.com
ping: bad address 'google.com'
4) Try to start networking.
lxc-attach -n dev-alpine /etc/init.d/networking start
* Starting networking ...
* lo ... [ !! ]
* eth0 ... [ !! ]
* ERROR: networking failed to start
5) Contents of interfaces...
cat /var/lib/lxc/dev-alpine/rootfs/etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
6) Processes running, which include no dhcp related daemon...
lxc-attach -n dev-alpine ps auxww
PID USER TIME COMMAND
1 root 0:00 init
172 root 0:00 /sbin/syslogd
178 root 0:00 /sbin/getty 38400 console
179 root 0:00 /sbin/getty 38400 tty1
180 root 0:00 /sbin/getty 38400 tty2
181 root 0:00 /sbin/getty 38400 tty3
182 root 0:00 /sbin/getty 38400 tty4
197 root 0:00 ps auxww
I'm unsure if the fix for this bug should be rolled into the LXC Alpine template or placed into
http://wiki.alpinelinux.org/wiki/Configure_Networking in an LXC section.
Someone let me know the correct way to...
1) Get networking to start inside an LXC container, including
any changes to /etc/network/interfaces that may be required.
2) Acquire IP inside guest container from host, which is usually done
via dhclient, which doesn't exist in the Alpine LXC base install.
Thanks.
*(from redmine: issue id 4617, created on 2015-09-06, closed on 2015-10-27)*3.2.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4644/dev mounted twice. By initramfs-init and busybox-initscripts/mdev-mount.initd2019-07-23T13:47:57ZSerge Fedotov/dev mounted twice. By initramfs-init and busybox-initscripts/mdev-mount.initdI investigated that this commit
http://git.alpinelinux.org/cgit/mkinitfs/commit/?id=ac397ebafd39a277ca94cd37b70ad15d1c1e3d46
breaks /etc/init.d/mdev-mount script:
---cut---
mount_dev_directory()
{
if [ "$(mountinfo...I investigated that this commit
http://git.alpinelinux.org/cgit/mkinitfs/commit/?id=ac397ebafd39a277ca94cd37b70ad15d1c1e3d46
breaks /etc/init.d/mdev-mount script:
---cut---
mount_dev_directory()
{
if [ "$(mountinfo -t /dev)" = "mdev" ]; then
# already mounted
if fstabinfo --quiet /dev; then
mount -o remount -n /dev
fi
return 0
fi
---cut---
But $(mountinfo -t /dev) return devtmpfs instead. As a result, /dev/
mounted twice, and I cannot connect to pty over ssh:
PTY allocation request failed on channel 0
Sorry for my “english”.
*(from redmine: issue id 4644, created on 2015-09-17, closed on 2017-04-07)*
* Changesets:
* Revision b47c3c9b5ba110bc042315f58155b3d309f74de7 by Natanael Copa on 2015-09-17T12:10:40Z:
```
main/busybox-initscripts: make mdev-mount work with devtmpfs
newer initramfs mounts /dev as devtmpfs.
fixes #4644
```Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4809mkinitfs doesn't add dirname/readlink for mdev helpers2019-07-23T13:45:21ZIsaac Dunhammkinitfs doesn't add dirname/readlink for mdev helpers(Running Alpine Linux edge, roughly 3.3)
dirname and readlink are used in some of the mdev helpers, but mkinitfs
does not add the commands to the initramfs by default.
This results in a rather messy boot when using mdev, with at leas...(Running Alpine Linux edge, roughly 3.3)
dirname and readlink are used in some of the mdev helpers, but mkinitfs
does not add the commands to the initramfs by default.
This results in a rather messy boot when using mdev, with at least a
pageful of ‘command not found’ messages here.
To confirm without rebooting, it’s possible to use this command:
for IRF in /boot/initramfs\*; do echo “$IRF:” && zcat <“$IRF” | grep
dirname ; done
If ‘dirname’ shows up in the path, mkinitfs does not have the bug.
I think the simple solution is to add these commands to
/etc/mkinitfs/features.d/base.files.
Thanks.
*(from redmine: issue id 4809, created on 2015-10-30, closed on 2017-04-07)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/4975Packages from apkcache are not installed2019-07-23T13:42:41ZDennis PrzytarskiPackages from apkcache are not installedupgraded from v3.2 to v3.3 with setup-bootable -u
1) Boot alpine v3.3 from USB
2) Setup alpine with lbu and apkcache
3) Install zsh or any package which needs to use the apkcache
4) Commit (lbu) the changes
5) Check,...upgraded from v3.2 to v3.3 with setup-bootable -u
1) Boot alpine v3.3 from USB
2) Setup alpine with lbu and apkcache
3) Install zsh or any package which needs to use the apkcache
4) Commit (lbu) the changes
5) Check, if the apkcache directory (usually /media/usb/cache) exists and contains the apks
5) Reboot
6) Any package in apkcache is not installed (but it is mentioned in world and available to install from the apkcache directory)
7) 'apk fix' will install the missing apks
*(from redmine: issue id 4975, created on 2015-12-22, closed on 2016-01-06)*
* Changesets:
* Revision 0ed15a08937ba71c1ef866ab73741940b36f8abd by Natanael Copa on 2016-01-06T14:45:55Z:
```
main/mkinitfs: upgrade to 3.0.2
fixes #4975
```
* Revision ec94135bbb1e62bf7e884e2f3de58048f560fbcc by Natanael Copa on 2016-01-06T14:48:44Z:
```
main/mkinitfs: upgrade to 3.0.2
fixes #4975
(cherry picked from commit 0ed15a08937ba71c1ef866ab73741940b36f8abd)
```
* Uploads:
* ![1_given-commands-executed](/uploads/23f8f23805544aac46ebb2c39224c7ac/1_given-commands-executed.png)
* ![2_using-uuid-in-fstab](/uploads/7062f2951da265137ed042aac648e79a/2_using-uuid-in-fstab.png)3.3.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5028Dont launch emergency shell if http repo is specified2019-07-23T13:41:55ZSerge FedotovDont launch emergency shell if http repo is specifiedPlease include commits
b4ebbafc0a53288788e6e11ede0b185d71269235..73fd80c87696f72d769aed377cc1bb89c2d540cf
to 3.3.2 release
*(from redmine: issue id 5028, created on 2016-01-18, closed on 2016-03-18)*
* Changesets:
* Revision ca9755b...Please include commits
b4ebbafc0a53288788e6e11ede0b185d71269235..73fd80c87696f72d769aed377cc1bb89c2d540cf
to 3.3.2 release
*(from redmine: issue id 5028, created on 2016-01-18, closed on 2016-03-18)*
* Changesets:
* Revision ca9755b3098c2ab129f2891e1d3a319a84771c2b by Natanael Copa on 2016-01-20T16:13:12Z:
```
main/mkinitfs: upgrade to 3.0.3
fixes #5028
```3.3.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5031Dmcrypt config-file example with inaccuracies2019-07-15T02:01:08ZAlexander BelkovDmcrypt config-file example with inaccuraciesLoopack file example section in /etc/conf.d/dmcrypt (package cryptsetup)
has errors:
\- doesn’t start with ‘target’ option (has ‘mount’ instead)
- doesn’t include empty line in the end which prevents the last option
from being interpr...Loopack file example section in /etc/conf.d/dmcrypt (package cryptsetup)
has errors:
\- doesn’t start with ‘target’ option (has ‘mount’ instead)
- doesn’t include empty line in the end which prevents the last option
from being interpreted
*(from redmine: issue id 5031, created on 2016-01-19)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5050Unable to finish boot with serial console2019-07-23T13:41:35ZalgitbotUnable to finish boot with serial consoleWhen trying to get working serial console the “init” always hung after
installing apks.
Appended “console=ttyS0,115200” as a kernel parameter to syslinux.cfg.
Enabled debug\_init to find out what’s wrong with the boot script and
found ...When trying to get working serial console the “init” always hung after
installing apks.
Appended “console=ttyS0,115200” as a kernel parameter to syslinux.cfg.
Enabled debug\_init to find out what’s wrong with the boot script and
found a bug in the “init”.
There is a procedure “setup\_inittab\_console()” that is intended to
configure Alpine for serial console.
A last thing it try to do is to add “ttyS0” (in my case) to
/etc/securetty, but it failed due to a bug in grep statement.
The original line was like this:
line 145: if \[ -e “$sysroot”/etc/securetty \] && ! grep -q -w “$tty”;
then
I’ve changed the line to:
line 145: if \[ -e “$sysroot”/etc/securetty \] && ! grep -q -w “$tty”
“$sysroot”/etc/securetty; then
compressed into new initramfs and since that time it works like a charm.
*(from redmine: issue id 5050, created on 2016-01-26, closed on 2016-06-06)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5146Firmware does not mount on tmpfs2019-07-23T13:40:27ZCarlo LandmeterFirmware does not mount on tmpfsWhen booting latest 3.3.1, the firmware directory does not get mounted
on /lib/firmware, it does exist in /.modloop/firmware
*(from redmine: issue id 5146, created on 2016-02-22, closed on 2017-05-19)*When booting latest 3.3.1, the firmware directory does not get mounted
on /lib/firmware, it does exist in /.modloop/firmware
*(from redmine: issue id 5146, created on 2016-02-22, closed on 2017-05-19)*3.3.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5192mkinitfs: nlplug-findfs takes too much time (it needs depth limit)2019-07-23T13:39:40Zdonobanmkinitfs: nlplug-findfs takes too much time (it needs depth limit)Hi,
Since I tried version 3.3.1 I noticed that it spends a lot of time for
booting from an USB stick. After I investigated it and with the help
of Natanael, the problem is probably due it looks for repository and
apkovl on the who...Hi,
Since I tried version 3.3.1 I noticed that it spends a lot of time for
booting from an USB stick. After I investigated it and with the help
of Natanael, the problem is probably due it looks for repository and
apkovl on the whole disk.
As a fix I tried to limit the recursion depth and I did a patch but I
can’t test it because I don’t know how to add my custom mkinitfs
package to the USB stick or make a new iso. Could someone help me with
this?
Regards.
*(from redmine: issue id 5192, created on 2016-02-26, closed on 2016-03-18)*
* Changesets:
* Revision a647b7e2dac8b3510c947ee5d1b2c59fa7207765 by Natanael Copa on 2016-03-14T09:16:11Z:
```
main/mkinitfs: upgrade to 3.0.4
(cherry picked from commit 8dcf8465f7a1718125caeeb46c247147fcfea2b8)
fixes #5192
```
* Uploads:
* [max_recursion_depth.patch](/uploads/f0169f9e02e1e71165a642b93acbce83/max_recursion_depth.patch) None3.3.2https://gitlab.alpinelinux.org/alpine/aports/-/issues/5296Failure to boot on Raspberry Pi 32019-07-23T13:38:15ZAndrew HainesFailure to boot on Raspberry Pi 3I’m trying to install Alpine 3.3.2 on my Raspberry Pi 3 (which I
understand from \#5197 is now supported).
I’ve created a bootable SD from my Mac and extracted the rpi tarball
onto it. However, when I start up my Pi I get a couple of fl...I’m trying to install Alpine 3.3.2 on my Raspberry Pi 3 (which I
understand from \#5197 is now supported).
I’ve created a bootable SD from my Mac and extracted the rpi tarball
onto it. However, when I start up my Pi I get a couple of flashes from
the disk access indicator LED and then nothing; all I see is a black
screen.
Am I doing something wrong? Anything I can try to get this working? Let
me know if I can provide any further info needed to troubleshoot.
I did the following to create the SD (although I get the same result
when I use a single partition, following the [instructions on the
wiki](http://wiki.alpinelinux.org/wiki/Create_a_bootable_SDHC_from_a_Mac))
# Format the disk as FAT32 with MBR
$ sudo diskutil eraseDisk FAT32 ALPINE MBRFormat /dev/disk2
# Partition into 1GB for OS and ~15GB for /var
$ sudo diskutil splitPartition /dev/disk2s1 FAT32 ALPINE 1GB FAT32 VAR R
# Use gnu tar to extract tarball (bsd tar complains that "./: Can't create '.'")
$ gtar xf alpine-rpi-3.3.2-armhf.rpi.tar.gz -C /Volumes/ALPINE
# Mark the first partition as active
$ diskutil unmountDisk /dev/disk2
$ sudo fdisk -e /dev/disk2
fdisk: 1> flag 1
Partition 1 marked active.
fdisk:*1> write
Writing MBR at offset 0.
fdisk: 1> print
Disk: /dev/disk2 geometry: 1936/255/63 [31116288 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
*1: 0B 1023 254 63 - 1023 254 63 [ 8192 - 1953120] Win95 FAT-32
2: 0B 1023 254 63 - 1023 254 63 [ 1961312 - 29154976] Win95 FAT-32
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
*(from redmine: issue id 5296, created on 2016-03-19, closed on 2016-03-24)*3.3.3Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5346Version 3.3.3 does not boot on Raspberry Pi Zero2019-07-23T13:37:40ZGerald PapeVersion 3.3.3 does not boot on Raspberry Pi ZeroHi everyone,
I just tried the latest Alpine Linux release (3.3.3) on two Raspberry Pi
Zeros. But the Pi only blinks and outputs nothing on hdmi. The card
works on a Raspberry Pi 2 and other distros work on the Zeros.
I also tried the ...Hi everyone,
I just tried the latest Alpine Linux release (3.3.3) on two Raspberry Pi
Zeros. But the Pi only blinks and outputs nothing on hdmi. The card
works on a Raspberry Pi 2 and other distros work on the Zeros.
I also tried the suggestions from
https://bugs.alpinelinux.org/issues/4989 (Copying certain files from the
raspbian card), but without success.
Cheers,
Gerald
*(from redmine: issue id 5346, created on 2016-03-29, closed on 2017-04-07)*Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5362Booting from a fully encrypted disk requires four incorrect passphrase attempts2019-07-23T11:12:38ZKlemens NanniBooting from a fully encrypted disk requires four incorrect passphrase attemptsWhen prompting for a passphrase to unlock / at boot, actually valid and
correctly entered passphrases are reported as invalid but the crypto
container still gets unlocked eventually.
After entering a valid passphrase when being prompted...When prompting for a passphrase to unlock / at boot, actually valid and
correctly entered passphrases are reported as invalid but the crypto
container still gets unlocked eventually.
After entering a valid passphrase when being prompted first, I’m getting
prompted other four times before booting into the unlocked root
partition actually continues. No matter what string was entered, all
attempts are reported as invalid.
My usual procedure to boot therefore consists of entering a valid
passphrase and hitting <Enter> five times.
I’m using latest Alpine v3.3 on a ThinkPad X230 running coreboot + GRUB2
payload, thus no ext/syslinux or any other bootloader on my disk is
used. GRUB2 unlocks my LUKS container and loads */boot/grub.cfg* which
then boots Alpine Linux.
Kernel parameters and initramfs features:
$ cat /proc/cmdline
BOOT_IMAGE=/__alpine_root__/boot/vmlinuz cryptroot=/dev/sda cryptdm=main root=/dev/mapper/main rootflags=compress=lzo,noatime,subvolid=319 modules=btrfs quiet
$ /etc/mkinitfs.conf
features="keymap cryptsetup kms ata base scsi btrfs"
*(from redmine: issue id 5362, created on 2016-04-03, closed on 2019-05-03)*Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5719setup-disk tries to restart syslog even if it is not running2019-07-23T13:32:38ZIan Campbellsetup-disk tries to restart syslog even if it is not runningIf setup disk is called from e.g. an initscript before syslog has been
started then it logs:
ERROR: cannot start syslog as hostname would not start
Which is rather misleading as syslog will be started later in the
bootsequence....If setup disk is called from e.g. an initscript before syslog has been
started then it logs:
ERROR: cannot start syslog as hostname would not start
Which is rather misleading as syslog will be started later in the
bootsequence.
Using `condrestart` in place of `restart` avoids this message:
--- a/alpine/sbin/setup-disk
+++ b/alpine/sbin/setup-disk
@@ -661,7 +661,7 @@ setup_var() {
mv /.var/* /var/
rmdir /.var
- /etc/init.d/syslog --quiet restart
+ service --quiet syslog condrestart
setup_mdadm_conf
}
While at it switch to `service` which AIUI is recommended over calling
the initscript directly (although with `openrc-run` I don’t know how
much difference it really makes)
*(from redmine: issue id 5719, created on 2016-06-13, closed on 2016-06-24)*
* Changesets:
* Revision cf023ac1ffecfdcc1997ee7b8e57cacdde62870e by Natanael Copa on 2016-06-13T13:34:02Z:
```
setup-disk: only restart syslog if its already running
ref #5719
```
* Revision cffed188deeaab6395053d91ca464ce1495b9569 by Natanael Copa on 2016-06-13T13:42:00Z:
```
main/alpine-conf: setup-disk: only restart syslog if its running
ref #5719
```
* Revision 53156fad07538de10656e573b58f450d8612c252 by Natanael Copa on 2016-06-17T16:39:26Z:
```
main/alpine-conf: upgrade to 3.4.1
fixes #5719
```3.4.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5758please provide x86/x86_64 image with uboot2019-12-19T15:10:24ZRay Davisplease provide x86/x86_64 image with ubootHello Guys/Girls
Requesting to enable non-iso releases for x86 and 64-bit alpine-linux.
This will enable more friendly usage for embedded and console based x86
boards like edison.
Thanking you
Oneinsect
*(from redmine: issue id 575...Hello Guys/Girls
Requesting to enable non-iso releases for x86 and 64-bit alpine-linux.
This will enable more friendly usage for embedded and console based x86
boards like edison.
Thanking you
Oneinsect
*(from redmine: issue id 5758, created on 2016-06-20)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5759The default alpine initramfs is not picking up the bootargs and changing the ...2019-07-23T13:32:11ZRay DavisThe default alpine initramfs is not picking up the bootargs and changing the etc/inittab and etc/securetty accordingly for ttyDears
Noticed the following while trying to check alpine on intel edison with
u-boot. No syslinux or bios.
ARGS
bootargs rootwait root=/dev/mmcblk0p5 rw rootfstype=ext4 console=ttyMFD2
earlyprintk=ttyMFD2 level=8 init=/sbin/init
EXP...Dears
Noticed the following while trying to check alpine on intel edison with
u-boot. No syslinux or bios.
ARGS
bootargs rootwait root=/dev/mmcblk0p5 rw rootfstype=ext4 console=ttyMFD2
earlyprintk=ttyMFD2 level=8 init=/sbin/init
EXPECTED
ttyMFD2 needs to be put in /etc/inittab and in /etc/securetty
Example
ttyMFD2::respawn:/sbin/getty -L ttyMFD2 115200 vt100
*(from redmine: issue id 5759, created on 2016-06-20, closed on 2016-06-24)*
* Changesets:
* Revision 1b0a3e1c91915514f56293cb07768be638846185 by Natanael Copa on 2016-06-20T14:46:09Z:
```
main/mkinitfs: fix ttyMFD/ttyUSB serial consoles and use 115200 speed
ref #5759
```
* Revision 53d0da973e94c507e91ccff0f5222ef467a2c931 by Natanael Copa on 2016-06-24T10:32:25Z:
```
main/mkinitfs: fix ttyMFD/ttyUSB serial consoles and use 115200 speed
fixes #5759
(cherry picked from commit 1b0a3e1c91915514f56293cb07768be638846185)
```3.4.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5868nlplug-findfs and initramfs-init don't support cryptsetup --header2019-07-23T10:50:28Z7heo .tknlplug-findfs and initramfs-init don't support cryptsetup --headerIt is possible to create a LUKS header on another device, with the
procedure described
[here](https://skrilnetz.net/bullet-proof-data-encryption-with-luks-and-a-detached-header/),
but it is impossible to boot it with the current Alpine b...It is possible to create a LUKS header on another device, with the
procedure described
[here](https://skrilnetz.net/bullet-proof-data-encryption-with-luks-and-a-detached-header/),
but it is impossible to boot it with the current Alpine boot scripts.
*(from redmine: issue id 5868, created on 2016-07-04)*
* Uploads:
* [patch](/uploads/8bbef67ed391c011a2bb9acfe97bb99c/patch)
* [patch.diff](/uploads/71a740dd63d1b8c9a70dabe780a5aeed/patch.diff) current patch3.3.47heo .tk7heo .tk2016-07-05https://gitlab.alpinelinux.org/alpine/aports/-/issues/5961nlplug-findfs leaks file decriptors2020-01-18T21:49:00Z7heo .tknlplug-findfs leaks file decriptorsWhen I boot, right after entering my encryption password, the screen
displays the following (with varying numbers at each boot, and many
times):
File descriptor 6 (/dev/random) leaked on lvm invocation. Parent PID
682: nlplug-findfs
F...When I boot, right after entering my encryption password, the screen
displays the following (with varying numbers at each boot, and many
times):
File descriptor 6 (/dev/random) leaked on lvm invocation. Parent PID
682: nlplug-findfs
File descriptor 8 (/dev/urandom) leaked on lvm invocation. Parent PID
682: nlplug-findfs
File descriptor 6 (/dev/random) leaked on lvm invocation. Parent PID
682: nlplug-findfs
File descriptor 8 (/dev/urandom) leaked on lvm invocation. Parent PID
682: nlplug-findfs
As suggested by skarnet, it probably is related to close-on-exec being
unset for the file descriptors for <code>/dev/random</code> and
<code>/dev/urandom\`</code>.
*(from redmine: issue id 5961, created on 2016-07-25)*7heo .tk7heo .tkhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6217nlplug-findfs segfaults on bogus extraneous cryptsetup execution2019-07-23T12:07:49Z7heo .tknlplug-findfs segfaults on bogus extraneous cryptsetup executionWhen opening a <code>cryptsetup</code> device with
<code>nlplug-findfs</code>, the device is first unlocked correctly, and
then <code>cryptsetup</code> is called a second time, and continues
asking for the passphrase until the amount of ...When opening a <code>cryptsetup</code> device with
<code>nlplug-findfs</code>, the device is first unlocked correctly, and
then <code>cryptsetup</code> is called a second time, and continues
asking for the passphrase until the amount of tries is exhausted. Then
the application segfaults, while the <code>cryptsetup</code> device is
open correctly (from the first execution).
*(from redmine: issue id 6217, created on 2016-09-26, closed on 2017-04-07)*
* Changesets:
* Revision 386aab2ad0e7becf3db1de3fc70d124cd85f5d47 by Timo Teräs on 2016-11-24T12:07:52Z:
```
main/mkinitfs: upgrade to 3.0.6
fixes #6217
fixes #6469
fixes #6473
```7heo .tk7heo .tkhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6471/init doesn't respect all options in /etc/fstab2020-01-18T22:05:33ZTavi Vi/init doesn't respect all options in /etc/fstabI haven’t looked to see if any other options are affected, but fmask and
dmask for fat volumes aren’t applied properly. I think it has to do with
lines 592-598:
<code>
1. respect mount options in fstab for ALPINE\_MNT (e.g if user wan...I haven’t looked to see if any other options are affected, but fmask and
dmask for fat volumes aren’t applied properly. I think it has to do with
lines 592-598:
<code>
1. respect mount options in fstab for ALPINE\_MNT (e.g if user wants
rw)
if \[ -f “$sysroot”/etc/fstab \]; then
opts=$(awk “\\$2 == \\”$ALPINE\_MNT\\" {print \\$4}"
$sysroot/etc/fstab)
if \[ -n “$opts” \]; then
mount -o remount,$opts “$ALPINE\_MNT”
fi
fi
</code>
When `mount` remounts and is given different options for fmask/dmask,
they dont take effect. I’m observing this happening on an rpi3 but I
would imagine it’s universal.
*(from redmine: issue id 6471, created on 2016-11-20)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6607virtualized AlpineLinux during booting process freeze on step - Loading modules2019-07-23T10:50:02ZMichal Mičkovirtualized AlpineLinux during booting process freeze on step - Loading modulesI prepared VM (QEMU-KVM | VirtualBox) based on AlpineLinux 3.5.0
(alpine-standard-3.5.0-x86\_64.iso).
I install required modules:
1. **VirtualBox** (install: virtualbox-additions-grsec,
virtualbox-guest-additions, virtualbox-guest...I prepared VM (QEMU-KVM | VirtualBox) based on AlpineLinux 3.5.0
(alpine-standard-3.5.0-x86\_64.iso).
I install required modules:
1. **VirtualBox** (install: virtualbox-additions-grsec,
virtualbox-guest-additions, virtualbox-guest-modules-grsec)
into /etc/modules added modules (vboxpci, vboxdrv, vboxsf)
2. **KVM**
into /etc/modules added modules (9p, 9pnet, 9pnet\_virtio)
When I start installed VM with **GUI window**, booting process **waiting
a few minutes** (3-6min) on step **Loading modules** and then system
start correctly.
When I start installed VM in **headless mode**, booting process
**FREEZE** probably on same step Loading modules. (*I waited only 15
minutes for it, I did not have patience.*)
I try branch **v3.5** and **edge** with same result.
*(from redmine: issue id 6607, created on 2016-12-30)*3.5.4Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6689Can't unpack encrypted LBU with libressl2019-07-23T12:01:26ZMike RothfussCan't unpack encrypted LBU with libresslWith a fresh install of v3.5.0, libressl is shipped instead of openssl.
The openssl apk is still required by the initramfs-init script to unpack
an encrypted LBU.
http://git.alpinelinux.org/cgit/mkinitfs/tree/initramfs-init.in
line 58...With a fresh install of v3.5.0, libressl is shipped instead of openssl.
The openssl apk is still required by the initramfs-init script to unpack
an encrypted LBU.
http://git.alpinelinux.org/cgit/mkinitfs/tree/initramfs-init.in
line 58: the openssl APK reference just needs to be changed to libressl
*(from redmine: issue id 6689, created on 2017-01-16, closed on 2017-01-25)*
* Changesets:
* Revision a13f26f5c5892f3ec379ebb4f478bd0e2101c711 by Natanael Copa on 2017-01-25T08:59:47Z:
```
main/mkinitfs: fix decrypt of apkovl
ref #6689
```
* Revision 478c6de32ceeee40e8b67480385526c93113e204 by Natanael Copa on 2017-01-25T09:09:04Z:
```
main/mkinitfs: fix decrypt of apkovl
fixes #6689
```3.5.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6760localmount fails if there are nfs mounts in /etc/fstab2020-01-18T22:34:23ZNatanael Copalocalmount fails if there are nfs mounts in /etc/fstabDuring boot localmount tries to mount nfs mounts before network is up
and before rpcbind is running. This will fail obviously. See screenshot.
When /etc/init.d/nfsmount runs later it will mount the filesystem
properly.
See attached scre...During boot localmount tries to mount nfs mounts before network is up
and before rpcbind is running. This will fail obviously. See screenshot.
When /etc/init.d/nfsmount runs later it will mount the filesystem
properly.
See attached screenshot.
*(from redmine: issue id 6760, created on 2017-01-27)*
* Uploads:
* ![Screenshot_alpine3.5-b_2017-01-27_10_39_32](/uploads/b906b6f3b315cd611675c8379f8722f1/Screenshot_alpine3.5-b_2017-01-27_10_39_32.png)3.9.5Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/6903Failed to mount cryptsetup + btrfs stripe (raid 0) on boot2019-07-23T11:19:56ZIvan ThamFailed to mount cryptsetup + btrfs stripe (raid 0) on bootMy setup is one luks encrypted disk on top of two btrfs raid disk, I
need to manually mount my disk on boot with the following but I just
can’t mount the ${KOPT\_root} that I have specified during boot or else
it will show “Mount (device...My setup is one luks encrypted disk on top of two btrfs raid disk, I
need to manually mount my disk on boot with the following but I just
can’t mount the ${KOPT\_root} that I have specified during boot or else
it will show “Mount (device…): Invalid argument”:
mount -t btrfs -o compress=lzo,subvol=alpine /dev/sda2 /sysroot
It can be be reproduced with arch’s mkinitcpio (without udev) as well.
Just note that I can mount the disk anyway I want just other than
${KOPT\_root}.
Some useful information:
https://transfer.sh/fVsjJ/blkid
https://transfer.sh/YpQ63/lsblk
*(from redmine: issue id 6903, created on 2017-02-21, closed on 2018-09-11)*3.7.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7024"can't open /dev/ttyS0" immediately after boot on Raspberry Pi since 3.5.22020-01-18T22:42:13ZSander de Leeuw"can't open /dev/ttyS0" immediately after boot on Raspberry Pi since 3.5.2I just installed Alpine Linux 3.5.2 on both:
1) Raspberry Pi 3
2) Raspberry Pi Zero W
On both devices, immediately after booting from the SDHC card, I get the
following error:
“can’t open /dev/ttyS0: No such file or directory”
Th...I just installed Alpine Linux 3.5.2 on both:
1) Raspberry Pi 3
2) Raspberry Pi Zero W
On both devices, immediately after booting from the SDHC card, I get the
following error:
“can’t open /dev/ttyS0: No such file or directory”
This error repeats constantly.
See the attached screenshot.
Note that I did not even run setup-alpine yet.
The issue occurs straight after booting from SDHC with the unzipped
tarball.
Alpine Linux 3.5.1 works without any issues.
*(from redmine: issue id 7024, created on 2017-03-16)*
* Uploads:
* ![image](/uploads/903c9b33ef67d7b5cf86cde5a7275ac7/image.jpg)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7954boot parameter "blacklist" not working properly2019-07-23T11:42:41ZKurnia D Winboot parameter "blacklist" not working properlywe cannot blacklist more than 2 modules, because of
https://git.alpinelinux.org/cgit/mkinitfs/tree/initramfs-init.in\#n327,
only first ‘,’ got replaced by ’ ’
*(from redmine: issue id 7954, created on 2017-10-03, closed on 2018-08-01)*we cannot blacklist more than 2 modules, because of
https://git.alpinelinux.org/cgit/mkinitfs/tree/initramfs-init.in\#n327,
only first ‘,’ got replaced by ’ ’
*(from redmine: issue id 7954, created on 2017-10-03, closed on 2018-08-01)*3.6.3Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7976keyfile support for encrypted partitions in mkinitfs2019-07-23T11:42:24Zalgitbotkeyfile support for encrypted partitions in mkinitfsadd linux kernel option cryptkey= and package /boot/key into initrd
*(from redmine: issue id 7976, created on 2017-10-05, closed on 2018-08-09)*
* Uploads:
* [mkinitfs-echoline.patch](/uploads/c05db9a0f358f39461c50b8c878857c1/mkinit...add linux kernel option cryptkey= and package /boot/key into initrd
*(from redmine: issue id 7976, created on 2017-10-05, closed on 2018-08-09)*
* Uploads:
* [mkinitfs-echoline.patch](/uploads/c05db9a0f358f39461c50b8c878857c1/mkinitfs-echoline.patch)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8090fsck on Rspberry Pi (possibly other systems too)2019-07-23T11:41:11ZHarald Beckerfsck on Rspberry Pi (possibly other systems too)Installing Alpine Linux on a Raspberry Pi SD Card revealed a bunch of
bugs belonging to fsck of OpenRC startup:
The Raspberry Pi Boot Partition is a DOS FAT32 Partition, so the
dosfstools package is required else the fsck crashes someti...Installing Alpine Linux on a Raspberry Pi SD Card revealed a bunch of
bugs belonging to fsck of OpenRC startup:
The Raspberry Pi Boot Partition is a DOS FAT32 Partition, so the
dosfstools package is required else the fsck crashes sometimes horribly
because of the missing fsck.vfat.
… but just installing the package dosfstools, got the Pi unable to boot
successfully. It took me some time to find the reason for this. The
OpenRC file system check uses the Busybox fsck, which call the fsck
helpers. For the FAT partitition this is called as:
from Busybox fsck =>fsck.vfat -p -C0 UUID=xxx…
fsck.vfat is symlinked to fsck.fat, so is the command dosfsck, but it
does not understand the -C0 option like the ext2/3/4 handlers. So the
fsck dumps the usage text on startup, and then the startup crashes due
to fsck exit code. Won’t let you get to a working logging prompt this
way.
… but removing -C0 option another problem is revealed. dosfsck doesn’t
understand the UUID=… or LABEL=… syntax, it needs the bare block device
name … but usually the partition is setup in /etc/fstab with the UUID
methode.
The easiest workaround is, to remove the symlink from /usr/sbin/dosfsck
to fsck.fat, rename fsck.fat to dosfsck, and create an fsck.fat shell
script wrapper:
cd /usr/sbin
rm dosfsck
mv fsck.fat dosfsck
echo “\#!/bin/sh” >fsck.fat
chmod 755 fsck.fat
This at least let the Raspberry Pi successfully boot with unmodified
OpenRC scripts. Usually a quick helper in this situation, until we get
some other changes on this topic.
… and this also effect other systems (tested on x86\_64) which include a
FAT partition on there disk setup, so it is not a specific Raspberry Pi
problem.
*(from redmine: issue id 8090, created on 2017-10-31, closed on 2017-11-29)*3.7.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8210Old kernel (.59) still bootet though .65 installed2019-07-23T11:39:41ZSteffen NurpmesoOld kernel (.59) still bootet though .65 installedYep, the system boots .59 which is no longer installed.
As a BSD person, i am pretty lost at the moment, any hint appreciated.
*(from redmine: issue id 8210, created on 2017-11-27, closed on 2017-11-29)*Yep, the system boots .59 which is no longer installed.
As a BSD person, i am pretty lost at the moment, any hint appreciated.
*(from redmine: issue id 8210, created on 2017-11-27, closed on 2017-11-29)*3.7.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8476Initramfs fails to boot from SCSI in VM with lsilogic controller and >3 GB RAM2021-11-18T12:14:34ZDisassembler .Initramfs fails to boot from SCSI in VM with lsilogic controller and >3 GB RAMHi,
I’m trying to get Alpine 3.7 (virthardened) to run in VM on VMWare
Workstation 14.1. The Alpine VM is set to boot from LVM but whenever I
set more than 3 GB memory, initramfs on first boot after the
installation fails with
moun...Hi,
I’m trying to get Alpine 3.7 (virthardened) to run in VM on VMWare
Workstation 14.1. The Alpine VM is set to boot from LVM but whenever I
set more than 3 GB memory, initramfs on first boot after the
installation fails with
mount: mounting /dev/vg0/lv_root on /sysroot failed: No such file or directory
Mounting root failed.
initramfs emergency recovery shell launched. Type 'exit' to continue boot
sh: can't access tty: job control turned off
When I activate and mount the volumes manually in initramfs shell, the
VM eventually starts.
lvm vgchange -ay
mount -t ext4 /dev/vg0/lv_root /sysroot
mount -t ext4 /dev/sda1 /sysroot/boot
exit
Whenever I set the RAM to 3 GB or less, the VM happily boots without any
problems or interruptions.
/etc/mkinitfs/mkinitfs.conf:
features="ata base ide scsi usb virtio ext4 lvm"
Relevant lines from /boot/extlinux.conf:
LINUX vmlinuz-virthardened
INITRD initramfs-virthardened
APPEND root=/dev/vg0/lv_root modules=sd-mod,usb-storage,ext4 pax_nouderef quiet rootfstype=ext4
Attached is the output from “nlplug-findfs -d -p /sbin/mdev
/dev/vg0/lv\_root >& nlplug-findfs.log”
*(from redmine: issue id 8476, created on 2018-02-06)*
* Uploads:
* [nlplug-findfs.log](/uploads/8a765cfca055e0442b44d755266bc551/nlplug-findfs.log)
* [nok.txt](/uploads/9a38d23e328e9ed2f4d5338a6228fa1d/nok.txt)
* [ok.txt](/uploads/640a1153fc01e0d6beeff4abc785d8ad/ok.txt)3.15.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8486please rip out all unneeded parts of busybox's fsck from initrd2021-01-30T00:36:59ZFlorian Heiglplease rip out all unneeded parts of busybox's fsck from initrdCurrently, there are multiple parts that look like we have a working
fsck in an initramfs provided by busybox.
As per kaniini the only supported fsck is the one from e2fsprogs.
We still got things like fsck.auto and some busybox-fsck ...Currently, there are multiple parts that look like we have a working
fsck in an initramfs provided by busybox.
As per kaniini the only supported fsck is the one from e2fsprogs.
We still got things like fsck.auto and some busybox-fsck symlinks that
also seem to be there even if they don’t work.
Would be great if this stuff could be completely removed.
*(from redmine: issue id 8486, created on 2018-02-13)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8599sysctl doesn't set net.ipv6.conf.all.forwarding2020-01-23T10:22:28Zalgitbotsysctl doesn't set net.ipv6.conf.all.forwardingI have a fresh installed Alpine 3.7 extended installation and wanted to
set a sysctl value \`net.ipv6.conf.all.forwarding\` to 1 upon boot.
What I did is added a line \`net.ipv6.conf.all.forwarding = 1\` to
/etc/sysctl.d/00-alpine.conf...I have a fresh installed Alpine 3.7 extended installation and wanted to
set a sysctl value \`net.ipv6.conf.all.forwarding\` to 1 upon boot.
What I did is added a line \`net.ipv6.conf.all.forwarding = 1\` to
/etc/sysctl.d/00-alpine.conf at the end of file with 3 newlines after
the line.
The values remains 0 after reboot, but all other parameters are being
set fine, such as custom net.ipv4.ip\_forward value.
I have tried what bernhardgruen suggested on IRC, creating
/etc/conf.d/sysctl with \`rc\_need=“net”\` line and following with
rc-update -u, which doesn’t provide any positive effect. I have tried
with rc\_need=“net.eth0”, rc\_need=“networking” but it didn’t help.
I have IPv6 address configured in /etc/network/interfaces and it comes
up at boot, but there seems to be some problem with sysctl settings for
IPv6 which i was not able to identify.
Is there way to set this parameter to 1 at boot without touching
anything else but sysctl and inventing additional boot scripts?
*(from redmine: issue id 8599, created on 2018-03-02)*3.7.4Natanael CopaNatanael Copa