2024-07-03 16:56:47 <ikke> mps: I didn't have time for it lately, but I should look at updating both of my rv boards
2024-07-03 16:59:46 <mps> ikke: also I didn't have much free time for starfive in last few months
2024-07-03 17:00:26 <ikke> what was the status of the rv1 board again? I remember the kernel not being suitable for it anymore
2024-07-03 17:00:31 <mps> anyway, kernel is upgraded to  6.8.9 and u-boot to 2024.04
2024-07-03 17:00:33 <ikke> I still have it pinned
2024-07-03 17:01:41 <mps> I plan to use some rc kernel with Emil Renner patches for VF1 but still didn't, have some private obligation to do
2024-07-03 17:02:02 <ikke> yeah, no worry
2024-07-03 17:04:15 <mps> ikke: I have linux-vf1-6.10_rc1-r0.apk for VF1 locally or you can find it in my riscv lxc
2024-07-03 17:04:39 <ikke> I still have it installed and pinned, so I'm good
2024-07-03 17:04:55 <mps> which version you have
2024-07-03 17:37:23 <ikke> I can't access it atm, will have to check later
2024-07-03 17:39:49 <mps> ikke: https://dev.alpinelinux.org/~mps/riscv64/linux-vf1-6.10_rc1-r0.apk just uploaded
2024-07-03 17:39:59 <ikke> mps: alright, thanks
2024-07-04 16:00:06 <ikke> mps: I have linux-starfive-6.2_rc7-r0 now
2024-07-04 16:00:27 <mps> ikke: on VF1?
2024-07-04 16:00:31 <ikke> yes
2024-07-04 16:00:52 <mps> I think this one I posted last night is safe to use
2024-07-04 16:01:37 <mps> now I'm working on u-boot upgrade and will check VF1 later in evening
2024-07-04 16:18:06 <ikke> mps: I don't need to update anything else or change some config for that kernel to work?
2024-07-04 16:30:24 <mps> ikke: I think so
2024-07-04 16:31:29 <ikke> ok, I'll try it
2024-07-04 18:02:14 <mps> ikke: uname -a shows Linux vf 6.10.0-rc1-0-vf1 #1-Alpine SMP PREEMPT Wed, 29 May 2024 19:24:52 +0000 riscv64 GNU/Linux
2024-07-04 18:03:29 <mps> but you have to add or change extlinux.conf with vmlinuz-vf1 and initramfs-vf1, and fdt /dtbs-vf1/starfive/jh7100-starfive-visionfive-v1.dtb
2024-07-04 18:04:57 <ikke> yes, I suspected that would be the case
2024-07-04 18:05:02 <ikke> I upgraded the kernel, but did not reboot yet
2024-07-04 18:12:09 <mps> looks like u-boot for VF1 could be upgraded to some newest git changes
2024-07-04 18:13:14 <ikke> Ok, my board booted with the new kernel :)
2024-07-04 18:13:32 <ikke> Thank you
2024-07-04 18:34:41 <mps> you are welcome
2024-07-04 19:00:33 <mps> hm, pioneer nvme is quite unstable
2024-07-04 19:04:29 <ikke> Yes, clandmeter already mentioned that a couple of times
2024-07-05 07:25:21 <clandmeter> i can try to upgrade one to samsung
2024-07-05 07:25:27 <clandmeter> see if it makes a difference
2024-07-05 07:31:11 <mps> clandmeter: not sure will it help but I have samsung nvme on VF2 and it is stable, last uptime was more than 100 days and it reboot because of power electricity break
2024-07-05 08:45:00 <ikke> mps: same for me
2024-07-09 21:50:15 <jahway603[m]> Which RISC V boards are people running Alpine on today?
2024-07-09 21:51:39 <ikke>  I have a Vision Five 2 board 
2024-07-09 22:32:52 <iggy> I have vf2 and lichee pi 4a
2024-07-09 23:13:38 <valerius> vf2
2024-07-10 12:12:40 <ncopa> i have vf2
2024-07-21 17:30:57 <fossdd> im excited about the milkv oasis. looks like a cheap decent computer that doesnt run like a potato
2024-07-22 00:09:21 <iggy> it'll be nice to finally have decent hardware with hypervisor extension (I think the spacemit chip does, but I've yet to see one of those available with more than 4G ram)
2024-07-22 03:02:41 <jahway603[m]> <fossdd> "im excited about the milkv oasis..." <- That milk-v oasis board does look very nice
2024-07-23 13:39:35 <mps> PCI for visionfive is merged in 6.11 kernel. So, in two months linux-edge should work on board
2024-07-23 13:40:34 <mps> V2 I meant to say
2024-07-23 13:48:30 <fossdd> thats nice
2024-07-23 13:49:04 <valerius> que bien
2024-07-23 13:53:25 <mps> anyway, I think to upgrade linux-starfive to 6.10 with patches
2024-07-23 14:02:13 <valerius> a wonderful idea if you ask me
2024-07-23 14:04:54 <mps> valerius: will try
2024-07-23 14:18:00 <valerius> I made sure all of my projects work on RISC-V a few months ago, only one needed changes
2024-07-23 15:05:23 <mps> valerius: very nice to hear
2024-07-23 18:20:00 <mps> https://dev.alpinelinux.org/~mps/riscv64/linux-starfive-6.10.0-r0.apk if anyone is brave enough to upgrade and test it on VF2
2024-07-27 13:48:46 <mps> did anyone tried kernel https://dev.alpinelinux.org/~mps/riscv64/linux-starfive-6.2.10-r0.apk on VF2 
2024-07-27 13:48:54 <mps> uh
2024-07-27 13:49:22 <mps> this one I meant to say https://dev.alpinelinux.org/~mps/riscv64/linux-starfive-6.10.0-r0.apk
2024-07-27 13:57:41 <ikke> I did not have time yet, sorry
2024-07-27 13:58:16 <mps> ikke: no worries, we are not in hurry
2024-07-27 13:58:42 <mps> I think I will be able to test it tomorrow
2024-07-28 09:44:53 <clandmeter> https://www.phoronix.com/news/Linux-6.11-RISC-V-ACPI-NUMA
2024-07-28 10:33:51 <mps> do you think that 6.11-rc1 will work on pioneer
2024-07-28 11:10:18 <clandmeter> There is a branch at sopgo 
2024-07-28 11:10:28 <clandmeter> which I think has this
2024-07-29 16:52:11 <mps> should we somehow create something for alpine on this https://sites.google.com/riscv.org/devboards-program/library
2024-07-30 01:33:11 <iggy> do we have a wiki page for risc-v stuff? If not we should probably flesh that out first
2024-07-30 08:09:05 <mps> iggy: I would prefer something on doc.a.o or maybe on gitlab.a.o where we can use git
2024-07-30 08:09:29 <mps> docs.a.o
2024-07-30 15:14:21 <iggy> okay, I just noticed that most of the links on that page were to wiki's... I should have said general page somewhere
2024-07-30 15:16:13 <iggy> we do have https://wiki.alpinelinux.org/wiki/Riscv64 but it's just a single line that talks about the first release being 3.20
2024-07-30 15:18:15 <iggy> docs.a.o seems very focused on installing and running. There's not really a place there for general info
2024-07-30 15:19:04 <mps> iggy: it is okay what you told, didn't wanted to say anything bad to you
2024-07-30 15:19:12 <iggy> I suppose there could be a bit in the installing section about how to install for riscv
2024-07-30 15:20:09 <iggy> but most distros seem to keep their !amd64 docs all in a centralized location (including notes on installing there).
2024-07-30 15:20:31 <mps> we have on gitlab https://gitlab.alpinelinux.org/nmeum/alpine-visionfive/
2024-07-30 15:20:57 <mps> and my https://arvanta.net/alpine/alpine-on-visionfive/
2024-07-30 15:21:28 <mps> and iirc nmeum have something about sifive somewhere
2024-07-30 15:21:50 <iggy> those definitely seem focused on a single board
2024-07-30 15:22:02 <mps> maybe we could consolidate all these to generic alpine page for riscv
2024-07-30 15:22:11 <iggy> but where?
2024-07-30 15:22:32 <mps> gitlab.a.o imo
2024-07-30 15:22:56 <iggy> okay, but do we just do it under one of our accounts?
2024-07-30 15:23:01 <mps> for now this looks best option to me
2024-07-30 15:23:06 <iggy> do we set up a project?
2024-07-30 15:23:26 <mps> idk, ikke or someone else should tell
2024-07-30 15:24:15 <mps> 
ACTION would like to have git push access

2024-07-30 15:26:43 <iggy> yeah, I don't mind doing some work to collect info, consolidate different sources, make it more easily consumable, etc, but a little guidance/help on where to put it would be awesome
2024-07-30 15:27:39 <ikke> So a project for a wiki?
2024-07-30 15:29:12 <mps> does wiki support merge request and in markdown syntax
2024-07-30 15:29:23 <iggy> I got the sense that mps wanted to be able to maintain it via MR
2024-07-30 15:29:56 <mps> iggy: right, but not necesserally only mps
2024-07-30 15:30:18 <ikke> sadly it does not support MRs afaik
2024-07-30 15:30:40 <iggy> right, and I don't have any prefence, so go with what mps said
2024-07-30 15:30:58 <mps> I created my personal pages because I'm bad with wikis
2024-07-30 15:32:25 <mps> else all on https://arvanta.net/alpine/ be on wiki.a.o
2024-07-30 15:32:42 <mps> s/be/will be/
2024-07-30 15:32:52 <ikke> Using MRs is a good goal
2024-07-30 15:33:28 <ikke> Apparently there is a way to support an MR based workflow
2024-07-30 15:33:37 <ikke> It's just a bit more setup
2024-07-30 15:33:38 <mps> nice
2024-07-30 15:38:18 <iggy> does gitlab have anything like github's pages? That might allow a little more flexibility for formatting
2024-07-30 15:38:33 <ikke> it does, but it's a bit of work to setup
2024-07-30 15:39:12 <iggy> gotcha, something we could look at later if necessary
2024-07-30 15:39:48 <ikke> Not sure how complicated it is, but we could also setup something with hugo
2024-07-30 15:39:56 <mps> I don't care much about formatting (bells and whistles) 
2024-07-30 15:40:44 <mps> ikke: hugo looks as idea which will force me to learn more about it :-)
2024-07-30 15:41:16 <mps> for now I use zola
2024-07-31 03:05:13 <cely> This is very weird, both qbs and libqofono build fine in lxc (but had issues in the Docker CI, when that was tried)
2024-07-31 03:07:29 <cely> Well, i must remind myself that i'm using GCC 14 in lxc, but i think the chances of this making the difference is not that great, especially when other build tools used are still those from the repo
2024-07-31 07:58:10 <clandmeter> yes, i also noticed this behavior yesterday 
2024-07-31 07:59:11 <ikke> clandmeter: we also have issues with java in docker on rv64, presumably because of seccomp, maybe that's also causing these issues?
2024-07-31 07:59:24 <clandmeter> that is possible
2024-07-31 08:01:39 <clandmeter> ikke: anything against disabling it?
2024-07-31 08:02:43 <ikke> It would remove a lot of protections
2024-07-31 08:06:58 <clandmeter> ok but we can at least try it and see if it makes a difference
2024-07-31 08:08:18 <ikke> Sure
2024-07-31 08:11:51 <clandmeter> ikke: did you ever try to disable it on runner level? 
2024-07-31 08:19:10 <ikke> No
2024-07-31 08:19:37 <ikke> I've never tried to disable it to be honest 😅
2024-07-31 08:23:02 <clandmeter> cely: are you able to try now?
2024-07-31 08:23:07 <clandmeter> i have tried to disable it....
2024-07-31 08:23:46 <clandmeter> ikke: i added security_opt = ["seccomp:unconfined"] to both runners config
2024-07-31 08:24:42 <clandmeter> btw, it would be nicer to do a bind mount to the host for the config dir
2024-07-31 08:26:12 <mps> clandmeter: disabling seccomp is not big risk
2024-07-31 08:26:28 <mps> IMO, ofc
2024-07-31 08:40:10 <clandmeter> level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
2024-07-31 08:40:22 <clandmeter> so i guess docker is picking it up 
2024-07-31 09:00:21 <cely> I've restarted my 3.20 py3-qt6 CI job on riscv64, and the edge qbs upgrade CI job (though i think this one got picked up by a Scaleway runner)
2024-07-31 09:01:41 <clandmeter> cely: im also running the py3-qt6
2024-07-31 09:01:50 <clandmeter> i guess thats why its so frschaskc slow
2024-07-31 09:03:31 <clandmeter> nah, its qmake running single threaded 
2024-07-31 09:13:54 <clandmeter> the job is taking much longer than before
2024-07-31 09:14:01 <clandmeter> i guess thats good news
2024-07-31 09:14:09 <clandmeter> 🤞
2024-07-31 11:24:27 <clandmeter> \o/
2024-07-31 11:24:42 <clandmeter> https://gitlab.alpinelinux.org/alpine/aports/-/jobs/1469244
2024-07-31 11:24:56 <clandmeter> ikke: good catch!
2024-07-31 11:26:53 <clandmeter> cely: did yours also pass?
2024-07-31 11:30:13 <clandmeter> looks like it
2024-07-31 13:27:24 <cely> py3-qt6 passed
2024-07-31 13:27:55 <cely> but qbs on Scaleway didn't