Re: Monitor Problem
Stephen P. Molnar composed on 2023-07-02 13:58 (UTC-0400):
> Felix Miata wrote:
>> Stephen P. Molnar composed on 2023-07-02 10:57 (UTC-0400):
>>> I should have posted to the debian users group, but unfortunately, I
>>> can't access the last reply you sent. Fortunately, I printed it.
>>> I guess I really did it this time, I found a HDMI to HDMi at the
>>> Microcenter but it doesn't open until 11:00am.
>> Walmart has them, unless the pegs are all out of stock. Same for Best Buy. They're
>> no different for PCs than for TVs.
>>> So I thought I'd go ahead and remove the xserver-org-video-radeon driver
>>> in preparation. When I rebooted the system I got an out of range signal
>>> again. When I booted in to the recovery mode I got a arm_radeon_ vga
>>> detect [radeon] *ERROR* VGA-1 probrd a monitor but no|invalid EDI error
>>> that repeats over and over.
>> At the Grub menu with the default still selected, strike the E key, then navigate
>> to the end of the line that begins linu. Append there nomodeset, then proceed with
>> the boot via F10 or Ctrl-X. First, try normally using the HDMI cable you should
>> have procured by now.
>> Most developers haven't used VGA connections for more than a decade, so they miss
>> regressions they cause. Until users discover and report them, nothing gets done
>> about them. Digital connections both produce higher quality output, and more
>> reliability.
>>> I really hate to bother you with this
> Once again, your expertise and instructions have moved me back to whete
> I was.
> (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 nomodeset
> 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: N/A alternate: radeon bus ID: 01:00.0 chip ID: 1002:68f9 class ID: 0300
> Display: x11 server: X.Org 1.20.11 driver: loaded: vesa unloaded: fbdev,modesetting
> alternate: ati 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: default res: 1024x768
> OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1
> direct render: Yes
That info is incomplete. Bullseye's inxi is ancient and broken. If you edit
/etc/inxi.conf to read as follows:
# cat /etc/inxi.conf
## We want to use the distro to track the package
B_ALLOW_UPDATE=true
GLOBAL_COLOR_SCHEME=0
#
then
sudo inxi -U
will update it to the current version.
> I am at a resolution of 1024x768. Also, after I got in the first tine I
> decided to reboot and see what would happen. I had to do the fix again,
> so, f course, it is not permanent.
Appending nomodeset is primarily intended for troubleshooting graphics issues by
enabling fallback graphics functional for editing configurations and running
package management. As long as you must use nomodeset, you are forced into
1024x768 at best, sometimes worse. It's only coincidental that this mode is used
by both your original problem and using nomodeset, because it's a failsafe fallback.
> So the question is what do I do next? Perhaps, install Debian 12.0.0 on
> my 500 GB SSD.
> What do you think?
Your new HD5450 GPU is in fact older than your "old" Kaveri Radeon R7 GPU. Your
new one is the last of its generation. Your old one was the second of its
generation. The generational change was very significant, quite a change in
technology. Thus, your initrds might not be supporting it, which would cause
fallback to the crude ancient techology VESA fallback display driver if the
support for the older had never been installed. If this is the problem, rebuilding
the initrds should solve it. Before doing that I would try
sudo modprobe radeon
to see if it has an apparent impact. If it solves the problem, running
update-initramfs might be all that is required. It might also be that
libdrm-radeon1 is not installed, which your HD5450 requires for optimal operation,
and so also would need to be installed. If all is well, you should probably see
pretty close to exactly as follows:
# lsmod | egrep 'vid|deo|ati ' | sort
drm 626688 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
video 61440 1 dell_wmi
# dpkg-query -W | egrep 'firmwar|radeon'
firmware-amd-graphics 20210315-3
firmware-linux-free 20200122-1
libdrm-radeon1:amd64 2.4.104-1
#
All that said, I cannot imagine a fresh Bookworm installation having similar
trouble, unless the problem is ultimately your LG and not Debian or your gfxcard.
If you're more comfortable with a fresh installation than wanting to get to the
bottom of the Bullseye issue, go ahead.
If you wish to be able to use your "old" Kaveri Radeon R7 GPU in Bookworm, you'll
need to ensure libdrm-amdgpu1 is installed, which might not happen using the older
HD5450 for installation.
--
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
Reply to: