HOW-TO set up an experimental BL Beryllium system on Bullseye.

johnraff · 2021-02-16 05:53:09

BL Lithium packages have been migrated to Beryllium for Debian Bullseye, and are available for testing purposes here:
https://kelaino.bunsenlabs.org/~johnraff/debian
The source is on GitHub in the 'beryllium' branches:
https://github.com/BunsenLabs

To set up a Debian Bullseye system using these packages, follow these steps:

1)
Download a Debian Bullseye "alpha 3" installer. These are netinstall images that pull in the current Bullseye packages. The "alpha 3" refers to the Debian Installer software itself, which will probably see more upgrades before the official release.

amd64
https://cdimage.debian.org/cdimage/bull … etinst.iso
or, with non-free firmware:
https://cdimage.debian.org/cdimage/unof … etinst.iso

i386
https://cdimage.debian.org/cdimage/bull … etinst.iso
or, with non-free firmware:
https://cdimage.debian.org/cdimage/unof … etinst.iso

2)
Follow the usual install process, remembering:
*) Don't set a password for 'root' in the user setup phase (you'll have sudo rights).
*) At the final package selection phase, choose only "standard system utilities" (up/down arrows to navigate, spacebar to toggle selection).

3)
Login to the new command-line system, and (just to make sure everything's up to date):

sudo apt update
sudo apt upgrade

Then (use vim if you prefer):

sudo nano /etc/apt/sources.list.d/bunsen.list

type in this line:

deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main

Get the signing key:

wget https://kelaino.bunsenlabs.org/~johnraff/bunsen-dev.asc
sudo cp bunsen-dev.asc /etc/apt/trusted.gpg.d

Also make sure you add 'contrib' and 'non-free' to all the existing debian lines in /etc/apt/sources.list
something like:

deb https://deb.debian.org/debian bullseye main contrib non-free

...etc

Update again:

sudo apt update
sudo apt upgrade

(No packages will probably be upgraded.)

4)
Now, time to install the bunsenlabs packages. The metapackage will pull them all in as dependencies, but be sure to use the --no-install-recommends option, or you'll get a pile of unwanted stuff:

sudo apt-get install --no-install-recommends bunsen-meta-all

Reboot to see the graphical interface:

sudo systemctl reboot

That's it, or was for me on a Virtual Machine.

On real hardware, you might need to tweak the network settings however.
I'm pasting in @hhh's advice from Lithium, but this might get updated:

---
network

Since iwconfig sets up the internet connection during the installation, editing of /etc/network/interfaces is necessary after the BL desktop is installed to allow Network Manager to handle connections.

Comment out anything except for the first eight lines as so...

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug enp9s0
#iface enp9s0 inet dhcp

---
NOTE
The Debian Bullseye backports do not yet exist, nor do the BL ones. Attempting to add them from the bl-welcome script will fail at the moment.

---
If you have any issues with any of this, then of course bug reports are very welcome and will help get BunsenLabs Beryllium into shape all the faster. Small things can go on this thread, and for anything that looks as if it might need discussion, please start a new topic in Bug Reports; a prefix of [Beryllium] in the title will help keep things organized. smile

Thanks!

Last edited by johnraff (2021-02-17 01:46:00)

johnraff · 2021-02-17 01:43:50

Bug in bunsen-welcome (wrong Debian base) has now been fixed, so if you do another apt update/upgrade and log out/in the welcome script popup should appear. (Remember not to add the backports yet though.)

NB Above advice is only for people who installed before the bugfixed bunsen-welcome came out yesterday. People following the HOWTO in the OP from now on don't have to do anything special.

Last edited by johnraff (2021-02-18 01:05:32)

dhalgren · 2021-02-17 06:10:48

On my system /etc/NetworkManager/NetworkManager.conf needed to be changed to read

managed=true

in order for WiFi to work.

johnraff · 2021-02-18 01:51:27

Hi @dhalgren, did you edit /etc/network/interfaces according to @hhh's instructions in the top post?
If any interface is defined there, then network-manager will ignore it with the default setting of managed=false.
https://wiki.debian.org/NetworkManager# … _Unmanaged

I'm guessing that the Debian Installer wrote your wireless interface details in /etc/network/interfaces, so you could try commenting-them out as @hhh suggests, and in /etc/NetworkManager/NetworkManager.conf setting [ifupdown] back to managed=false. Can you then enable wirelss via network-manager?

dhalgren · 2021-02-18 04:03:04

Hi @johnraff. Unfortunately @hhh's suggestion did not work. I could connect to the router, but had no internet connection, and there was nothing wrong or problematic with the router(other devices connected normally, with internet access). I had to do both to get the WiFi working so that I could connect and have the connection actually working.

I had to do both with Lithium experimental also, though when Lithium was released, everything changed back to how you are describing it here.

I have searched for reasons as to why this may be the case, but have found no answer.

I did, however, install using a cable, not WiFi, and the answer may be in that, for those with more knowledge than I.

I mentioned the difficulty just in case others have the same problem.

I installed, just for background, on a (Windows 8!!!) Asus X550C notebook, with bog standard hardware, and so far that has been the only problem I have experienced.

johnraff · 2021-02-18 04:40:58

^Sorry I'm not a networking expert, but it still sounds to me as if something is being written to /etc/network/interfaces during the installation process. That's the only thing that would account for the iso install working, but not the debian->metapackage route.

Could you post the content of your /etc/network/interfaces? (Remove any sensitive info like passwords of course.)

hhh · 2021-02-18 06:12:06

Try deleting the file /etc/network/interfaces.d/setup and overwrite /etc/network/interfaces with the this config, reboot...

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

dhalgren · 2021-02-18 09:50:36

As below:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# allow-hotplug enp4s0f2
# iface enp4s0f2 inet dhcp
# This is an autoconfigured IPv6 interface
# iface enp4s0f2 inet6 auto

There is nothing in /etc/network/interfaces.d/

Based on what has been said here, it should work. So, I will change NetworkManager back to "false", reboot, and see what happens.

EDIT: Now, I am even more completely confused, if that is possible.
Yesterday I rebooted, the WiFi did not work, I then applied @hhh's fix, rebooted, and it still did not work. I then modified NetworkManager.conf, restarted network-manager, and it worked. Just now, I changed it back to managed=false rebooted, and it works.

I do not know if I made a mistake yesterday, or what. However, commenting out the last five lines works.

Apologies for what I can only imagine was an error I made.

Last edited by dhalgren (2021-02-18 10:07:26)

johnraff · 2021-02-19 06:02:06

Glad you got it sorted, anyway! smile

Maybe there was a loose wire somewhere...

dolly · 2021-02-20 13:11:25

The instructions in your op @johnraff works. smile Installed on a T61 that works ok, a bit grumpy maybe. The first reboot after installation took forever, and I noticed that I were holding my breath for a couple of seconds because of it.

Have only had a quick look on it, and not noticed anything out of the normal so far. Will add some stuff and make some small personal preference changes of course, however I did add an user which I intend save as a default BL desktop.

Will report back if there is something unusual, and maybe a suggestion or two. smile

hhh · 2021-02-21 03:16:06

Thanks for the feedback, @dolly.

johnraff · 2021-02-21 07:31:45

dolly wrote:

... maybe a suggestion or two.

Please!

unklar · 2021-02-21 22:17:46

^I have installed today. smile

inxi -SMr
System:    Host: francescoPC Kernel: 5.10.0-3-amd64 x86_64 bits: 64 Desktop: Xfce 
           Distro: Debian GNU/Linux bullseye/sid 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx serial: <superuser required> 
           BIOS: American Megatrends v: 2102 date: 02/23/2009 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           2: deb-src http://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           3: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main

I had to chroot into the new system because I had already selected "Complete the installation" without using the "shell" below. big_smile

Here I also checked the note above about the network and immediately corrected it accordingly. Thanks!

The welcome script worked fine. I installed these additional packages:

   bunsen-images-archives
   bunsen-meta-bluetooth
   bunsen-meta-java
   bunsen-meta-vcs

In the tint2 bar there is this error with the power management.

Somewhere in the forum @johnraff had already referred to it though.
So far no problems detected.

rbh · 2021-03-31 10:25:04

Upgraded to Bullsey/Beryllium some days ago. All works well but for OS identified.
System is still identified as "Debian 10.5"..
Inxi -S, says "Distro: BunsenLabs GNU/Linux 10.5 (Lithium)"

File /etc/debian_version says "bullseye/sid"

BTW, package bunsen-exit-python is not upgraded yet. So you better change to bunsen-exit before upgrading and change back when berylium is released.

Last edited by rbh (2021-03-31 10:25:26)

Naik · 2021-03-31 20:26:52

I recently set up a fresh bullseye with xfce and than added the bunsenlabs beryllium repos. Everything works great so far as you can see here. There wasn't even the aforementioned icon issue.
Only that Grub also recognises it as "Debian 11 Bullseye/Sid".
I am so looking forward for the next release!

Naik --greetz

DeepDayze · 2021-04-01 01:33:50

Naik wrote:

I recently set up a fresh bullseye with xfce and than added the bunsenlabs beryllium repos. Everything works great so far as you can see here. There wasn't even the aforementioned icon issue.
Only that Grub also recognises it as "Debian 11 Bullseye/Sid".
I am so looking forward for the next release!
Naik --greetz

That's a nice scrot and I see you got the rounded corners. Does XFCE have this?

Naik · 2021-04-01 17:20:04

^ No, that's picom.
I didn't use the Xfce session much after recognising that the two-paned thunar I heard of is still not in sid. sad

Naik --greetz

dmontaine · 2021-04-02 21:58:58

Following this guide, I installed the experimental distro using the non-free Debian install on these two computers on bare metal:

Lenovo ThinkCentre M93p desktop
Lenovo X1 Yoga Gen 4 laptop

(10 Apr 2021) Also did a bare metal install on a

HP Prodesk 600 mini

Everything seems to be working well.

Last edited by dmontaine (2021-04-11 00:48:37)

rbh · 2021-04-04 14:40:43

rbh wrote:

System is still identified as "Debian 10.5".

That is because bunsen-os-release, is not released to Beryllium dev.
After removing bunsen-os-release, neofetch, reports "OS: Debian GNU/Linux bullseye/sid x86_64"

Last edited by rbh (2021-04-04 14:42:11)

bunsencub · 2021-04-16 14:16:35

johnraff wrote:

BL Lithium packages have been migrated to Beryllium for Debian Bullseye, and are available for testing purposes here:

Sorry, did not work, because

johnraff wrote:

...
Update again:
sudo apt update
sudo apt upgrade
(No packages will probably be upgraded.)

I got the message, something like this "https://kelaino.bunsenlabs.org/~johnraff/ has no release candidate, is therefore per default disabled". So also bunsen-meta-all could not be downloaded.

I had done the signing key stuff without error. What shall I do to enable it?

rbh · 2021-04-16 15:05:49

bunsencub wrote:

johnraff wrote:
BL Lithium packages
Sorry, did not work, because
johnraff wrote:
...
Update again:
sudo apt update
sudo apt upgrade
(No packages will probably be upgraded.)
I got the message, something like this "https://kelaino.bunsenlabs.org/~johnraff/ has no release candidate, is therefore per default disabled". So also bunsen-meta-all could not be downloaded.

Then you have not correct adress to the repository. Command:

$ inxi -r

will show your repositorys. Copy and paste them for us.

bunsencub · 2021-04-16 15:33:36

$ inxi -r

Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://deb.debian.org/debian/ bullseye main non-free contrib
           2: deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
           3: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https:/kelaino.bunsenlabs.org/~johnraff/debian beryllium main

rbh · 2021-04-16 15:53:11

Ok. I have a lokal mirror of repositorys here. Last sync was 09 pm GMT. "apt update" works ok for the Keliano mirror here.

Changed over to fetch directly from keliano-server and got:

Ign:1 https:/kelaino.bunsenlabs.org/~johnraff/debian beryllium InRelease
Err:2 https:/kelaino.bunsenlabs.org/~johnraff/debian beryllium Release
  Undetermined Error
[...]
Reading package lists... Done
E: The repository 'https:/kelaino.bunsenlabs.org/~johnraff/debian beryllium Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

So someting has happened att the server. Trying to pm Johnraff

bunsencub · 2021-04-16 16:09:53

rbh wrote:

...So someting has happened att the server. Trying to pm Johnraff

Sorry, rbh, I am confused. Shall I do anything? Just wait? What is the meaning of "pm" here?

Thanks, bunsencub

rbh · 2021-04-16 16:37:31

bunsencub wrote:

Sorry, rbh, I am confused. Shall I do anything? Just wait?

There is nothing you can do for the server. No package is updated after 2021-02-17. If you have upgraded after that date, there is nothing new to fetch.

If you are on a new installation, you can live with not updating until server is fixed. Or, you can download the packages manually and install with "dpkg -i *.deb"
You forst need to doenload and open file https://kelaino.bunsenlabs.org/~johnraf … 4/Packages (or the one for i386), så you know what packages to download.

What is the meaning of "pm" here?

PM means Personal Message.

I lost track of time. The second daily running of apt-mirror, was scheduled to 15:00 GMT. And the mirror is still working.

#1 2021-02-16 05:53:09

HOW-TO set up an experimental BL Beryllium system on Bullseye.

#2 2021-02-17 01:43:50

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#3 2021-02-17 06:10:48

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#4 2021-02-18 01:51:27

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#5 2021-02-18 04:03:04

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#6 2021-02-18 04:40:58

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#7 2021-02-18 06:12:06

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#8 2021-02-18 09:50:36

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#9 2021-02-19 06:02:06

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#10 2021-02-20 13:11:25

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#11 2021-02-21 03:16:06

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#12 2021-02-21 07:31:45

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#13 2021-02-21 22:17:46

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#14 2021-03-31 10:25:04

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#15 2021-03-31 20:26:52

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#16 2021-04-01 01:33:50

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#17 2021-04-01 17:20:04

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#18 2021-04-02 21:58:58

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#19 2021-04-04 14:40:43

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#20 2021-04-16 14:16:35

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#21 2021-04-16 15:05:49

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#22 2021-04-16 15:33:36

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#23 2021-04-16 15:53:11

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#24 2021-04-16 16:09:53

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

#25 2021-04-16 16:37:31

Re: HOW-TO set up an experimental BL Beryllium system on Bullseye.

Board footer