Anybody knowledgeable in Linux/Raspberry Pi drivers?

[m_c]

I have a raspberry Pi4b, that I've installed Octoprint on (using Octopi), that works well.
I also have a touchscreen, as I'd like to use Octodash to control the printer without the need to login to Octoprint via computer/phone.

However, when I install the touchscreen drivers, the USB ports stop working.
Using the lsusb command, one of the USB root hubs no longer shows.

And that is where my limit of Linux ends. I have tried various searches, but I'm struggling to find any kind of solution.

So, is there anybody on here who can help?
I can post more details if needed.

 

[sako243]

Simply put - more details required.

Have a look in dmesg or /var/log/messages to see if there are any errors when it starts up.

 

[MattF]

I always tend to keep an eye on new log entries in realtime with: tail -f [message file path]


Btw, don't Google "man tail". I was double checking my syntax before posting, & neglected to anticipate the obvious results, now that I think of it, which were returned.

 

[m_c]

It's an osoyoo 3.5" display, and these are the touchscreen installation instructions for installing the drivers on an existing installation - Raspberry Pi 3.5″ HDMI Touch Screen Installation for Linux Driver (2) « osoyoo.com
The touchscreen itself works perfectly once the drivers are installed, it's just the USB ports stop working.

The result of dmesg is attached below (I did paste it in, but it's too long for the message post length limit)

If it helps, I can get run dmesg on an install without the touchscreen drivers, as I have another sd card with just a basic octopi install.

There appears to be quite a lot of lines in the messages log, but I'll have to work out how to get a copy of the log on to my computer.

 

[m_c]

And here's the messages log, although it mostly seems to be errors from octoprint due to having no webcam attached.

 

[m_c]

And for reference, here's dmesg from the clean install of octopi, which appears to have some very noticeable differences in how things are being initialised.

 

[sako243]

Just a thought does the Pi have enough power going to it to supply everything powered off the USB hubs? I've had weird behaviour before when it's struggled.

Do you get the little lightening bolt icon on the GUI? If I remember correctly there's also some LEDs on the Pi itself that indicate brown outs.

Might be worth putting a bench supply directly onto the appropriate header if you can just for testing purposes (there's a couple of pins you can inject the power onto the 0.1" headers).

 

[brewdexta]

From memory, you also have to put tape on one of contacts on the usb lead from the pi running octopi to the printer to stop the printer from being powered by the pi. I have a link somewhere.

 

[brewdexta]

These two links should help https://www.mig-welding.co.uk/forum/threads/what-3d-printer.103545/post-1653673 and https://www.mig-welding.co.uk/forum/threads/what-3d-printer.103545/post-1649391

To summarise, with a pi4 you need to add "over_voltage=1" to /boot/config.txt of the pi as the USB behaviour as changed and without it you don't get serial comms. The other fix was to put a sliver of polyamide tape on the USB cable 5v connection so the pi is not trying to power the printer main board. I did try a cheapo 3.5" touchscreen first, the "drivers" screwed up everything so I reverted to a "proper" pi touchscreen from pimoroni or pi hut. I could have probably fixed it but got bored.

Edit - the screen that was pants was an Elegoo 3.5" screen. The screen I ended up using was from Adafruit

 

[MattF]

From memory, you also have to put tape on one of contacts on the usb lead from the pi running octopi to the printer to stop the printer from being powered by the pi. I have a link somewhere.

I noticed that the other day, when I connected the Ender to the PC. The display came on, even though the printer was off.

 

[growntree]

I noticed that the other day, when I connected the Ender to the PC. The display came on, even though the printer was off.

I just turn the printer on and then the pi.

 

[m_c]

@sako243 The Pi is powered via an official Pi 3Aamp power supply, and everything works fine until the touchscreen drivers are installed. The screen works perfectly as just a screen, so I very much doubt it's power related, as installing the drivers shouldn't cause any more power to be consumed.

@brewdexta I'm already aware of the 5V issue. I did add a bit tape to avoid things being powered the wrong way, but it never made any difference to the USB port issue.


Also, having had a bit look at the two dmesg outputs, it appears when the touchscreen drivers get installed, it's changes the version of Linux.
Clean install-

Linux version 5.4.79-v7l+ (dom@buildbot) (gcc version 8.4.0 (Ubuntu/Linaro 8.4.0-3ubuntu1)) #1373 SMP Mon Nov 23 13:27:40 GMT 2020

Touchscreen driver install-

Linux version 4.19.60-v7l (kedei@kedei-ThinkPad) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03)) #1 SMP Tue Jul 30 11:29:51 CST 2019

And having a look around the files in the driver download, it looks like they simply install a new kernel with the touchscreen functionality added, which I'm guessing is what kills the usb.

 

[Kayos]

Any touch screen that is not plug and play on a Pi causes issues

I wanted a decent resolution 8" screen but the drivers caused no end of other issues

Even editing x.conf didn't help, in the end I bought a different screen

 

[m_c]

That's the direction I think I'm going to have to go.
Although the only option I've not yet tried, is to use the osoyoo read to go image, then install ocotprint, which I might try before buying another screen.