January 2017 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] 4.10-rc2 kernel testing
by Andreas Färber 05 Jan '17

05 Jan '17

Hello, After the 4.9-rcX kernel troubles, Kernel:HEAD v4.10-rc2 is looking good so far: (+ = boots successfully, - = doesn't boot successfully) armv6hl: + Raspberry Pi Zero armv7hl: + BeagleBone Black (kernel-default) + Cubietruck (kernel-lpae) + Jetson TK1 (kernel-lpae) + Raspberry Pi 2 (kernel-lpae) aarch64: - Pine64 (new in 4.10, using U-Boot's dtb for lack of dtb-allwinner) + Raspberry Pi 3 Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] cubox-i wireless setup
by Alessio Adamo 04 Jan '17

04 Jan '17

Hi guys, I have tumbleweed running on my cubox-i pro, and the wireless card is working. But I set it up when 13.2 just came up (to give you an idea) and now, on a fresh Tumbleweed or Leap 42.2 I don't remember anymore how I did it. The system doesn't seem to recognize the card. In yast when I add the wireless interface, I'm not able to select a pertaining kernel module, nor I'm able to scan the network. Any hint on how I should proceed? Many thanks. Regards Alessio -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

[opensuse-arm] Cross compiling ARM on x64
by Roger Oberholtzer 04 Jan '17

04 Jan '17

I am currently building software for a Raspberry using a Raspberry as the build computer. It works surprisingly well. Nonetheless, I am considering setting up doing cross compiling on an intel x86 (non ARM) computer. I guess installing cross compilers and such tools from OBS is okay. I already do this for doing Windows (32- and 64-bit) cross compiling. I also install from OBS the various libraries needed for the Windows cross compile. They are nicely put in /usr/i686-w64-mingw32/sys-root/mingw or /usr/x86_64-w64-mingw32/sys-root/mingw. They are not installed in the Linux /usr/bin/ or /usr/lib/ trees. Unfortunately, I am guessing this would not be the case for ARM packages (e.g., libjpeg8-8.1.2-40.2.aarch64 and libjpeg8-devel-8.1.2-40.2.aarch64). They would be installed in the /usr/bin/ or /usr/lib/ trees, as that's where they are expected to be. Which is perhaps not what I want on a cross-compiling system Am I missing some brilliant thing to get these types of things installed in some other tree? Or is cross-compiling going to be more problematic than maintaining a Raspberry to do this work? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 18

[opensuse-arm] SUSE or openSUSE images for x86
by Jimmy PIERRE 03 Jan '17

03 Jan '17

Greetings, Somewhere around 22nd Dec 2016, RaspberryPi.org updated an image of Debian for x86. This of course can lure people to endorse Raspbian/Debian when their old PC dies for real. I am wondering, do SUSE or openSUSE have any project to cater for x86? This will help putting one foot in the door, figurately speaking and pave the way to x64 versions Tumbleweed, SUSE, Leap ... Just my two cents... May I take this opportunity to wish you a Happy New Year 2017, full of fun and above all health! Jimmy nui.fr -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] Raspi 3B: doesn't start correctly
by Edgar Dombrowski 02 Jan '17

02 Jan '17

Hallo, Raspbi-friends. I have download last sunday 2 Versions, but after installation te boot-activity stopped. 1. Version: openSUSE-Tumblewéed-ARM-E20-raspberrypi3-2ß16-11-23-Build4.21.raw.gz 2. Installation on a 16GB-SD-stick /dev/sdc1 200 MB /dev/sdc2 ext3 207 MB BOOT /dev/sdc3 btrfs 4,38 GB ROOT 3. When starting I get the following messages Menue: openSuse (vmx) (early messages not copied, to fast) FailSafe openSuse (vmx) Booting OpenSUSE.vmx (no text) loading linux.vmx loading initrd.vmx ( approx. 10 lines no text) EFI stub: Booting Linux Kernel EFI stub: UEFI Secure Boot is enabled EFI stub: Using DTB from configuration table EFI stub:Exiting boot servies and installing address map.... Thank you for any advice Regards Edgar Dombrowski, DJ3PU, Munich -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Raspberry Pi2 images not booting
by Knurpht - Gertjan Lettink 02 Jan '17

02 Jan '17

Hi, It looks like none of the current TW images for Rpi2 are working. Am I correct or struck by the coincedence of three faulty SD cards that do work with other distros? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] Tumbleweed JeOS btrfs issue: dtb missing
by Andreas Färber 02 Jan '17

02 Jan '17

Hi, Retesting my JeOS-hikey image with U-Boot I noticed that with the recent btrfs enablement the dtb folder is on the wrong partition (btrfs instead of ext3) and thus cannot be loaded by U-Boot. I am assuming this is also the reason why people reported recent rpi3 images as non-working! Could one of you guys who made that change please look into why this is misbehaving or revert that change? Thanks, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1