00:38 <yang> Is the latest Rock 5B kernel still 5.10.110-rockchip-rk3588 (ii linux-image-legacy-rockchip-rk3588 23.02.2) in armbian/bookworm ? I tried to enable kernel defreeze in armbian-config and upgrade this kernel, but it doesn't seem there is another more recent kernel out yet?

16:02 <DC-IRC> [Discord] <nompyy> is there anyway to turn off linux apps sandbox

16:02 <DC-IRC> [Discord] <nompyy> so you could like be able to use your normal file app for linux sandboxes

17:17 <DC-IRC> [Discord] <Tonymac32> in what?

18:09 <DC-IRC> [OFTC] <mjt> what's the way to try a different kernel/initrd? I guess I should be configuring u-boot somehow?

18:10 <DC-IRC> [OFTC] <mjt> and I guess I also need a dtb?

18:11 <DC-IRC> [OFTC] <mjt> hmm. I installed bookworm kernel, and now /boot/Image points to armbian kernel but /boot/uInitrd points to debian initrd. This isn't going to work :)

18:31 <DC-IRC> [OFTC] <mjt> actually it will work since armbian kernel does not actually need initrd

18:40 <DC-IRC> [Discord] <viraniac> Not sure what board you are using and what you are seeing, but armbian uses UUID to identify root partition. That can't be resolved without initrd

18:41 <DC-IRC> [OFTC] <mjt> from my /boot/armbianEnv.txt: rootdev=/dev/mmcblk2p2

18:41 <DC-IRC> [OFTC] <mjt> even with uuid=, - initrd from different kernel will work, since no additional modules need to be loaded

18:42 <DC-IRC> [Discord] <viraniac> What board is this? And which image are you using?

18:43 <DC-IRC> [OFTC] <mjt> board is orangepi 3 lts, image is bookworm-based cli armbian, but it doesn't really matter

18:44 <DC-IRC> [Discord] <viraniac> This is not standard configuration. As official image only contains single partition and uses uuid. So I am guessing you have customizations on top

18:45 <DC-IRC> [OFTC] <mjt> single partition - no. when installing to emmc one has an option to choose different filesystem type, in which case there will be 2 partitions

18:45 <DC-IRC> [OFTC] <mjt> speaking of rootdev= - I edited it just an hour ago in order to simplify my testing

18:46 <DC-IRC> [Discord] <viraniac> ok.. Haven't tried that. I mostly use sdcard as I have to burn a lot of images for testing

18:47 <DC-IRC> [Discord] <c0rnelius77> mmcblk2? seems wrong for the 3lts.

18:47 <DC-IRC> [Discord] <viraniac> Thats emmc

18:47 <DC-IRC> [OFTC] <mjt> all modules needed for booting are built-in to the kernel, so it doesn't really *need* initrd

18:47 <DC-IRC> [Discord] <c0rnelius77> mine is blk1

18:47 <DC-IRC> [OFTC] <mjt> 3lts has mmcblk0 for sdcard and mmcblk2 for emmc

18:47 <DC-IRC> [OFTC] <mjt> at least this one, I dunno

18:47 <DC-IRC> [Discord] <viraniac> Whats ur kernel version?

18:48 <DC-IRC> [OFTC] <mjt> right now kernel is 6.1.63-current-sunxi64 (from armbian)

18:50 <DC-IRC> [Discord] <viraniac> ok, thats official kernel version of 23.11 image I believe

18:51 <DC-IRC> [OFTC] <mjt> I was about to test debian kernel and my initramfs but don't really know how to proceed yet. It seems I need a) dtb specific to kernel (why it is kernel-specific?), b) some tool to make Image & uInitrd from vmlinuz and initrd.img, and c) a way to switch images

18:51 <DC-IRC> [OFTC] <mjt> yes, it's official 23.11 image

18:51 <DC-IRC> [Discord] <viraniac> If you are going to install debian kernel, there will not be a dtb for orangepi 3 lTS

18:52 <DC-IRC> [Discord] <viraniac> orangepi 3 lts never got upstreamed

18:52 <DC-IRC> [Discord] <viraniac> still you can install linux-image-arm64 to install debian kernel. It will continue to use armbian's dtb

18:52 <DC-IRC> [OFTC] <mjt> I did that before (with bullseye image), -- iirc I just copied armbian dtb with the right name

18:53 <DC-IRC> [OFTC] <mjt> is dtb kernel-specific? I thought it is a description of hardware

18:53 <DC-IRC> [Discord] <viraniac> If you will use debian kernel, you will also lose ethernet, wifi and audio

18:54 <DC-IRC> [Discord] <viraniac> We have have patches that adds the driver for the same

18:54 <DC-IRC> [OFTC] <mjt> yeah, ethernet didn't work with bullseye kernel (haven't tried other)

18:54 <DC-IRC> [OFTC] <mjt> well, it worked but only at first boot after armbian kernel

18:55 <DC-IRC> [Discord] <viraniac> Dtb is as you said hardware description and is not kernel specific. But kernel source contains the source for the same from which dtb is generated

18:55 <DC-IRC> [OFTC] <mjt> (first boot: boot armbian kernel (ethernet works fine), reboot into bullseye kernel, - ethernet works. Reboot into bullseye kernel again, - ethernet doesnt' work anymroe)

18:56 <DC-IRC> [Discord] <tenkawa42> That's not 100% accurate... there are dts differences between kernel branches sometimes

18:56 <DC-IRC> [OFTC] <mjt> so I thought I'd give it another try with bookworm kernel. Apparently it wont work :)

18:56 <DC-IRC> [Discord] <tenkawa42> notably naming changes

18:56 <DC-IRC> [Discord] <viraniac> That doesn't sound right. 6.1 kernel doesn't have yt8531 drivers so you can't theoretically have ethernet working

18:57 <DC-IRC> [OFTC] <mjt> when I tried bullseye image, I wasn't able to find any info about all this. If I knew network doesn't work, I'd not even try :)

18:57 <DC-IRC> [Discord] <viraniac> yes, but if all drivers are there, same dts can work across different kernels regardless of what is there in that kernel specific dts

18:58 <DC-IRC> [OFTC] <mjt> why I tried debian kernel in the first place: I was thinking about a way to ugrade kernel in case a (security) issue is fixed

18:59 <DC-IRC> [OFTC] <mjt> again, without much info about this I just gave debian kernel a try

18:59 <DC-IRC> [Discord] <viraniac> If you need kind of rolling kernel updates, switch to beta.armbian.com in /etc/apt/sources.list.d/armbian.list

19:00 <DC-IRC> [Discord] <viraniac> If you use the beta repository, you will get upgraded to 6.6.8 kernel

19:00 <DC-IRC> [Discord] <viraniac> Thats the latest version for current kernel branch we have

19:01 <DC-IRC> [OFTC] <mjt> still not upstream/linus but with necessary armbian-specific changes?

19:01 <DC-IRC> [Discord] <viraniac> All armbian specific changes are there

19:02 <DC-IRC> [OFTC] <mjt> aha. 3lts never has been upstreamed. got it

19:02 <DC-IRC> [OFTC] <mjt> sure armbian changes are there :) I was thinking about if these changes are still *necessary*

19:02 <DC-IRC> [OFTC] <mjt> now I see

19:04 <DC-IRC> [Discord] <viraniac> With 6.6, ethernet driver is upstreamed, wifi is still not upstream and audio will also be missing upstream. Same for the Orange Pi 3 lTS dts, thats also missing upstream

19:04 <DC-IRC> [Discord] <viraniac> We have them all

19:07 <DC-IRC> [OFTC] <mjt> [ 10.717964] dwmac-sun8i 5020000.ethernet end0: Too many address, switching to promiscuous

19:07 <DC-IRC> [OFTC] <mjt> heh

19:12 <DC-IRC> [OFTC] <mjt> viraniac: re inaccurate description of ethernet vs bullseye kernel. This is from memory which is about an year old now. I might misremember something. It wasn't completely non-working, it was something funny

19:24 <DC-IRC> [OFTC] <mjt> is there a reason why orangepi-3-lts (or other boards) has never been upstreamed?

19:30 <DC-IRC> [Discord] <viraniac> Most of the times these boards are upstreamed by volunteers. So I guys no one volunteered to do the same

19:31 <DC-IRC> [OFTC] <mjt> since support is here in armbian, someone did implement it, which is 95% of work already.. but I see

19:33 <DC-IRC> [Discord] <viraniac> I did fixed a lot of issues. But I didn't went to upstream it. Even the fixes I made were just unpaid work. Then for upstreaming, it will be again dealing with review comments and sending revision that takes a lot of time which will again be unpaid work

19:34 <DC-IRC> [OFTC] <mjt> eh. all my work on debian, qemu, samba, ... is 100% unpaid :)

19:34 <DC-IRC> [OFTC] <mjt> not that I ask others to do the same ofcourse :)

21:01 <Death_Syn> I'm having a strange issue with podman AND docker on my Libre Computer Renegade. Running `Armbian 23.11.1 Bookworm with Linux 6.1.63-current-rockchip64`, the Debian packaged podman cannot resolve image repositories, and I just pulled in docker from the official docker repos, and it has the same problem. However, other tools like dig, curl and wget seem to be able to resolve these hosts

21:01 <Death_Syn> acceptably with the local resolver. Other hosts on the same network are able to do docker/podman with the resolver. What am I missing?

21:27 <Death_Syn> interesting, seems my local network resolver and it don't get along (it's whatever opnsense is using). Added Google's resolver behind it and suddenly docker works

21:36 <DC-IRC> [Discord] <k.s.bedford.jr> where is the best place to list a arm64 board with wifi /4glte/gps/120g nvme ?

21:36 <DC-IRC> [Discord] <k.s.bedford.jr> as I no longer need the unit bt would like to recoop the cost

21:37 <DC-IRC> [Discord] <k.s.bedford.jr> only had less then 100 hours on it

21:37 <DC-IRC> [Discord] <k.s.bedford.jr> naopct6

21:37 <DC-IRC> [Discord] <k.s.bedford.jr> nanopct6

21:38 <DC-IRC> [Discord] <k.s.bedford.jr> it has the aluminum case also

21:39 <DC-IRC> [Discord] <k.s.bedford.jr> I fugre someone here would want it before it goes to ebay

21:39 <DC-IRC> [Discord] <k.s.bedford.jr> it has the wifi module in it also

22:05 <DC-IRC> [Discord] <k.s.bedford.jr> next question how well is the allwinner d1 chip supported in armbian thus far

22:05 <DC-IRC> [Discord] <k.s.bedford.jr> ?

22:10 <yang> k.s.bedford.jr there is a section on the forum "marketplace"

22:11 <yang> I don't know about d1 specifically, but I have the Teres/Olimex laptop which is an allwiner sunxi and it's supported

22:33 <DC-IRC> [Discord] <viraniac> Not very well actually. 2 boards were added and then marked eos as they no longer builds.

22:33 <DC-IRC> [Discord] <k.s.bedford.jr> I dont see martket place

22:34 <DC-IRC> [Discord] <k.s.bedford.jr> ok

22:34 <DC-IRC> [Discord] <k.s.bedford.jr> well as I am getting a clockwork riscv unit I will have to learn

22:37 <DC-IRC> [Discord] <k.s.bedford.jr> Looks like they might have removed it

22:37 <DC-IRC> [Discord] <k.s.bedford.jr> as I made a login and logged in and see no area for marketplace