Google Coral not recognized by proxmox | Home Assistant | Page 1

shell birch Dec 2, 2024, 4:43 PM

#

Not strictly HA but I hope it will pass since it's used for HA.

All of a sudden HA/Frigate doesn't work anymore, after some troubleshooting I find that proxmox reports "unplugged" for the passthrough. I have passed through the whole usb port to proxmox, and while it shows up as an option (and shows with ´lsusb´), Frigate fails to regonize it - most likely because proxmox reports it as "unplugged".

Changing ports doesnt help - proxmox suggests the new port used for passthrough, but it still says "unplugged".

Any ideas?

fleet spoke Dec 2, 2024, 4:45 PM

#

Does it show in vendor id?

shell birch Dec 2, 2024, 4:51 PM

#

fleet spoke Does it show in vendor id?

Yes, as generic though, and does not work either

fleet spoke Dec 2, 2024, 4:53 PM

#

Do you use USB port or PCI "passthrough" for any other VM?
You can also check lsusb -vt to get more info about the devices and their drivers.

#

Also try this once passed through in the SSH addon: #zigbee-archived message

shell birch Dec 2, 2024, 4:56 PM

#

No, only for this vm, and it's the only usb attachment

#

Run it in the proxmox shell or in the vm?'

fleet spoke Dec 2, 2024, 4:57 PM

#

Both. lsusb -vt in PVE and what I linked to in the SSH addon.

#

The picture is cropped too much.

shell birch Dec 2, 2024, 4:58 PM

#

#

fleet spoke Dec 2, 2024, 5:01 PM

#

You can also try to unplug it, run dmesg -Tw and then plug it in again. Maybe there's something wrong with it.
I'm not sure how corals are supposed to be shown. Usbfs might just what they normally get assigned.

#

In HAOS' case it has no driver assigned for example.

#

You can do the same in HAOS too btw. Use the VNC console, enter login, then run dmesg -Tw and plug it in. Or perhaps rather attach and detach via the GUI.
ha host logs -vf might also show it but best to use the same tools here.

shell birch Dec 2, 2024, 5:24 PM

#

Thanks, I'll try in a minute

shell birch Dec 2, 2024, 6:12 PM

#

fleet spoke You can do the same in HAOS too btw. Use the VNC console, enter `login`, then ru...

I got a lot of "detected hardware hang" when running this in the proxmox shell, feels like it would be related?

fleet spoke Dec 2, 2024, 6:13 PM

#

Please share what you see.

shell birch Dec 2, 2024, 6:14 PM

#

A very long log of entered and left promiscous mode, mixed in with some of these:

fleet spoke Dec 2, 2024, 6:14 PM

#

So good news I don't think it's related. Bad news this is quite common for these NICs: https://www.google.com/search?q=e1000e+proxmox
Maybe you could get yourself a 2.5G USB NIC? 2.5G simply because it's not much more expensive and more future proof.

shell birch Dec 2, 2024, 6:16 PM

#

Hm, but I do not have any other issues afaik.

fleet spoke Dec 2, 2024, 6:16 PM

#

What was shown when you plugged the coral in?

shell birch Dec 2, 2024, 6:17 PM

#

Shown where? Run the command again?

fleet spoke Dec 2, 2024, 6:18 PM

#

Yes. Run the command to follow the kernel logs, then plug the stick in and see what is shown.

#

Do that for both PVE and the VM as explained above. We might find out why it has no driver in HAOS.

shell birch Dec 2, 2024, 6:19 PM

#

disconnect and reconnect in pve:

#

So it sees... something

fleet spoke Dec 2, 2024, 6:19 PM

#

Makes sense PVE's manufacturer column is empty if there's nothing here.

#

This is not necessarily a problem.

shell birch Dec 2, 2024, 6:20 PM

#

I should say (shouldve probably said before), that I've had it shown as a generic usb device before (Global Inc something), and that has still worked with frigate when passing through the port rather than the device

#

Sorry, worked with frigate, not proxmox

fleet spoke Dec 2, 2024, 6:22 PM

#

Right now I kind of blame HAOS as it sees the device but hasn't assigned a driver to it.
Try dmesg -Tw there too.

#

Since it's virtual you can simply detach/attach the USB device in the PVE GUI to achieve the same effect of (un)plugging it.

shell birch Dec 2, 2024, 6:23 PM

#

fleet spoke Dec 2, 2024, 6:24 PM

#

Hmm. Looks pretty much the same.

shell birch Dec 2, 2024, 6:24 PM

#

Tried passing through the port ^

#

Not sure it means something, but in the GUI the port is called 4-1, in the console it says 3-1

fleet spoke Dec 2, 2024, 6:25 PM

#

That's for the PVE node and that matches.

shell birch Dec 2, 2024, 6:26 PM

#

ok

fleet spoke Dec 2, 2024, 6:26 PM

#

I'd still recommend using the vendor id to pass through.

shell birch Dec 2, 2024, 6:27 PM

#

Identical log with vendor id, bar a new number

#

Maybe I'll try another reboot of the host with the usb disconnected

fleet spoke Dec 2, 2024, 6:27 PM

#

I wasn't trying to imply that this would fix anything. It's just more reliable if you plug it in another port for example.

shell birch Dec 2, 2024, 6:28 PM

#

Yep gotcha

fleet spoke Dec 2, 2024, 6:30 PM

#

Unfortunately I don't see anything useful in the kernel logs. I'm not quite sure why the USB device has no driver. Maybe it will only get one assigned if something tries to actually use it. HAOS is a bit different than other operating systems.

shell birch Dec 2, 2024, 6:31 PM

#

There's no way to manually assign it that you know of?

#

thin ice for me 😬

fleet spoke Dec 2, 2024, 6:32 PM

#

Not at the top of my head.

shell birch Dec 2, 2024, 6:36 PM

#

Just for my understanding, could proxmox reporting the vendor as Unknown be because of HAOS not assigning it a driver? I thought that proxmox would be "on top" of the VM in the process, but maybe it needs its driver from HAOS here as well?

fleet spoke Dec 2, 2024, 6:37 PM

#

No. As you can see in the dmesg output of the node itself the USB device does not seem to provide such strings.

shell birch Dec 2, 2024, 6:37 PM

#

Hm, ok.

fleet spoke Dec 2, 2024, 6:37 PM

#

Have you tried to cold boot HAOS after attaching the USB device?

shell birch Dec 2, 2024, 6:38 PM

#

Assign to vm -> shut down vm -> boot vm?

fleet spoke Dec 2, 2024, 6:38 PM

#

Yeah or the Reboot button in the GUI. Kind of does the same.

shell birch Dec 2, 2024, 6:39 PM

#

Just with the device detached, I'll try now

#

I found this - worth trying? https://github.com/google-coral/edgetpu/issues/536#issuecomment-2378251821

fleet spoke Dec 2, 2024, 6:40 PM

#

Maybe. I don't own a coral myself and am not familiar with its potential quirks. I'm somewhat familiar with linux though.

#

I tested udevadm monitor and attached a WiFi stick. HAOS does not really take note of it until I reboot the VM.

shell birch Dec 2, 2024, 6:42 PM

#

o_O we've got progress in the Frigate logs, still loading but
2024-12-02 18:41:16.718691615 [2024-12-02 19:41:16] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found

fleet spoke Dec 2, 2024, 6:44 PM

#

Hmm.

shell birch Dec 2, 2024, 6:45 PM

#

You know what? It worked!

fleet spoke Dec 2, 2024, 6:45 PM

#

That script you linked?

#

Or the reboot?

shell birch Dec 2, 2024, 6:45 PM

#

PVE gui still reports it as unknown, but ´lsusb´ now reports it as Google Inc

#

The reboot

#

I rebooted so many times but maybe not with it actually attached, which was stupid in hindsight

#

I really appreciate the help 🙂

fleet spoke Dec 2, 2024, 6:46 PM

#

I just know that HAOS sometimes does not detect zigbee sticks unless it was booted with them plugged in.

shell birch Dec 2, 2024, 6:48 PM

#

Good to know! Actually now z2m is not working. But thats another problem with the pve then, something to fix after dinner.

fleet spoke Dec 2, 2024, 6:49 PM

#

If you need/want help with that and open another thread I might be able to help with that too 🙂
I marked this as resolved.

#Google Coral not recognized by proxmox