Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Out of Range Monitor Problim
63 views
Skip to first unread message
Stephen P. Molnar
Jun 29, 2023, 7:00:07 AM6/29/23
to
I have Bullseye currently installed on my main Linux platform.
When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
Although I have been using Linux since the early days of Slackware and
the Red Hat Mother's day release, I'm strictly a user. I googled the
problem and got answers that I don't understand. I can boot into the
rescue mode but can go no further.
Suggestions would be much appreciated.
Thanks in advance.
--
Stephen P. Molnar, PhD
https://insilicochemistry.net
(614)-312-7528
Skype: smolnar1
When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
Although I have been using Linux since the early days of Slackware and
the Red Hat Mother's day release, I'm strictly a user. I googled the
problem and got answers that I don't understand. I can boot into the
rescue mode but can go no further.
Suggestions would be much appreciated.
Thanks in advance.
--
Stephen P. Molnar, PhD
https://insilicochemistry.net
(614)-312-7528
Skype: smolnar1
Gareth Evans
Jun 29, 2023, 10:50:06 AM6/29/23
to
On 29 Jun 2023, at 13:58, Stephen P. Molnar <s.mo...@sbcglobal.net> wrote:
I should have added that I can get into the rescue mode. Unfortunately, I don't what to do at that point, and Google is of no help.
-------- Forwarded Message --------
Subject: Out of Range Monitor Problim Resent-Date: Thu, 29 Jun 2023 10:56:02 +0000 (UTC) Resent-From: debia...@lists.debian.org Date: Thu, 29 Jun 2023 06:55:35 -0400 From: Stephen P. Molnar <s.mo...@sbcglobal.net> To: debia...@lists.debian.org
I have Bullseye currently installed on my main Linux platform.
When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
Although I have been using Linux since the early days of Slackware and the Red Hat Mother's day release, I'm strictly a user. I googled the problem and got answers that I don't understand. I can boot into the rescue mode but can go no further.
It seems strange that you monitor config should "just change" but is this of any use?
Not sure off the top of my head how you persist changes, or whether xrandr is (initially) the correct tool with which to persist changes on your system, but that may give you some clues to check your DE/wm config if nothing else.
Kind regards,
Gareth
Felix Miata
Jun 29, 2023, 11:10:07 AM6/29/23
to
Stephen P. Molnar composed on 2023-06-29 06:55 (UTC-0400):
> I have Bullseye currently installed on my main Linux platform.
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
What was the system stated immediately before trying? IOW, was it suspended, off,
hibernated, asleep?
It's hard to help much when you tell so little about your current system. Was your
cat sleeping on it when you came to use it? Is it a laptop? How many displays are
attached? What GPU(s)? Which DE or WM? Inxi -GSaz is a good way to provide needed
system info, if you can get logged in successfully somehow, maybe by rebooting, or
Ctrl-Alt-F3 then Alt-F7/F1 cycled a time or three, or cycling the display's power.
Is your video cable loose? Ancient? Is your display ancient, or VGA (analog)? Is
your display under warranty? Maybe it's hinting you'd be wise to upgrade to
Bookworm, or shouldn't be tempted. How old is it?
--
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
> I have Bullseye currently installed on my main Linux platform.
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
hibernated, asleep?
It's hard to help much when you tell so little about your current system. Was your
cat sleeping on it when you came to use it? Is it a laptop? How many displays are
attached? What GPU(s)? Which DE or WM? Inxi -GSaz is a good way to provide needed
system info, if you can get logged in successfully somehow, maybe by rebooting, or
Ctrl-Alt-F3 then Alt-F7/F1 cycled a time or three, or cycling the display's power.
Is your video cable loose? Ancient? Is your display ancient, or VGA (analog)? Is
your display under warranty? Maybe it's hinting you'd be wise to upgrade to
Bookworm, or shouldn't be tempted. How old is it?
--
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
gene heskett
Jun 29, 2023, 1:30:06 PM6/29/23
to
On 6/29/23 06:56, Stephen P. Molnar wrote:
> I have Bullseye currently installed on my main Linux platform.
>
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
>
What version are you running now?
> I have Bullseye currently installed on my main Linux platform.
>
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
>
That sounds like something an older monitor could fuss about. Did you
get an indication it had dropped to a lower definition setting? Look at
/var/log/xorg.log.1 or maybe .2 and see what it says. OTOH xorg.log of
any kind is not being generated here. A clue I'm running wayland? Check
and reseat the monitor cables in any event. Otherwise maybe somebody
smarter might know.
> Although I have been using Linux since the early days of Slackware and
> the Red Hat Mother's day release, I'm strictly a user. I googled the
> problem and got answers that I don't understand. I can boot into the
> rescue mode but can go no further.
>
> Suggestions would be much appreciated.
>
> Thanks in advance.
>
--
"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
Genes Web page <http://geneslinuxbox.net:6309/>
Felix Miata
Jun 29, 2023, 2:00:06 PM6/29/23
to
Stephen P. Molnar composed on 2023-06-29 11:50 (UTC-0400):
> Felix Miata wrote:
>> Stephen P. Molnar composed on 2023-06-29 06:55 (UTC-0400):
>>> I have Bullseye currently installed on my main Linux platform.
>>> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz
>>> error.
>> What was the system stated immediately before trying? IOW, was it
>> suspended, off, hibernated, asleep?
>> It's hard to help much when you tell so little about your current
>> system. Was your cat sleeping on it when you came to use it? Is it a
>> laptop? How many displays are attached? What GPU(s)? Which DE or WM?
>> Inxi -GSaz is a good way to provide needed system info, if you can
>> get logged in successfully somehow, maybe by rebooting, or
>> Ctrl-Alt-F3 then Alt-F7/F1 cycled a time or three, or cycling the
>> display's power. Is your video cable loose? Ancient? Is your display
>> ancient, or VGA (analog)? Is your display under warranty? Maybe it's
>> hinting you'd be wise to upgrade to Bookworm, or shouldn't be
>> tempted. How old is it?
So many unanswered questions. :(
> First of all, I don't have a cat, so let's forego any further cattiness.
It really wasn't meant to be humorous. Horizontal configurations with top vents
are attractive to cats napping, leading to hair buildup collecting on components,
overheating, and strange behavior over time.
> I built the system on 6/26/2015 and have kept up on maintenance
> ASUS M5 A97 R2.0 Motherboard BIOS 2603
I see no video outputs on this one:
https://www.newegg.com/asus-m5a97-le-r2-0/p/N82E16813131872
> AMD FX-8320 Eight-Core Processor 3500MHz
No GPU found on that either:
https://www.amd.com/en/products/cpu/fx-8320
> 8179 MB (DDR 1600MHz)
Not likely system RAM has anything to do with an out-of-range display problem.
> The display is a 23 in LG flat screen (3 years old).
My then 3 year old LG from 2017 needed new LED strips, shortly after its warranty
expired. LG was Goldstar before its name change.
> All the cables are firmly attached.
When did that happen last, 3 years ago? eBay stuff, or good stuff, and what type?
USB-C to DP? HDMI to HDMI? DVI to HDMI? Any adapters? These come in many flavors.
Is a KVM switch involved?
Is inxi that hard for you to do? No help from rebooting, rebooting in failsafe
mode, or trying a TV instead of your 23?
# inxi -GSaz
System:
Host: ara88 Kernel: 5.10.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc
v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz root=LABEL=<filter> noresume
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
radeon.cik_support=0 amdgpu.cik_support=1
Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1,
HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f
class-ID: 0300
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l
model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60
dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide
serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD KAVERI (DRM 3.40.0
5.10.0-20-amd64 LLVM 11.0.1) direct-render: Yes
Out of range is a not infrequent occurrence here, with 11 or so displays shared
among 30+ computers. Reasons are many, including software that works the first
time, then barfs until a restart of X, or the whole PC. Asus' BIOS aren't stellar
performers either. Two of my FM2+ Asus motherboards from 2014 died over a year
ago, leaving me with an AMD PRO A8-8650B on the shelf, and an AMD A10-7850K moved
to an Asrock. Some UEFI BIOS don't like to play nice with their connected
displays. I see more out-of-range from them than from the oldies.
It wouldn't hurt for us to see /var/log/Xorg.0.log in addition to inxi output. If
not found, look for ~/.local/share/xorg/Xorg.0.log.
> Felix Miata wrote:
>> Stephen P. Molnar composed on 2023-06-29 06:55 (UTC-0400):
>>> I have Bullseye currently installed on my main Linux platform.
>>> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz
>>> error.
>> What was the system stated immediately before trying? IOW, was it
>> suspended, off, hibernated, asleep?
>> It's hard to help much when you tell so little about your current
>> system. Was your cat sleeping on it when you came to use it? Is it a
>> laptop? How many displays are attached? What GPU(s)? Which DE or WM?
>> Inxi -GSaz is a good way to provide needed system info, if you can
>> get logged in successfully somehow, maybe by rebooting, or
>> Ctrl-Alt-F3 then Alt-F7/F1 cycled a time or three, or cycling the
>> display's power. Is your video cable loose? Ancient? Is your display
>> ancient, or VGA (analog)? Is your display under warranty? Maybe it's
>> hinting you'd be wise to upgrade to Bookworm, or shouldn't be
>> tempted. How old is it?
> First of all, I don't have a cat, so let's forego any further cattiness.
It really wasn't meant to be humorous. Horizontal configurations with top vents
are attractive to cats napping, leading to hair buildup collecting on components,
overheating, and strange behavior over time.
> I built the system on 6/26/2015 and have kept up on maintenance
> ASUS M5 A97 R2.0 Motherboard BIOS 2603
I see no video outputs on this one:
https://www.newegg.com/asus-m5a97-le-r2-0/p/N82E16813131872
> AMD FX-8320 Eight-Core Processor 3500MHz
No GPU found on that either:
https://www.amd.com/en/products/cpu/fx-8320
> 8179 MB (DDR 1600MHz)
Not likely system RAM has anything to do with an out-of-range display problem.
> The display is a 23 in LG flat screen (3 years old).
My then 3 year old LG from 2017 needed new LED strips, shortly after its warranty
expired. LG was Goldstar before its name change.
> All the cables are firmly attached.
When did that happen last, 3 years ago? eBay stuff, or good stuff, and what type?
USB-C to DP? HDMI to HDMI? DVI to HDMI? Any adapters? These come in many flavors.
Is a KVM switch involved?
Is inxi that hard for you to do? No help from rebooting, rebooting in failsafe
mode, or trying a TV instead of your 23?
# inxi -GSaz
System:
Host: ara88 Kernel: 5.10.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc
v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz root=LABEL=<filter> noresume
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
radeon.cik_support=0 amdgpu.cik_support=1
Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1, DVI-D-1,
HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f
class-ID: 0300
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l
model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60
dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
Monitor-4: VGA-1 mapped: VGA-0 pos: middle-r model: Lenovo L2251x Wide
serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD KAVERI (DRM 3.40.0
5.10.0-20-amd64 LLVM 11.0.1) direct-render: Yes
Out of range is a not infrequent occurrence here, with 11 or so displays shared
among 30+ computers. Reasons are many, including software that works the first
time, then barfs until a restart of X, or the whole PC. Asus' BIOS aren't stellar
performers either. Two of my FM2+ Asus motherboards from 2014 died over a year
ago, leaving me with an AMD PRO A8-8650B on the shelf, and an AMD A10-7850K moved
to an Asrock. Some UEFI BIOS don't like to play nice with their connected
displays. I see more out-of-range from them than from the oldies.
It wouldn't hurt for us to see /var/log/Xorg.0.log in addition to inxi output. If
not found, look for ~/.local/share/xorg/Xorg.0.log.
Gareth Evans
Jun 29, 2023, 2:20:06 PM6/29/23
to
On Thu 29 Jun 2023, at 16:50, Stephen P. Molnar <s.mo...@sbcglobal.net> wrote:
> OK, Here we go.
xrandr -q
but this
https://unix.stackexchange.com/questions/651209/how-change-monitors-from-terminal-xrandr-cant-open-display
suggests xrandr expects to run from within a running X session.
If no other displays are available to test the system (or systems available to test the display) do you get the same behaviour from a live cd/usb if you have or can make one?
I was going to ask about logs but Felix has already done so.
Best wishes,
Gareth
> OK, Here we go.
>
> First of all, I don't have a cat, so let's forego any further cattiness.
>
> First of all, I don't have a cat, so let's forego any further cattiness.
>
> I built the system on 6/26/2015 and have kept up on maintenance
>
> ASUS M5 A97 R2.0 Motherboard BIOS 2603
>
>
> ASUS M5 A97 R2.0 Motherboard BIOS 2603
>
> AMD FX-8320 Eight-Core Processor 3500MHz
>
> 8179 MB (DDR 1600MHz)
>
>
> The display is a 23 in LG flat screen (3 years old).
>
> The display is a 23 in LG flat screen (3 years old).
>
> All the cables are firmly attached.
My previous message suggested
xrandr -q
but this
https://unix.stackexchange.com/questions/651209/how-change-monitors-from-terminal-xrandr-cant-open-display
suggests xrandr expects to run from within a running X session.
If no other displays are available to test the system (or systems available to test the display) do you get the same behaviour from a live cd/usb if you have or can make one?
I was going to ask about logs but Felix has already done so.
Best wishes,
Gareth
Cindy Sue Causey
Jun 29, 2023, 2:20:06 PM6/29/23
to
On 6/29/23, Felix Miata <mrm...@earthlink.net> wrote:
> Stephen P. Molnar composed on 2023-06-29 11:50 (UTC-0400):
monitor hardware button being accidentally pushed thus triggering a
different setting to become priority. I started a draft response that
I left hanging earlier. Animal related interference was my own first
suggestion, but my mindset was that the culprit might be an energetic
dog.
The other is: What is the screen showing when rescue mode hits "that
stage"? I just had to go through this yesterday k/t something related
to maybe GRUB EFI. Several rescue mode options were almost
understandable, but I opted to just wing it by entering root's
password, instead. That worked, and I'm still typing in that same
session 24 hours later.
Disclaimer is that my issue was not monitor settings so my success is
an apples to orange [anecdote].
Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
> Stephen P. Molnar composed on 2023-06-29 11:50 (UTC-0400):
>
>> First of all, I don't have a cat, so let's forego any further cattiness.
>
> It really wasn't meant to be humorous. Horizontal configurations with top
> vents
> are attractive to cats napping, leading to hair buildup collecting on
> components,
> overheating, and strange behavior over time.
Not only that, but there is also the possibility of an exterior
>> First of all, I don't have a cat, so let's forego any further cattiness.
>
> It really wasn't meant to be humorous. Horizontal configurations with top
> vents
> are attractive to cats napping, leading to hair buildup collecting on
> components,
> overheating, and strange behavior over time.
monitor hardware button being accidentally pushed thus triggering a
different setting to become priority. I started a draft response that
I left hanging earlier. Animal related interference was my own first
suggestion, but my mindset was that the culprit might be an energetic
dog.
The other is: What is the screen showing when rescue mode hits "that
stage"? I just had to go through this yesterday k/t something related
to maybe GRUB EFI. Several rescue mode options were almost
understandable, but I opted to just wing it by entering root's
password, instead. That worked, and I'm still typing in that same
session 24 hours later.
Disclaimer is that my issue was not monitor settings so my success is
an apples to orange [anecdote].
Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
Charles Curley
Jun 29, 2023, 2:50:05 PM6/29/23
to
On Thu, 29 Jun 2023 19:17:37 +0100
Gareth Evans <dono...@fastmail.fm> wrote:
> If no other displays are available to test the system (or systems
> available to test the display) do you get the same behaviour from a
> live cd/usb if you have or can make one?
If you can run a live CD or USB image, let me suggest a possibility.
Gareth Evans <dono...@fastmail.fm> wrote:
> If no other displays are available to test the system (or systems
> available to test the display) do you get the same behaviour from a
> live cd/usb if you have or can make one?
Boot to the live system, install arandr. Use it to get your display the
way you want it. arandr will then export a short script (in ~/.screen, I
believe; check the docs). You can then call this from your regular
installation's session manager.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Stephen P. Molnar
Jun 29, 2023, 3:30:06 PM6/29/23
to
On 6/29/2023 1:23 PM, gene heskett wrote:
> On 6/29/23 06:56, Stephen P. Molnar wrote:
>> I have Bullseye currently installed on my main Linux platform.
>>
>> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz
>> error.
>>
> What version are you running now?
>
> That sounds like something an older monitor could fuss about. Did you
> get an indication it had dropped to a lower definition setting? Look
> at /var/log/xorg.log.1 or maybe .2 and see what it says. OTOH xorg.log
> of any kind is not being generated here. A clue I'm running wayland?
> Check and reseat the monitor cables in any event. Otherwise maybe
> somebody smarter might know.
>
>> Although I have been using Linux since the early days of Slackware
>> and the Red Hat Mother's day release, I'm strictly a user. I googled
>> the problem and got answers that I don't understand. I can boot into
>> the rescue mode but can go no further.
>>
>> Suggestions would be much appreciated.
>>
>> Thanks in advance.
>>
>
> Cheers, Gene Heskett.
As I quered anther person responding to this thread, would that solve the problem or exacerbate it?
Felix Miata
Jun 29, 2023, 4:20:07 PM6/29/23
to
Stephen P. Molnar composed on 2023-06-29 15:15 (UTC-0400):
> All components were purchased from tho Microcenter herein Columbus.
> It could, in fact, connect to a TV on the LAN in the same room, But now
> I get form the TV: Computer No signal is it on?
Not a good sign. :( Did you turn the TV on, and to the correct input, before
turning on the PC? Some TVs don't like being late to the boot. So do some GPUs.
> inxi -GSaz, in safe mode, returns- bash: inxi: command not found
If network is working, sudo apt install inxi will install it, but because
Bullseye's inxi is a broken antique, better to do the following as root:
cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi
from:
https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
to get the much improved current version. Inxi -Gaz is the best there is for
providing basic graphics troubleshooting info.
> cat for both logs returns: no such file or directory
Bad sign. I never use Wayland, so can't be sure what if any logging it does that
ordinary people can locate. Xorg should have left an old one in either location if
there is no current one. I think Wayland leaves its stuff in the journal:
<https://www.google.com/search?q=debian+journalctl+wayland>
> Let me pose a hypothetical - Would installing Debian 12 on a different
> drive boot. or would I (most likely) muck-up the entire computer?
It's possible to muck up what you have, but if you remove the current drive and
install the different one and Bookworm, it might be your best way forward. If the
installer can't work either, it would be near certain you've acquired a hardware
problem, hopefully easily resolved with a graphics card swap if you can locate one
to try without too much trouble. What to look for might depend on what you have in
there now. NVidia as good at giving people headaches like you have. Intel only
just began (after more than two decades of not) providing discrete graphics cards.
So hopefully you could get hands on a PCIe AMD card made less than 10 years ago to
try.
Simply starting the Bookworm installer, if it starts at all, might say a lot.
> All components were purchased from tho Microcenter herein Columbus.
> It could, in fact, connect to a TV on the LAN in the same room, But now
> I get form the TV: Computer No signal is it on?
Not a good sign. :( Did you turn the TV on, and to the correct input, before
turning on the PC? Some TVs don't like being late to the boot. So do some GPUs.
> inxi -GSaz, in safe mode, returns- bash: inxi: command not found
If network is working, sudo apt install inxi will install it, but because
Bullseye's inxi is a broken antique, better to do the following as root:
cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi
from:
https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
to get the much improved current version. Inxi -Gaz is the best there is for
providing basic graphics troubleshooting info.
> cat for both logs returns: no such file or directory
Bad sign. I never use Wayland, so can't be sure what if any logging it does that
ordinary people can locate. Xorg should have left an old one in either location if
there is no current one. I think Wayland leaves its stuff in the journal:
<https://www.google.com/search?q=debian+journalctl+wayland>
> Let me pose a hypothetical - Would installing Debian 12 on a different
> drive boot. or would I (most likely) muck-up the entire computer?
It's possible to muck up what you have, but if you remove the current drive and
install the different one and Bookworm, it might be your best way forward. If the
installer can't work either, it would be near certain you've acquired a hardware
problem, hopefully easily resolved with a graphics card swap if you can locate one
to try without too much trouble. What to look for might depend on what you have in
there now. NVidia as good at giving people headaches like you have. Intel only
just began (after more than two decades of not) providing discrete graphics cards.
So hopefully you could get hands on a PCIe AMD card made less than 10 years ago to
try.
Simply starting the Bookworm installer, if it starts at all, might say a lot.
Gareth Evans
Jun 29, 2023, 5:10:06 PM6/29/23
to
> On 29 Jun 2023, at 20:21, Stephen P. Molnar <s.mo...@sbcglobal.net> wrote:
>
> I'm running Debian 11, but I was going to install Debian 12 on another drive in the computer.
> As I quered anther person responding to this thread, would that solve the problem or exacerbate it?
Stephen said this happened "when [he] logged in."
>
> I'm running Debian 11, but I was going to install Debian 12 on another drive in the computer.
> As I quered anther person responding to this thread, would that solve the problem or exacerbate it?
Stephen, assuming you actually logged in before the issue occurred, did you log in to a login/display manager such as LightDM or did you log in to a console/CLI prompt and subsequently run startx, whereupon the issue occurred? If the former, either X or Wayland is running at the point of "login screen", isn't it? At some "standard" (high-ish, working) resolution?
"[...] systemd [...] starts all the important system processes
and then starts X11 [...]
which in turn starts a login manager [eg.] LightDM [...]
The login manager starts a session manager [...]
which starts a window manager and usually a menu bar, a desktop [...]"
https://dev.to/jfhbrook/what-s-a-desktop-session-manager-and-why-do-i-want-one-agl
Doesn't this suggest a display configuration problem rather than a hardware issue?
Thanks
Gareth
Gareth Evans
Jun 29, 2023, 5:40:07 PM6/29/23
to
On Thu 29 Jun 2023, at 22:00, Gareth Evans <dono...@fastmail.fm> wrote:
[...]
> If [using a DM], either X or Wayland is running at the
"LightDM is a lightweight, cross-desktop display manager. A display manager is a daemon that:
Runs display servers (e.g. X) where necessary.
Runs greeters to allow users to pick which user account and session type to use.
Allows greeters to perform authentication using PAM.
Runs session processes once authentication is complete ..."
but I don't think my point re indication of config issues is affected, is it?
Thanks
G
[...]
> If [using a DM], either X or Wayland is running at the
> point of "login screen", isn't it? At some "standard" (high-ish,
> working) resolution?
>
> "[...] systemd [...] starts all the important system processes
> and then starts X11 [...]
> which in turn starts a login manager [eg.] LightDM [...]
> The login manager starts a session manager [...]
> which starts a window manager and usually a menu bar, a desktop [...]"
>
> https://dev.to/jfhbrook/what-s-a-desktop-session-manager-and-why-do-i-want-one-agl
LightDM (for example) combines some of this "under one roof/umbrella/[process?]":
> working) resolution?
>
> "[...] systemd [...] starts all the important system processes
> and then starts X11 [...]
> which in turn starts a login manager [eg.] LightDM [...]
> The login manager starts a session manager [...]
> which starts a window manager and usually a menu bar, a desktop [...]"
>
> https://dev.to/jfhbrook/what-s-a-desktop-session-manager-and-why-do-i-want-one-agl
"LightDM is a lightweight, cross-desktop display manager. A display manager is a daemon that:
Runs display servers (e.g. X) where necessary.
Runs greeters to allow users to pick which user account and session type to use.
Allows greeters to perform authentication using PAM.
Runs session processes once authentication is complete ..."
but I don't think my point re indication of config issues is affected, is it?
Thanks
G
David Christensen
Jun 29, 2023, 6:20:06 PM6/29/23
to
On 6/29/23 03:55, Stephen P. Molnar wrote:
> I have Bullseye currently installed on my main Linux platform.
>
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
>
> Although I have been using Linux since the early days of Slackware and
> the Red Hat Mother's day release, I'm strictly a user. I googled the
> problem and got answers that I don't understand. I can boot into the
> rescue mode but can go no further.
>
> Suggestions would be much appreciated.
>
> Thanks in advance.
Do you have a second machine that can log into the subject machine via
> I have Bullseye currently installed on my main Linux platform.
>
> When I logged in this morning I got an Out of Range 95.3 kHz/60 kHz error.
>
> Although I have been using Linux since the early days of Slackware and
> the Red Hat Mother's day release, I'm strictly a user. I googled the
> problem and got answers that I don't understand. I can boot into the
> rescue mode but can go no further.
>
> Suggestions would be much appreciated.
>
> Thanks in advance.
ssh(1)?
David
Felix Miata
Jun 30, 2023, 12:10:06 AM6/30/23
to
Gareth Evans composed on 2023-06-29 22:00 (UTC+0100):
>> Stephen P. Molnar wrote:
...
booting again next day. So, the state of the PC "when logged in" matters. Was it a
fresh boot? A resume from hibernation? Resume from sleep?
Given he got 'into rescue mode', it probably means nomodeset and/or other failsafe
X parameters that could preclude compositing that his DE depends on. It's pretty
important he report what his GPU is. If it's an NVidia, we need to know whether
he's using NVidia's proprietary drivers. It could be that before his last
successful session exit some automatic updates were applied to break a proprietary
driver installation. In that case, booting a prior kernel could be a workaround or
solution.
Indeed, if his words were meant literally, he may have been at a GUI login screen,
but he could have meant login at a shell prompt. From a shell prompt startx or
equivalent causing the black screen means any part of DM or DE or WM or personal
settings could be at fault. If at a GUI screen, he should be able to select some
other session type than his normal one to log into. Other type can mean both
switching between Wayland and Xorg, and/or among other installed DEs or WMs. This
could result in a successful session that might point to a problem with his
personal settings, or the DE or WM session type he normally uses. We need to see
more details about his normal login process, what actually transpired, and what
his normal DE or WM is.
There are multitudes of ways to get a black screen. The more info, the better and
faster a solution might be found.
>> Stephen P. Molnar wrote:
...
> Stephen said this happened "when [he] logged in."
> Stephen, assuming you actually logged in before the issue occurred, did you log in to a login/display manager such as LightDM or did you log in to a console/CLI prompt and subsequently run startx, whereupon the issue occurred? If the former, either X or Wayland is running at the point of "login screen", isn't it? At some "standard" (high-ish, working) resolution?
> Stephen, assuming you actually logged in before the issue occurred, did you log in to a login/display manager such as LightDM or did you log in to a console/CLI prompt and subsequently run startx, whereupon the issue occurred? If the former, either X or Wayland is running at the point of "login screen", isn't it? At some "standard" (high-ish, working) resolution?
> Doesn't this suggest a display configuration problem rather than a hardware issue?
A display configuration problem should not result from shutting down one day and
booting again next day. So, the state of the PC "when logged in" matters. Was it a
fresh boot? A resume from hibernation? Resume from sleep?
Given he got 'into rescue mode', it probably means nomodeset and/or other failsafe
X parameters that could preclude compositing that his DE depends on. It's pretty
important he report what his GPU is. If it's an NVidia, we need to know whether
he's using NVidia's proprietary drivers. It could be that before his last
successful session exit some automatic updates were applied to break a proprietary
driver installation. In that case, booting a prior kernel could be a workaround or
solution.
Indeed, if his words were meant literally, he may have been at a GUI login screen,
but he could have meant login at a shell prompt. From a shell prompt startx or
equivalent causing the black screen means any part of DM or DE or WM or personal
settings could be at fault. If at a GUI screen, he should be able to select some
other session type than his normal one to log into. Other type can mean both
switching between Wayland and Xorg, and/or among other installed DEs or WMs. This
could result in a successful session that might point to a problem with his
personal settings, or the DE or WM session type he normally uses. We need to see
more details about his normal login process, what actually transpired, and what
his normal DE or WM is.
There are multitudes of ways to get a black screen. The more info, the better and
faster a solution might be found.
David Christensen
Jul 1, 2023, 5:00:07 PM7/1/23
to
On 7/1/23 10:44, Stephen P. Molnar wrote:
> OK. Now I boot into as user, but the resolution leaves something to be
> desired, 1024x760.
>
> The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.
>
> The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of
> 1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before
> the mishap)
>
> I installed inxi and get the following results:
>
> (base) comp@AbNormal:~$ inxi -GSaz
> System: Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
> parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
> root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
> Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm:
> xfwm4 dm: LightDM 1.26.0
> vendor: VISIONTEK
> driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9
> class ID: 0300
> Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
> unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
> Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm
> (10.7x8.0")
> s-diag: 339mm (13.3")
> Monitor-1: VGA-0 res: 1024x768 hz: 60
> OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64
> LLVM 11.0.1)
> v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
>
> While I am quite comfortable, doing molecular orbital computations, I
> would be very uncomfortable trying to proceed further.
>
> Guidance would be very much appreciated.
>
> Thanks in advance.
> OK. Now I boot into as user, but the resolution leaves something to be
> desired, 1024x760.
>
> The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.
>
> The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of
> 1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before
> the mishap)
>
> I installed inxi and get the following results:
>
> (base) comp@AbNormal:~$ inxi -GSaz
> System: Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
> parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
> root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
> Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm:
> xfwm4 dm: LightDM 1.26.0
> Distro: Debian GNU/Linux 11 (bullseye)
> Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: VISIONTEK
> driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9
> class ID: 0300
> Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
> unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
> Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm
> (10.7x8.0")
> s-diag: 339mm (13.3")
> Monitor-1: VGA-0 res: 1024x768 hz: 60
> OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64
> LLVM 11.0.1)
> v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
>
> While I am quite comfortable, doing molecular orbital computations, I
> would be very uncomfortable trying to proceed further.
>
> Guidance would be very much appreciated.
>
> Thanks in advance.
Felix Miata
Jul 1, 2023, 10:10:06 PM7/1/23
to
Stephen P. Molnar composed on 2023-07-01 13:44 (UTC-0400):
> OK. Now I boot into as user, but the resolution leaves something to be
> desired, 1024x760.
> The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.
> The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of
> 1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before
> the mishap)
> I installed inxi and get the following results:
> (base) comp@AbNormal:~$ inxi -GSaz
> System: Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
> parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
> root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
> Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm:
> xfwm4 dm: LightDM 1.26.0
HDMI-to-HDMI cable and connect that HD5450 to your LG instead of the VGA
cable. If that isn't any better, connect it to a TV's HDMI input to see what
results. I suspect your VGA connection is the root problem, either the cable,
or the VGA connector on your LG. All is good here with Bullseye and HD5450
using VGA connection, HDMI connection, and/or DVI connection:
# inxi -GSaz
System:
Kernel: 5.10.0-23-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: ro root=/dev/sda12 noresume net.ifnames=0 ipv6.disable=1
consoleblank=0 preempt=full mitigations=off
Desktop: Trinity v: R14.1.0 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
driver: radeon v: kernel arch: TeraScale-2 code: Evergreen
process: TSMC 32-40nm built: 2009-15 pcie: gen: 2 speed: 5 GT/s lanes: 16
ports: active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 01:00.0
chip-ID: 1002:68f9 class-ID: 0300 temp: 60.0 C
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: r600 gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
Monitor-1: DVI-I-1 pos: right model: Dell P2213 serial: <filter>
5.10.0-23-amd64 LLVM 11.0.1) compat-v: 3.1 direct-render: Yes
# hwinfo --monitor
23: None 00.0: 10000 Monitor
[Created at monitor.125]
Unique ID: rdCR.VxQp9HL+fzB
Parent ID: VCu0.SWTcMEVMYM4
Hardware Class: monitor
Model: "NEC EA243WM"
Vendor: NEC "NEC"
Device: eisa 0x6863 "EA243WM"
Serial ID: "1Z101367NA"
Resolution: 640x480@60Hz
Resolution: 800x600@56Hz
Resolution: 800x600@60Hz
Resolution: 1024x768@60Hz
Resolution: 1280x960@60Hz
Resolution: 1280x1024@60Hz
Resolution: 1280x720@60Hz
Resolution: 1920x1200@60Hz
Size: 519x324 mm
Year of Manufacture: 2011
Week of Manufacture: 48
Detailed Timings #0:
Resolution: 1920x1200
Horizontal: 1920 1968 2000 2080 (+48 +80 +160) -hsync
Vertical: 1200 1203 1209 1235 (+3 +9 +35) +vsync
Frequencies: 154.00 MHz, 74.04 kHz, 59.95 Hz
Driver Info #0:
Max. Resolution: 1920x1200
Vert. Sync Range: 56-61 Hz
Hor. Sync Range: 31-77 kHz
Bandwidth: 154 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #10 (VGA compatible controller)
...
# hwinfo --gfxcard
16: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: VCu0.SWTcMEVMYM4
Parent ID: vSkL.l4tEjTIzexA
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "ATI Cedar [Radeon HD 5000/6000/7350/8350 Series]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x68f9 "Cedar [Radeon HD 5000/6000/7350/8350 Series]"
SubVendor: pci 0x1682 "XFX Pine Group Inc."
SubDevice: pci 0x304a
Driver: "radeon"
Driver Modules: "radeon"
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
Memory Range: 0xfbde0000-0xfbdfffff (rw,non-prefetchable)
I/O Ports: 0xd000-0xdfff (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 30 (106 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00001002d000068F9sv00001682sd0000304Abc03sc00i00"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #13 (PCI bridge)
Primary display adapter: #16
# dpkg-query -W | egrep 'amdgpu|radeon|mwar|xorg|x11|mesa|video' | sort
firmware-amd-graphics 20210315-3
firmware-linux-free 20200122-1
firmware-sof-signed 1.7-1
libdrm-amdgpu1:amd64 2.4.104-1
libdrm-radeon1:amd64 2.4.104-1
libegl-mesa0:amd64 20.3.5-1
libgl1-mesa-dri:amd64 20.3.5-1
libgl1-mesa-glx:amd64 20.3.5-1
libglapi-mesa:amd64 20.3.5-1
libglu1-mesa:amd64 9.0.1-1
libglx-mesa0:amd64 20.3.5-1
libva-x11-2:amd64 2.10.0-1
libx11-6:amd64 2:1.7.2-1+deb11u1
libx11-data 2:1.7.2-1+deb11u1
libx11-xcb1:amd64 2:1.7.2-1+deb11u1
mesa-utils 8.4.0-1+b1
x11-apps 7.7+8
x11-common 1:7.7+22
x11-session-utils 7.7+4
x11-utils 7.7+5
x11-xfs-utils 7.7+2+b1
x11-xkb-utils 7.7+5
x11-xserver-utils 7.7+8
xserver-xorg-core 2:1.20.11-1+deb11u6
xserver-xorg-input-evdev 1:2.10.6-2
xserver-xorg-legacy 2:1.20.11-1+deb11u6
# lsmod | egrep 'vid|amd|drm|radeon' | sort
cec 61440 1 drm_kms_helper
drm 630784 5 drm_kms_helper,radeon,ttm
drm_kms_helper 278528 1 radeon
i2c_algo_bit 16384 1 radeon
radeon 1675264 2
ttm 114688 1 radeon
#
You might notice that my HD5450 has loaded the modesetting Xorg display driver,
while yours has loaded ati,radeon. You may uninstall xserver-xorg-video-radeon
to allow yours to do the same.
> OK. Now I boot into as user, but the resolution leaves something to be
> desired, 1024x760.
> The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.
> The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of
> 1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before
> the mishap)
> I installed inxi and get the following results:
> (base) comp@AbNormal:~$ inxi -GSaz
> System: Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
> parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
> root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
> Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm:
> xfwm4 dm: LightDM 1.26.0
> Distro: Debian GNU/Linux 11 (bullseye)
> Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: VISIONTEK
> driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9
> class ID: 0300
> Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
> unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
> Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm
> (10.7x8.0")
> s-diag: 339mm (13.3")
> Monitor-1: VGA-0 res: 1024x768 hz: 60
> OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64
> LLVM 11.0.1)
> v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
> While I am quite comfortable, doing molecular orbital computations, I
> would be very uncomfortable trying to proceed further.
Now that you have a GPU with outputs other than VGA, find a DVI-to-HDMI or
> vendor: VISIONTEK
> driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9
> class ID: 0300
> Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
> unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
> Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm
> (10.7x8.0")
> s-diag: 339mm (13.3")
> Monitor-1: VGA-0 res: 1024x768 hz: 60
> OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64
> LLVM 11.0.1)
> v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
> While I am quite comfortable, doing molecular orbital computations, I
> would be very uncomfortable trying to proceed further.
HDMI-to-HDMI cable and connect that HD5450 to your LG instead of the VGA
cable. If that isn't any better, connect it to a TV's HDMI input to see what
results. I suspect your VGA connection is the root problem, either the cable,
or the VGA connector on your LG. All is good here with Bullseye and HD5450
using VGA connection, HDMI connection, and/or DVI connection:
# inxi -GSaz
System:
Kernel: 5.10.0-23-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: ro root=/dev/sda12 noresume net.ifnames=0 ipv6.disable=1
consoleblank=0 preempt=full mitigations=off
Desktop: Trinity v: R14.1.0 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
Graphics:
driver: radeon v: kernel arch: TeraScale-2 code: Evergreen
process: TSMC 32-40nm built: 2009-15 pcie: gen: 2 speed: 5 GT/s lanes: 16
ports: active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 01:00.0
chip-ID: 1002:68f9 class-ID: 0300 temp: 60.0 C
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: r600 gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
Monitor-1: DVI-I-1 pos: right model: Dell P2213 serial: <filter>
built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
Monitor-2: VGA-1 pos: primary,left model: NEC EA243WM serial: <filter>
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
API: OpenGL v: 3.3 Mesa 20.3.5 renderer: AMD CEDAR (DRM 2.50.0 /
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
5.10.0-23-amd64 LLVM 11.0.1) compat-v: 3.1 direct-render: Yes
# hwinfo --monitor
23: None 00.0: 10000 Monitor
[Created at monitor.125]
Unique ID: rdCR.VxQp9HL+fzB
Parent ID: VCu0.SWTcMEVMYM4
Hardware Class: monitor
Model: "NEC EA243WM"
Vendor: NEC "NEC"
Device: eisa 0x6863 "EA243WM"
Serial ID: "1Z101367NA"
Resolution: 640x480@60Hz
Resolution: 800x600@56Hz
Resolution: 800x600@60Hz
Resolution: 1024x768@60Hz
Resolution: 1280x960@60Hz
Resolution: 1280x1024@60Hz
Resolution: 1280x720@60Hz
Resolution: 1920x1200@60Hz
Size: 519x324 mm
Year of Manufacture: 2011
Week of Manufacture: 48
Detailed Timings #0:
Resolution: 1920x1200
Horizontal: 1920 1968 2000 2080 (+48 +80 +160) -hsync
Vertical: 1200 1203 1209 1235 (+3 +9 +35) +vsync
Frequencies: 154.00 MHz, 74.04 kHz, 59.95 Hz
Driver Info #0:
Max. Resolution: 1920x1200
Vert. Sync Range: 56-61 Hz
Hor. Sync Range: 31-77 kHz
Bandwidth: 154 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #10 (VGA compatible controller)
...
# hwinfo --gfxcard
16: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: VCu0.SWTcMEVMYM4
Parent ID: vSkL.l4tEjTIzexA
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "ATI Cedar [Radeon HD 5000/6000/7350/8350 Series]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x68f9 "Cedar [Radeon HD 5000/6000/7350/8350 Series]"
SubVendor: pci 0x1682 "XFX Pine Group Inc."
SubDevice: pci 0x304a
Driver: "radeon"
Driver Modules: "radeon"
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
Memory Range: 0xfbde0000-0xfbdfffff (rw,non-prefetchable)
I/O Ports: 0xd000-0xdfff (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 30 (106 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00001002d000068F9sv00001682sd0000304Abc03sc00i00"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #13 (PCI bridge)
Primary display adapter: #16
# dpkg-query -W | egrep 'amdgpu|radeon|mwar|xorg|x11|mesa|video' | sort
firmware-amd-graphics 20210315-3
firmware-linux-free 20200122-1
firmware-sof-signed 1.7-1
libdrm-amdgpu1:amd64 2.4.104-1
libdrm-radeon1:amd64 2.4.104-1
libegl-mesa0:amd64 20.3.5-1
libgl1-mesa-dri:amd64 20.3.5-1
libgl1-mesa-glx:amd64 20.3.5-1
libglapi-mesa:amd64 20.3.5-1
libglu1-mesa:amd64 9.0.1-1
libglx-mesa0:amd64 20.3.5-1
libva-x11-2:amd64 2.10.0-1
libx11-6:amd64 2:1.7.2-1+deb11u1
libx11-data 2:1.7.2-1+deb11u1
libx11-xcb1:amd64 2:1.7.2-1+deb11u1
mesa-utils 8.4.0-1+b1
x11-apps 7.7+8
x11-common 1:7.7+22
x11-session-utils 7.7+4
x11-utils 7.7+5
x11-xfs-utils 7.7+2+b1
x11-xkb-utils 7.7+5
x11-xserver-utils 7.7+8
xserver-xorg-core 2:1.20.11-1+deb11u6
xserver-xorg-input-evdev 1:2.10.6-2
xserver-xorg-legacy 2:1.20.11-1+deb11u6
# lsmod | egrep 'vid|amd|drm|radeon' | sort
cec 61440 1 drm_kms_helper
drm 630784 5 drm_kms_helper,radeon,ttm
drm_kms_helper 278528 1 radeon
i2c_algo_bit 16384 1 radeon
radeon 1675264 2
ttm 114688 1 radeon
#
You might notice that my HD5450 has loaded the modesetting Xorg display driver,
while yours has loaded ati,radeon. You may uninstall xserver-xorg-video-radeon
to allow yours to do the same.
0 new messages