Re: make a bootable dvd

2024-07-08 Thread Klaus-Peter Schrage via users
Am 08.07.2024 um 17:41 schrieb Patrick Dupre via users: There is a fedora tool Fedora Media Writer (see fedora web site) also unebootin On 7/8/24 10:01 AM, François Patte wrote: Bonjour, I downloaded the f40 iso for a worksation, but I did not see on the fedora website how to burn a bootab

Re: Boot hangs on recent kernels

2024-06-10 Thread Klaus-Peter Schrage via users
Am 10.06.24 um 18:39 schrieb Go Canes: On Mon, Jun 10, 2024 at 11:17 AM Klaus-Peter Schrage via users wrote: Thanks! You're welcome! Well, I followed https://fedoramagazine.org/setting-kernel-command-line-arguments-with-fedora-30/ and # grubby --update-kernel=ALL --remove-args=&q

Re: Boot hangs on recent kernels

2024-06-10 Thread Klaus-Peter Schrage via users
Am 10.06.24 um 13:05 schrieb Go Canes: On Mon, Jun 10, 2024 at 5:31 AM Klaus-Peter Schrage via users wrote: Am 09.06.2024 um 20:09 schrieb Go Canes: On Sun, Jun 9, 2024 at 7:47 AM Klaus-Peter Schrage via users wrote: What I don't understand: What produced the entry "resume=

Re: Boot hangs on recent kernels

2024-06-10 Thread Klaus-Peter Schrage via users
Am 09.06.2024 um 20:09 schrieb Go Canes: On Sun, Jun 9, 2024 at 7:47 AM Klaus-Peter Schrage via users wrote: What I don't understand: What produced the entry "resume=UUID=8e895..." in the file /etc/default/grub which was created on the install date, May 3rd? Do you have a /etc

Re: Boot hangs on recent kernels

2024-06-09 Thread Klaus-Peter Schrage via users
Am 09.06.2024 um 15:22 schrieb Felix Miata: Klaus-Peter Schrage via users composed on 2024-06-09 13:47 (UTC+0200): What I don't understand: What produced the entry "resume=UUID=8e895..." in the file /etc/default/grub which was created on the install date, May 3rd Doe

Re: Boot hangs on recent kernels

2024-06-09 Thread Klaus-Peter Schrage via users
Am 08.06.24 um 22:27 schrieb Jeffrey Walton: On Sat, Jun 8, 2024 at 12:20 PM Klaus-Peter Schrage via users wrote: Since kernel 6.8.10-300.fc40.x86_64, boot hangs on KDE Plasma (kernel 6.8.9-300.fc40.x86_64 was the last good one). I found that there is a job running infinitely: 'Job dev

Re: Boot hangs on recent kernels

2024-06-09 Thread Klaus-Peter Schrage via users
Am 08.06.24 um 22:04 schrieb Samuel Sieb: On 6/8/24 9:20 AM, Klaus-Peter Schrage via users wrote: This is a rather fresh install of fedora 40 (running on ext4): da  8:0    0 232,9G  0 disk ├─sda1   8:1    0   1,1G  0 part /boot ├─sda2   8:2    0  49,1G  0 part / ├─sda3   8:3    0  31,7G  0

Re: Boot hangs on recent kernels

2024-06-09 Thread Klaus-Peter Schrage via users
Am 08.06.24 um 19:52 schrieb Michael D. Setzer II: On 8 Jun 2024 at 18:20, Klaus-Peter Schrage via users wrote: might want to run blkid and see what it reports. The output is similar to yours, but # blkid | grep -i 8e8952 # shows that there isnt any device with an UUID containing 8e8952

Re: Boot hangs on recent kernels

2024-06-09 Thread Klaus-Peter Schrage via users
Am 08.06.24 um 19:04 schrieb Felix Miata: Klaus-Peter Schrage composed on 2024-06-08 18:20 (UTC+0200): Does any device within your system actually include 8e895whatever within it? No, there isn't any block device with an UUID (or PARTUUID) that includes 8e895 Did you previously have a swap par

Boot hangs on recent kernels

2024-06-08 Thread Klaus-Peter Schrage via users
Since kernel 6.8.10-300.fc40.x86_64, boot hangs on KDE Plasma (kernel 6.8.9-300.fc40.x86_64 was the last good one). I found that there is a job running infinitely: 'Job dev-disk-by\x2duuid-8e895running ...' The above mentioned UUID (8e895 ...) corresponds to the kernel 'resume=uuid=...' comma

Unwanted dialogs when starting Dolphin file manager

2024-05-02 Thread Klaus-Peter Schrage via users
On a fresh install of Fedora 40 KDE Plasma, after opening Dolphin, two windows pop up: "Online Accounts", asking "+ Add New Account" "Authentication Dialog", asking for a password What happened before: I had been struggling for a while to automount a smb sare via /etc/fstab (in fact, the share is

Re: Stuck at grub prompt after reordering partitions

2024-04-22 Thread Klaus-Peter Schrage via users
Am 21.04.24 um 18:34 schrieb Go Canes: On Sun, Apr 21, 2024 at 12:15 PM Klaus-Peter Schrage via users wrote: /boot/efi/EFI/fedora/grub.cfg: search --no-floppy --root-dev-only --fs-uuid --set=dev 206c0b5f-eddf-42e8-96f1-e666c5635cd0 set prefix=($dev)/grub2 export $prefix

Re: Stuck at grub prompt after reordering partitions

2024-04-21 Thread Klaus-Peter Schrage via users
Am 20.04.24 um 23:16 schrieb George N. White III: I assume you can still boot with manual grub commands. Yes, linux ..., initrd ..., boot or: >configfile (hd0,1)/grub2/grub.cfg which immediately brings back the grub menu. Retrace your steps and double check UUID's, other typos, and misplaced q

Re: Stuck at grub prompt after reordering partitions

2024-04-20 Thread Klaus-Peter Schrage via users
Am 20. April 2024 20:51:04 MESZ schrieb Lester Petrie : > > >On 4/20/2024 1:14 PM, Klaus-Peter Schrage via users wrote: >> I am really grateful for your detailed explanation! >> I went through all the steps, checked the IDs from efibootmgr and blkid >> with respect t

Re: Stuck at grub prompt after reordering partitions

2024-04-20 Thread Klaus-Peter Schrage via users
Am 19.04.24 um 16:58 schrieb Go Canes: The basic process is EFI is using its variables (which you can examine with efibootmgr) to find a device and the file on the device to use for the boot. That should be on the *.efi files in /boot/efi/EFI/fedora/. That in term should load grub2, which will

Re: Stuck at grub prompt after reordering partitions

2024-04-19 Thread Klaus-Peter Schrage via users
Am 17.04.24 um 18:45 schrieb Felix Miata: Klaus-Peter Schrage via users composed on 2024-04-17 16:48 (UTC+0200): After many years of maintaing dual boot setups (Fedora/Windows) my harddisk layout got a bit confusing: Linux and Windows partition were scattered on mainly two harddisks (all gpt

Re: Stuck at grub prompt after reordering partitions

2024-04-19 Thread Klaus-Peter Schrage via users
Am 17.04.24 um 17:51 schrieb Go Canes: Step by step: I recently had similar problems. These are the things to check: o use blkid to get the current UUID(s) The current UUIDs correspond to the ones in /etc/fstab, that hadn't been changed btw. o check /etc/kernel/cmdline if it exists - make sure

Re: Stuck at grub prompt after reordering partitions

2024-04-17 Thread Klaus-Peter Schrage via users
at 10:48 AM Klaus-Peter Schrage via users wrote: But rebooting still gets me to the dreaded grub>. So what am I missing? BTW, I did NOT use the grub2-install command which shoud not be used on UEFI systems. I recently had similar problems. These are the things to check: o use blkid to get the

Stuck at grub prompt after reordering partitions

2024-04-17 Thread Klaus-Peter Schrage via users
After many years of maintaing dual boot setups (Fedora/Windows) my harddisk layout got a bit confusing: Linux and Windows partition were scattered on mainly two harddisks (all gpt). I was able to free a third harddisk (ssd) and copied the linux partitions boot, root and home over to the new disk,

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users
Am 29.12.23 um 17:48 schrieb Jeffrey Walton: But an issue remains: Why got mysystem mal-labelled? I didn't do many things to it after the upgrade, and shouldn't be labelling be part of the system-upgrade process? But thanks again for your help. There are several post-upgrade steps that may be

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users
Am 29.12.23 um 16:36 schrieb Barry Scott: On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users wrote: Recently, I did an upgrade to F39 via dnf system-upgrade. For the first time in Fedora (I think I started around version 1), on booting into KDE I get a message saying "limited ne

Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users
Recently, I did an upgrade to F39 via dnf system-upgrade. For the first time in Fedora (I think I started around version 1), on booting into KDE I get a message saying "limited network connectivity", which means, my wired network is up but can't reach the outside world. The journals tell me that