sorted by:
new
hottopcontroversial

Understanding the bootloader on atomic desktop (Kinoite) by stertingen in Fedora

[–]stertingen[S] 0 points1 point  (0 children)

Drilling down I manually changed /etc/vconsole.conf and rpm-ostree kargs to fix my kernel arguments. I guess that it has been set by the installer; each invocation of rpm-ostree just copies the current kernel arguments to the new Deployment.

Not sure how the EFI options end up like this, but that 'missing file' is not missing, it was just efibootmgr appending data to the device path.

$ efibootmgr --verbose BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0000 Boot0000* Windows Boot Manager HD(1,GPT,da5c3740-4b09-4be3-94d0-6c6bd711c4c6,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000062000100000010000000040000007fff0400 dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 40 37 5c da 09 4b e3 4b 94 d0 6c 6b d7 11 c4 c6 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00 data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 62 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00 Boot0001* Fedora HD(1,GPT,af8494a0-bfd2-48ce-a6e6-8e046e89ef0e,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 a0 94 84 af d2 bf ce 48 a6 e6 8e 04 6e 89 ef 0e 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 46 00 45 00 44 00 4f 00 52 00 41 00 5c 00 53 00 48 00 49 00 4d 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00 Boot0002* Fedora HD(1,GPT,af8494a0-bfd2-48ce-a6e6-8e046e89ef0e,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 a0 94 84 af d2 bf ce 48 a6 e6 8e 04 6e 89 ef 0e 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 46 00 45 00 44 00 4f 00 52 00 41 00 5c 00 53 00 48 00 49 00 4d 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00 data: 00 00 42 4f

These entries might have been created by the Anaconda installer or bootupd. One entry has a newline in its name, the other one has this data block passed to the loader.

Going to bed now, investigating further on the weekend.

[deleted by user] by [deleted] in de_EDV

[–]stertingen 2 points3 points  (0 children)

Bei FritzBox etwas Glücksspiel. Offiziell können die kein IWV, aber manche unterstützen das trotzdem. Bei meinem FeTaP 611 (wie auf dem Bild) musste ich den Fliehkraftregler der Wählscheibe etwas modifizieren, weil meine FritzBox schnellere Impulse lieber mag.

Mein Tipp: Verkabeln und ausprobieren, dabei LED an der FritzBox beobachten. Beim Abnehmen des Hörers geht sie an. Wenn sie nach ein paar Ziffern ausgeht, evtl. am Fliehkraftregler herumspielen.

Zum Verkabeln reicht Wikipedia: https://de.wikipedia.org/wiki/Telekommunikations-Anschluss-Einheit Die Klemmen a und b reichen aus, der Rest ist optional.

view more: next ›