2025-01-02 10:26:57 <ncopa> clandmeter: btw, I have not set up the CI for the riscv machine we replaced storage for
2025-01-02 10:27:18 <ncopa> so riscv64 CI is on reduced capacity
2025-01-02 10:30:42 <clandmeter> Ok, not sure if i have time today. need to fix some other stuff at the house
2025-01-02 10:31:14 <clandmeter> i also think i know how to fix the bootloader menu not showing up on serial
2025-01-02 10:49:52 <mps> clandmeter: you use grub?
2025-01-02 10:53:57 <ncopa> we want be able to use grub for the pioneer machines
2025-01-02 10:54:39 <ncopa> or let me put it this way: we want be able to build and update kernels for pioneer without needing to rebuild and update the boot loader(s) with erevery kernel update
2025-01-02 10:57:13 <mps> does it use u-boot
2025-01-02 10:57:44 <mps> iirc when I looked at it u-boot is in 'chain' there
2025-01-02 11:09:51 <ncopa> no
2025-01-02 11:10:32 <ncopa> well it may use uboot, but I don't know how, and i dont find much documenation for u-boot on pioneer/sg2042
2025-01-02 11:11:17 <ncopa> they use u-root, which basically is a linux kernel with nvme drivers that will kexec kernel from nvme
2025-01-02 11:11:29 <ncopa> or they use edk2
2025-01-02 11:11:34 <ncopa> which loads grub
2025-01-03 19:35:21 <mps> anyone of you use riscv64 as desktop?
2025-01-03 19:43:07 <ncopa> no
2025-01-03 19:43:23 <ncopa> still too slow compared to the i9 and macbooks
2025-01-03 19:46:41 <mps> I've built telegram-desktop on riscv64 and not sure should it be pushed to aports. it is slow to build
2025-01-04 22:12:49 <mps> anyone knows why linux-edge 6.12.8 is not built in 3.21-stable
2025-01-04 22:13:06 <mps> or is not uploaded
2025-01-06 07:44:08 <ncopa> which arch?
2025-01-06 07:44:49 <ncopa> it is built https://build.alpinelinux.org/buildlogs/build-3-21-aarch64/community/linux-edge/
2025-01-06 07:45:15 <ncopa> it is uploaded https://dl-master.alpinelinux.org/alpine/v3.21/community/aarch64/linux-edge-6.12.8-r0.apk
2025-01-06 07:48:32 <mps> riscv64
2025-01-06 07:48:56 <mps> sorry, forgot to mention
2025-01-06 07:52:56 <ncopa> oh. not good :-/
2025-01-06 08:02:02 <ncopa> seems like it hadnt built anything since 29 Dec
2025-01-06 08:02:11 <ncopa> same with build-3-20-riscv64
2025-01-06 08:02:19 <ncopa> thanks for the ping mps
2025-01-06 08:24:54 <clandmeter> ncopa: there is an issue with that box
2025-01-06 08:25:05 <clandmeter> when it boots it need manual fw rules
2025-01-06 08:25:17 <clandmeter> i think this is what blocks the builds
2025-01-06 08:25:35 <clandmeter> im testing edk2 on pioneer2
2025-01-06 08:32:32 <ncopa> 👍
2025-01-06 08:42:27 <clandmeter> different error now
2025-01-06 08:42:35 <clandmeter> like reported on github
2025-01-06 09:17:37 <mps> I deleted my OTP on an old phone and now cannot login to gitlab.a.o
2025-01-06 09:18:02 <mps> how can I solve problem
2025-01-06 09:58:27 <ncopa> mps: I disabled the two factor auth for you now
2025-01-06 10:01:02 <mps> ncopa: thank you, I've got page to reregister OTP
2025-01-06 10:01:33 <ncopa> you're welcome
2025-01-06 12:00:24 <mps> huh, world is becoming too much complicated. my phone can't scan QR code to enable 2FA :|
2025-01-06 12:04:43 <clandmeter> install a compatible app maybe?
2025-01-06 12:10:12 <ncopa> maybe clean the camera lens? :)
2025-01-06 12:10:43 <mps> ncopa: :)
2025-01-06 12:11:46 <mps> I'm using FreeOPT+
2025-01-06 15:05:20 <clandmeter> ncopa: seems the edk2 relocation error happens when its loading the grub stub 
2025-01-06 15:05:51 <clandmeter> when renaming it on nvme it does go further, but still does not show me efi shell 
2025-01-06 15:15:53 <clandmeter> i just broke the boot sdcard
2025-01-06 15:16:02 <clandmeter> what a joy
2025-01-06 18:20:55 <mps> tried two otp programs on two phones, no one can recognize QR code on gitlab.a.o when I'm trying to enable 2FA, and looks like gitlab.a.o will be lodked for me in near day or two /o\
2025-01-06 18:21:38 <mps> can someone tell which program works on android
2025-01-06 18:23:05 <ikke> I use authy, but that's from twillio
2025-01-06 18:25:32 <mps> authy cannot be downloaded if user is not registered, iiuc?
2025-01-06 18:26:25 <ikke> iirc, an account is not required
2025-01-06 18:34:03 <mps> ah yes, https://www.authy.com/download/
2025-01-06 18:40:06 <mps> otpclient on alpine says "can't find a valid qrcode" when I feed image to it
2025-01-06 18:53:04 <mps> oh, otpclient and set it manually worked
2025-01-06 18:59:15 <mps> I guess now is all ok
2025-01-06 18:59:49 <mps> maybe 'hope' instead of 'guess' is better term
2025-01-07 08:41:28 <iggy> I just use oathtool
2025-01-07 09:44:20 <mps> iggy: first time hear for it, looks interesting. thanks
2025-01-07 15:10:34 <valerius> I use oathtool on my desktop, you can also import the keys into a program called "Aegis" on Android
2025-01-07 15:10:52 <valerius> an "app", sorry
2025-01-07 15:10:55 <valerius> 
ACTION strokes grey beard

2025-01-07 16:05:52 <mps> could be qrcode read by oathtool?
2025-01-07 16:06:27 <mps> to reformulate, could oathtool read qrcode?
2025-01-07 16:22:23 <iggy> mps: I don't think so, but every 2fa prompt I've ever seen either showed the key or there was a little button/link you could click to show it
2025-01-07 16:46:46 <panekj> mps: FreeOTP+ works on Android
2025-01-07 16:48:21 <mps> panekj: yes, but can't read qrcode on gitlab.a.o
2025-01-07 16:48:44 <panekj> what can I say, except for "works for me"
2025-01-07 16:49:13 <panekj> I had it set up before and just did it again to check if it didn't break and it worked
2025-01-07 16:49:30 <mps> could be problem with lineageOS on my phone
2025-01-07 16:49:40 <panekj> maybe you have time wrong?
2025-01-07 16:50:03 <mps> no, time is ok
2025-01-07 16:50:32 <panekj> does it just not understand the qrcode?
2025-01-07 16:51:14 <mps> though have to add that I don't have much experience with OTP, I use it only when must
2025-01-07 16:52:00 <mps> panekj: yes, it says "can't find a valid qrcode" when trying to read it
2025-01-07 16:52:20 <ikke> mps: what if you try some kind of qr-code scanner?
2025-01-07 16:52:32 <panekj> I would recommend using just the text code to add otp
2025-01-07 16:52:33 <mps> qrcode image is in firefox window
2025-01-07 16:53:23 <mps> same phone quite fine read qrcodes in telegram
2025-01-07 16:53:35 <mps> and one from DigiCert
2025-01-07 16:54:16 <mps> ikke: iiuc this will be useful only to test if qr-code is ok?
2025-01-07 16:55:30 <mps> anyway, what iggy says looks like it is a lot easier to use command line tools than these on android
2025-01-07 19:38:34 <valerius> I switched from lineageOS to GrapheneOS
2025-01-07 19:38:40 <valerius> I think I got Aegis from F-Droid
2025-01-07 19:45:03 <mps> 
ACTION wants to throw away all android devices

2025-01-07 19:45:45 <valerius> GrapheneOS is realistically the best option these days, unless you want to sacrifice basic functionality to use a niche platform
2025-01-07 19:46:03 <valerius> it at least makes me feel like I'm the one in control of the device for the first time ever in mobile devices
2025-01-08 04:10:03 <sms> Hi, does anyone have any experience with alpine on the star64 by pine64?
2025-01-08 04:10:46 <sms> I'm trying to build a wifi driver currently and was wondering if anyone had some advice
2025-01-08 07:18:01 <ncopa> looks like it is StarFive JH7110, so it should boot at least?
2025-01-08 07:18:52 <ncopa> do you know which wifi driver you need?
2025-01-08 09:05:10 <sms> yea it boots, i built an image with the script on this site: https://arvanta.net/alpine/alpine-on-visionfive/
2025-01-08 09:06:36 <sms> i found a driver on github, problem is i get the following error while compiling it: https://github.com/morrownr/rtl8852bu-20240418/issues/5
2025-01-08 09:07:05 <sms> perhaps i'm missing a library or something else necessary to build it
2025-01-08 09:10:59 <mps> sms: on which distro you build it
2025-01-08 09:13:12 <mps> I thought that wifi driver for star64 is in mainline kernel
2025-01-08 09:33:31 <sms> mps i built it on alpine, on the same board i installed it to
2025-01-08 09:34:05 <sms> is it? i tried adding linux-firmware to the image but it didn't recognize the card
2025-01-08 09:36:40 <mps> sms: I'm not sure it is in mainline, I just thought it is but I don't know for sure
2025-01-08 09:39:14 <sms> i dont think so, given the github project i linked is still a wip
2025-01-08 09:40:22 <mps> could you try to boot with linux-lts
2025-01-08 09:41:04 <mps> or linux-edge
2025-01-08 10:10:42 <mps> here is my Makefile for build out-of-tree modules https://tpaste.us/VYpv
2025-01-08 10:11:04 <mps> ofc, you can (and maybe should) replace clang with gcc
2025-01-08 10:12:44 <mps> this example is when I built my mpschar module
2025-01-08 13:12:41 <ncopa> it is probably lts.riscv64.config:CONFIG_TRIM_UNUSED_KSYMS=y
2025-01-08 13:13:36 <ncopa> yeah almost sure that is the issue
2025-01-08 13:14:24 <ncopa> it will fail on edge kernel as well
2025-01-08 13:15:01 <ncopa> $ grep UNUSED_KSYM * | tpaste
2025-01-08 13:15:01 <ncopa> https://tpaste.us/mepg
2025-01-08 13:30:43 <mps> nice, now have to fix this also on aarch64 and x86_64 in linux-edge
2025-01-08 13:31:01 <mps> and armv7
2025-01-08 13:38:46 <mps> u-boot 2025.01 pushed to builders
2025-01-08 13:39:47 <mps> it was one of easiest release to upgrade
2025-01-08 23:40:27 <sms> mps it seems linux-lts and linux-edge don't have the DTB's needed to boot on the star64, so i can't boot with just those packages
2025-01-08 23:41:39 <sms> unless i should manually include the DTB's alongside the linux-lts kernel, but that requires building the kernel myself correct?
2025-01-08 23:42:26 <sms> ncopa nice, that could be it. how do i turn that option off?
2025-01-09 06:52:26 <sms> mps nvm it does
2025-01-09 07:28:18 <mps> sms: iiuc linux-lts and linux-edge boots on star64 at the end?
2025-01-09 07:29:40 <ncopa> sms: im on it
2025-01-09 07:29:41 <mps> sms: to turn of ksyms clean from kernel and modules you have disable these options in kernel config and rebuild kernel and install it
2025-01-09 07:31:23 <mps> maybe time linux-{lts,edge}-dbg :)
2025-01-09 07:31:32 <mps> time for*
2025-01-09 07:32:42 <ncopa> star64 is JH7110 so I expect 6.12 kernel boots there
2025-01-09 07:33:21 <mps> yes, because this I told sms to try boot with lts and edge
2025-01-09 07:34:20 <mps> only don't know how mainline u-boot works on this SBC
2025-01-09 07:35:50 <sms> mps i was confused for a second on how to boot it, i think i got it now, i'll let u know if it works
2025-01-09 07:37:57 <mps> sms: if it can't find dtb in fdtdir you can set 'fdt $path to required dtb' in extlinux.conf
2025-01-09 07:39:51 <sms> i still would need to flash u-boot.itb and u-boot-spl.bin.normal.out from the u-boot-starfive package unto the sd card correct?
2025-01-09 07:40:20 <sms> i made a label for lts kernel on extlinux.conf
2025-01-09 07:42:30 <mps> we didn't enabled u-boot for star64
2025-01-09 07:42:47 <mps> we is me
2025-01-09 07:42:55 <mps> but no one else afaik
2025-01-09 07:44:04 <mps> probably you don't have to install new u-boot on board, just set path to dtb in 'fdt' directive in extlinux.conf
2025-01-09 07:44:41 <mps> u-boot-starfive is tested only on visionfive V2
2025-01-09 07:47:12 <mps> I see this 'board: support Star64 board' in u-boot git log. So probably we can enable it
2025-01-09 07:47:32 <mps> sms: could you post me official url for this SBC
2025-01-09 07:48:30 <mps> I will be AFK for some time, and later today I will look if we can add this SBC to our u-boot
2025-01-09 07:52:01 <mps> sms: nvm, I found url
2025-01-09 07:55:34 <sms> sorry for not responding. nice
2025-01-09 07:56:25 <sms> mps i've been using u-boot-starfive to boot on the star64, and it works
2025-01-09 07:57:01 <sms> i thought it made sense since its the same cpu as well. the board's spi comes with those dtbs as well i'm pretty sure
2025-01-09 07:57:12 <mps> looking u-boot source it could be that this SBC could work with visionfive V2 u-boot
2025-01-09 07:57:46 <mps> sms: ah nice, you just confirmed my guess
2025-01-09 07:58:16 <mps> so we can add in docs this
2025-01-09 07:58:27 <mps> BBL
2025-01-09 07:58:38 <sms> also tested linux-lts, it boots
2025-01-09 07:59:17 <sms> that grep UNUSED_KSYMS that ncopa did, where do i run that to see if the option is enabled?
2025-01-09 08:27:48 <sms> linux-edge also boots mps
2025-01-09 08:36:29 <mps> sms: it is in alpine aports tree
2025-01-09 08:37:52 <mps> sms: nice and thanks for info. maybe you can write some short notes/guide how to boot alpine on this SBC.
2025-01-09 08:38:39 <mps> would be nice to add this notes to https://arvanta.net/alpine/alpine-on-visionfive/
2025-01-09 08:54:35 <sms> sure
2025-01-09 11:39:33 <mps> sms: maybe you could build akms aport for rtl8852bu device
2025-01-09 12:44:56 <mps> ok, I've found reason why my BPI F3 sometimes hungs on boot from nvme with kernel 6.13-rc1. for unknown reason (at least for me) it doesn't initialize nvme successfully or it doesn't load nvme modules
2025-01-09 12:45:32 <mps> building kernel with nvne modules as =y it never hungs
2025-01-09 12:46:07 <mps> could be flaky nvme device or driver is not yet stable
2025-01-09 18:58:35 <mps> I narrowed problem with boot hungs. It is nlplug-findfs problem
2025-01-09 18:59:07 <mps> here is what appears on console https://tpaste.us/Eb4D
2025-01-09 18:59:25 <mps> but nvme driver is in-kernel
2025-01-09 19:02:16 <mps> ncopa: ^ do you have any idea
2025-01-09 20:53:32 <sms> mps might you hv a guide on hand for building a port? i'm a little new xd
2025-01-09 20:55:18 <mps> sms: this is old but still could be usable https://wiki.alpinelinux.org/wiki/Developer_Documentation
2025-01-09 20:55:52 <mps> i.e. to setup alpine development environment and use it
2025-01-09 20:56:32 <ncopa> looks like kernel goes boom after nlplug-findfs fails to write
2025-01-09 20:56:43 <ncopa> its definitively a kernel problem
2025-01-09 20:56:49 <ncopa> nlplug-finds loads kernel modules
2025-01-09 20:57:02 <ncopa> and writes output (logs etc)
2025-01-09 20:58:50 <mps> sms: if you want to skip and go straight to work (like me) then https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package
2025-01-09 20:59:18 <sms> thanks mps!
2025-01-09 20:59:52 <mps> ncopa: btw, linux-spacemit doesn't have this problem
2025-01-09 21:02:36 <mps> what makes me 'angry' is that I can't reproduce problem in controlled way. sometimes it hangs sometimes doesn't
2025-01-09 21:03:09 <mps> anyway, will continue to find what is culprit
2025-01-09 22:18:44 <sms> wierd, driver now compiles and installs fine, but i still can't see the wlan interface
2025-01-09 22:20:22 <sms> am i missing something?
2025-01-09 22:23:13 <mps> sms: modprobe?
2025-01-09 22:23:23 <mps> sorry for stuppid answer
2025-01-09 22:24:48 <sms> perhaps, the install script that the driver maintainer made doesn't have a modprobe command in it
2025-01-09 22:24:53 <sms> it does have depmod
2025-01-09 22:25:59 <mps> manually `modprobe /path/to/module`
2025-01-09 22:26:20 <sms> ok
2025-01-09 22:26:37 <sms> also i'm not using dkms for this atm, if it matters
2025-01-09 22:26:51 <mps> I understand
2025-01-09 22:27:42 <mps> you can manually copy module to /lib/modules/$KVER/kernel/...' where you want
2025-01-09 22:27:52 <mps> and then run depmod
2025-01-09 22:30:39 <mps> last option is `insmod $module_filename' in dir where is module
2025-01-10 04:34:10 <sms> so, i ran modprobe and the dmesg told me that it loaded, despite "module verification failed: signature and/or required key missing"
2025-01-10 04:34:26 <sms> however, no wlan0, nor any new interface
2025-01-10 04:34:35 <sms> after running ip a
2025-01-10 04:42:12 <sms> lsmod says its loaded too
2025-01-10 07:56:16 <mps> sms: with which kernel you built module?
2025-01-10 07:56:54 <mps> CONFIG_MODULE_SIG should be disabled in this kernel
2025-01-10 07:58:01 <mps> also module shouldn't be striped after build
2025-01-10 07:58:20 <clandmeter> mps:  did you try debug_init?
2025-01-10 07:58:47 <mps> clandmeter: question is to me?
2025-01-10 07:59:10 <clandmeter> i think so
2025-01-10 07:59:26 <mps> aha, what is debug_init
2025-01-10 07:59:37 <clandmeter> cmdline option
2025-01-10 07:59:53 <clandmeter> gives debug info about nlplug-findfs
2025-01-10 07:59:56 <mps> it is added to alpine initramfs?
2025-01-10 08:00:25 <clandmeter> add it to your kernel cmdline 
2025-01-10 08:00:29 <mps> tbh didn't knew it exists
2025-01-10 08:00:36 <clandmeter> RTFS ;-)
2025-01-10 08:01:28 <clandmeter> https://git.alpinelinux.org/mkinitfs/tree/initramfs-init.in#n487
2025-01-10 08:01:35 <mps> will look later when I boot board
2025-01-10 08:02:17 <mps> hah, every day I learn something surprising :)
2025-01-10 08:02:35 <mps> clandmeter: thanks for hint
2025-01-10 08:02:50 <clandmeter> yw
2025-01-10 08:03:01 <clandmeter> maybe it helps debugging the issue
2025-01-10 08:03:27 <mps> anyway, when booted board is quite stable even with kernel 6.13-rc1
2025-01-10 11:36:04 <mps> clandmeter: with debug_init it hangs rarely, about once in 15 reboots
2025-01-10 13:13:10 <ncopa> mps: i believe it is a race that happens when nlplug-findfs loads the modules
2025-01-10 13:14:18 <mps> ncopa: nvme drivers are built in kernel, and also used FS drivers
2025-01-10 13:15:31 <mps> now I build https://github.com/jmontleon/linux-bianbu/commits/linux-6.6.y/ kernel and will test with it
2025-01-10 14:07:06 <sms> i did it for 6.12.9-0-lts mps
2025-01-10 14:11:58 <sms> also for akms it looks like i need a user called akms, didn't find that in the manpages
2025-01-10 14:14:37 <mps> you have to disable CONFIG_TRIM_UNUSED_KSYMS in kernel and rebuild it
2025-01-10 14:16:52 <mps> for akms I'm not sure. you can look at some examples in aports
2025-01-10 14:34:28 <ncopa> f0ae82f0e1337a252070e267c374eb3e7a25c3e2
2025-01-10 14:34:46 <ncopa> thats included in the 6.12.9 kernel
2025-01-10 14:43:45 <sms> yea i was gonna say. btw thanks ncopa!
2025-01-10 14:45:20 <sms> also another funny thing, with akms if i make an AKMBUILD like the example, the build() will only do the MODPOST on Module.symvers, but if i leave build() with just make -j4 it does what it needs to xd
2025-01-10 15:00:44 <sms> also got a working AKMBUILD
2025-01-10 15:01:05 <sms> same problem though
2025-01-10 15:51:14 <mps> sms: you can look example here https://git.alpinelinux.org/aports/tree/testing/rtl8821ce-src/APKBUILD
2025-01-10 18:13:23 <sms> thanks mps
2025-01-23 08:52:01 <sms> hey mps, sorry for not talking for so long xd, been doin stuff
2025-01-23 08:53:09 <sms> would you or someone else know why a wifi card might not be showing up in dmesg?
2025-01-23 08:53:40 <sms> i'm a little scared its broken and that's why even with the correct module no interface is being brough up
2025-01-23 09:01:34 <mps> sms: sorry, i had 'injury' and i will not be able to work much for alpine in the near future
2025-01-23 09:03:33 <sms> oh jeez
2025-01-23 09:03:36 <sms> are you alright?
2025-01-23 09:07:46 <mps> well, yes and no. i am no as well as was 15 days ago, but i am on therapy and i hope i will be better
2025-01-23 09:08:52 <mps> good sign is that i am not in hospital
2025-01-23 09:14:32 <sms> glad ur still here, sounds tough man
2025-01-23 09:18:29 <mps> no worries, i'm improving every day though in 'small steps'. i hope i will improve enough to work normally
2025-01-23 09:19:47 <mps> typing with only left hand is very very hard and error prone
2025-01-23 09:20:42 <mps> and slow, ofc
2025-01-23 09:22:01 <sms> wow, i bet
2025-01-23 09:24:23 <sms> now i'm curious lol, not to pry
2025-01-23 09:28:29 <mps> what you mean by "not to pry"
2025-01-23 09:30:59 <sms> i dont know if its too personal too ask
2025-01-23 09:31:26 <sms> what happened
2025-01-23 09:31:37 <mps> ah
2025-01-23 09:32:32 <mps> rather would not about that in public
2025-01-23 09:34:13 <mps> 'medical issue' maybe is  enough
2025-01-23 09:34:39 <sms> i see
2025-01-23 09:35:16 <sms> godspeed man, hope u get better
2025-01-23 09:35:39 <mps> thank you
2025-01-23 09:48:05 <ikke> mps: I hope you'll recover soon! Glad to hear you're no longer in a hospital 
2025-01-23 09:49:24 <mps> ikke: thank you
2025-01-23 11:01:23 <clandmeter> mps: o/
2025-01-23 11:39:56 <mps> clandmeter: \o
2025-01-23 16:22:23 <mio> mps: sorry to hear of your injury, wishing you a quick and full recovery!
2025-01-23 16:25:44 <mps> mio: thank you
2025-01-23 17:44:36 <iggy> sms: did you try the relevant lsusb/lspci util to see if it shows up at all?
2025-01-23 18:04:09 <sms> iggy yes
2025-01-23 18:04:45 <sms> lsusb gives me an error and shows no devices, while lspci shows 1 device that sounds nothing like a network card
2025-01-23 18:39:54 <sms> uboot doesn't seem to catch it either, only the two ethernet NICs
2025-01-23 18:40:49 <sms> lsusb gives me "unable to initialize usb specunable to initialize libusb: -99"
2025-01-23 18:41:07 <sms> lspci "0001:00:00.0 PCI bridge: PLDA XpressRich-AXI Ref Design (rev 02)"
2025-01-23 18:43:22 <ikke> sms: anything in dmesg output?
2025-01-23 18:50:15 <sms> nothing with "wireless" or "wlan" or similar
2025-01-23 18:50:35 <sms> no realtek either
2025-01-23 18:53:50 <sms> full dmesg: https://tpaste.us/ZKd9 
2025-01-23 20:23:29 <iggy> how is the device physically connected? m.2? usb? pci slot? token ring?
2025-01-23 20:24:02 <sms> its onboard
2025-01-23 20:24:57 <sms> has two little antenas that connect to the board
2025-01-23 20:26:47 <iggy> ohhhh, suppose that could just be something with the dtb? The datasheet says it's USB
2025-01-23 20:28:43 <iggy> "The USB over-current protection is not wired up correctly to the USB ports on Star64. The default Starfive Kernel will disable USB on boot as it belives the ports are overcurrent. This ugly hack works around it" from the wiki
2025-01-23 20:50:15 <sms> could very well be yea
2025-01-23 20:52:13 <sms> i am using the lts kernel however, would that also disable the USB ports?
2025-01-25 10:03:24 <mps> algitbot: retry master
2025-01-25 11:44:59 <mps> algitbot: retry master
2025-01-25 12:08:42 <mps> algitbot: retry master
2025-01-28 08:16:10 <mps> arm dev lxcs are inaccessible
2025-01-28 08:35:24 <clandmeter> i think ikke mention osmething yesterday
2025-01-28 08:35:28 <clandmeter> mtu issue or related
2025-01-28 08:40:50 <mps> ok
2025-01-28 08:48:37 <ikke> The prefix has changed 
2025-01-28 08:49:16 <clandmeter> does it matter for dmvpn?
2025-01-28 08:59:00 <ikke> No, but I think mps connects via public ipv6?
2025-01-28 08:59:48 <mps> ikke: no. i use only ipv4
2025-01-28 09:01:12 <ikke> Ok, may have to do with the changes I made this morning then
2025-01-28 09:01:50 <ikke> (to deal with routing issues)
2025-01-28 12:14:49 <ikke> mps: can you check if you can access them again?
2025-01-28 13:27:59 <cely> I can access my aarch64 dev lxc
2025-01-28 14:14:20 <mps> ikke: now i can access it. thanks
2025-01-29 19:22:21 <mps> will the linux-stabe MR be accepted? in that case linux-edge should be removed
2025-01-29 19:22:50 <mps> ncopa: clandmeter: ikke: ^
2025-01-29 19:23:30 <ikke> You don't have a use for the different configuration that -edge has now?
2025-01-29 19:23:50 <ikke> Because that's the main reason people want another kernel, to have config that matches lts
2025-01-29 19:25:10 <mps> i am for removal of linux-edge and 'ok' with merge linux-stable
2025-01-29 19:25:57 <ikke> ok
2025-01-29 19:26:45 <mps> we don't need linux-edge if we have linux-stable
2025-01-29 19:27:45 <mps> ikke: make me a help and remove it
2025-01-29 19:28:14 <mps> also from 3.21-stable
2025-01-29 19:28:26 <ikke> mps: there are people using it, so we should at least make sure they will get -stable
2025-01-29 19:29:08 <mps> replaces in linux-stable?
2025-01-29 19:29:13 <ikke> provides
2025-01-29 19:29:20 <ikke> replaces is only necessary if files overlap
2025-01-29 19:29:21 <mps> ah yes
2025-01-29 19:29:33 <ikke> But what about bootloader config?
2025-01-29 19:30:19 <mps> bootloader? users should fix this?
2025-01-29 19:30:54 <mps> i don't have better idea
2025-01-29 19:41:11 <clandmeter> hi
2025-01-29 19:41:49 <clandmeter> mps: is it your pref to stop supporting linux-edge?
2025-01-29 19:43:45 <mps> clandmeter: yes, i think it doesn't make sense if we have another pkg with same version
2025-01-29 19:44:01 <clandmeter> i dont refer to linux-stable
2025-01-29 19:44:21 <clandmeter> i want your opinion excluding the stable idea
2025-01-29 19:46:24 <mps> though i don't see sense to have linux-stable which will be same config as linux-lts, but newcomers want strange things in alpine. and i will not argue about yhis
2025-01-29 19:47:01 <clandmeter> i said excluding the stable discussion :)
2025-01-29 19:47:12 <mps> this*
2025-01-29 19:48:02 <mps> stable is nonsense. so lts is not stable :)
2025-01-29 19:48:33 <clandmeter> im not talking about stable
2025-01-29 19:50:14 <fossdd[m]> mps: wait what are you talking about? please dont talk about me like that
2025-01-29 19:50:38 <fossdd[m]> this is really unfriendl
2025-01-29 19:51:18 <mps> fossdd[m]: i don't tell anything bad about you
2025-01-29 19:51:27 <clandmeter> fossdd[m]: can we be less sensitive please? 
2025-01-29 19:52:21 <mps> i respect your effort though i don't agree with idea about linux-stable
2025-01-29 19:53:09 <clandmeter> i think fossdd[m] means the newcomers statement, i think thats kind of misplaced.
2025-01-29 19:53:26 <mps> ah ok
2025-01-29 19:53:33 <clandmeter> although you are probably longer with the project, it does not need to be highlighted. 
2025-01-29 19:53:50 <clandmeter> lets just keep an open mind and open discussion.
2025-01-29 19:53:51 <mps> ofc
2025-01-29 19:54:01 <mps> i agree
2025-01-29 19:54:47 <fossdd[m]> yes sure
2025-01-29 19:55:11 <fossdd[m]> i know that there are different standpoints about this issue, but i think there is a good reasoning about a kernel following stable releases
2025-01-29 19:56:17 <mps> to repeat, i will not be against merge of linux-stable and have nothing bad to say against fossdd[m] 
2025-01-29 19:56:35 <fossdd[m]> alright :)
2025-01-29 19:57:45 <mps> and if linux-stable is merged i don't see reasons to keep linux-edge
2025-01-29 19:57:49 <clandmeter> fossdd[m]: i do think that disagreeing on one or more kernel config options should introduce a new kernel
2025-01-29 19:58:02 <clandmeter> should not*
2025-01-29 20:00:03 <ikke> clandmeter: I think the desire here is to have a kernel with similar config as lts, but follows the latest stable kernel, allowing someone to seemlessly switch between the 2
2025-01-29 20:00:16 <fossdd[m]> clandmeter: agreed, but currently both configs are a completely different
2025-01-29 20:00:19 <fossdd[m]> ikke: yes
2025-01-29 20:00:33 <clandmeter> ikke: this is not what i read in the issue which is linked 
2025-01-29 20:00:35 <mps> clandmeter: i stopped to use linux-edge on all machines except in loongarh64 and visionfive V2, so it is not important to me
2025-01-29 20:00:56 <clandmeter> mps: has nothing to do with you
2025-01-29 20:01:13 <ikke> "Kernel aport with an identical config of main/linux-lts following stable
2025-01-29 20:01:15 <ikke> kernel releases."
2025-01-29 20:01:15 <Ariadne> tbh i think linux-stable which matches up with linux-lts would be good for alpine
2025-01-29 20:01:52 <clandmeter> i read the issue, and after the the discussion about options missing in linux-edge it was suggested to start linux-stable
2025-01-29 20:02:15 <clandmeter> i have nothing against the idea of a specific kernel, just the reasoning behind it.
2025-01-29 20:02:23 <fossdd[m]> i had the idea earlier and it was not because of the single issue
2025-01-29 20:02:36 <ikke> Yeah, this is something that has been playing for quite some time
2025-01-29 20:02:47 <ikke> came up multiple times
2025-01-29 20:02:52 <clandmeter> we want to prevent kernels poping up on every config discussion
2025-01-29 20:02:56 <fossdd[m]> as far as i understood it -edge was for experimentation and not for stable usecases
2025-01-29 20:02:58 <Ariadne> i have switched from linux-lts to linux-edge before and found myself surprised by the differences
2025-01-29 20:03:04 <Ariadne> on several occasions
2025-01-29 20:03:22 <clandmeter> if you dont like kernel differences do not use lts
2025-01-29 20:03:31 <clandmeter> each arch has lots of differences
2025-01-29 20:03:43 <clandmeter> i found this out while playing with qemu
2025-01-29 20:03:48 <clandmeter> and hit my head
2025-01-29 20:05:08 <Ariadne> well, that's the other side of it.  we need to move to something more like linux-rpi's config style where we just store deviations from defconfig
2025-01-29 20:05:15 <Ariadne> that would fix most of that
2025-01-29 20:05:22 <clandmeter> yup
2025-01-29 20:05:22 <ikke> Ariadne: aren't we already?
2025-01-29 20:05:30 <clandmeter> not for lts afaik
2025-01-29 20:05:42 <Ariadne> not in lts, its still full configs there
2025-01-29 20:05:46 <fossdd[m]> lts already uses defconfig, edge is currently not
2025-01-29 20:05:53 <Ariadne> since when o.O
2025-01-29 20:06:00 <fossdd[m]> see also https://gitlab.alpinelinux.org/alpine/aports/-/issues/12933
2025-01-29 20:06:11 <mps> long ago
2025-01-29 20:06:46 <clandmeter> just see the sheer size differences between the arches
2025-01-29 20:06:54 <clandmeter> thats not just arch differences 
2025-01-29 20:07:36 <ikke> f2d708907ba2fccc8b499c588f713b47d5cba2ed
2025-01-29 20:07:38 <ikke> 2022
2025-01-29 20:08:35 <fossdd[m]> clandmeter: but i think that is a different problem (which we should take a look at at some point)
2025-01-29 20:09:22 <clandmeter> sure, im just trying to reason the reasoning. 
2025-01-29 20:09:47 <clandmeter> most important is that the maintainer in question is up for it
2025-01-29 20:16:03 <mps> i'm ok with what you decide, just think linux-edge does not needed if linux-stable is merged