Hi Jofemodo,
I thought in case of no WIFI the AP would be activated automatically…?
There is no zynthian AP on my Android phone as it used to be before…
Cheers,
Maarten
Yes. The new display version from what i was told is a version 2.1. The difference between the old and new versions is: the DSI0 network is changed to connect to the DSI1 network. Improved the problem that some cameras cannot be used when using the screen of some Raspberry Pi systems
It is kind of a rythmical exersize… typing one (1) character in the terminal each screen alternation… 
Cheers Maarten
I managed, 
Happy again…
But still… defining the SSID and password in the beginning would be great. I cannot imagine that I am the only one with this desire…?
Cheers,
Maarten
1 Like
Unfortunately, no. Zynthian doesn’t boot that far, that it would connect to my WiFi.
I tried to find anything interesting on the card’s rootfs partition, checking files that got a new timestamp with the backup, but didn’t come anywhere helpful…
I will reflash now and se if it’s different…since jofemodo fixed sth.
Let’s see:
[Edit]
Yes it worked now! 
I reflashed, updated and Zynthian happily rebooted this time!
Well, my story is less fortunate. I downloaded the RC2 release, burned it on sd with the raspberry pi imager. Placed it in the RPi5 and powered it. Got some boot messages and then the screen went black and the RPi gave 4 slow blinks and 5 fast ones, which indicates it now has a fatal firmware error.
Tried to rewrite the EEPROM with the bootloader, but this did not change it’s status unfortunately.
Power source was standard. Attached were a usb mouse, a network cable, an arduino and a tft monitor.
I guess my Zynthian adventures are on hold for a while.
Does this mean you’re still getting “4 slow blinks and 5 fast ones” even after running the recovery process on the eeprom?
I wonder if the serial port between the mini-hdmi connectors would give a more informative error message.
Yes, the 4 slow 5 fast blinks persist after flashing with the EEPROM bootloader, which I suppose does not bode well.
I agree, but feel you should not give up hope just yet.
When you say “standard” what do you mean? Is it an official RPi5 (or at less RPi4) PSU? If it’s not, you should suspect of this as the most probable cause of trouble.
I would repeat the process but disconnecting the network and the arduino. If everything goes well, you could connect them later.
Good luck!
It is an official PSU, and I did remove all peripherals, including the Hifiberry, repeated to flash the bootloader. No change.
I will see how far I can get tomorrow.
- You could try with a fresh Raspberry Pi OS.
- You could try to burn your SD using a different program. I never tested with the raspberry pi imager
Regards
Pfew! The RPi5 is alive again. Tried booting while powered through usb hub, no success. Tried booting Hifiberry OS, no success. Then, for some fortuitous reason, I burned a fresh bootloader image to SD from the Raspberry Pi Imager repository, and that, thank heavens, did the trick.
Now I am going to relax for a bit.
2 Likes
I’ve never used anything else, and I’ve found it pretty reliable especially for burning for other older versions of the Pi.
1 Like
Had you tried that before? It would be my first advise if a RPi5 fails to boot.
Well I did have a bootloader image on my computer still, which had worked before, so I figured it would function as intended, but when burned on SD and flashed on the RPi it made no difference at all.
So yes, it was in fact the first thing I did as well, but I guess the lesson learned here is to use the most current bootloader image available if you can.
1 Like
Hi All,
I get every 10 sec the message:
‘Sep 18 06:30:09 zynthian dhcpcd[818]: wlan0: requesting DHCPv6 information’
Something not configured OK? Or…
Cheers,
Maarten
I added:
noipv6rs
noipv6
to the file: /etc/dhcpcd.conf
It stopped the IP6 massaging… But I am not sure …
Cheers,
Maarten
Let me check it. Perhaps i should add it to the default config.
Thanks!
Hi All,
A new item/bug?
When I assign (in the zynthian interface, so not in the MOD web browser) the bypass of an lv2 effect (MOD-UI) to a controller , I cannot SAVE the snapshot… 
(I will make a bug report… with logging text)
Help…
Cheers,
Maarten