StuRa Diskussion:Install-Party/Fedora: Unterschied zwischen den Versionen

Aus Wiki StuRa HTW Dresden
Zur Navigation springen Zur Suche springen
 
(7 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)
Zeile 440: Zeile 440:
</pre>
</pre>
-->
-->
----
<!--
<pre>
[  223.617433] EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Quota mode: none.
[  277.589350] SELinux:  Context system_u:object_r:snappy_var_lib_t:s0 is not valid (left unmapped).
[  612.183196] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0xfffffffffffffffc flags=0x0030]
[  612.183204] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x40 flags=0x0020]
[  612.183207] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x1fc flags=0x0020]
[  612.183210] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x180 flags=0x0020]
[  612.183213] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x1c0 flags=0x0020]
[  612.183216] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x80 flags=0x0020]
[  612.183218] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x140 flags=0x0020]
[  612.183221] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x100 flags=0x0020]
[  612.183224] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x340 flags=0x0020]
[  612.183226] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x2c0 flags=0x0020]
[  642.324472] nvme nvme0: I/O 97 QID 3 timeout, aborting
[  642.388041] nvme nvme0: I/O 98 QID 3 timeout, aborting
[  642.562671] nvme nvme0: I/O 163 QID 7 timeout, aborting
[  642.568063] nvme nvme0: I/O 164 QID 7 timeout, aborting
[  642.601816] nvme nvme0: I/O 226 QID 8 timeout, aborting
[  642.601817] nvme nvme0: Abort status: 0x0
[  642.635973] nvme nvme0: Abort status: 0x0
[  642.640218] nvme nvme0: Abort status: 0x0
[  649.998246] nvme nvme0: I/O 35 QID 1 timeout, aborting
[  672.557471] nvme nvme0: I/O 97 QID 3 timeout, reset controller
[  702.793214] nvme nvme0: I/O 17 QID 0 timeout, reset controller
[  735.505844] nvme nvme0: Abort status: 0x371
[  735.505854] nvme nvme0: Abort status: 0x371
[  735.505857] nvme nvme0: Abort status: 0x371
[  736.113345] hrtimer: interrupt took 212891731 ns
[  736.360417] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 6.497 msecs
[  736.425344] perf: interrupt took too long (50942 > 2500), lowering kernel.perf_event_max_sample_rate to 3000
[  736.616868] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 171.883 msecs
[  736.832972] perf: interrupt took too long (1342998 > 63677), lowering kernel.perf_event_max_sample_rate to 1000
[  800.014261] nvme nvme0: I/O 17 QID 0 timeout, disable controller
[  800.281093] nvme nvme0: Removing after probe failure status: -4
[  800.287200] I/O error, dev nvme0n1, sector 5573696 op 0x1:(WRITE) flags 0x1800 phys_seg 9 prio class 0
[  800.287204] I/O error, dev nvme0n1, sector 38304264 op 0x0:(READ) flags 0x0 phys_seg 17 prio class 0
[  800.287205] I/O error, dev nvme0n1, sector 126200064 op 0x0:(READ) flags 0x1000 phys_seg 3 prio class 0
[  800.287207] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
[  800.287213] I/O error, dev nvme0n1, sector 5578112 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
[  800.287218] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
[  800.287218] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0
[  800.287229] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 1, rd 4, flush 0, corrupt 0, gen 0
[  800.287223] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 1, rd 3, flush 0, corrupt 0, gen 0
[  800.287251] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 2, rd 4, flush 0, corrupt 0, gen 0
[  800.287260] I/O error, dev nvme0n1, sector 28921496 op 0x0:(READ) flags 0x0 phys_seg 9 prio class 0
[  800.287265] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 2, rd 5, flush 0, corrupt 0, gen 0
[  800.287272] I/O error, dev nvme0n1, sector 25162600 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
[  800.287276] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 3, rd 5, flush 0, corrupt 0, gen 0
[  800.287278] BTRFS error (device dm-2): error loading props for ino 34305887 (root 257): -5
[  800.287280] BTRFS: error (device dm-2) in __btrfs_free_extent:3079: errno=-5 IO failure
[  800.287290] BTRFS info (device dm-2): forced readonly
[  800.287296] BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2159: errno=-5 IO failure
[  800.298242] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 3, rd 6, flush 0, corrupt 0, gen 0
[  800.298240] nvme0n1: detected capacity change from 500118192 to 0
[  800.298248] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 3, rd 7, flush 0, corrupt 0, gen 0
[  800.298491] BTRFS warning (device dm-2): Skipping commit of aborted transaction.
[  800.298494] BTRFS: error (device dm-2) in cleanup_transaction:1974: errno=-5 IO failure
[  800.304975] BTRFS: error (device dm-2) in free_log_tree:3461: errno=-5 IO failure
[  849.947301] btrfs_dev_stat_print_on_error: 46 callbacks suppressed
[  849.947308] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 36, flush 0, corrupt 0, gen 0
[  849.947407] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 37, flush 0, corrupt 0, gen 0
[  849.948401] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 38, flush 0, corrupt 0, gen 0
[  849.950301] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 39, flush 0, corrupt 0, gen 0
[  849.950423] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 40, flush 0, corrupt 0, gen 0
[  849.950559] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 41, flush 0, corrupt 0, gen 0
[  849.950619] BTRFS error (device dm-2): bdev /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 errs: wr 21, rd 42, flush 0, corrupt 0, gen 0
[  965.619293] FAT-fs (nvme0n1p1): unable to read boot sector to mark fs as dirty
</pre>
-->
===== home auf andere Platte sichern sichern =====
: <code>sudo mkdir /home_s</code>
: <code>sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /home_s/ -t btrfs -o subvol=home</code>
: <code>sudo mkdir /home_d</code>
: <code>sudo mount /dev/mapper/luks-9097c5bd-6d98-444c-b0a9-649835ee8ae2 /home_d/ -t btrfs</code>
: <code>rsync -a /home_s/Ich-5/ /home_d/</code>
: <code>sudo mkdir /root_s</code>
: <code>sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /root_s/ -t btrfs -o subvol=root</code>
: <code>mkdir /home_d/root</code>
: <code>sudo rsync -a /root_s /home_d/root</code>
== Fedora meets snapper ==
* https://sysguides.com/install-fedora-38-with-full-disk-encryption-snapshot-and-rollback-support/
== eigenen Kernel signieren (für [[wikipedia:en:secure boot|secure boot]]) ==
* https://sysguides.com/fedora-uefi-secure-boot-with-custom-keys/

Aktuelle Version vom 9. Oktober 2023, 05:24 Uhr

Probleme und Lösungen[Bearbeiten]

Treiber fehlen (nach dem versehentlichen Löschen durch dnf mit --allowerasing)

dnf install mesa-dri-drivers

wayland oder xorg[Bearbeiten]

echo $XDG_SESSION_TYPE
wayland

Verwaltung von Partionen[Bearbeiten]

dnf search blivet-gui
dnf install -y blivet-gui

Fedora Silverblue[Bearbeiten]

Suchen von Paketen[Bearbeiten]

rpm-ostree bietet keine Suche für Pakete.

Erstellen von einem allgemeinen Container, falls noch keiner erstellt ist

toolbox -y create
Created container: fedora-toolbox-33
Enter with: toolbox enter

Aulisten aller (nun verfügbaren) Abbilder für Container

toolbox list -i
IMAGE ID      IMAGE NAME                                        CREATED
92d6fdd7ebda  registry.fedoraproject.org/f33/fedora-toolbox:33  12 days ago

Aulisten aller (nun verfügbaren) Container

toolbox list -c
CONTAINER ID  CONTAINER NAME     CREATED        STATUS      IMAGE NAME
1234567890ab  fedora-toolbox-33  5 minutes ago  configured  registry.fedoraproject.org/f33/fedora-toolbox:33

Suchen von einem Paket (beispielsweise dem Paket ddate) mit dem standardmäßigen Programm zur Verwaltung von Paketen dnf von außerhalb vom Container im Container

toolbox run dnf search ddate


ddate.x86_64 : Convert Gregorian dates to Discordian dates



Entfernen vom allgemeinen Container, falls er nicht mehr gebraucht wird



toolbox rm fedora-toolbox-33


Entfernen vom Abbild für einen allgemeinen Container, falls es nicht mehr gebraucht wird



toolbox rmi registry.fedoraproject.org/f33/fedora-toolbox:33


Experiment KDE (Wayland) Silverblue[Bearbeiten]


toolbox run sudo dnf group info kde





Group: KDE
 Description: The KDE Plasma Workspaces, a highly-configurable graphical user interface which includes a panel, desktop, system icons and desktop widgets, and many powerful KDE applications.
 Mandatory Packages:
   NetworkManager-config-connectivity-fedora
   abrt-desktop
   adwaita-gtk2-theme
   akregator
   bluedevil
   breeze-icon-theme
   colord-kde
   cups-pk-helper
   dnfdragora
   dolphin
   earlyoom
   firewall-config
   glibc-all-langpacks
   gnome-keyring-pam
   gwenview
   initial-setup-gui
   kaddressbook
   kamera
   kcalc
   kcharselect
   kcm_systemd
   kcolorchooser
   kde-gtk-config
   kde-partitionmanager
   kde-print-manager
   kde-settings-pulseaudio
   kdegraphics-thumbnailers
   kdeplasma-addons
   kdialog
   kdnssd
   keditbookmarks
   kf5-akonadi-server
   kf5-akonadi-server-mysql
   kf5-baloo-file
   kf5-kipi-plugins
   kfind
   kget
   kgpg
   khelpcenter
   khotkeys
   kinfocenter
   kmag
   kmail
   kmenuedit
   kmousetool
   kmouth
   konsole5
   kontact
   korganizer
   kruler
   kscreen
   kscreenlocker
   ksshaskpass
   ksysguard
   kwalletmanager5
   kwebkitpart
   kwin
   kwrite
   pam-kwallet
   phonon-qt5-backend-gstreamer
   pinentry-qt
   plasma-breeze
   plasma-desktop
   plasma-desktop-doc
   plasma-discover
   plasma-drkonqi
   plasma-nm
   plasma-nm-l2tp
   plasma-nm-openconnect
   plasma-nm-openswan
   plasma-nm-openvpn
   plasma-nm-pptp
   plasma-nm-vpnc
   plasma-pa
   plasma-pk-updates
   plasma-user-manager
   plasma-workspace
   plasma-workspace-geolocation
   polkit-kde
   qt5-qtbase-gui
   qt5-qtdeclarative
   sddm
   sddm-breeze
   sddm-kcm
   spectacle
   xorg-x11-drv-libinput
 Conditional Packages:
   qt-at-spi



https://pagure.io/workstation-ostree-config/blob/master/f/kde-desktop-pkgs.yaml



btw


2020-11-16:


rpm-ostree install plasma-drkonqi


failed



rpm-ostree install initial-setup-gui


failed






systemctl disable gdm


systemctl enable sddm




Auswaehlen von Plasma (Wayland) bei der Anmeldung



echo $XDG_SESSION_TYPE


wayland



Logo Fedora Silverblue[Bearbeiten]



wget -c https://silverblue.fedoraproject.org/public/silverblue-logo.svg


wget -c https://silverblue.fedoraproject.org/public/silverblue-black.svg


wget -c https://silverblue.fedoraproject.org/public/silverblue-white.svg


systemd management GUI[Bearbeiten]


systemd control module von KDE[Bearbeiten]


Installieren vom Paket kcm_systemd ()



sudo dnf -y install kcm_systemd


Starten der Anwendung kcm_systemd



kcmshell5 kcm_systemd


System von USB (live) erreichen[Bearbeiten]


Mit dem Programm (GUI) Disks den Massenspeicher vom System entschluesseln.



sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /mnt -t btrfs -o subvol=root


ls /mnt


sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /mnt/home -t btrfs -o subvol=home


ls /mnt/home/


sudo mount /dev/nvme0n1p2 /mnt/boot


sudo mount /dev/nvme0n1p1 /mnt/boot/efi


sudo mount --bind /dev /mnt/dev


sudo mount -t proc /proc /mnt/proc


sudo mount -t sysfs /sys /mnt/sys


sudo mount -t tmpfs tmpfs /mnt/run


mkdir -p /mnt/run/systemd/resolve/


echo 'nameserver 9.9.9.9' > /mnt/run/systemd/resolve/stub-resolv.conf


sudo chroot /mnt




ping heise.de


sudo flatpak update


sudo dnf update


ls -l /lib64/libcrypto.so.3


rm /lib64/libcrypto.so.3


ln /lib64/libcrypto.so.3.0.5 /lib64/libcrypto.so.3


sudo dnf update


rm /lib64/libssl.so.3


ln -s /lib64/libssl.so.3.0.5 /lib64/libssl.so.3


sudo dnf update


rm /lib64/liblzma.so.5


ln -s /lib64/liblzma.so.5.2.5 /lib64/liblzma.so.5











home auf andere Platte sichern sichern[Bearbeiten]


sudo mkdir /home_s


sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /home_s/ -t btrfs -o subvol=home


sudo mkdir /home_d


sudo mount /dev/mapper/luks-9097c5bd-6d98-444c-b0a9-649835ee8ae2 /home_d/ -t btrfs


rsync -a /home_s/Ich-5/ /home_d/


sudo mkdir /root_s


sudo mount /dev/mapper/luks-d7064367-0e36-4dce-a0de-94401230d6f4 /root_s/ -t btrfs -o subvol=root


mkdir /home_d/root


sudo rsync -a /root_s /home_d/root


Fedora meets snapper[Bearbeiten]



eigenen Kernel signieren (für secure boot)[Bearbeiten]




Abgerufen von „https://wiki.stura.htw-dresden.de/index.php?title=StuRa_Diskussion:Install-Party/Fedora&oldid=43970“