On Sun, 2019-11-10 at 18:59 -0500, Sam Varshavchik wrote:
> I have the grub menu enabled. My poweroff procedure is to do a
> reboot, wait until I go back to the grub menu, stop the autoboot
> timer, and then hold the power key. This reliably shuts everything
> off, without putting stress on the 10-
On Mon, 11 Nov 2019 17:35:30 -0500
john.mel...@gmail.com wrote:
> It would appear that the problem is somehow related to booting an EFI
> partition.
Or something that got corrupted during the initial install. (But
I certainly have seen older machines where UEFI was very dodgy).
__
one of interesting/left question to me is:
why it had been working with the same bios config. on F30 and stopped it on F31
?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedo
On Sun, 2019-11-10 at 13:11 +0800, Ed Greshko wrote:
> On 11/10/19 12:56 PM, sixpack13 wrote:
> > okay, so we are both liars !
> > fine by me, "endowed" with that "competence" let's fix the OP pain
> > !
> > :-)
> >
> > the priciest questions are (just to put AND remove in one step a
> > topic on
On 11/11/19 10:21 PM, John Mellor wrote:
Ok, I installed the 5.4.0.0-0.rc6.git3.1.fc32 kernel from koji, but no effect
on the problem.
Next, I guess I can try the rawhide kernel.
I also swapped out the nVidia graphics card for an old ATI Cedar card, also to
no effect.
Another thing you may
On 2019-11-10 3:22 p.m., stan via users wrote:
On Sun, 10 Nov 2019 13:17:33 -0500
John Mellor wrote:
I'm starting to suspect a broken ACPI change in the newer kernel, but
I'm stuck...
Sure looks like it is a bug. Try installing the -debug kernel? At the
least it should give you more message
John Mellor writes:
Turning off rhgb and quiet at boot results in the unquiet shutdown, but no
more enlightenment. The screen output looks ok.
Doing a "systemctl poweroff" causes the same hang as the normal poweroff
from CLI or from GUI.
I have not yet tried the suggestion to relabel the
>
> When the system hangs, I have no keyboard or usable screen to debug
> with, as
> the system is almost all shutdown.
>
1)
is a second box and a null modem cable available to setup an serial console ?
currently I don't know/I'm unsure how to setup a serial console nowadays (did
that
On 11/10/19 10:17 AM, John Mellor wrote:
Turning off rhgb and quiet at boot results in the unquiet shutdown, but
no more enlightenment. The screen output looks ok.
Would you be able to type out what the last line on the screen is?
Doing a "systemctl poweroff" causes the same hang as the norma
On Sun, 10 Nov 2019 13:17:33 -0500
John Mellor wrote:
> I'm starting to suspect a broken ACPI change in the newer kernel, but
> I'm stuck...
Sure looks like it is a bug. Try installing the -debug kernel? At the
least it should give you more messages. You should probably open a
bugzilla again
On 2019-11-09 11:34 a.m., Tom Horsley wrote:
On Sat, 09 Nov 2019 11:00:42 -0500
john.mel...@gmail.com wrote:
I guess its possible that something is not completing its shutdown
step, but it does not appear to be logging that omission. Any idea how
to isolate which is the faulty daemon?
If you
s/inside/insight/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://f
agreed.
more inside in the log files needed.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct
On 11/10/19 12:56 PM, sixpack13 wrote:
okay, so we are both liars !
fine by me, "endowed" with that "competence" let's fix the OP pain !
:-)
the priciest questions are (just to put AND remove in one step a topic on my
list):
- OP, do have multi-card readers in your box ?
- do you or does fedora
okay, so we are both liars !
fine by me, "endowed" with that "competence" let's fix the OP pain !
:-)
the priciest questions are (just to put AND remove in one step a topic on my
list):
- OP, do have multi-card readers in your box ?
- do you or does fedora do "magic" mapping with them ?
- are th
On 11/10/19 12:22 PM, sixpack13 wrote:
I have read more then once in the howto's regarding upgrade that one task is to
do an relabeling.
I have never seen such recommendation. I'd rather defer to what Dan Walsh has
written on the subject:
Full relabelling of an SELinux machine should almos
On 11/10/19 10:45 AM, Ed Greshko wrote:
I'm not going to spend any time to determine when they do and when they don't.
They appear here on multiple systems, with no lvm,
OK, I lied.
I was curious as to why some the systems here had entries like
Nov 07 12:27:42 meimei.greshko.com lvm[43966]:
> On 11/10/19 10:25 AM, sixpack13 wrote:
>
> Nope
>
> But the point is,
the point is that I don't run lvm (esp. lvm2-monitor.service) since month/years.
so I was unable to see the OP message like "lvm[14772]: /dev/sdX: open
failed: No medium found" on my box.
therefore it appeared to m
On 11/10/19 10:25 AM, sixpack13 wrote:
okay,
journalctl | grep -i lvm
=>
Nov 08 03:07:27 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Nov 08 03:07:27 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket.
Nov 08 07:58:17 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Su
okay,
journalctl | grep -i lvm
=>
Nov 08 03:07:27 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Nov 08 03:07:27 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket.
Nov 08 07:58:17 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Nov 08 07:58:17 obelix.fritz.box
On 11/10/19 9:59 AM, sixpack13 wrote:
On 11/10/19 3:17 AM, sixpack13 wrote:
Those are "normal". If you check your own logs you will see the same thing.
there is no need to check my log's regarding lvm entries.
here is no lvm running !
so I can't know what is "normal" on lvm boxes.
and therefo
> On 11/10/19 3:17 AM, sixpack13 wrote:
>
> Those are "normal". If you check your own logs you will see the same thing.
>
there is no need to check my log's regarding lvm entries.
here is no lvm running !
so I can't know what is "normal" on lvm boxes.
and therefore I underwrote my prev. comment
On 11/10/19 12:00 AM, john.mel...@gmail.com wrote:
Git it. However, it is not showing any problems that I can see.
Excerpt from the log showing a shutdown and subsequent powerup:
=== excerpt start ===
ov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=
On 11/10/19 3:17 AM, sixpack13 wrote:
It hangs with a frozen window showing a stalled rotating
action indicator in Gnome, leaving the power on.
Wasn't hitting - I believe - ESC-Key a task to see what's going on on the
console.
what are sdb - sdf are ?
and what does the error "/dev/sdf: ope
On Sat, 9 Nov 2019 at 19:18, sixpack13 wrote:
> It hangs with a frozen window showing a stalled rotating
> > action indicator in Gnome, leaving the power on.
> >
>
> Wasn't hitting - I believe - ESC-Key a task to see what's going on on the
> console.
>
> what are sdb - sdf are ?
> and what does
It hangs with a frozen window showing a stalled rotating
> action indicator in Gnome, leaving the power on.
>
Wasn't hitting - I believe - ESC-Key a task to see what's going on on the
console.
what are sdb - sdf are ?
and what does the error "/dev/sdf: open failed: No medium
found" mean ?
wer
On 11/09/2019 09:56 AM, Anthony F McInerney wrote:
Yes i was also wondering when it's hanging, does the escape key work to
show the console?
Try it and find out.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On Sat, 9 Nov 2019 16:56:28 +
Anthony F McInerney wrote:
> > Yes i was also wondering when it's hanging, does the escape key
> > work to
> show the console?
I run a daemon that is usually sleeping at shutdown. If I don't
kill it manually, I get this error. Nothing I've tried does anythin
On Sat, 9 Nov 2019 at 16:35, Tom Horsley wrote:
> On Sat, 09 Nov 2019 11:00:42 -0500
> john.mel...@gmail.com wrote:
>
> > I guess its possible that something is not completing its shutdown
> > step, but it does not appear to be logging that omission. Any idea how
> > to isolate which is the faul
On Sat, 09 Nov 2019 11:00:42 -0500
john.mel...@gmail.com wrote:
> I guess its possible that something is not completing its shutdown
> step, but it does not appear to be logging that omission. Any idea how
> to isolate which is the faulty daemon?
If you turn off rhgb and quiet on the kernel boot
On Sat, 2019-11-09 at 23:00 +0800, Ed Greshko wrote:
> On 11/9/19 10:42 PM, john.mel...@gmail.com wrote:
> > I've had this problem ever since I moved up to Fedora 31 from
> > Fedora
> > 30. It fails to completely shutdown. It will reboot correctly,
> > but
> > not shutdown. It hangs with a froze
On 11/9/19 10:42 PM, john.mel...@gmail.com wrote:
I've had this problem ever since I moved up to Fedora 31 from Fedora
30. It fails to completely shutdown. It will reboot correctly, but
not shutdown. It hangs with a frozen window showing a stalled rotating
action indicator in Gnome, leaving th
I've had this problem ever since I moved up to Fedora 31 from Fedora
30. It fails to completely shutdown. It will reboot correctly, but
not shutdown. It hangs with a frozen window showing a stalled rotating
action indicator in Gnome, leaving the power on.
The machine is an older Gateway core-i7
33 matches
Mail list logo
