You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really much of an issue, but more of an annoyance. On Raspberry Pi B+ with the latest Raspbian OS lite (Oct 22, 2024, 32-bit, 12 Bookworm, Kernel 6.6) when booting, the output of run.sh or runpy.sh shows initially along with the Raspbian GNU/Linux header, My IP address is [ipv4] [ipv6], and the login prompt, but then gets wiped when the screen output "condenses" and the My IP address is message continually switches back and forth between the eth IP and wlan IP. Not sure if there's something on Pi-Pwn's end that could alleviate the annoyance or what could be done on the Raspbian OS side. Everything I tried on both ends made no difference, and as stated above, it's not really an issue since Pi-Pwn still fully works as intended, I just don't like having Pi-Pwn's output/status not readily visible on the screen. Hope this makes sense and that I'm not the only one experiencing this odd behavior.
The text was updated successfully, but these errors were encountered:
Not really much of an issue, but more of an annoyance. On Raspberry Pi B+ with the latest Raspbian OS lite (Oct 22, 2024, 32-bit, 12 Bookworm, Kernel 6.6) when booting, the output of run.sh or runpy.sh shows initially along with the Raspbian GNU/Linux header, My IP address is [ipv4] [ipv6], and the login prompt, but then gets wiped when the screen output "condenses" and the My IP address is message continually switches back and forth between the eth IP and wlan IP. Not sure if there's something on Pi-Pwn's end that could alleviate the annoyance or what could be done on the Raspbian OS side. Everything I tried on both ends made no difference, and as stated above, it's not really an issue since Pi-Pwn still fully works as intended, I just don't like having Pi-Pwn's output/status not readily visible on the screen. Hope this makes sense and that I'm not the only one experiencing this odd behavior.
The text was updated successfully, but these errors were encountered: