updated rpi4 lost hdmi output

glorsplitz · 06-10-2022, 08:42 PM

5.17.14-armv8 #1 SMP PREEMPT Thu Jun 9 10:20:18 BST 2022 aarch64 GNU/Linux

applied last updates, rebooted, watched it booting, turned away, came back, no output, system is up and running, I can ssh.

another reboot, watched it this time, after certain point in boot process, output to monitor just stops, goes blank

pchristy · 06-11-2022, 03:21 AM

Sounds like the same problem I'm having on a Pi 400. I keep hoping updates will fix the X freezing problem, but it seemed to be getting worse - now it is regularly freezing even from the command line! Tried a completely fresh install after the latest updates, and like yours, mine freezes during the boot process. Never even gets to the login before the screen goes blank!

I can ssh into it, but it doesn't respond to shutdown commands. I have to pull the power to shut it down!

Its not a hardware issue, as other OSs run perfectly on it.

--
Pete

drmozes · 06-11-2022, 03:16 PM

The HDMI works fine here.
We'll have Linux 5.18 out next week. I don't know if there are any RPi improvements in it, but we'll find out! :-)
You're welcome to suggest fixes, and I'm thinking about being more open to inclusion of patches (I can expand on that if you're interested). Using the RPi Kernel fork is off the table though. Slackware uses the kernel.org mainline Kernel with patches where required.

jimtabor · 06-11-2022, 05:53 PM

Hi!

Check your power supply,,, remove the fan if it is powered by the board.

Make sure your hdmi is plugged in all the way till there is a click. Otherwise it will fall out or become intermittent.

With slackwareaarch64-current, X still freezes on my RasPi 4/8G while testing.

,
James

glorsplitz · 06-11-2022, 08:18 PM

thank you all for comments

mine doesn't freeze, system appears to be fine ssh'd

is there anything log wise that might indicate any display issue, you know how there's Xorg.0.log for x, might there be something messages, syslog, or dmesg? I'll have a look

jimtabor, everything was running fine from install, through all updates except last one, can't imagine power supply issue happening just like that, I also had slackwarearm installed prior to it becoming aarch64 flavor

glorsplitz · 06-11-2022, 09:47 PM

from dmesg "CONNECTOR:32:HDMI-A-1" found this post which seems related, tail of dmesg attached

netcrawl · 06-11-2022, 11:11 PM

.

Edit: Ran a slackpkg update and now have kernel 5.18.3 and related packages installed on an Rpi4, all good so far.

pchristy · 06-12-2022, 04:46 AM

Unfortunately, since I did a complete re-install and can no longer even login, I can't provide any further help here! Since all my network settings got lost during the re-install, I can't even ssh in any more!

However, a brief summary of my experiences may help - at least, I hope so!

I have a Pi400 and a Pi4B. However, the 4B is running as a headless NAS and media server (OpenMediaVault on top of a minimal Debian install), and as it is running perfectly, I have no wish to disturb it! (If it ain't broke, don't fix it!).

The 400 has been flakey under slackwareaarch64 from day 1, primarily very poor graphics performance. However, initially it seemed to be stable. With each successive upgrade, the stability has got worse, with anything running X locking the machine up at irregular intervals - usually within 5 to 10 mins of booting, sometimes sooner, occasionally later.

After the penultimate updates, it became impossible to start X at all, either from run level 4 in inittab, or from the command line. Around this time, it also started freezing from the command line!

Whilst applying the most recent updates, it seemed to freeze whilst running slackpkg upgrade! (By freezing, I mean the screen freezes, and the keyboard is unresponsive.)

Ssh indicated something was still running, so I left it a few hours before rebooting. On rebooting, all HDMI output disappeared part way through the boot, and the keyboard was unresponsive. I could still ssh in, but it appeared to only respond to a very limited set of commands. (Top worked, but not much else.) I could not shut it down, and resorted to pulling the plug - something I don't like doing!

Thinking the update had failed, I did a complete re-install, only to immediately hit the same problem. Because of the re-install, I can't even ssh in any more as I usually set my network up in NetworkManager, and it never even gets to the point of allowing me to login!

Whilst I was digging through the X issues, I discovered that in contrast to other operating systems for the Pi, slackwareaarch64 appears to be using software rendering, rather than hardware!

For example, other Pi OSs (including Slackware based ones) give this:

Code:

glxinfo | grep renderer
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_control, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: V3D 4.2

Note the OpenGL renderer string.

In contrast, slackwareaarch64 gives:

Code:

glxinfo | grep renderer
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_OML_swap_method, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: llvmpipe (LLVM 13.0.1, 128 bits)

Again, note the OpenGL renderer string!

llvmpipe is a software renderer. Now I'm no expert in these things, but that seems to tell me that the CPU is doing the rendering, not the GPU. This probably explains the poor graphics performance!

Stuart: I hear what you are saying about the mainline kernel + patches. Unfortunately, I have a feeling that this will mean that slackwareaarch64 will continue to have serious issues with graphics even once the current problem is solved.

It had been my intention to try building a RPi fork kernel for the Pi and seeing if that helped. Unfortunately, that is not possible any longer, as I can no longer boot slackwareaarch64 at all!

Luckily, it is quite easy to switch OSs on the Pi by simply switching sd cards. However, installation takes a considerable amount of time, and I suspect that building a kernel will be a case of leaving it running over-night!

But until I can at least get it to boot again, that is academic!

--
Pete

glorsplitz · 06-13-2022, 07:22 PM

Quote:

Originally Posted by drmozes

Using the RPi Kernel fork is off the table though. Slackware uses the kernel.org mainline Kernel with patches where required.

Good! Stick with game plan.

pchristy · 06-14-2022, 12:34 PM

I see today's updates, and intend giving them a shot. Unfortunately, due to other commitments, it will be Thursday at the earliest before I get chance - and maybe the week-end (need to take advantage for the current hot weather!).

Thanks to Stuart for his efforts on this, which I do appreciate, despite my apparently negative comments! I really want to see this project succeed.

Cheers,

--
Pete

glorsplitz · 06-14-2022, 06:57 PM

Applied last updates via ssh, had hdmi monitor turned off, as it had gone blank, was ready to reboot, turned hdmi monitor back on, and guess what, it was showing login from when it had gone blank before ssh rebooting, that was odd. Some update applied without reboot?

After reboot, 5.18.3-armv8 #1 SMP PREEMPT Mon Jun 13 10:53:11 BST 2022 aarch64 GNU/Linux, hdmi display is back.

Cheers to aarch64 brain trust!

EDIT: hold that thought

was trying kde on my rpi4 aarch64 setup, so since I thought hdmi was back, startx, turned my head for couple minutes, went back, no hdmi display, ctrl-alt-backspace didn't work, ssh it's all there.

xwmconfig flux, blackbox both worked, tried couple apps, like mc, these worked, tried konqueror, screen quit on me, whatever situation I have now, doesn't seem to like kde stuffs

didn't see any (EE) in xorg log

mralk3 · 06-14-2022, 10:34 PM

Quote:

Originally Posted by pchristy

I see today's updates, and intend giving them a shot. Unfortunately, due to other commitments, it will be Thursday at the earliest before I get chance - and maybe the week-end (need to take advantage for the current hot weather!).

Thanks to Stuart for his efforts on this, which I do appreciate, despite my apparently negative comments! I really want to see this project succeed.

I appreciate your comments. I interpret them as constructive criticism that Stuart and I can use. Just try to remember that Slackware Aarch64 uses a different kernel than the one provided by the Raspberry Pi foundation. RPI OS and Slarm64 use that forked kernel. Slackware Aarch64 is built from source differently, and is resting on top of a generic mainline kernel.

I have been outside furiously doing yard work and landscaping while it's not TOO hot yet. Preparing the house and the property for the 4th of July celebration my family has planned. Which is why I've been absent here on the forums. Looking forward to your feedback on today's updates.

pchristy · 06-15-2022, 01:56 AM

Quote:

Originally Posted by mralk3

I appreciate your comments. I interpret them as constructive criticism that Stuart and I can use. Just try to remember that Slackware Aarch64 uses a different kernel than the one provided by the Raspberry Pi foundation. RPI OS and Slarm64 use that forked kernel. Slackware Aarch64 is built from source differently, and is resting on top of a generic mainline kernel.

I have been outside furiously doing yard work and landscaping while it's not TOO hot yet. Preparing the house and the property for the 4th of July celebration my family has planned. Which is why I've been absent here on the forums. Looking forward to your feedback on today's updates.

Thanks for that! I really don't want to upset anyone, but when something clearly doesn't work, however constructive I try and make my comments, it is hard not to sound negative! Also, bear in mind that although I have a good working knowledge of computers, I am NOT a programmer - certainly not at this level - so it is hard to know what information is relevant and what isn't. All I can do is report what I find.

I hear what you say about the kernels. I have no doubt that the "stock" kernels work fine on other Arm systems. My only experience of Arm is on the Raspberry Pi, and clearly there is something about the Broadcom chipset they use that is not covered by the stock kernels. This maybe due to copyright issues or who knows what, but clearly there is a problem there. If I can get the system up and running again - even without X - I will have a go at compiling the forked kernel and see what happens.

BTW, it appears that you are part of the aarch64 development team, so my apologies for not including you with Stuart in my comments.

Glorsplitz: I see you are still having problems with kde under X. Have you tried Wayland? My experience of it in x86_64 is that it is slower and clunkier than X, but maybe it will bypass whatever issue the X/kde system is having?

Just a thought!

--
Pete

stormtracknole · 06-15-2022, 01:39 PM

Greetings!

So I built the latest rpi official kernel from source (currently 5.15.45-v8+) following Exaga's steps on a pi4 4GB. When starting X, I still the llvmpipe under OpenGL renderer string. So, obviously it is not the kernel since I am still getting the same issue with it. Running lsmod does show the vc4 and v3d drivers loaded (on both the rpi and mainline kernels). So they are available. The desktop doesn't freeze at least. Perhaps we might be missing something related to mesa or xorg?

mralk3 · 06-15-2022, 03:35 PM

This is the bug we are dealing with: https://lore.kernel.org/all/CAPpJ_ec...l.gmail.com/T/

According to that report, these are the commits they refer to:

drm/vc4: kms: Remove async modeset semaphore
https://github.com/raspberrypi/linux...66d978ef2c6fef

drm/vc4: kms: Convert to atomic helpers
https://github.com/raspberrypi/linux...ecf63167596dc3

I'm not sure how to fix this issue without going through the mainline Linux kernel source to see if a git revert was applied. Clearly those commits are old in the RPi kernel, but has the mainline kernel been patched... I saw another more recent bug report where it was discussed whether to send or not send the patches upstream.

This also looks relevant: https://bugs.launchpad.net/ubuntu/+s...i/+bug/1946368

Any suggestions are welcome!