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

fraxoz · 2022-05-01 20:27:44

Giving the command spits out the machine and network data, with Device-1 being the Ethernet controller and Device-2 being the WiFi adapter.
If I have to say, network is doing just fine in the live environment (Lithium).
The problem pops up after booting into the CLI environment of Beryllium. I'm gonna try re-installing Beryllium and edit the post.
-- EDIT
Ok, for now, I think I'll be running Lithium with an upgraded kernel, I'll wait for the finished product.
I was able to try it on a VM and I gotta say it's fantastic (as long as you can get it working ;]).
Keep up the good work!

Last edited by fraxoz (2022-05-01 20:53:10)

vic · 2022-06-23 17:19:50

Did the hoops thingy.

vic@beryl:~$ uname -a
Linux beryl 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux

Conclusion, beryl ´s ok, no complaints.

AndrewSmart · 2022-07-02 00:23:59

I don't mind putting Bunsen packages on top of Debian and/or dealing with a netinst squashfs. Down with the tyranny of ISOs! Long live package management!
Viva la revolución!

Oh this thread would have been better, can't delete post: https://forums.bunsenlabs.org/viewtopic.php?id=8165&p=2

Last edited by AndrewSmart (2022-07-02 00:30:16)

dmontaine2 · 2022-07-04 17:50:29

July 4 2022 - error accessing experimental repository when trying to access beryllium packages

https://kelaino.bunsenlabs.org/~johnraff/debian is not known

Bearded_Blunder · 2022-07-04 22:11:51

dmontaine2 wrote:

July 4 2022 - error accessing experimental repository when trying to access beryllium packages
https://kelaino.bunsenlabs.org/~johnraff/debian is not known

Have you made a typo or other error somewhere in the process?
Putting

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

In my sources & adding the apt key is working fine here (UK).

johnraff · 2022-07-04 23:36:51

^^ & ^ kelaino is working OK for me too (in Japan). If not a typo, maybe a brief server outage?

dmontaine2 · 2022-07-05 17:24:49

Yep, I forgot something. Works fine. <sigh>

fraxoz · 2022-08-04 10:15:12

I'm trying to install beryllium on a Thinkpad L570.
I'm again facing the network error in the TTY, so I can't get over the 3rd step.
I've tried following the previous tips from other fellow BLers but even trying "inxi -Mnr" doesn't work.
WTF at this point can't we get a polished installation process? It's been almost a year and a half

johnraff · 2022-08-04 23:54:21

^ try this:
https://forums.bunsenlabs.org/viewtopic.php?id=8239

...but if you've got networking issues they might need to be fixed first.
Do other distros install OK for you?

Last edited by johnraff (2022-08-04 23:55:30)

unklar · 2022-10-16 14:04:02

Does anyone here know what is going wrong with today's update?

sudo apt update
...
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 2 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
sudo apt dist-upgrade
...
Die folgenden Pakete werden aktualisiert (Upgrade):
  tzdata
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
...
sudo apt list --upgradable -a
Auflistung… Fertig
bunsen-meta-all/beryllium 11.0-5 all [aktualisierbar von: 11.0-4]
bunsen-meta-all/now 11.0-4 all  [Installiert,aktualisierbar auf: 11.0-5]

inxi -r
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           2: deb-src https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           3: deb https://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src https://security.debian.org/debian-security bullseye-security main contrib non-free
           5: deb https://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen-bullseye-backports.list 
           1: deb https://pkg.bunsenlabs.org/debian bullseye-backports main
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main
           Active apt repos in: /etc/apt/sources.list.d/debian-bullseye-backports.list 
           1: deb https://deb.debian.org/debian bullseye-backports main contrib non-free

Thanks!

apt policy bunsen-meta-all
bunsen-meta-all:
  Installiert:           11.0-4
  Installationskandidat: 11.0-5
  Versionstabelle:
     11.0-5 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
 *** 11.0-4 100
        100 /var/lib/dpkg/status

Last edited by unklar (2022-10-16 14:08:49)

rbh · 2022-10-16 15:26:34

I have only one box, installed with adding package bunsen-meta-all.
On that, no problem upgrading.

Try command

$ sudo apt upgrade bunsen-meta-all

PS:
I recommend you to add source for "https://pkg.bunsenlabs.org/debian beryllium main"

unklar · 2022-10-17 15:55:50

rbh wrote:

...
PS:
I recommend you to add source for "https://pkg.bunsenlabs.org/debian beryllium main"

Thanks @rbh.
The missing of this repo was the error.

johnraff · 2022-12-09 06:48:21

The official repositories are now up to date. All you need in your apt sources is:

deb https://pkg.bunsenlabs.org/debian beryllium main

The experimental "kelaino" entry can now be removed, but first make sure you have bunsen-keyring installed.

or1o9 · 2022-12-10 10:39:31

Just so there is no confusion. With the experimental "kelaino" you refer to Beryllium systems installed with the netinstall script? Not the beta iso? And the "bunsen-keyring", is that the directory in /usr/share/doc that got created today during the upgrade?

Also during the upgrade this morning, apt complained about this: "dpkg: warning: unable to delete old directory '/etc/apt/keyrings': Directory not empty"

Should that be deleted? The only content there is "bunsen keyring.gpg".

Or have I missed something completely here?

rbh · 2022-12-10 14:22:30

orionH wrote:

Just so there is no confusion. With the experimental "kelaino" you refer to Beryllium systems installed with the netinstall script?

Before the beta iso, you could install Beryllium from plain debian cli, with netinstall script or get a close Beryllium installation with adding package bunsen-meta-all or individual packages. To do that, you had to ad the kelaino repo (often also refered to as "the development repo". Now the content of kelaino repo for beryllium and pkg.bunsenlabs repo for beryllium is the same. So, if you have not already done so, now it is time to change to pkg.bunsenlabs repo and delete source for kelaino.

Not the beta iso?

The beta iso had packages that only was in the kelaino repo. But, the BL sources it set up was only

And the "bunsen-keyring", is that the directory in /usr/share/doc that got created today during the upgrade?

If you If you bring up bunsen keyring in synaptic, you can see what files it installs. /usr/share/doc/bunsen-keyring/ holds information about the keyring.

Also during the upgrade this morning, apt complained about this: "dpkg: warning: unable to delete old directory '/etc/apt/keyrings': Directory not empty"
Should that be deleted? The only content there is "bunsen keyring.gpg".

Do not delete it. As you can see in synaptic, package 2022.12.06+bl11-1, holds /etc/apt/keyrings/bunsen-keyring.gpg. That key is newer than previous key...

The package has following key-files:
/etc/apt/keyrings/bunsen-keyring.gpg
/etc/apt/trusted.gpg.d/BunsenLabs-RELEASE.asc
/etc/apt/trusted.gpg.d/bunsen-keyring.gpg

In debian 12, will /etc/apt/keyrings/bunsen-keyring.gpg be used with the "Signed by" directive in sources.list (or rather bunsen.list).

As of now, it has no importance, but will have. See also man apt-key for Debian 12

or1o9 · 2022-12-11 07:45:47

@rbh, thank you for your clarifying this.

On a side note, but worth to mention. Whilst searching for a solution to an issue I had recently I installed the backport kernel 5.18 in pure desperation to see if it could make any difference to one of my Beryllium installations and help me with my issue. It did not, but I have not noticed anything out of the ordinary either. Things seems to work as usual. Just in case there are other desperados out there I thought it would be good to know.

Anyway the problem is solved now and had nothing to do with BL.

Last edited by or1o9 (2022-12-11 07:54:52)

johnraff · 2022-12-13 04:20:06

orionH wrote:

...the experimental "kelaino" you refer to Beryllium systems installed with the netinstall script?

The netinstall script adds both the experimental "kelaino" repository and the official pkg.bunsenlabs.org repo.

Up to last week, this HOW-TO used the kelaino repo, but the OP has been edited to show that it is no longer necessary.

And the "bunsen-keyring"...

bunsen-keyring is a package which provides the key needed to use the official repository, currently installed in /etc/apt/trusted.gpg.d/

Also during the upgrade this morning, apt complained about this: "dpkg: warning: unable to delete old directory '/etc/apt/keyrings': Directory not empty"
Should that be deleted? The only content there is "bunsen keyring.gpg".

dpkg will not remove files in /etc even if a package no longer provides them. It's safe to remove /etc/apt/keyrings/bunsen keyring.gpg, but a later package upgrade will probably remove it anyway. It's not serious.

johnraff · 2022-12-13 04:29:16

rbh wrote:

In debian 12, will /etc/apt/keyrings/bunsen-keyring.gpg be used with the "Signed by" directive in sources.list (or rather bunsen.list).

This will quite likely not happen in Debian 12/Bookworm/Boron because the Debian developers are not yet agreed on whether the 'signed-by' directive is helpful or not.
eg:
https://bugs.debian.org/cgi-bin/bugrepo … bug=990086
https://bugs.debian.org/cgi-bin/bugrepo … bug=980743

johnraff · 2022-12-21 03:04:38

The kelaino repository will go offline soon. It is time to switch to the official repository.
Details here: https://forums.bunsenlabs.org/viewtopic … 29#p125129

#101 2022-05-01 20:27:44

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

#102 2022-06-23 17:19:50

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

#103 2022-07-02 00:23:59

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

#104 2022-07-04 17:50:29

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

#105 2022-07-04 22:11:51

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

#106 2022-07-04 23:36:51

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

#107 2022-07-05 17:24:49

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

#108 2022-08-04 10:15:12

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

#109 2022-08-04 23:54:21

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

#110 2022-10-16 14:04:02

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

#111 2022-10-16 15:26:34

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

#112 2022-10-17 15:55:50

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

#113 2022-12-09 06:48:21

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

#114 2022-12-10 10:39:31

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

#115 2022-12-10 14:22:30

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

#116 2022-12-11 07:45:47

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

#117 2022-12-13 04:20:06

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

#118 2022-12-13 04:29:16

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

#119 2022-12-21 03:04:38

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

Board footer