3.2 inch touch screen - I did something I shouldn't. APT UPGRADE

[lerner]

Yes, I probably deserve it.

The Ras Pi was working and I `sudo apt update&&sudo apt -y upgrade`

The display is no longer displaying.

Luckily (if you can say that) I can VNC into it and the VNC screen is still 320 x 240.

Also, luckily: I kept the original LCD install files handy. On the Desktop.

Alas running them doesn't fix the problem.

I went to the site and downloaded newer version and it too doesn't work.

Given it used to work, and now it doesn't - yes: because of me - it is only a driver problem.

How do I go about getting it working again?
It just seems unbelievable that if the drivers were working they should suddenly stop.

Oh, for what help it may give/bring this is the link from which I am getting infromation:

http://www.lcdwiki.com/res/MPI3201/Docu ... y_V1.0.pdf

[W. H. Heydt]

Kernel 5.4 changed some things and *many* small SPI LCDs don't work now. you may may be able to get it working by reverting to the previous kernel (4.19). Alternatively, reload your SD card from your working back up. (You DO have backups, don't you?)

[lerner]

Sorry, but how do I revert to the previous kernel?

Specifically the one you mentioned.

Ok, I think I found the information I needed.

This link: https://github.com/Hexxeh/rpi-firmware/commits/master So I did it, and it is rebooting. It works!

Thanks.
(Problem solved!)

[DougieLawson]

sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2 will get you back to 4.19.118. But that's called burying your head in the sand or papering over the cracks as it's not a permanent solution.

[lerner]

sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2 will get you back to 4.19.118. But that's called burying your head in the sand or papering over the cracks as it's not a permanent solution.

Thanks.

I got/used a completely different and smaller number than that.

I did:

Code: Select all

sudo rpi-update e1050e9

For the sake of learning: Where did you get that number?

My number came from the link I posted which was found form this thread:

viewtopic.php?t=79031

Which to me makes sense.

I really need to learn this because I have an older RasPi which may need to have it done to it too.

Oh, though I am looking: How do I determine the kernel version which is installed "now", so I can document that on all RasPies.

[DougieLawson]

It's the same hex number, just truncated to the first six digits.

The number comes from the commits at https://github.com/hexxeh/rpi-firmware.

uname -a tells you what you've got for the kernel.
vcgencmd version tells you the firmware version.

[lerner]

Thanks.

I realised that after posting.

The link I posted was all I had at the time.

Again: Appreciated for the help.

I just want to ask though why you say:

But that's called burying your head in the sand or papering over the cracks as it's not a permanent solution.

If the later kernel versions don't use/support the LCD..... It isn't really doing that - from my take.

Could you please elaborate on why it is not a permanent solution?

[DougieLawson]

Because you'll never be able to upgrade. In 2021 when Bullseye comes out as stable you won't be able to move to that (it's guaranteed to have a V5 kernel).

You need to work with your hardware maker/vendor to find the solution to your touch screen problems, else send it back for a refund as "not fit for purpose".

[lerner]

Ok. Thanks.

With you now.

Sorry. I'm just a bit overwhelmed with things - Yeah: No excuse.

Anyway, I'll work with what I have for now.

Not meaning this directly at you, but I'm a bit confused.

Yeah, "in the beginning....." All was good. Things work.
That a kernel should then be released which doesn't support older things is a bit annoying.

Yes, I get the bigger picture that: "Things move on".
But is it that *bad* if I don't update/upgrade? So long as it is working. It is on a local network and doesn't really need access to the bigger picture.

On a side thing about kernel updates:
I have a NAMED WiPi dongle.
An update/grade black listed it as causing kernel panics. That is a NAME BRAND dongle.
That has really made a mess of some of my projects and RasPi simply wipe their hands of it. "Not our problem."

The fact RasPi can't support their own named hardware gives me little hope that a third party who made hardware for the RasPi will have any more motivation if RasPi themselves don't.

Anyway, for now I can work on this now I have the machine working again with the display.

[trejan]

But is it that *bad* if I don't update/upgrade? So long as it is working. It is on a local network and doesn't really need access to the bigger picture.

If you don't mind it being frozen in time for kernel fixes/features then no. If somebody writes the missing DT overlay for your specific LCD then you'll be able to upgrade but until that happens, you either have a broken display on 5.4 or are stuck with 4.19.

Some overlays have been written by third parties already. Try the ones at the end of https://github.com/notro/fbtft/wiki/FBTFT-RPI-overlays and see if your LCD is compatible with them. If it does work then you're fine to stay on 5.4. If you don't want to tinker with it or are happy to stay on 4.19 then that is your decision.

I have a NAMED WiPi dongle.
An update/grade black listed it as causing kernel panics. That is a NAME BRAND dongle.
That has really made a mess of some of my projects and RasPi simply wipe their hands of it. "Not our problem."

The fact RasPi can't support their own named hardware gives me little hope that a third party who made hardware for the RasPi will have any more motivation if RasPi themselves don't.

Wi-Pi wasn't made by Raspberry Pi so it isn't that surprising that they could only offer limited support for it.

[lerner]

Thanks.

I will check that link.

Appreciated.

Had a quick look. Looks promising.