On 2020-03-20 05:15, Ed Greshko wrote:
> On 2020-03-20 04:15, home user wrote:
>> No, that's the GPU temperature. I'm wanting the temperature in the Intel
>> Core i7.
> OK, I misread your post.
>
> Have you tried "sensors"?
>
> [egreshko@meimei ~]$ sensors
> coretemp-isa-
> Adapter: ISA adap
On 2020-03-20 04:15, home user wrote:
> No, that's the GPU temperature. I'm wanting the temperature in the Intel
> Core i7.
OK, I misread your post.
Have you tried "sensors"?
[egreshko@meimei ~]$ sensors
coretemp-isa-
Adapter: ISA adapter
Core 0: +38.0°C (high = +82.0°C, crit = +98
I did my weekly patches this morning. As Samuel predicted early in this
thread, if I deleted the 2 *rescue* files from /boot, the rescue would
be re-built the next time the OS was patched. That happened. I can
boot into it successfully. I do understand that's not what I'm wanting
anyway.
If your graphics are still ok, I prefer gkellm to read temps and display
loads.
70C is at the very upper end of acceptable cpu temps, and is probably
the root cause of your lockups. How hot is the intake airflow? Check
the airflow for obstructions like dirt or cat-hair, and then pull the
co
On Thu, 19 Mar 2020 at 00:58, home user wrote:
> (I'm not sure who I'm replying to!)
>
> I realize I'm not a good writer, but am I really this bad?!
>
It would be helpful to have one message to collect all the details. I'm
following issues across multiple forums and it is easy to get confused
On 2020-03-19 11:57, home user wrote:
> During a typical session (booted from the hard drive), I (even as an
> unprivileged user) can launch the NVIDIA X Server Settings GUI to look at the
> GPU temperature. Is there a way to check the CPU temperature during a
> typical session (root, admin, or
(I'm not sure who I'm replying to!)
I realize I'm not a good writer, but am I really this bad?!
The "freezes" are not screen blankings. After booting the F31 live
image from the USB stick,
I launched Firefox. I started typing in the URL to load the fedora
HYPERKITTY. Midway through that, th
On Wed, 18 Mar 2020 at 18:44, Samuel Sieb wrote:
> On 3/18/20 2:09 PM, Andy Paterson via users wrote:
> > I have a coolermaster cosmos case & diy system it has no reset button!
> > It sounds like your setup is similar.
> > Without a hardware reset, add-on cards like graphics or network cards
> ar
On 3/18/20 2:09 PM, Andy Paterson via users wrote:
I have a coolermaster cosmos case & diy system it has no reset button!
It sounds like your setup is similar.
Without a hardware reset, add-on cards like graphics or network cards are not
actually reset to initialise them.
I have to physically sw
On Wed, 18 Mar 2020 at 17:22, home user wrote:
> (replying to my post yesterday at 9:55 PM)
>
> > I'll try what you [George] suggest tomorrow.
>
> Powered down.
> Disconnected speaker and monitors.
> Removed sound board and graphics card (difficult!).
>
> I tried to find a place to reconnect one
I have a coolermaster cosmos case & diy system it has no reset button!
It sounds like your setup is similar.
Without a hardware reset, add-on cards like graphics or network cards are not
actually reset to initialise them.
I have to physically switch off mains power/disconnect the psu & wait a min
(replying to my post yesterday at 9:55 PM)
> I'll try what you [George] suggest tomorrow.
Powered down.
Disconnected speaker and monitors.
Removed sound board and graphics card (difficult!).
I tried to find a place to reconnect one monitor. Searched front, back,
both sides, and top of the tow
(On 2020-03-18 6:50 a.m., John wrote)
> ... You stated that you started getting overheat warnings
> when you ran the old recovery kernel, and shut it down. ...
The sequence:
1. System booted from f30 Live Image on USB stick.
2. System "froze". The CPU fan got load, suggesting that the CPU was
(On 3/17/20 9:49 PM, Samuel wrote)
> Nouveau is the open source reverse-engineered driver
> for NVidia graphics cards.
ok, Thank-you.
> Download that file and use mediawriter to write it
> to the USB drive.
Done.
Did a minimal test. (For obvious reasons, I did not go far!)
I'm satisfied.
> I
On Wed, 2020-03-18 at 08:50 -0400, John Mellor wrote:
> I suspect that either the processor or video card cooling fins are
> plugged with dust, or that the heat transfer goop on the top of the
> processor has dried out and you are not transferring enough heat
> away when under load.
Related to t
On Wed, 18 Mar 2020 at 09:51, John Mellor wrote:
> Something keeps bugging me about what you described as symptoms. You
> stated that you started getting overheat warnings when you ran the old
> recovery kernel, and shut it down. That should never happen unless the
> machine was not correctly bu
Something keeps bugging me about what you described as symptoms. You
stated that you started getting overheat warnings when you ran the old
recovery kernel, and shut it down. That should never happen unless the
machine was not correctly built.
I suspect that either the processor or video card
On 3/17/20 8:55 PM, home user wrote:
(On Tue, 17 Mar 2020 at 06:16, George wrote)
(responding to the whole message)
I'll try what you suggest tomorrow. I have only the one workstation. No
cell phone or mobile device, no laptops or notebooks, no wifi, old PCs,
etc. Not even old parts. So th
(On Tue, 17 Mar 2020 at 06:16, George wrote)
(responding to the whole message)
I'll try what you suggest tomorrow. I have only the one workstation.
No cell phone or mobile device, no laptops or notebooks, no wifi, old
PCs, etc. Not even old parts. So the test will be removing the
graphics
On 3/17/20 8:35 PM, home user wrote:
(On 3/17/20 3:42 PM, Samuel wrote)
> If this was mentioned in a previous email, I missed it.
You did not miss anything (unless I've forgotten some of what I wrote!)
I forgot: Is nouveau the one that come from rpmfusion or the proprietary
one? I have the o
(On 3/17/20 3:42 PM, Samuel wrote)
> If this was mentioned in a previous email, I missed it.
You did not miss anything (unless I've forgotten some of what I wrote!)
I forgot: Is nouveau the one that come from rpmfusion or the proprietary
one? I have the one that comes from rpmfusion, and is au
On Tue, 17 Mar 2020 at 17:14, home user wrote:
> (On Tue, 17 Mar 2020 at 06:17, George wrote)
>
> > You need to rule out hardware.
> Impossible.
> Good testing can make a really good case that it's not the hardware (nor
> the driver).
> Complete testing, 100% ruling out, impossible.
>
2 or 3 9'
On Tue, 17 Mar 2020 at 14:47, home user wrote:
> (On 3/16/20 11:36 PM, Samuel wrote)
> > I assume you're using the original released F31 live image.
>
> No, I'm using whatever F-30 live image the Fedora Media Writer grabbed
> on March 12. Ah, here it is:
> Fedora-Workstation-Live-x86_64-30-1.2.
On 3/17/20 1:13 PM, home user wrote:
is that all? The graphics driver (the one that came from rmpfusion) is
still there, and my impression is that getting those out will be messy,
time-consuming, and risky. Then later I'd have to put them back, also
messy, time-consuming, and risky. If the s
(On Tue, 17 Mar 2020 at 06:17, George wrote)
> You need to rule out hardware.
Impossible.
Good testing can make a really good case that it's not the hardware (nor
the driver).
Complete testing, 100% ruling out, impossible.
I must live with practical limits same as everyone else.
> To narrow th
On 3/17/20 10:46 AM, home user wrote:
(On 3/16/20 11:36 PM, Samuel wrote)
> I assume you're using the original released F31 live image.
No, I'm using whatever F-30 live image the Fedora Media Writer grabbed
on March 12. Ah, here it is:
Fedora-Workstation-Live-x86_64-30-1.2.iso
I do not know
(On 3/16/20 11:36 PM, Samuel wrote)
> I assume you're using the original released F31 live image.
No, I'm using whatever F-30 live image the Fedora Media Writer grabbed
on March 12. Ah, here it is:
Fedora-Workstation-Live-x86_64-30-1.2.iso
I do not know how up-to-date that actually is.
> Or y
On Tue, 17 Mar 2020 11:17:10 -0300
George N. White III wrote:
> This can be hardware or a driver issue. Graphics is a prime suspect.
> Live distros are useful for checking hardware compatibility.
Freezing display is the symptom I always get with nvidia
hardware and the nouveau drivers. The first
On Mon, 16 Mar 2020 at 21:58, home user wrote:
> Let's go back to the core problems and need.
>
> The problems:
> 1. Fedora Live (made last week, on a USB-2 stick) sometimes freezes
> shortly after the boot is done. That is, when I'm typing or scrolling,
> the display stops changing, the cursor
On 3/16/20 5:57 PM, home user wrote:
The problems:
1. Fedora Live (made last week, on a USB-2 stick) sometimes freezes
shortly after the boot is done. That is, when I'm typing or scrolling,
the display stops changing, the cursor does not respond to the
trackball, and nothing happens when I ty
On 2020-03-17 08:53, home user wrote:
> I agree with Samuel: it's the same as the memory test on the Fedora Live USB
> flash drive.
FWIW, I don't think I implied that the test was different. I was simply
pointing out an alternate method
to access the test which one may find convenient.
--
Th
Let's go back to the core problems and need.
The problems:
1. Fedora Live (made last week, on a USB-2 stick) sometimes freezes
shortly after the boot is done. That is, when I'm typing or scrolling,
the display stops changing, the cursor does not respond to the
trackball, and nothing happens w
I realize that this is generally frowned on, but I believe this is one
of those situations where it's best to reply to a multiple posts at once.
I did not see Samuel's response to Ed's suggestion regarding
/usr/sbin/memtest-setup until after I tried it. It worked. Perfect
score. I agree wit
On Mon, 2020-03-16 at 08:33 -0300, George N. White III wrote:
> Connectors and cables are far more prone to failure than chips.
That includes plug-in cards.
I found cards would walk out of their slots due to thermal expansion,
and people picking up and moving their PC. They're only screwed in at
On Mon, 16 Mar 2020 at 00:41, home user wrote:
> (On 3/15/20 2:59 PM, Samuel wrote)
> > Right after you select the USB flash drive from the bios menu,
> > you should get a grub menu that's titled something like
> > "Fedora Workstation Live".
>
> Thank-you. Found it. Ran the memory test. It
On 3/15/20 8:40 PM, home user wrote:
Is there a reasonably easy, short, and reliable way to test
* the CPU(s) (is that the correct term?) (Intel Core -7-3770K CPU @
3.5...)?
Maybe a benchmarking program, but it's unlikely that you have a problem
there.
* the power supply?
* the data bus (i
On 3/15/20 8:52 PM, home user wrote:
(On 2020-03-16 06:44 PM, Ed wrote)
> Or, and I haven't tried this, do what is indicated
> in the "dnf info memtest86+" and
Though I've now already done the memory test as Samuel suggested, this
looks worthwhile. The other one took a long time. I assu
On 2020-03-16 11:40, home user wrote:
>
> > ... but the net install boot has a real rescue option.
> I'm looking here:
> "https://getfedora.org/en/workstation/download/";
> and I don't see it. Where should I be looking? (or maybe I'm looking for
> the wrong thing?)
Go to https://alt.fedoraproj
(On 2020-03-16 06:44 PM, Ed wrote)
> Or, and I haven't tried this, do what is indicated
> in the "dnf info memtest86+" and
Though I've now already done the memory test as Samuel suggested, this
looks worthwhile. The other one took a long time. I assume this memory
test will, too. So I'll
(On 3/15/20 2:59 PM, Samuel wrote)
> Right after you select the USB flash drive from the bios menu,
> you should get a grub menu that's titled something like
> "Fedora Workstation Live".
Thank-you. Found it. Ran the memory test. It took a long time, but I
like that it kept me informed. The w
On 2020-03-16 06:13, Samuel Sieb wrote:
> The memory tester needs to be run with nothing else running, not even an OS.
> It needs full access to the hardware. That's what memtest does.
He may also consider going here, https://www.memtest86.com/memtest86.html, and
download the
free version.
On 3/15/20 2:59 PM, home user wrote:
(On 3/14/20 6:33 PM, Samuel wrote)
> That's probably not what you think it is. ...
Well, what I thought it was, was that when it was done booting, all I
would get is an old-fashioned command line interface, with many but not
all Linux commands. No GUIs.
(On 3/14/20 6:33 PM, Samuel wrote)
> That's probably not what you think it is. ...
Well, what I thought it was, was that when it was done booting, all I
would get is an old-fashioned command line interface, with many but not
all Linux commands. No GUIs. It should have ls, vim, grep, more, cd
On 3/15/20 2:28 PM, home user wrote:
(On 2020-03-14 05:06, Ed wrote)
> Use a live image instead.
Though I just made it last week, it does not work well. It sometimes
"freezes" within a very short time of the completion of it booting. When
shutting down, it sometimes seems to get the cpu into
(On 2020-03-14 05:06, Ed wrote)
> Use a live image instead.
Though I just made it last week, it does not work well. It sometimes
"freezes" within a very short time of the completion of it booting.
When shutting down, it sometimes seems to get the cpu into a tight loop
that gets the cpu hot e
On 3/14/20 7:52 PM, John Mellor wrote:
"home user" asked:
> How do I rescue the rescue mode?
I think the root cause of the problem is that you have upgraded multiple
times, and somewhere along the way (maybe around the F25 timeframe), the
management of the rescue image and its grub entry got
"home user" asked:
> How do I rescue the rescue mode?
I think the root cause of the problem is that you have upgraded multiple
times, and somewhere along the way (maybe around the F25 timeframe), the
management of the rescue image and its grub entry got lost by the release
and testing teams, and
On 3/14/20 12:53 PM, home user wrote:
I chose the line
"Fedora (0-rescue-[32 hex digits]) 30 (Thirty)"
That's probably not what you think it is. By default the initrds have a
very limited number of drivers, intended to be the minimum required to
boot the current hardware. The rescue image h
On 2020-03-15 03:53, home user wrote:
> How do I rescue the rescue mode?
Use a live image instead.
--
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to use
Robert G. (Doc) Savage wrote:
> You can also use the much smaller (220 MB) boot.iso CD image.
I guess I could just have gone to the command shell and run the install
command, eh? Just get to the grub shell and run root and setup commands. I
never thought of that until now. I thought I had to ru
On 01/28/2011 06:47 AM, Roberto Ragusa wrote:
> In this case the usual failure scenario is that someone sees a
> wrong time in the BIOS (UTC) and "corrects" it to the local time.
BTDTGTTS.
My desktop has Win98 on it, although I only boot into it once a year or
so. (There are one or two programs
On Fri, Jan 28, 2011 at 3:47 PM, Roberto Ragusa wrote:
> Try the registry switch to let Windows run the hw clock in UTC mode,
> as suggested by someone else.
> Never tried if it really works. But at least it will leave your
> hw clock alone and Linux will never be affected.
>
I have used it with
On 01/27/2011 07:58 PM, Rick Stevens wrote:
> IIRC, Windows forces the hardware clock to the local time. If you
> intend to dual-boot between Winblows and Linux, uncheck the "System
> clock uses UTC" button in system-config-date "Time Zone" tab and adjust
> your clock again to make sure it's righ
Petrus de Calguarium:
>>> Windows changed the system clock from UTC to local time, so fedora
>>> needed to do a complete relabelling before I could finally boot up
>>> again.
Tim:
>> I can't see why that was necessary.
Petrus de Calguarium:
> I've experienced it before. It says something like the
Andre Robatino fedoraproject.org> writes:
> There's a registry hack, which I use on both XP and Vista, and should work on
> Windows 7 as well, that will make Windows interpret the hardware clock as UTC
> (search for "registry UTC"). It works fine for me, though I've heard there may
> be issues wi
On 01/27/2011 10:14 AM, Petrus de Calguarium wrote:
> Tim wrote:
>
>> On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
>>> Windows changed the system clock from UTC to local time, so fedora
>>> needed to do a complete relabelling before I could finally boot up
>>> again.
>>
>> I can't
Tim wrote:
> On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
>> Windows changed the system clock from UTC to local time, so fedora
>> needed to do a complete relabelling before I could finally boot up
>> again.
>
> I can't see why that was necessary.
>
I've experienced it before.
On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
> Windows changed the system clock from UTC to local time, so fedora
> needed to do a complete relabelling before I could finally boot up
> again.
I can't see why that was necessary.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.f
Gabriel Ramirez wrote:
> maybe http://boot.fedoraproject.org/index can be useful
>
Thank you. I had downloaded it about a year ago when I first heard about it,
but never tried it. I decided to get a new version, in case it changed, and
burnt it to disk. It must have taken 15-20 minutes for it
Robert G. (Doc) Savage wrote:
> You can also use the much smaller (220 MB) boot.iso CD image. You can
> find it on a mirror site at:
>
> .../releases/14/Fedora/x86_64/os/images/boot.iso
>
I already tried that. It didn't work. A black screen appeared with a grub menu
and it was not able to dete
On Wed, 2011-01-26 at 13:22 -0700, Petrus de Calguarium wrote:
> OK. Thanks to both of you. Yes, I had feared that this might be the only way.
>
> I didn't want to have to download 700MB just to be able to reinstall grub,
> but
> I guess that is the only way.
>
> I don't have an installation di
On 01/26/2011 02:22 PM, Petrus de Calguarium wrote:
> OK. Thanks to both of you. Yes, I had feared that this might be the only way.
>
> I didn't want to have to download 700MB just to be able to reinstall grub, but
> I guess that is the only way.
>
> I don't have an installation disk, since I did a
OK. Thanks to both of you. Yes, I had feared that this might be the only way.
I didn't want to have to download 700MB just to be able to reinstall grub, but
I guess that is the only way.
I don't have an installation disk, since I did a system upgrade from f13 to
f14. I no longer have the f13 in
On Wed, 2011-01-26 at 10:57 -0700, Petrus de Calguarium wrote:
> Which disk would I download to get into rescue mode on F14 x86_64?
>
> All I need to do is reinstall grub, after (hopefully) repairing a broken
> Windows XP that I have not been able to boot for a year because of having
> gotten a
On 01/26/2011 09:57 AM, Petrus de Calguarium wrote:
> Which disk would I download to get into rescue mode on F14 x86_64?
Either the DVD or the first disk of the CD set will do. You can also do
it from a LiveCD if you prefer; the choice is yours.
--
users mailing list
users@lists.fedoraproject.o
65 matches
Mail list logo
