Closed LoneNomadBlue closed 10 months ago
The first one is failing because libusb doesn't ever install properly. The second one fails because you deleted the libusb line, again not installing right and cut out an echo with it breaking the command.
From your second comment:
abisselfar@toypad:~ $ sudo apt update toverlay=dwc2" | sudo tee -a /boot/config.txt echo "dwc2" | sudo tee -a /etc/modules echo "libcomposite" | sudo tee -a /etc/modules echo "usb_f_rndis" | sudo tee -a /etc/modules
git config pull.rebase false git clone https://github.com/Berny23/LD-ToyPad-Emulator.git cd LD-ToyPad-Emulator
toverlay=dwc2" is both not a command and a broken string, so it's interrupting.
But ultimately these logs feel like a mashup of different attempted fixes, we need a baseline. Reimage again to just the normal 32-bit Raspberry Pi Lite in the Raspberry Pi Imager. Run each command line-by-line one at a time, copy and pasted. And then share those logs and we can figure out what happened. The audit also doesnt really matter. It's just that a few of the libraries this project uses are outdated and have vulnerabilities. But since this device is only ever intended for local network that's not a concern.
Like I said, the audit notice is not an error and does not matter. So stop running audit fix, because that changes the versions of affected libraries. I'm not sure why the command disappears from the line but looking at those those last logs you posted seem to show a successful installation. Did you try it with the game?
But did you try on a successful installation where you didn't change the library versions by running audit fix because that could affect it.
Your earlier logs didn't install the usb driver properly which is why those ones weren't connecting. Also try running the toypad program before starting the game.
Again I'm telling you you're not "gaining vulnerabilities" everyone gets those it's just DDoS exploits found in the specific versions for a few libraries we use, but this is not an internet device so that does not matter. They are not an error or issue. Your scenario one is describing a successful installation. I even tested a fresh install on my Pi and had success.
But it leaves me kinda stumped if everything you say is true the only thing that makes sense to me is something is wrong with the USB connection. Either your usb cable, your computer, or the Pi itself.
Good to hear. Hope you have fun
.