Debian bullseye (11) image 1.0 released for B3

[MouettE]

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]

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]

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

Thank you!

[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]

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 (56.96 KiB) Viewed 825 times

[marcz]

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.