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="resume=UUI
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="resume=UUID=8e895273-b3ca-465e-b991-b7a
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=UUID=8e895..."
in
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=UUID=8e895..."
> >> in the file /etc/default/
On Mon, 2024-06-10 at 11:30 +0200, Klaus-Peter Schrage via users wrote:
> That was no problem
> until recent kernels which, as Barry stated, require that resume=
> refers to a physical partition.
That's not strictly true. You can arrange to resume to a BTRFS
subvolume. My boot params include:
res
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/kernel/cmdline f
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/kernel/cmdline file? I was tripped-up recently
becaus
> On 9 Jun 2024, at 13:06, Klaus-Peter Schrage via users
> wrote:
>
> What I already mentioned: It doesn't hang on kernel 6.8.9, only on more
> recent ones, with everything else left constant (e. g. no boot partition).
> --
The latest kernels require that resume= refers to an existing partit
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
Does your fstab or installati
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
Does your fstab or installation media or any other media used during or
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-disk-b
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
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... (t
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
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-disk-by\x2duuid-8e895running ...'
> The
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 part /home
└─sda4 8:4 0 151G 0 part
On 8 Jun 2024 at 18:20, Klaus-Peter Schrage via users wrote:
Date sent: Sat, 8 Jun 2024 18:20:26 +0200
To: users@lists.fedoraproject.org
Subject:Boot hangs on recent kernels
Send reply to: Community support for Fedora users
From
Klaus-Peter Schrage composed on 2024-06-08 18:20 (UTC+0200):
> 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 menti
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
19 matches
Mail list logo
