Re: [opensuse-arm] Status of the Pie Images

Hi Guillaume, Unfortunately, we need to update kiwi package in Factory:ARM but it has not been done yet (probably because people with commit rights are on vacation.) Then, if all is ok, OBS will create a (working?) image. If new problems appears, we will have to fix them to get a working

[opensuse-arm] ARMv7 building down, will be up in a bit

Hi, unfortunately the file server for the ARMv7 build farm gave up due to a disk crash. I'll try to restore service. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] openSUSE Hackweek upcoming !

Hi, SUSE is doing another Hackweek shortly, and there is a website for it put online: https://hackweek.suse.com/ The Nuernberg SUSE employees will do a Hackweek October 7th - 11th, and we're looking for projects and interested people that want to join those projects. Community people are

Re: [opensuse-arm] kiwi fix for Factory:ARM

Hi Adrian, it should be submitted asap there because we will need it in 13.1 project if we want to build medias, right? The local patches in our package were only backports from git, so any newer version of kiwi fixes the issues. (And those kiwi changes are already in 13.1). Greetings, Dirk

[opensuse-arm] openSUSE 13.1 for ARM

Hi, I've removed the bootstrap-only paths from openSUSE:13.1 for the ports repository, so now we have the real state of affairs visible on OBS: https://build.opensuse.org/project/show/openSUSE:13.1 and to be honest, it doesn't look that good. many low hanging packages are failing to build

Re: [opensuse-arm] openSUSE 13.1 for ARM

Hi Andrew, Having a quick look at the failures on https://build.opensuse.org/project/monitor/openSUSE:13.1?arch_armv7l=1defaults=0failed=1repo_ports=1 both Firefox and Thunderbird need builders with 4GB RAM (even if it's a swapfile). Are you able to assign them to one? I can do that, but we

[opensuse-arm] Re: 13.1 ARM images still broken. kiwi problem?

Hi, kernel-exynos This one is used for Arndaleboard. Not sure what is upstream support. Alex, any idea? It is based on upstream sources (with some small additional patches). I think it will remain as an additional flavor for now. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] ARMv6 (raspberry pi) image partitioning broken?

Hi Guillaume, That sounds all too familiar to me... when I build locally JeOS-raspberrypi image, I get a *.raw image but it seems that partitioning is a bit strange. We have the 2 partitions: * 1st: FAT32 for Pi bootloader (mandatory unfortunately) with bootflag enabled * 2nd: EXT4 for

Re: [opensuse-arm] Devel ARM 13.1 Contrib projects pointing to the right project?

Hi Guillaume, We have devel:ARM:13.1:Contrib:* projects pointing to openSUSE:13.1 (repository=ports). Should not we make them pointing to openSUSE:13.1:Ports (repository=ports), so that we have latest fixes? The actual plan is to not have any extra code overlays in openSUSE:13.1:Ports.. all

Re: [opensuse-arm] Re: 13.1 ARM images still broken. kiwi problem?

Hi Guillaume, It is fixed for officials repos workers but workers used for home repos are still broken. Dirk, could you have a look at it, please? There is no differentiation between official and non-official workers. where did you see it failing (project/package)? Thanks, Dirk -- To

Re: [opensuse-arm] kernel update for 13.1 ARM images

Hi Alex, As the kernel does get built already as part of the Kernel:openSUSE-13.1 project, couldn't we just add that repo to the kiwi description and always have the latest kernel included that way? That has the drawback that images constantly rebuild (that repo is pushed once a day) and

Re: [opensuse-arm] kernel update for 13.1 ARM images

Hi Alex, I just noticed that armv6 and aarch64 builds fine but armv7 never built! No armv7 folder in download repo. Probably in scheduled state forever. Hrm, Adrian, any idea what's going wrong here? It just never gets scheduled before the code gets changed again. Lack of available build

Re: [opensuse-arm] kernel update for 13.1 ARM images

Hi Adrian, Apart from the constraints issues, we do have currently 1200 build jobs open for 16 armv7l workers. I pushed the priority for this particular project temporarly now, but IMHO we should re-consider the qemu build approach. The arm workers will not be able to handle it. Looking at

Fwd: [opensuse-arm] 13.1 on BeagleBone Black

Hi Matwey, http://lists.opensuse.org/opensuse-packaging/2013-12/msg00099.html Cool, thanks for the update! I've created a JeOS for the beaglebone using your patches: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS-beaglebone Hopefully it will work. Let me know how testing

[opensuse-arm] New AArch64 qemu emulator

Hi, I've just deployed a new qemu-linux-user emulator for aarch64 in openSUSE:Factory:ARM. The new package is based on qemu master git plus the pending AArch64 target support patches from Linaro and others. This is a new code base that hopefully fixes some of the annoying emulation bugs that we

Re: [opensuse-arm] Please trigger rebuild of openSUSE:Factory:ARM ImageMagick

Hi *, Could you, trigger rebuild of openSUSE:Factory:ARM ImageMagick. done Normally those manual rebuilds should not be necessary, as I have a cron job running that does that. There was apparently an error around ImageMagick now, hopefully fixed. yes at least direct dependencies. Is

Re: [opensuse-arm] Please trigger rebuild of openSUSE:Factory:ARM ImageMagick

Hi Guillaume, What is the advantage of your cron job vs an OBS auto trigger? Needed rebuild are triggered. No? The direct rebuild flag works different from the cron job. The cron job rebuilds packages that became uninstallable. The direct rebuild rebuilds all direct dependencies of a changed

Re: [opensuse-arm] dtb-source

Hi Guillaume, JeOS should be updated accordingly. If I didn't do a mistake there shouldn't be any reason to update JeOS.. am I missing something? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Freedreno vs. X11 module ABI mismatch

Hi Andreas, openSUSE:Factory:ARM/standard uses rebuild=local, so only a source change will trigger a rebuild. No, thats not actually true. we run the same rebuild trigger script like openSUSE:Factory does, so all packages that turn uninstallable will get rebuild automatically. The problem

Re: [opensuse-arm] Package clamav for ARM

Hi Freek, In fact it was Publish Flag, which are crossed out. https://build.opensuse.org/package/repositories/openSUSE:13.1/clamav The mentioned packages are for Factory while I am using 13.1 on a Raspberry Pi (armv6l). Ah, okay. Publishing of released distributions is a whole different

Re: [opensuse-arm] Factory signing key(s) expired

Hi Andreas, Both for ARMv6 and for ARMv7 I've been getting the warning that the signing key of the Factory repository has expired on May 4th. This has been fixed already, see curl http://download.opensuse.org/ports/armv7hl/factory/repo/oss/content.key | gpg -v you probably need to either

Re: [opensuse-arm] Build not enabled for Factory armv7hl at http://download.opensuse.org/ports/armv7hl/factory/repo/oss/

Am 21.07.2014 um 12:51 schrieb Arnd Gronenberg a...@gronenberg.com: What is the reason that no worker is capable of building it (status is scheduled)? Is there just a lack of workers for armv7hl or is there a technical problem to build the libqt5-qtwebkit package? Its not possible to

Re: [opensuse-arm] Build not enabled for Factory armv7hl at http://download.opensuse.org/ports/armv7hl/factory/repo/oss/

Hi Arnd, Unfortunately, the build for http://download.opensuse.org/ports/armv7hl/factory/repo/oss/ seems to be disable for a couple of weeks, last builds were create around May 20th. I've force-published the current state of the tree now for armv7hl. Unfortunately the state is not that good

Re: [opensuse-arm] openSUSE JeOS Factory Build 207 not booting on Raspberry Pi

Hi Alex, But if I don't load the fdt file (bcm2835-rpi-b.dtb - what is that anyway?), I get all the way to the network: the fdt file is the device tree, its a binary blob that should exactly describe the hardware. This is used to avoid the kernel having to guess about the hardware (as

[opensuse-arm] [PATCH] Disable Exynos cpufreq modules

0001-Disable-Exynos-cpufreq-modules.patch Description: Binary data

Re: [opensuse-kernel] Re: [opensuse-arm] [PATCH] Disable Exynos cpufreq modules

Hi Alex, Would you mind if we only apply this to openSUSE-13.2 and leave it enabled on HEAD and STABLE? Then we can cross our fingers that the code will be fixed one day ;) I don't think it will work without the voltage regulator being compiled in. so for master this change would be needed

Re: [opensuse-arm] ARM in the 13.2 release announcement

Hi Andrew, Is there any chance we could rustle up a paragraph or two of the key ARM related features for inclusion in the announcement? Things I can think of - Unified kernel for ARMv7 (listing platforms supported), Yes, I think thats the main new feature. Both ARMv6 and aarch64 tree's are

[opensuse-arm] Re: Cubieboard2 JeOS Factory image broken

Hi Oscar, I'm trying to use the JeOS image for cubieboard2 but it fails to load anything because u-boot-cubieboard2 and its DT file are not included in the kiwi image. Thanks, I was already wondering how the cubieboard2 image works. I've converted it to the bootz code path now, but I noticed

Re: [opensuse-arm] getbinaries: missing packages: kernel-obs-build

Hi Michael, But it fails with: getbinaries: missing packages: kernel-obs-build Build seems to work now after setting VMinstall: !kernel-obs-build Whoops. should be fixed fairly soon (asap the OBS recovers from its current outage). Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] getbinaries: missing packages: kernel-obs-build

Whoops. should be fixed fairly soon (asap the OBS recovers from its current outage). Should be fixed now. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Which repo for rasperry pi

Hi Michael, http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ Does this repo receive all the openSUSE updates? It is following Factory (aka nowadays called openSUSE Tumbleweed), so yes. but its a rolling release, so you will frequently get new versions of packages and the overall

Re: [opensuse-arm] kernel-obs-build and qemu/arm/ppc

Hi Adrian, first of all, it makes sense to use kernel-obs-build also for qemu to avoid situations like in the last days were the worker host initrdkernel is not sufficient anymore for building. Just an exportfilter is needed to get the kernel-obs-build package from the right architecture.

Re: [opensuse-arm] [ARM] armv7 workers are broken

Hi Andreas, [ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init! exitcode=0x [ 6737s] [ 6703.295918] [ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System halted Apparently the guest kernel needs more features now, I’ll look into it.

Re: [opensuse-arm] [ARM] armv7 workers are broken

Hi Adrian, [ 16s] linux64 /usr/bin/qemu-system-arm -no-reboot -nographic -vga none -net none -enable-kvm -M virt Thats the issue, some when the build script was changed to use -M virt. It would have been great to know such major changes that in advance :-( I’ll try to fix it up now so

Re: [opensuse-arm] [ARM] armv7 workers are broken

[ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init! exitcode=0x [ 6737s] [ 6703.295918] [ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System halted Apparently the guest kernel needs more features now, I’ll look into it. This is now fixed,

Re: [opensuse-arm] [ARM] armv7 workers are broken

Hi, hm, does it make sense to have also virt kernelinitrd images in kernel-obs-build package? No, the -default flavor should just run on all machine types. It should, but its not as efficient. -default is more than twice the size (and needs initrd) than the guest kernel.. its not that

Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2

Hi Freek, Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again. yes, the kiwi firstboot somehow wrecks the firmware, so a 2nd boot fails. I currently think it is the resizing during initial boot, but it could be

[opensuse-arm] Attempt to run KIWI on unsupported architecture 'armv8l'

Hi, this is a known OBS bug, asked the admins to deploy a fix shortly. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] armv6l is missing on repository openSUSE-13.2-repo-update

Hi Freek, When running zypper up on my Raspberry Pi I get a warning about an obsolete repository openSUSE-13.2-repo-update. Looking at http://download.opensuse.org/ports/update/13.2/ I do not see anything about armv6l I wonder why? The Raspberry Pi 1 build (armv6l) was experimental with

Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2

Hi Michael, And how about the rasperry pi #1? Will the image also be fixed? I can't help with kernel problems. But I can test stuff. Can you point me to the issue that you're hitting? Perhaps I can help (although I don't own a RPi 1). Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] Re: qemu-linux-user breakage - armv6l / aarch64

Hi, Shouldn't o:F:ARM be using the o:Factory qemu package? Well, traditionally we've linked Virtualization there because we a) need to build qemu-linux-user special anyway for the cross-building to work properly and b) we usually prefer the fast turnaround time over using the devel project

Re: [opensuse-arm] Please create missing _link from u-boot-rpi2 to u-boot in Base:System

Hi Guillaume, I just updated u-boot to 2015.04-rc3 in Base:System, but we are missing u-boot-rpi2 package which should _link to u-boot. Could you fix this, please? Sure, done. I'll link this in devel:ARM:Contrib:Factory:RaspberryPi2 momentarily -- To unsubscribe, e-mail:

Re: [opensuse-arm] openSUSE Factory ARM DTBs are outdated

Hi Guillaume, the DTBs in Factory:ARM are all outdated. Could you trigger a rebuild, please? Done. The real fix is to make sure that the packages become uninstallable if the kernel version does not match, then they will get rebuild automatically. Ill take a look at that.. Currently,

Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2

Hi, There's a v3 patchset on the u-boot mailing list, but that's surely not yet in our Base:System u-boot package. You'd need a u-boot-rpi2 Contrib package with those patches applied to create an image. The u-boot patches are actually in git already and will be in the next stable release

Re: [opensuse-arm] NTP service fails to start

Hi Volker, # zypper in util-linux-systemd (1/1) Installing: util-linux-systemd-2.26-1.1 .[done] # systemctl restart ntpd Works. Cool! Thanks for finding this out. I've fixed Factory and 13.2 to include this package now, so fixed images should be available shortly. Greetings, Dirk

Re: [opensuse-arm] Re: qemu-linux-user breakage - armv6l / aarch64

Hi Andreas, Factory should not be affected (I don't submit -rc0), only OBS setups using qemu-linux-user from the Virtualization project directly, such as the armv6l and aarch64 builds (but not armv7l). [...] Depending on whether qemu-linux-user is taken from Virtualization or not, is might

[opensuse-arm] Re: Broken RaspberryPi 1 images

Hi Alex, Thank, I look forward to testing it. kernel-default from here: http://download.opensuse.org/repositories/home:/dirkmueller:/branches:/Kernel:/stable/ARM/armv6hl/ contains the minimal fixes neede and seems to work fine according to Michael, and shortly there will be a

Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2

Hi Freek, I studied on the BOOT disk the file boot.script and found in the value for bootargs the parameter disk=/dev/disk/by-id/mmc-0_0x1537043d . I have the feeling there should be -part? appended, where ? should be 2 or 3. Both root= and resume= have -part3. respectively -part4

Re: [opensuse-arm] u-boot-vexpressaemv8a dropped upstream

Hi Guillaume, I am updating u-boot to 2015.04-rc5 and u-boot-vexpressaemv8a has been dropped. Instead, we have 2 flavours: vexpress_aemv8a_juno_defconfig and vexpress_aemv8a_semi_defconfig. Should we simply drop our aemv8a config or enable one or both new configs? Not sure if it is used at

Re: [opensuse-arm] u-boot-vexpressaemv8a dropped upstream

Hi Guillaume, Ok, so please accept SR #294289. Done, thanks! -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] u-boot update - Need package rename

Hi Guillaume, *, No, it is similar to kernel builds : same sources, but various patches, different configs. Moreover, binaries produced may be named identically. Right. Personally I think the best solution would be to move the devel project for u-boot to devel:ARM:Factory and give Guillaume

Re: [opensuse-arm] ARM sunxi devicetree not up to date

Hi Frank, it seems that the sunxi device trees are not rebuild This has been fixed already, just waiting for OBS to finish publishing (hopefully within the next day or so). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

Re: [opensuse-arm] Some problems with Tumbleweed on Raspberry Pi B 1

Hi Freek, 1. zypper can't be updated because the proper version of libzypp is not available. In openSUSE Build I see building of libzypp for Factory disabled for all ARM architectures. Is there a problem with building this library? The build is not disabled, not sure where you looked:

Re: [opensuse-arm] openSUSE:Factory:ARM / aarch64 is now building on native hardware

Hi Ludwig, of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the local arch used for image building. armv7 isn't that slow, its just armv6. anyway, where is that restriction of overall settlement coming from? the OBS is not

Re: [opensuse-arm] Re: openSUSE:Factory:ARM / aarch64 is now building on native hardware

Hi Matwey, Can this hardware be used to build armv7 on it like x86_64 and i586? No, we kept this separate for now. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] openSUSE:Factory:ARM / aarch64 is now building on native hardware

Hi, for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available. == What changes == If you have packages enabled for building against openSUSE:Factory:ARM, nothing

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

Hi Andreas, Why wasn't it tested? Good question. Why does this suddenly depend on Factory? IIRC this was changed March 23rd based on your announcement that there are issues with 2.3.0-rc0. openSUSE:Factory:ARM uses qemu-linux-user from Virtualization, which means that if there were a

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

HI Andreas, its a bad worker and restarts the job on a different host, only to fail there the same way. It is only noticed then by an admin seeing You don't need to be admin to notice the problem. well, either that or actively waiting for a job to start, reloading the webui often enough so

[opensuse-arm] Factory/Tumbleweed and the switch to GCC 5.x

Hi, as you might know, Factory is currently in preparation of transitioning to use GCC 5.0.x as the system compiler. There are several oddities to sort out with that, and I would expect additional issues for our ARM architectures in the form of miscompiles and ICE's. To find those issues before

[opensuse-arm] Factory rebuild for icu / boost / ruby 2.2

Hi, a couple of updates went into Factory in the last few days that broke ARM, mainly due to bootstrap loops that needed to be resolved manually. I've done that now, and things are rebuilding. Hopefully tomorrow morning there should be a working tree again (unless something else enters factory

Re: [opensuse-arm] sunxi device tree outdated

Hi Andreas, There is in fact a BuildRequires: kernel-source, which should in theory trigger a rebuild once kernel-source is updated. No, only new sources trigger a rebuild. Not true either. Any change that causes a package to become uninstallable which was previously in succeeded state will

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

Hi Alex, The easy fix is to s/g_new/g_new0/ to expose the same allocation semantics as before. I've changed the code accordingly and submitted a fixed qemu package to the Virtualization project. Ah great, thanks for the quick fix. I've switched openSUSE:Factory:ARM to that new version now!

Re: [opensuse-arm] oS 13.2 on cubieboard1 doesn't start booting

Hi Volker, No NTP (ok solved, but it's not stable release). No, its not a stable release, but its definitely easier and quicker to fix factory than a stable release. the fixes to stable release require coordination with many people and usually have weeks/months of turnaround. Factory is quicker

[opensuse-arm] Re: Broken RaspberryPi 1 images

Hi Michael, This seems to work! :-) # uname -a Linux srv10 3.19.2-6.g7088b79-default #1 Wed Apr 1 15:14:39 UTC 2015 (7088b79) armv6l armv6l armv6l GNU/Linux Excellent. could you please as a last test also boot the 4.0-rc6 from here:

[opensuse-arm] ARM build workers updated

Hi, I just finished updating the majority of armv7l/aarch64 build workers to newer software versions (qemu 2.3.0, kernel 4.0.4, various bug + security fixes). It looks good to me, and I also fixed a few broken ones alongway, so we have more build power than before. Let me know if there are new

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, I tried to find the project on build.opensuse.org that builds libstorage-ruby, but could not find it. its a subpackage of libstorage: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/libstorage Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] Image repos needs cleanup

Hi Guillaume, Repo still needs cleanup. :( I know. I've mailed the OBS admins and still have not gotten a reply :-( Pinging again.. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, A new factory ftp tree has been published (finally). Does that one work as well for you? It works for RPi2 (date is June 3), but for RPi1 it is not published yet (date still February). Great, thanks for confirming. ARMv6hl also published now, but the package is old due to it no

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, I reported a bug in http://bugzilla.suse.com/show_bug.cgi?id=933274 about an Internal error in YaST. This problem is caused by a non-up-to-date ruby module on armv7l which is blocked by a boost library. Is it possible to look into the problem with the boost library in armv7l? The

[opensuse-arm] Re: Factory/Tumbleweed and the switch to GCC 5.x

Hi *, To find those issues before they happen, I've created a Staging project of Factory which builds against GCC 5: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Staging:A Since we switched to GCC 5.x now in Factory, I've deleted the project (and triggered a rebuild of

Re: [opensuse-arm] openQA : ARM qemu and real hardware?

Hi Guillaume, 2015-05-27 14:32 GMT+02:00 Guillaume Gardet guillaume.gar...@free.fr: I know that some work have been done to get openQA working on ARM through qemu, but also on real hardware. That work was so far only on aarch64/kvm (e.g. running on aarch64 hardware inside a KVM virtual

[opensuse-arm] aarch64 build workers updated

Hi, I just updated the aarch64 build workers to a newer host kernel. Let me know if there are new issues. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Buiding Libreoffice 5.0

Hi Bill, 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've been trying to debug that myself, it is an instability on the build host.. it probably doesn't help that we have multiple projects trying to build

Re: [opensuse-arm] cuboxi tumbleweed images don't boot

Hi, > Sounds good. Does that mean we can build JeOS in openSUSE:Factory:ARM > proper then or are there further dependencies? it looks like there was a really old kernel in there. I removed it now and switched to the factory kernel. can anyone verify that it boots ? Thanks, Dirk -- To

[opensuse-arm] Re: Factory:ARM publishing is disabled

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

Re: [opensuse-arm] 13.2 ARM updates

Hi Volker, > Loading repository data... > Warning: Repository 'openSUSE-13.2-repo-update' appears to be outdated. > Consider using a different mirror or server. Looks like the publishing got stuck again. filed a ticket against infra team.. Thanks, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] 13.2 ARM updates

Hi, > I filed another ticket with the sysadmin team since the previous one > got closed as fixed, although nothing changed so far. It seems mirroring to the outside got fixed, a bunch of new updates got pushed today. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] 13.2 ARM updates

Hi, >> AFAIK there will not be any update on 13.2 for armv6hl, only armv7hl. > That's fine, I'm interested in armv7hl updates. I filed another ticket with the sysadmin team since the previous one got closed as fixed, although nothing changed so far. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] armv6hl excluded for Kernel:stable?

Hi Stefan, > ARMv8/7 are likely to deal with a whole range of boards, configured in detail > by device tree blobs, so there is a range of SoCs and pheripherals (PMICs, > GPUs, ...) covered by these architectures. Correct. > > ARMv6 is mostly/only? targeted at Raspberries. So no PMIC, VC4 GPU,

Re: [opensuse-arm] Tumbleweed fails to boot in a Cubietruck

Hi, > According to [1] this should be fixed in Kiwi with: > https://github.com/openSUSE/kiwi/pull/521 > > It was merged. Is that maybe not checked into Tumbleweed yet? > Guillaume/Matwey, did you notice any improvement yet? Its not in tumbleweed, I'll add an overlay again. Greetings, Dirk --

Re: [opensuse-arm] No new JeOS images for Raspberry Pi 1, also meant for Raspberry Pi Zero?

Hi Freek, > Since September there are new images for other environments than JeOS, but not > anymore for this environment. These last images did not work, I don't know > why. Is that the reason there are no new images? Yeah, we're having issues with the build emulation. A fix is in preparation,

Re: [opensuse-arm] Udoo Quad (IMX6Q) hangs at kernel boot

Hi Oscar, > Now I would like to debug why it doesn't work with a current kernel. First > step (IMHO) is to try the same kernel version but with the default config. > Is there a way in OBS to recover a package to a point in time? If that's not > possible, what should I do now? you can recover the

Re: [opensuse-arm] Leap for armv7l

Hi Michal, >> Apparently you didn't search the list archives: >> http://lists.opensuse.org/opensuse-arm/2015-11/msg00011.html > Yep, I was searching in OBS, didn't expected answer this bad. Not sure how that answer is related to the question anyway.. So to summarize: Leap 42.1 is in sync with

Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > I have disabled for now kernel RNG support in the build script for arm, > but we need to discuss if we want to have this in future (by having > proper kernel and initrd support for it) or if we should disable it in > general for arm. Not all ARMv7 workers have support hardware

Re: [opensuse-buildservice] Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > That was the version which caused the problems on arm 32bit > with the the kernel/qemu startup Not really :-) the change fixed the problem. the issue was that somebody ,while editing the build script, forgot to remove the reference to the -pci device and only added the -device

Re: [opensuse-buildservice] Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > the current git master is the one with caused the armv7 failures, do > you speak about that one? When we talk about why armv7 fails, then yes, thats because https://github.com/openSUSE/obs-build/pull/210 is not merged in git master. Don't be confused by the "merged" state in github,

Re: [opensuse-arm] Most ARM v7 workers are broken

Hi, > Actually, I wonder if the rng stuff is really worth the effort > when the majority of our systems is not supporting it. passing through virtio-rng is definitely a good idea especially with the terrible openssl on SLE12 that requires several kilobytes of entropy for generating a trivial RSA

Re: [opensuse-arm] RaspberryPi3 and Aarch64

>> Let me know what happens. I am using the 32bit image right now, but for sure >> 64bit is more interesting. :) > The file above shouldn't exist really. Why? its (supposed to be) the regular Tumbleweed image, which in theory after we sorted out the pending u-boot and raspberrypi-firmware image

Re: [opensuse-arm] Leap 42.2 ARM: Ring 0 status

Hi Matwey, > Could you please take(aggregate) kernel-obs-build for > openSUSE:Leap:42.2:Ports [...] Thanks, I'm working on it (just returned from vacation today). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

Re: [opensuse-arm] kdump on arm

Hey Matwey, 2016-05-20 22:10 GMT+02:00 Matwey V. Kornilov : > Is kdump supposed to work on armv7l? Which kernel should I use as kdump > kernel? kdumptool doesn't like -default for me: > > # kdumptool find_kernel > Kernel '/boot/vmlinux-4.6.0-1.gd9e67cc-default' is not

[opensuse-arm] Re: JFYI: armv7l kernel for Leap 42.2

Hi Matwey, >> According to Michal, OBS Kernel:openSUSE-42.2 repo should be built >> automatically for armv7hl once when armv7hl is enabled in >> openSUSE:Leap:42.2:Ports (listed in rpm/config.sh). > > kernel-source repo looks for Update project (not Ports): >

Re: [opensuse-arm] Tumbleweed Raspberry Pi2 i2c-tools not work

Hi, 2016-05-19 12:00 GMT+02:00 Денислав Радославов : > After two months (first report for this bug -forum and mailing list), > bcm2835 modules working fine, but i2c-tools again not working. Missing > packages python-smbus is big problem. Have ready packages, Is it so hard >

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > Further I had repeatedly said that if you guys care about a Contrib > repository, such as RaspberryPi2, then you need to update and clean it > up yourselves. Guess how many people did since then. Well, normally the responsibility of fixing something is with the one who broke it.. I

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > Actually I think it is unfair of users to expect that SUSE engineers > must be the ones to fix things if random boards break I don't think anyone was calling for a "suse engineer". Users were asking for the openSUSE ARM contributors to take a look at the regression. I don't think

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Freek, > I don't think it is the proper way to use a serial cable to test images for > the Raspberry Pi 1. I made a wild guess on what the problem might be for the rpi1 image (I don't own such hardware), since the issue is imho universal (it broke all armv6/7 images). I've submitted a fix for

Re: [opensuse-arm] pihwm package relocated

Hi Andreas, > If you want to get this submitted to Factory, please step up as > maintainer and start the process: do an SR from hardware to > openSUSE:Factory and write an email to opensuse-factory mailing list > pointing to SR# and explaining the package (cf. raspberrypi-firmware). Just to

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > The people that took action here - myself, Alex, Andreas - all are, and > we're less than the users asking. .. action that you *perceived* to take action. A strong difference! > It could be documented a) in the spec file, b) in the package or project > description. And some

Re: [opensuse-arm] opensuse on odroid u3?

Hi Dieter, > Copying the SUSE image into that and booting it, also fabulously worked. > Even updating that 13.1 image to the latest state was possible. We have exynos 4 support disabled in the tumbleweed kernel, thats why. if you have patience to retest an image, I can branch a kernel with

Re: [opensuse-arm] Current Pi2 image

Hi Michael, 2016-02-03 21:05 GMT+01:00 Michael Emory Cerquoni : > I also had good success the only problem I am having now is I am stuck > in 800x480 resolution the raspberrypi-userland package needs to be > uninstalled Do you mean it needs to be *installed* ? Because

[opensuse-arm] Temporary outage

Hi, There is a network connectivity issue to the ARMv7 Build cluster right now on OBS. It is being investigated today. Hopefully workers are back up before the weekend. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

  1   2   >