I have been getting some weird console messages on shutdown/startup that say cannot get freq at ep 0x86 or some variation of this, and I am not sure why this is occurring or what usb peripheral of the argon oneup is causing this error message. If anyone could provide guidance, I would greatly appreciate it. I have attached a picture of this issue below:
1 Like
I have been seeing this as well. I’ve been told (I think on one of the Github pages dedicated to the One Up, but I’d have to look) that it’s related to the camera’s microphone, but I haven’t independently confirmed this.
I haven’t actually tested the microphone support yet for the laptop (haven’t had the need yet), but otherwise the system seems to run fine for me with no hiccups. I’ve used both a CM5 with EMMC and a CM5 Lite (without EMMC), so I am pretty sure it’s not related to the issue where shutdown is delayed 30-60 seconds when using a CM5 Lite and no SD card is in the reader.
If anyone has a fix or thoughts to at least confirm the culprit, I would be interested as well!
1 Like
Had a similar issue with another computer and it turned out that the camera wasn’t getting enough power and needed to be put onto an externally powered hub.
Not sure how to determine if this might be from the same cause; are schematics provided for the OneUP? Or I may have to do some board tracing one of these days, when it bugs me enough 
I have the same alert visible in journalctl on my machine (running EndeavourOS, an Arch derivative).
Both USB Audio devices (the C-Media main sound card, and the Camera’s microphone) seem to work correctly anyway.
Oh, I’m not particularly worried about it, and I agree that everything seems to work fine in spite of the warning. But it does offend my sense of propriety – if everything is properly setup and designed, warnings shouldn’t happen (at least not when it’s new).
This is not a slight on Argon - it’s a nice piece of kit, and the closest thing to a proper laptop the Pi family has ever seen. But bugs do happen, and if we can identify and fix it, a future version/update doesn’t have to have the same problems.
Like I said, I may trace it down further, if it starts to bug me enough. A schematic would be helpful, but probably isn’t necessary for the kind of tracing I envision.