You are not logged in.
- Topics: Active | Unanswered
#1 Re: Installation » No terminals after installation of Excalibur » 2026-01-09 12:59:06
Two more observations.
The first one:
Hibernate and suspend don't work properly either (no matter if from within the DE or the login greeter).
The laptop seems to go into both states but trying to come out of it will only give me a black screen and the thing doesn't react at all. No DE, no console, nothing.
The other one:
I used the same netinstall.iso as before to install Excalibur on another partition on the same laptop.
This time I chose automated install and SysVinit (contrary to expert install and runit on the first installation).
As I didn't get to choose a DE, the installer gave me the default XFCE-environment.
Consoles work right of the box as they should.
No clue if it is because of XFCE or the automated install process.
I don't believe that it's because of a different init-system....but who knows.
What remains the same is the issue that going to a console will kill the DE-session and dropping me to the login-greeter when trying to get back CTRL-ALT-F7.
Also, Hibernate and suspend don't work here either.
It could be because this laptop might need some work to get this running. Or Excalibur has problems finding the correct settings to make it work.
With Chimaera on my other laptop, it may take weeks before I boot the system in a normal way as I use hibernation all the time after a day's work.
(Both laptops are about the same age and from the same era.)
Conclusion so far:
With the same iso, two different install methods will give me different results with regard to consoles working (or not).
#2 Re: Installation » No terminals after installation of Excalibur » 2026-01-08 00:38:41
Well if you do not count being missing the proposed-updates repository which gives newer kernel then you are correct.
Apart from "aptitude update & upgrade" I just stuck with the defaults in /etc/apt/sources.list that the installation of Excalibur came with, assuming it would provide stable packages for this new installation.
...I had thought that was the default behaviour it logging you out when switching to the virtual consoles but am not totally certain
Could be if it has been changed.
But that's the first time I have ever experienced this as this does not happen with my Chimaera installation on my working machine nor have I ever seen this on Debian installations that I've had in the past.
#3 Re: Installation » No terminals after installation of Excalibur » 2026-01-07 21:20:02
Have you tried all different ttyN ?
Yes.
Traditionally graphical session is at tty7, but I have an inclination that sddm deviates from that
With lightdm it has always been tty 7 as well (as it has been on my working machine, too).
I would guess you have keyboard shortcuts for at least tty1-tty10 ...
I can leave the desktop session with CTRL-ALT-F[8-12], too, but then I don't get a login prompt. Just a blinking cursor in the upper right corner. I don't really need them anyway. Having tty1-6 is more than enough for me.
But still, with CTRL-ALT-F[1-6 + 8-12] the desktop session gets killed and with CTRL-ALT-F7, I'm always back at the lightdm login screen.
To clarify words... using CTRL-ALT-F(1-6) doesn't open a terminal. It opens a console...
Thanks for the correction.
In all of my previous posts thus far within this thread, whenever I typed "terminal" I was actually referring to "console".
Sorry for the confusion.
what kernel are we talking about?
That would be...
6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/LinuxThe most recent kernel for Excalibur that was being installed when I set up the system a few days ago.
#4 Re: Installation » No terminals after installation of Excalibur » 2026-01-06 18:13:00
1. Does the directory /etc/sv/ contain subdirectories named getty-tty1
Yes
2. Did the command create links in /etc/service/ named getty-tty2
At first: No.
Then I discovered that I had typed it not exactly as it is being displayed now (I had used quotation marks around parts of the command before and I could have sworn that they had been there yesterday in your 2nd post as I had typed in the command character by character).
Anyway, now that I removed the faulty link and re-typed this command again I can see all the links in /etc/service.
So now the answer is Yes.
3. Do tty 2 through 6 still show a blank screen with a cursor, and no login prompt?
They did before.
Now that I have re-typed the command, they all show a login prompt now.
Thanks a lot for helping me solve this misconfiguration so far.
One issue still remains though:
When I go to any terminal from a desktop session, the attempt to return to the desktop will still lead me to the login greeter of lightdm.
The desktop session is basically killed and I wonder why.
#5 Re: Installation » No terminals after installation of Excalibur » 2026-01-05 22:43:23
For several tries, I didn't even see that login prompt.
Now I do and pressing <Enter> drops me to a login prompt.
What could I try to enter now?
Btw... I noticed that after having logged in and being at the prompt, there is the following message showing up (had to type it here by hand on my working machine):
[583.821905] perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate 79750I then have to press <Enter> to get to clean prompt again.
This message will eventuall repeat but will have different numbers.
No clue about that and I have never experienced this before.
I also tried to switch from runit to openrc (another thing that worked flawlessly under Chimaera) and after a bunch of messages from rc-update, the last message read:
Error: udev is the name of a real and virtual service.Such stuff is way beyond me and if I were not here to contribute to Devuan within the limits of my capabilities, I would have already either tried a reinstall or switched to a different version.
(Have also tested MX Linux a few weeks back which worked very well on this machine. But I'd like to see Devuan 6 do just as well.)
#6 Re: Installation » No terminals after installation of Excalibur » 2026-01-05 19:57:01
It seems that on devuan, to get tty2-6, runit requires a little bit of manual setup.
Maybe on Excalibur.
Runit (and OpenRc) worked on Chimaera out of the box and without a single issue.
Note that tty1 *should* be working by default
There are only some startup messages visible, the last two being...
...
Starting Light Display Manager: lightdm.
Starting network connection manager: NetworkManager.So still not a single usable terminal.
...*as well as switching back to the gui on tty7.
Rather no.
It takes me back to a GUI but that will be the login prompt of the greeter.
The previous login into my DE is being reset.
But thinking about it, that could have already happened when trying to switch to a terminal.
I will get back after having tried out your suggestion for setting up that symbolic link.
Edit:
ln -s /etc/sv/getty-tty[2-6] /etc/service/...didn't change anything, except for I don't even get to the greeter anymore. (Although that has been the case before quite a few times.)
I am willing to try other approaches just for the benefit of improving future versions of Excalibur.
Unless someone would like me to try other settings/changes (in case I ever get to the DE again), I would do a reinstall of Excalibur, maybe with different settings (e.g. a different init system).
(If all fails, I will go for Daedalus.)
#7 Re: Installation » No terminals after installation of Excalibur » 2026-01-05 10:08:21
I use runit (as on my working machine).
This is the content of inittab:
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin --force
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin --force
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
#
# or on a USB serial line
#U0:23:respawn:/sbin/getty -L ttyUSB0 9600 vt100
# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
# Example for systemd-nspawn
# Only /dev/console exists inside nspawn, so we need a getty on that.
# Also make sure to comment out the gettys on tty* above.
#C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud console 115200,38400,9600The booting of the most recent Excalibur installation has some hiccups on this machine.
The booting process ended with a blank screen and nothing else happening. Had to pull the plug to end it. After the third try, it finally booted to the lightdm greeter although I hadn't changed a thing.
This had already happened yesterday, too.
The previous installation with the live.iso didn't give me this behavior. Although I had a problem with language settings and locale there, it would at least boot in a dependable way every single time.
Not so here. 
(I can't deny that I get slowly but increasingly frustrated with the current stable release.
This and some other things lead me to think that Devuan 6 is not (yet) as flawless as Chimaera was.)
#8 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2026-01-04 21:27:17
Thanks for your input.
Although it would not be good news if bga failures were the cause of my laptop's problem as it is my machine for daily work.
As long as it works (apart from 3-D games) I will not take it apart and mess with it, until I switch to another laptop altogether.
#9 Re: Installation » Can't change system language in Devuan 6 XFCE » 2026-01-04 21:14:19
I finally solved the problem by installing from scratch with the most current netinstall.iso.
Language and locale now work as they are supposed to.
(But now I encountered a problem with non-accessible terminals; (if interested, see this thread).
#10 Installation » No terminals after installation of Excalibur » 2026-01-04 21:05:07
- switching2Devuan
- Replies: 16
After having had problems setting the system language and locale on an installation of Excalibur (devuan_excalibur_6.0.0_amd64_desktop-live.iso) on an older spare laptop via a live.iso (see this thread, I decided to start from scratch again and chose the most current netinstall.iso (expert install) as I had done with Chimaera 3.5 years ago on the laptop that I use for daily work.
(Used version: devuan_excalibur_6.1.0_amd64_netinstall.iso)
The install itself went smoothly and I was able to boot the machine from the grub menu (had to use the "nomodeset" option though). Language and locale selection work as selected (contrary to the install from live.iso).
But I noticed that there is not a single terminal available when using CTRL-ALT-F(1-6). Only a black screen with a rapidly blinking cursor.
Even worse:
When logging into the installed DE (LXDE) and then trying to get to a terminal with CTRL-ALT-F(1-6), pressing CTRL-ALT-F7 will not return me to my desktop-session but kick me back out to the login-prompt (lightdm).
Has anyone experienced this before?
Or does anyone know what the problem is and how to solve it?
If more specific information is necessary, I will be happy to provide it.
Thanks for any input.
#11 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2026-01-03 23:25:53
failing hdd/ssd?
I would almost say "impossible" but I choose "highly unlikely", since the system (as already described in earlier posts) is running smooth and stable with many different programs for many, many hours UNTIL I start a game that uses 3-D-graphics.
Even then, I sometimes am able to play for an hour until the whole system freezes with the last 1 second of sound running in an infinite loop.
Upon rebooting and starting the same game again, it may happen after a few minutes. Same with another game.
But not limited to that, as I have also experienced this system freeze while watching a video or even just listening to music (I haven't experienced the latter two in quite a while though).
#12 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2026-01-02 19:43:21
Although I hadn't marked this topic as [SOLVED] yet, it is solved now.
From my perspective in the least preferable way, unfortunately.
I just booted Win 7 and tried to watch a video. Vlc started and a few seconds later, I found myself staring at the grub boot menu again.
Rebooted and tried to start a 3D-shooter. Same result. Also in a third try with a flight simulator.
In each case the whole system crashed in an instant and the machine rebooted.
I hate to confirm it but it indeed looks like a problem with the integrated graphics chipset.
At least under Devuan, I can still watch videos and play a game with 3-D graphics, knowing that the system might or might not freeze.
So the problem is not related to Devuan or any software.
Thanks for all the input in this thread.
#13 Re: Installation » Some Concerning Bugs » 2026-01-02 11:36:56
onedevone wrote:
Ext4 was designed for spinning drives. Nobody is using it anymore. It's an ancient history.
Quite an arrogant and self-centered assumption.
Just because you don't use it doesn't mean that everybody else doesn't use it as well.
#14 Re: Installation » Can't change system language in Devuan 6 XFCE » 2026-01-02 01:15:37
I have the same problem on a second notebook after an install to hd from a live-system of Devuan 6.0 from a usb-stick.
I ran "dpkg-reconfigure locales" to set it to my language-setting "de_DE.UTF-8" but it was already set from the install.
Still, I get the following message when opening a terminal:
bash: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): No such file or directory
bash: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): No such file or directoryWhen running "localehelper", I get this:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = (unset),
LC_NUMERIC = (unset),
LC_COLLATE = (unset),
LC_TIME = (unset),
LC_MESSAGES = (unset),
LC_MONETARY = (unset),
LC_ADDRESS = (unset),
LC_IDENTIFICATION = (unset),
LC_MEASUREMENT = (unset),
LC_PAPER = (unset),
LC_TELEPHONE = (unset),
LC_NAME = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").And "locale -v" gives me this message:
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=I don't know why it can't be set as on my main working machine (Devuan 4.0).
Maybe a bug?
Let me know if you need me to provide more informaton.
If everything fails I could also try a new install from the netinstall.iso and see if it works any better.
#15 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2026-01-01 23:35:34
* Except for the manual installation of 2 games that i wanted to try out ...
These were two other games that are very small in size and which I manually installed via aptitude in order to see what they were about.
The "games" during which the freezes occured were 3-D-shooters of which one was configured to be used with Wine and the other one extracted in a folder and run natively under Linux.
you may want to consider that there must be something going on with the combination [game/hardware].
That would be the first thing for me to consider, had the two games not been running for well over a year without any problems.
Also, system freezes have occured as well when watching videos with vlc or listening to music with audacious.
What those three scenarios have in common is sound.
But the freezes are rather irregular as I can also listen to music and nothing freezes at all (uptime today is 11+ hours without any incident).
Aside from that, I never had any problems with activities involving other programs.
Will now check playing the games over Win 7 just to confirm that it hopefully is not hardware-related.
#16 Re: Hardware & System Configuration » [SOLVED] Strange Grub behavior after new kernel installation » 2026-01-01 16:58:38
If you have not cleaned your apt cache you should be able to install the -36 version of the kernel still in there
I clean it from time to time. Kernel -37 is still there but -36 is gone.
No big deal as I will stick to -35 until a newer kernel is available.
#17 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2026-01-01 10:55:45
you still could check if on the windows 7 side you have similar problems
Already had the same thought a while ago but never did it so far.
Have used Win 7 only for 4 applications and since I managed to run 3 via WINE and one natively, I haven't used Windows at all for at least 2 years now.
But I will do that over the next few days, starting today.
Will report back on that in a few days.
Meanwhile, without playing a game, my system has been running smooth as always (yesterday 15 hours straight).
#18 Re: Hardware & System Configuration » [SOLVED] Strange Grub behavior after new kernel installation » 2026-01-01 10:46:18
Looks like you do a BIOS MBR...
That's correct.
Then once confirmed sudo grub-install /dev/sda to have it do a new install.
That did it.
In addition to kernel -35, the -37-version is now correctly listed in the boot menu.
Thanks a lot. 
Still interesting how grub got so twisted that it would not enter a newly installed kernel after "grub-update" as it has always done.
Although the system is running with this new kernel, I already experienced what was described in the link to the bug report (2nd post; thanks to greenjeans). All virtual consoles are unusable (except for the first one).
So I might purge this kernel and solely rely on the -35-version.
Anyway....problem solved. Thanks again.
#19 Re: Hardware & System Configuration » [SOLVED] Strange Grub behavior after new kernel installation » 2026-01-01 00:45:48
What makes you think that? Have you looked into the file and confirmed this?
Yes, I have. Otherwise I could not have known that kernel 5.10.0-37 was in the cfg-file.
Also posting the output of the update-grub command would be helpful...
Here you go:
sudo update-grub
[sudo] Passwort für mt:
Generating grub configuration file ...
Found background image: splash.png
Found linux image: /boot/vmlinuz-5.10.0-37-amd64
Found initrd image: /boot/initrd.img-5.10.0-37-amd64
Found linux image: /boot/vmlinuz-5.10.0-35-amd64
Found initrd image: /boot/initrd.img-5.10.0-35-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 7 on /dev/sda1
Found Devuan GNU/Linux 5 (daedalus) on /dev/sda9
doneWhat is the matter with sudo apt autoremove which would have done it by removing the third oldest entry the -35 version leaving the last two version that were installed by apt..
It was my personal choice to purge the .36-version.
In fact I usually purge the oldest version which in this case would indeed have been the -35-kernel but for some reason I decided to purge -36.
I've always used aptitude on the command line for installing, upgrading, purging etc.
As far as I know, aptitude doesn't know "autoremove". But it has an "--purge-unused"-option (which I have never used so far.
If I want to completely get rid of a package, I use "sudo aptitude purge package" which does the trick for me.
Anyway, as you can in the output of update-grub, the -37-kernel is recognized and enterd into the grub.cfg file but grub still does not show it in the boot menu.
And I have no clue why that is, nor how to fix it.
#20 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2025-12-31 21:42:43
Can you narrow down when this started with respect to package upgrades (if any)?
With the hint from "rbit", I searched the logs. As the freezes started occuring sometime by the end of november, I only looked for entries that occured in november (starting november 1st):
Start-Date: 2025-11-01 12:51:04
Requested-By: mt (1074)
Upgrade: xserver-xorg-core:amd64 (2:1.20.11-1+deb11u16, 2:1.20.11-1+deb11u17), python-pip-whl:amd64 (20.3.4-4+deb11u1, 20.3.4>
End-Date: 2025-11-01 12:51:53
Start-Date: 2025-11-04 12:51:18
Requested-By: mt (1074)
Upgrade: gimp-data:amd64 (2.10.22-4+deb11u3, 2.10.22-4+deb11u4), libdcmtk15:amd64 (3.6.5-1+deb11u4, 3.6.5-1+deb11u5), gimp:amd64 (2.10.22-4+deb11u3, 2.10.22-4+deb11u4), libgimp2.0:amd64 (2.10.22-4+deb11u3, 2.10.22-4+deb11u4)
End-Date: 2025-11-04 12:52:00
Start-Date: 2025-11-05 19:27:50
Requested-By: mt (1074)
Upgrade: bind9-host:amd64 (1:9.16.50-1~deb11u3, 1:9.16.50-1~deb11u4), bind9-dnsutils:amd64 (1:9.16.50-1~deb11u3, 1:9.16.50-1~deb11u4), bind9-libs:amd64 (1:9.16.50-1~deb11u3, 1:9.16.50-1~deb11u4)
End-Date: 2025-11-05 19:28:06
Start-Date: 2025-11-05 20:39:39
Requested-By: mt (1074)
Install: vectoroids:amd64 (1.1.0-15+b1)
End-Date: 2025-11-05 20:39:46
Start-Date: 2025-11-05 20:43:09
Requested-By: mt (1074)
Install: torus-trooper-data:amd64 (0.22.dfsg1-12, automatic), libbulletml0v5:amd64 (0.0.6-7, automatic), torus-trooper:amd64 (0.22.dfsg1-12+b1), libgphobos1:amd64 (10.2.1-6, automatic)
End-Date: 2025-11-05 20:43:15
Start-Date: 2025-11-14 18:24:25
Requested-By: mt (1074)
Upgrade: libarchive13:amd64 (3.4.3-2+deb11u2, 3.4.3-2+deb11u3), firefox-esr-l10n-de:amd64 (140.4.0esr-1~deb11u1, 140.5.0esr-1~deb11u1), firefox-esr:amd64 (140.4.0esr-1~deb11u1, 140.5.0esr-1~deb11u1)
End-Date: 2025-11-14 18:25:00
Start-Date: 2025-11-18 17:34:05
Requested-By: mt (1074)
Upgrade: gstreamer1.0-gl:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), thunderbird:amd64 (1:140.4.0esr-1~deb11u1, 1:140.5.0esr-1~deb11u1), libgstreamer-gl1.0-0:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), gstreamer1.0-alsa:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), gir1.2-gst-plugins-base-1.0:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), gstreamer1.0-x:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), gstreamer1.0-plugins-base:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), libgstreamer-plugins-base1.0-0:amd64 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4), libgstreamer-plugins-base1.0-0:i386 (1.18.4-2+deb11u3, 1.18.4-2+deb11u4)
End-Date: 2025-11-18 17:34:56
Start-Date: 2025-11-23 11:53:44
Requested-By: mt (1074)
Upgrade: gir1.2-javascriptcoregtk-4.0:amd64 (2.48.5-1~deb11u1, 2.50.1-1~deb11u1), gir1.2-webkit2-4.0:amd64 (2.48.5-1~deb11u1, 2.50.1-1~deb11u1), libjavascriptcoregtk-4.0-18:amd64 (2.48.5-1~deb11u1, 2.50.1-1~deb11u1), libwebkit2gtk-4.0-37:amd64 (2.48.5-1~deb11u1, 2.50.1-1~deb11u1)
End-Date: 2025-11-23 11:54:06
Start-Date: 2025-11-23 21:44:17
Requested-By: mt (1074)
End-Date: 2025-11-23 21:44:18
Start-Date: 2025-11-23 21:44:45
Requested-By: mt (1074)
Remove: python3-pyparsing:amd64 (2.4.7-1), python3-packaging:amd64 (20.9-2), python3-gpg:amd64 (1.14.0-1+b2), torbrowser-launcher:amd64 (0.3.3-6)
End-Date: 2025-11-23 21:45:05
Start-Date: 2025-11-23 22:34:01
Requested-By: mt (1074)
Install: python3-pyparsing:amd64 (2.4.7-1, automatic), python3-packaging:amd64 (20.9-2, automatic), python3-gpg:amd64 (1.14.0-1+b2, automatic), torbrowser-launcher:amd64 (0.3.3-6)
End-Date: 2025-11-23 22:34:11
Start-Date: 2025-11-29 12:15:19
Requested-By: mt (1074)
Upgrade: cups-filters:amd64 (1.28.7-1+deb11u3, 1.28.7-1+deb11u4), libsnmp-base:amd64 (5.9+dfsg-4+deb11u1, 5.9+dfsg-4+deb11u2), libsnmp40:amd64 (5.9+dfsg-4+deb11u1, 5.9+dfsg-4+deb11u2), libqt5core5a:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), qt5-gtk-platformtheme:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5network5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libfontembed1:amd64 (1.28.7-1+deb11u3, 1.28.7-1+deb11u4), libwbclient0:amd64 (2:4.13.13+dfsg-1~deb11u6, 2:4.13.13+dfsg-1~deb11u7), libssh-gcrypt-4:amd64 (0.9.8-0+deb11u1, 0.9.8-0+deb11u2), libqt5dbus5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libsmbclient:amd64 (2:4.13.13+dfsg-1~deb11u6, 2:4.13.13+dfsg-1~deb11u7), libqt5test5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5widgets5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), cups-filters-core-drivers:amd64 (1.28.7-1+deb11u3, 1.28.7-1+deb11u4), libqt5gui5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5printsupport5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5xml5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5opengl5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libqt5sql5:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), cups-browsed:amd64 (1.28.7-1+deb11u3, 1.28.7-1+deb11u4), libsdl2-2.0-0:amd64 (2.0.14+dfsg2-3+deb11u1, 2.0.14+dfsg2-3+deb11u2), libsdl2-2.0-0:i386 (2.0.14+dfsg2-3+deb11u1, 2.0.14+dfsg2-3+deb11u2), samba-libs:amd64 (2:4.13.13+dfsg-1~deb11u6, 2:4.13.13+dfsg-1~deb11u7), libqt5sql5-sqlite:amd64 (5.15.2+dfsg-9+deb11u1, 5.15.2+dfsg-9+deb11u2), libcupsfilters1:amd64 (1.28.7-1+deb11u3, 1.28.7-1+deb11u4)
End-Date: 2025-11-29 12:17:05Except for the manual installation of 2 games that i wanted to try out, everything else was installed via "aptitude update" and "aptitude upgrade".
...then I suspect that's old hardware giving up the ghost slowly
While I cannot completely exclude this possibility, I dare to say that it's neither cpu nor RAM-related, as the system has been running for many hours now without any hitch. But then again, I haven't run any games nor watched any videos or listened to music.
...and I would recommend blowing out any buildup of dust from the vents
That's another thing that I have done about 3 weeks ago.
In one way it is a good thing that this apparently was not the cause (...hoping that the issue is software-related).
It's the same kernel that's giving you problems, just manifests differently maybe.
I really DO wish it was the kernel. Because that would be very easy to solve.
But the issues started well before the installation of that kernel (which never showed up on the boot menu anyway).
#21 Re: Hardware & System Configuration » [SOLVED] Strange Grub behavior after new kernel installation » 2025-12-31 21:03:41
[Edit: I just checked the logs and saw that 5.10.0-37 had been installed only 2 weeks ago (on Dec. 16th).]
I wish it were just because of kernel 5.10.0-37 actively running on this system.
But I never got to the point to be able to boot it as it never showed up on the boot screen.
Since the installation of 5.10.0-37, I've been running 5.10.0-35 again.
And unfortunately, the issues that I described in my other thread started at least 2 weeks before the latest kernel update.
I still wonder, if the mere kernel installation might have lead to grub behaving in a weird way all of a sudden.
#22 Hardware & System Configuration » [SOLVED] Strange Grub behavior after new kernel installation » 2025-12-31 20:32:02
- switching2Devuan
- Replies: 9
After updating my system (Chimaera 4.0) about 4-5 weeks ago, a new kernel was installed (Linux devuan 5.10.0-37-amd64).
I purged one of the previous kernels + headers (5.10.0-36) as I have always done, then I ran "sudo update-grub".
Contrary to the many kernel installations that had happened on my system during the previous 3,5 years, 5.10.0-37 would not show up on the grub boot screen.
Instead, the entry for its direct predecessor (5.10.0-36) was still there but could not boot for obvious reasons (having been purged before).
Nevertheless, 5.10.0-37 is present in grub.cfg.
Another "sudo update-grub" didn't change anything.
Apparently grub.cfg is properly updated but grub somehow does not display the changes on the boot screen.
At the moment, I have to manually select the remaining old kernel (5.10.0-35) to boot the system.
Now I wonder why grub is not using the correct information from grub.cfg and still displays some outdated configuration.
Has anyone ever encountered this before?
I appreciate any suggestions.
(I hope this topic is in the correct subforum. Otherwise please move it to a more proper location.)
#23 Re: Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2025-12-31 18:42:11
the T4300 is probably a bit lame (please dont take it personally) for 2026,
No worries.
I could look into upgrading the cpu of course (although the speed is sufficient for what I am using this laptop for) but I just have the feeling that a different cpu won't solve the current problem.
#24 Desktop and Multimedia » [SOLVED] Chimaera started freezing completely under certain occasions » 2025-12-31 18:24:03
- switching2Devuan
- Replies: 17
Hello everybody,
I've been using Chimaera 4.0 on a laptop for about 3.5 years now and the reason why I have hardly visited this forum to look for help was because the system has been rockstable and a dependable basis for my daily tasks.
At least until about 4-6 weeks ago.
First off the specs:
- Toshiba Satellite laptop (from 2009)
- Pentium(R) Dual-Core CPU T4300 @ 2.10GHz
- Intel Mobile 4 Series Chipset Integrated Graphics Controller
- 4 GB RAM
- 500 GB HD
- DE is LXDE
- Dual-boot setup (Devuan Chimaera and Win 7)
Starting around mid november, I experienced irregular complete freezings of the whole system without a chance of recovering.
Sound playback would be repeated with the last second in an infinite loop and the keyboard would not react whatsoever, which left me unable to drop to a terminal to see what was going on.
The only solution to this is pressing the power button for a few seconds.
The first time this happened, I was playing a game over WINE.
After this freeze had happened a few times I thought that it had to do with WINE.
But then it also happened while playing another game natively and also when I was just watching a video with vlc.
So I figured that it could have to do with the integrated graphics chipset until it also happened when I was just listening to music with audacious.
Otherwise the system is stable and solid as always and will run many hours a day without hiccup.
OOM does not seem to be an issue as I've had those freezes with as little as 600 MB of RAM being used and well over 2 GB of free RAM.
Lockups/freezes when playing a game or listening to music are very irregular and can occur anywhere between a few minutes to well over an hour. Sometimes I can play for 1,5 hours and nothing freezes at all.
The funny thing is that I have done all of the now suspected activities within the last 3+ years without any problem.
As I update my system from time to time, it could theoretically be that some program/library was updated that's been causing problems on my system.
What I have done so far:
- After being frozen, I let the system run for more than an hour to see if it might recover --> no change though
- I ran Memtest to check for faulty memory --> no errors after 2+ hours and 2 complete passes
- I monitored cpu-temperatures on the desktop --> freezes occured even at a very low 43 °C (temperatures close to 60 °C when running Memtest were not a problem)
My question now is what else I should look into to find the cause of this erratic system behavior.
If someone wants to take a look at some log, I will be happy to provide it.
Any support is appreciated.
Thank you for taking the time to read this post.
#25 Installation » Choices during install of Chimaera not being applied » 2022-07-13 15:28:31
- switching2Devuan
- Replies: 4
After having installed Devuan Chimaera for the first time about 2 months ago on a separate partition, I installed it (with the same netinst-iso) to finally replace Debian Bullseye.
The installation process itself went smoothly.
However, this time I didn't choose any DE. So I had to deselect xfce4 as the default option.
When given the option to choose a display manager, I chose lightdm over the default Slim (which I was having trouble with during the previous test-install; see here).
When I rebooted, I was surprised to find that my choices had been ignored.
Not only had Slim been installed (I noticed that right away when not having a greeter again (as reported in the thread under the link above).
I also had a full installation of xfce4 just as if I had selected it during the installation process.
Both points are not troubling me too much as I simply replaced Slim with lightdm again.
And I was eventually going for xfce4 anyway.
That was with the automatic install btw.
Another thing is that I chose expert install on my first attempt but aborted due to the following reason:
When being in the partitioning window, I was presented with only 4 (or 5) choices for a filesystem (ext2 being one of them, but neither ext3 nor ext4).
As I wanted ext4 for / again, I aborted and chose automatic install where it was available (along with a lot more choices).
Just wanted to let developers know that there may be a glitch in the installation process (at least in my configuration).
Board footer
