2024-09-01 08:56:35 a 2024-09-01 10:41:53 a suspense 2024-09-01 14:46:41 I'm using setup-bootable to build a custom alpine live-usb. I've noticed that it places a copy of ldlinux.c32 and ldlinux.sys at the root of the disk, but these don't appear to be used by anything? as in, if I delete them it still boots fine. The official iso only has ldlinux.c32, and it's inside /boot/syslinux rather than the filesystem root. Anyone know why setup-bootable does this differently? 2024-09-01 14:48:33 oh, and it looks like setup-bootable also puts a second copy of ldlinux.c32 inside /boot/syslinux, to match the iso 2024-09-01 22:12:11 anyone try playing around with alpine+flatpak steam on the steam deck? curious if the controller works fine and if the refresh rate slider/gpu freq slider work out of the box or if the correct knobs can be exposed to make them work 2024-09-01 22:12:31 running nixos on mine currently but kinda missing alpine tbh 2024-09-02 01:14:49 How do i properly from inside a script pass a sting with spaces onto a script? i tried this one ./te.sh "$line4" 2024-09-02 01:16:12 i get a problem of filenames being cut at the first space counted from the right 2024-09-02 01:45:50 Let me see if i can paste all 7 lines in the script in case someone got a better idea to solve it all :) 2024-09-02 01:45:56 while IFS= read -r line; do 2024-09-02 01:45:56 ./te.sh "$line4" 2024-09-02 01:45:56 line4=$(echo "$line" | cut -b 45-) 2024-09-02 01:45:56 if [[ "$line" == *".mcr"* ]]; then 2024-09-02 01:45:56 cat "$line4" 2024-09-02 01:45:56 fi 2024-09-02 01:45:58 done < "$1" 2024-09-02 01:46:43 worked :) 2024-09-02 03:50:13 Babba: there's nothing wrong with the code you've provided; more likely whatever te.sh is doesn't handle parameters with spaces correctly 2024-09-02 09:29:11 how to set up loginctl? 2024-09-02 09:29:25 https://wiki.alpinelinux.org/wiki/Elogind 2024-09-02 09:29:34 i read this and loginctl wont detect my session 2024-09-02 09:30:10 summershine:~$ doas rc-service polkit status 2024-09-02 09:30:10 summershine:~$ doas rc-service elogind status 2024-09-02 09:30:10 * status: started 2024-09-02 09:30:10 * status: started 2024-09-02 12:18:51 Hello, 2024-09-02 12:18:51 I'm encountering issues while building Docker images with Alpine Linux. The build fails with the following error: 2024-09-02 12:18:54 "WARNING: updating and opening https://dl-cdn.alpinelinux.org/alpine/v3.19/main: temporary error (try again later)" 2024-09-02 12:18:57 This occurs across multiple Alpine versions. It seems the APK repositories might be temporarily down. Has anyone experienced this or have suggestions for resolving it? 2024-09-02 12:19:04 Thanks in advance! 2024-09-02 12:20:32 if you pop the URL (https://dl-cdn.alpinelinux.org/alpine/v3.19/main/) into your browser, you will probably see that the mirror is up 2024-09-02 12:20:57 that error message is a bit terse, but it probably points to a connectivity issue inside your build environment 2024-09-02 12:23:00 Thank you for the suggestion. I will check the network settings and connectivity within my Docker build environment to address this issue. 2024-09-02 12:26:49 Also, http seems to be the recommended proto, not https 2024-09-02 12:27:22 Could be part of what causes the issue you're having 2024-09-02 12:27:38 i use https myself and haven't had an issue. but if your clock is desync'ed enough, ssl cert verification could fail ya 2024-09-02 12:27:39 s/recommended/target/ 2024-09-02 12:27:56 peerl3ss, you aren't :) 2024-09-02 12:29:08 Just for an initial header exchange to tell your client to connect over http 2024-09-02 12:29:16 At least that's what I can see from here 2024-09-02 12:29:51 definitely uses ssl for me 2024-09-02 12:30:15 well, tls :) 2024-09-02 12:30:15 Can you try: curl -I https://dl-cdn.alpinelinux.org/alpine/v3.19/main 2024-09-02 12:30:23 Yeah ;) 2024-09-02 12:32:53 not sure what that's about, but i get an http 200 when i dl a pkg apk via https and curl 2024-09-02 12:33:21 I get a 301 to http://dl-cdn.alpinelinux.org/alpine/v3.19/main/ 2024-09-02 12:33:35 i get that on the landing page for some reason. odd 2024-09-02 12:33:39 That's… Weird that you don't get it too 2024-09-02 12:33:45 ah :D 2024-09-02 12:33:46 browser doesn't redirect tho 2024-09-02 12:33:46 ok 2024-09-02 12:33:55 strange 2024-09-02 12:33:59 That's an nginx issue if you leave out the final / 2024-09-02 12:34:12 ohh 2024-09-02 12:34:24 ohhh 2024-09-02 12:34:32 Would it be fixeable? 2024-09-02 12:35:12 good question, I haven't found a good solution yet 2024-09-02 12:35:13 I mean is it a configuration issue, or an inherent nginx problem 2024-09-02 12:35:17 ok 2024-09-02 12:35:29 Thanks for clarifying anyway ikke :) 2024-09-02 12:35:46 mkerkeni, sorry for the noise, can go on! 2024-09-02 12:35:55 Problem of nginx being behind a reverse proxy that does the tls termination 2024-09-02 12:37:00 right, it'd have to force the scheme instead of taking automatically from the server type 2024-09-02 12:38:46 They say: http://nginx.org/en/docs/http/converting_rewrite_rules.html 2024-09-02 12:39:19 Hummm, though I don't know what rules are actually there, I'll shut up. :) 2024-09-02 12:39:23 FWIW, wget says (among other): « URL transformed to HTTPS due to an HSTS policy » 2024-09-02 12:42:14 Got it, I'll check the nginx rewrite rules and HSTS policies. Thanks for the info! 2024-09-02 13:04:07 Hey all, I got it fixed! It was a time sync issue, as suggested. I synced the time in the Docker container, and now everything's working fine with the apk commands. Thanks for the help! 2024-09-02 14:55:37 lvscan show me inactive volumes as shown in the pic. Kindly need command line to make them active. Reference to the picture as actual setting going on, please 2024-09-02 14:56:29 ACTION uploaded an image: (89KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/aYwppzFhJBuZcAcdtITvAxLY/2024-09-02-19-49-50-967.jpg > 2024-09-02 14:56:56 the basic syntax iirc is lvchange -ay / 2024-09-02 14:57:52 usually tho i just do vgchange -ay to activate all volumes at once 2024-09-02 14:59:14 Thankyou 2024-09-02 15:00:22 sure, both the man page and --help are pretty cumbersome :P 2024-09-02 15:59:39 My machine keeps periodically rebooting suddenly (not a clean reboot; more like suddenly dies and then boots back up). Trying to figure out how I can try to get to the bottom of this in Alpine. Any ideas on pinning down the problem? 2024-09-02 16:01:41 RAM passes memtest86 (though the RAM stick used to have a partner that failed the memtest so the failed stick is gone) 2024-09-02 16:03:10 Might be worse problem than just a bad memory module 2024-09-02 16:03:19 SSD passes SMART health assessment. 2024-09-02 16:03:39 My current suspicion is bad motherboard. I've already replaced the PSU. 2024-09-02 16:11:24 ok 2024-09-02 16:11:25 yeah :/ 2024-09-02 16:30:03 grossaffe[m]: i experienced this before, your motherboard is probably shorting to the case 2024-09-02 16:30:20 Oh, that's an interesting thought. 2024-09-02 16:30:43 grossaffe[m]: i had the same issue (random reboots) when i ran alpine on a raspberry pi. the problem was indeed bad hw, but i had to narrow it down slowly by elimating other potential causes 2024-09-02 16:31:38 if you ran afford to sit and watch your dmesg logs until the issue recurs, you can run `dmesg -w` to tail them. you may get a kernel panic and a hint at the particular problem before the machine resets 2024-09-02 16:33:31 another thing to look at is file system corruption. you can reinstall all packages with `apk upgrade -a`. to detect corruption, generate a message authentication code for each file before and after this step. depending on the file system you chose, this may be relevant 2024-09-02 16:34:25 This is a new system. And this problem has been persistent across clean installs, so very much doubt package corruption to be the culprit. 2024-09-02 16:35:59 i suspected the SD card on the pi was dying but had to rule this out. but i think it is fair to say that sudden reboots can cause corruption and make the system even more instable 2024-09-02 16:37:01 i assume you're not running any out-of-kernel modules. those can cause issues sometimes 2024-09-02 16:37:55 I'll take a look at re-installing the motherboard and see if that helps. This is a mini-ITX board in a small case. As for corruption, Yes, I could see the sudden reboots potentially causing further issues to the filesystem (I see when it reboots that it is always fixing some fileystem issues, which isn't shocking given it doesn't shut down properly). 2024-09-02 16:37:55 And yes, I am using a pretty vanilla Alpine setup. No custom kernel. Just trying to make myself a little media server. 2024-09-02 16:39:32 yeah, i'd say getting the panic is your best bet. does the system ever just freeze instead of reboot? 2024-09-02 16:40:28 if not, would make sense if power issue 2024-09-02 16:40:46 It used to have freezing problems before I swapped out the PSU, I think. 2024-09-02 16:41:39 PSU was the only part I bought used for this build (the RAM was previously used, too, but by me and was known working; this machine killed one of my sticks) 2024-09-02 16:42:50 hmm, yeah that does make me suspect power and overvoltage protection 2024-09-02 16:43:09 err overcurrent 2024-09-02 16:43:13 But that PSU has since been replaced with a brand new EVGA PSU. 2024-09-02 16:43:38 My fear is that the old PSU may have damaged the motherboard, though. 2024-09-02 16:44:21 mhmm. i'd say all bets are off if a component died already 2024-09-02 16:50:04 i think the chipset (assuming intel here) runs on the same 3.3V rail as the memory modules 2024-09-02 16:51:34 AMD. Went with an AM5 APU (little did I realize at the time that AMD's AV1 encoder was broken for 1080p video) 2024-09-02 16:56:23 oic... another idea is to try inducing a failure with a stress test. you may be able to isolate the component that is defective if kernel panic logs are not fruitful 2024-09-02 16:57:59 i remember getting failures more often when i was compiling. this page has lots of good ideas: https://wiki.archlinux.org/title/Stress_testing 2024-09-02 16:58:20 My machine is h appy to fail at idle. 2024-09-02 16:59:57 haha, mine was too. but more prone with memory operations and cpu load 2024-09-02 17:00:51 Okay, I'll add stress test to my to-do list. 2024-09-02 17:01:22 you can run dmesg -w in tmux in one window and the stress test in another 2024-09-02 17:28:42 ACTION uploaded an image: (106KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/EgGyZjdJKcvXjXRYISEacFqm/2024-09-02-22-28-23-587.jpg > 2024-09-02 17:28:44 Need help with this 2024-09-02 17:47:40 how is alpine compared to kicksecure 2024-09-02 17:48:58 That assumes we know what kicksecure is 2024-09-02 18:02:26 i have not used kicksecure but i have used whonix. assume it's p similar 2024-09-02 18:02:41 oh, he left :P 2024-09-02 18:05:19 It might be https://www.kicksecure.com/ > Kicksecure is a secure by default OS always based on the latest security research. 2024-09-02 18:05:31 Never heard of it. 2024-09-02 18:08:35 ok, and i never tried Alpine OS, do you guys reccomend it as a daily, or only as a portable live os 2024-09-02 18:09:32 We absolutely recommend it as your daily os! 2024-09-02 18:09:58 (Depends on what you want to achive actually) 2024-09-02 18:10:52 my biggest reservation about recommending it for daily use is not being able to install multiple kernel versions natively. at least, not that i know of. i prefer running it virtualized so i can seamlessly roll back to previous kernels with file system snapshots 2024-09-02 18:10:53 well, kinda not have the OS spying on me. Do a bit of video and photo editing and run some social apps 2024-09-02 18:11:32 "2024-09-02-22-28-23-587.jpg" <- ? 2024-09-02 18:11:32 thanks for input 2024-09-02 18:13:20 why would you want to roll back to previous kernels / im still new to linux distros 2024-09-02 18:14:16 literally every linux distro out there doesn't spy on you 2024-09-02 18:15:34 user_: you might run into some issue with the newer kernel. maybe a kernel module failed to compile and you didn't notice before you rebooted. perhaps you upgraded from alpine 3.19 to 3.20 and some hardware isn't working the way you expect. it is nice to roll back in such situations 2024-09-02 18:16:48 i haven't tried kicksecure, but the impression i get is that it's basically a hardened install like whonix. except whonix is distributed in two parts: a gateway and a workstation. this is done to prevent malware on the workstation from deanonymizing your tor connection. the two projects have some relation to one another but i can't remember what 2024-09-02 18:18:33 if you just want a no nonsense distribution with sensible defaults and that doesn't spy on you, i generally recommend debian for people newer to linux 2024-09-02 18:21:26 Hardened distributions like kicksecure and whonix exist to make it harder for malicious (or exploited) programs to spy on you, no distribution itself spies on you (at least not the popular ones), like Ermine said 2024-09-02 18:24:27 I mean i migrated to Linux because win did unreasonably much spying. Then i stumbled upon kicksecure and now Alpine. And i have a bit of truble with kicksecure and apps to run on it. and it looks kind of dull, so i will definitly try Alpine. Thanks for the input guys 2024-09-02 18:26:24 if you don't have the technical know-how to troubleshoot and resolve hardening-related issues, it's not ideal to use them. hardening breaks things and that's why most distributions and kernels are not super hardened by default 2024-09-02 18:27:44 unfortuneatly, hardening is probably the way to go forward, more or less. 2024-09-02 18:28:15 have you looked into qubes at all? if you really want a secure distribution, it's the one i would recommend 2024-09-02 18:31:12 one nice thing about qubes is that you can pretty seamlessly run mainstream distros for the applications you need. it gives you a radical amount of control over sandboxing that is kind of mind-blowing. nice balance of compatibility and security 2024-09-02 18:35:48 thanks peerless. Yes but do you think Qubes is suitable as daily OS? I did run it before with whonix from usb. Now Im looking for a better daily experience. Will have a go with it again. thanks 2024-09-02 18:37:19 Do you know if Mullvad is working on Alpine? 2024-09-02 18:38:24 you can use just about any openvpn or wireguard service on linux 2024-09-02 18:38:59 i ran qubes for about a year as a daily. it worked well. i did end up running back to debian because security and convenience are at odds, and i had no real need for that level of isolation. there are things i learned from qubes that i brought into my daily practice though. it was a great learning OS 2024-09-02 18:43:11 security claims are hard to verify, because stuff changes all the time. but defaults do matter in the comparisons. 2024-09-02 18:45:26 you could just take a mainstream distro and apply some hardening techniques yourself. if things break, revert the changes you made. this is my bible on that subject: https://madaidans-insecurities.github.io/guides/linux-hardening.html 2024-09-02 18:48:06 thanks! 2024-09-02 18:48:08 or follow a STIG for AlmaLinux or SUSE https://www.stigviewer.com/stig/red_hat_enterprise_linux_9/ 2024-09-02 18:51:48 having gone down this rabbit hole years ago myself, i'd recommend avoiding hardened kernels and honestly, just use systemd lol. yes it's more attack surface but it makes service sandboxing trivial 2024-09-02 18:54:19 if you really want to compile your own slimmed down kernel, you can do so on fedora and follow the RHEL guidance for the most part 2024-09-02 18:54:58 gentoo is not for the faint of heart lol 2024-09-02 18:58:53 people are not good about setting constraints for themselves; which is why sane, well documented defaults matter. that's where the conversation starts. it's harder to have a conversation around innumerable security guides or wikis or youtube videos, primarily oriented around systemd, which alpine is not. 2024-09-02 19:01:22 downloaded alpine now, need to find somewere to run the iso from 2024-09-02 19:07:28 can you recomend an app for easy acces to apps 2024-09-02 19:07:45 like libray folder kind of thing 2024-09-02 19:13:10 for me, the main pitch of running alpine as your daily driver is having a personal bias towards simplicity. as a downstream consequence of security-conscious decisions e.g. running openrc instead of systemd, ash instead of bash, and busybox instead of gnu coreutils, the system is far less complex than are most distrubitons 2024-09-02 19:13:43 qubes is a decent amount of work but highly secure and compatible. source distributions are way too much work for me and keeping tabs on upcoming kernel features and flags is just painful. alpine "just works" (at least if you don't need GNU libc in which case there is a compatibility layer that mostly works) 2024-09-02 19:20:44 still, my main system is a hypervisor and i prefer systemd to openrc for that purpose. i also think it's better to learn systemd than openrc for general futureproof linux knowledge, as this is where most distributions have gone. likewise with gnu coreutils vs busybox 2024-09-02 19:23:55 sorry if i have triggered all of the openrc diehards :'D i DO like it quite a bit but not for everything 2024-09-02 19:54:07 can you turn pmos into alpine? but i wanted to use unl0kr 2024-09-02 20:15:16 scorpion2185[m]: seems alpine-to-pmos isn't well-supported: https://gitlab.com/postmarketOS/pmaports/-/issues/106 . the other direction has no documentation that i can find. in theory reversing https://wiki.postmarketos.org/wiki/Existing_Alpine_installation should work but i have no experience trying this and expect there be dragons... to get unl0kr on alpine, you will have to pull https://github.com/droidian/unl0kr and compile 2024-09-02 20:17:38 you might want to first test that you can compile unl0kr in an alpine virtual machine. it looks to me that you can obtain all of the dependencies that are not statically linked from alpine's package list 2024-09-02 20:21:55 in fact, you could try all of this in a virtual machine first to get the procedure down pat before messing with your real device 2024-09-02 20:26:04 unl0kr is in pmos repo it's from pmos actually, problem is https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/18 2024-09-02 20:26:21 when i turned alpine into pmos it messed up my tablet 2024-09-02 20:27:02 it's in buffybox "bundle" https://gitlab.com/postmarketOS/buffybox 2024-09-02 20:28:45 i wanted to install alpine on a pinephone using pmos repo masked for kernel etc. 2024-09-02 20:28:55 i suspect you don't want to mix pmos and alpine repos if your goal is to wind up with an alpine system, but alpine does not have unl0kr 2024-09-02 20:29:28 that's why you mask them 2024-09-02 20:30:01 does apk use the repo that's before in the file? 2024-09-02 20:32:23 not sure... the wiki page seems to imply that order matters 2024-09-02 20:51:48 seems like you'll have to hack quite a bit to get it working and maintain your hack to keep it working. given that an init.sh refactor exists in pmos, the biggest remaining blocker on a prospective MR is the creation of a regression test suite. you may be able to ping #alpine-devel about the feasability of this if you are not interested in rolling your own init.sh hack 2024-09-03 15:59:11 peerl3ss: I have followed https://wiki.alpinelinux.org/wiki/LVM_on_LUKS#Creating_and_Mounting_the_File_Systems guide for installing alpine full disk encryption. when at last I `reboot` and pullout USB. it booted to alpine and ask for encrypted password. but whenever I reboot again, I shows no bootable device found 2024-09-03 16:00:07 my laptop is Toshiba satellite pro NB10t 2024-09-03 16:00:25 I do have uefi 2024-09-03 16:19:13 Velo_Frost[m]: to be clear: you followed the uefi/gpt instructions, and ignored the dos/mbr instructions? 2024-09-03 16:22:14 opinion, that page should be split into two pages. one for uefi/gpt and another for dos/mbr. the subject matter gets more confusing when it tries to handle both. 2024-09-03 16:24:52 i followed uefi/gpt 2024-09-03 16:25:33 is dos/mbr good to try when facing the problem as i discussed above? 2024-09-03 16:26:10 moreover any other user guid for full disk encryption 2024-09-03 16:30:05 Toshiba satellite pro NB10t bootloader key 2024-09-03 17:10:04 Velo_Frost[m]: dos/mbr always works 2024-09-03 17:10:31 good to hear 2024-09-03 17:10:45 but why is the problem with uefi 2024-09-03 17:11:35 there shouldn't be but, in either case, everything has to be done right. 2024-09-03 17:11:38 and for dos/mbr my bootloader be uefi or CSM? as I only have these two options in bootloader 2024-09-03 17:12:47 invoked: all right, can I make a list of commands that I have to use with setup. if I am missing anyone and you can guide please 2024-09-03 17:15:06 Velo_Frost[m]: there is also setup-alpine which will do this for you 2024-09-03 17:15:39 that is not encrypting lvm 0n luks 2024-09-03 17:16:22 # setup-keymap... (full message at ) 2024-09-03 17:21:51 https://wiki.alpinelinux.org/wiki/LVM_on_LUKS 2024-09-03 17:22:32 i was just suggesting it as a more turnkey thing. 2024-09-03 17:32:02 in my own case -- usually -- i manually do mbr with grub, encrypted root, cryptkey, vg name == $HOSTNAME 2024-09-03 17:33:27 i thought about doing some MR with that as an option, but i'm not sure it would be in acceptable form. 2024-09-03 17:34:27 there's still things that can go wrong no matter what approach 2024-09-03 17:53:11 # setup-keymap... (full message at ) 2024-09-03 17:58:05 Velo_Frost[m]: > <@surya_x3:matrix.org> # setup-keymap... (full message at ) 2024-09-03 18:00:01 * ```... (full message at ) 2024-09-03 18:00:51 my apology 2024-09-03 18:03:19 Velo_Frost[m]: don't confuse your efi partition with your boot partition 2024-09-03 18:03:47 this is also why mbr is simpler (2tb disk limitation aside) 2024-09-03 18:03:50 invoked: these are two different things? 2024-09-03 18:03:54 yes. 2024-09-03 18:04:14 some people make them one thing, but they know exactly what they are doing 2024-09-03 18:04:26 lvcreate -L 16G vg0 -n boot 2024-09-03 18:04:32 and 2024-09-03 18:04:54 i have to step out. bbl 2024-09-03 18:05:03 mkfs.ext4 /dev/vg0/boot 2024-09-03 18:05:14 ok. all my steps are ok? 2024-09-03 18:17:57 https://paste.mozilla.org/ajwfbQxe 2024-09-03 18:17:57 kindly check the paste in for full disk encryption lvm on luks. Are these commands correct 2024-09-03 18:19:13 if some correction there is edit button on top to correct 2024-09-03 18:19:14 please 2024-09-03 18:31:18 clandmeter: friendly greetings :) 2024-09-03 18:32:07 just created a wiki account and saw there's a contribute artwork .. i flew about swiss alps and did some photos, so if there's an image you like and want to use: 2024-09-03 18:33:13 https://www.flickr.com/photos/aiei/sets/72157650144744776/with/24400951973/ (for some reason doesn't load for me, but maybe for you?) 2024-09-03 18:36:59 works for me. there are some really nice pictures in it 👍️ 2024-09-03 18:37:37 take with a canon 5d2 100mm 2024-09-03 18:37:40 fossdd[m]: can you check the paste in plz 2024-09-03 18:38:29 I Boot to USB media after 1st reboot when alpine full disk encryption is installed 2024-09-03 18:38:57 one time it Boot to sda than grub cannot find media device 2024-09-03 18:40:59 fossdd[m]: thanks. i should probably dig out the 1000 others, which are offline 2024-09-03 18:41:20 one alpine background image for every release? 2024-09-03 18:42:43 i'm mainly interested in small and desktop (multimedia, video, audio) and gnustep, so i will try to contribute. and because i like small, consistent and non-distracting, i'm using this as background: https://github.com/alexmyczko/autoexec.bat/blob/master/gray.png 2024-09-03 18:42:57 (works really well on the eyes, no matter if it's day or night) 2024-09-03 18:45:12 Velo_Frost[m]: your GRUB_CMDLINE_LINUX_DEFAULT is not correct. it should be, e.g. "modules=sd-mod,usb,ext4,nvme,keymap,whatever,whatever [options]" 2024-09-03 18:45:38 gone again 2024-09-03 18:46:53 invoked: all right it should contain (,)? 2024-09-03 19:13:25 and do I have to install syslinux? 2024-09-03 19:14:25 is it a necessary part? to write MBR without system partition. 2024-09-03 19:14:42 as I use uefi 2024-09-03 19:43:24 All right invoked I have successfully booted to encrypted alpine linux. what change I have to made so I don't Boot back to media installation grub window 2024-09-03 19:43:42 any post installation process I have to do 2024-09-03 19:54:46 i don't know what's wrong. but when i type date, i get today 2097. and when i uptime says 24855 days... 2024-09-03 19:55:08 lol 2024-09-03 19:55:12 How is it in the future? 2024-09-03 19:56:47 what's an rdate server that works? 2024-09-03 19:58:00 Never used rdate 2024-09-03 19:58:21 ok chrony says it's running, but it's still 2097 2024-09-03 19:58:38 alex_: what does chrony tracking say? 2024-09-03 19:58:40 chonyc 2024-09-03 19:59:23 it says many letters. which line do you want? i can't copy paste from this UTM 2024-09-03 19:59:33 last offset 2024-09-03 19:59:48 +0.005905933 seconds 2024-09-03 19:59:53 and the ref time it shows right 2024-09-03 19:59:59 huh 2024-09-03 20:00:12 alex_: im going to switzerland saturday. ill make some pics :) 2024-09-03 20:00:31 clandmeter: enjoy!. i'm in poland wed-sun 2024-09-03 20:00:48 how did you shoot them? 2024-09-03 20:01:05 ikke: ok /bin/date is busybox and i must confess randomly run upx on /usr/bin, /bin, /usr/sbin, /sbin binaryes, including busybox* 2024-09-03 20:01:23 clandmeter: sit in a small airplane, aim with camrea and click? 2024-09-03 20:01:35 oh, so upx may have broken things? 2024-09-03 20:01:48 let me upx -d busybox and see 2024-09-03 20:02:25 busybox is back to 935k from 509k and date is still wrong 2024-09-03 20:02:53 i'm not sure what exactly broke things, everything looked fine until i wanted to debug/fix ruptime 2024-09-03 20:03:21 clandmeter: Maybe you can make a picture like https://dev.alpinelinux.org/~kevin/alpine_wallpaper_2.png :P 2024-09-03 20:03:31 i guess just click and it stopped working 2024-09-03 20:06:27 ok i run rdate -s time.nist.gov and it gets even better Sat Oct 11 04:34:15 CEST 2160 2024-09-03 20:07:58 ikke: ill see what I can do 2024-09-03 20:09:44 ok date 100322092024 more or less fixed the time, but uptime is still wrong... 2024-09-03 20:10:56 hah using strace, checking /proc/uptime ... some seconds later date is wrong again.. 2024-09-03 20:12:33 stopping chrony, setting time, running date, wrong :( 2024-09-03 20:13:20 ok the virtual machine arm64, has been running a few days, with sleep (lid down up) hosted on macOS but this should not happen, trying reboot 2024-09-03 21:33:08 "All right invoked I have..." <- I have to install grub-install --target.............. again to boot my installed alpine linux. and I have to mount root,boot,sys,proc,swap and than install grub and finally umount all and reboot. than I am only able to boot to installed alpine linux in grub. what is the issue here? 2024-09-03 21:33:33 any body who has the same issue 2024-09-03 21:39:02 Do I need to install windows along side? as I only have installed alpine linux on whole system 2024-09-03 22:32:05 whydo you want windows? 2024-09-03 22:33:59 Occasionally for FW updates, but honestly... once the Linux system runs it hardly matters. I do have one laptop where I regret wiping Windows, as it has a graphics driver bug in every Linux distro: black screen after every mode switch, only fixable by a suspend/resume cycle. 2024-09-03 22:34:20 I do slightly wonder if a FW upgrade would help, who knows. 2024-09-03 22:34:41 But I also don't want to wipe the OS... 2024-09-03 23:18:21 I'm trying to write Alpine's standard x86_64 ISO to a USB drive and it's giving me hell. Tried downloading the image again, checked the hashes and signatures, nothing. Etcher did give me this error (https://imgur.com/a/ofAHwvA) but I don't know anything else. 2024-09-03 23:18:40 It just loops me back to the boot select menu with no error or anything. 2024-09-03 23:19:02 I even tried making a new GPT table and extracting the ISO contents to a FAT32 partition. 2024-09-03 23:19:19 Also wrote out /dev/zero to my flash drive to clear it, nothing. 2024-09-03 23:27:15 "whydo you want windows?" <- I cannot seet grub after installing alpine. its just show on 1st reboot when I install alpine. login and when I want to reboot and start laptop again, it shows **"Reboot and select proper Boot device or insert Boot Media in selected Boot device and press any key"** 2024-09-03 23:27:29 s/seet/see/ 2024-09-03 23:29:22 grub was installed (chroot) grub-install --target=x86_64-efi --efi-directory=/boot/efi 2024-09-03 23:30:58 efi partition is not encrypted which is sda1 and other sda2 partition is encrypted. 2024-09-03 23:36:54 GRUB is installed but the menu is not shown at boot when reboot. I only see GRUB once and for all and that when I finished all installation ALpine and type reboot. 2024-09-04 05:59:40 Velo_Frost[m]: i've run into some issues with EFI installs that were a bit difficult to troubleshoot 2024-09-04 06:01:10 it's been awhile and my memory is vague, but there was some issue with having seperate EFI and boot partitions in my case 2024-09-04 06:01:35 so what i wound up doing is: combine the /boot and /boot/efi mount points into a single partition, formatted as vfat 2024-09-04 06:03:34 on that unified partition, set the type code in gdisk (assuming you are using GPT disks) to EF00 2024-09-04 06:06:49 it took awhile to find that that arrangement worked and now all my alpine VMs are set up that way. it's worth a shot in your case 2024-09-04 07:59:59 "so what i wound up doing is..." <- I have efi boot partition on sda1 (not encrypted) 2024-09-04 07:59:59 Do you mean to combine them to one? 2024-09-04 07:59:59 And addationally created lvcreate -L 2G vg0 -n boot in an encrypted volume sda2 2024-09-04 08:06:45 Where as I have mounted as below... (full message at ) 2024-09-04 08:20:15 Velo_Frost[m]: yes, this is what i had to do to get GRUB to boot Alpine on an UEFI system (though I did not use LVM) 2024-09-04 08:21:39 well, hold on. not quite "yes" 2024-09-04 08:22:08 the idea would be to combine boot and EFI on sda1 and not encrypt either 2024-09-04 08:22:52 300MB is more than enough space for both 2024-09-04 08:24:10 another option would to try a bootloader other than GRUB. i prefer GRUB, so i was willing to compromise my ideal partition layout to keep it 2024-09-04 09:16:36 "the idea would be to combine..." <- What would be the command line for both if using sda1 2024-09-04 09:17:59 And also mount command for this 2024-09-04 09:21:05 that depends on how you have your disks set up. if you had just one partition on the sda device, you could run "sgdisk -o -N 1 -c 1:boot -t 1:ef00 /dev/sda" 2024-09-04 09:21:34 i would imagine you have your lvm partition on sda also, so it's probably better to do the partitioning interactively with `gdisk` 2024-09-04 09:21:44 I have 2 partation 2024-09-04 09:22:01 peerl3ss: I did with parted 2024-09-04 09:22:38 ohh, you're doing mbr 2024-09-04 09:24:07 Sad... (full message at ) 2024-09-04 09:24:28 peerl3ss: No its got but MBR is protected 2024-09-04 09:24:45 * No it is GPT but MBR is protected 2024-09-04 09:25:17 s/Sad/Sda/ 2024-09-04 09:26:03 ok, gotcha. i usually use gdisk to set up GPT disks with protected MBR so i don't know the syntax off the top of my head 2024-09-04 09:27:45 it should be the same as this section: https://wiki.alpinelinux.org/wiki/LVM_on_LUKS#UEFI_with_GPT_disklabel 2024-09-04 09:28:52 i would 300M instead of 200M for the combined partition but honestly 200M is probably enough 2024-09-04 09:29:36 then you just skip the `lvcreate` for boot (command #2) of https://wiki.alpinelinux.org/wiki/LVM_on_LUKS#LV_Creation_for_UEFI/GPT 2024-09-04 09:31:05 `mount -t vfat /dev/sda1 /mnt/boot` to mount. in this case, efi is just a subdirectory of /boot not a mount point itself. you may need to mkdir /mnt/boot/efi 2024-09-04 09:44:21 All right. I too follow the lvm on luks guide which you have mentioned. But you said earlier that you didn't use lvm. 2024-09-04 09:45:02 yeah, i don't use encryption either, though i'd recommend GRUB for that 2024-09-04 09:47:47 but... if you are just using LVM for a swap partition and the root, i think you could certainly get by without it 2024-09-04 09:47:53 Thing is when I followed this guide using encryption and lvm. Uefi and grub. I boot to alpine successfully. Everything work fine. But once I reboot, I don't see any grub menu and all I see black screen asking for bootable device, press any key. 2024-09-04 09:49:09 hmm. did you reboot with the USB taken out? 2024-09-04 09:51:32 I than again boot from USB, setup-interfaces select wlan0 for WiFi and than install cryptsetup and decrypt sba2 and mount all things. Chroot and install grub than reboot. Unplug USB immeditly and alpine boot to grub menu to select alpine or uefi settings. 2024-09-04 09:52:55 i'm not sure what to make of your being able to boot into your system successfully only once. in my case, i wasn't able to get past the bootloader unless i combined /boot and /boot/efi 2024-09-04 09:53:55 sometimes removing a device can change the boot order in the UEFI compared to when you had it in. you might just need to manually create a boot entry when that happens 2024-09-04 09:53:58 peerl3ss: Yes. I took USB out on 1st booting the machine, at that point grub work well. Login to alpine. But once login without USB in, and if I reboot, than the error occured 2024-09-04 09:55:33 peerl3ss: How can I manage manual 2024-09-04 09:56:07 depending on your motherboard, you can probably do this interactively in the settings menu when you switch the PC on 2024-09-04 09:56:08 I think the problems is grub. Which disappeared 2024-09-04 09:57:01 it could be that you're not getting to grub because the boot entry for it went away 2024-09-04 09:58:38 if you 'boot from file' in the uefi menu and select the disk containing your EFI partition, the file to boot from is `boot\bootx64.efi` (assuming you are on x86_64 CPU architecture` 2024-09-04 09:59:25 peerl3ss: Oh yes, that I select ssd than man than usb 2024-09-04 09:59:47 that's supposed to be efi\boot\bootx64.efi 2024-09-04 09:59:57 peerl3ss: Yes this is what happen. But I don't know how to manage 2024-09-04 10:00:02 (which the firmware would find automatically if it existed) 2024-09-04 10:00:18 I don't think grub installs itself there by default though 2024-09-04 10:00:51 on my system, i don't have the extra `efi` dir. but that's probably because i combined EFI and boot into one partition 2024-09-04 10:01:22 i would try boot from file and see if that works. if it does, you can manually add the new entry afterwards 2024-09-04 10:02:05 maybe a result of moving files around during said combining 2024-09-04 10:02:46 peerl3ss: I too have no extra setting in uefi in boot settings. Its just uefi,CBM or CSM thing and secure boot toggel. 2024-09-04 10:02:48 e.g. if you had /boot and /boot/efi, but told grub to install to /boot, and then moved /boot/efi to /boot... 2024-09-04 10:02:49 it has something to do with the --efi-directory=/boot/efi parameter to grub-install 2024-09-04 10:03:22 but it nevertheless has to be [efi_partition]\efi\boot\ from the firmware point of view (so e.g. /boot/efi/efi/boot from the linux perspective) 2024-09-04 10:03:41 ye, i just have /boot/efi/boot 2024-09-04 10:04:15 Velo_Frost[m]: there should be a list of boot menu entries in your settings somewhere. usually the boot from file option is in/near there 2024-09-04 10:04:41 if there's no "boot from file" look for "launch efi shell" 2024-09-04 10:06:12 anyway the point I wanted to make is that if the file were at the correct location [efi_partition]\efi\boot\bootx64.efi the firmware would most likely find and boot it automatically 2024-09-04 10:06:42 so if it somehow happens to be at just \boot\bootx64.efi, better figure out why that is the case first 2024-09-04 10:07:02 because no bootloader install puts it there... 2024-09-04 10:07:14 peerl3ss: Its not there. I search the whole uefi boot settings. I have Toshiba satellite pro mini laptop 2024-09-04 10:07:46 yeah not all firmwares have it 2024-09-04 10:07:54 is there an "efi shell" option though? 2024-09-04 10:08:33 grawity: No 2024-09-04 10:09:02 I will send the pic of my uefi screen in while. I'm on way to home 2024-09-04 10:10:26 what files do you have in the efi partition? 2024-09-04 10:10:39 well, what *.efi files 2024-09-04 10:18:42 ACTION uploaded an image: (52KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/LyWCTYQZlKYBMAilTguLfGGQ/2024-09-04-15-15-44-021.jpg > 2024-09-04 10:18:43 ACTION uploaded an image: (65KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/UdsNfOjwDITvsiFUoLukMAKo/2024-09-04-15-16-03-855.jpg > 2024-09-04 10:18:46 ACTION uploaded an image: (78KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/VRttZyffCdTQrEAPAbkgtQAp/2024-09-04-15-16-24-345.jpg > 2024-09-04 10:18:49 ACTION uploaded an image: (62KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/jdvgosvjPuNKxUkoUgjiPOEB/2024-09-04-15-16-37-048.jpg > 2024-09-04 10:18:52 ACTION uploaded an image: (52KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/tVJhsXydXFlHkGRUgpgEVgDL/2024-09-04-15-16-50-256.jpg > 2024-09-04 10:18:54 ACTION uploaded an image: (65KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/uRKuuzmyYMhSCgpdhuyduXkY/2024-09-04-15-16-58-719.jpg > 2024-09-04 10:18:57 ACTION uploaded an image: (63KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/VixldaXrqzbiHzPIsueSGgYE/2024-09-04-15-17-20-700.jpg > 2024-09-04 10:18:58 .. 2024-09-04 10:19:00 These are overall setting I have. No more no less 2024-09-04 10:19:05 ACTION uploaded an image: (62KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/FDRltQXOWXTYxVQkdVZKuWPb/2024-09-04-15-17-31-403.jpg > 2024-09-04 10:19:10 ACTION uploaded an image: (70KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/XnNwmSxRlmZWpMsxmwoZgemY/2024-09-04-15-17-52-721.jpg > 2024-09-04 10:19:40 ok 2024-09-04 10:19:51 what files do you have in the EFI partition? 2024-09-04 10:20:05 "what files do you have in the..." <- I don't understand what you mean. Sorry 2024-09-04 10:20:17 literally a list of files 2024-09-04 10:20:45 grawity: Let me check them 2024-09-04 10:31:13 "what files do you have in the..." <- Should I have to mount efi partition 1st to see the constant? 2024-09-04 10:32:57 mount -t vfat /dev/sda1 /mnt/boot/efi 2024-09-04 10:33:34 yes. you can list files with `find /boot -name '*.efi'` 2024-09-04 10:40:31 ACTION uploaded an image: (92KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/saKEssFboJEzZUMwGrJGJKuR/2024-09-04-15-40-08-821.jpg > 2024-09-04 10:40:33 ACTION uploaded an image: (127KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/hjTWAVNwAvPdKOGEBdaKCeOu/2024-09-04-15-40-17-318.jpg > 2024-09-04 10:41:21 ok, looks like the boot entry is indeed missing 2024-09-04 10:42:29 "yes. you can list files with `..." <- What is the exact command. 2024-09-04 10:43:14 if you have efi mounted to /mnt/boot/efi, it is `find /mnt/boot -name '*.efi'` 2024-09-04 10:45:25 peerl3ss: Wait I just didn't mount anything. I'm on bootable USB. Let me mount root,proc,sys et 2024-09-04 10:46:35 you can recreate the missing boot entry with efibootmgr: `efibootmgr -c -d /dev/sda -L Alpine` 2024-09-04 10:49:31 what file path does that default to? 2024-09-04 10:51:43 Command not ececuted 2024-09-04 10:52:20 find /mnt/boot-name'*efi' 2024-09-04 10:52:49 Boot-name is sda1 or it is as it is 2024-09-04 10:53:02 first of all you're missing a few spaces in there 2024-09-04 10:53:10 it was `/mnt/boot` separately from `-name` 2024-09-04 10:53:24 the `/mnt/boot` is wherever you mounted sda1 2024-09-04 10:53:34 so like if you did `mount /dev/sda1 /mnt/boot/efi` as you said previously 2024-09-04 10:53:46 then do `find /mnt/boot/efi -name "*.efi"` 2024-09-04 10:55:26 grawity: Work 2024-09-04 11:00:09 * Checking 2024-09-04 11:00:47 ACTION uploaded an image: (108KiB) < https://matrix.org/oftc/media/v1/media/download/AUoNVSB77nz8zsWI8uBFX71g6O2cIQr78JIRk9LZecSbAzzF8YEWeiVRBhU5HDZTwVyJp75SfxQbEpW4khrXnNtCeRvmki7gAG1hdHJpeC5vcmcvTE96WUZUR25RZmNxUklkaWh6SGt6cUN5 > 2024-09-04 11:01:47 interesting. no `bootx64.efi` 2024-09-04 11:02:14 yeah as I said grub-install does not install one by default 2024-09-04 11:02:37 some distros patch it to install both, I know debian does, but from what I remember, alpine doesn't 2024-09-04 11:02:56