Op zaterdag 6 februari 2016 22:30:15 schreef Alexander Graf:

On 02/06/2016 07:41 PM, Jimmy PIERRE wrote:

...

Please advise which one you want checked first, then second etc.

I think the most efficient thing to test would be the XFCE image. If that works, all is well. If it fails, try the JeOS image and see if that breaks too. If JeOS works and XFCE fails, then the breakage is X related.

Whether the repository is the correct one, I will defer to Dirk. Does the current image work?

The JeOS image is OK. You have to be patient for a few minutes before you can see it works. The repository is the intended one for a working image. The image gets replaced by a working one from ...RapberryPi2:/Staging/image -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op zondag 7 februari 2016 13:08:35 schreef Jimmy PIERRE:

On 7 February 2016 at 00:00, Freek de Kruijf <freek@opensuse.org> wrote:

...

Op zaterdag 6 februari 2016 22:30:15 schreef Alexander Graf:

...

On 02/06/2016 07:41 PM, Jimmy PIERRE wrote:

...

Please advise which one you want checked first, then second etc.

I think the most efficient thing to test would be the XFCE image. If that works, all is well. If it fails, try the JeOS image and see if that breaks too. If JeOS works and XFCE fails, then the breakage is X related.

Whether the repository is the correct one, I will defer to Dirk. Does the current image work?

The JeOS image is OK. You have to be patient for a few minutes before you can see it works. The repository is the intended one for a working image. The image gets replaced by a working one from ...RapberryPi2:/Staging/image Hi!

Sadly XFCE would not boot despite several attempts and VGA cables. I have ordered an ACER 24" monitor with HDMI and will retest :(

Cheers, J

Tested the XFCE version also with a HDMI display attached and it works. See attached picture. I accessed the system via ssh. Also inserted a USB mouse and I was able to move the pointer on the screen. Did not have a USB keyboard to test. Had some trouble to get an outside connection; inside my network was OK. Problem was /etc/resolv.conf had to replace it by /etc/resolv.conf.??? -- fr.gr. member openSUSE Freek de Kruijf

Op zondag 7 februari 2016 10:45:23 schreef Michael Emory Cerquoni:

I actually get this far as well, but as soon as I log in it freezes and never continues.

I did not try to log in. No keyboard attached.

Been sitting at this screen for 20 minutes http://nebadon2025.com/pi2/raspberrypi2_tumbleweed_xfce_001.jpg then it eventually goes black and nothing can wake it up again at that point.

Apparently there is power safe facility that blanks the screen. I have seen it too with the JeOS version. I used Build372.1 for the JeOS version and Build374.1 for te XFCE version.

also what resolution are you running in here, is it the native maximum resolution your monitor supports? Like i said previously the only way I have been able to successfully log in is to replace raspberrypi-userland packages with Mesa-libEGL* packages

I have tested with a Dell 1280x1024 DVI-D using HDMI Adapter, a Dell 1920x1080 DVI-D with Adapters, a Gateway 1440x900 DVI-D with adapter and a Asus VG248QE 1080p 144hz HDMI screen, they all show 800x480 no matter what i set in the config.txt or even if i craft a xorg.conf trying to force another resolution.

I can't say what resolution the screen was written. It is my Full HD TV with several HDMI ports. You may get the screen back via ssh and "systemctl restart display-manager". -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

I have captured the following journal log from my pi2 running the latest available image with raspberrypi-userland packages installed, I am using KDM to log into LXDE, but so far I have the same experience on everything I have tried. https://gist.github.com/nebadon2025/6c30f041b50b90d2f7fc in addition to this the console and DM/DE are always stuck in 800x480 resolution, and it seems as if the Config.txt is being ignored, I have tried changing many things with no discernible results. I do not know how useful this information is but at the moment best I could get, if there is some way I can enhance this data or provide anything more please do let me know. -- Michael Emory Cerquoni -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi Jimmy,

Chich primarily image that you want tested please?

depends on what you want to achieve. the JeOS image is minimal text only, ideal for small remote servers that are only used for SSH. XFCE/LXQT are graphical images, but I have personally not tested them as I don't own a HDMI capable screen. The *packages file that you mentioned in the screenshot are just debugging files. they list the package sthat are included in the image. the "*.armv7.raw.xz" files are actually symlinks and the Buildservice is too stupid to show that to you. they always link to the latest built image, e.g. Build276.1.raw.xz in your case. You can use that to have a static download link. so with other words both downloads end up downloading the same image.

Monitor arrived and old image just shows a blinking cursor on top left, *but* before there was some activity on the screen :)

Yeah, I saw that as well. There is something wrong with the new kernel that causes it to fail the disk resize, so you end in a initrd. I've added a workaround to kiwi, hopefully this fixes it. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org