Mike Pinkerton

Nope.

Allo doesn't seem to monitor this site any more :-(

What this page doesn't address is what image to put on the SD card. I asked them that and got no response when the image I put on there didn't boot at all.

Seems they have stopped responding or even visiting this site. I've sent multiple messages and gotten no replies. Haven't seen a sign in from their latest account (they have several) in over a month. At this point I will spend my money elsewhere (as my USBridge no longer boots) rather than try to get it working again. -mike

This weekend i thought I would update my DigiOne as I hadn't in a while. When running dietpi-update (as recommended on the Allo web UI screen), there was a curl error about an out of date SSL certificate and the update stopped. However, it left the OS in a weird state. When I rebooted it, it no longer connects on the network and cannot put up the web UI or ssh into it. I know in the past when this happened, customer service would ship out a new SD card with a fixed OS on it. Can you do that for me? Having to go through all the hassle of re-imaging a card with the latest DietPi seems like a lot. -mike

I filed https://github.com/MichaIng/DietPi/issues/2652

I'm on 6.13 and when i use dietpi-update I get... [ OK ] DietPi-Update | APT update, please wait... Ign:1 http://ftp.debian.org/debian stretch InRelease Hit:2 http://ftp.debian.org/debian stretch-updates InRelease Hit:3 http://ftp.debian.org/debian stretch-backports InRelease Hit:4 http://ftp.debian.org/debian stretch Release Ign:5 https://deb.debian.org/debian-security stretch/updates InRelease Err:6 https://deb.debian.org/debian-security stretch/updates Release server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none Reading package lists... E: The repository 'https://deb.debian.org/debian-security stretch/updates Release' does no longer have a Release file. [FAILED] DietPi-Update | G_AGUP Ideas?

On the Pi, the ethernet and USB share the same bus, which reduces available data bandwidth. The Pi can handle DSD64 just fine over Ethernet, but I had issues going up to DSD128.

Thanks for the help, but I ended up using an extra SD card to create a fresh OS install, copy over a new disk image from a USB key to the eMMC, then start over from scratch. For devices that are supposed to be turnkey, making this network change required a significant amount of Unix knowledge. Thankfully it's all back to normal. I did waste 20 minutes on the USB vs. USB1.1 DAC setting. @Daniel Knight can you add some explanatory text in the AlloGUI dropdown that USB 1.1 is for older devices and plain USB is for newer ones? Even though I know this, my lizard brain still picked 1.1 because it's "higher" than no number.

My network changed rather significantly (new Xfinity router means all NAT and static IPs changed). I had my USBridge configured with a static IP address on 10.0.1.X, but my new network is 10.0.0.X and so my USBridge won't seem to connect to the new network. How do I reset it to factory defaults so it goes back to DHCP so I can connect to it again? @Allo please help!

@Allo Is this a concern?

So you're saying that elevated temp is normal?

@Allo What is the normal temp? Mine is running at 52C, which is "running warm, but safe". My RPi with a BOSS hat is only running at 40C, which is "optimum". This is not streaming/playing anything (idle except for my ssh), and the RPi is currently streaming via RAAT. This seems high and worries me.

@Allo any response?

Just got mine installed and it's all working great (even after updating). However I have two questions: 1) What is the normal temp? Mine is running at 52C, which is "running warm, but safe". My RPi with a BOSS hat is only running at 40C, which is "optimum". This is not streaming/playing anything (idle except for my ssh), and the RPi is currently streaming via RAAT. 2) When I type "alsamixer" at the command-line, I get "cannot open mixer: No such file or directory". That seems odd, is something misconfigured? It plays just fine. -mike