March 2016 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] grub2 in JeOS
by Matwey V. Kornilov 11 Mar '16

11 Mar '16

Hi, I've just enjoyed grub2 in JeOS. It works very well. Alexander, many thanks. -- 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] RPi2, Tumbleweed and "official" 7" RPi touchscreen
by Michael Emory Cerquoni 11 Mar '16

11 Mar '16

I have been trying for a year or so to get this working correctly with absolutely zero luck, and so far have not found any way to get the GPU working correctly for the opensuse-arm Raspberry Pi2 images, it uses an ancient kernel (3.18) and no one seems interested in updating and making sure things work properly, i would suggest if you really need this you switch to Raspbian or Ubuntu Mate, you will have considerably better luck and much better community support, I hate to sound negative and really I am not happy about having to recommend you use a different operating system, but chances are you will not be able to get opensuse working very well, there seems to be very little interest in making this hardware work correctly on opensuse. -- Michael Emory Cerquoni -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 30

[opensuse-arm] 'Factory-Contrib-RPi' unknown key '16C5D54F3F546F34'
by Michael Ströder 10 Mar '16

10 Mar '16

HI! It would be nice if repo changes and thus key changes would be announced here or on other lists. I currently get: Retrieving repository 'Factory-Contrib-RPi' metadata -------------------------------------------------------------------------------------------------------------------[\] File 'repomd.xml' from repository 'Factory-Contrib-RPi' is signed with an unknown key '16C5D54F3F546F34'. Continue? [yes/no] (no): 'Factory-Contrib-RPi' points to: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… Ciao, Michael.

2 1

Re: [opensuse-arm] Leap 42.2 plans?
by Ludwig Nussel 10 Mar '16

10 Mar '16

Dirk Müller wrote: > Yes of course. It would be preferably bootstrapped in the main project, but > if that's again not possible, then please create a ports subproject and add > me as maintainer. Ok, great! I'm quite sure we'd both regret adding it as main architecure at this point though so I'd go for the ports approach again :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, 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

2 2

Re: [opensuse-arm] RPi2, Tumbleweed and "official" 7" RPi touchscreen
by Michael Emory Cerquoni 09 Mar '16

09 Mar '16

ariel, I agree its completely unstable, I have yet to go more than 24 hours without it completely freezing up and need a power cycle. I have tried dozens of images over the last year and while it works better now than it ever has, its still far from stable on any level. -- Michael Emory Cerquoni -- 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] Cross-distribution ARM meetings at Linaro connect this weel
by Riku Voipio 07 Mar '16

07 Mar '16

Hi, We have a few sessions at this Linaro connect that could be in interest of Linux distributions working on Arm/Linux: Tuesday 14.00 Bangkok time: (07.00 UTC): https://bkk16.pathable.com/meetings/372827 BKK16-212: What's broken on ARM64? Thursday 10.10 Bangkok time: (03.00 UTC): https://bkk16.pathable.com/meetings/372890 BKK16-402: Cross distro BoF Friday 10.10 Bangkok time: (03.00 UTC): https://bkk16.pathable.com/meetings/372923 BKK16-501: Kernel Consolidation and Other Short Stories Talks are being live-streamed (thou there were problems today..) and recorded in case time happens to be inconvenient in your timezones. If you have anything specific in your mind, feel free to reply to this mail to cross-distribution list, and I'll get it added to the agenda slides. Cheers, Riku -- 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] perl-Bootloader still needed?
by Michael Ströder 07 Mar '16

07 Mar '16

HI! I'd like to completely get rid of perl on my systems. Hence my question: Is package perl-Bootloader still needed on raspberry pi systems for kernel updates or similar? Ciao, Michael.

2 2

[opensuse-arm] opensuse on odroid u3?
by Dieter Thalmayr 04 Mar '16

04 Mar '16

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:/Odr… 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(a)VDDQ_EMMC_1.8V: set 1800000 uV; enabling LDO22(a)VDDQ_EMMC_2.8V: set 2800000 uV; enabling LDO21(a)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(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

8 14

[opensuse-arm] Raspberry Pi 1 downstream strange behavior
by Guillaume Gardet 04 Mar '16

04 Mar '16

Hi, On the downstream image for raspberry pi 1, I have a very strange error. First boot is ok, but generated initrd is broken after 1st reboot. At the end of the 1st boot, I can verify initrd with 'lsinitrd /boot/initrd-4.3.3-1-raspberrypi' and all is ok. But if I reboot or if I umount and remount /boot (mmcblk0p2), initrd file is broken: lsinitrd /boot/initrd-4.3.3-1-raspberrypi returns: ******************************************************************************** Image: /boot/initrd-4.3.3-1-raspberrypi: 5,8M ======================================================================== xzcat: /boot/initrd-4.3.3-1-raspberrypi: Compressed data is corrupt Version: Arguments: xzcat: /boot/initrd-4.3.3-1-raspberrypi: Compressed data is corrupt dracut modules: xzcat: /boot/initrd-4.3.3-1-raspberrypi: Compressed data is corrupt ======================================================================== xzcat: /boot/initrd-4.3.3-1-raspberrypi: Compressed data is corrupt cpio: premature end of file drwxr-xr-x 15 root root 0 Feb 29 01:04 . drwxr-xr-x 2 root root 0 Feb 29 01:04 bin -rwxr-xr-x 1 root root 771176 Feb 29 01:04 bin/bash ======================================================================== ******************************************************************************** Once remounted, if I call "dracut -f -H" manually to regenerate initrd, all is ok after umounting and remounting the partition or if I reboot. Any idea what would be the problem and how to fix that ? Note that upstream image is not affected. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 9

[opensuse-arm] Newest image for Raspberry Pi 1 looks promising
by Freek de Kruijf 02 Mar '16

02 Mar '16

Finished testing the newest image openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build377.2.raw.xz from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/ for Raspberry Pi 1B This image is much smaller than its predecessor: 160 MiB versus 230 MiB. I test it with a HDMI device connected, so I can see the messages. First it shows the u-boot messages, shows for a short while Tux and shows a black screen for quite a while. Apparently during this time the SD card is changed to have a swap partition at the end and the ROOT partition is enlarged to cover the remaining space on the SD card. After that it shows a number of messages typical ones one see during boot. There is an an error message about being not able to mount /boot/efi The system ends in an emergency state. After power down and up it does not boot anymore but it looks the system is trying to boot via the network. One of the last messages is that one should run "journalct -xb" to see what went wrong. I mounted the SD card, or rather the ROOT partition, on my desktop and started the command "journalctl -D <path-to-/var/log/journal-on-ROOT> -xb" which showed me the messages. Most likely the problem is the mounting of /boot/vfat; the error message reports: mount[5289]: mount: unknown filesystem type 'vfat', so apparently there is a missing module in the kernel. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 8