#raspbianos — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #raspbianos, aggregated by home.social.
-
I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
-
I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
-
I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
-
I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
-
I’ve been experiencing repeating issues in #HomeAssistant with devices not responding. It’s been manifesting in the system log as an error:
cp210x ttyUSB0: failed set request 0x12 status: -110
That’s Zigbee dongle. The workaround was to reboot the system, but I’ve changed it’s USB port and it seems to be gone.
The system is #RaspbianOS on #Raspberry Pi5. Pi is powered via PoE and it should have sufficient power budget, though it’s running of an nvme.2 and with USB hard drive, so who knows…
-
@WestkirchenAndi Ich nutze einen Raspberry Pi 4 mit 8 GB RAM mit externer SSD über USB angeschlossen. Das Ganze läuft mit Raspbian OS und komplett verschlüsselter Platte, inklusive Remote Passworteingabe per SSH. HomeAssistant läuft über docker compose.
-
@WestkirchenAndi Ich nutze einen Raspberry Pi 4 mit 8 GB RAM mit externer SSD über USB angeschlossen. Das Ganze läuft mit Raspbian OS und komplett verschlüsselter Platte, inklusive Remote Passworteingabe per SSH. HomeAssistant läuft über docker compose.
-
@WestkirchenAndi Ich nutze einen Raspberry Pi 4 mit 8 GB RAM mit externer SSD über USB angeschlossen. Das Ganze läuft mit Raspbian OS und komplett verschlüsselter Platte, inklusive Remote Passworteingabe per SSH. HomeAssistant läuft über docker compose.
-
Ah... Let's get to it shall we?!?
Bash and Nano on the good ole RaspbianOS!****ferris Buller plays (Oh Yeah - Yello)
-
Ah... Let's get to it shall we?!?
Bash and Nano on the good ole RaspbianOS!****ferris Buller plays (Oh Yeah - Yello)
-
So... Let's begin the updates shall we?!
Updating RaspbianOS. Time to apply all that was studied these prior moons.
Side note: Cmatrix always gets me in the mood to code.
-
So... Let's begin the updates shall we?!
Updating RaspbianOS. Time to apply all that was studied these prior moons.
Side note: Cmatrix always gets me in the mood to code.
-
Ok this is incorrect. I didn't realize that Waveshare has two different versions of their dtoverlays, one for legacy versions of RaspbianOS and one for “new" versions. Obviously, if I try to load the wrong version, the OS won't initialize the LCD properly.
-
Ok this is incorrect. I didn't realize that Waveshare has two different versions of their dtoverlays, one for legacy versions of RaspbianOS and one for “new" versions. Obviously, if I try to load the wrong version, the OS won't initialize the LCD properly.
-
Ok this is incorrect. I didn't realize that Waveshare has two different versions of their dtoverlays, one for legacy versions of RaspbianOS and one for “new" versions. Obviously, if I try to load the wrong version, the OS won't initialize the LCD properly.
-
Ok this is incorrect. I didn't realize that Waveshare has two different versions of their dtoverlays, one for legacy versions of RaspbianOS and one for “new" versions. Obviously, if I try to load the wrong version, the OS won't initialize the LCD properly.
-
When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.
If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.
Is there some intermediate step happening on first boot?
-
When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.
If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.
Is there some intermediate step happening on first boot?
-
When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.
If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.
Is there some intermediate step happening on first boot?
-
When I load the Waveshare dtoverlays and modify the config.txt and cmdline.txt *after* the first boot of a fresh RaspbianOS install, the DPI LCD is not used.
If I load the Waveshare dtoverlays onto the SD card and modify the config.txt and cmdline.txt *before* the first boot of a fresh system, everything works as expected.
Is there some intermediate step happening on first boot?
-
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
-
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
-
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
-
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
-
So, I had to use #raspbianos to get the v3 camera module working on my pi3A+. This feels like a huge downgrade from my usual #dietpi install. Once everything was said and done with the camera working, I finally disconnected it from my TV to run headless. A lot of frustration later, I find out that VNC isn't working properly with the new #bookworm release.
-
I'd like to install #WriteFreely on my #RaspberryPi 4 where I also run my #Mastodon #SingleUserInstance and #JellyFin. (Yeah, since they're not consuming too much power, compute or space)
But how do I install #WriteFreely from the #RaspbianOS #CLI, with #PostgreSQL & #ngnix? 🤔 Any documentation for it? 🙏🏼😔
@darnell would you know?
-
I'd like to install #WriteFreely on my #RaspberryPi 4 where I also run my #Mastodon #SingleUserInstance and #JellyFin. (Yeah, since they're not consuming too much power, compute or space)
But how do I install #WriteFreely from the #RaspbianOS #CLI, with #PostgreSQL & #ngnix? 🤔 Any documentation for it? 🙏🏼😔
@darnell would you know?
-
@aswath can definitely sell it as an appliance, especially if you can box up a #RaspberryPi (I'm on 4 with 4 GB RAM).
Only challenges would be simplifying the installation wizard for domain registration, #SSL certificate registration, and #DynamicDNS.
Best world be if that wizard comes up while imaging the #RaspbianOS on the #microsdxc card itself. Or booting up the appliance for the first time.
You could do that on 1 TB microsdxc or 256 GB microsdxc plus 1 TB USB drive.
-
@aswath can definitely sell it as an appliance, especially if you can box up a #RaspberryPi (I'm on 4 with 4 GB RAM).
Only challenges would be simplifying the installation wizard for domain registration, #SSL certificate registration, and #DynamicDNS.
Best world be if that wizard comes up while imaging the #RaspbianOS on the #microsdxc card itself. Or booting up the appliance for the first time.
You could do that on 1 TB microsdxc or 256 GB microsdxc plus 1 TB USB drive.
-
How to check--get the Raspberry Pi CPU temperature simplest way. Use command in terminal. https://www.ungeekiness.com/2022/11/how-to-check-get-raspberry-pi-cpu.html
#RaspberryPi #howtoget #cputemp #simplestway #terminalcommand #RaspbianOS #rpios