Beiträge von uname

uname · 23. September 2021

Code

# zypper in google-earth-pro-stable-current.x86_64.rpm 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'mesa-libGLU' needed by the to be installed google-earth-pro-stable-7.3.4.8248-0.x86_64
 Solution 1: do not install google-earth-pro-stable-7.3.4.8248-0.x86_64
 Solution 2: break google-earth-pro-stable-7.3.4.8248-0.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c): c

......................
# zypper in mesa-libGLU-0.0.1-lp153.3.2.noarch.rpm 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 79 NEW packages are going to be installed:
...
Continue? [y/n/v/...? shows all options] (y): y
.....
mesa-libGLU-0.0.1-lp153.3.2.noarch.rpm:
    Header V3 RSA/SHA256 Signature, key ID 53840158: NOKEY
    V3 RSA/SHA256 Signature, key ID 53840158: NOKEY

Looking for gpg key ID 53840158 in cache /var/cache/zypp/pubkeys.
Repository Plain RPM files cache does not define additional 'gpgkey=' URLs.
mesa-libGLU-0.0.1-lp153.3.2.noarch (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]                                              
Abort, retry, ignore? [a/r/i] (a): i
....
# zypper in google-earth-pro-stable-current.x86_64.rpm
...
Looking for gpg key ID 7FAC5991 in cache /var/cache/zypp/pubkeys.
Repository Plain RPM files cache does not define additional 'gpgkey=' URLs.
google-earth-pro-stable-7.3.4.8248-0.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): i

Checking for file conflicts: ......................................................[done]
(1/1) Installing: google-earth-pro-stable-7.3.4.8248-0.x86_64 .....................[done]
Additional rpm output:
warning: /var/cache/zypper/RPMS/google-earth-pro-stable-current.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY

Alles anzeigen

... jetzt nur noch hoffen das alles läuft.

uname · 18. September 2021

@erfolgreich-wissen

Zitat von erfolgreich-wissen

Vorhin war der AMDGPU noch aktiv.

und jetzt?

Code

# lspci -nnk | grep -A3 "\[03..\]:"

uname · 18. September 2021

Zitat von sterun

..zeigt dir, wann welche Timer liefen und erneut laufen werden.

wieder was gelernt, Danke

Code

systemctl list-timers --all | more
NEXT                         LEFT               LAST                         PASSED             UNIT                         ACTIVATES 
                    
Sat 2021-09-18 11:00:00 CEST 35min left         Sat 2021-09-18 10:00:33 CEST 23min ago          snapper-timeline.timer       snapper-ti
meline.service      
Sun 2021-09-19 00:00:00 CEST 13h left           Sat 2021-09-18 08:19:49 CEST 2h 4min ago        logrotate.timer              logrotate.
service             
Sun 2021-09-19 00:00:00 CEST 13h left           Sat 2021-09-18 08:19:49 CEST 2h 4min ago        mandb.timer                  mandb.serv
ice                 
Sun 2021-09-19 00:02:54 CEST 13h left           Sat 2021-09-18 09:10:49 CEST 1h 13min ago       backup-sysconfig.timer       backup-sys
config.service      
Sun 2021-09-19 01:12:50 CEST 14h left           Sat 2021-09-18 09:10:49 CEST 1h 13min ago       check-battery.timer          check-batt
ery.service         
Sun 2021-09-19 01:15:18 CEST 14h left           Sat 2021-09-18 09:10:49 CEST 1h 13min ago       backup-rpmdb.timer           backup-rpm
db.service          
Sun 2021-09-19 08:35:33 CEST 22h left           Sat 2021-09-18 08:35:33 CEST 1h 48min ago       snapper-cleanup.timer        snapper-cl
eanup.service       
Sun 2021-09-19 08:40:33 CEST 22h left           Sat 2021-09-18 08:40:33 CEST 1h 43min ago       systemd-tmpfiles-clean.timer systemd-tm
pfiles-clean.service
Mon 2021-09-20 00:40:50 CEST 1 day 14h left     Mon 2021-09-13 10:32:09 CEST 4 days ago         fstrim.timer                 fstrim.ser
vice                
Fri 2021-10-01 00:00:00 CEST 1 week 5 days left Wed 2021-09-01 08:53:29 CEST 2 weeks 3 days ago btrfs-balance.timer          btrfs-bala
nce.service         
Fri 2021-10-01 00:00:00 CEST 1 week 5 days left Wed 2021-09-01 08:53:29 CEST 2 weeks 3 days ago btrfs-defrag.timer           btrfs-defr
ag.service          
Fri 2021-10-01 00:00:00 CEST 1 week 5 days left Wed 2021-09-01 08:53:29 CEST 2 weeks 3 days ago btrfs-scrub.timer            btrfs-scru
b.service           
Fri 2021-10-01 00:00:00 CEST 1 week 5 days left Wed 2021-09-01 08:53:29 CEST 2 weeks 3 days ago btrfs-trim.timer             btrfs-trim
.service            

13 timers listed.

Alles anzeigen

uname · 18. September 2021

Zitat von sterun

Um noch einige Sekunden herauszuholen...

Ich habe noch das ein oder andere auf manuell gesetzt.

@sterun

Besten Dank für die Unterstützung

lg. uname

Code

# systemd-analyze time
Startup finished in 4.141s (kernel) + 5.672s (initrd) + 19.229s (userspace) = 29.043s 
graphical.target reached after 19.215s in userspace

uname · 17. September 2021

Code

# btrfs balance start --full-balance /

Done, had to relocate 51 out of 51 chunks
suse:/home/tuxracer # 
suse:/home/tuxracer # systemctl stop backup-rpmdb.service
Warning: Stopping backup-rpmdb.service, but it can still be activated by:
  backup-rpmdb.timer
suse:/home/tuxracer # systemctl start backup-rpmdb.service

2 Min. warten - Reboot:

Code

# systemd-analyze time
Startup finished in 4.157s (kernel) + 6.024s (initrd) + 21.147s (userspace) = 31.329s 
graphical.target reached after 21.134s in userspace
suse:/home/tuxracer # systemd-analyze blame | head -n 15
5.329s polkit.service                                                           
5.287s avahi-daemon.service                                                     
5.155s initrd-switch-root.service                                               
4.392s firewalld.service                                                        
4.114s systemd-logind.service                                                   
3.715s display-manager.service                                                  
3.217s plymouth-quit-wait.service                                               
2.617s apparmor.service                                                         
2.553s smartd.service                                                           
2.209s dracut-initqueue.service                                                 
2.140s systemd-udevd.service                                                    
2.111s postfix.service                                                          
1.176s rsyslog.service                                                          
1.149s nscd.service                                                             
 837ms systemd-random-seed.service

Alles anzeigen

uname · 17. September 2021

Zitat von sterun

...nun sollte keine Warnung mehr erscheinen

Code

# btrfs quota rescan -w /
quota rescan started
suse:/home/tuxracer # btrfs qgroup show /
qgroupid         rfer         excl 
--------         ----         ---- 
0/5          16.00KiB     16.00KiB 
0/256        16.00KiB     16.00KiB 
0/258       811.60MiB    811.60MiB 
0/259        16.00KiB     16.00KiB 
0/260        14.08MiB     14.08MiB 
0/261        16.00KiB     16.00KiB 
0/262        10.83MiB     10.83MiB 
0/263        16.00KiB     16.00KiB 
0/264        36.83GiB     36.83GiB 
0/265        16.00KiB     16.00KiB 
0/266         2.50MiB      2.50MiB 
0/267        28.00KiB     28.00KiB 
0/268         6.14GiB    183.09MiB 
0/504         6.14GiB     81.72MiB 
0/505         6.15GiB      7.49MiB 
1/0           6.23GiB    267.27MiB

Alles anzeigen

uname · 17. September 2021

Code

btrfs qgroup show / && inxi -F        #siehe Anhang

Rechner danach neu booten gleich:

Code

# systemd-analyze blame | head -n 15
5.214s display-manager.service                                                  
4.867s initrd-switch-root.service                                               
4.749s plymouth-quit-wait.service                                               
4.649s polkit.service                                                           
4.592s avahi-daemon.service                                                     
3.817s smartd.service                                                           
3.687s systemd-logind.service                                                   
3.528s firewalld.service                                                        
3.213s apparmor.service                                                         
2.163s dracut-initqueue.service                                                 
1.961s postfix.service                                                          
1.887s systemd-udevd.service                                                    
1.061s mcelog.service                                                           
 885ms nscd.service                                                             
 857ms systemd-rfkill.service

Alles anzeigen

Code

# systemd-analyze critical-chain --system
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @21.383s
└─display-manager.service @16.167s +5.214s
  └─time-sync.target @16.161s
    └─chronyd.service @16.036s +124ms
      └─network.target @16.018s
        └─NetworkManager.service @15.402s +615ms
          └─network-pre.target @15.401s
            └─wpa_supplicant.service @16.421s +204ms
              └─dbus.service @7.203s
                └─basic.target @7.198s
                  └─sockets.target @7.198s
                    └─pcscd.socket @7.198s
                      └─sysinit.target @7.051s
                        └─apparmor.service @3.836s +3.213s
                          └─var.mount @3.753s +50ms
                            └─local-fs-pre.target @3.737s
                              └─systemd-tmpfiles-setup-dev.service @3.507s +229ms
                                └─kmod-static-nodes.service @3.381s +29ms
                                  └─systemd-journald.socket
                                    └─-.mount
                                      └─system.slice
                                        └─-.slice
lines 5-25/25 (END)

Alles anzeigen

uname · 16. September 2021

Code

# systemd-analyze critical-chain backup-rpmdb.service
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

backup-rpmdb.service +15.400s
└─backup-rpmdb.timer @32.164s
  └─time-sync.target @32.164s
    └─chronyd.service @31.816s +347ms
      └─network.target @31.801s
        └─NetworkManager.service @31.113s +687ms
          └─network-pre.target @31.111s
            └─wpa_supplicant.service @32.081s +226ms
              └─dbus.service @13.402s
                └─basic.target @13.398s
                  └─sockets.target @13.398s
                    └─pcscd.socket @13.398s
                      └─sysinit.target @11.932s
                        └─systemd-backlight@backlight:intel_backlight.service @14.149s +610ms
                          └─system-systemd\x2dbacklight.slice @14.147s
                            └─system.slice
                              └─-.slice

Alles anzeigen

uname · 16. September 2021

Code

systemd-analyze blame
15.400s backup-rpmdb.service                                                     
 9.281s firewalld.service                                                        
 9.078s mandb.service                                                            
 8.376s polkit.service                                                           
 8.298s avahi-daemon.service                                                     
 8.133s systemd-udevd.service                                                    
 6.926s systemd-logind.service                                                   
 5.398s display-manager.service                                                  
 5.050s plymouth-quit-wait.service                                               
 4.856s apparmor.service                                                         
 4.759s initrd-switch-root.service                                               
 3.900s rsyslog.service                                                          
 2.753s smartd.service                                                           
 2.752s ModemManager.service                                                     
 2.601s mcelog.service                                                           
 2.144s dracut-initqueue.service                                                 
 1.868s postfix.service                                                          
 1.337s nscd.service                                                             
  787ms rtkit-daemon.service                                                     
  726ms klog.service                                                             
  687ms NetworkManager.service                                                   
  675ms kbdsettings.service                                                      
  639ms upower.service                                                           
  610ms systemd-backlight@backlight:intel_backlight.service                      
  567ms systemd-random-seed.service                                              
  521ms plymouth-read-write.service                                              
  518ms systemd-tmpfiles-setup.service                                           
  483ms systemd-journald.service                                                 
  449ms dracut-shutdown.service                                                  
  443ms auditd.service                                                           
  371ms plymouth-switch-root.service                                             
  350ms sysroot.mount                                                            
  347ms chronyd.service                                                          
  289ms dev-disk-by\x2duuid-9e6030ec\x2d0120\x2d4e60\x2d82f7\x2deee781c512ac.swap
  287ms logrotate.service                                                        
  253ms udisks2.service                                                          
  250ms boot-grub2-i386\x2dpc.mount                                              
  248ms user@1000.service                                                        
  231ms systemd-tmpfiles-setup-dev.service                                       
  226ms wpa_supplicant.service                                                   
  225ms modprobe@fuse.service                                                    
  210ms systemd-udev-trigger.service                                             
  208ms systemd-journal-flush.service                                            
  206ms modprobe@configfs.service                                                
  192ms initrd-parse-etc.service                                                 
  133ms systemd-vconsole-setup.service                                           
  126ms boot-grub2-x86_64\x2defi.mount                                           
  121ms root.mount                                                               
  120ms srv.mount                                                                
  118ms tmp.mount                                                                
  108ms systemd-modules-load.service                                             
   89ms plymouth-start.service                                                   
   88ms backup-sysconfig.service                                                 
   85ms dracut-cmdline.service                                                   
   77ms bluetooth.service                                                        
   63ms systemd-remount-fs.service                                               
   63ms dev-hugepages.mount                                                      
   62ms dev-mqueue.mount                                                         
   61ms sys-kernel-debug.mount                                                   
   60ms sys-kernel-tracing.mount                                                 
   52ms home.mount                                                               
   52ms var.mount                                                                
   51ms systemd-sysctl.service                                                   
   50ms sound-extra.service                                                      
   45ms systemd-update-utmp.service                                              
   40ms systemd-fsck-root.service                                                
   39ms opt.mount                                                                
   38ms dracut-pre-udev.service                                                  
   34ms kmod-static-nodes.service                                                
   32ms modprobe@drm.service                                                     
   30ms systemd-user-sessions.service                                            
   27ms initrd-cleanup.service                                                   
   21ms user-runtime-dir@1000.service                                            
   20ms \x2esnapshots.mount                                                      
   19ms usr-local.mount                                                          
   16ms systemd-rfkill.service                                                   
   15ms issue-generator.service                                                  
   13ms systemd-tmpfiles-clean.service                                           
   10ms systemd-update-utmp-runlevel.service                                     
    9ms initrd-udevadm-cleanup-db.service                                        
    5ms alsa-restore.service                                                     
    5ms check-battery.service                                                    
    5ms sys-kernel-config.mount                                                  
    4ms sys-fs-fuse-connections.mount                                            
lines 51-84/84 (END)

Alles anzeigen

Code

> systemd-analyze critical-chain
....
graphical.target @37.570s
└─display-manager.service @32.170s +5.398s
  └─time-sync.target @32.164s
    └─chronyd.service @31.816s +347ms
      └─network.target @31.801s
        └─NetworkManager.service @31.113s +687ms
          └─network-pre.target @31.111s
            └─wpa_supplicant.service @32.081s +226ms
              └─dbus.service @13.402s
                └─basic.target @13.398s
                  └─sockets.target @13.398s
                    └─pcscd.socket @13.398s
                      └─sysinit.target @11.932s
                        └─systemd-backlight@backlight:intel_backlight.service @14.149s +610ms
                          └─system-systemd\x2dbacklight.slice @14.147s
                            └─system.slice
                              └─-.slice

Alles anzeigen

uname · 16. September 2021

Zitat von sterun

Wie sieht generell die Bootzeit aus?

eher schlecht:

Code

 > systemd-analyze time
Startup finished in 4.153s (kernel) + 5.359s (initrd) + 41.334s (userspace) = 50.847s 
graphical.target reached after 37.570s in userspace

Beiträge von uname

Google-Earth mit mesa-libGLU (wenn das mal gut geht...)

Video-Wiedergabe ruckelt nach Neuinstallation - AMDgpu

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Boot-Vorgang optimieren (wenn es mal wieder länger...)

Ubuntu 26.10 „Stonking Stingray“ ist erschienen

Tumbleweed-Update bricht ab

KDE Plasma 6.8 verabschiedet sich von X11

VBox - gemeinsame Zwischenablage

Linux-Kernel: Kennzeichnungspflicht für KI-generierten Code soll entfallen

k.113

BlackPhoenix

aitexturegenerator

Giorgio68

pavelstr