Hi Dieter,

Copying the SUSE image into that and booting it, also fabulously worked. Even updating that 13.1 image to the latest state was possible.

We have exynos 4 support disabled in the tumbleweed kernel, thats why. if you have patience to retest an image, I can branch a kernel with exynos4 enabled intot he contrib and we'll continue from there. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 09/02/16 10:00, Dieter Thalmayr wrote:

Hey, why not?

Sounds tempting. I'm kind of disappointed that ubuntu runs on all this stuff, and my SUSE seems always to lag behind.

So let's take it as a kind of sporty initiative. And expect stupid questions ;)

Helau

Dieter

On Tue, 9 Feb 2016 10:20:57 +0100, Dirk Müller wrote:

...

Hi Dieter,

...

Copying the SUSE image into that and booting it, also fabulously worked. Even updating that 13.1 image to the latest state was possible.

We have exynos 4 support disabled in the tumbleweed kernel, thats why. if you have patience to retest an image, I can branch a kernel with exynos4 enabled intot he contrib and we'll continue from there.

Greetings, Dirk

openSUSE never took ARM to be a serious platform until the Raspberry Pi arrived on the scene. I had asked a long way back and was told that Intel Atom would obsolete ARM - I quoted that email back to the author on this list when openSUSE woke up to the fact that ARM wasn't going away any decade soon. The first implementation on ODROID-X eventually crashed irretrievably and there was nowhere else to go but to Ubuntu. I am definitely not fond of Ubuntu, I run openSUSE on 4 x86_64 boxes - my preferred choice, Kubuntu on a couple more to help Ubuntu users and Ubuntu ARM on ODROID-X/-U3/-C1, Parallella-16, Raspbian on Raspberry Pi 2 and it looks like having to go to Ubuntu again for PINE A64+ and ODROID-C2. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Ey, calm down. Do we want to play the u3, or should I go on doing ubuntu? If you want to try the u3 with me, I'd be honored. As Ex-SUSE employee I'm well used to that quasi-religious "who was able to see better into the future"-approach, but I think this does not help at all. With the u3, we are well behind the time, since hardkernel already stopped it and sells its c1's, xu3 and xu4's now. I've one of these xu4's too, and no suse image for it, if you want to know. Ubuntu runs fine on it, and I use it as a multimedia player, but the frequent loud ventilator sucks. The u3 was much more silent, and it ran nice and fast. Does anyone of you still have one, or am I the only one? Greetings and Helau Dieter On Tue, 9 Feb 2016 15:30:02 +0100, Andreas Färber wrote:

Am 09.02.2016 um 14:29 schrieb Sid Boyce:

...

openSUSE never took ARM to be a serious platform until the Raspberry Pi arrived on the scene.

Bullshit. The Raspberry Pi had nothing to do with our ARM port, it went on sale half a year later and was incompatible with our ARMv7 packages. It was rather people with Beagleboard, Pandaboard and Toshiba AC100 and the prospect of ARM based servers that inspired both hobbyists and SUSE engineers at openSUSE Conference 2011 and the following SUSE Hackweek.

Can't comment on the previous ARMv5 port - I believe that evolved around the Seagate DockStar.

ARM board support in openSUSE has always been driven by people owning the boards or by companies donating some to be enabled and to power OBS. Don't broadly blame "openSUSE" or some Intel fan-boy, it's individuals.

Regards, Andreas

-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

-- magnum opus GmbH Tel: 08441/ 7978 107 Eichendorffstr. 19a Fax: 08441/ 7977 114 D-85276 Pfaffenhofen/Ilm http://www.magnum-opus.de GF: Dieter Thalmayr, Dieter Jäger RG: Neuburg / Donau · HRB 91.238 Ust-IdNr DE227355001 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi Michael,

I have to say as someone who is new to opensuse-arm but a long time user/admin of opensuse that the -arm channels seem a bit chaotic and hostile and totally void of useful info and what it sounds like is being promoted to me is that if you can't figure it out on your own, do not bother asking,

We're trying to fix that perception, please be patient :)

Thanks to everyone who has tried to help, unfortunately after a year or so of trying to get opensuse working on my Pi, I am no further along than I was a year ago.

I"ll try to take a look at the graphical images, but I currently do not have any HDMI capable device so it'll take a bit. if you have any information that would help digging down what is going on that would help me already getting started. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 09/02/2016 10:20, Dirk Müller a écrit :

Hi Dieter,

...

Copying the SUSE image into that and booting it, also fabulously worked. Even updating that 13.1 image to the latest state was possible. We have exynos 4 support disabled in the tumbleweed kernel, thats why. if you have patience to retest an image, I can branch a kernel with exynos4 enabled intot he contrib and we'll continue from there.

Indeed. Why exynos4 was disabled? I cannot remember. Maybe it was when we had an exynos flavour? Guillaume

Greetings, Dirk

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi there, finally found the time to check I used an image called openSUSE-Tumbleweed-ARM-JeOS-odroid.armv7l-20160303.0.0-Build9.1.raw Ethernet wasn't connected, but it looks as if the kernel doesn't support the exynos again.. U-Boot 2016.03-rc2 (Feb 26 2016 - 21:53:43 +0000) CPU: Exynos4412 @ 1 GHz Model: Odroid based on Exynos4412 Board: Odroid based on Exynos4412 Type: u3 DRAM: 2 GiB LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling LDO21@TFLASH_2.8V: set 2800000 uV; enabling MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 *** Warning - bad CRC, using default environment Net: No ethernet found. Hit any key to stop autoboot: 0 2732 bytes read in 136 ms (19.5 KiB/s) ## Executing script at 42000000 switch to partitions #0, OK mmc0 is current device 7286136 bytes read in 4429 ms (1.6 MiB/s) 32449885 bytes read in 16362 ms (1.9 MiB/s) 53476 bytes read in 424 ms (123 KiB/s) Kernel image @ 0x40007fc0 [ 0x000000 - 0x6f2d78 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 32449821 Bytes = 30.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 40800000 Booting using the fdt blob at 0x40800000 Using Device Tree in place at 40800000, end 408100e3 Starting kernel ... Greetings Dieter On Thu, 25 Feb 2016 13:51:51 +0100, Guillaume Gardet wrote:

Hi Dieter,

Could you try the latest image from:

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro...

Guillaume

Le 29/01/2016 14:47, Dieter Thalmayr a écrit :

...

Hi there,

Guillaume Gardet helped me to get an odroid u3 running with a SUSE anything younger than a 12.3. Actually, we used an image that can be found at

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro...

That image is "factory".

We had many issues with the uboot bootloader, but after months and close to one dozen tries the bootloader boots the kernel.

But then: ----snip ---- U-Boot 2016.01 (Jan 25 2016 - 22:47:58 +0000)

CPU: Exynos4412 @ 1 GHz Model: Odroid based on Exynos4412 Board: Odroid based on Exynos4412 Type: u3 DRAM: 2 GiB LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling LDO21@TFLASH_2.8V: set 2800000 uV; enabling MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 *** Warning - bad CRC, using default environment

Net: No ethernet found. Hit any key to stop autoboot: 0 2721 bytes read in 135 ms (19.5 KiB/s) ## Executing script at 42000000 autoboot=if test -e mmc 0 boot.scr; then; run boot_script; elif test -e mmc 0 I; baudrate=115200 boardname=odroidu3 boot_fit=setenv kerneladdr 0x42000000;setenv kernelname Image.itb;run loadkerne} boot_script=run loadbootscript;source ${scriptaddr} boot_uimg=setenv kerneladdr 0x40007FC0;setenv kernelname uImage;run check_dtb;r; boot_zimg=setenv kerneladdr 0x40007FC0;setenv kernelname zImage;run check_dtb;r; bootargs=Please use defined boot bootcmd=run autoboot bootdelay=0 check_dtb=if run loaddtb; then setenv fdt_addr ${fdtaddr};else setenv fdt_addr;; check_ramdisk=if run loadinitrd; then setenv initrd_addr ${initrdaddr};else set; console=console=ttySAC1,115200n8 consoleoff=set console console=ram; save; reset consoleon=set console console=ttySAC1,115200n8; save; reset dfu_alt_info=Please reset the board dfu_alt_system=uImage fat 0 1;zImage fat 0 1;Image.itb fat 0 1;uInitrd fat 0 1;2 fdtaddr=40800000 fdtcontroladdr=bae47f70 fdtfile=exynos4412-odroidu3.dtb fileaddr=42000000 filesize=aa1 initrdaddr=42000000 initrdname=uInitrd kernel_args=setenv bootargs root=/dev/mmcblk${mmcrootdev}p${mmcrootpart} rootwa} loadbootscript=load mmc ${mmcbootdev}:${mmcbootpart} ${scriptaddr} boot.scr loaddtb=load mmc ${mmcbootdev}:${mmcbootpart} ${fdtaddr} ${fdtfile} loadinitrd=load mmc ${mmcbootdev}:${mmcbootpart} ${initrdaddr} ${initrdname} loadkernel=load mmc ${mmcbootdev}:${mmcbootpart} ${kerneladdr} ${kernelname} mmcbootdev=0 mmcbootpart=1 mmcrootdev=0 mmcrootpart=2 scriptaddr=0x42000000 soc_id=4412 soc_rev=2.0

Environment size: 2090/4092 bytes switch to partitions #0, OK mmc0 is current device 7420680 bytes read in 4206 ms (1.7 MiB/s) 68337422 bytes read in 31408 ms (2.1 MiB/s) 53476 bytes read in 464 ms (112.3 KiB/s) Kernel image @ 0x40007fc0 [ 0x000000 - 0x713b08 ] ## Loading init Ramdisk from Legacy Image at 44007fc0 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 68337358 Bytes = 65.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43f07fc0 Booting using the fdt blob at 0x43f07fc0 Using Device Tree in place at 43f07fc0, end 43f180a3

Starting kernel ...

--- snap ---

and afterwards only the sad sound of the ventilator.

Does anybody have an idea what goes wrong? What can I do to get more information

Plus, I would be very interested in building an image on my own. Is there somewhere a howto that can help me with the first steps?

Although I have to admit that I am only a high-hearted amateur if it comes down to real technics..

Greetings

Dieter

-- magnum opus GmbH Tel: 08441/ 7978 107 Eichendorffstr. 19a Fax: 08441/ 7977 114 D-85276 Pfaffenhofen/Ilm http://www.magnum-opus.de GF: Dieter Thalmayr, Dieter Jäger RG: Neuburg / Donau · HRB 91.238 Ust-IdNr DE227355001 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org