run 'sudo apt update' and it will prompt you with a y/n. choose y and that will go away
Just got my pi4 4gb installed this build and restored my previous setup with ZERO problems. All connections transferred over and work great with the USB 3 ports. Camera setup transferred without any adjustments. If there is any additional information I can give about this build I would be happy to help!
Thank you so much!
Hello,
thanks for the image for the pi 4.
test pass:
- octoprint OK
- connection to printer OK
- control printer (home) OK
- webcam logitech C270 OK
- GPIO BCM OK
- GPIO BOARD FAILED
for fix:
- update wiringpi
cd /tmp
wget https://project-downloads.drogon.net/wiringpi-latest.deb
sudo dpkg -i wiringpi-latest.deb
- update python gpio lib
~/oprint/bin/pip install --upgrade --pre rpi.gpio
- update system
sudo apt update && sudo apt full-upgrade
On that note, I don't know if everyone's heard but Gordon, the author of wiringpi got fed up with cheeky users and decided to pull the plug on this project.
I did not know, it's ugly.
unfortunately it does not shock me 
I've been trying to connect my Pi 4 running this version of Octopi to an SKR Mini v1.1, but for the life of me, can't get the Pi to see when I connect to the board via usb. I've tried (ls/dev, lsusb, dmesg) and it appears as though it doesn't see the connection at all. The board connects fine to a PC and communicates fine via Repetier Host, just not the Pi. Any thoughts?
If you have a Raspberry Pi 3B then you might put the same microSD into that and see if that one is happy. It might not be so much a Pi4 thing as a basic setup thing.
I have a Pi 0, think it would be able to handle the imaged Octoprint?
Nope.
It's good for a dedicated webcam server, though. (Search the forum for that.)
I plugged in a standard empty USB stick and the RPI4 recognized it right away, so I have narrowed the problem down to the Pi recognizing my SKR Mini board, but am clueless on what to look at to resolve the issue. All I know is that after running "sudo dmesg -C", then plugging in the USB cable to the Pi, then running "dmesg", the Pi reports back nothing.
Not sure what to tell you other than to verify that your serial cable is good.
Serial cable is fine, as it connects my old Anet board to my Pi 0 fine and the SKR mini to my PC fine.... which is why this is so frustrating. But I appreciate the attempt to help.
Okay, work with what you know: what device did Repetier Host use for it?
OutsourcedGuru, not sure where to find that information in RepHost. I can give you whatever information you're looking for from the properties in Device Manager, if that helps. I don't see any tty information though
Not that I've ever used the software but it didn't take long to find a page like this on Repetier's website. Visit the Printer Settings dialog box and look for the port/device.
Outsourced, I'm not sure how knowing that the board is communicating through COM6 on my PC is going to help me in figuring out why my RPI4 doesn't even register that there is a device plugged into the USB port when I connect the serial cable in. I do appreciate your attempt at helping me figure this out. I'm here because simple internet searches for the problem I am experiencing have turned up no results.
On the Pi, with the printer plugged in, what is the output of lsusb -vvv
pi@octopi:~ $ lsusb -vvv
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.19
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 4.19
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x001f
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
bMaxBurst 0
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x3431 Hub
bcdDevice 4.20
iManufacturer 0
iProduct 1
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.19
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Do you have your printer connected through a USB hub?
Can you try with the printer connected directly to the RPI usb ports? Try both the USB 2 and USB 3 ports.
No USB hub connected. This same output comes up no matter which of the four ports I connect the printer to on the RPi4, with multiple cables