You are not logged in.
No extra messages when I add one of them
Hi,
I have two very different dell laptops, one with daedalus, the other with excaliber.
I also have two external hardrives for backups and restoring files after installs etc. One is self powered from the usb, the other has an external powerbrick. Both are read by the daedalus laptop, neither can be seen in excaliber.
On the excaliber laptop lsblk shows no changes when plugging the drives in, one is 3Tb, the other is 6Tb, so I do not expect immediate recognition, but even after several minutes the excaliber machine is not seeing these drives anywhere.
Oh yes, it is the mate desktop. I also turn off recommended quite early after install, or one can get stuck in a loop with unwanted extras that wont be removed without a major re-installation fiasco.
Any ideas what I could try next?
check that you untick "install recommended packages as dependencies" in synaptic preferences and you might not have got that pulled in with something else. I made that mistake for the first few packages after a new install recently, and wondered why all sorts of rubbish was being pulled in.
Hi Lorenzo,
I have rsyslog and cron definitely installed on that laptop.
good to know the fix is on its way, I am not sure if the postcondition I used is correct or in the correct file(s).
Mike
Hi, a recent install on a laptop I used the 5.01 Daedalus Am64, desktop iso.
I had a few niggles I had to track down and on the way I noticed some significant logrotate issues.
ls -la /var/log
total 16428
drwxr-xr-x 15 root root 4096 Oct 1 10:19 .
drwxr-xr-x 13 root root 4096 Sep 27 18:09 ..
drwxr-xr-x 2 root root 4096 Oct 1 09:56 account
-rw-r--r-- 1 root root 0 Oct 1 10:19 alternatives.log ****
-rw-r--r-- 1 root root 132906 Sep 29 18:32 alternatives.log.1 ****
drwxr-xr-x 2 root root 4096 Feb 14 2023 apparmor
drwxr-xr-x 2 root root 4096 Oct 1 10:19 apt
-rw-r----- 1 root adm 0 Oct 1 10:19 auth.log ****
-rw-r----- 1 root adm 167590 Oct 2 01:25 auth.log.1 ****
-rw-r----- 1 root adm 309762 Oct 1 09:49 auth.log.2.gz
-rw-r----- 1 root adm 5497 Oct 1 09:50 boot
-rw-r----- 1 root adm 5657 Sep 29 12:18 boot.0
-rw-r----- 1 root adm 1221 Sep 27 19:35 boot.1.gz
-rw-r----- 1 root adm 1121 Sep 27 13:30 boot.2.gz
-rw-r----- 1 root adm 136 Sep 27 12:53 boot.3.gz
-rw-rw---- 1 root utmp 0 Oct 1 10:19 btmp
-rw-rw---- 1 root utmp 0 Sep 27 12:53 btmp.1
drwxr-xr-x 2 root root 4096 Sep 29 12:28 chkrootkit
-rw-r----- 1 root adm 0 Oct 1 10:19 cron.log ****
-rw-r----- 1 root adm 7265 Oct 2 01:25 cron.log.1 ****
-rw-r----- 1 root adm 8976 Oct 1 09:45 cron.log.2.gz
drwxr-xr-x 2 root root 4096 Oct 1 10:19 cups
-rw-r----- 1 root adm 78491 Oct 1 09:50 dmesg
-rw-r----- 1 root adm 77424 Sep 29 12:18 dmesg.0
-rw-r----- 1 root adm 20165 Sep 27 19:35 dmesg.1.gz
-rw-r----- 1 root adm 18823 Sep 27 13:30 dmesg.2.gz
-rw-r--r-- 1 root root 0 Oct 1 10:19 dpkg.log ****
-rw-r--r-- 1 root root 3188602 Oct 1 03:24 dpkg.log.1 ****
drwxr-s--- 2 Debian-exim adm 4096 Oct 1 10:19 exim4
-rw-r--r-- 1 root root 0 Sep 27 12:53 faillog
-rw-r--r-- 1 root root 13581 Sep 29 15:23 fontconfig.log
drwxr-xr-x 2 root root 4096 Sep 27 12:53 fsck
drwxr-xr-x 3 root root 4096 Sep 27 13:29 installer
-rw-r----- 1 root adm 0 Oct 1 10:19 kern.log ****
-rw-r----- 1 root adm 294704 Oct 2 01:18 kern.log.1 ****
-rw-r----- 1 root adm 200714 Oct 1 09:49 kern.log.2.gz
-rw-rw-r-- 1 root utmp 292292 Oct 1 09:51 lastlog
-rw-r--r-- 1 root root 108254 Sep 27 13:52 popularity-contest
-rw-r--r-- 1 root root 0 Sep 27 13:52 popularity-contest.0
-rw-r--r-- 1 root root 29035 Sep 27 13:52 popularity-contest.gpg
drwxrwxr-t 2 root postgres 4096 Sep 28 22:47 postgresql
drwxr-x--- 2 puppet puppet 4096 Feb 10 2023 puppet
drwxr-x--- 2 puppet puppet 4096 May 7 2023 puppetserver
drwxr-xr-x 9 root root 4096 Sep 28 14:49 runit
-rw-r--r-- 1 root root 123 Oct 1 09:51 slim.log
-rw-r--r-- 1 root root 75 Sep 29 12:31 slim.log.1
-rw-r----- 1 root adm 0 Oct 1 10:19 syslog ****
-rw-r----- 1 root adm 1931572 Oct 2 01:25 syslog.1 ****
-rw-r----- 1 root adm 186794 Oct 1 09:49 syslog.2.gz
drwxr-xr-x 2 root root 4096 Dec 4 2022 sysstat
-rw-r----- 1 root adm 0 Oct 1 10:19 user.log ****
-rw-r----- 1 root adm 1178 Oct 2 00:56 user.log.1 ****
-rw-r----- 1 root adm 727 Oct 1 07:59 user.log.2.gz
-rw-rw-r-- 1 root utmp 635520 Oct 2 01:25 wtmp
-rw-rw-r-- 1 root utmp 9141120 Oct 1 10:19 wtmp.1
-rw-r--r-- 1 root root 43922 Oct 2 00:56 Xorg.0.log
-rw-r--r-- 1 root root 42509 Oct 1 09:49 Xorg.0.log.old
I have added some asterix to highlight that there were many pairs of logs where the log file proper stayed at zero, and the *.1 log is the one that keeps growing.
I used this next webpage to see what might be happening:
https://serverfault.com/questions/82372 … rrect-file
So then I tried to force an update
Usage: logrotate [-dfv?] [-d|--debug] [-f|--force] [-m|--mail=command] [-s|--state=statefile] [-v|--verbose] [-l|--log=logfile] [--version] [-?|--help] [--usage] [OPTION...] < configfile >
sudo logrotate -f /etc/logrotate.conf
This did not work because the proper file of each set was still blank...
This next page gave me some more to go on.
sudo logrotate --force -d /etc/logrotate.conf > ~/Documents/logrotateForce.txt
warning: logrotate in debug mode does nothing except printing debug messages! Consider using verbose mode (-v) instead if this is not what you want.
reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file alternatives
reading config file apt
reading config file aptitude
reading config file btmp
reading config file cups-daemon
reading config file dpkg
reading config file dracut-core
reading config file exim4-base
reading config file exim4-paniclog
reading config file postgresql-common
reading config file ppp
reading config file rkhunter
reading config file rsyslog
reading config file sane-utils
reading config file slim
reading config file wtmp
Reading state from file: /var/lib/logrotate/status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Handling 17 logs
rotating pattern: /var/log/alternatives.log forced from command line (12 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/alternatives.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
rotating pattern: /var/log/apt/term.log forced from command line (12 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/apt/term.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
rotating pattern: /var/log/apt/history.log forced from command line (12 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/apt/history.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
rotating pattern: /var/log/aptitude forced from command line (6 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/aptitude
log /var/log/aptitude does not exist -- skipping
rotating pattern: /var/log/btmp forced from command line (1 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/btmp
Now: 2024-10-02 02:00
Last rotated at 2024-10-02 01:46
log needs rotating
rotating log /var/log/btmp, log->rotateCount is 1
dateext suffix '-20241002'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/btmp.1 to /var/log/btmp.2 (rotatecount 1, logstart 1, i 1),
log /var/log/btmp.2 doesn't exist -- won't try to dispose of it
renaming /var/log/btmp to /var/log/btmp.1
creating new /var/log/btmp mode = 0660 uid = 0 gid = 43
rotating pattern: /var/log/cups/*log forced from command line (7 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/cups/access_log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
considering log /var/log/cups/error_log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
not running postrotate script, since no logs were rotated
rotating pattern: /var/log/dpkg.log forced from command line (12 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/dpkg.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
rotating pattern: /var/log/dracut.log forced from command line (12 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/dracut.log
log /var/log/dracut.log does not exist -- skipping
rotating pattern: /var/log/exim4/mainlog /var/log/exim4/rejectlog forced from command line (10 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/exim4/mainlog
log /var/log/exim4/mainlog does not exist -- skipping
considering log /var/log/exim4/rejectlog
log /var/log/exim4/rejectlog does not exist -- skipping
rotating pattern: /var/log/exim4/paniclog forced from command line (10 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/exim4/paniclog
log /var/log/exim4/paniclog does not exist -- skipping
rotating pattern: /var/log/postgresql/*.log forced from command line (10 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/postgresql/postgresql-15-main.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-02 01:46
log does not need rotating (log is empty)
rotating pattern: /var/log/ppp-connect-errors forced from command line (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/ppp-connect-errors
log /var/log/ppp-connect-errors does not exist -- skipping
rotating pattern: /var/log/rkhunter.log forced from command line (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/rkhunter.log
log /var/log/rkhunter.log does not exist -- skipping
rotating pattern: /var/log/syslog
/var/log/mail.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/cron.log
forced from command line (60 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/syslog
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
considering log /var/log/mail.log
log /var/log/mail.log does not exist -- skipping
considering log /var/log/kern.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
considering log /var/log/auth.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
considering log /var/log/user.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
considering log /var/log/cron.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-01 10:19
log does not need rotating (log is empty)
not running postrotate script, since no logs were rotated
rotating pattern: /var/log/saned.log forced from command line (7 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/saned.log
log /var/log/saned.log does not exist -- skipping
rotating pattern: /var/log/slim.log forced from command line (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/slim.log
Now: 2024-10-02 02:00
Last rotated at 2024-10-02 01:46
log does not need rotating (log is empty)
rotating pattern: /var/log/wtmp forced from command line (1 rotations)
empty log files are rotated, only log files >= 1048576 bytes are rotated, old logs are removed
considering log /var/log/wtmp
Now: 2024-10-02 02:00
Last rotated at 2024-10-02 01:46
log needs rotating
rotating log /var/log/wtmp, log->rotateCount is 1
dateext suffix '-20241002'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/wtmp.1 to /var/log/wtmp.2 (rotatecount 1, logstart 1, i 1),
log /var/log/wtmp.2 doesn't exist -- won't try to dispose of it
renaming /var/log/wtmp to /var/log/wtmp.1
creating new /var/log/wtmp mode = 0664 uid = 0 gid = 43
So now I had to add a postcondition halt and restart of syslog into the config files, on a temporary basis I stopped the option to do nothing if the log was empty. I think that last bit is only needed on a temporary basis until the postcondition operation is added.
Once I had done that the log files started behaving correctly
well a couple of comments added to
/usr/share/dbus-1/systemservices/org.freedesktop.RealtimeKit1.service
has bought me some time to find the runit way of taming this, it was just slowing everything down with how busy it was, adds to my determination to keep the potteringisms out of my PC.
Seems it was not fixed, syslog has stayed empty, but syslog.1 has kept growing!
Still trying to get to grips with runit as supervisor, so something has gone wrong with the rotation. It is a fresh install, still monitoring it and tracking down these little problems.
I found out what caused it, the pc has recently been upgraded to devuan and I was installing some programs I needed, one of them dragged in "pulseaudio-utils". It was generating 2Mb of text log every hour.
I have now removed that, and this has reminded me to set a bunch of pulse audio bits to -1 in the apt conf!!!
Hi,
running with Runit, and have added a few programs recently, now getting a crazy amount of entries about rtkit-daemon messaging about how many processes it is handling and then even more messages about exceeding the limits.
The help info in /usr/share/dbus-1/system-services/org.freedesktop.RealtimeKit1.service
and
/usr/libexec/rtkit-daemon
Does not help very much, anyone else come across this and solved it?
sudo /usr/libexec/rtkit-daemon --help
rtkit-daemon [options]
COMMANDS:
-h, --help Show this help
--version Show version
OPTIONS:
--stderr Log to STDERR in addition to syslog
--user-name=USER Run daemon as user (rtkit)
--scheduling-policy=(RR|FIFO) Choose scheduling policy (RR)
--our-realtime-priority=[1..99] Realtime priority for the daemon (21)
--our-nice-level=[-20..19] Nice level for the daemon (1)
--max-realtime-priority=[1..99] Max realtime priority for clients (20)
--min-nice-level=[-20..19] Min nice level for clients (-15)
--rttime-usec-max=USEC Require clients to have set RLIMIT_RTTIME
not greater than this (200000)
--users-max=INT How many users this daemon will serve at
max at the same time (2048)
--processes-per-user-max=INT How many processes this daemon will serve
at max per user at the same time (15)
--threads-per-user-max=INT How many threads this daemon will serve
at max per user at the same time (25)
--actions-burst-sec=SEC Enforce requests limits in this time (20)
--actions-per-burst-max=INT Allow this many requests per burst (25)
--canary-cheep-msec=MSEC Canary cheep interval (5000)
--canary-watchdog-msec=MSEC Watchdog action delay (10000)
--canary-demote-unknown When the canary dies demote unknown
processes too?
--canary-demote-root When the canary dies demote root
processes too?
--canary-refuse-sec=SEC How long to refuse further requests
after the canary died (300)
--no-canary Don't run a canary-based RT watchdog
--no-drop-privileges Don't drop privileges
--no-chroot Don't chroot
--no-limit-resources Don't limit daemon's resources
and
sudo cat org.freedesktop.RealtimeKit1.service
# This file is part of RealtimeKit.
#
# Copyright 2009 Lennart Poettering
#
# RealtimeKit is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# RealtimeKit is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with RealtimeKit. If not, see <http://www.gnu.org/licenses/>.
[D-BUS Service]
Name=org.freedesktop.RealtimeKit1
Exec=/usr/libexec/rtkit-daemon
SystemdService=rtkit-daemon.service
User=root
Well things have taken a turn for the better for me.
Family member had run out of free space on google, that was why some known pics were not appearing, they freed up a bunch of space, and the phone has now automatically synced to the mothership. No more effort required on my part.
I currently have a mobile phone too, but it is too toxic for browsing, cant stand it, impossible to really scrub those ads from view. so mostly used as a dumb phone.
It is cheaper to by another second hand phone than to replace screen, so it will be scrapped.
job done without messing with adb, thank fcuk
Thanks, I had forgotten about the pop-up on the phone, that is what is stopping things from happening. It is a family memers phone that had a big drop, was found again and worked normally for about a week then went black, as the family sort of IT expert I am expected to fix this problem...
I will try adb to see where that gets me.
I am using daedalus on a dell m-6800, and I get error messages about not being able to connect to the phone, I get the top level connection only:
mtp://SAMSUNG_SAMSUNG_Android_R58N515N63A/
It is empty below that, not sure what to add or configure to get access to the phone, phone display has died, but it can be made to ring remotely, so hopefully only a dead display to contend with.
Hi Geki,
Yes I have that page, in frustration I even put the windows bootloader in the excluded list on the right hand side. I will keep trying. It does seem to be on the latest BIOS for the L14, it is currently already at version 19, so someone updated it before I bought it. Yes the mystery key to bring up bios is not fun anymore.
I still cannot get it to change out of totally locked to windows.
My next thing to try is to try and setup a supervisor password to see if that unlocks some of the options. But I want to check through Lenovos interpretation of the various things to set.
Thank you Ralph,
I went into settings > System > Recovery
That gives you the option to reboot into the hypervisor level of windows, from there I can get into the bios (the slow way round) and I can ask it to reboot from a choice of media, but it still does not reboot to anywhere but windows, usually telling me it is doing windows recovery.
The same 3 usb sticks give me a boot menu in 2 other laptops, but not this one.
It clearly does the the USB stick, makes some sort of start to read it and then bails out to tell me it want to repair windows.
In two other PC's It starts and lets the USB run.
It is plainly the secure boot getting in the way.
Any questions about other
I only get to choose the boot order in the bios, I never get the selection option when it reads the usb, I am bounced back to windows, so HOAS I did answer your question first time round there is nothing to select...
I think I must put my own keyset in there, each thing I try makes it seem like that is what I must do. But the risk of bricking it is holding me back, I must try a few more things before I go to that.
currently I am trying to get ventoy to run the usb with a 32Mb UEFI partition,so that I may run clonezilla and take off the image onto the usb before wiping it for devuan. It is then the best of both worlds, I get devuan, and other family members get win11 inside a firewall...
Hi Altoid, the boot usb stick works in another PC, And I do know when I am in the bios settings. On this Lenovo they are very empty, on another 2 lenovos it is busier.
Well it can be done, but it is even less secure, as the EFI layer with all its opaque complexity is still there, but now not locked down.
I know that is the fallback option, but with this lenovo I am not even sure it can be done, seems so much more locked down than previous bios I have worked with.
It keeps dropping back to windows even with the Gparted usb stick being presented.
It is generation 1, and every attempt to get the usb stick to run leads back to windows trying to stop the install.
The days of reading the numbers off SMD devices is past, I needed a magnifying glass to read the text on the bottom.
It is a thinkpad L14, second hand, I have the service manual etc, and I just know I do not want win11.
I cannot even get it to see the usb stick yet. the bios has quite a sparse menu, so not many things to miss in theory.
I guess I must send an email to support then.
I have a Lenovo that I need to install Devuan, the bios is not like the Lenovo examples on the web:
https://forums.linuxmint.com/viewtopic.php?t=377054
https://support.lenovo.com/gb/en/solutions/ht103400-linux-operating-system-limitations-when-secure-boot-is-enabled
and a lenovo PDF as well
BUT on my BIOS pages there does not seem to be any option to change the secure boot from "standard mode" to "Custom mode", the text provided implies the choice is there, but I am unable to find how to activate that.
This page is of great help:
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot
I have already done a trial run of generating the keys required, and it does seem, looking at the bios options available that I can remove the keys and install my own, and it has an option to revert the keys, if I want to sell the laptop later.
I just need to know that it is my only option, as there is a risk of bricking the laptop this way.
I want win11 to exist inside a VM on the laptop, not the other way round, there are family members that are resistant to linux.
Mike-thinky wrote:I got frustrated and rebooted, it came straight back up to 38%
Don't reboot with the machine plugged in and charging. That sudden jump in percentage may have been caused by your battery being flooded with power during the reboot cycle. That will kill the battery *very* quickly indeed. And when I say "kill" I actually mean "potentially explode" (yes, really).
Check /sys/class/power_supply/BAT0/energy_full_design and compare it to /sys/class/power_supply/BAT0/energy_full to see how much damage has been sustained.
With an empty battery or a full battery that might be possible, but in between I cannot see how that would happen unless the psu delivered huge fault currents into the battery
well it was charge_full and charge_full_design, they both report 3242000, so thankfully a sane psu design.
That gives me some things to look at.
It stayed at 7% for about an hour, I got frustrated and rebooted, it came straight back up to 38%, so the panel thingy in bottom right had been lying to me for most of that hour.
your link took me after a little look to this page:
https://docs.xfce.org/xfce/xfce4-power-manager/faq
It seems to be that daedalus is missing pm-utils, the rest seems to be systemd tentacles. I will install that and monitor behaviour on low battery and unplugged.
As a separate note, I do like being able to keep laptop batteries charged between 60%min, 80-85%max, it makes the battery last so much longer.
Eventually I will have to tinker to make that possible here too.
Hi,
System nearly how I want it, but this morning the battery ran low, but not empty.
I plugged it back into the charger, and it displayed charging, but the update to the percentage is very very slow, and I do not know where it is set.
As a consequence of getting below 10%? it would not connect to the wifi, so unable to search on there for an answer
So where should I be looking on a Daedalus XFCE and lightdm build to tinker with the battery charge status update interval, and or change the percentage threshold for this?
The settings editor GUI does not have this number available, unless the name is misleading and I have glossed past it?