I’m into the second day of using the Oram stable release. I have fixed yesterday’s problem of ‘Enter’ on QWERTY keyboard not working by re-burning the SD and starting over. Today I was experimenting switching between my on-board pHat DAC and an external Roland Go:Mixer and had an issue - possibly due to me unplugging the Go:Mixer and rebooting before setting the soundcard back to Hifiberry light on WebConf. Anyway, after several reboots before Zynth would work again, I found that the single ethernet cable connection no longer worked. I have tried another ethernet cable - so it looks like I’ll be doing another reburn. This isn’t too hard for me to do just now because I’ve got a space cleared for taking my Smartipi screen case apart. I don’t want to do this too often, though, because the first time I assembled it - the ribbon cable connector clamp on the screen broke meaning that the cable is only held in place by luck - and that amount of luck can’t last forever.
There is a good chance the problems I have been having are my own fault by using a battery to power my Zynth running the gauntlet of low power issues in favour of not being connected to the mains while I play with Zynth on the settee with the TV on. In which case there won’t be anything anyone can do to fix my woes other than to tell me to mend my ways but I thought I’d let you know anyway,
I am keen to get ethernet connectivity going because, although Wifi worked well to start with, it seems to have become less reliable and ethernet has, until now, always been my surefire method of connection. I am suspicious of my router being the problem I have with my wifi connection. And/or low voltage issues.
I know it isn’t recommended but I’d love to know if there is a battery pack available with enough oomph to power a pi4 running Oram for a reasonable amount of time…
Edit: 22 hours (and many probably unnecessary system rebuilds) later - it looks like I should have simply set my browser to the .local domain listed under ‘Network Info’ all along.
Loss of wired network is very unusual. How are you testing this? Are you using an IP address or hostname to connect? What does the network info show from admin menu?
BYW you should turn off the TV and take your portable rig to a more inspirational location, like a wood or a stream. Find the music within your real self!
Note the telly is off. My muse has my undivided attention (I once went to a John Cooper Clarke gig where he had a telly on on stage. He kept stopping and watching it for a while. Not the best gig ever :-))
That generally means there is data present at the socket at last. . .
There is a audio USB reload branch out there somewhere, but I don’t think it got burned into vangelis or indeed oram. Without that present it is likely that hot plugging audio connections on USB is going to confuse issues a little.
Can you see any indication on start up of an Internet address? can you ping on the network and does the Pi show up in the Router list? There is always the possibility of IPv6 connection which complicate behaviour like this.
Basicaly a Pi will sulk if it doesn’t get network access at start up and have you selected wifi or is it trying to set up it’s own wifi router ? Lot’s to consider.
SSD’s have a nasty habit of getting corrupted precisely when they are doing first updates and that can involve downloads so…
I’e learned to ensure the SSD is easily accessible on zynths, indeed it was a issue with the first release hardware. You can get extenders that would allow you to mount the SSD in slightly more convenient places. It can help in development. It’s tempting to soldier on with an SSD and see if you can spring it back into life with a judicious update but as you lack network connection it’s worth having a known good ssd to get back to for the inevitable sanity checks that this sort of failure involves. Try, if you can to be gentle in shutdowns if possible.
Do you know off hand what the good windows console/ new window console thingy whatever it is called (I have it set up I’m sure) commands are? I used to know what some of the old timey equivalents were on a good day 20 years ago…
I did a reboot of my laptop to see if that helped. Interestingly Zynthian reverted to a completely powered-down state when I did this. The ethernet cable was plugged in. Also, I have now got (what I assume is - because I have no idea why else I would have a wired usb C to mains adaptor) the official power supply plugged in. Sadly there was still now ethernet when I unplugged it and plugged it in again to let it power up.
I’m thinking that my woes are down to some sort of static ip address problem. I have taken the zynth apart again and put in a fresh installation of the latest bookworm and still the pc to pi connection via an ethernet cable wouldn’t work. The pi will, however, get itself an IP and talk to the internet via ethernet if I plug it into my LAN. Silly pi. At least it seems to work… It’s just getting it to do what I want it to do is the problem :-)))
Bookworm is engrossed in a massive and very slow update at the moment. I’m reluctant to interrupt it even though I’m going to whip it out and put yet another fresh install of Zynthian in as soon as it’s done. I’m assuming it’s possible to set up a static IP address on Zynthian? Has anyone else done this for a direct one cable connection? I guess I will try it out on Bookworm before I take that SD card out.
