- openSUSE ARM

[opensuse-arm] Leap 42.1 for armv7l ?
by Thomas Bechtold 15 Nov '15

15 Nov '15

Hi, are there plan to do a openSUSE Leap 42.1 release for the armv7l platform? Best, Tom -- 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] cuboxi tumbleweed images don't boot
by Thomas Bechtold 14 Nov '15

14 Nov '15

Hi, I tried to use the Tumbleweed images from [1] but the image does not boot. Here's the output during boot: U-Boot SPL 2013.10-rc4 (Oct 16 2015 - 05:16:01) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4 (Oct 16 2015 - 05:16:01) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 2 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device 2762 bytes read in 34 ms (79.1 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 mmc0 is current device 7163544 bytes read in 492 ms (13.9 MiB/s) 49298053 bytes read in 2897 ms (16.2 MiB/s) ** File not found dtb/call_autodetectfdt ** Kernel image @ 0x10800100 [ 0x000000 - 0x6d4e98 ] ## Loading init Ramdisk from Legacy Image at 14800100 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 49297989 Bytes = 47 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree ** File not found /boot/boot.scr ** ** File not found /boot/uEnv.txt ** ** File not found /boot/zImage ** ** File not found /boot/uImage ** Booting from net ... FEC Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY FEC FEC Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY FEC FEC Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY FEC Booting uImage ## Booting kernel from Legacy Image at 10800000 ... Image Name: Boot-Script Image Type: ARM Linux Script (uncompressed) Data Size: 2698 Bytes = 2.6 KiB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 2690 Bytes = 2.6 KiB Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! CuBox-i U-Boot > Evironment is: CuBox-i U-Boot > printenv autoboot=echo Booting ${boot_file}; if test ${boot_file} = zImage; then bootz ${loadaddr} ${ramdisk_addr} ${fdt_addr}; else bootm ${loadaddr} ${ramdisk_addr} ${fdt_addr}; fi; autodetectfdt=if test ${cpu} = 6SOLO || test ${cpu} = 6DL; then setenv fdt_prefix imx6dl; else setenv fdt_prefix imx6q; fi; if test ${board} = mx6-cubox-i; then setenv fdt_file ${fdt_prefix}-cubox-i.dtb; elif test ${board} = mx6-hummingboard; then setenv fdt_file ${fdt_prefix}- hummingboard.dtb; else setenv fdt_file ${fdt_prefix}-hummingboard2.dtb; fi; baudrate=115200 board=mx6-cubox-i boot_fdt=try boot_file=uImage boot_kernel=${boottype} ${kerneladdr} ${ramdiskaddr}:${rd_filesize} ${fdtaddr} boot_prefixes=/ /boot/ bootargs=console=ttymxc0,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp bootcmd=for bootdev in ${bootdevs}; do for unit in ${units}; do setenv bootpart; for bootpart in ${bootparts}; do setenv fix_bootpart "setenv bootpart $bootpart"; run fix_bootpart; run setdev; run doit; done; done; done bootdelay=3 bootdevs=mmc bootenv=uEnv.txt bootfile=uImage bootit=setenv boot_file ${bootfile}; if test -n ${ramdisk_file}; then if run loadramdisk; then echo Loaded ${ramdisk_file}; setenv ramdisk_addr ${ramdisk_addr}:0x${filesize}; else setenv ramdisk_addr -; fi; else setenv ramdisk_addr -; fi; if test ${boot_file} = zImage; then if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then echo Loaded ${fdt_file}; else setenv fdt_addr; if test ${boot_fdt} = try; then echo WARN: Cannot load the DTB and boot file is type zImage;echo if you have not appended a dtb to the file it may;echo hang after displaying Starting kernel...;echo ;else echo WARN: Cannot load the DT; fi; fi; else setenv fdt_addr; fi; else setenv fdt_addr; fi; run autoboot; bootpart=0:1 bootparts=${unit}:1 bootscript=echo Running bootscript from mmc ...; source; boottype=net console=ttymxc0 cpu=6Q doit=run load_splashfile; if run load_kernel; then; run load_initrd; run loadfdt; run boot_kernel; fi ethact=FEC ethaddr=d0:63:b4:00:66:05 ethprime=FEC fdt_file=imx6q-cubox-i.dtb fdt_high=0xffffffff fdt_prefix=imx6q fdtaddr=0x14700100 fdtfile=call_autodetectfdt fdtfolder=dtb file_prefix=/boot/ filesize=2f03a85 fix_bootpart=setenv bootpart ${unit}:1 flavor=cuboxi get_cmd=dhcp importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}; initrd=boot/initrd.uboot initrd_high=0xffffffff ip_dyn=yes kernel=boot/linux.vmx kerneladdr=0x10800100 load_initrd=${fs}load ${bootdev} ${bootpart} ${ramdiskaddr} ${initrd}; setenv rd_filesize ${sizeprefix}${filesize} load_kernel=${fs}load ${bootdev} ${bootpart} ${kerneladdr} ${kernel} load_splashfile= loadaddr=0x10800000 loadbootenv=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${file_prefix}${bootenv}; loadbootfile=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${file_prefix}${bootfile}; loadbootscript=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${file_prefix}${script}; loadfdt=${fs}load ${bootdev} ${bootpart} ${fdtaddr} ${fdtfolder}/${fdtfile} loadramdisk=if test ${boottype} = mmc; then load mmc ${mmcdev}:${mmcpart} ${ramdisk_addr} ${file_prefix}${ramdisk_file}; else ${get_cmd} ${ramdisk_addr} ${ramdisk_file}; fi; mmcargs=setenv bootargs quiet console=${console},${baudrate} root=${mmcroot}; mmcboot=echo Booting from mmc ...; run mmcargs; setenv boottype mmc; run bootit; mmcdev=0 mmcpart=1 mmcroot=/dev/mmcblk0p2 rootwait rw netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp; netboot=echo Booting from net ...; run netargs; setenv boottype net; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if test ${bootfile} = auto; then setenv bootfile zImage; if ${get_cmd} ${bootfile}; then run bootit; else setenv bootfile uImage; fi; fi; ${get_cmd} ${bootfile}; run bootit; origbootfile=auto preboot=if hdmidet; then usb start; setenv stdin serial,usbkbd; setenv stdout serial,vga; setenv stderr serial,vga; else setenv stdin serial; setenv stdout serial; setenv stderr serial; fi; ramdisk=boot/initrd.uboot ramdisk_addr=- ramdisk_file=initrd ramdiskaddr=0x14800100 rd_filesize=0x2f03a85 script=boot.scr setdev=mmc dev ${unit} should_load_fdt=1 should_use_fdt=1 should_use_splashfile=0 sizeprefix=0x splashfile=opensuse.bmp splashpos=m,m stderr=serial stdin=serial stdout=serial target=firstboot units=0 update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if mmc dev ${mmcdev}; then if ${get_cmd} ${update_sd_firmware_filename}; then setexpr fw_sz ${filesize} / 0x200; setexpr fw_sz ${fw_sz} + 1; mmc write ${loadaddr} 0x2 ${fw_sz}; fi; fi; update_sd_firmware_filename=u-boot.imx Environment size: 4849/8188 bytes CuBox-i U-Boot > Comments how to solve this? Best, Tom [1] http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Cont rib:/IMX6/images/openSUSE-Tumbleweed-ARM-JeOS-cuboxi.armv7l.raw.xz -- 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] Booting udoo board
by Oscar 03 Nov '15

03 Nov '15

Hi, I'm trying to boot my udoo board (uses the imx6 quad SoC). So far, u-boot starts but when the kernel starts nothing happends. This is the u-boot log: U-Boot SPL 2015.10 (Oct 31 2015 - 09:05:51) U-Boot 2015.10 (Oct 31 2015 - 09:05:51 +0000) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: Udoo Quad DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device reading boot.scr 2735 bytes read in 16 ms (166 KiB/s) Running bootscript from mmc ... ## Executing script at 12000000 switch to partitions #0, OK mmc0 is current device reading boot/linux.vmx 7157072 bytes read in 496 ms (13.8 MiB/s) reading boot/initrd.uboot 48673918 bytes read in 3213 ms (14.4 MiB/s) reading dtb/imx6q-udoo.dtb 32562 bytes read in 38 ms (835.9 KiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x6d3550 ] ## Loading init Ramdisk from Legacy Image at 16000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 48673854 Bytes = 46.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 15f00000 Booting using the fdt blob at 0x15f00000 Loading Device Tree to 4fd7d000, end 4fd87f31 ... OK Starting kernel ... I suppose there's a problem with the machine ID or seomthing similar. To debug that I see that I need to activate the DEBUG_LL option in kernel. How can I do that? 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] JeOS from openSUSE:Factory:ARM doesn't boot
by Matwey V. Kornilov 03 Nov '15

03 Nov '15

Hi, I am facing the following with openSUSE-Tumbleweed-ARM-JeOS-beaglebone.armv7l-1.12.1-Build339.1 http://paste.opensuse.org/46688397 -- 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] Re: [opensuse-factory] Suse and Raspberry Pi Build
by Freek de Kruijf 28 Oct '15

28 Oct '15

Op woensdag 28 oktober 2015 11:31:53 schreef gm1mqe(a)aol.com: > This is GREAT! As soon as my HDMI cable arrives I will install it onto a Pi > 2 B+ and just have some fun. I had seen there were some ARM buids but was > not sure what to use. Do any problems go here or is there a specific ARM > forum? There is a special ARM mailing list: opensuse-arm(a)opensuse.org Subscribe via: opensuse-arm+subscribe(a)opensuse.org -- 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

1 0

[opensuse-arm] openSUSE on Raspberry B+/2 usable as a server?
by Johannes Kastl 27 Oct '15

27 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear opensuse-on-Raspi-Folks, I read the last couple of months of the mails on the opensuse-arm mailinglist, but I am not sure: Is openSUSE 13.x usable on a Raspberry B+ or 2? If I find one of the few images that are installing correctly, can I keep it up to date and secure without issues? (I am not talking about Tumbleweed, I'd prefer something less time consuming. And I do not mean I would take lots of manual intervention, its just lots and lots of updates and the occasional configuration change) Ideally this would mean 13.1 or 13.2 being usable, or maybe Leap is going to be usable. Anyone tried Leap yet? Thanks in advance for your input! Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlYgDfMACgkQzi3gQ/xETbJChQCeN/wgiXCfLio5jP3pG3iVqpsp C4sAn1d0VJW5KGj40ROlSQ7yVfc7Z4UQ =mMa1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 10

[opensuse-arm] Creating a coreboot based image
by Andrew Wafaa 22 Oct '15

22 Oct '15

Hi, I'm the proud owner of a delightful Asus C100P Chromebook Flip (veyron_minnie), and I'm hoping to create an image similar to the Series3 Samsung Chromebook. One of the big differences is that the Flip uses coreboot only and not u-boot, so I can't reasonably just copy what was done previously. So how am I supposed to go about it? Thanks, Andy -- 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] Re: Factory:ARM publishing is disabled
by Dirk Müller 20 Oct '15

20 Oct '15

Hi, >> It's always disabled, because publishing happens via product building and >> testing. I just checked, we have recently published a new tree (a day ago) >> and have worked on openqa the last few days. >> Is there any particular problem that you're looking for? > I'm trying to build u-boot for udoo board (since it's very similar to > cuboxi, I'm using it as a base). I branched u-boot from Base:System in > home:ocurero:branches:Base:System and then I modified the templates to build > each flavour. However, I'm must be doing something wrong because all u-boot > packages I have are "blocked" for two days. Ah, that can happen, we just had a deep rebuild on Tumbleweed due to a toolchain update. sometimes this can take a few days until things get unblocked. if you want to not wait for blocking, change your prj meta for that repo to "block=local" Greetings, Dirk -- 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] sunxi GMAC disabled
by Frank Kunz 16 Oct '15

16 Oct '15

Hello, unfortunately the GMAC kernel configuration for Allwinner A20 and A31 devices is disabled in armv7l kernel 4.2. Therefore the A20 Olimex bards do not have network anymore. What needs to be done to get that enabled again: config DWMAC_SUNXI tristate "Allwinner GMAC support" default ARCH_SUNXI depends on OF ---help--- Support for Allwinner A20/A31 GMAC ethernet controllers. This selects Allwinner SoC glue layer support for the stmmac device driver. This driver is used for A20/A31 GMAC ethernet controller. Br, Frank -- 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] Factory:ARM publishing is disabled
by Oscar C 16 Oct '15

16 Oct '15

Hi, It seems that Factory publishing got disabled. Is there any problem? Thanks! -- 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] zypper dup problem
by Peter Czanik 15 Oct '15

15 Oct '15

Hi, I was trying to run "zypper dup" on my Raspberry Pi2 to have all the "recommended" packages installed. The problem is: Retrieving: libcolord-gtk1-0.1.26-1.1.armv7hl.rpm ........................[done] Retrieving package libcolorhug2-1.2.12-1.1.armv7hl (66/435), 71.7 KiB ( 66.0 KiB unpacked) Retrieving: libcolorhug2-1.2.12-1.1.armv7hl.rpm .........................[error] File './suse/armv7hl/libcolorhug2-1.2.12-1.1.armv7hl.rpm' not found on medium 'http://download.opensuse.org/ports/armv7hl/tumbleweed/repo/oss/' Abort, retry, ignore? [a/r/i/? shows all options] (a): r Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

Re: [opensuse-arm] Raspberry Pi 2
by Peter Czanik 15 Oct '15

15 Oct '15

Hi, Thanks! With the removal of raspberry-gfx now I have at least something on screen. I better take a smaller screen for the demo :) Bye, CzP On 10/14/2015 06:06 PM, Michael Emory Cerquoni wrote: > I have not been able to get GUI working correctly on the raspberry pi > 2 myself. at the blinking cursor if you hit ctrl+alt+f1 you should > get a console log in. The only way i could get video to come up was > to uninstall the raspberrypi gfx packages and let the stock mesa > packages install, once those were installed reboot and you should get > graphics but you will be stuck in 800x480 resolution. So far I have > not gotten anything better than this on my Raspberry Pi 2 Model B. > > On Wed, Oct 14, 2015 at 11:33 AM, Peter Czanik <peter(a)czanik.hu > <mailto:peter@czanik.hu>> wrote: > > On 10/14/2015 04:05 PM, Guillaume Gardet wrote: > > Hi, > > > Le 14/10/2015 16:02, Peter Czanik a écrit : > > Hi, > > I'd like to demo Raspberry Pi 2 with openSUSE at a > conference. I tried the XFCE image at > http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… > which I found at the RPi2 HCL page at > https://en.opensuse.org/HCL:Raspberry_Pi2 > I was prepared for a slow boot, but after 20 minutes, the > screen is still blank with the cursor blinking in the > upper left corner. > Any idea, what could have gone wrong? Any other image I > should try? > > > You could try to access it through network (SSH) or serial > port to see what is going on. > > > Just found it in the Xorg logs: > > xfce4-session: symbol lookup error: /usr/lib/libEGL.so.1: > undefined symbol: glDiscardFramebufferEXT > > Does it affect other window managers? Should I give the LXDE image > a try? > > Bye, > CzP > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > <mailto:opensuse-arm%2Bunsubscribe@opensuse.org> > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > > > > -- > 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] Raspberry Pi 2
by Peter Czanik 14 Oct '15

14 Oct '15

Hi, I'd like to demo Raspberry Pi 2 with openSUSE at a conference. I tried the XFCE image at http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… which I found at the RPi2 HCL page at https://en.opensuse.org/HCL:Raspberry_Pi2 I was prepared for a slow boot, but after 20 minutes, the screen is still blank with the cursor blinking in the upper left corner. Any idea, what could have gone wrong? Any other image I should try? 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 3

[opensuse-arm] New 8250 OMAP serial driver (second try)
by Matwey V. Kornilov 07 Oct '15

07 Oct '15

Hello, Please, test an image from http://download.opensuse.org/repositories/home:/matwey:/JeOS-omap-serial/im… if you have device with OMAP UART. Now, new OMAP driver works for me on BeagleBone Black. Kernel is 4.3.0-rc3-1.gb439548-default. I am going to submit patch switching to new 8250 driver, so please test. -- 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] Re: [opensuse-kernel] Re: armv7hl kernel-default config have tegra20 serial output broken
by Misha Komarovskiy 06 Oct '15

06 Oct '15

Hello, I have no experience with kgdb. As system restarts after panic timeout i wanted to catch oops message in kernel output via serial console. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Sat, Aug 1, 2015 at 1:46 PM, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> wrote: > 01.08.2015 12:48, Misha Komarovskiy пишет: >> Hello, >> I found that latest images for my armv7 board (paz00/ac100) which use >> kernel-default have kernel panic on start without any output to serial >> console, but serial output was working last time i tested image back >> in may. >> >> I cloned kernel-source git repo made sequence-patched kernel and >> recompiled it with >> enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to >> config/armv7hl/default config, but found that there is no ttyS0 >> output, only earlycon here is paste: >> http://paste.opensuse.org/31390203 >> > > Have you tried to use kgdb? Does it not work too? > >> Recompiling same kernel with multi_v7_defconfig config and same >> debug/earlyprintk options have no panics and normal serial output: >> http://paste.opensuse.org/13080662 >> >> Maybe kernel-default config require some extra tricks now to have serial output? >> I want to catch that panic. >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> > > > -- > To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 11

[opensuse-arm] openSUSE_Factory_ARM: systemd-tmpfiles: command not found
by Michael Ströder 06 Oct '15

06 Oct '15

HI! I'm building in a local OBS branch: https://build.opensuse.org/package/show/home:stroeder:branches:server:dns/u… All builds work ok but all openSUSE_Factory_ARM builds fail with this message: /.build_patchrpmcheck_scr: line 22: systemd-tmpfiles: command not found postinstall script of unbound-1.5.5rc1-21.1.armv6hl.rpm failed Any clue? Ciao, Michael.

2 2

[opensuse-arm] Cubietruck built-in Ethernet broken with kernel 4.2
by Andreas Färber 05 Oct '15

05 Oct '15

Hi, Updating from 4.1 to 4.2 breaks the built-in Ethernet on Cubietruck, possibly Allwinner based boards as well (kernel-lpae and -default). As a workaround, a USB Ethernet adapter can restore eth0 for ssh access. Serial console output is still not working for me. A quick glance at the configs reveals # CONFIG_DWMAC_SUNXI is not set on both packages - not yet sure if related. 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

2 3

[opensuse-arm] armv6hl excluded for Kernel:stable?
by Stefan Bruens 05 Oct '15

05 Oct '15

Hi, since OBS revision 407 of Kernel:stable [1] no kernel is built for armv6hl (it is no longer in ExclusiveArch:). Whats the reasoning behind this? Resources should not be the issue, as kernel-docs, which is a) noarch b) a real resource hog is still built for armv6hl Kind regards, Stefan [1] https://build.opensuse.org/package/rdiff/Kernel:stable/kernel-source?linkre… -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- 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] Drop 12.2 and 12.3 ARM build in X11:Enlightenment:Factory
by Tomáš Čech 01 Oct '15

01 Oct '15

Hi, is there chance that anyone would be using and requiring 12.2 and 12.3 ARM builds of X11:Enlightenment:Factory? I should either drop the support or fix it but I'd rather drop it and have just latest distro versions as build targets... Is anyone still using that? If there is noone during the week, I'll just drop it. Thanks. Tomas Cech Sleep_Walker -- 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] have same soname but different type
by Michael Ströder 30 Sep '15

30 Sep '15

Updating a rasperry pi results in a lot of messages saying "have same soname but different type" (see below). Anything to be concerned about? Ciao, Michael. Additional rpm output: /sbin/ldconfig: libraries libtasn1.so.6.4.2 and libtasn1.so.6.5.1 in directory /usr/lib have same soname but different type. (14/65) Installing: libsystemd0-224-1.1 ..................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (15/65) Installing: libsensors4-3.4.0-1.2 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (16/65) Installing: libseccomp2-2.2.3-2.1 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (17/65) Installing: libdbus-1-3-1.8.18-3.1 ...............................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (18/65) Installing: libavahi-common3-0.6.31-25.3 .........................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (19/65) Installing: libapparmor1-2.10-4.1 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (20/65) Installing: libXmuu1-1.1.2-5.1 ...................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (21/65) Installing: libXext6-1.3.3-3.1 ...................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (22/65) Installing: iproute2-4.2-1.1 .....................................................................................................................................................................[done] (23/65) Installing: hwinfo-21.21-1.2 .....................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type.

1 0

[opensuse-arm] kiwi initrd: perl modules installed but not used
by Matwey V. Kornilov 27 Sep '15

27 Sep '15

Hello, In initrd from openSUSE:Factory:ARM JeOS there is > du -sch usr/lib/perl5 2,4M usr/lib/perl5 At the same time, there is no /usr/bin/perl, and I have not found who needs this modules. Maybe the perl modules have to be dropped as well? -- 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] kiwi initrd drivers
by Matwey V. Kornilov 26 Sep '15

26 Sep '15

Hello, In JeOS.kiwi for armv7hl I see the following: <drivers> <file name="drivers/ata/*"/>  <file name="drivers/dma/*"/>  <file name="drivers/gpio/*"/>  <file name="drivers/gpu/*"/>  <file name="drivers/mmc/*"/>  <file name="drivers/phy/*"/>  </drivers> but in the generated initrd I see that all drivers are present: lib/modules/4.3.0-rc2-1.g2b75354-default/kernel/drivers> ls ata cdrom dma gpu hwmon input media mfd mmc ntb phy ptp soc thermal uwb video block char gpio hid iio md message misc net parport pps scsi ssb usb vhost virtio And I cannot understand how this is supposed to work. What <drivers> is used for? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 7

[opensuse-arm] 13.2 ARM updates
by Volker Kuhlmann 23 Sep '15

23 Sep '15

oS 13.2 on a cubieboard: # zypper up Loading repository data... Warning: Repository 'openSUSE-13.2-repo-update' appears to be outdated. Consider using a different mirror or server. Same after zypper ref (which zypper up does first anyway). This came up in May too, without answer. # zypper lr -u | grep upda http://download.opensuse.org/ports/update/13.2/ Is this the correct repo to use for 13.2 ARM updates? If yes, the answer is obvious - the latest update in there is 25 June! 13.2 x86 has updates every few days. Some of them won't be appliccable to ARM, but I'm sure libgcrypt and gnutls are, and I'd have guessed there to have been some kernel fixes too. The kernel, dtb-sun4i, dracut and u-boot are from factory (by necessity, the 13.2 ones don't work). Are mainstream updates not available for ARM / ports? I hope not. Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 11

[opensuse-arm] start startx automatically?
by Jimmy PIERRE 15 Sep '15

15 Sep '15

Greetings, Using http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… I need to ssh and start startx manually... Please advise accordlingly!. Cheers, Jimmy -- 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] Raspberry Pi with OpenSuSe: I am lost
by Edgar Dombrowski 14 Sep '15

14 Sep '15

Hi, Raspberry Pi-Friends. I am lost. Following the different advices in this forum, I have downoaded the different xz-files as listend in the Repos for the OS13,2- arm-v6i- and the arm-v7l-versions for installation into the Raspbi B+ and 2B. But it always failed when booting. What can I do? The Mikro-CD-cards are ok as success when loading varios Debian-Squeeze. Thank you for your assistance Edgar Dombroiwski, DJ3PU, Munich -- 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] How to upgrade kernel on Raspberry Pi
by Olav Reinert 07 Sep '15

07 Sep '15

Hi, I've got a Raspberry Pi running openSUSE Factory. The kernel is kernel-raspberrypi-3.11.4-1.7.armv6hl Recently, a new kernel update was installed: kernel-raspberrypi-3.11.4-10.1.armv6hl However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel? Regards, Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 9

Re: [opensuse-arm] New 8250 OMAP serial driver
by Andreas Färber 03 Sep '15

03 Sep '15

Hi, Am 28.08.2015 um 09:22 schrieb Misha Komarovskiy: > On Mon, Aug 24, 2015 at 8:01 PM, Matwey V. Kornilov > <matwey.kornilov(a)gmail.com <mailto:matwey.kornilov@gmail.com>> wrote: > > Still no luck. > > > I noticed that current default and vanilla configs contain some platform > specific defines: > > grep -ni debug_ll * > default:7724:# CONFIG_DEBUG_LL is not set > default:7727:CONFIG_DEBUG_LL_INCLUDE="debug/bcm63xx.S" > lpae:7335:# CONFIG_DEBUG_LL is not set > lpae:7337:CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S" > vanilla:7719:# CONFIG_DEBUG_LL is not set > vanilla:7722:CONFIG_DEBUG_LL_INCLUDE="debug/bcm63xx.S" > > maybe wrong debug macro may break some platform drivers? As you can see, CONFIG_DEBUG_LL is not enabled, so you can ignore CONFIG_DEBUG_LL_* defaults. lpae simply doesn't enable bcm63xx. Regards, Andreas P.S. No need for HTML here. :) -- 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 6

[opensuse-arm] Force to load module in kiwi initrd
by Guillaume Gardet 02 Sep '15

02 Sep '15

Hi Marcus, We are facing a problem with our Chromebook image. We need to load (manually) some module to get the display working. WIth dracut, we passed the right option (force_driver+="some modules"), so it is ok on 2nd boot but our 1st boot (with kiwi initrd) still show a black screen because we need to load the modules manually (which are not auto-loaded). Does kiwi support such an option? Guillaume -- 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] Samsung Chromebook current tumbleweed images
by Misha Komarovskiy 02 Sep '15

02 Sep '15

Hello, Just tried latest 316/318 Tumbleweed images for Samsung Chromebook and noticed that u-boot wont auto load boot.scr now and output contain alot errors about extlinux pxeboot. If i load boot.scr manualy, with ext2load mmc 1:2 0x50000000 boot.scr and then source 0x50000000 boot starts fine. Also lcd screen stays black after kernel start, probably some drm module still missing. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 32

[opensuse-arm] Perl 5.22 is not published
by Oscar C 31 Aug '15

31 Aug '15

Hi, I'm trying to install the update 5.22.0 of perl but although it's build it's not yet on the repository (openSUSE:Factory:ARM), the published version is 5.20.1. Is there any problem? -- Thanks! -- 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] New 8250 OMAP serial driver
by Matwey V. Kornilov 24 Aug '15

24 Aug '15

Hello, First test with CONFIG_SERIAL_8250_OMAP=y has been failed. However, you are welcome to try: http://download.opensuse.org/repositories/home:/matwey:/JeOS-omap-serial/im… Now, I don't see any output from console. However, the system is successfully booted and available by ssh. In dmesg I see авг 17 02:03:08 linux kernel: WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' авг 17 02:03:08 linux kernel: This ensures that you still see kernel messages. Please авг 17 02:03:08 linux kernel: update your kernel commandline. and that is how it should to be. Serial device seems to be here: linux:/ # head /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:8250 mmio:0x44E09000 irq:154 tx:7266 rx:0 RTS|CTS|DTR|DSR agetty is started on /dev/ttyS0 but no communication here. -- 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] Tests with latest Raspberry Pi images
by Freek de Kruijf 24 Aug '15

24 Aug '15

I tested a number of images from both Contrib:/RaspberryPi:/upstream as Contrib:/RaspberryPi/. From the last one I never got a working image, from upstream the last one that works is Build330.10 from Aug 6. All images for Raspberry Pi 2B are usable. -- 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

2 1

[opensuse-arm] U-Boot 2015.10-rc1 ASIX Usb ethernet dongle
by Misha Komarovskiy 21 Aug '15

21 Aug '15

Hello, With update to U-Boot 2015.10-rc1 ASIX Usb ethernet dongle not detected as ethernet device anymore, but visible as usb device in usb info, tested on Chromebook Snow. Worked fine with 2015.07-rc3 in both usb2 and usb3 ports. Maybe this happen because of removal "add_snow_usb_boot.patch"? I didn't tried clean upstream versions yet, specific snow patch was my first guess. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[opensuse-arm] kiwi fails to build Tumbleweed ARM images
by Guillaume Gardet 14 Aug '15

14 Aug '15

Hi Marcus, Tumbleweed ARM images fails to build on OBS. The problem is that it cannot find the pre bootloader install script (uboot-image-*-setup). See the build log: ******************************************************************************** [ 1906s] Aug-14 11:01:45 <1> : Creating uBoot initrd image... [ 1906s] Aug-14 11:01:45 <1> : EXEC [mkimage -A arm -O linux -T ramdisk -C none -a 0x0 -e 0x0 -n 'Initrd' -d /tmp/kiwiboot.ptkelf/boot/initrd.vmx /tmp/kiwiboot.ptkelf/boot/initrd.uboot] [ 1906s] Aug-14 11:01:45 <1> : EXEC [rm -f /tmp/kiwiboot.ptkelf/boot/initrd.vmx 2>&1] [ 1906s] Aug-14 11:01:45 <1> : Creating boot.script uboot config file... [ 1906s] Aug-14 11:01:45 <1> : Calling pre bootloader install script: [ 1906s] Aug-14 11:01:45 <1> : --> uboot-image-raspberrypi-setup [ 1907s] bash: uboot-image-raspberrypi-setup: No such file or directory [ 1907s] Aug-14 11:01:46 <3> : Call failed, see console log ******************************************************************************** Any idea why? Guillaume -- 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] Raspberry Pi 1 and 2 images from of Aug 6
by Freek de Kruijf 14 Aug '15

14 Aug '15

Results of the test with images for RPi 1 and 2 from Aug 6 Raspberry Pi 1: from RapberryPi1/ image works, however command "yast lan" crashes; from RaspberryPi1:/upstream image builds a corrupt ext4 partition Raspberry Pi 2: from RaspberryPi2/ image does not boot (non of these images ever booted) from RaspberryPi2:/Staging image works. I compared the installed packages from the two working images and found some obvious differences, kernel and firmware, but other packages only has differences in the building versions, the part of the version of the package after the last -. Except: llibmicrohttpd10-0.9.41-1.2 <-> ibmicrohttpd10-0.9.42-1.1 libyui-ncurses-pkg6-2.46.2-1.4 <-> libyui-ncurses-pkg6-2.47.0-1.1 libzypp-15.4.0-1.1 <-> libzypp-15.9.0-1.1 vim-7.4.788-1.1 <-> vim-7.4.712-1.1 yast2-bootloader-3.1.127-1.1 <-> yast2-bootloader-3.1.138-1.1 zypper-1.12.3-1.1 <-> zypper-1.12.8-1.1 This dpes not give me a clue why "yast lan" crashes on the RPi1 and is OK on the RPI2. -- 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

3 6

[opensuse-arm] Strange problem with Wi-Fi connection
by Freek de Kruijf 12 Aug '15

12 Aug '15

I have a RPi 1B with a Wi-Fi USB interface using the latest image for this system. The network is configured with a fixed IP address and obviously default gateway and DNS are configured as well. IPv6 is disabled. When I start the system, or later when things went wrong restart the network, I get a proper connection and can run "zypper up" with no problem. I access that system from my desktop via ssh. When I use the command "ip -d ne" I get the following: 192.168.178.1 dev wlan0 lladdr 9c:c7:a6:0a:1f:48 REACHABLE 192.168.178.6 dev wlan0 lladdr e0:cb:4e:cd:d7:b6 REACHABLE The first line shows the default gateway/router/Wi-Fi AP However after some time I get the following: 192.168.178.1 dev wlan0 lladdr 9c:c7:a6:0a:1f:48 STALE 192.168.178.6 dev wlan0 lladdr e0:cb:4e:cd:d7:b6 REACHABLE So I still have a connection from my desktop via the Wi-Fi AP to the RPi. When I try a ping to the default gateway I do not get a response. I used tcpdump on the RPi to catch the traffic. When doing the ping I see ARP requests for the MAC address of the IP address of the default gateway. However there is no response from the router. Puzzled!! -- 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

3 5

[opensuse-arm] ARM 13.2 update broken
by Guillaume Gardet 12 Aug '15

12 Aug '15

Hi, http://download.opensuse.org/ports/update/13.2/ repo is outdated. Last update is from 25th of june. Any idea what is the problem? OBS problem? Guillaume -- 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] Support for device-tree overlays
by Stefan Bruens 08 Aug '15

08 Aug '15

Hi everyone, as the RaspberryPI kernel is nowadays "configured" by the device tree, there are some issues for the current openSUSE images. By default the dtbs as shipped disable any optional hardware, which is a good thing. On the other hand things like SPI are no longer working. Raspbian tackles this with so called overlays and some help from the binary start.elf bootloader: 1. start.elf reads the dtb from the fat boot partition a) a file defined in config.txt, "device_tree=foo.dtb" b) a hardcoded hardware specific default file, "bcm2708-rpi-<variant>.dtb" 2. if the config.txt specifies "dtoverlay=foo-overlay" 1. the boot loader reads "overlays/foo-overlay.dtb" from the fat partition 2. the overlay is patched into the flattened device tree 3. the boot loader puts the device tree at address 0x100 (override with "device_tree_address=0xabcd1234" 4. the boot loader loads the specified kernel As openSUSE does not directly jump into the kernel, but starts u-boot, this does not work here. Issues: 1. u-boot does not have overlay support 2. u-boot loads its own dtb from storage, e.g. bcm2835-rpi-b.dtb 3. The u-boot boot.scr is loaded at address 0, and overwrites the boot loader provided dtb. The 3rd issue can be worked around with a "device_tree_address=0x1000" in config.txt. I tried to replace the "loadfdt" function in the boot.scr with a "fdt move 0x1000 0x2000000". Although the move succeeds, the kernel start crashes afterwards: ---- 4443840 bytes read in 1041 ms (4.1 MiB/s) 6946368 bytes read in 1403 ms (4.7 MiB/s) Copying FDT ... Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ] data abort pc : [<17f63d68>] lr : [<17f644e0>] reloc pc : [<0001dd68>] lr : [<0001e4e0>] sp : 17b48a50 ip : 17b521e9 fp : 17f51c54 r10: 17f91354 r9 : 17b49ee8 r8 : 17f922bc r7 : 17f922b8 r6 : 17b521e0 r5 : 00000003 r4 : 33554432 r3 : 00000000 r2 : 00000010 r1 : 00000000 r0 : 33554432 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... ---- instead of: ---- 4443840 bytes read in 1268 ms (3.3 MiB/s) 6946368 bytes read in 1753 ms (3.8 MiB/s) 8127 bytes read in 56 ms (141.6 KiB/s) Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ] ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 02004fbe ---- So either this approach needs more work, or a completely different approach is needed to get overlays to work. Any ideas? Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 9

[opensuse-arm] armv6 kernel update 4.1.3
by Michael Ströder 06 Aug '15

06 Aug '15

1 3

[opensuse-arm] Some tests with RPi 1 images
by Freek de Kruijf 06 Aug '15

06 Aug '15

I tested Build319.9 in /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ This image shows an error message about not finding the boot device and reboots again after 120 sec., etc. So there is something wrong in the partition boot. None of the images in this repository works. I tested Build330.7 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which still contains the bug in yast in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 When booting I see an error message about an error in a udev rule, but the system still boots. This system appears usable. I tested Build330.8 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which boots, but shows an error about /home and finally reboots again after a wait time of 120 sec., so does not work. -- 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

1 1

[opensuse-arm] Tests with RPi2 images
by Freek de Kruijf 06 Aug '15

06 Aug '15

I tested Build320.12 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/ which works OK. I tested Build321.14 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/ which works OK. Both these images do NOT show any message on the screen after the initial boot. As soon as the openSUSE boot image is used the screen blanks and only the final prompt is shown. It would be more instructive to see how the partitions are expanded and configured. When starting the image for the first time the date/time is set, apparently at about the date/time the image is build (Aug 05 02:00 CEST). Booting the image the next time this date/time is Jan 1 1970 02:00 CEST. I wonder if it is possible to preserve the shutdown time so that the next boot gets that time. In that case date/time in logs are ascending. -- 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

1 0

[opensuse-arm] armv7hl kernel-default config have tegra20 serial output broken
by Misha Komarovskiy 05 Aug '15

05 Aug '15

Hello, I found that latest images for my armv7 board (paz00/ac100) which use kernel-default have kernel panic on start without any output to serial console, but serial output was working last time i tested image back in may. I cloned kernel-source git repo made sequence-patched kernel and recompiled it with enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to config/armv7hl/default config, but found that there is no ttyS0 output, only earlycon here is paste: http://paste.opensuse.org/31390203 Recompiling same kernel with multi_v7_defconfig config and same debug/earlyprintk options have no panics and normal serial output: http://paste.opensuse.org/13080662 Maybe kernel-default config require some extra tricks now to have serial output? I want to catch that panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[opensuse-arm] u-boot update - Jetson TK1 patches
by Guillaume Gardet 05 Aug '15

05 Aug '15

Hi Andreas, you submitted u-boot patches for Jetson TK1 against 2015.07 version. I want to update to 2015.10-rc1 but your patches does not apply anymore. Probably because of tegra 210 addition. Could you provide an updated version of your patches against my home project, please? https://build.opensuse.org/package/show/home:Guillaume_G:branches:Base:Syst… Guillaume -- 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] Cubietruck 13.2 regression
by Andreas Färber 05 Aug '15

05 Aug '15

Hello, After upgrading 13.2 from kernel-lpae-3.16.7-7 to -11/-21 (why is it installing two new kernels btw?) I no longer have network. Diagnosing this is difficult because, as reported previously, the kernel does not provide any serial output to ttyS0. The LED lights up, which is done by my boot.local script, so it is coming up to some degree, just not far enough to login via ssh, and it's not reachable by ping either. I doubt this is just the dtb getting out of sync again? Originally it was a U-Boot 2014.10, but same with 2015.07 (and still working with a downgraded kernel/initrd). Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, 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 3

[opensuse-arm] Raspberry Pi 1 Model B+, No USB without b-plus dtb
by Evan McClain 20 Jul '15

20 Jul '15

Hi list, After rebasing my pi setup on a recent openSUSE image (since I was using raspberrypi branch kernels), it took me longer than I'm willing to admit to realize that the B+ needs to use the B+ dtb for things like USB to work. The kernel does boot with the rpi-b.dtb, but since USB isn't up the network devices aren't up and you can't plug in a keyboard to do anything about it. The ethernet MAC, serial, and revision still aren't being picked up, but this time I'm going with the ifcfg-eth0 change instead of switching kernels and editing the boot args. Have a lot of fun, Evan

3 2

[opensuse-arm] What repository is recommended for images for Raspberry Pi's?
by Freek de Kruijf 20 Jul '15

20 Jul '15

I am a bit confused about which repositories should be used for Raspberry Pi Tumbleweed images. Currently I have: for RPi1: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… for RPi2: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… -- 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

1 1

[opensuse-arm] Build327.8 for rpi1 broken
by Michael Ströder 15 Jul '15

15 Jul '15

HI! openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build327.8 does not work. It soon runs into a "rebootException" after start. FWIW openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build327.6 seems to work. Could someone look at the difference(s)? Ciao, Michael.

2 1

[opensuse-arm] Buiding Libreoffice 5.0
by Bill Merriam 14 Jul '15

14 Jul '15

I have for many months been trying to build Libreoffice on ARM with no success. There is a working build of it on Debian so it must be possible. I suspect the first thing they did is remove a whole bunch of obscure options that are hardly every used. This would remove pre-requisite packages and reduce the build time. I am trying now to build LO 5.0. It runs for a day and then starts over again. Can someone explain why this never builds? I am going to look at the package on Debian and see what options they use and how they break it into sub-packages. Maybe I will try building the Debian package on the openSuse Build System to see if there is a problem with the build system. Any thoughts on this would be appreciated. Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 4

[opensuse-arm] Corrupted files in recent Builds for RPi1
by Freek de Kruijf 13 Jul '15

13 Jul '15

When trying to build an updated package which was not available in the repository I needed the file: /usr/lib/perl5/5.20.1/armv6l-linux-thread-multi/Fcntl.pm which gives gives an error Right after putting the image on the SD card, I mounted the lxroot partition on /mnt/ll and got the following on the command: # ls -l /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-thread-multi/ ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Fcntl.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Config.pod: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Config_git.pl: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/.packlist: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Encode.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/GDBM_File.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/DynaLoader.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Config.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Config_heavy.pl: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/DB_File.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Errno.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/Cwd.pm: Invoer-/uitvoerfout ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux- thread-multi/B.pm: Invoer-/uitvoerfout totaal 428 [....] -r--r--r-- 1 root root 20519 23 jun 17:39 encoding.pm -????????? ? ? ? ? ? Errno.pm -????????? ? ? ? ? ? Fcntl.pm drwxr-xr-x 3 root root 4096 9 jul 04:38 File [....] -- 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

2 3

Re: [opensuse-arm] Experiences with Build317.3 for RPi2
by Dirk Müller 09 Jul '15

09 Jul '15

Hi, > Sorry for the slow response on this, I did not have time to look into this > recently. It appears that the issue is that the first boot does not detect > the MMC anymore, so it doesn't find the boot partition and goes into a > rescue reboot. I have reverted the commit that most likely is causing this > issue and am going to debug it further in the next day(s). hopefully the > next image build after build 317.6 should be working again. took slightly longer than anticipated since the kernel didn't build with gcc 5.x anymore, so I had to revert to gcc 4.8, but the image now works again, and I've moved all changes to :Staging and debug that image. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0