The image have been written to the memory card on a Win10 using Etcher.
When the RPi4 boots the network interface show link (both green and orange), but it doesn’t get an IP-address.
It’s connected to a Cisco network (Router and switch) and the interface on the switch don’t register any mac-addresss (sh mac ad int g0/1), but the interface says connected (sh int status), and the routers DHCP doesn’t give an IP-address (sh ip dhcp bin); properly because it never receives a request (DHCP discover).
If I configure a static IP-address using Yast, the network is very slow and doesn’t respond all the time. Pinging the RPi4 I only get a reply around 1 out 10. SSH is impossible. I do see a mac-address on the Cisco switch though.
Installing the TWeed with Gnome works, but seems too much for the RPi4, Raspbian works flawlessly - Tweed JeOS doesn’t work.
The network works perfectly with all my other devices.
Anyone tried this or know what could be causing it?
Although there probably is nothing wrong with your image,
It’s been my experience writing other RPi images that the only way to guarantee a 100% working image is to follow the instructions and use xzcat as described
If you don’t have access to an openSUSE running on a physical machine, you can write from an openSUSE Guest running in some virtualization. Although I described how to do this in a VMware Guest (VMware Player is free), if you understand the principle of what is described it should be possible to use any virtualization including VBox.
What do you mean by TW with Gnome is “too much?”
Although I haven’t installed on a RPi4, on a RPi Zero which has much fewer resources it runs although it’s not my favorite. XFCE and LXQt are lighter DE alternatives which can be tried.
If you think networking is working with the Gnome image,
Then assuming the JeOS was built properly, I’d assume there shouldn’t be a networking problem (I assume that whoever built the JeOS would know how to remove only what wasn’t necessary and the basic networking components of both images would be the same).
Malcolm’s link only suggests a problem with using a certificate to authenticate SSH clients.
There isn’t anything else that’s related mentioned on the RPi4 HCL
There may be other issues not mentioned, but it’s likely that basic networking should work and SSH username/password also likely should work.
As I described, unless you burn your image following the directions in the above RPi4 HCL, your image may be faulty.
You might even find that your Gnome Desktop works better (I’ve been seeing reviews that suggest the RPi4 supports full Desktops like Gnome well), but if that proves that the case you should try one of the lighter Desktops (recommend XFCE if you like Gnome).