April 2014 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] OpenSuse 13.1 on beaglebone
by Sad Clouds 27 Apr '14

27 Apr '14

On Fri, 25 Apr 2014 08:32:44 +0400 "Matwey V. Kornilov" <matwey.kornilov(a)gmail.com> wrote: > Instructions look very common, the page might be created from > template. However, you help in editing the page would be highly > appreciated. 24.04.2014 23:26 ???????????? "Sad Clouds" < > cryintothebluesky(a)googlemail.com> ???????: > > > On Thu, 24 Apr 2014 09:40:06 +0400 > > Matwey Kornilov <matwey.kornilov(a)gmail.com> wrote: > > > > > Hi, > > > > > > It worked some time ago, but you need fetch images from > > > home:matwey:beaglebone > > > > I'm confused. I came to https://en.opensuse.org/HCL:BeagleBone_Black > > via Google. I assumed that page contained official instructions on > > how to get 13.1 up and running on Bealgebone Black. > > > > If it doesn't work, why have a page with instructions on it? Has > > anyone tested it, or did someone create it for a laugh? > > Never mind, I'll give another distro a try. Cheers. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 12

[opensuse-arm] SR for openSUSE:13.1:Ports kernel
by Matwey Kornilov 26 Apr '14

26 Apr '14

Hello, All. Could you please either accept or reply something on 224264? -- Best regards! Posted using Hotdoged on Android -- 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] OpenSuse 13.1 on beaglebone
by Sad Clouds 24 Apr '14

24 Apr '14

Hello, could I ask if OpenSuse 13.1 works with beaglebone? I followed instructions on https://en.opensuse.org/HCL:BeagleBone_Black However I get as far as "Starting kernel" and then nothing else happens. Any ideas? U-Boot 2013.04 (Mar 17 2014 - 15:34:07) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 1948 bytes read in 5 ms (379.9 KiB/s) Running bootscript from mmc0 ... ## Executing script at 80200000 kerneladdr=0x80200000 ramdiskaddr=0x81000000 mmc0 is current device 4500264 bytes read in 571 ms (7.5 MiB/s) 65308180 bytes read in 8153 ms (7.6 MiB/s) 21959 bytes read in 13 ms (1.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 81000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 65308116 Bytes = 62.3 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f885c6 Starting kernel ... -- 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: Asking for help about ARM version of SuseLinux
by Alexander Graf 14 Apr '14

14 Apr '14

Hi Mathias, Sorry for the late reply - I was on vacation and only now managed to work myself through my inbox far enough for your email :). Do you still see that problem? What exactly fails for you? Alex On 04.03.14 13:51, Mathias Bauer wrote: > Hi together, > > thanks for the hint with the IRC, I already joined. > > Any help is greatly appreciated! > > BTW: Maybe I wasn't clear enough in my mail, while I use clang for my > own code, the build of gcc that I tried was done with gcc (the same > gcc 4.7.2. that was already installed). > > (I had to remove Andrew from the list of recipients, my mail server > for whatever reason did not accept this mail address) > > Regards, > Mathias > > Am 04.03.14 13:04, schrieb Michael Meeks: >> Hi guys, >> >> An old friend is asking for some help with openSUSE on ARM - IMHO >> it's >> great that he wants to use openSUSE there. Alex / Andrew - is there any >> chance you can find the best person to help him and/or help out. >> >> Mathias - have you tried #opensuse-arm on irc.freenode.net ? that's >> prolly a good place to hang out too. >> >> Many thanks ! >> >> Michael. >> >> On Tue, 2014-03-04 at 09:55 +0100, Mathias Bauer wrote: >>> I'm currently trying to do some hacking on OpenSuse on an Arndale >>> Board, >>> but I ran into problems that I couldn't solve by myself and also didn't >>> find any solution by searching. Maybe you can point me to someone who >>> can help me? >>> >>> I'm using clang, but had problems with the exception handling. It was >>> activated for ARM processors recently, but it still has bugs that I >>> wanted to track down. >>> >>> So I tried to build the libgcc_s with debug information (that's where >>> the code for the stack unwinding is located, if I'm not wrong), but for >>> the life of me I can't compile gcc4.7 on this system. It's an Armdale >>> Board running OpenSuse 12.3 (image directly from OpenSuse, completely >>> unmodified). >>> >>> Do you know someone at Suse or a mailing list where I could get some >>> help? It's starting to drive me mad. >>> >>> All the best, >>> Mathias >> -- 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] kiwi does not find boot partition in Factory
by Guillaume Gardet 12 Apr '14

12 Apr '14

Hi, with Factory ARM images, kiwi is not able to find boot device on firstboot and we get: ******************************************************************************** [1397088002.636285] Including oem partition info file [1397088002.701788] Searching for boot device... [1397088022.334972] Failed to find boot device ! [1397088022.344577] rebootException: reboot in 120 sec... ******************************************************************************** It seems that modules from initrd are not loaded. In this case MMC modules are not loaded whereas they are in initrd. It works fine with 13.1 images with same kiwi version. I guess there is a change between 13.1 and Factory and kiwi may need some update so that modules get loaded? Any idea? Guillaume -- 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] chroot - /bin/bash not found?
by Per Jessen 11 Apr '14

11 Apr '14

For getting my Minix Neo X7 to run openSUSE, I have been using the chroot method as described here: http://en.opensuse.org/HCL:Chroot It has worked quite well on my laptop, but today I wanted to move it to a different machine. So I grabbed the latest rootfs image: openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz With this when I try to chroot, I get "/bin/bash not found". With Build32 it works though: openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build32.2.tbz -- Per Jessen, Zürich (12.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- 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] 13.1:Ports and Factory:ARM
by Guillaume Gardet 10 Apr '14

10 Apr '14

Hi Dirk, Hi Alex, We need you for some updates. 13.1:Ports: * JeOS-vexpress64 is setup to be build for armv7l instead of AArch64. => Just switch JeOS-vexpress64 build flag. * All DTB files are broken => Update from latest Base:System is a solution but we will lost Beaglebone Black fixes. * E17-beaglebone must be rebuild (failed due to a broken worker apparently) Factory:ARM: * JeOS-sabrelite, E17-sabrelite and XFCE-sabrelite links need to be created. Would it be possible to setup a contrib project for iMX6 SABRE Lite board, please? So that, I (and others, if any) can get things working for this board, as suggested by Alex. Regards, Guillaume -- 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] dtb-source
by Matwey V. Kornilov 03 Apr '14

03 Apr '14

Hi, It would be great if dtb-source version were in sync with the kernel one. What do you think, is it worth to reimplement dtb-source, using buildrequires: kernel-source instead of using linux tarball? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 8

[opensuse-arm] Re: [opensuse-kernel] [PATCH] ARM: update armv7 default config - master branch
by Alexander Graf 03 Apr '14

03 Apr '14

On 03.04.14 13:47, Guillaume Gardet wrote: > Le 03/04/2014 13:39, Alexander Graf a écrit : >> On 02.04.14 20:48, Guillaume Gardet wrote: >>> Hi, >>> >>> please find in attachment an ARMv7 -default config update to fix Ethernet and HDMI output on iMX6 SABRE Lite board. It also add initial support to USB on this board. >>> >>> This patch is against master branch. >>> >>> Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> >> Moving modules from =m to =y is the wrong answer usually. Why don't the modules work as modules? > I do not know. > Modules are loaded with no error but they do not work. The fact is switching FEC and SDMA from =m to =y fix the problems. It is true for 13.1 and master branches. Sascha, you're the one closest to upstream i.MX development that I'm aware of. Do you have any idea why we have to set FEC and SDMA to =y to make them work? Have you ever tried to use them as modules? Thanks, Alex -- 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] kernel default for armv7l
by Dirk Müller 03 Apr '14

03 Apr '14

Hi, anyone working on the xen bits build failure in kernel-default on armv7l on Factory right now? Tia, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2