Fresh install of Pi-Top OS on Pi-Top 4.
pi@pi-top:~ $ pi-top devices
Error on pitop-devices.run: Unable to get device type from pt-device-manager: Resource temporarily unavailable
It seems that no device can be found.
Any clue?
Thx
It seems that the pi-top hub cannot be detected. Any suggestions? Did I get a faulty top or somehow the connection with the hub was not right?
Running
pi@pi-top:~ $ systemctl status pt-device-manager.service
● pt-device-manager.service - pi-top device auto-detection and configuration daemon
Loaded: loaded (/lib/systemd/system/pt-device-manager.service; enabled; vendor preset: enabled)
Active: activating (start) since Wed 2021-04-28 20:01:49 PDT; 2s ago
Docs: https://knowledgebase.pi-top.com/knowledge
Main PID: 14100 (pt-device-manag)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/pt-device-manager.service
└─14100 /usr/bin/python3 /usr/lib/pt-device-manager/pt-device-manager
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.896497 W] Could not initialise v3 hub
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.897491 I] Attempting to find pi-topHUB v2…
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.898450 I] Initialising I2C connection…
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.900134 W] Unable to read from hub (v2) over i2c: [Errno 121] Remote
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.900860 W] Unable to detect pi-topHUB v2 connection
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.901436 W] Could not initialise v2 hub
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.901986 I] Attempting to find pi-topHUB v1…
Apr 28 20:01:49 pi-top pt-device-manager[14100]: [20:01:49.934984 I] Initialising I2C…
Apr 28 20:01:50 pi-top pt-device-manager[14100]: [20:01:50.943796 W] Unable to get battery current
Apr 28 20:01:50 pi-top pt-device-manager[14100]: [20:01:50.943962 I] Initialising SPI…
~
Hi @phabulosa. Could you tell me if you have a pi-top DIY that you assembled? It sounds as though there’s a loose connection somewhere. This could be either the Mezzanine PCB doesn’t have a good connection to the Raspberry Pi, or that the ribbon cable (with the metal backing) that comes out from the hub side, doesn’t have a flush connection to the connector on the Mezzanine PCB. You’re getting the whole device turning on which tells me that ribbon cable has some sort of connection. Or that you have the USB Plug connected.
If you do or don’t have a DIY version of the pi-top [4], could you try typing sudo i2cdetect - y 1 into the command line and see what you find? The another test would be to connect an I2C hat and run the same command to see if that device appears, though the best test would be to connect a foundation plate or an expansion plate and see if those are detected as well. If you were to see the HAT and not the plate then it would definitely be the connections at fault.
Do let me know what you find, hopefully we can find the problem soon!
-Rez
Rez:
I have the DIY version.
This is what I got
pi@pi-top:~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
I believe I fixed the problem.
It was a loose connection for J7.
Many thanks again!
2 Likes