Welcome @lsdoc77!
There have been reports of failures with large capacity uSD cards. @lsdoc77, what size card did you use?
32gb and I verified the image after flashing it.
1 Like
@lsdoc77 you say that you tested on Pi400. Is that the only platform it fails on or did you also test on a RPi4? (There are other reports of Pi400 having issues and we don’t support that platform - although it should work!)
I have not tried it on rpi4 but I will check that too. For now I am reflusing the image. Also I want to say that I have been trying to download the image a couple of days and the md5 was not correct. I download a lot of things and I very rarely have this kind of problems… It’s strange
1 Like
That is interesting. I too seldom have failed downloads. Maybe this could explain why there have been a few reports of bad images recently. (The reports are generally about failed behaviour but we trace it to bad images after some diagnostics.)
1 Like
Ok , I reflushed the image and tried it on an rpi4. Same problem… I guess since md5 was correct there is no need to download it again… Can it be a problem with the image?
Hi @zynthianers!
I found the problem with the latest stable when booting with HDMI display. A “typo” in the auto-config script is preventing to detect the HDMI configuration and it defaults to V4 settings.
I’m fixing it and will update the image ASAP.
Regards,
1 Like
I’m generating a SD image with the latest hot-fixes on stable and hope to release it in the next few hours.
Regards,
1 Like
Hi @zynthianers!
I just uploaded a patched stable SD-image that fixes the “first-boot” issues and also the webconf login authentication error.
https://os.zynthian.org/2023-11-02-zynthianos-stable-2308.zip
Those having a working stable don’t need to re-burn, simply update for getting the webconf fixes.
BTW, i’ve released a testing SD-image:
https://os.zynthian.org/test/2023-11-02-zynthianos-testing-2311.zip
Enjoy!
6 Likes
It is perhaps an experimental/interlocutory stage of the coming 64 bit stable… ? 
1 Like
Do you mean the 64 bit testing image?
https://os.zynthian.org/test/2023-08-22-zynthianos-bullseye-arm64-testing-2308.zip
It’s a work in progress and still needs some extra work. Also, we will jump to bookworm.
But you can try it if you like to be in the cutting edge. It’s 95% functional and “quite stable”, indeed! 
Regards!
4 Likes
It works really well on my minimal Zynthian. All that’s missing is the ability to calibrate the touchscreen (which however works perfectly) and the Zynthian logo at startup… But I’ve been using it for several weeks without any problems… Well done
Long time lurker, first time commenter
I feel like (maybe?) I’m experiencing something similar.
I flashed the last stable zip six times tonight. Would get to zynthian screen on my touchscreen and rasp pi 4, would change settings in zynthian.local, and nothing…in fact after my last attempt i left it plugged in and it’s sitting theref displaying “configuring your zynthian”… 6 hours i’ve been at this :') my partner thinks i’m on drugs.
I admit I know little to nothing about typing…command…prompts? or whatever the computer black magic most of you can do is called…but I was able to get to the terminal (also mystical to me) and i guess made it so i can no longer access zynthian.local…
I saw briefly something along the lines of “refusing to connect”
it’s super late and i can’t stomach using etcher another time tonight, so i figure i’ll re-do it in the morning and ask what I can do when i do and am able to access the terminal again…
I’m in shreds, man. Would anyone be able to help? I have been afraid to ask because i’m not super familiar with your morse code (I mean this in the most endearing way)
Only to confirm, could you confirm the “file name” of the image you are using? it should be this one:
https://os.zynthian.org/2023-11-02-zynthianos-stable-2308.zip
Please, note the revision date “2023-11-02”
Also, perhaps you could try the testing version …
https://os.zynthian.org/test/2023-11-02-zynthianos-testing-2311.zip
Regards,
1 Like
Yes it was actually the 2308. I don’t know if what i’ve been reading is outdated, but i vaguely remember someone commenting that a faulty sound card (I’m only using what the rasp pi 4b has on deck) could be linked to the software crashing? I bought a rasppi audio dac hat along with a smaller micro-sd card in hopes that they would help. I don’t know if this was an impulsive buy, as i should’ve come here first. Time will tell D:
I am so grateful for your timely response. Thank you for your help, I will definitely try the testing version right now.
I’ve been wanting to use this for so long, the suspense is killing me. Thank you 
I must say as a long time lurker, I am very excited to see that my first response was from you @jofemodo 
I’m just one in the crowd
I tested my sd/pi with a different touch display, it boots but is stuck on the mixer, and touchscreen doesn’t work…switched back to this display that I want to break in half and it’s pure white screen, until I re-burn the sd and start over with it stuck on the configuration screen…when I turn it off, same thing, white screen then the cycle starts again.
weird to me that this isn’t happening with my other display, the other display at least gets me to a mixer…? If only I could use it…I have no idea what I’m doing wrong ):
the display that’s working is through hdmi the one that isn’t working is placed on via pins.
If I got the kit, this wouldn’t be as much of an issue as it is now right?
Hi @MakeSpeedNotwar !
-
Regarding the SPI display, please, could you give the details about the display brand & model? Did you try to configure it?
-
Regarding the HDMI display, you need to connect the “touch” part by USB. The HDMI connection alone don’t carry touch info. Again, details are important. Brand, model, some pictures, etc.
Did you try to reach the webconf for configuring your display(s)?
Regards,
yes, so with the touch display (I use for accessing virtual instruments on my mac mini for preforming) accessing zynth.local works as you’d hope. the only problem is touch. I think this might have to do with having to power it seperately. I figure it’s not able to be used.
So the original screen i’ve been having problems with is
https://www.amazon.com/dp/B083C12N57?psc=1&ref=ppx_yo2ov_dt_b_product_details
this is the one that turns white after every power-off, etc. I’m able to use local maybe once or twice before it becomes unresponsive and just on loading screen.
It shows me where to download the drivers to burn onto an sd, but would it be possible to burn the drivers then zynthian? I understand i lack fundamental knowledge on how this works, and I’m wanting nothing but to actually understand and try to figure it out.
and this is the one that I have to power/actually will load the interface but i can’t find a way to use the touchscreen. it’s all usbc (and too powerful to be powered by rasppi
https://www.amazon.com/dp/B08D1MLTQD?psc=1&ref=ppx_yo2ov_dt_b_product_details
I’d rather not use this if i don’t have to.
thank you so much for listening to me I really appreciate your help thus far, and i understand if it’s too much of a pain to try to put into layman’s terms.
I found this article about displays and interfaces very helpful:
1 Like