You are not logged in.
it was a usb drive issue (funny as the checksum passed okay)
Offline
Thanks for the follow-up. So, installed and running? care to give us some feedback?
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Yes, installed and up and running.
First impressions are very good, I'm using a 10 Yr old laptop and it runs really well (ssd drive helps). I have used helium for a while and lithium feels slick in comparison.
One problem so far is putting the laptop into suspend - bringing it back up leads to a frozen system. Not sure why? Any ideas?
Generally happy though, well done bunsenlabs.
Offline
Also, I just realised my laptop is 64bit. Would I be better off installing the 64bit version, I only have 4GB of Ram but I guess it would give me more software choice as I notice a few programs now only come packaged as 64bit.
Offline
Hello, good evening, I can install Lithium 64bits on a 32-bit PC with PAE kernel.
:~$ uname -a
Linux debian 4.9.0-12-686-pae #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) i686 GNU/Linux
Offline
Hello, good evening, I can install Lithium 64bits on a 32-bit PC with PAE kernel.
:~$ uname -a
Linux debian 4.9.0-12-686-pae #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) i686 GNU/Linux
No, you cannot. You can install 32 bit to a 64 bit system, not the other way around. uname -a for a 64 bit system would look like something like this...
rachel@TyrellCorp:~$ uname -a
Linux TyrellCorp 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Installed the 32bit-RC1 to a medion akoya E1210 netbook from 2008 (rebranded MSI Wind U100) without any real problems. Awesome.
The machine has been upgraded to 2GB RAM and an SSD.
Only the bl-welcome script didn't restart itself after the apt update/upgrade (as promised). Manual run worked fine. Installed the "All" meta-package, no problems yet.
Found a .dillo folder but no dillo installed. That was before the full bl-welcome run adding the All meta-package, so I don't know if it is there on purpose or a left-over from development.
Only the Super-x menu takes an astonishing long time to pop up .. never under 2 seconds, even with subsequent runs back-to-back. Not an issue, it just feels weird when the file browser opens faster than a (presumably simple) exit menu.
Offline
Thanks for the feedback!
Only the bl-welcome script didn't restart itself after the apt update/upgrade (as promised).
Thank you, you found a bug. A command was wrongly quoted. Fix pushed and should be released soon.
Found a .dillo folder but no dillo installed. That was before the full bl-welcome run adding the All meta-package, so I don't know if it is there on purpose or a left-over from development.
It's there so that if dillo is later installed it will be able to post to the BL forums out of the box. (colours slightly tweaked too) Dillo is the default browser in the CD iso, and worth considering by people with slow hardware. It has no support for javascript however, so Firefox might be inescapable.
Only the Super-x menu takes an astonishing long time to pop up .. never under 2 seconds, even with subsequent runs back-to-back.
That's very weird. On my 2006 Panasonic Centrino/1GB laptop it comes up in less than a second. How about the command-line utility, in a terminal: 'bl-exit'? Is that fast?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Thank you, you found a bug.
I know, it's an annoying super power. ;-)
It's there so that if dillo is later installed it will be able to post to the BL forums out of the box. (colours slightly tweaked too) Dillo is the default browser in the CD iso,
I found some forums posts on dillo in the mean time, it's a browser I never used before. Nice choice.
How about the command-line utility, in a terminal: 'bl-exit'? Is that fast?
Yes, the command-line is fast .. as pretty much always.
I see "yad" rising to the top of top before the dialog pops up. Maybe the GTK+ init is taking so long?
Btw, I like the new dialog - it's pretty, good to understand and use. And maybe that little delay is good to avoid unwanted initiations. Super-x is a bit too easy to hit for a "once in a day" function - at least for my taste. On my old xubuntu system I have Super-x linked to "open terminal" because of the proximity of the keys. We'll see how I customize my BL install after the switch-over.
Offline
You can test to install package "bunsen-exit-python" instead (will remove bunsen-exit).
With bunsen-exit-python, you can add Hibernate and Hybrid Sleep if that works on your harware.
// 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
Is this still available? I noticed that the link in the OP stopped working a couple of weeks ago and I assumed it had been withdrawn for tweaking, it still doesn't work though, will it be back?
Offline
Is this still available? I noticed that the link in the OP stopped working a couple of weeks ago and I assumed it had been withdrawn for tweaking, it still doesn't work though, will it be back?
Do you need the release-candidate when there is the forst releas of stable lithium iso? (Links on https://www.bunsenlabs.org/installation.html, releasinfo on [STABLE RELEASE] BunsenLabs Lithium Official ISOs
// 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
(Note added to the top post.)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Thanks for the response, I assumed that the thread OP would be rolling until the final release, but now I notice that [FINISHED] has been added to the title.
You've done a great job in getting the size down, it seems a bit quaint in this day and age to try and produce CD sized ISO's, but I quite like the tradition (do any distros other than Debian still bother?). The 64bit version uses swap a great deal on my 3Gb laptop and I was wondering if the 32bit version use the memory better.
Offline
^Yes indeed, getting down under 700MB was pretty hard this time and all the tricks had to be brought out...
Next release, Beryllium? Let's wait and see...
Memory handling is just whatever Debian decides - we don't tweak anything there. But the non-PAE kernel that comes in the 32bit iso might behave differently.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Memory handling is just whatever Debian decides - we don't tweak anything there. But the non-PAE kernel that comes in the 32bit iso might behave differently.
I haven't done any extensive comparisons, but it seemed that Helium used swap a lot less on that machine - at least it has an SSD, it would slow to a crawl with a disk hardrive.
It has a 64bit processor and I've heard that 32bit runs a bit slower on these, but if it handles memory better then the trade-off will be worth it
Last edited by brogild (2020-08-08 10:01:08)
Offline
Thanks for the response, I assumed that the thread OP would be rolling until the final release, but now I notice that [FINISHED] has been added to the title.
You've done a great job in getting the size down, it seems a bit quaint in this day and age to try and produce CD sized ISO's, but I quite like the tradition (do any distros other than Debian still bother?). The 64bit version uses swap a great deal on my 3Gb laptop and I was wondering if the 32bit version use the memory better.
The problem is that the kernel version is different. Different kernel versions can't be expected to behave in the same way unless you understand and configure a myriad of aspects, and build them using the same configs, etc etc . Likely nothing would change at all when going 32bit again.
There is really no good reason to remain on 32bit nowadays unless you have very specific requirements or no hardware support.
The first thing I'd try is to adjust swappiness https://wiki.archlinux.org/index.php/Swap#Swappiness to 0-5 on your machine -- at first, without making the setting permanent --, and then toggling swap off and on to clear it, and then observe future swapping behaviour:
sudo sysctl -w vm.swappiness=0
sudo swapoff -a
sudo swapon -a
If your system behaves weirdly, try moving the swappiness to 5, then 10.
Offline
johnraff wrote:Memory handling is just whatever Debian decides - we don't tweak anything there.
seemed that Helium used swap a lot less on that machine
There is a difference between Debian Stretch and Debian Buster. I think there is more that is autostarted in Buster.
you can browse the list of autostarted processes and disable those you do not need. More info aboout program systemctl here https://www.howtogeek.com/216454/how-to … ux-system/
You can manualey start processes you use very seldom.
I do not know if it is still possible to tweak "swapiness". There seems to be different opinions about that. I do not experince that my settings of swappines no longer is obeyed...
You can try.
As root, edit /etc/sysctl.conf. Add "vm.swappiness = 10". Default is 60.
How much ram du you have free, when it starts swapping?
Maybe you should open a new thread in "Basic help", if you need more help.
// 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
You're right, it might be as simple as altering the 'swappiness' so I'll try that. The machine, with my standard apps open, hovers at about 2Gb and then starts swapping at 2.5Gb. This is probably standard behaviour anyway and I wasn't really aware of these things until I had a conky on the desktop, it might not even be use of the swap that slows things down, ie it is filling up by going into sleep mode rather than during regular running.
Offline
There is really no good reason to remain on 32bit nowadays unless you have very specific requirements or no hardware support.
I'm 'experimenting' with this rather than having a firm requirement for it, so I don't a serious urge to open a thread elsewhere.
The installer hangs after the 'autoconfiguring network' stage and this happens whether I'm trying to connect via ethernet or wirlessly, and has happened on two different machines, possibly manually configuring works but I haven't tried that yet.
It installed ok without network (it's a bit fiddly to get around this), and had to add in the repositories afterwards. I am however missing the public key for the 'kelaino' repository, can I get hold of this somewhere, or can I find it on the install medium?
Offline