Bookworm upgrade availability soon ?

Started by stanlog, June 14, 2023, 12:17:03 PM

Previous topic - Next topic

stanlog

Hello,
I would like to know when you planned to upgrade your debian repository to use Bookworm as stable version ? I upgraded Olinuxino yesterday to Debian 12 without problem, upgrade Olimex repo to your "SID" repo. But I have already a very old kernel (5.10.105-olimex). I use this A64 board as a server, I don't know if I can use the official Debian kernel in replacement of yours without break anything :(

If somebody can tell me, it would be great.
Thanks.

LubOlimex

We plan to upgrade but we don't have a timeline. As soon as we test how it works and apply all fixes needed. Bookworm was released 4 days ago...

>  I use this A64 board as a server, I don't know if I can use the official Debian kernel in replacement of yours without break anything

Things will break, better stick with official images if you want to avoid trouble.
Technical support and documentation manager at Olimex

stanlog

Thank you for the answer, and for your products.

Quote from: LubOlimex on June 14, 2023, 01:27:39 PMWe plan to upgrade but we don't have a timeline. As soon as we test how it works and apply all fixes needed. Bookworm was released 4 days ago...

Yes but in freeze status for a while ;) Nevermind.

If someone has a cookbook to build this kernel and some other Olimex dedicated Debian packages (arm-trusted-firmware-oliuxino for example), maybe the community could help ? I really love Olimex products, and I want to buy and use European single boards computers as long I can. It's why softwares and drivers publishing regularity are really important in my point of view, to be honest.

LubOlimex

We have instructions at the end of the manual, all sources are also available at the GitHub.

Make sure to start from the Olimage manual:

https://github.com/OLIMEX/OLINUXINO/tree/master/DOCUMENTS/OLIMAGE
Technical support and documentation manager at Olimex

stanlog

Thank you,
I'm going to read this documentation.
Have a nice evening.

gregh

Quote from: LubOlimex on June 14, 2023, 01:27:39 PMWe plan to upgrade but we don't have a timeline. As soon as we test how it works and apply all fixes needed. Bookworm was released 4 days ago...

Can you give a rough estimate when the bookworm repo [1] for A20 Micro will be available?
Because if it is just a few weeks I will wait with my server upgrade and make 10 -> 11 -> 12 in one downtime. But if it will take months I will do  10->11 now and 11->12 seperate later.

[1] http://repository.olimex.com/dists/

mbosschaert

Maybe not the answer you were waiting for, but I installed debian bookworm on olinuxino-lime2 following the regular debian procedure which actually work very good. There is also a firmware file for the MICRO. Have not tested all possible hardware but so far it creates a perfect working basic debian system on which I was able to install homeassistant-supervised. For the debian installation I followed the instructions given in the README file in https://deb.debian.org/debian/dists/bookworm/main/installer-armhf/current/images/netboot/SD-card-images/

mossroy

Quote from: LubOlimex on June 14, 2023, 01:27:39 PMWe plan to upgrade but we don't have a timeline. As soon as we test how it works and apply all fixes needed.

@LubOlimex do you now have a timeline? Bookworm is the stable debian version since more than 10 months

mossroy

I have several A20 and A64 boards that are still running on Debian Buster.

As major debian upgrades are not officially supported by Olimex, I will have to reinstall them.

Debian Buster long-term support will end on June 30, 2024. Will the Bookworm image be available by this time? Or shortly after? It would save much time for me to skip Bullseye, and do only one reinstall instead of two.

BTW, supporting debian major upgrades (like on any regular debian) would be even better

mbosschaert

As for whom it may be relevant, now, halve a year after installing bookworm from scratch on a lime2 board, is is still rock-solid. Even better, homeassistant-supervised is stable and the regular updates install without any issues. If someone is interesed in the installation process for homeassistant, just drop me a personal message

mossroy

Quote from: mbosschaert on May 08, 2024, 01:34:41 PMAs for whom it may be relevant, now, halve a year after installing bookworm from scratch on a lime2 board, is is still rock-solid. Even better, homeassistant-supervised is stable and the regular updates install without any issues. If someone is interesed in the installation process for homeassistant, just drop me a personal message

You're certainly right on your device (A20-OLinuXino-LIME2?), and I would love to be able to use the regular debian installer as you do: much more installation options (like full-disk encryption), much more frequent kernel security updates etc

But stock debian is not working on the devices I have.
I have several A20-OLinuXino-MICRO, where I was happily using the regular debian until buster. But, since Bullseye, there are kernel panics that make it unsusable, see my blog post in 2022: https://blog.mossroy.fr/2022/03/31/upgrade-vers-bullseye-des-serveurs-olinuxino/

I also have several A64-OLinuXino-2Ge8G-IND, on which I never could install the regular debian.

I re-tested with debian bookworm in November 2023:
On A20-OLinuXino-MICRO board, the installation worked fine but, after logging in, and using the board a few minutes, there was this kernel panic:
[  855.175881] 8<--- cut here ---
[  855.179204] Unable to handle kernel paging request at virtual address fffffffe
[  855.186510] [fffffffe] *pgd=80000040207003, *pmd=6ffce003, *pte=00000000
[  855.193343] Internal error: Oops: 80000207 [#1] SMP ARM
[  855.198608] Modules linked in: binfmt_misc ecb des_generic aes_arm_bs crypto_simd cryptd sun4i_backend axp20x_battery axp20x_adc axp20x_ac_power lima axp20x_pek at24 gpu_sched drm_shmem_helper sun4i_codec snd_soc_core ftdi_sio sun4i_ts snd_pcm_dmaengine nvmem_sunxi_sid snd_pcm usbserial snd_timer snd soundcore sunxi_cedrus(C) sunxi_wdt v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common sun4i_drm_hdmi cec sun4i_ss videodev rc_core libdes mc display_connector leds_gpio cpufreq_dt evdev loop fuse dm_mod configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic axp20x_usb_power industrialio axp20x_regulator pinctrl_axp209 sunxi phy_generic ahci_sunxi dwmac_sunxi stmmac_platform stmmac pcs_xpcs phylink of_mdio fixed_phy fwnode_mdio libphy musb_hdrc libahci_platform libahci i2c_mv64xxx libata sun4i_lradc_keys ohci_platform scsi_mod ohci_hcd udc_core ehci_platform ehci_hcd scsi_common phy_sun4i_usb usbcore spi_sun4i sunxi_mmc sun4i_drm
[  855.199059]  sun4i_frontend sun4i_tcon sun8i_tcon_top drm_dma_helper drm_kms_helper drm
[  855.293448] CPU: 0 PID: 2719 Comm: dpkg-deb Tainted: G         C         6.1.0-12-armmp-lpae #1  Debian 6.1.52-1
[  855.303621] Hardware name: Allwinner sun7i (A20) Family
[  855.308843] PC is at 0xfffffffe
[  855.312001] LR is at free_pipe_info+0x90/0xc4
[  855.316375] pc : [<fffffffe>]    lr : [<c06f260c>]    psr: a0080033
[  855.322637] sp : f0d5def8  ip : 00000010  fp : b6e66368
[  855.327859] r10: 000000f8  r9 : 00000000  r8 : c87f1c38
[  855.333080] r7 : 00000000  r6 : 0000000e  r5 : 00000150  r4 : c3930800
[  855.339601] r3 : ffffffff  r2 : e08db1e0  r1 : c23eed38  r0 : c3930800
[  855.346124] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment user
[  855.353429] Control: 30c5387d  Table: 43ce01c0  DAC: fffffffd
[  855.359169] Register r0 information: slab kmalloc-cg-128 start c3930800 pointer offset 0 size 128
[  855.368065] Register r1 information: slab kmalloc-cg-512 start c23eec00 pointer offset 312 size 512
[  855.377122] Register r2 information: non-slab/vmalloc memory
[  855.382785] Register r3 information: non-paged memory
[  855.387837] Register r4 information: slab kmalloc-cg-128 start c3930800 pointer offset 0 size 128
[  855.396719] Register r5 information: non-paged memory
[  855.401770] Register r6 information: non-paged memory
[  855.406820] Register r7 information: NULL pointer
[  855.411523] Register r8 information: slab dentry start c87f1c38 pointer offset 0 size 36
[  855.419624] Register r9 information: NULL pointer
[  855.424327] Register r10 information: non-paged memory
[  855.429464] Register r11 information: non-paged memory
[  855.434600] Register r12 information: zero-size pointer
[  855.439823] Process dpkg-deb (pid: 2719, stack limit = 0x2b4da20b)
[  855.446008] Stack: (0xf0d5def8 to 0xf0d5e000)
[  855.450366] dee0:                                                       c3930800 c212b900
[  855.458539] df00: c358b440 c21d19d0 c87f1c38 c06f2760 c212b900 002c0002 c358b440 c06e8f00
[  855.466713] df20: c0450b80 c3aed500 c22bdcc0 000000f8 b6e66368 c93fa840 c26ea8f4 c26ea100
[  855.474886] df40: 00000824 f0d5df70 00000000 c046e1bc c26ea100 c39d5c00 c26ea920 c39d5c38
[  855.483058] df60: f0d5df70 c0450b94 f0d5dfb0 b6e90c04 c1612d98 c0451438 00000000 c3a7b300
[  855.491232] df80: c26ea100 42654441 c04002e4 c9fd1500 b6e66368 c04513f8 000000f8 c045145c
[  855.499403] dfa0: 00000001 c04000c0 00000001 b6e63888 00000000 b6f9e220 00000000 00000000
[  855.507575] dfc0: 00000001 b6e63888 00000000 000000f8 b6e65000 b6e66368 b6e66368 b6e66368
[  855.515749] dfe0: 000000f8 beddba44 b6de2129 b6d77616 60080030 00000000 00000000 00000000
[  855.523935]  free_pipe_info from pipe_release+0xbc/0xc4
[  855.529182]  pipe_release from __fput+0x8c/0x270
[  855.533821]  __fput from task_work_run+0x94/0xc4
[  855.538457]  task_work_run from do_exit+0x30c/0x99c
[  855.543351]  do_exit from do_group_exit+0x40/0x8c
[  855.548071]  do_group_exit from __wake_up_parent+0x0/0x20
[  855.553490] Code: bad PC value
[  855.556668] ---[ end trace 0000000000000000 ]---
[  855.561385] Fixing recursive fault but reboot is needed!

On A64-OLinuXino-2Ge8G-IND, the installation itself worked fine too, but the first boot never reaches the login phase. The console just remains black

mossroy

@LubOlimex do you now have a timeline? At least an approximate one?

gregh

Quote from: mossroy on May 11, 2024, 02:57:23 PMBut stock debian is not working on the devices I have.
I have several A20-OLinuXino-MICRO, where I was happily using the regular debian until buster. But, since Bullseye, there are kernel panics that make it unsusable, see my blog post in 2022: https://blog.mossroy.fr/2022/03/31/upgrade-vers-bullseye-des-serveurs-olinuxino/

I can confirm this.
I just tried to install Debian 12 on an A20-OLinuXino-MICRO that was working with Debian 10 for years.
The installation was fine and it boots fine.
But after some minutes of work the kernel crashed twice.