You are not logged in.

#1 2021-04-03 17:42:42

manyroads
Member
From: around here, somewhere
Registered: 2019-04-16
Posts: 102
Website

Bunsenlabs on non-systemd Debian (antiX19)

If you want to work with, or play around with, BunsenLabs (BL) on a non-systemd Debian platform, here is a method by which you can install BL on antiX19.   (Later, I'll move things over to Bullseye...)

https://eirenicon.org/bunsenlabs-on-non … n-antix19/


Pax vobiscum,
Mark Rabideau - http://many-roads.com  Professional Genealogist
dwm & i3wm on arch ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

Offline

#2 2021-04-05 12:17:48

ceeslans
Member
Registered: 2015-09-30
Posts: 109

Re: Bunsenlabs on non-systemd Debian (antiX19)

manyroads wrote:

If you want to work with, or play around with, BunsenLabs (BL) on a non-systemd Debian platform, here is a method by which you can install BL on antiX19.   (Later, I'll move things over to Bullseye...)

https://eirenicon.org/bunsenlabs-on-non … n-antix19/

Thanks Mark for the write-up.
Used a fresh antiX-19.3-amd64 and installed bunsen-meta-all as per your guide. It worked flawlessly.
With clipit, update-notifier and bluetooth disabled at startup. my Bunsenlabs system is idling at ~275mb.
(It does feel a bit odd though, to kill the 'soul' of the host (antiX) by cutting most of its window managers and orphaned applications...)
kwjzKMTt.png

Last edited by ceeslans (2021-04-05 14:07:06)

Offline

#3 2021-04-05 13:27:22

sleekmason
zoom
Registered: 2018-05-22
Posts: 608
Website

Re: Bunsenlabs on non-systemd Debian (antiX19)

Very nice tutorial!  Thank you:) My "todo" list of fun stuff is growing beyond my time to try them! Mark another one down.

Offline

#4 2021-04-05 15:52:29

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,332

Re: Bunsenlabs on non-systemd Debian (antiX19)

Mmm this should be nice to try out, and maybe go out on a limb to upgrade this to Sid  monkey


Real Men Use Linux

Offline

#5 2021-04-05 16:29:30

manyroads
Member
From: around here, somewhere
Registered: 2019-04-16
Posts: 102
Website

Re: Bunsenlabs on non-systemd Debian (antiX19)

FWIW... the same thing actually works on MXLinux 19.4 (I tested that yesterday).  As for sid, I think you'll find it breaks because of all the old software used in BL.  It will work once Bullseye is out.  If you are niggling things at a very detailed level you will find that BL embeds a few systemd dependencies that are not addressed by my tutorial.  You will need to fix them to your liking if you want them to work.     

On another note... I did a quick fix on a rofi theme for any who want to use it.  It sort of looks like Lithium now...

/*******************************************************************************
 * ROFI Color theme
 * User: ManyRoads
 * Copyright: Rasmus Steinke & ManyRoads
 * modified from the original by ManyRoads
 *******************************************************************************/

* {
    selected-normal-foreground:  rgba ( 255, 255, 255, 100 % );
    foreground:                  rgba ( 193, 193, 193, 100 % );
    normal-foreground:           @foreground;
    alternate-normal-background: rgba ( 39, 50, 56,
     100 % );
    red:                         rgba ( 188, 75, 79, 100 % );
    selected-urgent-foreground:  rgba ( 255, 24, 68, 100 % );
    blue:                        rgba ( 52, 96, 120, 100 % );
    urgent-foreground:           rgba ( 255, 154, 80, 100 % );
    alternate-urgent-background: rgba ( 39, 50, 56, 100 % );
    active-foreground:           rgba ( 128, 203, 196, 100 % );
    lightbg:                     rgba ( 238, 232, 213, 100 % );
    selected-active-foreground:  rgba ( 128, 203, 196, 100 % );
    alternate-active-background: rgba ( 39, 50, 56, 100 % );
    background:                  rgba ( 43, 69, 79, 100 % );
    bordercolor:                 rgba ( 39, 50, 56, 100 % );
    alternate-normal-foreground: @foreground;
    normal-background:           rgba ( 39, 50, 56, 100 % );
    lightfg:                     rgba ( 88, 104, 117, 100 % );
    selected-normal-background:  rgba ( 57, 66, 73, 100 % );
    border-color:                @foreground;
    spacing:                     2;
    separatorcolor:              rgba ( 30, 37, 41, 100 % );
    urgent-background:           rgba ( 39, 50, 56, 100 % );
    selected-urgent-background:  rgba ( 57, 66, 73, 100 % );
    alternate-urgent-foreground: @urgent-foreground;
    background-color:            rgba ( 0, 0, 0, 0 % );
    alternate-active-foreground: @active-foreground;
    active-background:           rgba ( 39, 50, 56, 100 % );
    selected-active-background:  rgba ( 57, 66, 73, 100 % );
}
#window {
    background-color: @background;
    border:           1;
    padding:          5;
}
#mainbox {
    border:  0;
    padding: 0;
}
#message {
    border:       1px dash 0px 0px ;
    border-color: @separatorcolor;
    padding:      1px ;
}
#textbox {
    text-color: @foreground;
}
#listview {
    fixed-height: 0;
    border:       2px dash 0px 0px ;
    border-color: @separatorcolor;
    spacing:      2px ;
    scrollbar:    true;
    padding:      2px 0px 0px ;
}
#element {
    border:  0;
    padding: 1px ;
}
#element.normal.normal {
    background-color: @normal-background;
    text-color:       @normal-foreground;
}
#element.normal.urgent {
    background-color: @urgent-background;
    text-color:       @urgent-foreground;
}
#element.normal.active {
    background-color: @active-background;
    text-color:       @active-foreground;
}
#element.selected.normal {
    background-color: @selected-normal-background;
    text-color:       @selected-normal-foreground;
}
#element.selected.urgent {
    background-color: @selected-urgent-background;
    text-color:       @selected-urgent-foreground;
}
#element.selected.active {
    background-color: @selected-active-background;
    text-color:       @selected-active-foreground;
}
#element.alternate.normal {
    background-color: @alternate-normal-background;
    text-color:       @alternate-normal-foreground;
}
#element.alternate.urgent {
    background-color: @alternate-urgent-background;
    text-color:       @alternate-urgent-foreground;
}
#element.alternate.active {
    background-color: @alternate-active-background;
    text-color:       @alternate-active-foreground;
}
#scrollbar {
    width:        4px ;
    border:       0;
    handle-width: 8px ;
    padding:      0;
}
#mode-switcher {
    border:       2px dash 0px 0px ;
    border-color: @separatorcolor;
}
#button.selected {
    background-color: @selected-normal-background;
    text-color:       @selected-normal-foreground;
}
#inputbar {
    spacing:    0;
    text-color: @normal-foreground;
    padding:    1px ;
}
#case-indicator {
    spacing:    0;
    text-color: @normal-foreground;
}
#entry {
    spacing:    0;
    text-color: @normal-foreground;
}
#prompt {
    spacing:    0;
    text-color: @normal-foreground;
}
#inputbar {
    children:   [ prompt,textbox-prompt-colon,entry,case-indicator ];
}
#textbox-prompt-colon {
    expand:     false;
    str:        ":";
    margin:     0px 0.3em 0em 0em ;
    text-color: @normal-foreground;
}

Here's a patch (replacement script) for bl-exit that you can place in tint2.... the short-cut Super+x is one of those systemd probs...

#! /bin/bash
yad --center --borders=1 --on-top --sticky --single-click --title='Logout Options' \
	--buttons-layout=center \
	--window-icon="gtk-quit: exit" \
	--button="Logout!system-log-out:openbox --exit" \
	--button="Reboot!system-reboot:sudo reboot" \
	--button="Shutdown!system-shutdown:sudo halt" \
	--button="Suspend!system-suspend:sudo pm-suspend" \
	--button=Cancel:0 \

Pax vobiscum,
Mark Rabideau - http://many-roads.com  Professional Genealogist
dwm & i3wm on arch ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

Offline

#6 2021-04-30 14:15:39

Naik
Member
From: Lipsia
Registered: 2015-10-03
Posts: 298

Re: Bunsenlabs on non-systemd Debian (antiX19)

Hey there!

Thanks for the write up @manyroads!
I just tried to follow your tutorial and everything went smooth until I decided that it's time reboot and start my new bunsenlabs session.
I found grub to be broken beyond my understanding (some error regarding *symbol missing? )¹ and unable to boot anything.

loading Linux 4.9.235-antix.1-amd64-smp...
Error: Symbol >>grub_register_command_lockdown<< not found.
loading Initial Ramdisk...
Error: Symbol >>grub_register_command_lockdown<< not found.

I can't remember having removed anything but the libreoffice related stuff you suggested. But I have enabled the b43 driver (to have wifi) and the windows-driver support (just for fun, haven't downloaded or enabled any of such things...).
Can this be due to the fact that I installed Antix onto an sd-card checking encryption option from the installer? Though it did reboot fine once, after the installation.
Or is it more likely that I missed something like rebuild initramfs or updating grub?

My own internet search only brought up one hit where someone complained having this same issue after trying to create a bootable ubuntu via rufus and the suggestion was to chroot into the installation and reinstall grub, which is exactly what I am going to do now but it is of no avail in understanding what caused the problem in the first place. Could grub have been updated into oblivion while installing bunsen-meta-all? I guess not, but hey...

Any Help would be highly apreciated.

EDIT:
¹I will try to take a note of the exact error-message ASAP, and edit my post accordingly.

Naik --greetz

Last edited by Naik (2021-04-30 14:43:14)


"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen on GitHub

Offline

#7 2021-04-30 14:38:56

manyroads
Member
From: around here, somewhere
Registered: 2019-04-16
Posts: 102
Website

Re: Bunsenlabs on non-systemd Debian (antiX19)

I have never installed anything to an sd card... I have no idea what you may have encountered. I wish I did.  I think you are operating above my 'pay grade'. wink


Pax vobiscum,
Mark Rabideau - http://many-roads.com  Professional Genealogist
dwm & i3wm on arch ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

Offline

#8 2021-04-30 15:08:59

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 1,554

Re: Bunsenlabs on non-systemd Debian (antiX19)

^The error is fixed by running the command in the chroot:

dpkg-reconfigure grub-pc

@Naik, make sure that the correct device is selected!

Last edited by unklar (2021-04-30 17:46:15)

Offline

#9 2021-04-30 16:32:21

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,192

Re: Bunsenlabs on non-systemd Debian (antiX19)

It is hard for us to spekulate about what you have done... You have to examine the logs of your system. Should be possible in chroot.

There is tools to examine content of first sector of hd and verify if grub was correct written. many years ago I did that, can not be more specific.

Have you tried booting with the sd-card atached. Did you write grub for your hd installation on the sd-card?


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#10 2021-04-30 21:55:32

Naik
Member
From: Lipsia
Registered: 2015-10-03
Posts: 298

Re: Bunsenlabs on non-systemd Debian (antiX19)

^ I choose to let the installer write grub on the /boot partition ofe the sd-card. But as there is no entry for "Bunsenlabs (on sda1)" I guess it didn't use os-prober.
Or do you mean using grub-install --directory /path/to/grub/on/hd? I have never used this.

^^ I did as You told me unklar, and it worked. Thank You!
Leider habe ich immer noch nicht verstanden was da falsch war..
Is it a bug or my fault?

Naik --greetz

Last edited by Naik (2021-04-30 22:03:00)


"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen on GitHub

Offline

#11 2021-04-30 22:47:20

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,192

Re: Bunsenlabs on non-systemd Debian (antiX19)

Naik wrote:

^ I choose to let the installer write grub on the /boot partition ofe the sd-card.

If the sd-card is sdb, /boot is on sdb1, you can write grub to sdb1, if you don't want to boot from sdb...

But as there is no entry for "Bunsenlabs (on sda1)" I guess it didn't use os-prober.

When grub udates, it will run os-prober unles /etc/default/grub, contains the line: 'GRUB_DISABLE_OS_PROBER="true"'
If that is not the case the installation to sdb, when updating grub, should have made entry for your os on sda.

But, if you by misstake, when installing to sdb-disk, wrote grub to sda instead, it can only boot from sdb when the sd-card is inserted....

^^ I did as You told me unklar, and it worked. Thank You!
Leider habe ich immer noch nicht verstanden was da falsch war..
Is it a bug or my fault?

Probably you made an overwrite of grub... But, chroot os a wonderfull thing to have acess to!

Edit: do you mix up installing grub and writing grub code?

Last edited by rbh (2021-04-30 22:59:24)


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#12 2021-04-30 22:57:06

manyroads
Member
From: around here, somewhere
Registered: 2019-04-16
Posts: 102
Website

Re: Bunsenlabs on non-systemd Debian (antiX19)

A tip of my hat to all who knew!


Pax vobiscum,
Mark Rabideau - http://many-roads.com  Professional Genealogist
dwm & i3wm on arch ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

Offline

#13 2021-05-01 06:58:22

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 1,554

Re: Bunsenlabs on non-systemd Debian (antiX19)

Naik wrote:

^^ I did as You told me unklar, and it worked. Thank You!
Leider habe ich immer noch nicht verstanden was da falsch war..
Is it a bug or my fault?

It was a BUG from March of this year and it occurred with those users who use multiple disks in their system.

Bob Proulx describes it (to my understanding) as debconf being misused as a registry.
Hence the --reconfigure command because that is the only thing that corrects the problem.  wink

Offline

#14 2021-05-05 07:28:40

Naik
Member
From: Lipsia
Registered: 2015-10-03
Posts: 298

Re: Bunsenlabs on non-systemd Debian (antiX19)

Hey!
thanks again..
I found that I actually reconfigured Grub too well.. kind of.
It turned out that when grub was updated it was messed up because the LUKS container has a different UUID than the filesystem it conains and since the later was decrypted and mounted when I reinstalled AND rewrote GRUB it didn't honour the encryption part at all..
and I had to manually update the /etc/default/grub and /boot/grub/grub.cfg to get everything in place.

But now there is another problem with screen estate:
I get only 1024x768px resolution although my Laptop display is capable of handling 1280x800px. All intel driver packages are up to date.
Is there anything I can do about it?

naik --greetz


"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen on GitHub

Offline

#15 2021-05-05 09:50:05

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 1,554

Re: Bunsenlabs on non-systemd Debian (antiX19)

Naik wrote:

But now there is another problem with screen estate:
I get only 1024x768px resolution although my Laptop display is capable of handling 1280x800px. All intel driver packages are up to date.
Is there anything I can do about it?

Why not do it as I have described here.
If you are alone at the computer, then you can also put the script in your $HOME.

https://forums.bunsenlabs.org/viewtopic … 89#p111389

Offline

#16 2021-05-05 15:40:21

Naik
Member
From: Lipsia
Registered: 2015-10-03
Posts: 298

Re: Bunsenlabs on non-systemd Debian (antiX19)

^ I'd love to do that, but Arandr shows only 1024x768 and 800x600 as possible resolutions, so it I gues it must be a problem with the video-driver in use.


"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen on GitHub

Offline

#17 2021-05-06 09:58:21

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 1,554

Re: Bunsenlabs on non-systemd Debian (antiX19)

^I have zero idea about your video driver....  hmm

But, you could test this solution.

Offline

Board footer

Powered by FluxBB