You are not logged in.

#1 2021-08-21 17:48:39

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

Errors in lithium-2.1 install iso

When installing with lithium-2.1:

N0 Debian repositorys can be verified and they are commented out by the installer!

The bl-welcome script is running. The terminal pops up but the script is aborted and the terminal is shut down, It goes very fast.

One has to manualy edit /etc/apt/sources.list, update and upgrade and laslt, remove ~/.config/bunsen/bl-setup, to get bl-welcome script autostart at login.


// 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

Online

#2 2021-08-21 18:28:01

Peregrino69
Member
Registered: 2016-03-11
Posts: 88

Re: Errors in lithium-2.1 install iso

rbh wrote:

When installing with lithium-2.1:

N0 Debian repositorys can be verified and they are commented out by the installer!

The bl-welcome script is running. The terminal pops up but the script is aborted and the terminal is shut down, It goes very fast.

One has to manualy edit /etc/apt/sources.list, update and upgrade and laslt, remove ~/.config/bunsen/bl-setup, to get bl-welcome script autostart at login.

OK so it wasn't my systems after all big_smile

A comment on the last point - I've not removed bl-setup. I've just added

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

and run update/upgrade. After next reboot system has booted to 4.19.0-17 (which before that wasn't even available) and bl-welcome has run as expected.

Offline

#3 2021-08-21 19:05:51

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

Re: Errors in lithium-2.1 install iso

Peregrino69 wrote:

I've just added

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

No security enabled?
Essential repos:

buster main contrib non-free  
debian-security/ buster/updates main contrib non-free

I prefer also:

buster-backports main contrib non-free  
buster-updates main contrib non-free  
buster-proposed-updates main contrib non-free

// 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

Online

#4 2021-08-21 19:18:40

Peregrino69
Member
Registered: 2016-03-11
Posts: 88

Re: Errors in lithium-2.1 install iso

rbh wrote:

No security enabled?

Usually has been enabled already, just the rest missing smile

Thanks for the suggestions. I've just done the bare minimum to get the new kernel running.

Offline

#5 2021-08-21 23:27:29

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

Re: Errors in lithium-2.1 install iso

Peregrino69 wrote:
rbh wrote:

No security enabled?

Usually has been enabled already, just the rest missing smile

Thanks for the suggestions. I've just done the bare minimum to get the new kernel running.

A good idea is to enable backports and there's a question for that in BL-Welcome. Enabling backports allow you to update the kernel to a more recent version as well as newer packages that were backported.


Real Men Use Linux

Offline

#6 2021-08-22 02:51:44

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,281
Website

Re: Errors in lithium-2.1 install iso

Part-way progress report.

I've just done an install on a VM from BL Lithium-2.1 iso, and it stopped at the "selecting mirror" stage.
Opening the messages on tty4 (Ctrl+Alt+F4, on a VM use "Send Key" or similar) showed something like (cannot copy/paste):
"https://deb.debian.org/debian buster has changed its {suite} value from Stable to Oldstable" and seemed to be waiting for some input.

It's possible to open a shell on tty2 or tty3 and while apt and apt-get are unavailable, there is cat and nano for file editing.
The installed system is on /target at this point, so it's possible to: 'nano /target/etc/apt/sources.list' and add the necessary lines by hand. (The original install screen is on tty1 or tty5.)

That's not enough though, the installer still decides the lines are invalid, and comments them out, so the only thing to do is to ignore the mirror error message, continue with the install, and fix /etc/apt/sources.list after installation, as Peregrino69 did.

I don't remember any such problem with our Helium iso when Debian Stretch went from Stable to Oldstable, but anyway this is clearly not an ideal situation. roll

More research is needed...

EDIT: This Debian bug might be related:
https://bugs.debian.org/cgi-bin/bugrepo … bug=931566

I guess, whatever it is, a new Lithium iso build will be necessary, maybe just with the same configs. That might pick up the new apt libraries and fix the issue in itself.

Last edited by johnraff (2021-08-22 04:13:36)


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#7 2021-08-22 11:07:08

Peregrino69
Member
Registered: 2016-03-11
Posts: 88

Re: Errors in lithium-2.1 install iso

DeepDayze wrote:

A good idea is to enable backports and there's a question for that in BL-Welcome. Enabling backports allow you to update the kernel to a more recent version as well as newer packages that were backported.

The original issue from dmontaine (https://forums.bunsenlabs.org/viewtopic.php?id=7760 is that bl-welcome doesn't run at all. I've experienced the same multiple times, and resolved it by adding the two repos to the already available security-repo.

I just did another VB installation, and this time bl-welcome actually run. System booted to 4.19.0-13. I allowed the update and backport addition. After reboot I got the 17-kernel, but backport repos were not added to sources.list.

I think that at least some of the repo problems with physical machines in my case has been due to flaky WiFi. A bit more rigorous testing would be needed to confirm tho'.

Offline

#8 2021-08-22 14:41:56

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,281
Website

Re: Errors in lithium-2.1 install iso

I forgot to say, but bl-welcome looks at the apt sources to check what Debian codename is being run - in this case it should be Buster and if the apt entries are missing it exits immediately.

Fix sources.list and you can run 'bl-welcome' in a terminal.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#9 2021-08-23 14:34:08

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

Re: Errors in lithium-2.1 install iso

johnraff wrote:

the installer still decides the lines are invalid, and comments them out, so the only thing to do is to ignore the mirror error message, continue with the install, and fix /etc/apt/sources.list after installation, as Peregrino69 did.

I don't remember any such problem with our Helium iso when Debian Stretch went from Stable to Oldstable, but anyway this is clearly not an ideal situation. roll

That Buster has gone from stable to oldstable, is no problem. It is correct.

I skipped some other comittment and did some test today.

Tried a new installation, got error on tty4:

Getting default hostname from rDNS lookup of autoconfigured adress [ip4-address]
getnameinfo() returned -2 (Name or service not known)
Getting default hostname from rDNS lookup of autoconfigured adress [ip6-address]
getnameinfo() returned -3 (Temporary failure in name resolution)

Extracted preseed.cfg from lithium-2.1-amd64.hybrid.iso, edited it:

d-i passwd/root-login boolean false
d-i passwd/user-default-groups string audio cdrom dip floppy video plugdev netdev scanner lpadmin systemd-journal
d-i mirror/country string manual
d-i mirror/protocol string http
d-i mirror/http/hostname string [server.ip.on.lan]
d-i mirror/http/directory string /debian
d-i mirror/https/proxy string
d-i apt-setup/use_mirror boolean true
d-i apt-setup/non-free boolean true
d-i apt-setup/contrib boolean true
d-i apt-setup/services-select multiselect updates
d-i apt-setup/local0/repository \
    string http://[server.ip.on.lan]/security.debian.org/debian-security/ bullseye-security main contrib non-free
d-i apt-setup/local0/comment string Debian security updates
d-i apt-setup/enable-source-repositories boolean false
d-i apt-setup/disable-cdrom-entries boolean true
d-i clock-setup/utc boolean false
d-i preseed/late_command string \
    apt-install bunsen-os-release bunsen-python-apt-template ;\
    in-target /usr/local/bin/bunsen_preseed ;\
    in-target rm -f /usr/local/bin/bunsen_preseed

Copied it to http://[server.ip.on.lan]/preseed.cfg
Booted lithium-2.1-amd64.hybrid.iso in Vitualbox-VM, with bridged nic.
Added boot parameter:" install url=http://[server.ip.on.lan]/preseed.cfg.

Saw on tty4, that i got error on dns-resolution, but installation ok.

In sources.list activated lines:

deb http://server.ip/debian/ buster main contrib non-free
deb http://server.ip/security.debian.org/debian-security bullseye-security main contrib non-free

Should have been secutity for buster :-) ...

BL-welcome script started.
After installation no problem ping bunsenlabs.org

Glanced through the logs,could not find any essential errors.

If you have provided a preseed.cfg in install iso, only way to override the directives in that, is to provide another preseed.cfg on the bootline.

Configured dhcp-server to give fix ip-adress, booting with server-preseed.. No DNS-error in tty4..., installation ok.

New test with normal installation and new mac-adress. DNS-error in log, ok to ping bunsenlabs.org, but debian repos inactivated.

I guess, whatever it is, a new Lithium iso build will be necessary, maybe just with the same configs. That might pick up the new apt libraries and fix the issue in itself.

If that does notfix it, maybe we have to concentrate on getting Beryllium out?
After all, there is a workaround with lithium-2.1 install iso...


// 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

Online

#10 2021-08-23 21:20:13

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

Re: Errors in lithium-2.1 install iso

Testing on hardware a couple of times (Lenovo Thinkpad T440s).
Pc both connected on cable and wifi, both default installation and specifying preseed.cfg on server.

Failure every time with default installation, success every time with preseed.cfg read from server.


// 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

Online

#11 2021-08-24 00:50:27

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

Re: Errors in lithium-2.1 install iso

Hopefully with beryllium a new, corrected preseed.cfg would be provided on the ISO to resolve this issue.


Real Men Use Linux

Offline

#12 2021-08-24 01:27:28

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,281
Website

Re: Errors in lithium-2.1 install iso

rbh wrote:
johnraff wrote:

the installer still decides the lines are invalid, and comments them out, so the only thing to do is to ignore the mirror error message, continue with the install, and fix /etc/apt/sources.list after installation, as Peregrino69 did.
I don't remember any such problem with our Helium iso when Debian Stretch went from Stable to Oldstable, but anyway this is clearly not an ideal situation. roll

That Buster has gone from stable to oldstable, is no problem. It is correct.

Of course the Debian Buster transition is correct - I meant that the debian-installer hang which appears to result from it is not ideal!

Of course it is yet to be determined if that really is the cause, but the apt bug I previously linked to, along with the last message on tty4 when the installer hangs (cannot copy/paste):
"https://deb.debian.org/debian buster has changed its {suite} value from Stable to Oldstable"
suggest that it this might be.

I skipped some other comittment and did some test today.
Extracted preseed.cfg from lithium-2.1-amd64.hybrid.iso, edited it:

d-i passwd/root-login boolean false
d-i passwd/user-default-groups string audio cdrom dip floppy video plugdev netdev scanner lpadmin systemd-journal
d-i mirror/country string manual
d-i mirror/protocol string http
d-i mirror/http/hostname string [server.ip.on.lan]
d-i mirror/http/directory string /debian
d-i mirror/https/proxy string
d-i apt-setup/use_mirror boolean true
d-i apt-setup/non-free boolean true
d-i apt-setup/contrib boolean true
d-i apt-setup/services-select multiselect updates
d-i apt-setup/local0/repository \
    string http://[server.ip.on.lan]/security.debian.org/debian-security/ bullseye-security main contrib non-free
d-i apt-setup/local0/comment string Debian security updates
d-i apt-setup/enable-source-repositories boolean false
d-i apt-setup/disable-cdrom-entries boolean true
d-i clock-setup/utc boolean false
d-i preseed/late_command string \
    apt-install bunsen-os-release bunsen-python-apt-template ;\
    in-target /usr/local/bin/bunsen_preseed ;\
    in-target rm -f /usr/local/bin/bunsen_preseed

Thank you for working on this. Apart from the hostname change I notice you switched from https to http protocol and disabled utc time. What do you consider to be the change in preseed.cfg which fixed the issue for you?

Anyway:

I guess, whatever it is, a new Lithium iso build will be necessary, maybe just with the same configs. That might pick up the new apt libraries and fix the issue in itself.

If that does notfix it, maybe we have to concentrate on getting Beryllium out?
After all, there is a workaround with lithium-2.1 install iso...

I'll try a new iso build with existing configs very soon - possibly today.
If that fixes the issue (at least the issue as it appeared at this end) then we should be able to put it on the server along with an announcement in a few days.

Otherwise, I agree - any extensive development work on the Lithium iso would hold back Beryllium, which should have priority.

I'm already putting in significant time on Beryllium but there are still a number of small (and a couple of medium-sized) issues to fix. And we eagerly await the new graphics stack. smile


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#13 2021-08-24 01:36:33

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

Re: Errors in lithium-2.1 install iso

johnraff wrote:
rbh wrote:
johnraff wrote:

the installer still decides the lines are invalid, and comments them out, so the only thing to do is to ignore the mirror error message, continue with the install, and fix /etc/apt/sources.list after installation, as Peregrino69 did.
I don't remember any such problem with our Helium iso when Debian Stretch went from Stable to Oldstable, but anyway this is clearly not an ideal situation. roll

That Buster has gone from stable to oldstable, is no problem. It is correct.

Of course the Debian Buster transition is correct - I meant that the debian-installer hang which appears to result from it is not ideal!

Of course it is yet to be determined if that really is the cause, but the apt bug I previously linked to, along with the last message on tty4 when the installer hangs (cannot copy/paste):
"https://deb.debian.org/debian buster has changed its {suite} value from Stable to Oldstable"
suggest that it this might be.

I skipped some other comittment and did some test today.
Extracted preseed.cfg from lithium-2.1-amd64.hybrid.iso, edited it:

d-i passwd/root-login boolean false
d-i passwd/user-default-groups string audio cdrom dip floppy video plugdev netdev scanner lpadmin systemd-journal
d-i mirror/country string manual
d-i mirror/protocol string http
d-i mirror/http/hostname string [server.ip.on.lan]
d-i mirror/http/directory string /debian
d-i mirror/https/proxy string
d-i apt-setup/use_mirror boolean true
d-i apt-setup/non-free boolean true
d-i apt-setup/contrib boolean true
d-i apt-setup/services-select multiselect updates
d-i apt-setup/local0/repository \
    string http://[server.ip.on.lan]/security.debian.org/debian-security/ bullseye-security main contrib non-free
d-i apt-setup/local0/comment string Debian security updates
d-i apt-setup/enable-source-repositories boolean false
d-i apt-setup/disable-cdrom-entries boolean true
d-i clock-setup/utc boolean false
d-i preseed/late_command string \
    apt-install bunsen-os-release bunsen-python-apt-template ;\
    in-target /usr/local/bin/bunsen_preseed ;\
    in-target rm -f /usr/local/bin/bunsen_preseed

Thank you for working on this. Apart from the hostname change I notice you switched from https to http protocol and disabled utc time. What do you consider to be the change in preseed.cfg which fixed the issue for you?

Anyway:

I guess, whatever it is, a new Lithium iso build will be necessary, maybe just with the same configs. That might pick up the new apt libraries and fix the issue in itself.

If that does notfix it, maybe we have to concentrate on getting Beryllium out?
After all, there is a workaround with lithium-2.1 install iso...

I'll try a new iso build with existing configs very soon - possibly today.
If that fixes the issue (at least the issue as it appeared at this end) then we should be able to put it on the server along with an announcement in a few days.

Otherwise, I agree - any extensive development work on the Lithium iso would hold back Beryllium, which should have priority.

I'm already putting in significant time on Beryllium but there are still a number of small (and a couple of medium-sized) issues to fix. And we eagerly await the new graphics stack. smile

Good for at least checking this as this bug might bite in Beryllium and getting this one fixed just might help with Beryllium.

Last edited by DeepDayze (2021-08-24 01:36:49)


Real Men Use Linux

Offline

#14 2021-08-24 05:44:13

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

Re: Errors in lithium-2.1 install iso

johnraff wrote:

What do you consider to be the change in preseed.cfg which fixed the issue for you?

The fix - I think - is that D-I dont need to make any DNS-work.
It seems its no reason try with ip-address https;//151.101.86.132 (deb.debian.org), as the service is not possible to browse by the ip-address.
The server says:

The server deb.debian.org does not have packages itself, but the name has SRV records in DNS that let apt in stretch and later find places.

To use it with a sufficiently recent apt,

Last edited by rbh (2021-08-24 05:46:09)


// 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

Online

#15 2021-08-24 06:36:25

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,281
Website

Re: Errors in lithium-2.1 install iso

I've just rebuilt a Lithium iso and the problem did not occur - everything seems OK.
My conviction - that the issue was with an apt library that was subsequently (post 20200722) fixed - has become stronger.

I'll build an i386 iso too and ask @twoion to put them on the BL server so you can try them.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#16 2021-08-24 08:32:23

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

Re: Errors in lithium-2.1 install iso

Also an network preseed with https disabled but else asBL preseed, worked.

The installer could not handle https:


// 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

Online

#17 2021-08-24 08:37:21

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

Re: Errors in lithium-2.1 install iso

Actually there is no need to use https in preseed.cfg..
Why not use "deb http://deb.debian.org/debian unstable main" as http://deb.debian.org/ suggests?

Last edited by rbh (2021-08-24 08:37:36)


// 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

Online

Board footer

Powered by FluxBB