4 Dec
2024
4 Dec
'24
3:08 p.m.
Hello mailing list,
This is not TDE related, but maybe someone can help.
My main machine has stopped working. It boots to a dark screen when loading
the system.
- I can go to the BIOS
- I see the GRUB menu
- I see the initial (text) messages, but then the screen turns black
- This happens for three OS installed on different disks (MX-21, MX-23, Debian
Buster), so it's not a disk problem.
- I can boot "Image for Linux" (from USB) and access the partitions (graphical
screen, but at low resolution).
The computer uses an integrated video card (AMD Ryzen 2400E)
I'm trying to find out if this is a motherboard problem or a processor
problem. For the moment I am thinking the problem is related to higher
resolution, but I can't figure out what causes it.
The important data has been migrated to another machine so no worry there, but
I simply want to understand.
What log am I to look for (all three systems are Debian based)?
I'm thankful for any suggestion :)
Thierry
4 Dec
4 Dec
3:23 p.m.
Anno domini 2024 Wed, 4 Dec 16:08:29 +0100
Thierry de Coulon via tde-users scripsit:
Hello mailing list,
This is not TDE related, but maybe someone can help.
My main machine has stopped working. It boots to a dark screen when loading
the system.
- I can go to the BIOS
- I see the GRUB menu
- I see the initial (text) messages, but then the screen turns black
- This happens for three OS installed on different disks (MX-21, MX-23, Debian
Buster), so it's not a disk problem.
- I can boot "Image for Linux" (from USB) and access the partitions (graphical
screen, but at low resolution).
The computer uses an integrated video card (AMD Ryzen 2400E)
I'm trying to find out if this is a motherboard problem or a processor
problem. For the moment I am thinking the problem is related to higher
resolution, but I can't figure out what causes it.
The important data has been migrated to another machine so no worry there, but
I simply want to understand.
What log am I to look for (all three systems are Debian based)?
I'm thankful for any suggestion :)
Sounds like a broken graphic card. VESA modes work, but accelerated drivers expose the
problem. If it's onboard graphics card: run memtest, maxbe a ram chip is bad.
Nik
Thierry
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
5:20 p.m.
On Wednesday 04 December 2024 16:23:36 Dr. Nikolaus Klepp via tde-users wrote:
Sounds like a broken graphic card. VESA modes work,
but accelerated drivers
expose the problem.
Yes, that's what I was thinking too
If it's onboard graphics card: run memtest, maxbe
a ram
chip is bad.
Memtest stops at 27% checking the L1 cache (both smtp and failsafe mode.
So that means processor failure, right?
Thierry
5:56 p.m.
On 12/4/24 9:20 AM, Thierry de Coulon via tde-users wrote:
Memtest stops at 27% checking the L1 cache (both smtp
and failsafe mode.
So that means processor failure, right?
Processor or motherboard. In my experience, motherboard is far more likely.
--
For PGP key, search on the PGP Global Directory.
9:21 p.m.
On 12/4/24 12:58, Dan Youngquist via tde-users wrote:
On 12/4/24 9:20 AM, Thierry de Coulon via tde-users
wrote:
I'd vote for MB too, memtest will report failed memory, but keep on going.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Memtest stops at 27% checking the L1 cache (both
smtp and failsafe mode.
So that means processor failure, right?
Processor or motherboard. In my experience, motherboard is far more likely.
9:30 p.m.
Anno domini 2024 Wed, 4 Dec 16:21:42 -0500
gene heskett via tde-users scripsit:
On 12/4/24 12:58, Dan Youngquist via tde-users wrote:
IIIRC L1 cache is on the CPU and not connected over MB to RAM.
Nik
On 12/4/24 9:20 AM, Thierry de Coulon via
tde-users wrote:
I'd vote for MB too, memtest will report failed memory, but keep on going.
Memtest stops at 27% checking the L1 cache (both
smtp and failsafe mode.
So that means processor failure, right?
Processor or motherboard. In my experience, motherboard is far more likely.
Cheers, Gene Heskett, CET.
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9:50 p.m.
On 12/4/24 11:56 AM, Dan Youngquist via tde-users wrote:
Processor or motherboard. In my experience,
motherboard is far more likely.
Agreed, and capacitor on the motherboard may be the likely culprit. In the old
days you could just look at the caps and find the one (or two) that look like
a Dr. Pepper can that was left in the freezer too long an is "puffy". If there
are only one or two and they are in a reasonably accessible locations, then
replacement is an option.
When hardware starts getting flaky, unless you are prepared for an extended
deep-dive in electronics repair, it's probably time to just put it in the
bone-pile and replace it with something that works. Your time is likely more
valuable than the cost of replacement compared against the amount of time you
will spend trying to sort out what happened.
If memtest fails and a quick RAM swap doesn't fix the issue -- I think you
have your answer.
--
David C. Rankin, J.D.,P.E.
3:40 p.m.
Thierry de Coulon composed on 2024-12-04 16:08 (UTC+0100):
This is not TDE related, but maybe someone can help.
My main machine has stopped working. It boots to a
dark screen when loading
the system.
- I can go to the BIOS
- I see the GRUB menu
- I see the initial (text) messages, but then the screen turns black
- This happens for three OS installed on different disks (MX-21, MX-23, Debian
Buster), so it's not a disk problem.
- I can boot "Image for Linux" (from USB) and access the partitions (graphical
screen, but at low resolution).
The computer uses an integrated video card (AMD Ryzen
2400E)
I'm trying to find out if this is a motherboard
problem or a processor
problem. For the moment I am thinking the problem is related to higher
resolution, but I can't figure out what causes it.
The important data has been migrated to another
machine so no worry there, but
I simply want to understand.
What log am I to look for (all three systems are
Debian based)?
Did you upgrade all three, or your BIOS, yesterday?
Does the same Grub start all three OSes, or do you select using BBS hotkey, or are
you using one's Grub to chainload other two?
Low resolution is a common result of kernel GPU module failing to load or broken,
or employing nomodeset or amdgpu.modeset=0 in your boot stanzas' linu line(s).
'lsmod | grep amd' should result in a fair number of lines in result, somewhere
in
the 7-15 range more or less.
Broken Plymouth (if installed and not disabled) can cause black screen booting,
and may trigger failure of login greeter to appear. E key strike at Grub menu puts
it in edit mode. There you can modify linu line, editing, adding or removing
parameters. One of plymouth=0, noplymouth or plymouth.enable=0 should disable
plymouth if plymouth is the problem, as would purging plymouth if the OS allows it.
After black screen long enough to be sure boot should be completed, can you reach
a login prompt via Ctrl-Alt-F[3,4,5]? Can you login remotely to it from another
computer?
Xorg.0.log from /var/log/ or ~/.local/share/xorg/ if it exists may point out
problem(s). Sometimes another number instead of 0 will exist instead or in addition.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
5:28 p.m.
On Wednesday 04 December 2024 16:40:35 Felix Miata via tde-users wrote:
Did you upgrade all three, or your BIOS, yesterday?
no
Does the same Grub start all three OSes, or do you
select using BBS hotkey,
or are you using one's Grub to chainload other two?
Same Grub
Low resolution is a common result of kernel GPU module
failing to load
Boot succeeds with nomodeset
plymouth=0, noplymouth or
plymouth.enable=0 should disable plymouth if plymouth is the problem,
None help. As
far as I know the Buster boot does not use plymouth. MX does.
After black screen long enough to be sure boot should
be completed, can you
reach a login prompt via Ctrl-Alt-F[3,4,5]?
Nope. Can't reach the login, seems
the system does not load
Can you login remotely to it from another computer?
no
As I said in my answer to Nick, memtest stops at 27% when testint the L1
cache. I guess that means byebye processor...
Thierry
10:20 p.m.
Thierry de Coulon composed on 2024-12-04 18:28 (UTC+0100):
As I said in my answer to Nick, memtest stops at 27%
when testint the L1
cache. I guess that means byebye processor...
Overheat somewhere is another possibility: power supply component, motherboard
component, CPU or GPU.
I fixed a 3 month's of no-POST motherboard yesterday by changing one of its two
25.000MHz crystals, transplanted from another dead motherboard with identical CPU
socket and support. The old somehow, unknown when, acquired a small case dent, so
I took a gamble, and it worked.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
18
days inactive
18
days old
9 comments
6 participants
participants (6)
-
Dan Youngquist -
David C. Rankin -
Dr. Nikolaus Klepp -
Felix Miata -
gene heskett -
Thierry de Coulon