Debian bullseye (11) image 1.0 released for B3

Discuss development on Bubba
MouettE
Site admin
Posts: 341
Joined: 06 Oct 2011, 19:45

Re: Debian bullseye (11) image 1.0 released for B3

Post by MouettE »

fredrikj wrote: 23 May 2022, 08:28 Mouette, I saw this commit:
> Imported new upstream version 5.10.117
https://github.com/Excito/kernel-5.10/c ... e02f05d339

Does that mean that you'll roll out kernel 5.10.117 as a stable update to all bullseye users now? If so, yay! :)
Yes
MouettE
Site admin
Posts: 341
Joined: 06 Oct 2011, 19:45

Re: Debian bullseye (11) image 1.0 released for B3

Post by MouettE »

Kernel 5.10.117-1 is uploaded in the repo and available as an update, with intel wifi drivers included.

Do not hesitate to ask for kernel changes and/or upgrades. I cannot automate the build process (because it requires minimal testing) but building a new kernel is not very time consuming on my part.
Satrap
Posts: 12
Joined: 13 Jan 2012, 15:50

Re: Debian bullseye (11) image 1.0 released for B3

Post by Satrap »

MouettE wrote: 23 May 2022, 17:02 Kernel 5.10.117-1 is uploaded in the repo and available as an update, with intel wifi drivers included.
Thank you! :D
skion
Posts: 7
Joined: 24 Jul 2011, 08:18

Re: Debian bullseye (11) image 1.0 released for B3

Post by skion »

I get the following on an install with bullseye and wipe = false...
2000-08-07 09:07:13.916 - INFO - Running Excito installer version 2.0 daemon process with pid 101
2000-08-07 09:07:13.923 - INFO - Checking image file /mnt/usb/install/bullseye/b3-bullseye-1.0-20211220-1622.txz
2000-08-07 09:07:13.930 - INFO - Checking /dev/sdb
2000-08-07 09:07:13.931 - INFO - Running 'fdisk -l /dev/sdb'
2000-08-07 09:07:13.957 - INFO - Running 'sgdisk -p /dev/sdb'
2000-08-07 09:07:13.999 - INFO - Running 'blkid /dev/sdb1'
2000-08-07 09:07:14.91 - INFO - Running 'blkid /dev/sdb2'
2000-08-07 09:07:14.185 - INFO - Running 'blkid /dev/sdb3'
2000-08-07 09:07:14.239 - INFO - Running 'sgdisk -i 1 /dev/sdb'
2000-08-07 09:07:14.278 - INFO - Running 'sgdisk -i 2 /dev/sdb'
2000-08-07 09:07:14.318 - INFO - Running 'sgdisk -i 3 /dev/sdb'
2000-08-07 09:07:14.359 - INFO - Destination disk: sdb (2.7 TiB, gpt)
2000-08-07 09:07:14.361 - ERROR - The existing (0.0 B) system partition does not meet minimal size criteria of 8 GiB
This is a bit odd, since the same install.ini file worked fine with buster and before. Tips anyone?

Running the indicated commands manually results in:

Code: Select all

[root@b3-install ~]# sgdisk -p /dev/sdb
Disk /dev/sdb: 5860533168 sectors, 2.7 TiB
Model: WDC WD30EZRZ-00G
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 05775DC6-40BF-47A3-AAC2-549B44555D1B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048       104859647   50.0 GiB    8300  
   2       104859648       107931647   1.5 GiB     8200  
   3       107931648      5860533134   2.7 TiB     8E00  

and for the first partition:

Code: Select all

[root@b3-install ~]# sgdisk -i 1 /dev/sdb
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: 7E2167AA-3A64-4B98-A912-EEF67B64F0CB
First sector: 2048 (at 1024.0 KiB)
Last sector: 104859647 (at 50.0 GiB)
Partition size: 104857600 sectors (50.0 GiB)
Attribute flags: 0000000000000000
Partition name: ''
UPDATE (and solved):

The logical sector size wasn't detected correctly in partitions.py, because there is no line starting with Logical sector size: in the output of sgdisk -p. I hardcoded it to 512 in that file and the installer ran...
guidol
Posts: 1
Joined: 19 Sep 2022, 09:26

Re: Debian bullseye (11) image 1.0 released for B3

Post by guidol »

MouettE wrote: 23 May 2022, 17:02 Kernel 5.10.117-1 is uploaded in the repo and available as an update, with intel wifi drivers included.
@MouettE
Many Thanks for the image ;) It is working GREAT on my B3
debian has a fine support for the old kirkwood devices (like also the Sheevaplug)

excito_B3_bullseye.jpg
excito_B3_bullseye.jpg (56.96 KiB) Viewed 1446 times
marcz
Posts: 6
Joined: 01 Oct 2011, 06:25

Re: Debian bullseye (11) image 1.0 released for B3

Post by marcz »

grushog wrote: 09 Jan 2022, 09:23 I have upgraded as well.

I did have an issue with "/" being owned by the "excito" user rather than "root".
Probably due to my own error when doing the original install back in 2017.
After fixing this the upgrade went smooth.

Thanks for keeping this alive.
I had the same issue, with systemd not upgrading and blocking the upgrade process.

The errors message was :

Code: Select all

Detected unsafe path transition / → /var

Code: Select all

Detected unsafe path transition / → /run
This was also caused by the root "/" being owned by "excito:excito" instead of "root:root", and a chmod solved the issue

Until upgrading to buster no error was detected.

I just give these details if some other people encounter the same issue.

Thank you Charles for maintaining the new debian kernels, without this, the b3 would just be a museum device.
stasheck
Posts: 126
Joined: 15 Jan 2014, 13:13

Re: Debian bullseye (11) image 1.0 released for B3

Post by stasheck »

I just noticed the current kernel is missing Wireguard support, opened an issue on Github: https://github.com/Excito/kernel-5.10/issues/2
Clive
Posts: 164
Joined: 07 Mar 2007, 07:15

Re: Debian bullseye (11) image 1.0 released for B3

Post by Clive »

Noticed a new bubba3-kernal was just uploaded, anyone know what it contains/changed ?

Update: AHA ! Just checked that github link and understand that wireguard support was added. This is really useful as I recently needed to use a RaspberryPi to act as a wireguard server to my summer house, I much prefer to use my B3 for this instead.

(Also, not sure why, but my B3 always feels faster than my RPI's, even though it is now 10+ years old, it just feels more stable)
MouettE
Site admin
Posts: 341
Joined: 06 Oct 2011, 19:45

Re: Debian bullseye (11) image 1.0 released for B3

Post by MouettE »

Yes indeed. Do not hesitate if you miss any feature on the kernel, I can add them and release a new version.
stasheck
Posts: 126
Joined: 15 Jan 2014, 13:13

Re: Debian bullseye (11) image 1.0 released for B3

Post by stasheck »

Thanks a ton for the new kernel! Truly, this community is extraordinary, and MouettE is one the pillars :-)
goodgirl
Posts: 5
Joined: 24 Nov 2019, 12:20

Re: Debian bullseye (11) image 1.0 released for B3

Post by goodgirl »

Hi everyone!

Just a big THANK YOU for the chance to update to bullseye. Just upgraded 2 B3 boxes from buster to bullseye, the first one was done remotely, no error allowed ;-) I employed the standard way via apt. Before:

Code: Select all

root@b3:/etc/apt# uname -a
Linux b3.local 4.19.117-1 #1 Wed Apr 22 09:44:09 EDT 2020 armv5tel GNU/Linux
root@b3:/etc/apt# uptime
 21:59:36 up 992 days, 22:18,  0 users,  load average: 1.09, 1.70, 1.77
root@b3:/etc/apt# shutdown -r now
After:

Code: Select all

root@b3:~# uname -a
Linux b3.local 5.10.177-1 #1 Mon Apr 17 06:42:38 UTC 2023 armv5tel GNU/Linux
Best regards
Goodgirl
bubba two, unboxed 2019 :-)
MouettE
Site admin
Posts: 341
Joined: 06 Oct 2011, 19:45

Re: Debian bullseye (11) image 1.0 released for B3

Post by MouettE »

Thanks for your message. It's a great incentive for me to know people continue using this hardware and the distribution I maintain !

Also I started working on the new debian version (12), I have some issues with the 6.1 kernel which refuses to boot. Nevertheless I still hope I'll be able to make it work and release it shortly after the official distribution. Stay tuned !
Gordon
Posts: 1457
Joined: 10 Aug 2011, 03:18

Re: Debian bullseye (11) image 1.0 released for B3

Post by Gordon »

MouettE wrote: 25 Apr 2023, 17:54 Thanks for your message. It's a great incentive for me to know people continue using this hardware and the distribution I maintain !

Also I started working on the new debian version (12), I have some issues with the 6.1 kernel which refuses to boot. Nevertheless I still hope I'll be able to make it work and release it shortly after the official distribution. Stay tuned !
I had some issues with that as well. Not real sure how that works with Debian though or how you tell it to build the kernel. In my case there appeared to be some conflict with a ported pre-6.x kernel setting that caused init to be killed but to this point I have no clue what setting that might have been. I ended up discarding my old kernel config and reverting to mvebu_v5_defconfig which did boot correctly and then I re-added all of the desired features and modules and none of them caused it to break.

So while writing this I remembered that when I started with no config I ended up with a kernel that didn't output even a single line to early console and got an idea. I tested what happens if I simply run `make defconfig` rather than specifying the actual target system and it turns out that the automatic detection wrongfully identifies the B3 as a `multi_v7` which is somehow enough to break the resulting kernel completely even though the compiler still produces armv5 code.
MouettE
Site admin
Posts: 341
Joined: 06 Oct 2011, 19:45

Re: Debian bullseye (11) image 1.0 released for B3

Post by MouettE »

Gordon wrote: 03 May 2023, 18:21 I had some issues with that as well. Not real sure how that works with Debian though or how you tell it to build the kernel. In my case there appeared to be some conflict with a ported pre-6.x kernel setting that caused init to be killed but to this point I have no clue what setting that might have been. I ended up discarding my old kernel config and reverting to mvebu_v5_defconfig which did boot correctly and then I re-added all of the desired features and modules and none of them caused it to break.

So while writing this I remembered that when I started with no config I ended up with a kernel that didn't output even a single line to early console and got an idea. I tested what happens if I simply run `make defconfig` rather than specifying the actual target system and it turns out that the automatic detection wrongfully identifies the B3 as a `multi_v7` which is somehow enough to break the resulting kernel completely even though the compiler still produces armv5 code.
The problems we face are different because you still use the interstitial kernel from sakaki and I boot directly my kernel from U-Boot. The problem I had was not from the configuration but from the updated dtc code in the kernel tree. Kernel developpers regularly update it from upstream (code is directly copied in the kernel tree) and the updates done since 5.11 prevent b3's u-boot from booting the kernel (even on the 2013 version). So I had to revert those updates and version 6.1 the kernel started working again. The debian 12 image is approaching !

I'm very happy I managed to get it working but it took a lot of time to identify the problematic commits (had to build each commit with a minimal bootable config until it stopped working, revert it and test, all the way from 5.11 to 6.1, probably built at least 40-50 versions). Debian 12 will include this custom kernel as always but I will try to design an alternate kernel packaging using an interstitial kernel loading the official kirkwood debian package for test. In any case it will be a nice challenge and address issues with custom kernels (lack of security updates until requested, lack of modules, etc) if I manage to get it working.
Gordon
Posts: 1457
Joined: 10 Aug 2011, 03:18

Re: Debian bullseye (11) image 1.0 released for B3

Post by Gordon »

I actually built my own because Sakaki's didn't work for me at first ;)

The big advantage of the interstitial kernel is that you can manipulate the command line options to the kernel, meaning I only need to create one single kernel and be able to use that for all combinations of init (openrc, systemd) and disk (usb, internal drive, partition layout) and because the DTB is a separate file I can also select what LED colour to show during boot.

If you like to experiment you can simply grab the one from my GitHub page. The only caveat is that the init script is based on a boot partition that is separate from the root partition, so if you're using the original Excito partition layout this means that the kernel image must not be in /boot but in /, but that should be good enough for testing.
Last edited by Gordon on 04 May 2023, 15:24, edited 1 time in total.
Post Reply