July 2016 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] pine64
by Alexander Graf 14 Jul '16

14 Jul '16

> On 10 Jul 2016, at 04:12, Stefan Bruens <stefan.bruens(a)rwth-aachen.de> wrote: > > On Sonntag, 10. Juli 2016 03:17:06 CEST you wrote: >>> Am 10.07.2016 um 00:57 schrieb Stefan Bruens <stefan.bruens@rwth- > aachen.de>: >>>> On Sonntag, 10. Juli 2016 00:47:47 CEST Stefan Bruens wrote: >>>>> On Freitag, 8. Juli 2016 12:05:33 CEST Alexander Graf wrote: >>>>>> On 08.07.16 12:02, Peter Czanik wrote: >>>>>> Hi, >>>>>> >>>>>> After quite a bit of delay, my Pine64 is here. The boards boots with >>>>>> the >>>>>> Android image, so I wanted to give openSUSE a try. I downloaded the >>>>>> image from >>>>>> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib: >>>>>> / >>>>>> Pi >>>>>> ne64:/Downstream/images/openSUSE-Tumbleweed-ARM-JeOS-pine64.aarch64.raw >>>>>> . >>>>>> xz >>>>>> as this one is supposed to have graphics, but after about 15 minutes >>>>>> the >>>>>> screen is still blank. Is it normal? Did anyone test the image >>>>>> recently? >>>>> >>>>> IIRC I added console=ttyAMA0 to the default kernel command line. You do >>>>> see grub2 coming up? >>>>> >>>>> Alex >>> >>> Just switched power supplies, no I get: >>> >>> Booting `openSUSE-Tumbleweed-ARM-JeOS-pine64' >>> >>> Loading Linux 3.10.65-1-pine64aw ... >>> Loading initial ramdisk ... >>> EFI stub: Booting Linux Kernel... >>> EFI stub: UEFI Secure Boot is enabled. >>> [ 0.000000] script buffer is NULL! >>> [ 27.735603] axp81x_board_init: axp regl_devs num = 23 >>> [ 27.988108] Warning: can not find np for pmu1. >>> [ 27.988441] add_sys_pwr_dm: get ldo name for id: vcc-lpddr failed >>> [ 27.988718] Warning: can not find np for dynamic_standby_para. >>> [ 32.063459] hci: ERR: sunxi_ehci is null >>> [ 32.063470] hci: ERR: sunxi_ohci is null >>> [ 32.063504] hci: ERR: sunxi_ehci is null >>> [ 32.063515] hci: ERR: sunxi_ohci is null >>> [ 34.186102] Failed to alloc md5 >>> [ 34.484571] get() with no identifier >>> [ 34.488470] get() with no identifier >>> [ 34.492365] get() with no identifier >>> [ 34.560263] Call trace: >>> [ 34.562972] plugout_end:switch:0 >>> [ 34.583294] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !! >>> [ 34.590853] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !! >>> [ 34.602220] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! >>> [ 34.612782] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! >>> [ 34.620154] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! >>> [ 34.627519] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! >>> [ 34.713047] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RE !! >>> [ 34.719938] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RE !! >>> [ 34.730274] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RE !! >>> [ 34.737065] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! >>> [ 34.743879] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! >>> [ 34.750633] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! >>> [ 34.757368] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! >>> [ 34.764119] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! >>> [ 34.770965] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! >>> [ 34.777793] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! >>> [ 34.784634] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! >>> [ 34.791568] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RE !! >>> [ 34.900927] systemd[1]: Failed to start Load Kernel Modules. >>> [FAILED] Failed to start Load Kernel Modules. >>> See 'systemctl status systemd-modules-load.service' for details. >>> >>> Starting Apply Kernel Variables... >>> Starting Create Static Device Nodes in /dev... >>> >>> [ OK ] Started Apply Kernel Variables. >>> [ OK ] Started Create Static Device Nodes in /dev. >>> [ OK ] Started Journal Service. >>> [ OK ] Started dracut cmdline hook. >>> >>> Starting udev Kernel Device Manager... >>> >>> [ OK ] Started udev Kernel Device Manager. >>> >>> Starting udev Coldplug all Devices... >>> Mounting Configuration File System... >>> >>> [ OK ] Mounted Configuration File System. >>> [ OK ] Started udev Coldplug all Devices. >>> [ OK ] Reached target Remote File Systems (Pre). >>> [ OK ] Reached target Remote File Systems. >>> [ TIME ] Timed out waiting for device dev-di...L64G_0x70c31c5f >>> \x2dpart3.device. >>> [DEPEND] Dependency failed for Resume from h...y-id/mmc-SL64G_0x70c31c5f- >>> part3. >>> [ OK ] Reached target Local File Systems (Pre). >>> [ OK ] Reached target Local File Systems. >>> [ OK ] Reached target System Initialization. >>> [ OK ] Reached target Basic System. >>> [** ] A start job is running for dev-disk...rt2.device (1min 48s / no >>> limit)^C >>> ... >>> [ ***] A start job is running for dev-disk...rt2.device (7min 22s / no >>> limit) >> >> I think this indicates a previous failed firstboot run. Please try to >> reflash the original image onto your sd card, then try again with your >> known-good power supply :). Keep in mind that first boot may take a few >> minutes (just remove the quiet option from the kernel cmdline to see what's >> going on). >> >> Alex > > Tried again with a fresh SD install: > > On first boot attempt, after loading of the kernel/initrd, the "screen" is is > cleared, and after about 2 minutes the boot commences with the normal systemd > messages about started services. > > After a reboot, the GPT seems to be broken: > > U-Boot reports: > > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > GUID Partition Table Entry Array CRC is wrong: 0xb58bf7a3 != 0x5c9246a8 > get_partition_info_efi: *** ERROR: Invalid GPT *** > get_partition_info_efi: *** Using Backup GPT *** This indicates that we’re writing the SPL/boot0 to the SD card, but didn’t resize the GPT properly to make space for it. The code that should have done this is here at line 287: https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/uboo… I guess using the absolute path /usr/src/packages/KIWIROOT-oem/usr/sbin/gdisk in the firstboot script isn’t the smartest idea. Instead we should just set PATH accordingly. I’ve checked in an updated version of the description that hopefully build correct images: https://build.opensuse.org/package/rdiff/openSUSE:Factory:ARM/JeOS?linkrev=… Please give it a try once you see the new build emerge :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

Re: [opensuse-arm] 4.7-rc6 status
by Oscar C 12 Jul '16

12 Jul '16

El 2016-07-11 02:17, Andreas Färber escribió: > Hello, > > With help from Matwey we finally have armv7hl kernels in Kernel:HEAD > again. Here are some mixed test results of 4.7.0-rc6-4.g3146576: Wow nice work, thanks! > > Jetson TK1: > * lpae works but only with Tumbleweed kernel-firmware, oops otherwise > * 4.6.2-1-lpae boots okay with dtb-tegra124 4.7.rc6 > > Cubietruck: > * lpae broken, no output > * 4.6.2-1-lpae boots with dtb-sun7i 4.7.rc6 > * Only boot.scr works, no output with GRUB (u-boot-cubietruck > 2016.05) > > Raspberry Pi 2: > * default and lpae broken, no output > * 4.6.2-1-default boots with dtb-bcm2836 4.7.rc6 (-lpae known broken) > > Raspberry Pi: > * default boots fine, except for some deadbeef vc4 error > * 4.6.2-1-default boots with dtb-bcm2835 4.7.rc6 My udoo quad (imx6) doesn't boot either. No output with kernel 4.7 (I tried with the new dtb and with the old one but neither of them worked). Kernel 4.6.2 works fine. -- Cheers -- 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] JeOS-raspberrypi3_aarch64 GRUB issues
by Andreas Färber 11 Jul '16

11 Jul '16

Hi, Testing the above image (from oSC16) some more, I've found that there is no serial console when selecting the rescue option. This appears to be because there is a huge set of command line options in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT while GRUB_CMDLINE_LINUX is empty. The console= option should be in the latter instead. Also there is a root= option in ..._DEFAULT - we don't need to specify it here, it is duplicate. Are those Kiwi issues or JeOS issues? Regards, 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

3 4

[opensuse-arm] FYI: wicked issue with custom arm64 kernels
by Andreas Färber 11 Jul '16

11 Jul '16

Hi, Since I ran into this the second time within three weeks myself: The currently published aarch64 wicked packages contain a known incompatibility with upstream defconfigs [1]. The issue has been fixed in wicked 0.6.36, but no new packages have been published yet for aarch64 (0.6.35). For armv7hl and armv6hl we have 0.6.36 already. Symptoms: You boot your kernel okay and after `zypper dup` network stops working, with the wicked.service failing to start and the interfaces failing to come up (`ip a`). If you're using official openSUSE kernels (e.g., openSUSE:Factory:ARM, Kernel:stable or Kernel:HEAD) you won't be affected, as the config options have been enabled all along. Contrib kernels may be affected! Our JeOS images don't contain an alternative to wicked, so the naive idea of simply switching to NetworkManager won't work easily, given the lack of network. Workaround: Either modify your kernel to enable the intermittently required config options [1] (IP_ADVANCED_ROUTER, IP_MULTIPLE_TABLES) or download on another machine and install via USB/SD a newer wicked .rpm. Regards, Andreas [1] https://bugzilla.opensuse.org/show_bug.cgi?id=981887 -- 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] pine64
by Peter Czanik 10 Jul '16

10 Jul '16

Hi, After quite a bit of delay, my Pine64 is here. The boards boots with the Android image, so I wanted to give openSUSE a try. I downloaded the image from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pin… as this one is supposed to have graphics, but after about 15 minutes the screen is still blank. Is it normal? Did anyone test the image recently? Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 6

[opensuse-arm] USB TTL on raspberry pi 3
by Goldwyn Rodrigues 05 Jul '16

05 Jul '16

Hi, I am trying to use USB TTL on raspberry pi 3. I get the console messages when the device is up, but I get garbage after the message "Starting kernel ...". I found the post http://raspberrypi.stackexchange.com/questions/45007/garbage-on-raspberry-p… and added dtoverlay=pi3-disable-bt dtoverlay=pi3-miniuart-bt enable_uart=1 in /boot/vc/config.txt but it still does not work. What is the way to to get the serial communication working? I also noticed the kernel is pretty old (4.1.19-1-rpi2). Is there a newer kernel we should use? Also, do we have the corresponding dtb trees for pi3? -- Goldwyn -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Memory size for Pi3
by Murakawa Ryo 03 Jul '16

03 Jul '16

Hi I have been using OopenSUSE Tumbleweed (20160623) (armv7hl)² on 2 Pi3. When I run ³free² on the terminal, the output is below. phoenix:/etc # free total used free shared buff/cache available Mem: 880080 305804 164312 8580 409964 538068 Swap: 506856 17776 489080 My question is below. This Pi3 has 1GByte memory. But the output of free is 880080. So why is the output equal to 1GB? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Leftover published rpi3 images
by Andreas Färber 02 Jul '16

02 Jul '16

Hi, On http://download.opensuse.org/ports/armv7hl/tumbleweed/images/ there's some openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.armv7l* files from April 16th that are clearly misplaced and outdated. Can someone please remove them to avoid user confusion? 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 0