Open ofcJakes opened 1 year ago
Here you can place your folders containing docker-compose.yml files
is this important?
@khassel might know. Did you try plugging in to another screen as a test?
yes I have but its not only magicmirroros if I install linux and try magicmirror its gives me a black screen with cursor if I try raspbian with magicmirror it give me a black screen with cursor maybe Im missing a setting but I have followed different installations and os's but nothing works?
Just got ERROR:viz_main_impl.cc(186) Exiting GPU process due to errors during initialization
Don't know if you already edited the config.js
, if so, try with the default one first.
but its not only magicmirroros
so this sounds like a general problem and I recommend to ask in the magicmirror forum.
I think this image is broken. I see the same thing as the issue creator. If I ssh into the device and run top
, I see npm run start
appearing over and over again, which suggests it's crashing. Steps to reproduce:
top
.In other words, I am not doing anything except the mainline path according to the directions.
I speculate this is because the underlying MagicMirror project has moved on in the ~2 years since this image was created, and requires a current version of the Raspberry Pi distribution. (https://github.com/guysoft/MagicMirrorOS/issues/53 seems to say the same thing.)
I could update the Debian-based distro, but that would defeat the purpose of using the MagicMirrorOS project, which is an "out of the box Raspberry Pi Raspbian distro that lets you run MagicMirror to make an interactive mirror" (emphasis added). If I have to get into maintenance of the distro, then it's no longer out-of-the-box, and it's unclear what the value is of MagicMirrorOS over MagicMirror.
I can build a new nightly image if you can test it.
Thanks! I'd be happy to try a fresh installation.
On Tue, Feb 28, 2023 at 5:28 AM Guy Sheffer @.***> wrote:
I can build a new nightly image if you can test it.
— Reply to this email directly, view it on GitHub https://github.com/guysoft/MagicMirrorOS/issues/56#issuecomment-1448181100, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAHMVF2FBGPDFJMFQQXL3TWZX4P7ANCNFSM6AAAAAAUGWSH2Q . You are receiving this because you commented.Message ID: @.***>
Started a build that would likely fail becauae of https://github.com/guysoft/MagicMirrorOS/issues/58 will look in to it
Jumping in to say I'm seeing the same issue. Following the instructions, I get a black screen.
@sowbug There is a new image here: https://unofficialpi.org/Distros/MagicMirrorOS/nightly/2023-03-15_2023-02-21-magicmirroros-bullseye-armhf-lite-0.3.0.zip
You can also use the pi-imager: https://github.com/guysoft/pi-imager
@khassel we could release an RC if any of you can test and confirm it works
Does anyone have time to test the new build? It would help me understand if its worth releasing an RC.
Thanks for the ping. I missed that the build succeeded. I'll be happy to give it a whirl today.
On Wed, Apr 5, 2023, 2:41 AM Guy Sheffer @.***> wrote:
Does anyone have time to test the new build? It would help me understand if its worth releasing an RC.
— Reply to this email directly, view it on GitHub https://github.com/guysoft/MagicMirrorOS/issues/56#issuecomment-1497205322, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAHMVBQ5QO4NERGBSCEKU3W7U44HANCNFSM6AAAAAAUGWSH2Q . You are receiving this because you were mentioned.Message ID: @.***>
Flashed, booted to console login screen. I waited a long time to see what would happen. I then set up the wpa_supplicant file on the boot partition and rebooted. Nothing happened after booting back to console. I ssh'ed in and determined that scripts/run_magicmirroros
needed to run. So I executed that script. About an hour later, I noticed the RPi was rebooting a couple times. I let it sit another half hour, still at the console login. Then I ssh'ed in again and noticed it was boot-looping npm run start
, just like in my Feb 23 comment.
@guysoft I'm baffled that your successful boot experience is so different from mine, given that the number of hardware configurations is relatively small. When you tested the new image, which Raspberry Pi hardware were you using?
I dont have any hardware to test it on. I have no magic mirror.
@khassel could you take a look at it? Sounds like an issue with the node code
I am having the same problem. I can get it to run if I swap the start for server in the docker-compose.yml but then it is running as a headless server without projecting the actual board from the pi. I can then access it from a web browser on another computer
note: I now have it working for me. I had to run the raspi-config to tell it to automatically boot into windows.
I dont have any hardware to test it on
me too at the moment ...
I missed the new image is now already bullseye. So this will not work with current configuration. Workaround for testing would be to replace the docker-compose.yml
:
cp -v "$HOME/magicmirror/run/rpi.yml" "docker-compose.yml"
Before releasing an RC this must be fixed so I created the above PR which moves parts of the start script into my repo so I can react faster and can change/update things there (without the neccessarity of building a new pi image).
So @guysoft please merge and build a new pi image ...
New image built.
You can flash it using pi-imager.
https://github.com/guysoft/pi-imager/releases
Or download it here: https://unofficialpi.org/Distros/MagicMirrorOS/nightly/
I have an Raspberry pi 3 B plus and don't know much about MM or shell. I do really need this to work and I keep getting stuck on a black screen with my cursor. I'm not sure how ssh works what can I try. Keep in mind very little knowledge about Pi's and MM